Hey,
Today I tried to install stock and downloaded an RUU while I had my older ones still there.
While I was trying to install it through the exe it showed Error 170, I tried it again so the same. I tried using my old RUU, even that showed me the same problem.
So I decided to copy the zip from the exe and flash it manually.
I copied the zip and got to the bootloader and then typed "fastboot OEM rebootRUU"
Then, "fastboot flash zip ROM.zip
It ran with some errors and the green bar on the phone stopped close by to the end. I waited for long and it still didn't move further so I decided to flash it all over again.
So this time I typed "fastboot OEM rebootRUU" and I get a black HTC symbol with 4 error symbol each in one corner of the screen. It goes no further than this. Such here.
Any help is much appreciated.
Error 170 from my reading is a driver issue. This thread suggests that you uninstall any HTC (or other like Samsung) sync managers and drivers. Reinstall the latest HTC Sync (to get the latest drivers) and then uninstall HTC Sync leaving the drivers. Then, use "fastboot devices" to make sure your PC sees your phone. If good, then use the latest RUU.exe and hopefully it will reset everything.
The four icons in the corners (again from my Google searching) means you are stuck in a bad RUU flash. If the latest RUU doesn't work, you may need to find the one that matches your radio that you currently are using (source).
This other thread may help too. Good luck!
Related
Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.
Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?
If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.
flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.
Mud3 said:
flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.
Click to expand...
Click to collapse
I recently had the same issue, you should be able to fix this by following these steps, keep in mind, continuing this process will unroot your device. Thus, you will loose all of your data on your phone.
first begin by booting into bootloader, then plugging in your device via usb cable to your computer, it should now say "fastbootusb" on the device's screen.
if you don't already have the the fastbooot files required for your computer, you can download them here: ftp.qbking77.(com)/Files/OneDrivers_Fastboot.zip
after that, extract the zip file somewhere on your computer, and open the fastboot folder. Now hold down shift and click on an empty space in the folder and choose open new command window here, or something along those lines.
Now that you've done this, type fastboot oem lock and press enter, this will relock your phones bootloader.
Now, unplug your phone from usb, and reboot back into fastboot, and once again, plug the device into the computer. Just as before, your phones screen should now say fastboot usb. You can now flash this file via fastboot by following the instructions below.
androidfilehost.(com)/?fid=23329332407568410
rename the file downlaoded to firmware.zip and copy it to the folder containing your fastboot.exe file
now in the command prompt window, type in Fastboot oem rebootRUU
you should now see a black screen with the HTC logo, type Fastboot flash zip firmware.zip,
once that is complete, type fastboot reboot and once more, reboot into fastboot
you can now download this RUU file from the following link: androidfilehost.(com)/?fid=23329332407573774
extract the zip folder somewhere on your computer
boot into bootloader, and once again choose fastboot,
plug in your usb cable to your phone and computer, and the phone should once again say fastboot usb.
now open the folder you extracted and run ARUWizard.exe, this will unroot your device and return you to stock.
now, if you wish, you may re root your device.
Hope this works, if none of this makes sense, mention it. I typed this up in a bit of a rush.
also, you will have to copy and paste the links, as I have not made 10 general posts, so I can't add direct links to my post. Sorry mate.
have issue with the first step there... can't boot into bootloader, i'm stuck on the black screen with silver htc letters in the middle, exclamation on all four corners. i'm able to turn off the phone using the flashlight trick, but when i boot back up it's to that screen every time. it's stuck there from a failed ruu, just don't know how to get un stuck...
okay, some more info here. I was running hboot 1.57 ( i did relock) trying to run ruu 5_03_651_3 i'm not even positive this is the ruu i should be trying to use. now when I try to run the ruu it starts going but every time eventually fails wtih windows bringing up an error that says htc_fastboot.exe has topped working. i hit close program and the rom update utility gives me error [171]: usb connection error
edit: and now after the sixth time of that failing i am able to boot into bootloader again! weird... and it says i have an os now... still wont boot up all the way, but it's no longer blank on the bootloader screen.
second edit: after getting the usb error again and again i remembered glossing over something about flashing roms not liking usb 3.0 or something... switched to a usb 2.0 port and ruu worked perfectly. now to try and get this thing rooted again.
So, I took a look around the forums thinking that maybe another newbie such myself did this thing but apparently I am one of a kind. So here is my story:
I have my HTC One M7 since the summer of 2014, I rooted it without any problems and unrooted it when the Lollipop update came out. After two or three days of the update, I had a problem where my phone would lose all sounds and would be unable to play any media that involved music. I thought it might be a software problem so I rooted it again and I installed the ViperOne ROM from the forums. Despite the fact that I really loved the ROM, the problem insisted and once/twice a day I needed to clear cache, restart the phone and if I was lucky it would go away on the first trial.
P.S. The problem only occurred when a call started.
This past Friday however, the problem wouldn't go away no matter what I did. My phone had lost all sounds and I couldn't do anything about it. Ringtones, alarms, videos, youtube, calls, even the bootup sound, nothing.
So I decided to redo everything from the beginning, in case I did something wrong and with the hope that it will just get fixed. Thinking that my software was the problem, I decided not to do a backup (please don't kill me I know it was a stupid decision) and to just wipe everything off, and do it from scratch. I re-installed viper as a first step but it didn't fix. I wiped the whole system and data partitions and installed the ROM again, nothing. Then I tried to install a clean HTC RUU and I found that the latest was this one
Code:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3
but it needed to be installed through HTC Sync and it just wouldn't work. I was getting a message that the phone was not connected.
Uninstalled HTC Sync, Re-installed HTCDriver_4.1.0.001 and downloaded a KitKat ROM from HTC1Guru site but when I tried to install it, I was getting an error message from the TWRP recovery.
Next, I downloaded Guru_Reset_M7_2.24.401.8, installed it, opened it, sound still wouldn't work no matter what. Also, while I installed the Guru Reset, I was asked if I wanted to also install stock recovery and I said yes. Since this ROM was able to be installed, I started doing the OTA updates with the hope that one of them might fix the sound problem. On the third update, the phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
TL;DR
phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
Please help me I don't know what to do and I cannot send it to service to fix it because the Bootloader has the "Tampered" message on top.
This is what my bootloader has:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4A.17.3250.14
OpenDSP-v35.120.274.0718
OS-7.19.401.2
eMMC-boot 2048MB
skypse said:
So, I took a look around the forums thinking that maybe another newbie such myself did this thing but apparently I am one of a kind. So here is my story:
I have my HTC One M7 since the summer of 2014, I rooted it without any problems and unrooted it when the Lollipop update came out. After two or three days of the update, I had a problem where my phone would lose all sounds and would be unable to play any media that involved music. I thought it might be a software problem so I rooted it again and I installed the ViperOne ROM from the forums. Despite the fact that I really loved the ROM, the problem insisted and once/twice a day I needed to clear cache, restart the phone and if I was lucky it would go away on the first trial.
P.S. The problem only occurred when a call started.
This past Friday however, the problem wouldn't go away no matter what I did. My phone had lost all sounds and I couldn't do anything about it. Ringtones, alarms, videos, youtube, calls, even the bootup sound, nothing.
So I decided to redo everything from the beginning, in case I did something wrong and with the hope that it will just get fixed. Thinking that my software was the problem, I decided not to do a backup (please don't kill me I know it was a stupid decision) and to just wipe everything off, and do it from scratch. I re-installed viper as a first step but it didn't fix. I wiped the whole system and data partitions and installed the ROM again, nothing. Then I tried to install a clean HTC RUU and I found that the latest was this one
Code:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3
but it needed to be installed through HTC Sync and it just wouldn't work. I was getting a message that the phone was not connected.
Uninstalled HTC Sync, Re-installed HTCDriver_4.1.0.001 and downloaded a KitKat ROM from HTC1Guru site but when I tried to install it, I was getting an error message from the TWRP recovery.
Next, I downloaded Guru_Reset_M7_2.24.401.8, installed it, opened it, sound still wouldn't work no matter what. Also, while I installed the Guru Reset, I was asked if I wanted to also install stock recovery and I said yes. Since this ROM was able to be installed, I started doing the OTA updates with the hope that one of them might fix the sound problem. On the third update, the phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
TL;DR
phone got bricked and stuck in a bootloop.
At this point, I can only enter bootloader without the phone crashing.
Recovery gives me a Red triangle with an exclamation mark in it.
Factory Reset goes bootloop.
And the worst of all is that now my PC doesn't recognize the device and fastboot commands give me the "waiting for device" middle finger and I can't do anything.
Please help me I don't know what to do and I cannot send it to service to fix it because the Bootloader has the "Tampered" message on top.
This is what my bootloader has:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4A.17.3250.14
OpenDSP-v35.120.274.0718
OS-7.19.401.2
eMMC-boot 2048MB
Click to expand...
Click to collapse
oops, that's the wrong RUU for you phone, I would also hazard a guess that the guru reset is just too old, the key for you is in the numbers, your current os is 7.19.401.2 its the 401 part which matters the most, the 7 part is also android revision, as your on 7, I would say 2 is very too old for your phone., the RUU you tried to use if you look at the numbers is android revision 4 developer edition 1540 (4.19.1540.9) hope that explains that a little for you.
The red exclamation mark is stock recovery, when you see that symbol, press volume up and power a few times and you'll get the menu.
well the first thing you need to do is get your drivers sorted, so uninstall HTC sync manager and the drivers now restart your computer, then re-download it, install it, and then go into add/remove programs and remove HTC sync, just above it you will see HTC driver package, leave that alone.
now boot your phone into the bootloader, fastboot USB mode and plug it into the computer, leave it alone to detect your phone ands install the fastboot drivers.
your going to need to download 2 files: your RUU zip and HTC's fastboot to flash it: https://www.androidfilehost.com/?fid=95916177934554130 rename this file to RUU for ease, and also download this: https://www.androidfilehost.com/?fid=96042739161891970, put both files on your computer in the same folder as your current adb and fastboot files, then just issue these commands, this will wipe your entire phone by the way, but I think you've probably already done that anyway.
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
your phone should now say tampered and relocked at the top
fastboot oem rebootRUU black screen silver HTC logo
htc_fastboot flash zip RUU.zip notice your now using the HTC fastboot, the normal one wont work for this flash
it take about 10 mins to flash, at the end make sure it says successful and OKAY, final commands are:
fastboot reboot-bootloader
fastboot reboot
phone should now boot, it will be a first time boot so may take a while
Seanie280672 said:
oops, that's the wrong RUU for you phone, I would also hazard a guess that the guru reset is just too old, the key for you is in the numbers, your current os is 7.19.401.2 its the 401 part which matters the most, the 7 part is also android revision, as your on 7, I would say 2 is very too old for your phone., the RUU you tried to use if you look at the numbers is android revision 4 developer edition 1540 (4.19.1540.9) hope that explains that a little for you.
The red exclamation mark is stock recovery, when you see that symbol, press volume up and power a few times and you'll get the menu.
well the first thing you need to do is get your drivers sorted, so uninstall HTC sync manager and the drivers now restart your computer, then re-download it, install it, and then go into add/remove programs and remove HTC sync, just above it you will see HTC driver package, leave that alone.
now boot your phone into the bootloader, fastboot USB mode and plug it into the computer, leave it alone to detect your phone ands install the fastboot drivers.
your going to need to download 2 files: your RUU zip and HTC's fastboot to flash it: https://www.androidfilehost.com/?fid=95916177934554130 rename this file to RUU for ease, and also download this: https://www.androidfilehost.com/?fid=96042739161891970, put both files on your computer in the same folder as your current adb and fastboot files, then just issue these commands, this will wipe your entire phone by the way, but I think you've probably already done that anyway.
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
your phone should now say tampered and relocked at the top
fastboot oem rebootRUU black screen silver HTC logo
htc_fastboot flash zip RUU.zip notice your now using the HTC fastboot, the normal one wont work for this flash
it take about 10 mins to flash, at the end make sure it says successful and OKAY, final commands are:
fastboot reboot-bootloader
fastboot reboot
phone should now boot, it will be a first time boot so may take a while
Click to expand...
Click to collapse
Thank you very much for your help Seanie. I followed all the steps as you described but I still get "waiting for device" message in the command prompt. How can I overcome this? Is it supposed to be a problem with the drivers?
skypse said:
Thank you very much for your help Seanie. I followed all the steps as you described but I still get "waiting for device" message in the command prompt. How can I overcome this? Is it supposed to be a problem with the drivers?
Click to expand...
Click to collapse
yes it's a driver issue
see nkk71 guide post 2 faq 2 / to get fastboot working with your phone
http://forum.xda-developers.com/showthread.php?t=2541082
Thank you for your reply! I downloaded the drivers from the guide and it works. I'm on step 5 now and waiting for flash to end.
EDIT: So everything worked perfectly and I finally was able to turn my phone on again. Thank you very much for your assistance!
Bad news is that the sound problem is still here. I really have no idea on what would be the problem. Maybe it has something to do with the hardware and the whole Lollipop upgrade was an unfortunate moment. I guess I'll start another thread in the following days to see if anyone can help with that.
Hi guys,
I am trying to help out a mate and unfortunately dont have much experience with HTC's.
This is where i stand...phone wont be recognized in normal boot, nor in TWRP, so adb is not working at all. FASTBOOT works.
i have been circling around with locking and unlocking the bootloader to try out all the methods of updating the system, RUU fails with error 155. when unlocking, supercid fails with some java error.
To get S-OFF, i definitely need adb to load the "much talked for" file, but that is impossible right now.
RUU normal way fails as i said above, so does FUU with rom.zip (found away to get it out of exe, so it is untouched) as soon as it "updates signatures" it'll fail, I even use the fastboot command with the renamed file firmware.zip ends up saying it cannot verify partition ...adding zip after flash command says file is out of size
I am on 4.20.651.10, and trying to get the latest package, and am out of ideas. I found out the hard way that if i lock back the phone, it wont boot to TWRP and nor on a modified system.
I am really not sure what to do, having adb on would've spared me a lot of trouble. Friend says the USB port has been changed twice, it is so odd to have fastboot and not even a single refresh in Device Manager when i plug the damn phone on...
There are more replies to question threads outside the Help section then in here...
Anyway, i lost fastboot too, and no idea why. tried in two pc's, one of them with 3 different os's, tried two macs, tried even an OTG cable with my other android phone, nothing.
I cant even relock the phone so i can update through the RUU ZIP in the sdcard, but that's a scratched off solution if no USB connection is delivered.
I even tried the S-Off unlocking file on /data/local/tmp, but it doesnt seem to execute from TWRP terminal, and ofc it wont through a booted system either...
I managed to install a custom rom since i have no OS, and tried the "AndroidHtcSync.apk" solution to no avail
i seriously hope anyone has the will to help me...
EDIT: port is definitely fine, as the phone charges from the charger, and fastboot shows "fastboot ac".
EDIT2: fastboot is back... renamed the zip in sdcard, now it fails flashing there too with "Device halted due to large image update fail"