Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Can't get an MK808 (2207:300a) to list with adb

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can't get an MK808 (2207:300a) to list with adb

    Anyone else have a 2207:300a one that could offer some advice? The only way I can get it to show up is from holding the button down when plugging it in. And when it does that, it still will not show up in the adb devices list.

    #2
    What windows version are you on and how did you install ADB drivers?

    If on windows 7 you may have to make a ini file manually.
    go into users>your user name> and create a folder .android if it is not there. Now in .android create a file called adb_usb.ini and in this file put this device ID 0x2207

    Bob
    "Pzebacz im, bo nie wiedzą, co czynią"
    "Прости им, они не ведают, что творят"
    "Perdona loro perché non sanno quello che fanno"
    "Vergib ihnen, denn sie wissen nicht, was sie tun"
    "Vergeef hen want ze weten niet wat ze doen"
    "Pardonne-leur car ils ne savent pas ce qu'ils font"
    "Perdónalos porque no saben que lo que hacen"
    "Oprosti im, jer ne znaju što čine"
    "Forgive them as they know not what they do"





    Comment


      #3
      I do not use windows, I run linux. I already have the lines in my adb_usb.ini file. They are also in my udev android.rules file. They are listed below. I seem to have another problem now though. My stick will not boot. I have not yet done anything to it but it just sits at the android bootsplash.

      ~/.android/adb_usb.ini
      Code:
      # ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
      # USE 'android update adb' TO GENERATE.
      # 1 USB VENDOR ID PER LINE.
      0x1949
      0x0006
      0x0005
      0x2207
      0x0e79
      /etc/udev/rules.d/51-android.rules
      Code:
      SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", MODE="0600", OWNER="eshep"
      SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0005", MODE="0600", OWNER="eshep"
      SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0600", OWNER="eshep"
      Sorry, I should have included those to begin with.

      Comment


        #4
        If it wont boot then the /data file system got corrupted. Common to happen with these units if you just unplug it while Android is up. Your going to have to flash a ROM to it now.

        Bob
        "Pzebacz im, bo nie wiedzą, co czynią"
        "Прости им, они не ведают, что творят"
        "Perdona loro perché non sanno quello che fanno"
        "Vergib ihnen, denn sie wissen nicht, was sie tun"
        "Vergeef hen want ze weten niet wat ze doen"
        "Pardonne-leur car ils ne savent pas ce qu'ils font"
        "Perdónalos porque no saben que lo que hacen"
        "Oprosti im, jer ne znaju što čine"
        "Forgive them as they know not what they do"





        Comment


          #5
          How would I go about flashing it when it wont show up for adb? Is there another way to flash these things? I found one post about throwing an update.zip on the SD card and it will update upon boot but that does not work.

          Comment


            #6
            [SOLVED] Flashed with Finless 1.7c

            I was able to locate a Win7 machine to use this method on and it worked brilliantly.

            Thank you so much Finless Bob for your hard work and dedication to hacking these devices.

            Comment

            Working...
            X