I need to return the phone to Sprint to check on my phone. I am on MeanRom and S-ON. I used Regawmod to gain root an the bootloader says it has been Tampered.
What is the best way to go back to stock and remove the Tampered sign, if possible.
I saw this thread but don't think it will work because my phone is S-On.
http://forum.xda-developers.com/showthread.php?t=1744700
Thank for any insight.
You need soff to disable the developer warnings
I had to return mine too after i'd flashed a ROM, forgot nandroid. Just took it in there and played dumb. "My friend just got this phone too and mine has weird apps and options that his doesn't." They just took it and changed it back to stock for me. "relocked"
Related
Is there anyway to reset the Rezound to the factory locked bootloader?
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment); here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/sho...uide to S-On to restore that too if you wish.
PhantasmRezound said:
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment) and have it handy; here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/showthread.php?p=22045045
Now make sure your bootloader is Locked before running the RUU. Check this and be certain; have to do a bit of extra work if it isn't, so please say you didn't Dev Unlock again after doing S-off lol. (I did this. Had to repeat the whole S-off process to achieve a "Locked" message ultimately. Not fun.)
Ok, after making sure bootloader is Locked... Running that RUU should put the stock hboot back on, verify that after the process. And remeber to turn USB Debugging back on in the stock ROM after running that RUU lol . Then proceed with the guide on the same computer you got all those Dev tools on from doing S-off.
Click to expand...
Click to collapse
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
LakerStar25 said:
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
PhantasmRezound said:
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
Click to expand...
Click to collapse
Cool I was just trying to help out lol.
Sent from my ICS Rezound
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
rezin said:
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
Click to expand...
Click to collapse
Tampered is normal. Did you try flashing it with a ph98img, or as an .exe
It happens after you unlock and install a custom recovery I believe. Are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
big_mike_2k6 said:
And are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yeah make sure your bootloader is relocked
i was in the middle of doing s-off when the phone froze and corrupted the mem card...so i tried redoing the whole process over and i havent been able to get past the hboot...im still unlocked and have access to recovery and hboot but i cant flash a rom and boot into it...i cant run an ruu but the phone is not technically bricked...its an odd predicament...i just flashed a rom and i still cant get it to get past the hboot
Have you tried re-locking the bootloader and then run the ruu?
Sent from my ADR6425LVW using Tapatalk 2
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
rezin said:
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
Click to expand...
Click to collapse
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
synisterwolf said:
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
Click to expand...
Click to collapse
Yeah I already got it up n running...between being unlocked and having a slightly dead battery I wasn't even being given the option to run an ruu...its running now but I still need to do s-off again, and of course my sd card is corrupted so ill work on that tonight
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
willdo7474 said:
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
Click to expand...
Click to collapse
Hey, I didn't have to do this, but if you noticed, controlbear makes backup copies of stuff like boot.img (forget what else) and puts them on your computer. If you crap out you ought to be able to fastboot flash boot [bootimgfilename.img] and be able to boot up your phone. I saw where one person did this to get going again after a failed soff.
Yeah well happened in my case is that I was already s-offed and then I flashed the ruu to go back to stock...then I relocked my phone cuz I'm having an issue with one of the pins on phone (the terminal that connects to battery).so I was gonna get it exchanged, I wanted it to look absolutely stock...so the "relocked" status wasn't good enough, so someone suggested doing s-off again so it will show locked in hboot...well that's where everything went wrong, the phone froze at the wire trick and then the entire memory card was corrupted which is normal...so when I went to redo the whole s-off procedure again I kept rebooting into the blank screen with the arrow...could not get past that, so I resorted to putting my real sd card in...I had no backups for that card cuz that one has my actual personal stuff so I figures it'd be ok since I used a spare to do s-off anyway...well upon powering on the phone it was also corrupted...so Ive actually given up on s-off and getting my phone restored and replaced for a while...I don't know why s-off has always given me problems I've watched and read every vid or post about s-off and am in no way tech illiterate but I've always had problems with s-off (i lost all my pics and documents the first time I did s-off even thought I backed everything up cuz the only way to get it right was to eliminate every file in the folder and rerun it again cuz it didn't back up my sd correctly If at all)...its beyond infuriating
well that didnt last long...i just unlocked and s-offed my phone again, only to be returned to s-on and fully locked (indistinguishable from brand new in box), as i originally intended...im gonna miss this particular phone but it has to be done
Edit:
Thanks for the below suggestions - think I have it figured out.
Installing the stock recovery will removed the tampered error, there's no way while you're s-on to set the bootloader to locked, it will list as re-locked if you run the lock command against it.
You'd need to s-off to return it fully back to the stock settings.
I recently s offed my phone and as long as you read and reread the instructions you will be fine. Make sure that whichever ROM you are using is rooted, at first I ran an RUU and attempted to s off without root and it didn't work so I gave up for a month. Also I found Hansoons s off tool helpful.
Sent from my ADR6425LVW using xda app-developers app
mjones73 said:
Installing the stock recovery will removed the tampered error, there's no way while you're s-on to set the bootloader to locked, it will list as re-locked if you run the lock command against it.
You'd need to s-off to return it fully back to the stock settings.
Click to expand...
Click to collapse
Could you list the order in which I should do things? Like first I should get S-Off - then are there two things I have to install? I really need baby instructions.....Re:
1) S-Off
2) Run this
3) Run this
I'm debating whether I should just say f* it and leave it "Re-Locked" by following the instructions listed on that site and running the ICS RUU.
But I dunno....just wanna get the phone back to them ASAP and hoping to not have to spend hrs on it.....
Hi guys i just switched over from the charge and got my self a rezound. i bought the phone used off of amazon (turned out to be quite the mistake) and was on gb 2.3.4 when it came. so first thing i went to do was to update to ics. I tried the ota update from the phone and most of the time i got "server unavailable" or it would show up in my notifications and would just never start to download. so now im stuck i am guessing the previous owner had to phone rooted and modded or something? i boot my phone into recovery and this is what it says
***** LOCKED *******
VIGOR PVT SHIP SL-ON RL
HBOOT-2.11.0000
eMMC-boot
oct 6 2011,15:4322
HBOOT
VOL UP
VOL DOWN
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
What happens is that the owner did root and did an unroot and now you cant root again happened to me when i bought and inc 2 off amazon and was stuck with the gb 2.3.4 so i think the same happened to you try looking around and trying every root solution and maybe it will work
Is that a typo or does it actually say SL-ON? Should say S-ON. If it really says SL-ON then it was def messed with.
Since it has GB on it it's very likely it was never unlocked and rooted. If it had been rooted I would think the previous owner would have updated it.
If it was s-on and had been unlocked and rooted it would say ***RELOCKED***. Since yours says ***LOCKED*** I think it wasn't rooted before. It's possible that they did the s-off wire trick and then went back to s-on, I think, I'm not sure what the phone would show in bootloader if they did that, but I think it looks like it has never been unlocked.
Regardless, if you want to update to the latest official OTA you can run the 3.14.605.12 RUU from here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you up to date as of a month ago and fully stock. (sorry if you know this, I don't know what your experience is)
Make sure you let it run through a couple times on its own, when it's done it will leave you back in bootloader. The screen will go black for a bit, don't do anything, just leave it, it will go through updating a second time, just make sure you don't interrupt it.
Then you can try to take the OTA from about a month ago which will take you to 3.14.605.13. From what I've read there's not much to that OTA so if you can't take that for whatever reason it's no big loss.
Then if you want to root you'll need to unlock the phone via HTCDev, flash a recovery then root.
feralicious said:
Is that a typo or does it actually say SL-ON? Should say S-ON. If it really says SL-ON then it was def messed with.
Since it has GB on it it's very likely it was never unlocked and rooted. If it had been rooted I would think the previous owner would have updated it.
If it was s-on and had been unlocked and rooted it would say ***RELOCKED***. Since yours says ***LOCKED*** I think it wasn't rooted before. It's possible that they did the s-off wire trick and then went back to s-on, I think, I'm not sure what the phone would show in bootloader if they did that, but I think it looks like it has never been unlocked.
Regardless, if you want to update to the latest official OTA you can run the 3.14.605.12 RUU from here:
That will get you up to date as of a month ago and fully stock. (sorry if you know this, I don't know what your experience is)
Make sure you let it run through a couple times on its own, when it's done it will leave you back in bootloader. The screen will go black for a bit, don't do anything, just leave it, it will go through updating a second time, just make sure you don't interrupt it.
Then you can try to take the OTA from about a month ago which will take you to 3.14.605.13. From what I've read there's not much to that OTA so if you can't take that for whatever reason it's no big loss.
Then if you want to root you'll need to unlock the phone via HTCDev, flash a recovery then root.
Click to expand...
Click to collapse
thanks for the quick responses and it was a type o. i flashed the ruu and am now running 4.0.3 thank you very much
i have the tools to unlock and know how to do it but im not sure about the recovery or s-on/s-off i know what it is im just not sure if i wanna take it off and with the recovery is there a certain one i have to use or is there one that works better than all others? id like to find a rom that is s-on compatible and looking through some of the threads and some have 300+ pages so anything to lightin up my reading load would be greatly appreciated
Hey guys,
I feel like this is a pretty dumb question to ask, but maybe someone can help me. I have to return my phone back to Verizon for a speaker issue on the phone. Anyway, mine says relocked at the very top, I have flashed it back to factory using RUU and I have changed my CID back to factory. Now I haven't gone to S-On yet, and I am following this thread http://forum.xda-developers.com/showpost.php?p=41801200&postcount=2
As I stated it still says ***Relocked*** at the top and I didn't start following this till after I had flashed the RUU, What do I need to do to get it to back to locked? Any ideas as to the direction to move in? Do I need to unlock and root it again, then just follow that guide to get it back to stock?
Thanks
Johnson90512 said:
Hey guys,
I feel like this is a pretty dumb question to ask, but maybe someone can help me. I have to return my phone back to Verizon for a speaker issue on the phone. Anyway, mine says relocked at the very top, I have flashed it back to factory using RUU and I have changed my CID back to factory. Now I haven't gone to S-On yet, and I am following this thread http://forum.xda-developers.com/showpost.php?p=41801200&postcount=2
As I stated it still says ***Relocked*** at the top and I didn't start following this till after I had flashed the RUU, What do I need to do to get it to back to locked? Any ideas as to the direction to move in? Do I need to unlock and root it again, then just follow that guide to get it back to stock?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2293919 ://
Follow the guide for whichever method you used to achieve soff.
Needed to lock first... Since still s-off, flash recovery, flash lock zip, ruu again, then s-on