Related
I've tried almost everything to my knowledge. I'm trying to use the instructions on HTCdev.com and when i get to the last page where I type in "fastboot oem get_identifier_token all that returns is <waiting for device>. USB debugging is enabled, I'm in charge only mode, I've uninstalled HTC sync after installing the drivers. I have the SDK tools installed and in the correct location. What the hell else could it be? I'm at my wits end here and looking for any help I can get.
anghellic said:
I've tried almost everything to my knowledge. I'm trying to use the instructions on HTCdev.com and when i get to the last page where I type in "fastboot oem get_identifier_token all that returns is <waiting for device>. USB debugging is enabled, I'm in charge only mode, I've uninstalled HTC sync after installing the drivers. I have the SDK tools installed and in the correct location. What the hell else could it be? I'm at my wits end here and looking for any help I can get.
Click to expand...
Click to collapse
lol. wrong section. but anyways. you need to be in bootloader.. power down. take off battery and put it back. then hold power and volum down till you go to bootloader. then enter fastboot. plug your phone in and you should see. fastboot usb. and then start the unlock process again.
Marshmellow92 said:
lol. wrong section. but anyways. you need to be in bootloader.. power down. take off battery and put it back. then hold power and volum down till you go to bootloader. then enter fastboot. plug your phone in and you should see. fastboot usb. and then start the unlock process again.
Click to expand...
Click to collapse
I'm PMing you...
I apologize for posting in the wrong section, I didn't realize I had posted it here, but instead of saying "fastboot USB" when plugged into the computer, it says "fastboot AC" does that make any difference?
Did you manage to get this sorted? You should be in the bootloader (which is in the HTCDev.com instructions)...
anghellic said:
I apologize for posting in the wrong section, I didn't realize I had posted it here, but instead of saying "fastboot USB" when plugged into the computer, it says "fastboot AC" does that make any difference?
Click to expand...
Click to collapse
Your phone thinks its connected to a charger instead of a USB cable. Try changing cables or USB ports.
Sent from my De-Sensed HTC Vivid using XDA Premium App
I think its the pc I'm using...I tried every USB port, Ill have to wait til I can get another laptop since the one I'm using is my moms and it just sucks to put it plainly. -_-
Sent from my HTC PH39100 using xda premium
anghellic said:
I think its the pc I'm using...I tried every USB port, Ill have to wait til I can get another laptop since the one I'm using is my moms and it just sucks to put it plainly. -_-
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Are you using the micro usb cable that came with the phone? I had a longer cord that wouldn't work and only showed as ac charging, not usb charging.
Yeah I'm using the stock cable.
Sent from my HTC PH39100 using xda premium
Have you tried another USB port?
Sent from my HTC PH39100 using Tapatalk 2
Yes I tried all of them Idk ill try it again when I have access to another pc.
Sent from my HTC PH39100 using xda premium
anghellic said:
Yes I tried all of them Idk ill try it again when I have access to another pc.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Maybe your best option to try another pc
I finally got it working. I ended up trying a Kodak USB cable and it's the only one that would work correctly. Problem Solved!
anghellic said:
I finally got it working. I ended up trying a Kodak USB cable and it's the only one that would work correctly. Problem Solved!
Click to expand...
Click to collapse
Glad you have got it to work
I have been having some trouble trying to unlock the bootloader. When plugged into my laptops' usb, the phone charges but is never detected by the pc. Usb debugging is on and I have tried selecting each of the different default connection options to try and get a response. I have used different cables and different ports, still nothing. My main os is Ubuntu 13.04 but I have also tried on a mac as well to see if that was the problem. I have the correct java, sdk tools and sdk fastboot files.
Any ideas? Thanks in advance
update* Also, when plugged into the usb when at the fastboot menu, the display shows "Fastboot AC", not Fastboot usb
BigHuse said:
I have been having some trouble trying to unlock the bootloader. When plugged into my laptops' usb, the phone charges but is never detected by the pc. Usb debugging is on and I have tried selecting each of the different default connection options to try and get a response. I have used different cables and different ports, still nothing. My main os is Ubuntu 13.04 but I have also tried on a mac as well to see if that was the problem. I have the correct java, sdk tools and sdk fastboot files.
Any ideas? Thanks in advance
update* Also, when plugged into the usb when at the fastboot menu, the display shows "Fastboot AC", not Fastboot usb
Click to expand...
Click to collapse
Have you tried connecting your phone to an AMD Motherboard's Chipset/Processor Computer to see if it can be detected? Because mine does the same behaviour until I found out that it cannot be detected in any Intel based Computer.
Raz0r1911 said:
Have you tried connecting your phone to an AMD Motherboard's Chipset/Processor Computer to see if it can be detected? Because mine does the same behaviour until I found out that it cannot be detected in any Intel based Computer.
Click to expand...
Click to collapse
My laptop and my compiler machine is all based intel. No such issues. Install correct driver on the machine. Dont use usb 3.0 or usb hubs. Directly connected in the back side of the computer.
Sent from my Sensation XL using xda premium
anders3408 said:
My laptop and my compiler machine is all based intel. No such issues. Install correct driver on the machine. Dont use usb 3.0 or usb hubs. Directly connected in the back side of the computer.
Sent from my Sensation XL using xda premium
Click to expand...
Click to collapse
Can confirm that. All my laptops are Intel-based and working fine for me. Only problem some times seems to be some versions of Windows..
AlluXX said:
Can confirm that. All my laptops are Intel-based and working fine for me. Only problem some times seems to be some versions of Windows..
Click to expand...
Click to collapse
Windows 8 release is **** when talking fastboot and adb. Device drivers is an issue
Sent from my Sensation XL using xda premium
anders3408 said:
Windows 8 release is **** when talking fastboot and adb. Device drivers is an issue
Sent from my Sensation XL using xda premium
Click to expand...
Click to collapse
Yep. Tried it for a while and went back to 7.
Sent from my GT-N7105 using xda premium
BigHuse said:
I have been having some trouble trying to unlock the bootloader. When plugged into my laptops' usb, the phone charges but is never detected by the pc. Usb debugging is on and I have tried selecting each of the different default connection options to try and get a response. I have used different cables and different ports, still nothing. My main os is Ubuntu 13.04 but I have also tried on a mac as well to see if that was the problem. I have the correct java, sdk tools and sdk fastboot files.
Any ideas? Thanks in advance
update* Also, when plugged into the usb when at the fastboot menu, the display shows "Fastboot AC", not Fastboot usb
Click to expand...
Click to collapse
Have u tried using "anders3408"'s "Runnymede AIO tool", the new drivers ;ever since ics have been unusable for me and his tool was the only one that was able to install drivers for my SXL
Hey guys I unlocked my boot loader and rooted once then I un-rooted and re-locked the boot-loader and now I am trying to do it again but I am having a problem. When I have my phone connected in debugging mode it shows up fine, I can use the code "adb devices" and it shows up but then when I load into the boot loader and go into fastboot and connect my phone to my computer Windows 8 says that it can not recognize the device this is on USB 2.0 it also says "device failed enumeration". On USB 3.0 I get a message that says "The device cannot start code 10". I have un-installed and then re-installed the sync manager and mulitple drivers to no avail. Please help.
Help
Anyone?
I had this before. It's a glitch I think but after keep trying I finally got it to work and really I don't know how to fix it.
What's your hboot version? Battery full? Try a different computer? Have a linux live cd?
Sent from my HTC One using xda app-developers app
Tw1tchy said:
I had this before. It's a glitch I think but after keep trying I finally got it to work and really I don't know how to fix it.
What's your hboot version? Battery full? Try a different computer? Have a linux live cd?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yea I've tried two different computers I did have luck with one but I got as far as "fastboot flash unlocktoken Unlock_code.bin" and get an error that says that it cannot load the "Unlock_code.bin". My hboot version is 1.44. My battery has been full all day due to the fact that its been connected to a computer all day http://forum.xda-developers.com/images/smilies/tongue.gif
arenglish said:
Yea I've tried two different computers I did have luck with one but I got as far as "fastboot flash unlocktoken Unlock_code.bin" and get an error that says that it cannot load the "Unlock_code.bin". My hboot version is 1.44. My battery has been full all day due to the fact that its been connected to a computer all day http://forum.xda-developers.com/images/smilies/tongue.gif
Click to expand...
Click to collapse
Well lets kinda rule things out. It shouldn't be your computer hardware or fastboot files because you tried this on multiple computers. Now what drivers are you using on each computer? Did you tried other micro usb cords? What shape is your micro usb slot on your device (looking at mine right now its kinda dirty)?
Complete those and it should tell you if its a connection problem or not. Otherwise we can partially assume its the software on your phone.
Tw1tchy said:
Well lets kinda rule things out. It shouldn't be your computer hardware or fastboot files because you tried this on multiple computers. Now what drivers are you using on each computer? Did you tried other micro usb cords? What shape is your micro usb slot on your device (looking at mine right now its kinda dirty)?
Complete those and it should tell you if its a connection problem or not. Otherwise we can partially assume its the software on your phone.
Click to expand...
Click to collapse
I have been using drivers that didn't seem to work(some that I got off some thread here) but those didn't work so I uninstalled those and then uninstalled and then re-installed HTC Sync. I have used three different cables and my micro usb slot seems to be in fine condition it doesn't seem to be that dirty.
What happens when you try
fastboot erase cache
Does the command work or fail?
Sent from my HTC One using xda app-developers app
Tw1tchy said:
What happens when you try
fastboot erase cache
Does the command work or fail?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I would assume this would not work as the op states that his device is not recognised in fastboot.
bobsie41 said:
I would assume this would not work as the op states that his device is not recognised in fastboot.
Click to expand...
Click to collapse
Incorrect, OP has got as far as loading the unlock code but fails at fastboot.
Sent from my HTC One using xda app-developers app
Ok so with one laptop when I have my phone in debugging mode and are in the sense OS the phone is detected using the code "adb devices" but when I go to the bootloader and put the phone in fastboot mode it is unrecognized. On my other laptop it is recognized in fastboot using the code "fastboot devices". I have not used the clear cache yet I will try it later.
Sent from my HTC One using xda app-developers app
arenglish said:
Ok so with one laptop when I have my phone in debugging mode and are in the sense OS the phone is detected using the code "adb devices" but when I go to the bootloader and put the phone in fastboot mode it is unrecognized. On my other laptop it is recognized in fastboot using the code "fastboot devices". I have not used the clear cache yet I will try it later.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm in the exact same place as you on the first computer, as soon as I boot my phone into fastboot my computer no longer recognizes it and I've tried at least 5 different drivers and the HTC sync thing to help with the driver, what is wrong??
Sent from my HTC One using Xparent Cyan Tapatalk 2
Tw1tchy said:
What happens when you try
fastboot erase cache
Does the command work or fail?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
When I try that command all that happens is it says "waiting for device" and stays like that.
arenglish said:
When I try that command all that happens is it says "waiting for device" and stays like that.
Click to expand...
Click to collapse
Have you updated your firmware? If so, make sure your sdk is the latest version.
Use usb 2.0, usb 3.0 is known to cause problems.
Un-install htc sync but not the drivers.
Before attempting commands, eject htc sync drive from My PC.
Let me know how you get on.
bobsie41 said:
Have you updated your firmware? If so, make sure your sdk is the latest version.
Use usb 2.0, usb 3.0 is known to cause problems.
Un-install htc sync but not the drivers.
Before attempting commands, eject htc sync drive from My PC.
Let me know how you get on.
Click to expand...
Click to collapse
Ok, my firmware is 1.26.502.12 which I believe is the latest for AT&T, I've switched from USB 3.0 to 2.0 still not working in fastboot. I re-installed the SDK yesterday so I don't think there should be an update. I have un-installed HTC sync but not HTC Driver Installer and still after doing all of this the device shows up when it is in the OS but not in fastboot. Also when I reboot my device USB debugging keeps disabling itself.
Any updates to this? I'm running Windows 8, have the HTC drivers / Sync installed.. The phone connects fine while in Windows. But is unrecognized when the phone is in bootloader. This is driving me nuts. I do not have access to another PC. I'm sure someone has this working.
Edit: usb 3.0 ports working after following the plugable.com method for windows 8 usb 3 host controller fix.
born_fisherman said:
Any updates to this? I'm running Windows 8, have the HTC drivers / Sync installed.. The phone connects fine while in Windows. But is unrecognized when the phone is in bootloader. This is driving me nuts. I do not have access to another PC. I'm sure someone has this working.
Edit: usb 3.0 ports working after following the plugable.com method for windows 8 usb 3 host controller fix.
Click to expand...
Click to collapse
Thanks... tried that method worked like a charm.
Hi guys,
I have an HTC One with S-OFF and GPE ROM, I'm trying to get pretty much everything back to stock now. I've identified my CID and downloaded the appropriate RUU exe, the drivers are installed properly and the device is recognized when I run adb devices. However, when I try the RUU it gives me error 170, and on the last step it shows this which is pretty weird "abd dfksfsafjsdfkklsj". Any ideas? Thanks.
Edit: It seems to give that error even when I don't have the phone plugged in at all:
"1. Connect the Smartphone to the USB cable
abd dfksfsafjsdfkklsj"
enduu said:
Hi guys,
I have an HTC One with S-OFF and GPE ROM, I'm trying to get pretty much everything back to stock now. I've identified my CID and downloaded the appropriate RUU exe, the drivers are installed properly and the device is recognized when I run adb devices. However, when I try the RUU it gives me error 170, and on the last step it shows this which is pretty weird "abd dfksfsafjsdfkklsj". Any ideas? Thanks.
Edit: It seems to give that error even when I don't have the phone plugged in at all:
"1. Connect the Smartphone to the USB cable
abd dfksfsafjsdfkklsj"
Click to expand...
Click to collapse
Error 170 = usb connection error either because a bad cable, drivers installed incorrectly etc. etc... Try a different cable, re-install drivers correctly and use usb 2.0 ports only.
Ok so after digging through the error logs I found something really weird:
The reason it fails is that when the RUU runs adb devices from C:\Program Files\HTC\HTC Sync 3.0\ it outputs the device number + offline. I know this is true since I tested it in a prompt. However, when I run the command from a mini-sdk I have placed somewhere else, it recognizes the device properly ( device number + "device").
Does anyone have an idea what's going on? I've installed HTC Sync but I tried HTC Sync Manager as well earlier, same problem.
alray said:
Error 170 = usb connection error either because a bad cable, drivers installed incorrectly etc. etc... Try a different cable, re-install drivers correctly and use usb 2.0 ports only.
Click to expand...
Click to collapse
This is the second cable I'm trying, different port, I have no idea how many times I've reinstalled the drivers today lol. I'm using the latest HTC Sync & Driver version
enduu said:
This is the second cable I'm trying, different port, I have no idea how many times I've reinstalled the drivers today lol. I'm using the latest HTC Sync & Driver version
Click to expand...
Click to collapse
Try another computer, another ruu. Make sure the usb cables you are using are not only charging cables. Maybe a defective usb port on the phone.
error 170 is usb connection error, so troubleshoot everything related to this:
usb ports
usb cables
usb drivers
phones drivers
RUU
computer
phone usb port
alray said:
Try another computer, another ruu. Make sure the usb cables you are using are not only charging cables. Maybe a defective usb port on the phone.
Click to expand...
Click to collapse
Well this is the only computer I have access to for the next couple of days, and the only ruu I could find. I am not sure what you mean with the cables though.
Here's the thing, if I replace the adb file from htc sync ( 159kb ) with the one from the mini-sdk ( 800kb) it recognizes the device, and I'm thinking it will probably run the RUU as well. Do I risk messing up something if I do this? This is in regards to http://forum.xda-developers.com/showpost.php?p=54529900&postcount=3 . Thanks.
enduu said:
Well this is the only computer I have access to for the next couple of days, and the only ruu I could find. I am not sure what you mean with the cables though.
Click to expand...
Click to collapse
Some usb cable only have +5v and ground to provide power and charge devices. Data usb cable have 4 connections: +5V, Ground, Data +, Data -.
Here's the thing, if I replace the adb file from htc sync ( 159kb ) with the one from the mini-sdk ( 800kb) it recognizes the device, and I'm thinking it will probably run the RUU as well. Do I risk messing up something if I do this? This is in regards to http://forum.xda-developers.com/showpost.php?p=54529900&postcount=3 . Thanks.
Click to expand...
Click to collapse
Never keep htc sync installed when you flash things on your phone, only install it for the drivers, then uninstall the program (drivers will not be removed). HTC sync might be the problem here.
alray said:
Some usb cable only have +5v and ground to provide power and charge devices. Data usb cable have 4 connections: +5V, Ground, Data +, Data -.
Never keep htc sync installed when you flash things on your phone, only install it for the drivers, then uninstall the program (drivers will not be removed). HTC sync might be the problem here.
Click to expand...
Click to collapse
Well I did remove htc sync but after checking the logs I noticed the problem was still the same. For some reason, every time the device failed to be recognized with the adb devices command, what fixed it for me was putting the it in fastboot, weird.
enduu said:
Well I did remove htc sync but after checking the logs I noticed the problem was still the same. For some reason, every time the device failed to be recognized with the adb devices command, what fixed it for me was putting the it in fastboot, weird.
Click to expand...
Click to collapse
device offline when booted into a rom error is either drivers, out of date adb / fastboot, but normally it will tell you if its out of date or finally you don't have usb debugging enabled properly, this also applies to the 170 error, easy way to test if its the usb cable or ports etc is to try fastboot getvar all, if you get a result, then its not cables or ports.
adb commands don't work in the bootloader, only fastboot commands.
Hello.I am in some kind of a trouble..I just bought a phone with firmware problems,hoping i could make it work.The problem is this,someone tried to update the firmware,unsuccesfully,and now it's stuck with no OS.I can only start recovery and bootloader.
Recovery is Teamwin 2.6.3.3.Already tried to clear cache and everything,to use an USB with OTG,but it's not recognised,ADB sideload also it's not working.
adb devices shows the phone is not connected,and FastBoot says "Waiting for device".Any idea? I've tried,read a lot,but I can't really work it out..
Also,I can't find the device in Device Manager,neither in ADB nor Fastboot.
I tried using Windows 8.1 and 7..Same deal.
Thank you!
chris_b0ss said:
Hello.I am in some kind of a trouble..I just bought a phone with firmware problems,hoping i could make it work.The problem is this,someone tried to update the firmware,unsuccesfully,and now it's stuck with no OS.I can only start recovery and bootloader.
Recovery is Teamwin 2.6.3.3.Already tried to clear cache and everything,to use an USB with OTG,but it's not recognised,ADB sideload also it's not working.
adb devices shows the phone is not connected,and FastBoot says "Waiting for device".Any idea? I've tried,read a lot,but I can't really work it out..
I tried using Windows 8.1 and 7..Same deal.
Thank you!
Click to expand...
Click to collapse
Is it a M8 or a M7, because your title says M8 but you have posted in the M7 forum.
Sorry,I am quite scared.It's M7.
chris_b0ss said:
Sorry,I am quite scared.It's M7.
Click to expand...
Click to collapse
First, follow instructions given in this post to install the latest android sdk-tools and the latest htc drivers. Also make sure you don't have HTC Sync installed on your computer.
Then connect your phone to you computer with the original cable (or any other cable already known to work for data transfer - some usb cable are only providing power), reboot the phone in bootloader mode by holding vol down and power. Make sure you see the red "fastboot usb" caption on the screen, if not use vol up/down and power to select the "fastboot" menu. Once there open a command window form the android sdk-tools folder and type "fastboot getvar all". Copy/paste the ouput of this command here (except the imei and serialno).
I've followed that,and still not working.pics attached.
It's very weird,because I was expecting for a soundfrom the Windows,like a new device connected .But ..nothing
Sent from my GT-I9100 using XDA Free mobile app
chris_b0ss said:
I've followed that,and still not working.pics attached.
It's very weird,because I was expecting for a soundfrom the Windows,like a new device connected .But ..nothing
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
With your phone in bootloader/fastboot mode, go to your windows device manager, take a screenshot of your device manager and post it here please.
The unknown device is related to my laptop.Nothing happens when I connect the phone.
chris_b0ss said:
The unknown device is related to my laptop.Nothing happens when I connect the phone.
Click to expand...
Click to collapse
Ok so its not detected at all
Might be caused by
a bad usb cable --> Try another one that you are 100% sure its working
a bad usb port on the computer (use only usb 2.0 ports btw)
a problem with the computer ---> Try another computer.
a bad usb port on the phone ---> need to replace the usb/front mic board
Might also worth to fix your laptop drivers problem. Might be causing problem if the "unknown" device is an adapter or usb controller...
Then reboot the computer.
I think we can exclude the first two,because I've tried 2 different USB cables,and with my S2 ,both of them are working,even ADB.I will try to replace the usb port from the phone,and then try again.But,do you think it will work ?
Thank you!
chris_b0ss said:
I think we can exclude the first two,because I've tried 2 different USB cables,and with my S2 ,both of them are working,even ADB.I will try to replace the usb port from the phone,and then try again.But,do you think it will work ?
Thank you!
Click to expand...
Click to collapse
Its hard to tell, there isn't any background info about what was done on that phone. The usb board is pretty cheap so it worth a try if you are 100% sure everything else is fine (computer, cables etc..)
I understand,but,I mean,as far as I know,it's not hard brick,because the phone is still booting..in some way ..so if I manage to connect it,I can flash the rom..am I right?
Sent from my GT-I9100 using XDA Free mobile app
chris_b0ss said:
I understand,but,I mean,as far as I know,it's not hard brick,because the phone is still booting..in some way ..so if I manage to connect it,I can flash the rom..am I right?
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Normally it should be pretty easy to fix if you can get fastboot and adb connectivity. You could then update the firmware so you can flash the correct RUU to restore the phone back to stock, already made the research and all the files (firmware and ruu) you'll need are available.
alray said:
Normally it should be pretty easy to fix if you can get fastboot and adb connectivity. You could then update the firmware so you can flash the correct RUU to restore the phone back to stock, already made the research and all the files (firmware and ruu) you'll need are available.
Click to expand...
Click to collapse
Sorry for the late reply,the phone is now in service,in 1-2 days they should fix the USB board,and I will get back with more info soon.
Thank you very much for your quick answers and for taking time to help me!
Good news,I've managed to unbrick it.I asked a friend with a Mac to check it out,and his Mac recognized with no problems.Installed the Os,but still,Windows can't detect it.I've tried on 2 pc's(7 and 10) with the proper drivers.Weird..
Anyway,thank you for your time @alray !