I know this is not a new problem and I have tried to glean information from other threads and have been trying for 2 days straight to solve this issue to no avail. The problem occurred when installing the android 4.0 ICS update. I left the phone to install and when i came back to it it was stuck on the white htc screen. i have attempted flashing a new RUU but this has done nothing, possibly because i have no idea what im doing and have only tried my best to do what i have found on forums. How can i solve this???
by the way, unrooted, s-on, the phone and OS are factory in all aspects as far as i know
Make sure that your bootloader is locked to flash an RUU
Sent from my HTC Rezound using Tapatalk 2
wlmeng11 said:
Make sure that your bootloader is locked to flash an RUU
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse
how do i know if it is unlocked and if so how would i lock it?
On the bootloader menu it will say locked or unlocked.
Command to lock is
fastboot oem lock
Sent from my HTC Rezound using Tapatalk 2
wlmeng11 said:
On the bootloader menu it will say locked or unlocked.
Command to lock is
fastboot oem lock
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse
and how do i enter this command?
Related
Ran an ruu today to get back to stock and the ruu failed now I'm stuck at the HTC and four triangles in the corner screen... Can anyone help?
Sent from my K1 using Tapatalk 2
thispaininmyhead said:
Ran an ruu today to get back to stock and the ruu failed now I'm stuck at the HTC and four triangles in the corner screen... Can anyone help?
Sent from my K1 using Tapatalk 2
Click to expand...
Click to collapse
what hboot did u have and what ruu did u flash?
1.12.0000 tried both the 1.12 and the 1.13(those being what base the ruu was)
Sent from my K1 using Tapatalk 2
If you unlocked the boot loader you will have to relock first
How am I supposed to do that if the phone won't boot
Sent from my K1 using Tapatalk 2
In fastboot you type fastboot oem lock
But my bootloader doesn't fully load anymore because of the ruu... Now I get this orange ruu text where my bootloader options used to be.... Is fast boot still enabled in this screen? And btw I'm s-off not HTC unlocked
Sent from my K1 using Tapatalk 2
It shouldnt be a problem then, usually that error pops up when someone son forgets to relock
Well something is a problem cause nothing is working... I get a "fail-uz", next to system when running an ruu whether using the exe or bootloader zip method
Sent from my K1 using Tapatalk 2
I just purchased an evo lte off Craigslist and I would like to put it back to stock. When I try to enable wifi it says there is an error. In the bootloader it says tampered, unlocked, s on, hboot 1.19.0000 also it has twrp recovery.
What steps do I need to take to get back to completely stock as it would be from the store. Thanks
Sent from my EVO using Tapatalk 2
Here you go!
oldpreowner said:
I just purchased an evo lte off Craigslist and I would like to put it back to stock. When I try to enable wifi it says there is an error. In the bootloader it says tampered, unlocked, s on, hboot 1.19.0000 also it has twrp recovery.
What steps do I need to take to get back to completely stock as it would be from the store. Thanks
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
If I'm correct the bootloader will always say tampered unlocked unless you use the tool to rename it...look in original development section...its by Regaw something. You can run the RUU but all the info will be in original development on returning to stock
Sent from my EVO using Tapatalk 2
The tool to edit hboot is by regaw_lienad, but it will only work on s-off hboot. You are s-on. Tampered means it's rooted. If you want unrooted stock out of the box, need to run 1.19 RUU. Check the stickies.
hurled from my AOKP'd Evo LTE. Enjoy.
scottspa74 said:
The tool to edit hboot is by regaw_lienad, but it will only work on s-off hboot. You are s-on. Tampered means it's rooted. If you want unrooted stock out of the box, need to run 1.19 RUU. Check the stickies.
hurled from my AOKP'd Evo LTE. Enjoy.
Click to expand...
Click to collapse
Do I have to lock the bootloader before running the ruu?
Sent from my EVO using Tapatalk 2
You do have to relock the bootloader through fastboot. Fastboot OEM lock. Then if it boots up afterwards put back in fastboot to run the RUU. I have done this multiple times with success. Afterwards it will not say tampered, but it will.say relocked instead of locked. But I've sent mine into sprint several times for repair and even got a replacement device
Sent from my EVO using Tapatalk 2
jscoggs81 said:
You do have to relock the bootloader through fastboot. Fastboot OEM lock. Then if it boots up afterwards put back in fastboot to run the RUU. I have done this multiple times with success. Afterwards it will not say tampered, but it will.say relocked instead of locked. But I've sent mine into sprint several times for repair and even got a replacement device
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I'm a Samsung guy but to stop it saying 'relocked' could you not rewrite that ,before you lock it ? Not changing the command, just the writing it puts up ?
Sent from the man in Your attic.....
jscoggs81 said:
You do have to relock the bootloader through fastboot. Fastboot OEM lock. Then if it boots up afterwards put back in fastboot to run the RUU. I have done this multiple times with success. Afterwards it will not say tampered, but it will.say relocked instead of locked. But I've sent mine into sprint several times for repair and even got a replacement device
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
After I re locked the bootloader I had a tough time getting the ruu to run. I ended up having to hook the phone up to the computer in the fast boot screen. The ruu finally ran successfully and I'm now completely back to stock. Thanks for the help!
Sent from my EVO using Tapatalk 2
Tried running an ruu to take my phone into sprint and the ruu failed somewhere along the way and now I'm stuck with the HTC black screen with the 4 triangles... can't get back to the boot loader at all that I know of... any help or direction would be appreciated... willing to donate to the person who helps get it running again...
Sent from my Crespo4G using Tapatalk 2
What ROM were you on when you tried to RUU, and what RUU did you try to run?
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
What ROM were you on when you tried to RUU, and what RUU did you try to run?
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
I was running cm10 and it was a 2.13 firmware and lazy panda s-off
Sent from my Crespo4G using Tapatalk 2
Sounds like you brick it.
Just take it to Sprint and tell them it was doing an OTA System Update and it rebooted now it's doing this. They will write it off as a hardware failure and send u a free replacement.
I'm pretty sure it's bricked if it fails when doing the RUU process.
Sent from my EVO using Tapatalk 2
Had a similar situation when I screwed something up myself. If you're able to get I to bootloader still (try holding power button down til bottom lights blink and phone shuts off, then holding volume down and power combo gets you into bootloader which don't know if you've tried or not) set it to fastboot, connect to your computer so it says "fastboot usb" and run command (i believe its "fastboot lock oem_token" or something like that) to relock your bootloader and then keep it connected and try to run the ruu on your computer....hope that helps. Its at least worth a try....
Sent from my EVO using xda app-developers app
onefasttreopro said:
Had a similar situation when I screwed something up myself. If you're able to get I to bootloader still (try holding power button down til bottom lights blink and phone shuts off, then holding volume down and power combo gets you into bootloader which don't know if you've tried or not) set it to fastboot, connect to your computer so it says "fastboot usb" and run command (i believe its "fastboot lock oem_token" or something like that) to relock your bootloader and then keep it connected and try to run the ruu on your computer....hope that helps. Its at least worth a try....
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'm lazy panda s-off not htcdev unlocked
Sent from my Nexus S 4G using Tapatalk 2
Did you re-lock the bootloader prior to trying to run the RUU? You have to re-lock the bootloader to run a RUU, as I understand it. Also, a custom recovery will prevent the RUU from working.
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
Did you re-lock the bootloader prior to trying to run the RUU? You have to re-lock the bootloader to run a RUU, as I understand it. Also, a custom recovery will prevent the RUU from working.
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
No, you can still do a RUU with a custom recovery. The bootloader just has to be locked. None of this process takes place in recovery, it's all in the bootloader. Plug your phone in and try typing in "adb reboot bootloader" and see what happens. Also you have to relock the bootloader before you run a ruu. To do that you would have to be in fastboot and type in "fastboot oem lock" and that will lock the bootloader.
-Cupper- said:
No, you can still do a RUU with a custom recovery. The bootloader just has to be locked. None of this process takes place in recovery, it's all in the bootloader. Plug your phone in and try typing in "adb reboot bootloader" and see what happens. Also you have to relock the bootloader before you run a ruu. To do that you would have to be in fastboot and type in "fastboot oem lock" and that will lock the bootloader.
Click to expand...
Click to collapse
My bad. I thought I remembered reading in one of the countless threads on here that you couldn't be on a custom recovery. Makes sense, though.
Sent using my HTC EVO LTE and a magic wand
Actually, lazy panda uses HTC unlock to unlock the bootloader, and then runs an exploit to achieve s-off... You still have to re-lock in order to run an RUU...
Sent from my EVO using xda app-developers app
jthein1989 said:
Actually, lazy panda uses HTC unlock to unlock the bootloader, and then runs an exploit to achieve s-off... You still have to re-lock in order to run an RUU...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info... Good to know... Got sprint to comp me a new phone though...
Sent from my Nexus S 4G using Tapatalk 2
thispaininmyhead said:
Tried running an ruu to take my phone into sprint and the ruu failed somewhere along the way and now I'm stuck with the HTC black screen with the 4 triangles... can't get back to the boot loader at all that I know of... any help or direction would be appreciated... willing to donate to the person who helps get it running again...
Sent from my Crespo4G using Tapatalk 2
Click to expand...
Click to collapse
If you still have power and any display then things are still ok. In fact I rooted my wife's LTE just a couple weeks ago and it ended up shut off, no power, nothing would do anything BRICK... and I followed this guide and I was able to not only get it to turn back on but STILL achieved root with S - off!!!!
I know it's supposed to only be for when stuck in QUALCOMM DIAG but hey it might still help.
http://unlimited.io/lteunbricker.htm
Before I went to that extreme though I would try first holding the power button down for a while. I have found it to be a bit easier to know things are going as they should when I keep it plugged into my computer or just plugged in. That way after you've held the power button down long enough you will see the screen go black, and the red charging light will come on.... keep holding the VOL down button and let go of the power at that point. Then I just count to three, then I start pushing the power down and holding for 1 sec and then let go and push right back down on it and repeat until I am in BOOTLOADER.
I would think that basically if you follow what Mac_Gyver lays out really well in this thread:
http://forum.xda-developers.com/showthread.php?t=1932914
I think you won't have any problems... I hope things work out for you, and I don't know it all but I will help all I can!!
Hey guys I had to send my HTC One back to ATT. So I stupidly tried to get it back to stock, so I first flashed an Odex-ed Stock Rooted Rom, then flashed stock recovery in fastboot, then locked the bootloader and am now trying to run the RUU. And it doesnt seem to be working..what do I do? I just keep booting into the bootloader straight. Im so lost.
So your bootloader is locked, you start the ruu and what happens?
I had a similar issue. For some resason all of my laptops had issues with drivers. If you go in device manager in windows, check to see if you see exclamation mark on my HTC.
I tried different drivers, sync app from HTC and even fresh virtual box environments on MacBook to no avail. It always shows that yellow exclamation when in bootloader.
Anyways, didn't mean to hijack your thread but just trying to see what's in your device manager. Try hansoon HTC one app?
Sent from my HTC One using xda app-developers app
it either says "Phone not found" or the RUU wont even open .. will say issues with drivers
Damn, I hope you get it figured out. I wish I could help. I know I better keep my htc one stock for the time being. This could of happened to me.
Sent from my HTC One using Tapatalk 2
Packer2058 said:
Hey guys I had to send my HTC One back to ATT. So I stupidly tried to get it back to stock, so I first flashed an Odex-ed Stock Rooted Rom, then flashed stock recovery in fastboot, then locked the bootloader and am now trying to run the RUU. And it doesnt seem to be working..what do I do? I just keep booting into the bootloader straight. Im so lost.
Click to expand...
Click to collapse
Lol u can't just lock ur boot loader u have to run the firmware first and u must unroot all he had to do is unlock bootloader again and it would of booted
Sent from my HTC Butterfly using xda premium
Packer2058 said:
it either says "Phone not found" or the RUU wont even open .. will say issues with drivers
Click to expand...
Click to collapse
Reinstall the drivers
daorderdillon said:
Lol u can't just lock ur boot loader u have to run the firmware first and u must unroot all he had to do is unlock bootloader again and it would of booted
Sent from my HTC Butterfly using xda premium
Click to expand...
Click to collapse
yea i unlocked bootloader and it booted...what to do now
Packer2058 said:
yea i unlocked bootloader and it booted...what to do now
Click to expand...
Click to collapse
Flash a Rom like android revolutionary
Sent from my HTC Butterfly using xda premium
i currently have the us at&t htc one x plus
i have trwp recovery and bootloader unlocked
all i want to know is do i have to reflash the stock recovery and lock the bootloader
before i can run the new update
denial4242 said:
i currently have the us at&t htc one x plus
i have trwp recovery and bootloader unlocked
all i want to know is do i have to reflash the stock recovery and lock the bootloader
before i can run the new update
Click to expand...
Click to collapse
On my ATT all I did was relock bootloader then ran the RUU while in fastboot.
Sent from my One X+ using Tapatalk
re locking bootloader
thank you for the quick respones my head was hurting from all the info ive been reading
ive had some bad expeience with fast boot is there a step by step on how to re lock the bootloader using windroid htc toolkit
and how install the 4.2 using fastboot
denial4242 said:
thank you for the quick respones my head was hurting from all the info ive been reading
ive had some bad expeience with fast boot is there a step by step on how to re lock the bootloader using windroid htc toolkit
and how install the 4.2 using fastboot
Click to expand...
Click to collapse
No idea I don't use it....and you double click the exe file, it will reboot the device Into RUU mode automagically
Sent from my One X+ using Tapatalk
thank you very much