I think my wife's Rezound is starting to have issues. It is randomly freezing and you need to power it off and on for it to come back. Even happened right after a clean flash while in the setup screens.
I do have ICS on it and my bootloader is unlocked and I am s-off. What are the steps needed before sending it back to Verizon and has anyone had any issues when sending the device back after re-locking it?
I looked for a thread on this but had no luck on a step by step process......
Appreciate the help in advance.
Reflash the factory RUU and then revert to S-ON. If your bootloader is unlocked, you'll need to relock it before you flash the RUU.
shrike1978 said:
Reflash the factory RUU and then revert to S-ON. If your bootloader is unlocked, you'll need to relock it before you flash the RUU.
Click to expand...
Click to collapse
Where can we get the latest update RUU? Does it need to be flashed in the bootlader screen? How does one get back to S-ON?
So step one is to relock the bootloader which I know can be done with the tool.
Then flash the RUU, (waiting for correct way)
Then back to S-On (waiting on instructions how)
i'll help
Are you unlocked or locked?
You are s-off right?
What is you're hboot? is it modified?
I am unlocked
I am s-off
Not sure which hboot I am on. Can't get my wife's phone right now. I am not on the latest hboot I don't think but the one right before it.
As far as it being modified, was that something it asked when doing the s-off? If yes, then I believe I did it. Can no for sure tomorrow when I check the device.
Relock with the toolkit or with "fastboot oem lock"
Latest OTA RUU: http://forum.xda-developers.com/showthread.php?t=1810931&highlight=+12+ruu
How to S-ON: http://forum.xda-developers.com/showthread.php?p=25167284
Do it in that order
Search is your friend.
Also, when you S-OFF, it will relock your bootloader. You do not need to unlock it again. S-OFF > unlock.
Related
Due to the very right side of my touch screen failing I have a warranty replacement on the way. I was able to flash back to the last GB RUU from the ICS Leak without issues. However I would like to bet able to minimize the any reasons for dismissal of the claim. I know when I got s-off, it locked (not re-locked) my bootloader, however I unlocked it after to install 4ext and then root via flashable zip.
So the question is can I revert to s-on as I doubt I could re s-off update my phone to relock it.
Alright, was able to with some help over at the Juopunutbear IRC, wound up having to s-on the device, re s-off (so the device is locked not relocked) then s-on'd the device again.
Phone is 100% stock and ready for return.
Where did u get the gb ruu id like to reset back to stock
Sent from my HTC_Amaze_4G using Tapatalk 2
Guide?
Can you please post what exactly did you do to restore your phone to 100% stock?
chauza01 said:
Can you please post what exactly did you do to restore your phone to 100% stock?
Click to expand...
Click to collapse
Download the stock rom you want from http://forum.xda-developers.com/showthread.php?t=1617644
Rename the file PH85IMG.zip, put it on your external sdcard and flash from Hboot.
You need to have s-off to downgrade.
Did you use the writesecureflag 3 command to revert to s-on?
anyone have accomplish this? I've been trying for last few days. I run the gb ruu the latest Ota twice (yesterday I ran it 4 times) and then the s-on command trough fastboot/adb and I'm left whit stock gb, s-on and RE-LOCKED HBOOT.
Is there anyway to get it to LOCKED?
Thanks in Advance
Edit: I've been running the 2.01.605.11 Ota gb ruu.
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Cares said:
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Click to expand...
Click to collapse
While s-off run the fastboot commands to relock the HBOOT? Can you tell me those commands? Thanks.
Did you unlock while s-off? If you did, you need to s-off again. After s-off you will have a locked bootloader again. Than ruu to gb ota, and send the s-on commands through fastboot.
That will leave you with stock gb, s-on and lock bootloader.
Do not send the s-on command unless your are 100% sure you have an ota stock hboot. Or you will have a brick
I am pretty sure that there is no way to get it to say locked. It will just say relocked. Someone was working on a way to change that but I think they decided not to continue because they didn't want to be accused of encouraging fraud.
Cares said:
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Click to expand...
Click to collapse
No no, just do the S-OFF. If you attempt to lock after S-OFF, it will say RELOCKED.
The S-OFF process is the only way to get back to LOCKED. If you unlock or run the fastboot command to lock again after that, it will show RELOCKED.
a.mcdear said:
No no, just do the S-OFF. If you attempt to lock after S-OFF, it will say RELOCKED.
The S-OFF process is the only way to get back to LOCKED. If you unlock or run the fastboot command to lock again after that, it will show RELOCKED.
Click to expand...
Click to collapse
I meant turning security flag on.
Alright thanks guys gonna try again tonight after work. I'll report back later.
You can definitely return to **Locked** without question if you have s-off. Just run the newest leak RUU twice and it should take it back to locked but S-OFF, did it to my girl's unlocked+s-off rezound two nights ago. I didn't even have to manually run it twice, it just keep rebooting and did the 2nd run on it's own. It's now the stock hboot, locked, s-off. Then if you want GB there shouldn't be any issue flashing the GB RUU since you'd maintain S-OFF
PhantomApollyon said:
You can definitely return to **Locked** without question if you have s-off. Just run the newest leak RUU twice and it should take it back to locked but S-OFF, did it to my girl's unlocked+s-off rezound two nights ago. I didn't even have to manually run it twice, it just keep rebooting and did the 2nd run on it's own. It's now the stock hboot, locked, s-off. Then if you want GB there shouldn't be any issue flashing the GB RUU since you'd maintain S-OFF
Click to expand...
Click to collapse
So the newest one is this one?
3.14.605.10
Kratz17 said:
So the newest one is this one?
3.14.605.10
Click to expand...
Click to collapse
right
PhantomApollyon said:
right
Click to expand...
Click to collapse
Ok gonna give a shot to that. Thanks.
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 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
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