hi devs!! guys whenever i try to run ruu i always get ERROR 170: USB CONNECTION ERROR!! i tried everything!! tried to put phone in fastboot usb mode and then run the ruu !! also tried putting the phone in RUU mode by command fastboot oem rebootRUU!! but no luck!:crying::crying: also tried rebooting the phone and then run the ruu!! tried different ports and usb cables but still no luck!! i am s-0ff and have already flashed the atest full firmware!! any help woulde be greatly appreciated!!
Related
Hi, flashed many many times but today when trying to flash the latest NRG ROM when I go into bootloader I am getting problems.
First of all when I go into bootloader it quickly flashes a message saying no image file or something.
Then HSPL 1.56 Olinex it doesnt show USB when I connect via USB just sticks at serial.
When connected to PC the PC just says USB device not recognized.
So I am unable to flash, I am at a loss to what to do???
I have tried different PCs, different cables, all have the same problem.
The phone boots into ROM OK and works fine, and then when I connect via USB it activesyncs fine. I really dont understand this, can anyone help?? PLeeaase as I want the new ROMs
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
nathlynn22 said:
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
Click to expand...
Click to collapse
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
[email protected] said:
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
Click to expand...
Click to collapse
I tried fast boot devices in fast boot USB by going into minisdk. Didn't try in recovery would have been good to try adb devices in recovery because I was stuck in that when first tried the custom recovery but a hard reset kicked it back out. Got recovery sorted just wanted to take nandroid backup off phone to PC and put root files which I'm still trying to get best 1's any idea where to get them where URL link is working? I've tried fastboot so doesn't work and basic trying to connect phone to PC for file transfer doesn't work either
stovie_steve said:
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
Click to expand...
Click to collapse
Ok so not only person. When I try connect mine doesn't even flag up I've connected a device USB debugging starts up on phone but have just noticed USB connection doesn't show. Plus I connect to PC and doesn't make the sound as I've it recognized my connecting anything. Fastboot USB comes up empty. I've been spending a couple hours here and there for past 2 nights trying to set phone up ready for rum runner. But my other question is if I'm already on htc_001 there's no need for me to change CID num anyways? Thanks
Try going to command prompt and typing in set devmgr_show_nonpresent_devices=1 followed by start devmgmt.msc
Click on view and show hidden devices. This will show devices which are not connected but have been installed. Look for something like android phone or android device and update the drivers by selecting update driver > let me select > have disk and then select the driver from here:
http://forum.xda-developers.com/showthread.php?t=2386956
Try that and see if it works
I'm all sorted now thanks just kept at it.
Sent from my HTC One using XDA Premium 4 mobile app
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 :cyclops:,
i bricked my phone, so i want to restore it using fastboot mode; the thing is that the pc doesnt detect it (the phone is charging but not connected), so i cannot flash anything;
the phone is bricked, so i can only get it to enter fastboot mode, and i've tried different usb cables, ports and even different pcs;
my last option is changing the usb board, but i was looking for any other ideas before doing that... thanks in advance
TRy install Fastboot package ROM with XiaoMiFlash.exe...
https://c.mi.com/oc/miuidownload/detail?guide=2
// ou, pc doesnt detect it
jojovrtak said:
TRy install Fastboot package ROM with XiaoMiFlash.exe...
https://c.mi.com/oc/miuidownload/detail?guide=2
// ou, pc doesnt detect it
Click to expand...
Click to collapse
dont worry, i end up solving it by trying even more cables
Hi ! I have just downgraded to PIE via NewFlasher and I'm running Stock pie.
My bootloader is unlocked.
I enter fastboot via Volume up key + connect USB
fastboot devices shows
BH9035KS9E fastboot
then I try to run
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
but it fails every time, with different messages, for instance
Sending 'recovery' (34548 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
I noticed that the blue led turns off immediately after I try to execute the fastboot flash
I've tried rebooting and several different cables.
I also tried with the linux and win10 version of fastboot, but no luck so far.
I also tried to boot via
fastboot boot twrp-3.3.1-0-lilac-pie-5.img
but the error message is the same
I also tried several versions of twrp ... and I don't know what else to try !
Any ideas ? thx !
Did you other cables?
Did you try other usb ports?
Did try usb 2.0? usb 3.0?
It works for me after any error.
Try another pc too.
If you face the same issue, it is a problem with the device.
VD171 said:
Did you other cables?
Did you try other usb ports?
Did try usb 2.0? usb 3.0?
It works for me after any error.
Try another pc too.
If you face the same issue, it is a problem with the device.
Click to expand...
Click to collapse
yep, tried all that
VD171 said:
Did you other cables?
Did try usb 2.0? usb 3.0?
Click to expand...
Click to collapse
this gave me an idea, silly but it worked, I tried to connect my usb cable to an old usb 2.0 splitter... and it worked, have no idea why !
thanks !
enorrmann said:
this gave me an idea, silly but it worked, I tried to connect my usb cable to an old usb 2.0 splitter... and it worked, have no idea why !
thanks !
Click to expand...
Click to collapse
well, definitely our creativity is the solution
you are welcome