I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Try it on Windows 7 or update your drivers.
http://androidxda.com/download-htc-usb-drivers
http://www.andromods.com/fix-troubleshoot/issue-fastboot-waiting-for-device-windows-81-fixed.html
Fastboot and adb don't work on Windows 10 yet. That's why I didn't upgrade from Windows 7 ?
Related
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
Hello,
i was going to unlock my phone ( done with desire,desire hd and sensation too) but i got a problem with recognizing phone in fastboot
i tried in a pc with windows8 64bit ( installing manually drivers like procedure) and also on win7 32bit
Both system see my phone when in normal mode, using adb devices it shows the letter/numbers
but once i type adb reboot booloader it rebbot it and then nothing..
Phone recognize Fastboot USB and my pc recognize it as working, but adb devices list nothing
Any help?
i also installed htc sync manager
EDIT:
is because i'm a totally IDIOT ,yes
I was typing adb devices in fastboot INSTEAD of fastboot devices..
I'm an idiot right xD??
erto90 said:
is because i'm a totally IDIOT ,yes
I was typing adb devices in fastboot INSTEAD of fastboot devices..
I'm an idiot right xD??
Click to expand...
Click to collapse
No, this is not it at all.
Newb mistake is the preferred terminology. "Newb" because unlike a noob you at least figured out the issue on your own and then shared back with the community. This is never a bad thing
None the less, thread closed as requested.
Hi all,
I have recently updated to the one and am having some trouble getting the fastboot commands working. Having been rooting/unlocking my phones for a few years now and have never really found the need to sign up and ask question as you can generally find what you need to solve most problems on here.
I have updated the driver using tutorials from here using the windows 7 ones. I have done this and everything works fine, the device is recognised. I can use the adb command to get the device connected information and adb reboot into bootloader, however when I get into the bootloader and into fastboot usb a windows notification pops up saying 'USB not recognised , the usb device connected to this computer malfunctioned and windows does not recognise it.'. As expected when I try any fastboot command it says it is waiting on device and is stuck there.
Hopefully it is something stupid I am missing out and not the device.
Any help would be good.
Thanks.
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
nathlynn22 said:
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
Click to expand...
Click to collapse
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
[email protected] said:
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
Click to expand...
Click to collapse
I tried fast boot devices in fast boot USB by going into minisdk. Didn't try in recovery would have been good to try adb devices in recovery because I was stuck in that when first tried the custom recovery but a hard reset kicked it back out. Got recovery sorted just wanted to take nandroid backup off phone to PC and put root files which I'm still trying to get best 1's any idea where to get them where URL link is working? I've tried fastboot so doesn't work and basic trying to connect phone to PC for file transfer doesn't work either
stovie_steve said:
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
Click to expand...
Click to collapse
Ok so not only person. When I try connect mine doesn't even flag up I've connected a device USB debugging starts up on phone but have just noticed USB connection doesn't show. Plus I connect to PC and doesn't make the sound as I've it recognized my connecting anything. Fastboot USB comes up empty. I've been spending a couple hours here and there for past 2 nights trying to set phone up ready for rum runner. But my other question is if I'm already on htc_001 there's no need for me to change CID num anyways? Thanks
Try going to command prompt and typing in set devmgr_show_nonpresent_devices=1 followed by start devmgmt.msc
Click on view and show hidden devices. This will show devices which are not connected but have been installed. Look for something like android phone or android device and update the drivers by selecting update driver > let me select > have disk and then select the driver from here:
http://forum.xda-developers.com/showthread.php?t=2386956
Try that and see if it works
I'm all sorted now thanks just kept at it.
Sent from my HTC One using XDA Premium 4 mobile app
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
clsA said:
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
Click to expand...
Click to collapse
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
alray said:
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
Click to expand...
Click to collapse
Get no luck on that... The y510p cannot even boot from a USB /___\
But anyway, I have borrowed my fds computer with Win 7 installed. And all works fine now. Thank you very much~~
ac3kill said:
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
Click to expand...
Click to collapse
Your Phone is broken send it to HTC or take it to a repair shop