S-off with locked bootlader...help - Sprint HTC EVO 4G LTE

i unrooted running the 2.13 RUU and i ended up with s-off and the 1.19 bootloader. When i run the s-on program it says wrong bootloader...what can i do?
i just need to take my phone back to best buy to exchange

Related

[Q] Removal of *** RELOCKED ***?

As I had the unfortunate pleasure of receiving my phone with 1.5 already on it I had used HTC's unlock method. However now, I was able to downgrade my HBoot to 1.40 with this amazing guide by Unknownforce and was able to finally attain S-OFF.
To get back to the latest radios and everything I ran the 2.17 RUU knowing I'd keep S-OFF through it and would downgrade my HBoot afterwards. However, I noticed that I still have the mark of *** RELOCKED *** above S-OFF (I had to relock it to use the RUU to brick).
I downgraded (again) back to 1.40 HBoot but I'm curious if it's possible to hide the fact that I've unlocked in case I ever have to turn my phone back into Sprint.
I would have thought that replacing the HBoot partion with the stock 1.40 image with the emmc_recover tool would have overwritten that. I take it that means that the locked/unlocked/relocked flag is stored elsewhere?
If you did HTC unlock then sprint has your serial numbers on file that you did it so dont worry about it
Sent from my PG86100 using Tapatalk

[Q] S-OFF & Craigslist Rezound

So I bought a phone from a guy on Craigslist, while it works fine, there's something weird here. What I want to do is have it S-OFF, but here's whats up:
Bootloader is HBOOT 2.21.0000. It says ***UNLOCKED*** but also it says ***TAMPERED***. Also it says VIGOR PVT SHIP S-ON RL.
Everything seems to be working fine; it currently has CleanROM 4.3 on it. I'm afraid to start doing anything until I know where to start. I *THINK* what I need to do is the following:
1. fastboot oem lock the bootloader
2. Flash latest ICS leak RUU twice.
3. Follow the Juopounut guide for S-OFF using the 2.21.0000 modified HBOOT
Does this sound right? Thanks for your help!
If its already unlocked, stay unlocked. Relocking it is going backwards toward s-off. Once s-off you will have a locked bootloader. I did not install the jbear modified hboot. I installed Amon ra as a ph img after s-off and ics ruu
You should just follow the jbear s-off instructions since you already have unlock
S-off prior to ics is my preferred method, if something goes wrong with the ruu, you're stuck.
Also, no need to unlock once you have s-off
I got it. I wanted to go back to the newest leak and then proceed. I flashed the latest leak RUU and then re-unlocked.
The ***TAMPERED*** appears once I flashed the amon-ra recovery. Guess thats normal on the ICS builds...
Mine does not show tampered. I am s-off, locked, ics 3.14 firmware with ruu hboot, amon ra recovery, running newts one xxx
in_retrospekt said:
Mine does not show tampered. I am s-off, locked, ics 3.14 firmware with ruu hboot, amon ra recovery, running newts one xxx
Click to expand...
Click to collapse
Yep mine doesn't either. I'm just guessing but I think it might only been the 3.11.605.22 leak that did that.
Sent from my Sense4 ICS Rezound
Mine doesn't show it now that its truly S-OFF. Thanks all!

Relock phone to S-ON after jbear and HTCDEv

I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
vega312 said:
I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
Click to expand...
Click to collapse
You need to start by flashing the 2.89.651.2 RUU, either using the RUU.exe from Windows or an RUU.zip renamed to PG86IMG.zip from the bootloader. If you didn't do the htcdev unlock again after the wire trick, the stock bootloader should show ***LOCKED*** with a version of 1.58. Since you are only getting the phone serviced, it's probably OK to leave it S-OFF, but if you want it 100% stock you need to issue the following command after you have verified that the bootloader is 1.58:
fastboot oem writesecureflag 3
Once you have issued this command your phone will be S-ON and you will have to do the wire trick again after you get it back to be S-OFF. My understanding is that most repair facilities, including Sprint, don't mind if you give it to them S-OFF. However, if you are sending it back to HTC it might be worth doing since with stock software, a locked bootloader and S-ON it will look "factory fresh" to them.
You might also want to test your GPS again once everything is back to stock, just to make sure it's not a ROM problem.
ramjet73
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
jb14813 said:
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?p=19089387

ATT ruu keep hboot 1.44

I need to send my phone in for a warranty reason, my bottom mic stopped working. I am currently S-off and on hboot 1.44. I was wondering what att RUU I should use to keep the ability to s-off in the chance that att denies the warranty claim.
What I want to do
- lock boot loader
- change relocked to locked using revone
- run RUU
- go back to s-on
- warranty claim
if warranty denied, is shouldn't be but I would rather be safe than sorry, I would like to be able to get s-off again.
is the the right right ruu or will this leave me with a phone I cannot s-off
RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe
From what i can tell it should work, I think it keeps the same hboot but I just want to be sure.
Answered my own question the phone was on 1.26.502.12 already
Flashing an RUU won't return to s-on anyway
gunnyman said:
Flashing an RUU won't return to s-on anyway
Click to expand...
Click to collapse
I was worried about the RUU upgrading the hboot because I need to go back to S-on for a warranty claim.

Confusing result after RUU

In an effort to upgrade bootloader and software to be compatible with cm11.. I used vipeRUU to go from 1.12 bootloader to 2.09 bootloader with the 3.17.651.471 software, whats confusing me is bootloader still says ..Unlocked ..and S-off after running ruu ..bootloader has changed and so has the software... (i was Previously s-off via Lazy panda).. i was under the impression that this would un root and lock bootloader again.. i know that i now have lost root i know how to check that .. question is , is bootloader locked now as well?..tried rumrunner and moonshine to no avail, to get S-OFF .. and it needs to be unlocked for those exploits to work.. any ideas?
It will lock your bootloader and return the phone S-on if you chose those options in the menu when you first ran VipeRUU. If you're still S-off, then all you need to do is unlock the bootloader again unless it's showing unlocked. An easier route than what you chose would have been to update your Hboot to the Rumrunner Hboot, which takes less than a minute to do. You'll still need to update your firmware, since VipeRUU is a version behind what's currently out there. If you're S-on now, you'll need to unlock the bootloader and run Moonshine.
Sent from my HTC EVO 4G LTE
ok .. i see what you're saying .... i just ran rum runner... and it seemed to do the trick im currently S-OFF hboot 2.09 with the 3.17.651.4 71 software.. was able to install twrp>>>..I think im good to go!?..>>>>> i shall now...FOAF..lol...btw Thanks!!!
Yep, you should be good to go now. Just make sure that you have Superuser privileges and all should be right with the world:thumbup:
Sent from my HTC EVO 4G LTE

Categories

Resources