Real quick back story: Originally this device was being rooted to try to perform some data recovery after a factory reset. Everything went fine to unlock boot loader and root phone, TWRP was used as a recovery manager, but after installing SuperSU it wouldn't load from the booted device (error about binaries missing when clicking its icon). So a newer SuperSU zip was found and installed, and then the phone bricked on reboot. Just would freeze at the HTC logo with white background.
Fast forward to no longer needing the data recovery, just want to restore back to working condition. The boot loader was relocked and the latest RUU package from HTC was downloaded for AT&T build. Booting to the boot loader and setting it to fastboot USB, everything works fine running RUU (tells me current OS version and what it will flash to, etc) until it gets to the point where it says it needs to reboot to the bootloader on the RUU software (even though that is where I am initiating RUU flash from in the first place). The phone reboots to a black screen with HTC logo, and then the RUU software gets error 171 that it cannot communicate with the device. When RUU gets an error, there is no retry, only exit and start again. I read on another post someone said don't worry if this happens, just hit exit, run RUU again and it will pick up and continue to flash. However when you click exit on RUU, the phone reboots back to the white screen with HTC logo and hangs there.
Does anyone have any advice to get this device back to a stock android install? Thanks. If there is a better sub forum for this question, please let me know and I will post there.
Related
I installed Modaco switch Beta 8 on my HTC One after rooting it and installing TWRP custom recovery. I can't post a link in this because I haven't posted on the site enough. If you just google MoDaCo swtich, the information will show up. Sorry for the inconvenience but Switch is actually a very cool rom that gives the best of both worlds.
It was working well and I was not having any problems until I downloaded an app called Haxsync. Haxsync syncs Facebook information into People because stock does not support that like Sense does. I pulled the notification shade down and clicked the app, the phone proceeded to completely shut down. I was in the stock 4.2.2 rom when it cut out. I tried to reboot it and got the "htc quietly brilliant" screen. Then the GPE boot screen came on and once finished the "htc quietly brilliant" came back up and it goes nowhere. I can get into the boot loader and it says "unlocked" and "tampered", S-ON is also there. When I try to get into my TWRP recovery the TWRP splash screen comes up and then it jumps back to the "htc quietly brilliant" screen and it wont go away. When I select factory reset, it brings the TWRP screen again and then goes back to the "htc quietly brilliant".
I tried to unlock the boot loader again but when I tried to push the Unlock_code.bin file to the phone again, the unlock boot loader screen never comes up. I tried to unlock the boot loader again because it would presumably factory reset the phone so that I could reroot it and reinstall the Switch rom and go back the way it was before. Sadly that would not work.
I am on running Mountain Lion on my mac and windows 8 through bootcamp. The HTC One drivers do not work on windows 8 no matter how hard I try and what i do to try to upgrade them. If I need access to a WIndows 7 pc then so be it.
From my research I need to relock the boot loader and then run the RUU thing to factory reset it back to the stock firmware. I can't figure out how to relock it with my mac and the RUU wont won't on mac. I don't know how the "S-ON" works in here.
If my phone has to be completely wiped then so be it and I will work back from scratch. As long as I can get my phone back I will be a happy camper.
Suggestions and help are greatly appreciated.
Thank you
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted
Hi all,
This is my sons phone which he doesn't use as phone - just for games.
Last night he dropped it and it froze, after removing battery it started powering and boot-looping on white htc logo screen.
I powered it with vol down and went on boot-loader and I thought I just restore it via recovery to a state I made him few months back, but failed to go to recovery, again on white screen loop.
I tried installing shipped ruu and after few fails I did it, but again restarts on white screen.
I can connect it to pc and all, running fastboot commands usualy comes with "remote not allowed"
I was sure that I did unlock bootloader for this phone but it says locked, so I am not sure ( having 4 htc phones in same house hard to know what I did to which )
This phone prior to drop had:
4EXT_Recovery_Touch_v1.0.0.5_RC7
S-OFF
not sure on unlocked bootloader
and
Cool-ICS-v17-EvoC
any ideas appreciated
Thank you
PS
I tried to go to htc page and unlock boot-loader, but numbers i paste are not recognized ( I did this many times so its not my error in copy paste)
I guess I cant edit my post.
I managed to unlock bootloader
I installed "Cool-ICS-v17-EvoC" rom via sd card as PG86IMG.zip as I can't load into recovery
and it reboots on white htc logo again
help
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Brian706 said:
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Click to expand...
Click to collapse
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
cipher101 said:
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
Click to expand...
Click to collapse
Apologies, I went and re-read the op and now I see that.
I think you are having trouble with the fastboot commands because of the locked bootloader like you said. You could also use the juopunutbear patched hboot since you are s-off, it will give you access to the extra fastboot commands regardless of locked/unlocked state. It can be flashed as a PG86IMG.zip via the bootloader.
If you use the patched hboot you could attempt to boot recovery into memory by using fastboot boot recovery.img
Because you are s-off, you can also flash a recovery via the bootloader as a PG86IMG.zip. If you want to try, here is 4ext recovery:
https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip
Obviously just Rename the file and remove everything prior to PG86IMG.zip.
I have a feeling though that since you successfully ran the ruu and it still won't boot, that no amount of software changes will fix the issue. I'm not sure if the motherboard will fix the issue or not buy that's a pretty cheap fix to try
Thanks for help and advice man,
I bought him a working used evo 3d from ebay, it was under $30 so I'll keep this one for parts I guess.
Thanks again
2 days ago my phone went from running perfectly to turning off and getting stuck in a boot loop, I'm assuming it had something to do with supersu updating because i noticed a popup about the binaries needing updating before the crash. I couldn't load recovery (would show team win logo then reboot) but i could load safe mode, i tried downgrading to lower versions of su ( i tried 2.13, 1.8 and 2.01) but that didn't work my phone would boot normally, i could access it for about a minute then it would reboot and do it all over again. i had originally followed this guide (URL at the bottom as i can't post links) so last night i attempted to just re do it all following the same guide. I got the recovery mode to boot and wiped the cache but i still had the same issue where i could access my phone for a minute before crashing. Now when i try to enter recovery it shows the htc logo and immediately reopens boot loader on the fast boot option. I rurally don't want to go out and buy a new phone so any help is appreciated. My current PC access is fairly limited but i can use one if i have to.
Also when i launched safe mode i noticed id get an error report after a few minutes, not sure if thats relevant but it never showed up when i booted normally.
android forums(.)com/desire-601-all-things-root/817068-root-unlock-bootlader-install-recovery-guide-htc-desire-601-zara.html
(remove the brackets)
*edit* i have tried searching for similar threads but i think i will have a better result if the replies are directed towards me directly
Thats weird. Ive never seen this issue before
Try this steps : http://forum.xda-developers.com/and...1-zaraul-s-t2893035/post56365857#post56365857
It works for me.
RUU stuck on "Sending ... " at 14% progress while trying to restore to stock
I'm running the Skydragon 9.0 HTC One M8 ROM, and I'm trying to restore my M8 to stock. I locked the bootloader as I was told on another thread before running the RUU, and I made sure I had the CID as CWS__001 before starting, and I ran the RUU tool.
However, after doing it's usual thing, it gets stuck at 14% while saying "Sending... Updating the ROM image on your android phone". What did I do wrong? Is there another way to return this to stock? Also, I ran this exact RUU once before installing the Skydragon rom, so everything but the kernel should be intact.
Did you try it only once? If so, do it again. Sometimes it just gets stuck.
If this happens again and again, it may be a different matter. But it sounds like you ran the RUU successfully on this same computer before?
Late to the party, but ran into the same issue. Disconnect the USB cable from the m8. The HTC logo on black will disappear, and the white bootloader screen will pop up showing "RUU". The RUU app in Windows will pop into recovery mode. Click through the "next" buttons, and when instructed (step 4), plug the USB cable back into the m8. The RUU app will restart the dialogues to flash again. It should get further along and work on the 2nd attempt.