[Q] Getting Error 170 while trying to RUU to 3.18...what am I doing wrong? - AT&T, Rogers HTC One X, Telstra One XL

As the title says: I'm trying to install the 3.18 RUU for my AT&T HTC One X. I'm currently on an old build of CM10.1 (beautifully maintained by H8rift) and was wanting to try the latest build he posted with the 3.4 Kernel. I am S-Off and Unlocked. I searched the forum (internal search seems to be broken at the moment) and all I keep seeing is mostly go to fastboot THEN run the RUU. Well I'm in fastboot (enabled the menu from within CM...less I just misunderstood that completely). Fastboot shows "Fastboot USB" but the RUU still gives Error 170. What did I do wrong?
Running this on a Windows 8 x64 system, installed HTC Sync Manager (still didn't help). I updated the Android SDK Tools to the latest version. My CID is all 1's (as per the S-Off directions). I'm at a loss here hehe.
Ooh I have TWRP 2.4.1.0. And yes I barely post, just always looking, reading, etc.

Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.

RollTribe said:
Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.
Click to expand...
Click to collapse
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).

Turbo Mach 5 said:
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).
Click to expand...
Click to collapse
Is your phone showing up in adb?

Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.

Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
Hmm... is your USB debugging on? If yes, try reinstalling the driver.

Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU

exad said:
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU
Click to expand...
Click to collapse
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).

Turbo Mach 5 said:
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).
Click to expand...
Click to collapse
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.

RollTribe said:
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.
Click to expand...
Click to collapse
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.

Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse
Annd now when I was all set to update to his latest one he posted, H8rift goes and begins posting nightlies and I don't have to downgrade touchpanel firmware! Hahaha (I had downgraded it and was about to install)! Still, thank you guys. I'm back in business!

Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse

sathish804 said:
Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Click to expand...
Click to collapse
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita

Hi timmaaa,
Thank You very much for the clarification and update on cm 10.2 rom.
I was thinking with RUU my bootloader is going to re-lock even though I have S-off.
Thanks and Regards,
Sathish.
timmaaa said:
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita
Click to expand...
Click to collapse

Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!

Your post is a bit confusing as to which drivers you actually have installed. Download the latest HTC Sync Manager from the HTC One XL page at HTC.com, install it, connect your phone, drivers will install, uninstall HTC Sync Manager but leave drivers installed. Also, make sure you're using a usb 2.0 port and the HTC cable that came with the phone.
Sent from my Evita

thelloydr said:
Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!
Click to expand...
Click to collapse
Scratch that...
Manually installed drivers and i got it working. Had to manual install twice, after one more error (171 this time), the RUU is applied. CM10.2 here i come!

htc vivid
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.

biradar said:
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.
Click to expand...
Click to collapse
You're in the wrong section, this is the HTC One XL section, you need to go here:
http://forum.xda-developers.com/htc-vivid

Just had the same issue trying to manually update my M9 to Nougat. Rebooted to download mode (Volume down & Power from off state) and it worked.

Related

Help!!!Messed it up

Hello dear members, Ok to start with I am having One X at&t and I am using it at the moment in Pakistan. It is sim unlocked. I was new to this rooting stuff but I already had a lot of experience with jailbreaking iphone stuff so I thought there should be no problem.
I started with rooting and after going through all the threads on this forum plus other websites I was able to root my cell and then I unlocked the bootloader. I was having difficulty with the drivers as I am using windows 8 but somehow managed to fix it (Thanks to xda forums).At this point I thought of upgrading to ota update but since I am out of range of at&t so I tried to manually install it by PC. Now when I tried to install, it was stuck on waiting for bootloader menu and then ultimately gave "error 171" "please check if your phone is connected by USB cable" .I checked the drivers they are properly installed and device manager recognizes my phone in bootloader menu too. I again surfed the net and forums and realized I have to relock the bootloader before installing RUU. So I relocked the bootloader by "fastboot oem lock" command and then tried again but no luck. But this time this thing happened when the cell screen was stuck at "blank screen+htc logo" and I got the error 171, I restarted my device and it automatically opened bootloader menu which on the top says *tampered* then *relocked* and then *security warning". I rebooted again and the phone is in working condition as of now but when I enter the bootloader menu first it says this is build verison for htc only blah blah and then there is security warning in bootloader menu.
I now just want to get my phone in the stock condition and then update it to RUU 2.20 . Can anyone help me with it?
Sorry for such a long and boring post but I tried to make my point clear.
I have attached the pics of my software info incase they may help.
Plus this is the info I get in bootloader menu:
Evita PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OPENDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
Ok so the tampered flag is due to you rooting your phone. It will go away if you RUU back to stock. The relocked flag will not go away even if you go back to stock. The security warning when it loads up the kernel (that red text that says "This build if for development purposes only yada yada yada") is nothing, don't even worry about it, we all have it once we start messing with our phones.
Anyway...Did you install HTC Sync on your PC? That installs all the necessary drivers to make sure your phone is recognized. I don't really know how Windows 8 behaves with our phone but if you have HTC Sync and the drivers installed and it still doesn't work then I would try borrowing a friend's Win7 computer and trying it there.
When you're in the bootloader and go to the fastboot menu does it say FASTBOOT USB at the top when you have it plugged in?
stnguyen09 said:
Ok so the tampered flag is due to you rooting your phone. It will go away if you RUU back to stock. The relocked flag will not go away even if you go back to stock. The security warning when it loads up the kernel (that red text that says "This build if for development purposes only yada yada yada") is nothing, don't even worry about it, we all have it once we start messing with our phones.
Anyway...Did you install HTC Sync on your PC? That installs all the necessary drivers to make sure your phone is recognized. I don't really know how Windows 8 behaves with our phone but if you have HTC Sync and the drivers installed and it still doesn't work then I would try borrowing a friend's Win7 computer and trying it there.
When you're in the bootloader and go to the fastboot menu does it say FASTBOOT USB at the top when you have it plugged in?
Click to expand...
Click to collapse
Thanks for replying. Yes it does says FASTBOOT USB highlighted in red. And yes I have installed HTC Sync which apparantely didn't install the required drivers and I had to install them manually from device manager but they are properly installed now as there is yellow triangle in device manager and it recognizes my phone as "android adb interface" when the phone is in bootloader menu and "android composite ABD interface " when the phone is on.
UsmanImtiaz said:
Thanks for replying. Yes it does says FASTBOOT USB highlighted in red. And yes I have installed HTC Sync which apparantely didn't install the required drivers and I had to install them manually from device manager but they are properly installed now as there is yellow triangle in device manager and it recognizes my phone as "android adb interface" when the phone is in bootloader menu and "android composite ABD interface " when the phone is on.
Click to expand...
Click to collapse
Hmmm... I'm not sure anymore. Did you try using another usb port? It sounds stupid but I've had more than one instance of certain usb ports not doing what they should because of drivers only being installed/recognizing certain ports.
Which RUU did you try running? The 2.20 or the 1.85?
Sent from my One X using xda premium
stnguyen09 said:
Hmmm... I'm not sure anymore. Did you try using another usb port? It sounds stupid but I've had more than one instance of certain usb ports not doing what they should because of drivers only being installed/recognizing certain ports.
Which RUU did you try running? The 2.20 or the 1.85?
Sent from my One X using xda premium
Click to expand...
Click to collapse
Ok I will try changing the ports. I am trying to run 2.20 RUU
Can never understand why people who are rooted and bootloader unlocked want to install 2.20 OTA or RUU. You will lose ability to flash kernels using recovery.
Consider it a blessing that the RUU did not install. There is no benefit to installing the 2.20 RUU. just flash the pre-rooted stock 2.20 in the Development forum. Better yet, rooted stock 2.23, which is newer, or custom ROMs based on 2.23 or 2.29.
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
Can never understand why people who are rooted and bootloader unlocked want to install 2.20 OTA or RUU. You will lose ability to flash kernels using recovery.
Consider it a blessing that the RUU did not install. There is no benefit to installing the 2.20 RUU. just flash the pre-rooted stock 2.20 in the Development forum. Better yet, rooted stock 2.23, which is newer, or custom ROMs based on 2.23 or 2.29.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Wait, we lost kernel flashing with 2.20?
stnguyen09 said:
Wait, we lost kernel flashing with 2.20?
Click to expand...
Click to collapse
yep. new Hboot locks down the boot partition. This is a good thing IMHO less bricks due to flashing ROMS meant for the Tegra 3 HOX.
fastboot still works for boot.img.
More importantly it WP's hboot. Good for some users (such as OP), bad for others.

[Q] Cyanogenmod install problems

Just tried to install Cyanogenmod for the first time but i am also stuck like many others. So excuse me for any noobness.
Got an HTC one S. Installed Cyanogenmod 1.0.0-ville (stable), rooted with openrecovery. Forgot to wipe the data and cache before install so thought that might be the reason for not getting past the Cyanogen BOOT screen, did it afterwards still no response. Followed instructions coming from this thread but am stuck with he ""waiting for device" error when executing fastboot flash boot boot.img. I think it has something to do with not having the USB debug mode. Fastboot doesnt recognize the device.
The thing that puzzles me is that at point 2 of the instuctions USB debugging must be enabled, how can i check this mode is enabled without getting into the Android device settings?
Sounds like a driver issue to me. Have you used the phone on that computer before.
Sent from my HTC One S using the xda-developers app
npiper05 said:
Sounds like a driver issue to me. Have you used the phone on that computer before.
Click to expand...
Click to collapse
Thank you for your reply
Yes i did the whole install process with the same pc, got HTC sync manager installed and did the Fastboot process with the same machine.
kverleg said:
Thank you for your reply
Yes i did the whole install process with the same pc, got HTC sync manager installed and did the Fastboot process with the same machine.
Click to expand...
Click to collapse
Hmm... Maybe try re-installing HTC Sync and the drivers on your PC. This post http://forum.xda-developers.com/showthread.php?t=1604677 has a link for the drivers.
Just curios - what hboot, radio do you have? Are you s-on or s-off? And what TWRP version are you using?
Did you make a backup you could restore?
**Edit**
One last thought, what ROM were you running before? Was it stock? I'm wondering if you could flash a rom that works with the stock kernel (maybe TrickDroid 7.0?). It depends on what you were running before. Other option is to run an RUU to get back to stock,and then start from scratch. Can be a pain, but will give you a fresh start. I'm sure those aren't the only solutions, as I'm still learning all this stuff.
Good luck and feel free to ask questions...
npiper05 said:
Hmm... Maybe try re-installing HTC Sync and the drivers on your PC. This post http://forum.xda-developers.com/showthread.php?t=1604677 has a link for the drivers.
.
Click to expand...
Click to collapse
Hasoon's all in one toolkit drivers did the trick mate killer! Thanks a lot!
kverleg said:
Hasoon's all in one toolkit drivers did the trick mate killer! Thanks a lot!
Click to expand...
Click to collapse
Glad you got it sorted out!

After RUU Camera won't work

Hey all,
I used the 318 RUU on my hox. Now the camera wont work, it launches and the app opens but then in closes. If I try to relaunch it a toast pops up and says cant connect to camera.
Unlocked
S-off
11111111
hboot 2.14.0000
0.24p.32.09.06
Would the Super CID or the bootloader effect the camera?
stoopid2001 said:
Hey all,
I used the 318 RUU on my hox. Now the camera wont work, it launches and the app opens but then in closes. If I try to relaunch it a toast pops up and says cant connect to camera.
Unlocked
S-off
11111111
hboot 2.14.0000
0.24p.32.09.06
Would the Super CID or the bootloader effect the camera?
Click to expand...
Click to collapse
No
I would check the MD5 of the RUU if possible. If it's off, redownload and reRUU, if it still happens, it's likely a hardware issue. I think I recall reading a thread a while back with a similar issue that was not in fact hardware related however I cannot recall how it was fixed.
Just re-RUU'd, no dice same issue.
edit-Flashed CFX, camera works fine. This doesn't help with selling it on ebay though!
stoopid2001 said:
Just re-RUU'd, no dice same issue.
edit-Flashed CFX, camera works fine. This doesn't help with selling it on ebay though!
Click to expand...
Click to collapse
What is CFX? I have the same problem and have yet been able to fix.
HOXnoo8 said:
What is CFX? I have the same problem and have yet been able to fix.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2426919
My camera won't work on stock (3.18 RUU) but it worked on CM 10.1 before and now it works on CFX.
stoopid2001 said:
forum.xda-developers.com/showthread.php?t=2426919
My camera won't work on stock (3.18 RUU) but it worked on CM 10.1 before and now it works on CFX.
Click to expand...
Click to collapse
I flashed CFX and no dice. I will keep looking. Thanks.
Same problem here guys, camera works sometimes and sometimes just black screen. It works when I erase the camera cache or data but, after one use, the black screen again.
Ale993 said:
Same problem here guys, camera works sometimes and sometimes just black screen. It works when I erase the camera cache or data but, after one use, the black screen again.
Click to expand...
Click to collapse
Its not the "same problem" unless every single detail is exactly the same. Otherwise, you need to tell us the details.
If S-off, did you try to RUU the phone?
Is this the same across different ROMs.
redpoint73 said:
Its not the "same problem" unless every single detail is exactly the same. Otherwise, you need to tell us the details.
If S-off, did you try to RUU the phone?
Is this the same across different ROMs.
Click to expand...
Click to collapse
Yes. I have S-Off. It is the same across different ROMS, Hboots, firmwares, and TWRP. I have been trying to RUU again but cant seem to get my phone to jive with ADB. I know thats a different topic altogether but it is definitely hindering my progress. I've updated SDK, installed the Drivers from HTC Sync, and tried to point device manager to the drivers manually. Still no "Android Composite Device". Even HTC Sync Manager does not recognize the device. Fastboot does not work either. I know that I used to have everything set up correctly because I was able to S-Off, RUU, run adb commands in the past on both of my computers and no problems. Only now. Whats weird, is that android does register in device manager when i am in TWRP. Back to the subject at hand, I am not able to RUU to check if that fixes the camera. RIght now I am on the Stock Telstra NEW 5.08.841.3 UPDATE with root. TWRP 2.6.0. Hboot 2.15.
HOXnoo8 said:
Yes. I have S-Off. It is the same across different ROMS, Hboots, firmwares, and TWRP. I have been trying to RUU again but cant seem to get my phone to jive with ADB. I know thats a different topic altogether but it is definitely hindering my progress. I've updated SDK, installed the Drivers from HTC Sync, and tried to point device manager to the drivers manually. Still no "Android Composite Device". Even HTC Sync Manager does not recognize the device. Fastboot does not work either. I know that I used to have everything set up correctly because I was able to S-Off, RUU, run adb commands in the past on both of my computers and no problems. Only now. Whats weird, is that android does register in device manager when i am in TWRP. Back to the subject at hand, I am not able to RUU to check if that fixes the camera. RIght now I am on the Stock Telstra NEW 5.08.841.3 UPDATE with root. TWRP 2.6.0. Hboot 2.15.
Click to expand...
Click to collapse
You've tried other USB cables and other USB ports? adb connection issues are rather common, but not reading on USB at all (HTC Sync) is a bit more unusual.
redpoint73 said:
You've tried other USB cables and other USB ports? adb connection issues are rather common, but not reading on USB at all (HTC Sync) is a bit more unusual.
Click to expand...
Click to collapse
Yes. I have tried to OEM cable, iFrogz cable (which has always done the job), a cable I purchased from Best Buy, and an LG cable. I used front ports and back ports. Same thing. Its almost as if the last time I RUU's was the last time period that adb was working. I never did do much after that except for custom roms and upgrading to firmware 2.15. But the camera stopped working BEFORE I RUU'd. Thats why I did it in the first place.
I am at the moment trying these things with no sim card. Would that make a difference? I just downloaded new drivers from the General Thread and when I use device manager and uninstall the drivers and then point to my new ones, it says that the drivers are up to date. Still only seeing the phone as an MTP device. Im stuck. I just dont understand how my phone cannot be recognized as an adb device now when just a month ago it was good.
Little help please? Kind of a big deal.
im having the same issue....when i run RUU 3.18 firmware my camera freezes and doesnt work on stock rom. if i run RUU with older firmware i my camera works fine it only does it with 3.18. Anyone find a fix?

[Q] Can't install cyanogen mod on HTC Sensation Z710a

Hi!
I have a HTC Sensation that I would like to put Cyanogenmod on but no matter what I do I can't get anywhere. Also I'm 100% new to installing custom ROMs/Rooting. I can't do revolutionary because my HBOOT is 1.27.0000 so I found out there is a way to unlock it from the HTC Dev site but that doesn't work either because it keeps saying 'Waiting for device'. I have seen about 5 articles that say how to fix this problem (Check drivers, change USB Port, move certain files, etc) but after trying every single one nothing has changed. One said to use HTC Sync to get the drivers but my phone can't find HTC Sync on my computer and HTC Sync can't find my phone.
I have used http://forum.xda-developers.com/showthread.php?t=1152148 and http://forum.xda-developers.com/showthread.php?t=1631861 but I can't get past unlocking bootloader. Any help would be very much appreciated!!!
Thanks!
Phone details:
Model: HTC Sensation Z710a
Android Version: 4.0.3
HBOOT: 1.27.0000
zolwie said:
Hi!
I have a HTC Sensation that I would like to put Cyanogenmod on but no matter what I do I can't get anywhere. Also I'm 100% new to installing custom ROMs/Rooting. I can't do revolutionary because my HBOOT is 1.27.0000 so I found out there is a way to unlock it from the HTC Dev site but that doesn't work either because it keeps saying 'Waiting for device'. I have seen about 5 articles that say how to fix this problem (Check drivers, change USB Port, move certain files, etc) but after trying every single one nothing has changed. One said to use HTC Sync to get the drivers but my phone can't find HTC Sync on my computer and HTC Sync can't find my phone.
I have used http://forum.xda-developers.com/showthread.php?t=1152148 and http://forum.xda-developers.com/showthread.php?t=1631861 but I can't get past unlocking bootloader. Any help would be very much appreciated!!!
Thanks!
Phone details:
Model: HTC Sensation Z710a
Android Version: 4.0.3
HBOOT: 1.27.0000
Click to expand...
Click to collapse
have you enabled usb debugging mode from settings?
in the hboot screen if it shows only fastboot then choose fastboot from the menu when it is connecting to the pc
it will show fastboot usb after
rzr86 said:
have you enabled usb debugging mode from settings?
in the hboot screen if it shows only fastboot then choose fastboot from the menu when it is connecting to the pc
it will show fastboot usb after
Click to expand...
Click to collapse
Yes I did the whole process with USB Debugging on.
zolwie said:
Yes I did the whole process with USB Debugging on.
Click to expand...
Click to collapse
what OS do you have in your pc?
rzr86 said:
what OS do you have in your pc?
Click to expand...
Click to collapse
Windows 8.1 x64-bit
zolwie said:
Windows 8.1 x64-bit
Click to expand...
Click to collapse
that's why you are facing those issues
there are some incompatibility with win8
search here in xda how to setup adb/fastboot on windows 8
you will see plenty of guides
rzr86 said:
that's why you are facing those issues
there are some incompatibility with win8
search here in xda how to setup adb/fastboot on windows 8
you will see plenty of guides
Click to expand...
Click to collapse
This came up http://forum.xda-developers.com/showthread.php?t=2588979 . Will this be ok and after installing it do I do the cmd stuff with my phone on the hboot screen or do I do something else?
EDIT: I installed it and it still says waiting for device. I will look at some other posts.
EDIT #2: Also tried this http://forum.xda-developers.com/galaxy-nexus/general/tutorial-installing-adb-fastboot-t1982718 but still says waiting for device. Starting to think maybe my phone is completely against me changing the OS.
zolwie said:
This came up http://forum.xda-developers.com/showthread.php?t=2588979 . Will this be ok and after installing it do I do the cmd stuff with my phone on the hboot screen or do I do something else?
EDIT: I installed it and it still says waiting for device. I will look at some other posts.
EDIT #2: Also tried this http://forum.xda-developers.com/galaxy-nexus/general/tutorial-installing-adb-fastboot-t1982718 but still says waiting for device. Starting to think maybe my phone is completely against me changing the OS.
Click to expand...
Click to collapse
see these 2 too
http://forum.xda-developers.com/showthread.php?t=2232799
http://forum.xda-developers.com/showthread.php?t=1583801
see how it goes
rzr86 said:
see these 2 too
http://forum.xda-developers.com/showthread.php?t=2232799
http://forum.xda-developers.com/showthread.php?t=1583801
see how it goes
Click to expand...
Click to collapse
Still doesn't work. I think by now I have installed so many different programs/files trying to get it to work that they might be getting confused with each other or something. I might see if deleting all the files and starting over will help tomorrow. Thanks for the help so far!
I deleted all the files I could find that I installed and then tried this http://forum.xda-developers.com/showthread.php?t=2646453 as well but still getting nowhere. Any ideas what might be the problem?
zolwie said:
I deleted all the files I could find that I installed and then tried this http://forum.xda-developers.com/showthread.php?t=2646453 as well but still getting nowhere. Any ideas what might be the problem?
Click to expand...
Click to collapse
if you are using usb 3.0 ports try with usb 2.0 ports

HTC One cant figure out what I need to do

I have an HTC One M7 from sprint that I owned for not even 6 months before it started randomly bootlooping and losing signal. I gave up on it and used it as a paper weight, but now I would like to finally get it functional again as my old phone is no longer usable. I am new to Android devices. I have read thread after thread for the past 2 days and have yet to fix this phone.
I have cleared all caches and done factory resets to no avail.
The phone is stuck in bootloop if it is allowed to restart as normal. Once booted, it will immediately reboot if you swipe to unlock. If you wait, it will display "com.htc.htcdialer not responding" before rebooting again. It does not bootloop if you put it into bootloader/fastboot/recovery whatever you call it. I am trying to just load Android Revolution on to the phone instead of retrying the old OS.
I have already unlocked bootloader. I originally tried to push the androidrevolution.zip to the phone, but ADB gave an "error: device not recognized". I tried to install twrp recovery, but fastboot gets stuck at "waiting on device". I understand I'm having issues with the PC not recognizing the phone. The only android thing in device manager is "Android 1.0" and it has no driver installed. I have installed multiple drivers and tried different ports and cables. I cannot use PDANet to install drivers to recognize it because I cannot get access to the phone to enable debug mode. I cannot use sideloading because I can't get the device to be recognized. Everything I try seems like a constant circle.
I don't know if I'm giving enough information or not. I'll answer any question/give whatever info you need to solve this.
Can anyone please give me any insight as to how I can get my phone to work before I get angrier and break it?
BUMP
Has anyone else been in the same boat? Still struggling to figure this out.
DoostyD said:
BUMP
Has anyone else been in the same boat? Still struggling to figure this out.
Click to expand...
Click to collapse
If its a software related error you can get rid of it by flashing (installing) the stock firmware again. First you ned to check HBoot and CID. Connect your phone in "fastboot" bode, open commandline and type
fastboot getvar all
Post the output here (Delete your IMEI). Then i will get the right firmware for you and can guide you how to install it.
If the error is hardware related (signal loss?!) you probably can't do much on your own. What brings me no the next question: If you had the phone for just 6 month when the errors occured first, why didn't you let the vendor fix it? Phone still had guarantee.
It just says :
Waiting for device
My computer won't recognize the phone properly.
I took my phone to sprint and was told I would have to pay $65 for a used phone replacement, which I thought was ridiculous. I contacted HTC and was told I would have to pay shipping to send it in, and would be a week before I got an answer for it. (Fix it or refurbished one). So I said screw it, and reactivated my old phone. I'd fix it myself eventually.
DoostyD said:
It just says :
Waiting for device
My computer won't recognize the phone properly.
I took my phone to sprint and was told I would have to pay $65 for a used phone replacement, which I thought was ridiculous. I contacted HTC and was told I would have to pay shipping to send it in, and would be a week before I got an answer for it. (Fix it or refurbished one). So I said screw it, and reactivated my old phone. I'd fix it myself eventually.
Click to expand...
Click to collapse
Make sure you install the "fastboot" driver correctly. Are you running win 8.1?
LS.xD said:
Make sure you install the "fastboot" driver correctly. Are you running win 8.1?
Click to expand...
Click to collapse
I'm pretty positive it's installed correctly. I've deleted it and reinstalled it 3 times. The first two times I did it all manually. The one I'm currently running I got from here:
http://forum.xda-developers.com/showthread.php?t=2317790
I am running Windows 7 Home Premium 64bit.
DoostyD said:
I'm pretty positive it's installed correctly. I've deleted it and reinstalled it 3 times. The first two times I did it all manually. The one I'm currently running I got from here:
http://forum.xda-developers.com/showthread.php?t=2317790
I am running Windows 7 Home Premium 64bit.
Click to expand...
Click to collapse
I meant the HTC driver (for fastboot) -> Your devices must be listed as "My HTC" in the device manager. If it has a yellow exclamation mark, try to install the driver manually for "My HTC".
@DoostyD
LS.xD said:
I meant the HTC driver (for fastboot) -> Your devices must be listed as "My HTC" in the device manager. If it has a yellow exclamation mark, try to install the driver manually for "My HTC".
Click to expand...
Click to collapse
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Newyork! said:
@DoostyD
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Click to expand...
Click to collapse
I had done that before but it didn't work. I tried it again but this time noticed a windows protection blocking it. I disabled it and got it all to work now!
I put the new rom on the phone but it gets stuck at the HTC screen and never loads. I read that I have to change the CID and change to S-OFF for it to work.
However, now I've got another problem that I can't find a solution to ANYWHERE.
I cannot get the phone to S-OFF. Everytime I try to change my CID I get this:
C:\Android>fastboot oem readcid
...
(bootloader) cid: SPCS_001
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Android>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Android>
Click to expand...
Click to collapse
I've tried manually changing the CID and using a CID script and both keep giving me the "[JAVACARD_ERR] SD/USBDISK Init error".
Any ideas??
DoostyD said:
I had done that before but it didn't work. I tried it again but this time noticed a windows protection blocking it. I disabled it and got it all to work now!
I put the new rom on the phone but it gets stuck at the HTC screen and never loads. I read that I have to change the CID and change to S-OFF for it to work.
However, now I've got another problem that I can't find a solution to ANYWHERE.
I cannot get the phone to S-OFF. Everytime I try to change my CID I get this:
I've tried manually changing the CID and using a CID script and both keep giving me the "[JAVACARD_ERR] SD/USBDISK Init error".
Any ideas??
Click to expand...
Click to collapse
Is your phone already S-OFF ? Uninstall HTC sync before changing the CID. If you want to flash a unbranded firmware later, make sure that its compatible with your MID.
BTW
Why don't you flash the sprint firmware again to check if your error got fixed.
Here is the link to the current Sprint RUU:
http://www.htc.com/us/support/htc-one-sprint/news/
Sent from my HTC One_M8 using XDA Free mobile app
Newyork! said:
@DoostyD
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Click to expand...
Click to collapse
LS.xD said:
Is your phone already S-OFF ? Uninstall HTC sync before changing the CID. If you want to flash a unbranded firmware later, make sure that its compatible with your MID.
BTW
Why don't you flash the sprint firmware again to check if your error got fixed.
Click to expand...
Click to collapse
No, the phone says it's S-ON. If I uninstall HTC Sync, won't that remove the drivers I needed to get my computer to recognize my phone?
I'm sorry I'm new to this, but what is MID?
I thought about retrying the original sprint firmware but I'd honestly rather just try out a new custom one.
c5satellite2 said:
Here is the link to the current Sprint RUU:
http://www.htc.com/us/support/htc-one-sprint/news/
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
My bootloader is unlocked and I have TWRP recovery. Would I have to remove those to use the Sprint RUU?
DoostyD said:
My bootloader is unlocked and I have TWRP recovery. Would I have to remove those to use the Sprint RUU?
Click to expand...
Click to collapse
Just relock your bootloader to use the ruu BUT if your phone is S-ON you can only RUUs that are newer or the same version number as actually installed on the phone. You can safely uninstall HTC sync, drivers persist.
The RUU link I posted is LP and was just released. Should be newer than what he was running.
Sent from my HTC One_M8 using XDA Free mobile app
c5satellite2 said:
The RUU link I posted is LP and was just released. Should be newer than what he was running.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I checked the RUU myself. Was just a general information and not a "stop, what are you doing?!''
LS.xD said:
I checked the RUU myself. Was just a general information and not a "stop, what are you doing?!''
Click to expand...
Click to collapse
Ok, cool. Just letting him and everyone else know.
Sent from my HTC One_M8 using XDA Free mobile app

Categories

Resources