This is my first post so if I seem a little noobish I apologize.
I have a DNA that I need to revert back to stock to make an insurance claim on it. I have tried everything but I can't get the RUU to bring me back to stock. I have tried installing and uninstalling drivers, I have used ADB and fastboot to try and flash stock recoveries and boots to see if that would help me flash but no matter what I do I always see the same error:
Error 170: USB CONNECTION ERROR
I have looked online for threads on how to get around it but none of them have worked so far. I am running windows 8 64bit. I don't really know what to do as I need to have my phone sent out as soon as possible. Below is what my bootloader reads:
*** TAMPERED ***
*** RELOCKED ***
MONARUDO PVT SHIP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSPv4.120.240.0920
eMMC-boot
Jan 15 2013,19:37:51:-1
Thank you for the help in advance!
Zerios1`6 said:
This is my first post so if I seem a little noobish I apologize.
I have a DNA that I need to revert back to stock to make an insurance claim on it. I have tried everything but I can't get the RUU to bring me back to stock. I have tried installing and uninstalling drivers, I have used ADB and fastboot to try and flash stock recoveries and boots to see if that would help me flash but no matter what I do I always see the same error:
Error 170: USB CONNECTION ERROR
I have looked online for threads on how to get around it but none of them have worked so far. I am running windows 8 64bit. I don't really know what to do as I need to have my phone sent out as soon as possible. Below is what my bootloader reads:
*** TAMPERED ***
*** RELOCKED ***
MONARUDO PVT SHIP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSPv4.120.240.0920
eMMC-boot
Jan 15 2013,19:37:51:-1
Thank you for the help in advance!
Click to expand...
Click to collapse
I know this might sound strange but it might be a win8 issue... open CMD and while your phone is plugged in and USB Debugging enabled do an adb devices and see if it can detect the phone
dont do this till you get unrooted and stock rom after you get back to a stock rom get your hboot screen to look 100% stock take a look at this thread (the Number 2 section): http://forum.xda-developers.com/showthread.php?t=2160677
That is what makes it very strange. Both ADB and fastboot will recognize the phone just the ruu will not. I can issue commands in both adb and fastboot and the phone responds. Also for the ruu I should be in fastboot usb mode right? I have also disabled digitally signed drivers in windows 8.
Zerios1`6 said:
That is what makes it very strange. Both ADB and fastboot will recognize the phone just the ruu will not. I can issue commands in both adb and fastboot and the phone responds. Also for the ruu I should be in fastboot usb mode right? I have also disabled digitally signed drivers in windows 8.
Click to expand...
Click to collapse
The RUU is run from the desktop. If the phone is connected and gives a return when looking for devices doubleclick on the RUU and let it run.
It may require additional input from you.
Zerios1`6 said:
That is what makes it very strange. Both ADB and fastboot will recognize the phone just the ruu will not. I can issue commands in both adb and fastboot and the phone responds. Also for the ruu I should be in fastboot usb mode right? I have also disabled digitally signed drivers in windows 8.
Click to expand...
Click to collapse
Yeah in fastboot USB mode... Run it as admin, see if that works
Sent from my Nexus 7 using XDA Premium HD app
RLGL said:
The RUU is run from the desktop. If the phone is connected and gives a return when looking for devices doubleclick on the RUU and let it run.
It may require additional input from you.
Click to expand...
Click to collapse
I am running the ruu from the desktop but it still will not recognize my phone.
.torrented said:
Yeah in fastboot USB mode... Run it as admin, see if that works
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have tried running it as an admin but still won't recognize the phone. When I do compatibility checker it freezes up the program and it won't run at all.
Zerios1`6 said:
I am running the ruu from the desktop but it still will not recognize my phone.
I have tried running it as an admin but still won't recognize the phone. When I do compatibility checker it freezes up the program and it won't run at all.
Click to expand...
Click to collapse
What happens when you run "ADB Devices"
has numseen
RLGL said:
What happens when you run "ADB Devices"
Click to expand...
Click to collapse
ADB sees the phone and gives me the output of the device. It can see that it is there.
I had no luck getting the RUU to open at all on Windows 8 or the drivers working on a Windows 7 VM that I eventually partitioned my laptop's hard drive and installed the same Windows 7 media on the physical hardware. The RUU then ran fine with the phone in fastboot and with just admin rights. To save headaches that would be my suggestion.
Azbulldog said:
I had no luck getting the RUU to open at all on Windows 8 or the drivers working on a Windows 7 VM that I eventually partitioned my laptop's hard drive and installed the same Windows 7 media on the physical hardware. The RUU then ran fine with the phone in fastboot and with just admin rights. To save headaches that would be my suggestion.
Click to expand...
Click to collapse
I'll try that on my windows 7 laptop. I didn't have access to it these past few days and I was trying to find a way to do it on my windows 8 PC but if I have to do it on Win7 then I will. Thanks for the tip.
Azbulldog said:
I had no luck getting the RUU to open at all on Windows 8 or the drivers working on a Windows 7 VM that I eventually partitioned my laptop's hard drive and installed the same Windows 7 media on the physical hardware. The RUU then ran fine with the phone in fastboot and with just admin rights. To save headaches that would be my suggestion.
Click to expand...
Click to collapse
This still did not work. I am at a loss completely now.
Related
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
msiviter said:
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
Click to expand...
Click to collapse
You are probably running the wrong driver. Follow my driver guide part iv. (You should be on My HTC not ADB driver)
If not then probably your gold card hasn't stuck (check it) or you'll need to use windows xp instead (can use a virtual machine).
I had this issue when using windows 7 64 bit.
Download the drivers in the attachment in the noob guide. Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
oliwan said:
Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
Click to expand...
Click to collapse
Depending on whether this works for this guy, might be a simpler method than the alternative.
@msiviter - please try the above quoted method first
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Try This
While trying to flash the RUU the phone reboots.
When it is rebooted you see RUU.usb on your phone screen. But no flash process.
While phone is still connected to pc and is still in RUU.usb mode.
Go to device manager on your pc. Right klik android devices and renew the USB driver to HTC driver.
Reboot computer and reboot phone.
then try to flash again.
This was the solution for me.
Tried all the above, spent 6 hours on it, I've got the closest by going to a (win7 64bit) pc that has never had the sdk on it then the RUU goes further but terminates with error [140] Incorrect Bootloader. I've made my goldcard again to no avail (Sandisk 512mb) and checked the goldcard data which was OK, I'll try it tomorrow on a different (Kingston 8gb) card.
Any other ideas?
Thanks for your help so far.
Matt
Update: New SD card and goldcard now gives 'Error [131] Incorrect Customer ID' on my Win7 x64, I'll try on my dads old XP laptop later!!!
I suspect it is a windows 7 issue. On the first attempt I managed to downgrade when I moved to my Vista machine.
I must have tried for about 6 hours with Win7 then moved back to my old Vista PC and it worked first time.
From observing the process on Win7, when the phone boots to the bootloader, the RUU program then gives it 180 seconds to confirm Bootloader is loaded "waiting for bootloader...1-180sec". Looking at the system tray the USB driver that is used for HTCsync disconnects and the device now says it is Android 1.0 and Win7 needs to find a driver for this. Win7 fails to find a driver for "Android 1.0" so it never allows propper communication between the phone and the computer.
(There are separate Win7 64-bit drivers - check you are using these?)
P.P.S. The stock card that came with the phone worked fine as a Goldcard for me and I think most people.
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] whether trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
You installed the latest version of HTC Sync while your phone was unplugged/ Then you plugged the phone in to detect new drivers. Waited for the drivers to successfully install and then ran the RUU?
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
What drivers are reading in device manager when in the normal os? And same question when in fastboot mode?
I did exactly that on my win7 x64 and xp mce sp3 x86 pc's both had 'My HTC' in Device manager and had a sync relationship established with the latest 'Legend' HTC sync software.
Both gave the almost random error messages although now the bootloader almost finishes now so I'm past the [171] usb (driver) errors and I'm on [131] and [140] errors which pertain to bootloader and incorrect customer errors which I think are goldcard related. Although like most people I do rush through things and not read instructions! I've now made 4 goldcards via the various guides and I'm sure they are OK.
My Bro is getting his desire this week and I was determined to beat him to eclair but it looks like I'm in the lap of the T-mobile gods waiting until June (or july....September.... December etc).
Matt
I have same issue with msiviter, CUSTOMER ID ERROR.
I was able to run RUU regarding to guid from btdag (section IV).
What can I do now?
try deleting the drivers and then starting again perhaps?
I have the same issue here, can't downgrade to the previous Orange RUU, also using Win7 x64.
Have tried reinstalling drivers, and using other ROMS, nothing seems to work. I also find that when I run the RUU it loses connection to my phone before it even tried rebooting the phone into the bootloader.
shotgunfool said:
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Click to expand...
Click to collapse
this is how i've done 2 of mine, 2 dev laptops on 2 differnt hero's ... didnt work, with adb, sdk everything loaded for android dev ...
desktop worked fine for both hero's.
Same Issue
The trick to get the RUU to actually update the phone, for me, was to make sure that in Device Manager the ADB Interface driver was showing "My HTC" and not "HTC Bootloader". I was able to switch between drivers using the update driver button, and didn't need to download any new files or specify a folder or anything.
use windows xp and try my method of downgrade from 2.1 in my sig.
Hey guys
I've been trying to run ADB on my mac and it starts up but it won't recognize my phone, I run a parallel on my mac and I can run ADB on my windows parallel but when I switch over to my mac it won't recognize it for some reason when I go into 'system report' it show's my phone there but when I run ADB in terminal it doesn't show my device... I've been to
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html
http://forum.xda-developers.com/showthread.php?t=1387527
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx
I've tried everything and adb just won't recognize my phone, I have debugging on and make sure I have enough batter life...
I'm running Lion 10.7.4, I can fastboot without any difficulty but not ADB...
does anyone have any idea about what could be wrong or how I can update my drivers on my phone maybe?
THANK in advance!!!
RMseth said:
Hey guys
I've been trying to run ADB on my mac and it starts up but it won't recognize my phone, I run a parallel on my mac and I can run ADB on my windows parallel but when I switch over to my mac it won't recognize it for some reason when I go into 'system report' it show's my phone there but when I run ADB in terminal it doesn't show my device... I've been to
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html
http://forum.xda-developers.com/showthread.php?t=1387527
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx
I've tried everything and adb just won't recognize my phone, I have debugging on and make sure I have enough batter life...
I'm running Lion 10.7.4, I can fastboot without any difficulty but not ADB...
does anyone have any idea about what could be wrong or how I can update my drivers on my phone maybe?
THANK in advance!!!
Click to expand...
Click to collapse
I am EXTREMELY unfamiliar with a MAC computer, but I imagine it would have a command prompt like program. I believe it's called "Terminal" on MAC.
Have you tried manually running adb through terminal with a command?
Or is it just a problem within the phones adb?
Tried putting your phone on USB mass storage like mode, such as mount as disk drive?
Just trying to think of some things off the top of my head.
ya I've been using terminal and ADB shows that it starts up perfectly like my windows side. I can run fastboot commands with no problem, I've hooked my phone to the computer regularly and also as a mass storage device and ether way it doesn't recognize it.
I think it is something wrong with the ADB code on my phone because I was able to run adb with my brother's phone and my mac recognized it. his phone is stock he hasn't rooted it or anything...
RMseth said:
ya I've been using terminal and ADB shows that it starts up perfectly like my windows side. I can run fastboot commands with no problem, I've hooked my phone to the computer regularly and also as a mass storage device and ether way it doesn't recognize it.
I think it is something wrong with the ADB code on my phone because I was able to run adb with my brother's phone and my mac recognized it. his phone is stock he hasn't rooted it or anything...
Click to expand...
Click to collapse
That's pretty strange. Have you tried flashing to another ROM?
Ya I flashed by to my stock rom and it still didn't want to run... I flashed to an MIUI rom and it didn't want to recognize it ether... so I don't know what's going on... I did unlock my phone using the HTC method, but I did it through my windows side so that might be the reason because it was flashed under windows instead of mac, I don't know if that would really make a difference since it's the same language for fastboot and ADB... what do you guys think? if you think if would make a difference then I'll do it but it just takes a LONG time to run you have to lock the bootloader and then unlock it again, wipes all my data and then I have to reload everything over again... so if you think it would make a difference I'll definitely try it.
Did you get s off before you tried flashing roms? I know that miui is packaged with a custom kernel and you can't flash roms in recovery that have a custom kernel with s on.
Sent from my ADR6400L using Tapatalk 2
no I don't have s off, but I do have an unlocked bootloader and through adb and fastboot I can flash custom kernels, right now I have imoseyon-6.1.AOSP+root and running liquid Gingerbread 3.2 ROM, Android 2.3.7, with the tbolt's update a few months ago HTC locked down the Bootloader and there's no new program like revolutionary to unlock the new bootloader that I know of... I can change everything on my phone except the Radio, but it's through ADB and fastboot you just have to know the codes and what you're doing haha! I've been able to do all that through my windows parellel but I want to get away from that so I can develop everything through my mac OS which is suppose to be easier, from what I read and hear.
Hmmm... I have heard linux is but not mac. I dunno maybe you're right.
Sent from my ADR6400L using Tapatalk 2
Maybe you should try flashing back through windows.
I suppose it wouldn't hurt anything. I'm sure it's worth a shot anyways.
RMseth said:
...with the tbolt's update a few months ago HTC locked down the Bootloader and there's no new program like revolutionary to unlock the new bootloader that I know of...
Click to expand...
Click to collapse
You can S-OFF with the latest update. I have a windows tool that automates most of it.
so I relocked my bootloader with my windows and then unlocked it again through my MAC and the ADB still doesn't want to recognize my phone through terminal, it shows it on my system info just not through ADB...
trter10- you can!!!??? SA-WEE-TA!!! what's the link?
RMseth said:
so I relocked my bootloader with my windows and then unlocked it again through my MAC and the ADB still doesn't want to recognize my phone through terminal, it shows it on my system info just not through ADB...
trter10- you can!!!??? SA-WEE-TA!!! what's the link?
Click to expand...
Click to collapse
Link in my sig. You will have to relock and ruu before it works though because just relocking causes a security warning
Sent from my ADR6400L using Tapatalk 2
What to you mean relock and RUU?
RMseth said:
What to you mean relock and RUU?
Click to expand...
Click to collapse
Relock the boot loader and flash a pg05img to 2.11.605.19. Problem is that it wipes data
Sent from my ADR6400L using Tapatalk 2
1. Make sure parallells is closed so it doesn't steal your connection.
2. cd to the directory platform-tools
3. Type ./adb devices
I didn't see if you confirmed Parallels being closed or not.
OK I FIGURED IT OUT!!!! oh my goodness!!!! this was soo easy and I totally bashed my head in when I finally figured it out!!! oh my goodness!!!!
I had debugging on but I didn't have "unknown sources" marked!!! oh my goodness!!! so when I had both of those marked then it pulled my device right up on my MAC!!!
well for all of those that tried to help me thank you very much!!! I hope you all have a good day!!!
Hi Everyone,
I'm trying to connect my phone to the computer so I can root it but when I plug the USB in windows doesn't recognise my device and fails to install the drivers. I tried installing the newest HTC Sync and that didn't do anything to help. I tried uninstalling the drivers and reconnecting my phone but that didn't work either. I just got the same message.
Any help is much appreciated
Joe.Tolchard said:
Hi Everyone,
I'm trying to connect my phone to the computer so I can root it but when I plug the USB in windows doesn't recognise my device and fails to install the drivers. I tried installing the newest HTC Sync and that didn't do anything to help. I tried uninstalling the drivers and reconnecting my phone but that didn't work either. I just got the same message.
Any help is much appreciated
Click to expand...
Click to collapse
delete Htc Sync
Download this- RootEvo3d
Extract the zip file
Then install the HTCDriver3.0.0.007.exe file.
reboot and your phone should be able to connect.
iTzLOLtrain said:
delete Htc Sync
Download this- RootEvo3d
Extract the zip file
Then install the HTCDriver3.0.0.007.exe file.
reboot and your phone should be able to connect.
Click to expand...
Click to collapse
Thanks, i'll give it a go now!
Unfortunately that didn't work
Here's a couple suggestions. Check to see if your cord is the culprit and switch them out. I forgot your phone is having issues with PC detection. Try and connect it to another computer to rule out your PC. Another option would be to find a "signed" ruu and flash it through your bootloader. I emphasize signed because only a signed ruu can flash on a s-on device with the bootloader relocked. Then again if your bootloader is unlocked there's no point in trying the ruu option. Lol
Jsparta26 said:
Here's a couple suggestions. Check to see if your cord is the culprit and switch them out. I forgot your phone is having issues with PC detection. Try and connect it to another computer to rule out your PC. Another option would be to find a "signed" ruu and flash it through your bootloader. I emphasize signed because only a signed ruu can flash on a s-on device with the bootloader relocked. Then again if your bootloader is unlocked there's no point in trying the ruu option. Lol
Click to expand...
Click to collapse
My bootloader is already relocked, I'm trying to unlock it. Do you know where I could find a signed ruu? Can't hurt to try
Joe.Tolchard said:
My bootloader is already relocked, I'm trying to unlock it. Do you know where I could find a signed ruu? Can't hurt to try
Click to expand...
Click to collapse
Try here.
ramjet73
Joe.Tolchard said:
Hi Everyone,
I'm trying to connect my phone to the computer so I can root it but when I plug the USB in windows doesn't recognise my device and fails to install the drivers. I tried installing the newest HTC Sync and that didn't do anything to help. I tried uninstalling the drivers and reconnecting my phone but that didn't work either. I just got the same message.
Any help is much appreciated
Click to expand...
Click to collapse
Maybe your cable is damaged. Had the same problem on my girlfriends Desire and it was the cable
ramjet73 said:
Try here.
ramjet73
Click to expand...
Click to collapse
donkeykong1 said:
Maybe your cable is damaged. Had the same problem on my girlfriends Desire and it was the cable
Click to expand...
Click to collapse
Thanks guys, I'll try the signed ruu and try a different PC but unfortunately I only have one cable I can't really try that one till I get borrow a phone cable
Right well it's not the computer, it won't connect to my laptop either, I've tried restarting both the phone and the computer/ laptop and the signed ruu didn't help either
I believe its safe to say that perhaps your phones hardware got damaged somehow. It really sucks because had it been something else, you couldve used the wire trick to gain s-off and put your phones bootloader back on "locked" state. Ran the ruu and could've took it in for repair. My best guess is to take it to a non sprint repair shop and hopefully they will fix it for you. Good luck.
I'm already s-off. I didn't know this previously so I'll give that a go, thanks
Sent from my Evo 3D GSM using xda app-developers app
I have to have all the drivers correct as I have used this PC to unlock the bootloader and flash all my boot.img files, but the RUU won't find my DNA and gives me error 170 I believe it is. Windows 7 64bit ultimate.
try putting it in fastboot mode and as long as device manager says My HTC instead of android 1.0 and your phone reads fastboot usb then just run the RUU and it should work fine
crackeyes said:
try putting it in fastboot mode and as long as device manager says My HTC instead of android 1.0 and your phone reads fastboot usb then just run the RUU and it should work fine
Click to expand...
Click to collapse
In fastboot. In fact I can't get out of fastboot. I relocked bootloader fine, but can't seem to get the RUU to run. In DM it reads as "Android ADB device."
cstrife999 said:
In fastboot. In fact I can't get out of fastboot. I relocked bootloader fine, but can't seem to get the RUU to run. In DM it reads as "Android ADB device."
Click to expand...
Click to collapse
Could be it's 64 bit related as I recently tried flashing some files that were cake in win 7 32 bit but would not budge in win 8 64 bit. i have not figured out the issue as of yet but since I had another machine I just used that and it was fine. Think it's related to adb driver that either is not there or isn't working the same way in 64 bit...just a thought.
rootntootn said:
Could be it's 64 bit related as I recently tried flashing some files that were cake in win 7 32 bit but would not budge in win 8 64 bit. i have not figured out the issue as of yet but since I had another machine I just used that and it was fine. Think it's related to adb driver that either is not there or isn't working the same way in 64 bit...just a thought.
Click to expand...
Click to collapse
I'm going to try and run in VMware I guess. This is seriously frustrating I need to get this phone to stock to ship on ebay.
EDIT: Okay I ran it again after uninstalling/installing drivers for the millionth time and it worked somehow... Well I'm happy
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Did you try closing HTC Sync Manager?
Make sure and exit completely, right click and exit in the system tray
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
TheEmpyre said:
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
Click to expand...
Click to collapse
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
jonathan413 said:
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
Click to expand...
Click to collapse
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
an0ther said:
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
Click to expand...
Click to collapse
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
TheEmpyre said:
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
Click to expand...
Click to collapse
there is no other drivers showing up other than HTC's. and ive reinstalled it at least three times. everything is working except ADB recognizing the phone.
jonathan413 said:
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
Click to expand...
Click to collapse
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
an0ther said:
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Click to expand...
Click to collapse
thats already checked. just unistalled all duplicate drivers and started fresh. now there is 3 drivers not installing. CDC serial, Android phone, and CDC serial again. not sure why that one installs twice but it failed anyway..those 3 will not install for the life of me.
TheEmpyre said:
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
Click to expand...
Click to collapse
in the toolkit it says "device not found"..when i run ADB devices it says "list of devices" but shows nothing. Now when i run the command it says in missing some .DLL extension file
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
TheEmpyre said:
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
Click to expand...
Click to collapse
ok i followed your instructions and yes all the drivers installed correctly, thank you. BUT now i run the toolkit and now it says "error: device offline".
an0ther said:
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
Click to expand...
Click to collapse
not sure. i dont keep ADB on my computer. I download it only when I need to. But i followed the instructions from the other user but now i get this message. "error: device offline".
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
TheEmpyre said:
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
Click to expand...
Click to collapse
ok so i ran the toolkit for the 3rd or 4th time and it rebooted in fastboot to obtain my token to unlock. but when i enter the token into htcdev website it keeps saying its wrong length. i checked over and over and its the right length and im copying what i see from the htc dev website instructions but three times i get wrong token length.
ok i got the code to work..now onto the next step.if i have problems ill be back here.