Pretty much subject says everything. But here's is my situation.
What I did earlier:
Unlocked Bootloader
Tried S-on with Firewater - didn't work - gave up- didn't spend money for getting S-off via moonshine
Installed TWRP
Installed custom roms
NOW, I need to go back to slock and claim some warranty issue (speakers too harsh)
Here's is an at&t RUU
http://forum.xda-developers.com/showthread.php?t=2757462
Can I go back to stock from here? Do I certainly need S-off? Do I just run RUU exe?
Please help!!
Thanks!
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Sent from my HTC One_M8 using Tapatalk
Jano342000 said:
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Click to expand...
Click to collapse
That's correct.
Also to the OP, note that AT&T only voids warranty for physical or water damage. They don't care about software mods, although it is a good idea to return to as close to stock as possible before requesting warranty exchange.
RUU is a good way to do so. S-on is fine, but you have to relock the bootloader. The bootloader will then say RELOCKED instead of UNLOCKED or LOCKED. No other evidence of modding should remain after the RUU.
Related
Something has been bothering me for the past two days. After achieving S-Off I went ahead and unlocked the boot loader via HTCDev (Noob Tool). Now after reading some post it seems I made a mistake Hboot currently says : unlocked and S-off and I also installed JB Hboot now I kind of want to go back to locked but also S-off ,can anybody give me some good directions on how to achieve this?
Also the main reason for this is that I think i messed up my proprietary port on my rezound and might have to take it back in the future. Just moving the phone around with the USB cable attached to my PC I constantly get disconnect and connect sounds on windows and loose inter SD access and Ext also. I just want to take precautions if I really do take it back so I can replace it and just S-On again.
Also I think I twisted the port while it was attached to the USB cable cause I slept on my phone while charging
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
I'm locked with S-Off. So I think there is such a thing.
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
Thats actually really wrong. S-Off is S-Off. Unlocked gives you access to additional fastboot commands (there are a couple hboots in the Dev section that do this without changing the locked status).
[edit]
Correction, you need to S-Off again to become locked. There is a thread in the dev section about setting S-On (it's easy).
CAUTION: Make sure you are on the stock hboot when you S-On. If you S-On the GB Eng hboot or the Juponutbear hboot, you WILL brick your phone.
Sent from my ADR6425LVW using Tapatalk 2
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
Everything you just said was wrong. Normal state after achieving s-off is a locked bootloader. Locked won't matter because there are no longer any security checks. You can essentially flash whatever you want.
Sent from my Dell Streak 7 using Tapatalk 2
Just to clear this up for you, if you unlocked after achieving s-off you will not be able to lock again without returning to s-on then back to s-off. If you try to lock now using fastboot oem lock you will end up "relocked".
Sent from my ADR6425LVW using XDA
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
Duuuude! Now you know. Learning something new every day is a good thing.
trickster2369 said:
Duuuude! Now you know. Learning something new every day is a good thing.
Click to expand...
Click to collapse
You know, in retrospect, thats a much nicer way to about it.
Sorry I was a d*ck
Sent from my ADR6425LVW using Tapatalk 2
Greetings,
I'm sending my phone in for repair as bluetooth has stopped working. I am currently on the OTA ICS, S-On with a RELOCKED flag on Hboot.
Question: How many people would bother with rooting, s-off, just to relock without the flag?
In theory, because I went through HTCdev, they should already know this...right?
Thanks.
Mark
Most would say to be completely sure they don't give you trouble about it being unlocked go ahead and s-off so you can get it back to saying locked instead of relocked. Personally I sent my first Rezound back unlocked and didn't have a problem. I actually don't know if Verizon gets the info about you unlocking through htcdev or even checks. If you were going through HTC then that would be different.
Sent From My HTC Rezound
I just successfully performed S-off but my bootloader changed to "locked". Is that normal?
Also, I declined to install jp modified hboot because I was not sure what it was. Do I have to install another hboot after S-off?
S-OFF > unlocked bootloader. You don't need an unlocked bootloader when you are S-OFF.
With a stock locked bootloader you won't be able to use most fastboot commands. That's the purpose of the jpbear hboot. It allows you to use them without unlocking. However, if you ever go back S-ON, you have to have a stock bootloader or you'll brick, so you should only use a modded hboot if you need the fastboot commands. Otherwise, stock is just fine.
I read a lot about this subject in this thread last night:
http://forum.xda-developers.com/showthread.php?t=1852228
Could give you some useful info on the pros and cons of flashing the j-nut hboot or not and keeping locked or unlocking.
shrike1978 said:
S-OFF > unlocked bootloader. You don't need an unlocked bootloader when you are S-OFF.
With a stock locked bootloader you won't be able to use most fastboot commands. That's the purpose of the jpbear hboot. It allows you to use them without unlocking. However, if you ever go back S-ON, you have to have a stock bootloader or you'll brick, so you should only use a modded hboot if you need the fastboot commands. Otherwise, stock is just fine.
Click to expand...
Click to collapse
Sorry for the noob questions. I don't know much about the tech, I can only follow the instructions. So, do I need a modified bootloader if I want to flash Rom that require S-off or is the stock bootloader OK? I want to flash a Rom for which I need to be S-off and on the latest RUU.
I'd guess that 99% of people who do the jbear s-off procedure take the modified hboot as an uniformed choice. They figure if jbear provided this, then it must be great.
If you do not install the jbear hboot, you should unlock your bootloader using htcdev unlock bin file. You will have the following benefits with s-off, stock unlocked hboot:
o can ruu with unlocked bootloader. you will never need to relock before performing an ruu.
o install ROMs easier without the need to install kernels via ph98img.zip. method
o able to fastboot flash recovery and boot/kernel
o less bricking risks in the future
being s-off with the locked jbear modified hboot has the advantages of:
o displaying Locked, but can do everything an unlocked bootloader can do.
o makes it easier to lie to Verizon that you never tampered with the phone, never unlocked, never ROMed, it is not your fault the phone is bricked.
o able to fastboot flash recovery and boot/kernel
o able to fastboot flash hboot/bootloaders and some other fastboot commands that no developers are using.
One guy went so far as to hexedit his hboot to display "s-on" and "locked" to hide the fact that he is s-off and unlocked. He bricked his phone on his first attempt. got phone insurance to replace his phone. Then he got others to test his later attempts which work and didnt brick. So if you want to lie with impunity to Verizon, don't use jbear hboot, instead use this guy's hboot. you'll find it in the developer's forum.
Personally I take great care and deliberation about what changes I make to my phone because I do not plan on lieing to get someone else to pay for my mistakes.
Wendemixda said:
I just successfully performed S-off but my bootloader changed to "locked". Is that normal?
Also, I declined to install jp modified hboot because I was not sure what it was. Do I have to install another hboot after S-off?
Click to expand...
Click to collapse
Yes it is normal....see what the other guys say about jb hboot.....for me, since I haven't and don't plan on having to use fastboot commands, I just left it locked with stock hboot.
How can I reunlock mine? S off locked bootloader
An old HTC Incredible 4G
EzraDi said:
How can I reunlock mine? S off locked bootloader
An old HTC Incredible 4G
Click to expand...
Click to collapse
This is the Rezound forums. You should find the Incredible forums and ask there, although I think a lot of Rezound users used to have Incredibles, but it's pretty dead here now that the phone is 4 years old.
feralicious said:
This is the Rezound forums. You should find the Incredible forums and ask there, although I think a lot of Rezound users used to have Incredibles, but it's pretty dead here now that the phone is 4 years old.
Click to expand...
Click to collapse
Thank you
I'd like to restore my phone to its absolute default. I would like to return my phone tomorrow. Can you help explain to me how a rooted phone can be restored?
WARNING: If you have flashed a custom bootloader make sure you flash it back to a stock bootloader before you do S-ON or you WILL brick.
First read the revone one thread on how to lock everything back up. First and second post have all the info you need to make it look untouched.
http://forum.xda-developers.com/showthread.php?t=2314582
Then flash the RUU after you have S-ON and Locked in the bootloader.
http://dl3.htc.com/application/tmo/....20_10.40.1150.04_release_324846_signed_2.exe
designgears said:
WARNING: If you have flashed a custom bootloader make sure you flash it back to a stock bootloader before you do S-ON or you WILL brick.
First read the revone one thread on how to lock everything back up. First and second post have all the info you need to make it look untouched.
http://forum.xda-developers.com/showthread.php?t=2314582
Then flash the RUU after you have S-ON and Locked in the bootloader.
http://dl3.htc.com/application/tmo/....20_10.40.1150.04_release_324846_signed_2.exe
Click to expand...
Click to collapse
I currently have "unlocked" and "tampered," so do I just need to flash the RUU?
hammettorchandler said:
I currently have "unlocked" and "tampered," so do I just need to flash the RUU?
Click to expand...
Click to collapse
Do you have hboot version 1.44? If so run this from bootloader:
fastboot oem lock
Then run the ruu. If you're s-off check the thread designgears just shared with you and go s-on last.
Sent from my HTC One using xda premium
mikeyinid said:
Do you have hboot version 1.44? If so run this from bootloader:
fastboot oem lock
Then run the ruu. If you're s-off check the thread designgears just shared with you and go s-on last.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
He should use revone first to make it look untouched because the motochopper root method is blocked. Otherwise he will have to go back to the state he is in now and do it all in the right ordered
designgears said:
He should use revone first to make it look untouched because the motochopper root method is blocked. Otherwise he will have to go back to the state he is in now and do it all in the right ordered
Click to expand...
Click to collapse
ah, you are correct.
Many thanks to you both. Mission accomplished. I re-rooted too afterwards.
Sorry for the newbish questions, but if I'm getting a replacement phone because my screen cracked and I need to send my current phone back to Asurion. I'm currently on the 1.54 hboot from the international firmware, so do simply need to flash back to the stock 1.44 hboot, use REVONE to revert to S-On, lock the bootloader and then flash the RUU? Also, can I flash the decrypted RUU zip instead of the RUU.exe after I've relocked the bootloader? I'm a Linux user and would prefer not having to install Windows to bring the phone back to stock.
RobBull69 said:
Sorry for the newbish questions, but if I'm getting a replacement phone because my screen cracked and I need to send my current phone back to Asurion. I'm currently on the 1.54 hboot from the international firmware, so do simply need to flash back to the stock 1.44 hboot, use REVONE to revert to S-On, lock the bootloader and then flash the RUU? Also, can I flash the decrypted RUU zip instead of the RUU.exe after I've relocked the bootloader? I'm a Linux user and would prefer not having to install Windows to bring the phone back to stock.
Click to expand...
Click to collapse
Insurance doesn't care what state you are in. Because you are paying them a deductible. No need to go through a that
Sent from my HTC One using xda app-developers app
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.