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
First off, I've gone through thread after thread hoping to find an answer, but simply have not.
I rooted my phone back in July and don't remember which method I used. I need to get my phone back to stock for warranty (I have a dead strip on my screen) and before I thought, I used SU to get back to S-On, but now I can't get back to stock.
I've tried to run various RUU's, more specifically regaw's version among others, but I haven't had any success. Every time I run an RUU it says that my phone is not connected to my computer. I've also downloaded the PJ75IMG and tried that method as well, but nothing happens.
Phone: Evo 4g LTE
HBOOT: 1.12.000
ROM: UR/EVO 4G LTE SIX
SilverJaw said:
First off, I've gone through thread after thread hoping to find an answer, but simply have not.
I rooted my phone back in July and don't remember which method I used. I need to get my phone back to stock for warranty (I have a dead strip on my screen) and before I thought, I used SU to get back to S-On, but now I can't get back to stock.
I've tried to run various RUU's, more specifically regaw's version among others, but I haven't had any success. Every time I run an RUU it says that my phone is not connected to my computer. I've also downloaded the PJ75IMG and tried that method as well, but nothing happens.
Phone: Evo 4g LTE
HBOOT: 1.12.000
ROM: UR/EVO 4G LTE SIX
Click to expand...
Click to collapse
Do you have HTC Sync installed? I know that has been a issue for myself, if so uninstall that, and you will need to run the RUU for the Firmware you have. Also I have downloaded mine from this website. http://shipped-roms.com/index.php?category=android&model=Jewel
lloydw82 said:
Do you have HTC Sync installed? I know that has been a issue for myself, if so uninstall that, and you will need to run the RUU for the Firmware you have.
Click to expand...
Click to collapse
I don't have HTC Sync installed. How do you know which RUU will work for which firmware?
Sent from my EVO using xda app-developers app
In your settings under about -> Software Information -> More -> Baseband Version.... That will be the RUU you will Run, i had the same issue with my old EVO 3D
lloydw82 said:
In your settings under about -> Software Information -> More -> Baseband Version.... That will be the RUU you will Run, i had the same issue with my old EVO 3D
Click to expand...
Click to collapse
Got the correct firmware, started the process no problem. Now I've got an Error [155]: Unknown and that's as far as it'll take me. I've tried multiple times, and nothing happens. When the phone is supposed to restart it just sits there as if nothing happened to it at all. The RUU instructed me to restart the phone and do the recovery through the program. Once through, it says that I should now try to start the RUU again. and the same thing happens. Am I missing something here?
When running the RUU, are you getting a 155 Error Code?
Yeah, the Error 155 keeps coming up.
Sent from my EVO using xda app-developers app
SilverJaw said:
Yeah, the Error 155 keeps coming up.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Is your bootloader relocked?
lloydw82 said:
Is your bootloader relocked?
Click to expand...
Click to collapse
I have S-On but it still shows "tampered" and "unlocked."
Sent from my EVO using xda app-developers app
SilverJaw said:
I have S-On but it still shows "tampered" and "unlocked."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
you HAVE to relock your bootloader inorder to run the RUU
Follow these steps
http://forum.xda-developers.com/showthread.php?t=1655832
lloydw82 said:
you HAVE to relock your bootloader inorder to run the RUU
Follow these steps
http://forum.xda-developers.com/showthread.php?t=1655832
Click to expand...
Click to collapse
Yep, that's the problem I was having. Once I relocked the bootloader the RUU ran smooth as butter. Took a little while so make sure you have enough battery/have it plugged in.
kidstechno said:
Yep, that's the problem I was having. Once I relocked the bootloader the RUU ran smooth as butter. Took a little while so make sure you have enough battery/have it plugged in.
Click to expand...
Click to collapse
Glad i could help you. I had those same issues so it was just in my knowledge. Now i am S-OFF and love it so far.
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
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.