Related
Hello guys
I've got some serious issues with my DHD (and Vista). It all started up by trying to install HTC Sync on my computer. After a month of countless attempts i was unable to get it working as well as internet pass-through. But today when i attempted a root, i couldnt use any adb command because it kept giving me an "error: Device not found". When i tried "adb devices" it showed me "List of devices" but no serial number below. I tried to install USB drivers through Android SDK but with no succes and i even tried some HTC USB drivers. No chance. In device manager i can see "Android phone" and "Android ADB interface" with the exclamation mark. So does anybody know how to get those USB drivers working so i can downgrade an root my phone? thanks
you probly have it on.. but you do have usb debugging switched on?
htc sync drivers should have install no problem so maybe uninstall them and reinstall with admin permissions.
did you update sdk drivers by sdk manger?
this post could help
http://forum.xda-developers.com/showpost.php?p=10054771&postcount=271
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
Since I can't post on the actual threads yet, due to being a new account, I will be posting here in hopes that someone comes across this and can help me out.
I have done a pretty hefty amount of reading trying to get my Nexus 7 rooted and for some reason I just can't get past the part of installing the necessary drivers for my computer.
Specs:
- Windows 7 32 bit. (Administrator account)
- Nexus 7 32GB (Wifi) running 4.2.1 w/ OEM cable (Also tried a non-OEM cable)
What I have done so far with Wug's Toolkit:
- Step 1
1. Plugged in my device and made sure USB Debugging was enabled. (At this point, the Device Manager recognized a device and tried installing drivers, but failed.) So the first thumbnail is what I have in my device manager from the start. Nexus 7 under "Portable Devices" and "Other Devices."
2. I uninstalled both of the devices.
3. Unplugged my device and used USBDeview to uninstall anything that resembled "Google" or "ADB", etc. like it states.
4. Rebooted my computer.
- Step 2
1. It says that the recommended solution is #3, so naturally, I tried that one first. I followed the steps and installed the Android Composite ADB Interface drivers successfully and it even shows it under "Android Phone" in my device manager, second thumbnail, when my device is plugged in. (USB Debugging enabled)
2. Now, when I click on the "Reboot Bootloader" button on step 6 is where it just hangs with the dialog box "Rebooting your device into bootloader mode..." but my Nexus never reboots or anything. My Task Manager show two "adb.exe" processes and none ever end. I read the thread and some users were having the same problem and they got it to work by ending one of the adb.exe processes. So I have to end one of them and after a while I get a "Checking Fastboot status" then a few seconds later this message box pops up, third thumbnail. It says that Debugging is not necessary for bootloader mode, so I turn off USB Debugging and my computer recognizes a new device. So it successfully installs Android ADB Interface and I try the Reboot Bootloader button again, and it still hangs. Only this time, there is one adb.exe. So I kill it, and after a while I get the same error dialog box as the third thumbnail. Like it states, I am using driver configuration #3, so I will go ahead and close the dialog box and go to step 7.
3. Since my device is already configured, I go to Step 12.
4. I hit the "Reboot Device" button, but nothing happens to my device.
At this point, I decide to try a different driver solution. So I go through the whole process all over again, with Solution 1. Go through and install the drivers, everything goes according to the tutorial. I get to Step 3, and hit "Full Driver Test" and it hangs on "Checking ADB Status". There are two
adb.exe's so I end one of them. I get a dialog box that says ADB device not found.
Finally, I decide to try Solution 2. So I go through the whole process. Yet I still get the same hanging with adb.exe. I even tried different USB ports, but nothing.
Now, with mskip's Toolkit I never get past the "Starting ADB..." message. It just hangs there.
So the problem lies with ADB.exe I'm guessing. I'm tired and I've spent hours just trying to root this thing. Am I SOL? Anyone have anything that I can try out or the same problems?
Have you tried rebooting your PC after installing the drivers? It took me ages to get mine installed and I think a reboot allowed the device to show up and work properly. I thought it would be easy being a nexus device. Turned out to be a right pain in the ass.
Yep.
davidoff59 said:
Have you tried rebooting your PC after installing the drivers? It took me ages to get mine installed and I think a reboot allowed the device to show up and work properly. I thought it would be easy being a nexus device. Turned out to be a right pain in the ass.
Click to expand...
Click to collapse
Hey thanks for the response. Yes I have. I tried rebooting after every driver change. (Uninstalling, re-installing, etc.) My device does show up, almost as if the drivers are working correctly. Though I'm not sure why adb.exe is giving me troubles.
Have you tried 'adb devices' via cmd prompt? I take it your all stock then?
davidoff59 said:
Have you tried 'adb devices' via cmd prompt? I take it your all stock then?
Click to expand...
Click to collapse
No I haven't. Is this what you are talking about? http://forum.xda-developers.com/showthread.php?t=1741395
EDIT: I just tried "adb devices" via command prompt in the Advanced Settings, "Daemon not running, running it now, daemon started successfully." Now it'st just hanging. Two adb.exe processes.
What I was hoping to do was to create a backup of all my apps and data before I mess around with it. Yes, I'm all stock.
Add me on gchat and hit me up. Not sure what you are having problems but I could help you trouble shoot.
{{ WugFresh }}
WugFresh said:
Add me on gchat and hit me up. Not sure what you are having problems but I could help you trouble shoot.
{{ WugFresh }}
Click to expand...
Click to collapse
Thanks for the response, I have e-mailed you.
Tried to unlock the bootloader on the Nexus 4 today, downloaded the Android SDK, along with Google's USB drivers. Enabled USB debugging and popped into ADB, which has no issues with the phone. adb reboot bootloader boots into bootloader no problem. fastboot oem unlock, however, is greeted by the dreaded "Waiting for device" message. Device Manager shows "Android Bootloader Interface" with a little yellow triangle next to it, with error code 10: "This device cannot start".
I tried the universal drivers from this forum, I tried different USB ports on the computer, I even tried a different OS installation, so far nothing works. Any help would be appreciated. Thanks!
I found a tool kit worked for me
Zehlek said:
I found a tool kit worked for me
Click to expand...
Click to collapse
That's cool, do you have any links to the toolkit?
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