Related
Took my Nexus One off my cradle today to see it was locked up. Thought no biggie, I'll pull battery and restart it.
Now when it boots it comes up with four bars. Red, Green, Blue, White and the 3 skateboarding Droid Bots. I have no clue what to do now.
I was running Cyanogenmod (Forget the version, but it was 2-3 months old. I have not done anything to my phone except add the ebay app to it yesterday.
I can not get my computer to recognize it as a Nexus One anymore so I can not use Fastboot. I tried recovery from HBOOT, but keep coming up the same way.
Please Help
Ray
Picture of my Nexus One from Wifes iPhone...
I can get to FASTBOOT and when connected to USB it says FASTBOOT USB, but my computer fails to recognize the device and it goes back to FASTBOOT.
I can not turn on USB Debuging because it will not boot normal. I do not know what to do.
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Yes its the only thing I see.
I do not see anything Prior.
I have tried to boot to recovery many many times. I have 3 different results.
1. Nexus X with nothing else
2. Nexus X with Unlocked icon below
3. The screen you see
Either way, it does not move forward it just hangs. Is there a way to turn on USB debugging from FASTBOOT or HBOOT?
Ray
Russ T. Nail said:
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Click to expand...
Click to collapse
looks like the bootloader screen, thats what the rainbow screen was on the g1.
havent seen it on the nexus though so it could be something else.
Did you try a factory reset using hardware keys?
I believe you do this by holding vol-down, power and trackball for 5 secs.
That does not seem to do anything but take me to FASTBOOT
There has to be a way to turn on USB Debugging from FASTBOOT?
If you can get fastboot usb to work you could try the following (using latest amon_ra recovery.img):
Code:
fastboot boot c:\path\to\recovery.img
To boot into recovery, then use adb or try nand-ing etc.
if you get that far (recovery)
Code:
adb shell reboot normal
should take you into os.
However, the colored bars look like some pretty serious hardware failure I'd guess...
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
check this out to help you get fastboot to work http://forum.xda-developers.com/showthread.php?t=613217
i know its titled ADB but it might help you out.
TheQue said:
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
Click to expand...
Click to collapse
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
have you tried to contact htc or even google?theyve helped me over the phone even knowing i have an unlocked bootloader.
pvillasuso said:
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
Click to expand...
Click to collapse
not the sd card if it was a bad card it would just bootloop
if you have SDK you can see what the phone is doing with ddms
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
That pic reminds me of the MDA Win Mobile 5 boot screen, real similar...
Don't know how to help, keep us updated if you figure this one out.
gtrplr71 said:
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
Click to expand...
Click to collapse
I 2nd that. Try using ddms or logcat.
Good luck man!
What happens when you try to flash a rom?
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.
I was trying to restore back to stock and followed the directions completely. After over and hour plus the onscreen message kept saying it was sending the ROM files to the phone its pretty clear it wasn't. So now I am stuck in the Bootloader with no ROM image at all. My Win8 computer suddenly won't recognize the device, I have removed and re-installed the drivers that worked before and get nothing.
I am on my wife's Win7 computer and I still cannot get the device to be recognized with the current drivers installed. The only thing I can do is power down my HTC One and reboot in the Bootloader - Fastboot.
I could use any help urgently.
RaptorMD said:
I was trying to restore back to stock and followed the directions completely. After over and hour plus the onscreen message kept saying it was sending the ROM files to the phone its pretty clear it wasn't. So now I am stuck in the Bootloader with no ROM image at all. My Win8 computer suddenly won't recognize the device, I have removed and re-installed the drivers that worked before and get nothing.
I am on my wife's Win7 computer and I still cannot get the device to be recognized with the current drivers installed. The only thing I can do is power down my HTC One and reboot in the Bootloader - Fastboot.
I could use any help urgently.
Click to expand...
Click to collapse
Have you tried flashing a recovery in fastboot?
The command is fastboot flash recovery nameofrecovery.img
Flash a custom recovery and then install a custom rom through it.That should make your phone usable for the moment. When you have time again you can try going back to stock.
I have heard these things recommend by others:
- Be sure you have the latest drivers. Download HTC Sync if need be, and sure to reboot your PC, then allow enough time for the phone to be recognized.
- Try a different USB port.
- Power down phone by simulating a battery pull by holding down the power button for up to fifteen seconds, then reboot into recovery by pressing the volume down key as the phone restarts.
Good luck!
Sent from my HTC One using Tapatalk 2
BillTheCat said:
I have heard these things recommend by others:
- Be sure you have the latest drivers. Download HTC Sync if need be, and sure to reboot your PC, then allow enough time for the phone to be recognized.
- Try a different USB port.
- Power down phone by simulating a battery pull by holding down the power button for up to fifteen seconds, then reboot into recovery by pressing the volume down key as the phone restarts.
Good luck!
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I tried the power down as you mentioned it just reboots everytime, I also tried the rebooting into recovery - Fastboot. I also tried all 4 USB Ports on my laptop.
Any other thoughts on this?
I tried the HTC Sync installer still get the same thing USB Device Not Recognized.
My device wasn't able to work with USB 2.0 port, is there only USB 2.0 on your laptop?
Sent from my HTC One™
I have USB 3.0 but no joy on any of my ports. On the phone with HTC Support they are USELESS. The only thing they can offer is to reload the OS by replacing the motherboard and that takes 2 weeks and $200. There has to be a better way.
http://androidforums.com/incredible-tips-tricks/161463-ruu-error-170-171-solution-windows-7-a.html
Don't know if this is any help to you
a box of kittens said:
http://androidforums.com/incredible-tips-tricks/161463-ruu-error-170-171-solution-windows-7-a.html
Don't know if this is any help to you
Click to expand...
Click to collapse
I am off to bed its nearly 1:30am and I need to go to work in 5 hours so I need some sleep. Any other suggestions, voodoo help or chants are welcome
hassan89 said:
Have you tried flashing a recovery in fastboot?
The command is fastboot flash recovery nameofrecovery.img
Flash a custom recovery and then install a custom rom through it.That should make your phone usable for the moment. When you have time again you can try going back to stock.
Click to expand...
Click to collapse
At the moment I cannot get my phone to show up on my computer, without that I cannot even push a recovery image like TWRP. If only I could.
Original poster: born_fisherman
My laptop only has USB 3.0 ports. I could get HTC sync to
work fine, but the PC wouldn't recognize the phone when in the bootloader. I was struggling to find an answer until I came across this blog and this worked flawlessly. The problem is with the Microsoft USB 3 host controller. This method replaces 2 Microsoft drivers with Intel drivers.
http://plugable.com/2012/12/01/windo...st-controllers
Follow this to a T. It does require rebooting the PC to disable driver signing, so make sure you bookmark the link to go back to it after you rebooted. If this helps you, just press the thanks button!
Rocker19943 said:
Original poster: born_fisherman
My laptop only has USB 3.0 ports. I could get HTC sync to
work fine, but the PC wouldn't recognize the phone when in the bootloader. I was struggling to find an answer until I came across this blog and this worked flawlessly. The problem is with the Microsoft USB 3 host controller. This method replaces 2 Microsoft drivers with Intel drivers.
http://plugable.com/2012/12/01/windo...st-controllers
Follow this to a T. It does require rebooting the PC to disable driver signing, so make sure you bookmark the link to go back to it after you rebooted. If this helps you, just press the thanks button!
Click to expand...
Click to collapse
Thank you. The link isn't working, could you send it to me via PM.
Thanks.
Rocker19943 said:
Original poster: born_fisherman
My laptop only has USB 3.0 ports. I could get HTC sync to
work fine, but the PC wouldn't recognize the phone when in the bootloader. I was struggling to find an answer until I came across this blog and this worked flawlessly. The problem is with the Microsoft USB 3 host controller. This method replaces 2 Microsoft drivers with Intel drivers.
http://plugable.com/2012/12/01/windo...st-controllers
Follow this to a T. It does require rebooting the PC to disable driver signing, so make sure you bookmark the link to go back to it after you rebooted. If this helps you, just press the thanks button!
Click to expand...
Click to collapse
Was this the link you were suggesting? http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers I found it doing some google searches.
Yes, it is
Sent from my HTC One™
If you can get into bootloader all is not lost. We'll figure something out. Have you tried a different cable?
makbil said:
If you can get into bootloader all is not lost. We'll figure something out. Have you tried a different cable?
Click to expand...
Click to collapse
I truly want to say THANK YOU, to everyone here at XDA-Developers. It is truly one of best communities for help, advice and resources and no one is ever left behind.
I was able to use my Win7 desktop at work, (very open workplace) and use the drivers that come with the All In One Root Kit and was able to get Fastboot USB and get my ROM back on my phone. I am now completely back to stock, wow that was scary stuff.
Above all else I learned a HUGE lesson, ask questions, wait for responses and ask more questions if you don't understand because someone will help you. Just as I was helped and saved last night and today by everyone here I too will pay it forward in anyway I can.
Thank you all for your help. HTC is NOT getting my $200 for a new motherboard. I mean their Tech Support at 12:20am is not that great but at least someone was there.
Thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you
Rocker19943 said:
Yes, it is
Sent from my HTC One™
Click to expand...
Click to collapse
Thanks again. I got the drivers d/l this morning along with the two small files I needed to copy and replace into the drivers folder (took me a few minutes to figure out where they wanted me to paste them). So tonight I will get home and I will move forward with removing the MS drivers grrrr.
Hello,
A long time stalker of these forums, but first time poster so apologies if this is in the wrong place.
I'm quite experienced with rooting and installing custom roms, my M7 is currently running CM and I've got the scars from bricking devices over the years! However this current problem has got me stumped and I wonder if anyone here has seen something similar.
I'm running the latest skinny Android fastboot / adb files. If I boot my phone into recovery > fastboot while connected to my pc everything is wonderful, fastboot devices can see the phone. However if I reboot the phone to desktop, fastboot on my PC doesn't do anything. I've tried different HTC drivers, USB cables and ports etc.
The strange thing is it was fine a few months ago!
Any thoughts?
Thanks,
Ben
B3ndy said:
Hello,
A long time stalker of these forums, but first time poster so apologies if this is in the wrong place.
I'm quite experienced with rooting and installing custom roms, my M7 is currently running CM and I've got the scars from bricking devices over the years! However this current problem has got me stumped and I wonder if anyone here has seen something similar.
I'm running the latest skinny Android fastboot / adb files. If I boot my phone into recovery > fastboot while connected to my pc everything is wonderful, fastboot devices can see the phone. However if I reboot the phone to desktop, fastboot on my PC doesn't do anything. I've tried different HTC drivers, USB cables and ports etc.
The strange thing is it was fine a few months ago!
Any thoughts?
Thanks,
Ben
Click to expand...
Click to collapse
You have enabled USB debugging on your Phone?
Justin2003 said:
You have enabled USB debugging on your Phone?
Click to expand...
Click to collapse
Hey Justin, thanks for the reply.
Yes, USB debugging is enabled.
B3ndy said:
Hey Justin, thanks for the reply.
Yes, USB debugging is enabled.
Click to expand...
Click to collapse
I should also add when the device is plugged into the PC, Windows recognises it ok.
B3ndy said:
I should also add when the device is plugged into the PC, Windows recognises it ok.
Click to expand...
Click to collapse
bootloader: you can use fastboot commands (no adb)
custom recovery: you can use adb commands (no fastboot)
booted up ROM + USB debugging: you can use adb commands (no fastboot)
Just a quick update, solved!
It was actually something up with the HTC drivers, I'd noticed that HTC Sync had updated (never use that thing anyway). Quickly nuked all mention from the machine, reinstalled drivers via the brilliant HTC One Toolbox and everything is good again.
Interestingly I also had some problems getting S-Off on this device but Firewater seems to have solved it as well.
Thanks for the replies!
Ben
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?
I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse
Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!