fastboot not working in RUU mode - One (M7) Q&A, Help & Troubleshooting

Hi guys,
I'm having a really strange issue. I wanted to update my M7 to firmware 7.15.401.1
So before rebooting into RUU mode, I always check my getvar all to ensure that everything is working. However, today, when I got into RUU mode, fastboot wasn't working. It was working in bootloader mode, but not in RUU. I got the 'Windows didn't recognize the connected device' or something like that. And, when I typed 'fastboot reboot' it was 'waiting for devices'.
My PC is on Windows 8.1 with the latest Sync Manager, my M7 is S-OFF, unlocked bootloader and TWRP 2.8.4.0. There's no issue with the working of the phone; its rocking MaximusHD perfectly. But this issue prevents me from updating my firmware or going back to stock if I need to.
Any help is greatly appreciated.

raghav kapur said:
Hi guys,
I'm having a really strange issue. I wanted to update my M7 to firmware 7.15.401.1
So before rebooting into RUU mode, I always check my getvar all to ensure that everything is working. However, today, when I got into RUU mode, fastboot wasn't working. It was working in bootloader mode, but not in RUU. I got the 'Windows didn't recognize the connected device' or something like that. And, when I typed 'fastboot reboot' it was 'waiting for devices'.
My PC is on Windows 8.1 with the latest Sync Manager, my M7 is S-OFF, unlocked bootloader and TWRP 2.8.4.0. There's no issue with the working of the phone; its rocking MaximusHD perfectly. But this issue prevents me from updating my firmware or going back to stock if I need to.
Any help is greatly appreciated.
Click to expand...
Click to collapse
The issue is the driver, I had the same problem recently, when you plug your phone into the computer and put your phone into ruu mode or recovery, have a look in Windows device manager, it will probably say "one" with a yellow exclamation mark next to it, you need to force the driver, so right click on it, select update driver, the when given 2 options, choose Browse my computer for driver, next select android devices from the list it gives you, and then choose your latest myhtc driver, should be at the top of the list of available drivers, it will give you a warning about the driver might be wrong are you sure you want to install it, just say yes, done, problem solved.

Seanie280672 said:
The issue is the driver, I had the same problem recently, when you plug your phone into the computer and put your phone into ruu mode or recovery, have a look in Windows device manager, it will probably say "one" with a yellow exclamation mark next to it, you need to force the driver, so right click on it, select update driver, the when given 2 options, choose let me pick the driver myself, next select android devices from the list it gives you, and then choose your latest myhtc driver, should be at the top of the list of available drivers, it will give you a warning about the driver might be wrong are you sure you want to install it, just say yes, done, problem solved.
Click to expand...
Click to collapse
Alright. Ill try it later. Thanks a lot mate

Related

Fastboot Troubles

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.

[Q] HTC One fastboot devices returns blank

Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
zWiLLX said:
Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
Click to expand...
Click to collapse
i would say you havent installed the drivers. best thing to download to get your HTC one to recognize in any mode is the HTC sync manager. i know its kinda annoying but the phone will get recongized in every mode and the initial plug in just requires a few minutes to detect, download, and install the drivers.
syaoran68 said:
i would say you havent installed the drivers.
Click to expand...
Click to collapse
I did try the "stripped" HTC One drivers found here on XDA.. I mean http://forum.xda-developers.com/showthread.php?t=2217396 seems pretty straightforward!
But yes at this point in the game why not give the full bloatware a try, thx
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Is your phone actually in fastboot mode?
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
BenPope said:
Is your phone actually in fastboot mode?
Click to expand...
Click to collapse
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
skinsfanbdh said:
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Click to expand...
Click to collapse
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
zWiLLX said:
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
Click to expand...
Click to collapse
there is a thread around for people who are having issues with windows 8. the soulution for you problem is probably in that thread
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
zWiLLX said:
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
Click to expand...
Click to collapse
to use fastboot commands it needs to say fastboot usb
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
zWiLLX said:
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
Click to expand...
Click to collapse
when it says waiting for device you have to close that cmd screen and if your phone says fastboot usb it will start but you have to manually close the first window
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
zWiLLX said:
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
Click to expand...
Click to collapse
when your phone is in bootloader does it say fastboot usb at the top?
i think the links for drivers are for samsung devices he said its copied from his other thread. you need to get drivers from somewhere else
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
zWiLLX said:
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
Click to expand...
Click to collapse
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
try pressing the power button while in bootloader. does it switch between hboot and fastboot usb?
MacHackz said:
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
Click to expand...
Click to collapse
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
yea it has to be plugged it to the computer first
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
Hey, I replied to your email PM me your TeamViewer info
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey guys, Im experiencing similar problems. How exactly did you guys solve it?
Thanks
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey, I´m experiencing the same problem here. Could you help me too?
Kenchinito said:
Hey, I´m experiencing the same problem here. Could you help me too?
Click to expand...
Click to collapse
Sorry for the very slow reply. Unfortunately, we won't know why HTC didn't play nicely with my Lenovo/Win8 laptop. However, I was quick to try a different older netbook I had lying around. At first, nothing happened, and I got used to the Sense UI enough to tolerate it.
But, I couldn't wifi tether and a few other unacceptable details, so I tried again last week with the same netbook that didn't seem to work the first time, and voila! Flawless. Maybe a reboot of that kicked it into gear, but both ADB and Fastboot were recognizing the HTC as a specific device, as opposed to the lenovo which found a ghost device with no name.
I am guessing too many android devices were installed and in the registry as USB devices, disorienting the PC, even though they were uninstalled, perhaps their drivers lingered as shared drivers. In theory I had S3 S4, HTC, possibly S2 and Motorola drivers all present.
The key is, keep the drivers on a folder on your phone with adb fastboot etc, and try a couple diff laptops. You'll know it worked when the device is recognized via "devices" with its unique number in both adb and fastboot.
Now running Revolution HD Google Play after trying CM 10.2 and Revolution HD Sense. CM did not work very smoothly with a lot of force crashes (navigation and music) and I can strongly recommend RevolutionHD google play edition.
Beware though, the first wipe takes out all the contacts and pictures etc, unfortunately, because I thought they would be spared.

Phone won't connect to HTC Sync or adb

Got my phone about a week ago & got pretty bored of it so I wanted to root it and get a different ROM going. For some reason, I can't get the phone to connect to HTC Sync Manager though I updated the drivers. Any time the phone is switched into USB debugging, My HTC drivers fail to install. I have no idea how to solve this problem. Also when trying to get the Token ID using the command prompt, the device doesn't show up after using the command adb devices either. Need help please.
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
bigdaddy619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
HurtMeSole said:
If the phone doesn't have USB debugging enabled, it doesn't appear in the device manager besides under portable devices. Once USB debugging is turned on, Android devices tab appears at the top but the drop down reads My HTC with the yellow triangle with ! on the inside indicating there's some sort of issue. I tried updating the drivers, uninstalling the drivers, restarting the phone and computer, then reinstalling the drivers but nothing has worked thus far. HTC Sync still isn't detecting the phone at all and I can't get the Token ID to continue the rooting process until the device is able to be detected.
Click to expand...
Click to collapse
Windows 8.1?
bigdaddy619 said:
Windows 8.1?
Click to expand...
Click to collapse
No, Windows 7, 64-bit.
HurtMeSole said:
No, Windows 7, 64-bit.
Click to expand...
Click to collapse
Check PM
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
HurtMeSole said:
I'm still having the same issue. I gave up for the time being but hopefully someone else had the same issue & can help us out.
Click to expand...
Click to collapse
Same problem here with an HTC One Mini. Its driving me mad!:silly:
trinity343 said:
i'm having this same issue. i just had to reload my phone back to stock bc it crashed. i'm trying to get it to be set to s-off but i can't get rumrunner to see my phone with adb connection. also on the device manager it shows the android phone under other devices with a ! on it.
i'm also using win7Pro x64 not sure what else to do on it at this point to get it working correctly
HTC Sync also doesn't see it. i got it see it for a few minutes last night but the it stopped again
Click to expand...
Click to collapse
Strangely enough, I literally just tried it on a different computer and everything worked exactly as it was supposed to. I had 3 computers in my home, none of which worked but got to work and the laptop they gave me worked just fine. Then I got on my gf's Mac and it went mostly smooth (even though it was difficult not being as familiar with the OS). My advice is do everything you're doing on a different computer until you see it without the ! in the device manager.
Boblud said:
Same problem here with an HTC One Mini. Its driving me mad!:silly:
Click to expand...
Click to collapse
Should try using a different computer. Worked for me after trying several computers.
BD619 said:
In bootloader you should type fastboot devices not adb devices.
You can try this to get the drivers installed correctly
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Also try these drivers http://d-h.st/FXC
Click to expand...
Click to collapse
My experience may be helpful. I had no ADB driver, but Composite USB seemed to work. However, the driver install crashed. I needed to open my phone and answer the dialogs on my phone while the driver was installing. After that, everything is hunky-dorry (I know, showing my age).
I was having the same problem until I UNCHECKED the USB debugging mode and reconnected the phone to the computer. Drivers reinstalled and HTC Sync Manager (not HTC Sync--different program) recognized the phone. I had to answer dialogue on phone and then the USB debugging mode status changed itself to enabled. It's all working now, after hours of fiddling.

[Q] Need some help! Currently in a very bad situation.

Okay, I'm not sure exactly what happened, but long story short:
I flashed a rom and instead of getting a new rom on my phone, the phone rebooted into fastboot. I tried to enter recovery... no dice. Somhow my recovery uninstalled itself. So now I'm stuck with a phone with no rom installed, and no recovery installed. Frustration.
First step would be to reinstall recovery right? But when attempting to use fastboot flash command, i get stuck at <waiting for device>. I have the htc phone driver installed, and it's recognizing the phone is plugged into the pc in device manager. The phone screen even says FASTBOOT USB. I have no idea why it's not flashing. The recovery i'm trying to flash is twrp, the latest sprint build. It's the same one I had before it somehow uninstalled itself.
Please help out guys?
Thanks.
What phone?
Sent from my SM-P600 using Tapatalk
Details
Sorry for not making this clear earlier: the phone is the HTC One, Sprint. Just the regular one.
I'm really in a bind in here. Right now I have no recovery or rom to work with, and the only rom on my phone is the one that caused all this mess. I'm going to have to sideload a rom, but right now I need to get twrp on there. For some reason, it still won't get on, i'm still stuck at <waiting for device>. The phone is coming up on device manager as "My htc", so it's definitely plugged into the computer correctly. I have no idea what's going on.
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
tdhite said:
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
Click to expand...
Click to collapse
The command doesn't return anything. I guess this means my drivers aren't working. This doesn't make any sense though (pun intended): the phone is being recognized in device manager under "Android USB Devices" as "My HTC" via HTC's drivers that come with htc sync. I already downloaded htc sync and uninstalled it, keeping the driver files. This is really wierd stuff, any idea on how to get the drivers working? I'm sure if I could just get a recovery on there, resolving the issue wouldn't be too difficult via adb. Thanks.
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
BD619 said:
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
Click to expand...
Click to collapse
I am running 8.1, but my hboot is 1.55.
There it's a specific question in this in the faq page, particularly 8.1 and usb. Did you look at that?
See this: http://forum.xda-developers.com/showthread.php?p=49038239
EXDetonator said:
I am running 8.1, but my hboot is 1.55.
Click to expand...
Click to collapse
Did you install HTC sync? You need it for the proper drivers
Fixed! ...halfway
Alright guys, I flashed a recovery.
I actually started off with HTC's drivers, but they were causing the issue.
Thankfully the information the thread tdhite posted had a link to a working driver.
Thanks everyone! Now I need to sideload a rom.

Fastboot "waiting for device"

I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app
Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.
This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?
MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.
Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?
okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?

Categories

Resources