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!!
Related
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
I am trying to run an RUU to bring back to stock. When I run the RUU it fails and everything that I have read says that for the RUU to be successful your bootloader must be locked. So I do my fastboot oem lock and the re-lock succeeds but now can only boot into the bootloader. I cant get the os to boot so I cant run the RUU. If I then go through the unlock procedure again my phone boots with no problem. I just cant get it to boot while locked. Any Ideas would be greatly appreciated.
Also I am S-On running stock w/goodies 2.28
How to Relock the HTC EVO 4G LTE Bootloader
http://www.youtube.com/watch?v=5yS7yy4XVA4
How to Unroot / Unbrick the HTC EVO 4G LTE
http://www.youtube.com/watch?v=NChdb...B1EB8DBE7A5B59
bigdaddy619 said:
How to Relock the HTC EVO 4G LTE Bootloader
http://www.youtube.com/watch?v=5yS7yy4XVA4
How to Unroot / Unbrick the HTC EVO 4G LTE
http://www.youtube.com/watch?v=NChdb...B1EB8DBE7A5B59
Click to expand...
Click to collapse
That is what I have already done but when I run the fastboot oem lock as it says in the video my phone reboots but wont boot into the OS just goes back into the bootloader.
Also I dont know if this means anything or not but when I am at the bootloader at the top it says "tampered" "relocked" and also "security warning"
tyrob56 said:
Also I dont know if this means anything or not but when I am at the bootloader at the top it says "tampered" "relocked" and also "security warning"
Click to expand...
Click to collapse
I don't think the phone will boot with anything but the stock rom after an oem lock. It should boot again after running the ruu
Sent from my EVO using Tapatalk 2
tyrob56 said:
Also I dont know if this means anything or not but when I am at the bootloader at the top it says "tampered" "relocked" and also "security warning"
Click to expand...
Click to collapse
I think it says tampered because you still have root access
Sent from my MB855 using xda app-developers app
Flash the stock ruu. It will boot and tampered message will be gone
Sent from my Cm10 powered Evo Lte!!
After you relock the bootloader like you said you did, get back into bootloader, set to fastboot, connect/or keep phone connected to computer after locking, and it should say "fastboot usb" in red when you go into fastboot selection. From there run RUU on your computer, and you should be all set. Hope that helps.
Sent from my EVO using xda app-developers app
kaos420 said:
Flash the stock ruu. It will boot and tampered message will be gone
Sent from my Cm10 powered Evo Lte!!
Click to expand...
Click to collapse
When you say flash the Stock ruu I think that is where my confusion lies. The only ruus I have been able to find are an executable that is run from my PC. Also if I am able to find the ruu to flash is it a .zip or a .img and is it flashed thru fastboot or recovery?
ok thank you everyone. I was able to get the ruu to run from fastboot. I thought I had tried that before and the ruu wasnt able to detect the phone but as of now it seems that I am good.
Again thank you guys
Okay so I used the SuperCID apk and it converted my CID to a bunch of Twos and then I used the HTC unlock method to unlock my phone. But after I select root my phone I'll void the warranty it boots into Android mode where I reboot it into recovery it says locked. It doesn't say relocked or unlocked it simply says locked like it never unlocked my phone even though it had just said it unlocked it maybe 2 minutes prior. Has anyone else had this problem? How do I fix it?
Can you try to explain what's happening a little bit better.
Sent from my HTC6435LVW using xda app-developers app
Did you flash the unlock_code.bin file?
Bigandrewgold said:
Can you try to explain what's happening a little bit better.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Okay so I ran the SuperCID from http://forum.xda-developers.com/showthread.php?p=36976137 and it changed my CID to 22222222.
I then do "fastboot flash unlocktoken Unlock_code.bin" that I got from HTC and then select Yes on the prompt.
It then boots into normal android mode and then it goes through the normal setup. I then enable the debuging mode and then do
"adb reboot-bootloader" it then reboots into bootloder locked.
Balask said:
Okay so I ran the SuperCID from http://forum.xda-developers.com/showthread.php?p=36976137 and it changed my CID to 22222222.
I then do "fastboot flash unlocktoken Unlock_code.bin" that I got from HTC and then select Yes on the prompt.
It then boots into normal android mode and then it goes through the normal setup. I then enable the debuging mode and then do
"adb reboot-bootloader" it then reboots into bootloder locked.
Click to expand...
Click to collapse
Is there a way for you to take a video of when you send the unlock token and click yes on your phone. Because I'm really not sure what's going wrong.
Sent from my HTC6435LVW using xda app-developers app
Balask said:
Okay so I ran the SuperCID from http://forum.xda-developers.com/showthread.php?p=36976137 and it changed my CID to 22222222.
I then do "fastboot flash unlocktoken Unlock_code.bin" that I got from HTC and then select Yes on the prompt.
It then boots into normal android mode and then it goes through the normal setup. I then enable the debuging mode and then do
"adb reboot-bootloader" it then reboots into bootloder locked.
Click to expand...
Click to collapse
Keep flashing it until it unlocks sometimes it takes 20 times
.torrented said:
Keep flashing it until it unlocks sometimes it takes 20 times
Click to expand...
Click to collapse
I've only heard of it taking multiple times if your trying to re unlock, not on the first unlock.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
I've only heard of it taking multiple times if your trying to re unlock, not on the first unlock.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
sccrgoalie1 said:
Worked for me as well but it seriously took 15 to 20 tries to reunlock. Thanks!
Click to expand...
Click to collapse
Just keep trying... some people get it first try other dont...
If you do a factory reset first from bootloader then unlock, it will work first time every time.......it'll wipe your SD tho. Once you have a custom recovery flashed don't use that method anymore tho
Sent from my SPH-L710 using Tapatalk 2
For me. I had to turn phone completely off. Then boot into HBOOT/Fastboot in order for the unlock to work. Make sure fast boot is unchecked in the power options before turning off.
In about three minutes this video should show a HTC DNA not unlocking even with SuperCID change and the correct file to unlock the phone with.
Code:
youtu.be/6P7mQ0rP-ms
Just keep at the command. Keep redoing it until it sticks. Took me 5 tries. Now I'm S-OFF & unlocked...with the OTA. Just keep doing it. It'll stick...eventually.
AW: [Q] Hboot won't unlock
Flyhalf205 said:
For me. I had to turn phone completely off. Then boot into HBOOT/Fastboot in order for the unlock to work. Make sure fast boot is unchecked in the power options before turning off.
Click to expand...
Click to collapse
Yep,same Problem,Power Completely off and it works for me.
Sent from my HTC6435LVW using xda app-developers app
Thanks a lot turning it completely off actually did the trick. Now my next question is since I had to put on a custom recovery to install Super User now do I install a stock recovery so that it can do over the air updates now that I have S-Off. If it updates my stock rom with OTA will I have to flash a custom rom to root it again or will SU still be there because its S-Off?
Balask said:
Thanks a lot turning it completely off actually did the trick. Now my next question is since I had to put on a custom recovery to install Super User now do I install a stock recovery so that it can do over the air updates now that I have S-Off. If it updates my stock rom with OTA will I have to flash a custom rom to root it again or will SU still be there because its S-Off?
Click to expand...
Click to collapse
I'm not sure why'd you want to take the ota, but yes, you'll need the stock recovery if you want to take it. Then you'll need to install a custom recovery and install a superuser package.
Having s off has nothing to do with superuser or the ota.
Sent from my GT-P7510 using xda app-developers app
Hello, quick background, My sisters bf tried to root her phone. He failed. I received it and attempted to fix, here is the thread where I almost succeeded: http://forum.xda-developers.com/showthread.php?p=38442511
only problem now is when I went to install the RUU my computer reboot and left the phone with the HTC in silver and on the 4 corners,4 triangles with exclamation marks inside. I cant boot back to bootloader, when I try to run the RUU from the terminal it says error cant run RUU. running linux 12.04.
Hmm I could say many things suggestions etc but they would all be untested. Best bet, take it in telling em you where updating the phone via ruu pc rebooted while ruu was being run.
Sent from my EVO using xda app-developers app
Sinistertensai said:
Hmm I could say many things suggestions etc but they would all be untested. Best bet, take it in telling em you where updating the phone via ruu pc rebooted while ruu was being run.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Won't Sprint see that the phone was tampered with? everyonce in a while when I unplug the phone from the comp it shows the bootloader screen with just RUU in orange but at the top it says tampered and relocked.
When it shows the bootloader, as you said, can't you volume button down to select recovery? If your recovery got wiped during the messed up RUU flash, you might really be hosed. Have you tried rerunning RUU from a windows device? Sinister knows a lot about android/Linux, glad he posted, but if he suggests it's hosed, it probably is. That said, it's pretty hard to completely hose it. One of your other partitions may have got borked, in which case I'd check the jewel Evita brick toolkit thread here in a sticky or at one X in a sticky, I forget.
From my Evo LTE, yup.
BusstopBill44 said:
Won't Sprint see that the phone was tampered with? everyonce in a while when I unplug the phone from the comp it shows the bootloader screen with just RUU in orange but at the top it says tampered and relocked.
Click to expand...
Click to collapse
Can you get into hboot? If so remove your sd add to the root of it an recovery image. That is if you can't hboot<recovery. If that don't work use regamods s-on and his other thing to hide the rl tampered thing in hboot. Provide more details bro. Its hard to guess.
Sent from my EVO using xda app-developers app
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
kennypow3rs said:
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
Click to expand...
Click to collapse
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
to my knowledge any htc device no longer show "locked" after you unlocked it the first time..it will always show relocked when locked again..
Nick281051 said:
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
kennypow3rs said:
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
Click to expand...
Click to collapse
No problem lol good luck
Sent from my HTC One using Tapatalk
Nick281051 said:
No problem lol good luck
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ok now I have some problems. I unlocked again, s-off'd and then tried to "lock" and s-on again. Something went wrong and now I have a message in hboot that says "security warning" and tampared over the words "locked". I doesnt boot to the rom again just goes to recovery im guessing with the phone and the red triangle. lol Pain in the butt.
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Nick281051 said:
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Theres no rom on the phone now lol.Gotta figure this out! Thanks for your help dude!
Run a ruu that will fix it tampered will be gone too
Sent from my HTC One using Tapatalk
So right now it's unlocked with tampered above an s-off. Is it wise to lock bootloader first before I run ruu? Which order should I go? I know s-on is last for sure...
Sent from my HTC One using Tapatalk
For anyone that's searching for this exact issue ill share what i did to get my phone completely back to stock. I did search the forum but the info was all over the place and in my opinion it was as clear as "I" needed it to be hence me creating a thread for something so simple. Ok as follows here is what I did step by step.
First I had to make sure I installed HTC sync of course. At the moment my firmware was 3.57 and I downloaded the 3.17 RUU.exe from HTC.com
Your firmware *HBOOT* and the RUU you download have to match or you will get errors. Well, least I did.
Make sure you download some type of toolkit it would make life a lot easier. I used this one it worked like a charm!
At the moment, my phone is bootloader unlocked and s-off fyi.
Next, Use the tool to "lock" your bootloader first not "re-lock" just "lock". If you're having issues push revone again and follow commands on toolbox.
Now, check hboot to see if it shows "locked" if it has tampered above locked that's ok the RUU will take care of that.
Run, the RUU, make sure usb debugging on and htc sync already installed. Let it run.
After its done, start up phone again, turn off fastboot under "power" and turn usb debugging on again.
Start up toolkit, look to the right and it will say "s-on" device. You can only s-on after you've ran the RUU and are on stock hboot and rom.
Check Hboot again and it should read "Locked" and now "s-on".
Phone now ready to send back for warranty or etc.
Hope this helps anyone that searches. I found a few thread via google and they helped out a bunch.