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
Related
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!!
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
Unsure what happened. Phone has been rebooting and overheating for days so I went to RUU it and after I relocked the bootloader my phone decided not to go past bootloader anymore. When I try RUU I get Error 140 Bootloader Version Error. My bootloader has a Security Warning at the top which was not there before. I would like to RUU and get S-OFF so I can take the phone in without issue but am having no luck.
Some more info would be useful. What Hboot & baseband are you currently on, and what RUU did you try to run?
Sent from my EVO using xda premium
FinZ28 said:
Some more info would be useful. What Hboot & baseband are you currently on, and what RUU did you try to run?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The 3.15 RUU and HBoot 2.09 I dunno basebands. If there is a working 3.16 RUU that would be helpful but there isn't...
Vysse said:
The 3.15 RUU and HBoot 2.09 I dunno basebands. If there is a working 3.16 RUU that would be helpful but there isn't...
Click to expand...
Click to collapse
Baseband is your radio version, and you can check it in the bootloader.
Sent from my EVO using xda premium
FinZ28 said:
Baseband is your radio version, and you can check it in the bootloader.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
1.12
Vysse said:
1.12
Click to expand...
Click to collapse
The radio version is directly below the Hboot version. That looks like the Hboot version. Boot into the bootloader and list the info displayed in the top left corner of the screen, all the way down to the radio version.
You relocked so you'll need to unlock again. You may even need to install a recovery again. What ROM/kernel combo were you on? If you were on a custom kernel, I would try a different one or stick with stock. Some kernels don't play well with certain phones, especially if you're overclocking or changing the voltage any. For now, try unlocking and getting the phone up and running again.
Also, gaining S-off is highly recommended
Sent from my EVO using xda premium
FinZ28 said:
The radio version is directly below the Hboot version. That looks like the Hboot version. Boot into the bootloader and list the info displayed in the top left corner of the screen, all the way down to the radio version.
You relocked so you'll need to unlock again. You may even need to install a recovery again. What ROM/kernel combo were you on? If you were on a custom kernel, I would try a different one or stick with stock. Some kernels don't play well with certain phones, especially if you're overclocking or changing the voltage any. For now, try unlocking and getting the phone up and running again.
Also, gaining S-off is highly recommended
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hboot is 2.09 Radio is 1.12 I cannot unlock because it won't write. I cannot seem to do anything. I tried using the Unbricking tool but it does not recognize my device. I think this issue started when I tried to lock after a failed s-off attempt.
What do you mean when you say it won't write?
Also, for your radio, use the last four digits, not the ones at the beginning.
Sent from my EVO using xda premium
FinZ28 said:
What do you mean when you say it won't write?
Also, for your radio, use the last four digits, not the ones at the beginning.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Full Radio is 1.12.11.1210 and when I flash something via fastboot it sends it then has a write error. I have tried flashing RUU's, recovery, my unlock_code all to no avail. I tried using the unbricking tool but linux doesn't seem to see my device (I am new to linux). I appreciate the help btw.
You won't be able to use fastboot commands to push a recovery to your phone while it's relocked. Also, the RUU won't work because you're on a software version higher than the most recent RUU.
Sent from my EVO using xda premium
FinZ28 said:
You won't be able to use fastboot commands to push a recovery to your phone while it's relocked. Also, the RUU won't work because you're on a software version higher than the most recent RUU.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This is where HTC screwed us with no recent ruu... Smh.
The the op... Have you gone through the steps to HTC Dev unlock again? What does it say when you send the unlock token?
Sent from my Evo 3D CDMA using Tapatalk 4 Beta
gunfromsako said:
This is where HTC screwed us with no recent ruu... Smh.
The the op... Have you gone through the steps to HTC Dev unlock again? What does it say when you send the unlock token?
Sent from my Evo 3D CDMA using Tapatalk 4 Beta
Click to expand...
Click to collapse
The unlock token won't write. Nothing will write. If there was a modified RUU that would help. If I could modify my version so the RUU would work that would work... and yeah HTC really screwed us...
Edit: Actually the unlock_code.bin writes but then nothing happens on the phone...
Update: took it to a sprint store and they fixed it. They apparently have 3.16 RUU. Or magic....
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.
Hey all,
I am looking to sell my Evo 4g lte because sprint really messed things up but that is neither here nor there. I would like to return it to stock for ease of selling it. can i do this without having a stock rooted rom and if possible can i run the updates to get the phone current for the next user? IF one of you want the rooted phone pm me i am up for anything.
Phone has MEAN BEAN rom on it and is s-off h boot 1.12.2222 radio 1.12.11.1210
thanks
stubby
stubby1 said:
Hey all,
I am looking to sell my Evo 4g lte because sprint really messed things up but that is neither here nor there. I would like to return it to stock for ease of selling it. can i do this without having a stock rooted rom and if possible can i run the updates to get the phone current for the next user? IF one of you want the rooted phone pm me i am up for anything.
Phone has MEAN BEAN rom on it and is s-off h boot 1.12.2222 radio 1.12.11.1210
thanks
stubby
Click to expand...
Click to collapse
Hit the top link in my sig and go to the section on RUU's. At the bottom of the first post I have links to all applicable RUU's for the EVO LTE. Easiest thing would be to run one of them if you want to get back to stock. If you want to go back to being S-on and stock, use VipeRUU.
Magnum_Enforcer said:
Hit the top link in my sig and go to the section on RUU's. At the bottom of the first post I have links to all applicable RUU's for the EVO LTE. Easiest thing would be to run one of them if you want to get back to stock. If you want to go back to being S-on and stock, use VipeRUU.
Click to expand...
Click to collapse
Thanks Magnum
Using the VipeRUU was supper easy and quick. Back to stock off to sell.:good:
Not a problem. Just remember that the RUU is run from your computer. Connect your phone and PC via USB cable, and once the connection is complete double-click the RUU file to start the installer. You may need to install HTC Sync so that you have the proper drivers installed on your computer. It takes about 10-15 minutes for the RUU to run, so be patient. VipeRUU is a little bit different. When you double-click the file to start the process, it will bring up a menu with options in it for you to choose from. It's pretty straightforward, though.
I've run VipeRUU a few times, but the bootloader stays unlocked. Anyone have any suggestions to get it back to a "Locked" state? I'm S-OFF, HBOOT 2.09.
Sent from my EVO using Tapatalk
CornDogg said:
I've run VipeRUU a few times, but the bootloader stays unlocked. Anyone have any suggestions to get it back to a "Locked" state? I'm S-OFF, HBOOT 2.09.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
fastboot oem lock
Sent from my Nexus 5 using XDA Premium 4 mobile app
That would just make it show "Relocked", though, right?
Sent from my EVO using Tapatalk
Evolution_Freak said:
fastboot oem lock
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe that will work being S-off (I've tried it before just for kicks and it didn't do anything). Even if it did, the bootloader would show the tampered and unlocked warning.