Related
So I was following the tutorial HERE to install TWRP, after successfully installing root via the previous tutorial.
I got to the step where you have to hit "reboot" on the kindle screen, and then press any key in the CMD prompt. I waited till it was on the yellow triangle screen, with text at the bottom stating I can press power button for recovery. I hit "space" to progress my installation, and it got stuck at "activating normal <4000>" as the video said might happen.
Following the instructions, I opened Device Manager and sure enough, the kindle was displaying a missing driver icon (although mine was still called kindle, in the video it was called something else.) I told it to reinstall the drivers, and this is where it got strange. It claimed the driver was up to date, but still displayed the yellow driver error symbol. Now, when I plug in the kindle, it shows up as "unknown device" and when I try to install the driver, it claims my driver for unknown device is up to date.
Meanwhile, the kindle itself it chilling on the yellow fire/triangle screen.
wat do
It says your drivers are up to date? You shouldn't be trying to auto install drivers, you have to do it manually, or are you trying but its just not letting you?
I am manually selecting the folder in the Device Manager dialog, and it tells me that the driver for "unknown device" is up to date
I have found that if I turn the kindle off by holding the power button down, then plugging it in(while off) it will show up as "ADB Device" (not ADB Composite Device), but nothing works, and if at this point it is unplugged and re-plugged in, it returns to Unknown Device giving an error code 43
Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally
googlelover said:
Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally
Click to expand...
Click to collapse
well, I got it to display "ADB Composite Interface, but when I run the KFU, it says ADB Status: Offline.
Furthermore, when I run "adb devices" my kindle does not show up
What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery
SirVilhelm said:
What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery
Click to expand...
Click to collapse
I added the 0x18D1 to adb_usb.ini, and I beleive it was already in the other .inf file. Now, my kindle is connected, and device manager sees adb composite device, but adb devices says nothing is connected. Im feeling a reboot might be necessary, which sucks because my computer doesnt reboot well (long story)
You can try adb kill-server and try again
Trouble
Having trouble getting TWRP to install on my Kindle Fire, I had no problems getting it Rooted and getting the Market installed, but trying to run the TWRP program it just hangs at the waiting for device and the Kindle hung at the KindleFire logo. I'm running Window's 7 64 bit is this suitable for TWRP
Thanks for any help.
SirVilhelm said:
You can try adb kill-server and try again
Click to expand...
Click to collapse
it is still not seeing the kindle connected. Anyway, how do I use KFU to restore the device?
I fixed my device using the info I found in a thread: http://forum.xda-developers.com/showthread.php?t=1431785
fastboot oem idme bootmode 4000
fastboot reboot
Unplug your Fire from USB, turn it off (hold the power button ~30 sec), run the first fastboot command above, then plug it in. If the first command completes, do the second.
Click to expand...
Click to collapse
I got a nexus 7 2012 wifi 32gb today, updated to 4.3, and I have had nothing but problems trying to root the thing. I have been unable to unlock the bootloader, currently whenever I'm in bootloader mode windows 7 64 bit just shows it as an "unkown device" when I look at the properties it says "Windows has stopped this device because it has reported problems. (Code 43)" I have tried "update drivers" and had it look at C:\PROGRAM FILES (X86)\WUGFRESH DEVELOPMENT\DATA\DRIVERS but it just says the drivers are up to date for my unkown device. There was actually a point where in bootloader mode windows had device manager say bootloader something instead of unkown device however it says drivers were not installed and I think the error code was 10 or something, basically it was still useless and would not recognise my device and install drivers. I have tried on my laptop which has windows 8 64 bit but it is far worse there, the computer keeps giving malfunction usb message or something over and over again as if the device is constantly connecting and disconnecting. Despite this however MTP works fine and I have transferred a music album over as a test and it was fine and the device charges fine too. Would really appreciate help as I'm desperate at this point.
Uninstall whatever out of date drivers that came with the toolkit then install the latest Android Composite ADB Interface Driver 8.0.0.0.
You also need to install this in order to use ADB while in recovery.
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Short of going back in and deleting (not just uninstalling) every USB driver, might be easier to borrow another computer?
lightlink7 said:
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Click to expand...
Click to collapse
The Android Composite ADB Interface Driver 8.0.0.0 driver from SDK is for bootloader and when booted into ROM. Naked Driver 0.72 is only for when in recovery or else your computer would show "Nexus 7" under Unknown Devices in the Device Manager.
I Flashed the latest version of android 6.0 from the google's factory images website, and now want to root my NP.
However, I'm don't see the device in the device manager anymore (I've enabled usb debugging).
"adb devices" returns nothing neither on my mac or windows laptop.
Please help!!!!
OK, got it sorted out
so I left the NP connected to my windows laptop, and played around with the usb debugging,
turned it on and off for 3-4 times and suddenly my laptop recognized it and I started seeing it in the device manager.
but "adb devices" was still returning nothing!!!
so unplugged the usb cable plugged it back in, and suddenly I got the message on my NP to trust the device that was connected to it
after I checked that, now I "adb devices" returns my device.
Nexus Player Driver Isuues
s_hamid_d said:
I Flashed the latest version of android 6.0 from the google's factory images website, and now want to root my NP.
However, I'm don't see the device in the device manager anymore (I've enabled usb debugging).
"adb devices" returns nothing neither on my mac or windows laptop.
Please help!!!!
Click to expand...
Click to collapse
If you have any issues with Computer not detecting Nexus Player it is the driver. Very easy to sort. Keep the drivers in a safe place and just reinstall by doing driver update and point towards it manually. This worked for me on all roms without any issues.
Hi. I am trying to sideload the Android 6.0.1 update but am having some problems detecting the device in recovery mode.
I have previously unlocked my bootloader on the day i got my phone.
I have enabled USB Debugging and have installed android USB Driver 11.0.
On my Windows 8.1 Device Manager...
When I am in normal android = Android Composite ADB Interface is present.
When I reboot to Bootloader = Android Bootloader Interface was installed.
However, when I am in the stock recovery, Android Composite ADB Interface is not found. Neither is there any unknown devices in my Device Manager (yellow question mark) that might look like the ADB Interface.
As a result, when I am in Recovery Mode, "ADB Devices" command does not work.
Help? Thanks!
Same here!
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!
I am having this same issue. I've installed HiSuite with the latest USB drivers and have the latest Android SDK Platform Tools updates. I have tried unplugging and plugging-in the device when it is in recovery to try and trigger something but nada. I've tried different USB ports too.
My behavior is exactly the same. The phone shows up in ADB devices under normal full boot and also in the bootloader. As soon as it goes to stock recovery it won't show up as a device in Windows anymore. Not as an even an unrecognized device.
Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.
Minlock said:
Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.
Click to expand...
Click to collapse
Thanks! I realised im actually on Windows 10 too...
However, your method doesnt seem to be working for me.
In Recovery mode, "Android ADB Interface" doesnt show up. Hence, I added a legacy hardware as you suggested, but it shows up that "This device cannot start. (Code 10)".
I also tried to update the hidden "Android Composite ADB Interface". While driver installation was okay, the phone is still not detected.
I tried replugging in the phone into a different USB port but it is still the same.
Strange... seems like only some people are encountering such issues? Wonder what is the difference. Thanks.
okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....
l0nEr said:
okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....
Click to expand...
Click to collapse
After doing all the previous steps, doing this step really did the trick.
Thanks!!!
makeitra1n said:
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!
Click to expand...
Click to collapse
i'm here too
I had same problem and after searching days it solved by installing universal ADB Drivers from the link below:
Universal ADB Drivers
Hi!
So I've just received my Oreo 8.1 update. but before updating, I decided to backup my EFS/persist after some reading in this forum.
Turns out ADB works fine, "adb devices" shows my phone ID but when I reboot to booloader, fastboot doesn't work, it doesn't show my phone ID.
While on ADB mode:
On Windows 10 Device Manager, Moto G5 Plus is listed under Android Devive > Motorola ADB Interface. (Everything ok here, no exclamation mark, working as it should)
-While on fastboot mode:
Phone gets listed under "Other Devices" as "Fastboot Potter S" (exclamation mark inside a triangle)
Tried uninstalling/reinstalling motorola drivers but I always get: Windows found drivers for your device but encountered an error while attempting to install it."
-Moto G5 Plus (XT1683) - Stock, Nougat 7.0 ( NPNS25.137-92-14 )
-Debugging mode is enabled.
-When connected to the PC, If I change from Charging to Transfer Files, my phone doesn't show up as another drive where I can transfer files and also gets listed as MTP (Exclamation mark/Triangle) under "Other Devices"
-Windows 10. Updated.
Anyone has been through that? Any ideas, tips, solutions or workaround would be appreciated.
Use "Fastboot Reboot Bootloader" device will go to bootloader automatically without the need of switching off.