Related
PLEASE READ: This will only work on a stock, signed S-OFF HBOOT. Do not try this on a patched or ENG HBOOT or the result will be a permanent hard brick.
1. Boot into fastboot on your device
2. Open a terminal or command prompt and navigate to where your fastboot binary is.
3. Type the following commands:
Code:
fastboot devices
Ensure your device is listed
_________________________________
Code:
fastboot oem readsecureflag
The output should read something like: secure_flag: 0
_________________________________
Code:
fastboot oem writesecureflag 3
_________________________________
Last:
Code:
fastboot reboot bootloader
Verify that your device is now S-ON
Thanks to Blue6IX for original tutorial
Thanks for this man, I was wondering when someone would come up with this. People will need it to fully return to stock.
Sent from my HTC PH39100 using xda premium
Thanks bud. Logic would suggest you could enter 0 to give s off inplace of 3 to return to s on.
Sent from my HTC Velocity 4G using XDA Premium App
78cortina said:
Thanks bud. Logic would suggest you could enter 0 to give s off inplace of 3 to return to s on.
Sent from my HTC Velocity 4G using XDA Premium App
Click to expand...
Click to collapse
No that will not work, you will have to run the S-Off tool again to regain it.
Awesome thank you
Sent from my HTC PH39100 using XDA
hey cruzin long time, how u been?
do you know if this will return you to a "LOCKED" stated instead of RELOCKED?
lebmb said:
hey cruzin long time, how u been?
do you know if this will return you to a "LOCKED" stated instead of RELOCKED?
Click to expand...
Click to collapse
I tried it... can confirm that u first what I did was lock bootlader run stock rom like ruu and then do these steps.... It will say locked and s on
Sent from my HTC PH39100 using XDA
Marshmellow92 said:
I tried it... can confirm that u first what I did was lock bootlader run stock rom like ruu and then do these steps.... It will say locked and s on
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
that's what i thought
thanks
Just clarifying something, so this will or will NOT work for the ics hboot posted on the s-off site by juopunutbear?
slapshot30 said:
Just clarifying something, so this will or will NOT work for the ics hboot posted on the s-off site by juopunutbear?
Click to expand...
Click to collapse
It will, just as long as you chose the non-patched hboot without fastboot commands.
Just had to use this method.
Used the PH39IMG to get back to a stock hboot and ran the commands. Confirmed that it does display locked in hboot.
Unlocked, reflashed recovery.. and I am good to go s-on
Sent from my HTC PH39100 using XDA
Where can I find the steps on flashing the PH39IMG to get back stock hboot ?
dynamiclynk said:
Where can I find the steps on flashing the PH39IMG to get back stock hboot ?
Click to expand...
Click to collapse
Superuser guide opt 6
http://forum.xda-developers.com/showthread.php?t=1416836
Just FYI it reboots once during the process let it do it's thing don't interrupt it.
esloan said:
Superuser guide opt 6
http://forum.xda-developers.com/showthread.php?t=1416836
Just FYI it reboots once during the process let it do it's thing don't interrupt it.
Click to expand...
Click to collapse
Thanks!
Yeah seems the
SECOND OPTION (PH39IMG.zip flash) <-- link dead
So can I do OPTION ONE and download the correct RUU and do the same or does the PH39IMG.zip have something the RUU does not ?
dynamiclynk said:
Thanks!
Yeah seems the
SECOND OPTION (PH39IMG.zip flash) <-- link dead
So can I do OPTION ONE and download the correct RUU and do the same or does the PH39IMG.zip have something the RUU does not ?
Click to expand...
Click to collapse
The RUU will do the trick.
Sent from my HTC Holiday using xda premium
Curious. Could you write the secureflag to 0?
Sent from my HTC PH39100 using XDA
mibikin said:
Curious. Could you write the secureflag to 0?
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Nope ,
Sent from my HTC PH39100 using XDA
after i say
fastboot oem readsecureflag
The output is : secure_flag: 3
can i proceed to safety or killing the phone?
i did a s off through HTC by the way
Marshmellow92 said:
I tried it... can confirm that u first what I did was lock bootlader run stock rom like ruu and then do these steps.... It will say locked and s on
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
So for all intents and purposes, it will look like it was never HTC Unlocked then? My g/f has a Vivid, and she's very picky about going to the darkside of rooting, because she doesn't want her warranty voided. If it can look like it's been returned to stock, that would help.
I cant get it to say ***LOCKED*** I locked hboot, ran GB RUU, ran ICS RUU, followed your steps, fastboot oem readsecureflag
Output is : secure_flag: 3
***RELOCKED***
S-ON
Did I do something wrong?
I promise I searched I just couldn't find anything.
Sent from my HTC One using xda premium
spitfire2425 said:
I promise I searched I just couldn't find anything.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
No
Sent from my HTC One using xda premium
Read the rev s-off guide... People with locked phones succeed
Sent from my HTC One using xda app-developers app
spitfire2425 said:
I promise I searched I just couldn't find anything.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
From what I've read is S-Off is base security off completely and bootloader unlock isnt needed. Im just leaving my bootloader unlocked in case.
Hi
greetings,
unlock bootloader gives access to partial system files
where as S-OFF which means security off will give you full system access
if your s-off and locked bootloader then you can not use fastboot\abd commands. for that you need a unlocked bootloader.
but you being S-OFF you can directly flash a patched hboot which will give access to bootloader option ( do not know if its available right now)
so you will have to unlock your hboot or flash a patched hboot.
you need fastboot\abd commands to flash recovery and that needs unlocked bootloader.
I don't believe that's true. You have to use fastboot to unlock the bootloader and I used fastboot getvar all while locked.
I just wanna know if I can flash a Rom with locked bootloader and s-off.
Sent from my HTC One using xda premium
spitfire2425 said:
I promise I searched I just couldn't find anything.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I have a HTC butterfly and I already did that we now have s off and we can change our relocked to locked on our bootloader. Once ur s off u can use custom recovery and root and also flash roms when bootloader is locked I did it couple times jus make sure u have cwm or twrp as the recovery. But for ur phone I don't think so because we don't use fastboot oem lock command no more we use a flashable zip to lock
Sent from my HTC Butterfly using xda premium
Yes you can flash a ROM with S-OFF and locked but you can't flash a custom recovery whilst locked unless you have a ZIP you can flash via fastboot (like it used to be with the Sensation/Desire). Leaving it unlocked doesn't actually matter as if you ever need to send it back to HTC you can reload the stock ROM and lock it again before doing so. Everyone wins
Thank you for the answer.
Sent from my HTC One using xda premium
Anyone know how? I have to return the phone because of physical defect.
Sent from my HTC One using xda premium
Well then you're going to want full stock locked not relocked..do you have s off
a box of kittens said:
Well then you're going to want full stock locked not relocked..do you have s off
Click to expand...
Click to collapse
I also would like to know how to. I have been searching endless on restoring this one back to stock every possible way leads to verification fail.... I have the correct nandroid for my model (bell mobility canada) but its becoming a pain. If anyone can point me in the direction that would be much appreciated..and yes I have read the stickies and guides. My major issue it seems is I cannot restore the nandroid in cwm as it wont mount to my sd
a box of kittens said:
Well then you're going to want full stock locked not relocked..do you have s off
Click to expand...
Click to collapse
My s-off is on. So no I'm not on s-off. Just rooted with custom recovery
Sent from my HTC One using xda premium
erapmicks said:
My s-off is on. So no I'm not on s-off. Just rooted with custom recovery
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Your going to have to S-OFF first... You need S-OFF first so that you can lock your boot loader again without it saying "relocked" and "tampered". I'd recommend Revone S-OFF since it does NOT install a custom boot loader and is very easy to use.
bluegizmo83 said:
Your going to have to S-OFF first... You need S-OFF first so that you can lock your boot loader again without it saying "relocked" and "tampered". I'd recommend Revone S-OFF since it does NOT install a custom boot loader and is very easy to use.
Click to expand...
Click to collapse
After having my s-off, what do I do next? Thanks in advance
Sent from my HTC One using xda premium
Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.
Indirect said:
Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd if=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.
Click to expand...
Click to collapse
Flash an ruu.zip or can it be ruu.exe also? Should revone be done after the ruu?
Sent from my PG86100 using xda app-developers app
bleichtman said:
Flash an ruu.zip or can it be ruu.exe also? Should revone be done after the ruu?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
either or and yes. After you RUU.
Indirect said:
either or and yes. After you RUU.
Click to expand...
Click to collapse
Just to be sure cause I'm having issues. This will allow me to flash a 1.29 ruu after having the 1.31 update? This could save me!
Sent from my PG86100 using xda app-developers app
bleichtman said:
Just to be sure cause I'm having issues. This will allow me to flash a 1.29 ruu after having the 1.31 update? This could save me!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes...as it is said in the post.
Indirect said:
Yes...as it is said in the post.
Click to expand...
Click to collapse
Thank you...had a lot of aggravation lately. Sorry for the stupid question.
Sent from my PG86100 using xda app-developers app
So I didn't see this post but did something slightly different and it worked perfect.
Unlocked the bootloader via HTCdev
pushed TWRP for Sprint
Flashed SuperSu
Then followed the revone instructions particularly step 3 su (and going onto the device to grant access.) and everything worked perfect and never had to downgrade from 1.31.
MG
Nice work Indirect good lookin out
Win for Indirect!
Sent from my HTCONE using xda premium
THANK YOU!!!
I owe you!!!
Indirect... you saved many a phones. I have been searching for this and read many a post where people were scrambling (not necessarily for s-off, but the fact that they relocked the bootloader and could not run the 1.29 RUU. I encountered the same thing but just unlocked again and flashed my stock nandroid. Thanks!
If I run just...
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29
Does that leave me with a stock build and s-on? In the event I had to part with the One, etc.
Yes.
Sent from my hidden jewel
Indirect said:
Yes.
Click to expand...
Click to collapse
Kind of related thing happened to me, what do I make of this?
I was S-OFF, but with the newest firmware and custom ROM, TWRP installed.
I did the fastboot oem lock, then RUU'ed back to OMJ's straight up stock Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Once that got booted up I went ahead and did the system update to 1.31.
NOW, when I go into bootloader it says "relocked" up top, but says S-OFF. S-OFF?!? Didn't I relock it and RUU?
Also, when I try to enter recovery, all I get is a phone with a red triangle above it.
FlowingAway said:
Kind of related thing happened to me, what do I make of this?
I was S-OFF, but with the newest firmware and custom ROM, TWRP installed.
I did the fastboot oem lock, then RUU'ed back to OMJ's straight up stock Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Once that got booted up I went ahead and did the system update to 1.31.
NOW, when I go into bootloader it says "relocked" up top, but says S-OFF. S-OFF?!? Didn't I relock it and RUU?
Also, when I try to enter recovery, all I get is a phone with a red triangle above it.
Click to expand...
Click to collapse
When you RUU, it doesn't turn the security back on, hence the S-Off still. However, it does put the stock recovery back on, which is why it has the phone with the red triangle. If you want S-On, you can flash the Stock H-boot, or use Revone to make it say locked instead of relocked and say S-On (I believe it can do that, although I'm not entirely sure.) As for recovery, just re-flash twrp in fastboot.
Edit: "Fastboot OEM lock" doesn't mess with security at all. It just re-locks the bootloader.
Sent from my HTCONE using xda premium
If I am S-on and want a factory recovery, can a stock recovery be flashed in fastboot once back to 1.31?
enmriley said:
If I am S-on and want a factory recovery, can a stock recovery be flashed in fastboot once back to 1.31?
Click to expand...
Click to collapse
Yes.
Sent from my HTCONE using xda premium
plegrand said:
Yes.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Thanks. one more question on this topic. The recovery (or screen) with the red triangle will flag a problem with Sprint right? I assumed the RUU didn't flash the stock recovery when I saw this. I am trying to get around the screen with the red triangle. Will flashing a stock recovery replace this? If not can you provide guidance on doing so after the 1.29 RUU is flashed as described in the OP?
enmriley said:
Thanks. one more question on this topic. The recovery (or screen) with the red triangle will flag a problem with Sprint right? I assumed the RUU didn't flash the stock recovery when I saw this. I am trying to get around the screen with the red triangle. Will flashing a stock recovery replace this? If not can you provide guidance on doing so after the 1.29 RUU is flashed as described in the OP?
Click to expand...
Click to collapse
What? The red triangle means you booted into recovery but something went wrong, either there's no update to flash or something like that. Are you trying to now update to 1.31 after the 1.29 RUU?
Sent from my HTCONE using xda premium
No, I went through the process defined in the OP to return to stock executing a 1.29 RUU. This seemed to work fine. I then received the OTA update to 1.31. After refusing the update several times I accepted it. I didn't go into recovery before accepting the OTA update (not sure that would matter but it would have identified the red triangle apart from the 1.31 uodate) Now when I boot to recovery I get the red triangle where I was expecting to see the stock boot menu.
so i ran the echo command and get seek 1seek64 failed am i in the clear to flash the ruu or what should i do kind of scared to move away from recovery
it worked xD thanks dude
Hello there!!!.....Really need some help form you HTC experts. Here is my problem, my htc is currently stuck at the screen where all i am seeing is the htc logo with four exclamation marks in the 4 corners. 1. whenever i tried to run the RUU (run as administrator) i would get a error 152, and this is with my bootloader locked. now i read through a few forums and this one guy told me to change back to S on, now that i have done so when ever i try to run the ruu i get error 132. can anyone please assist?
Do you have a custom recovery on your device? And a backup? If so hold your phone up to a light and hold power and volume down it should boot into fast boot from there boot into recovery and restore your back up
Sent from my SGH-T989D using xda app-developers app
offwiththeface said:
Do you have a custom recovery on your device? And a backup? If so hold your phone up to a light and hold power and volume down it should boot into fast boot from there boot into recovery and restore your back up
Sent from my SGH-T989D using xda app-developers app
Click to expand...
Click to collapse
no custom rom installed.....no backup either.
Are you still on hboot 1.44?
If yes, s-off again.
If no, going s-on was probably a terrible mistake.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
Are you still on hboot 1.44?
If yes, s-off again.
If no, going s-on was probably a terrible mistake.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes i am still on hboot 1.44. how do i s off with the device stuck in ruu?
altezza1 said:
yes i am still on hboot 1.44. how do i s off with the device stuck in ruu?
Click to expand...
Click to collapse
Definitely get back s-off !!! It will have zero effect (now or in the future) about locked/unlocked, custom/stock rom, OTAs, etc. but it would allow you to flash unsigned firmware and/or downgrade, which is very important if you want to run a RUU.
If you flash a custom recovery, you can issue the revone ADB commands in the recovery screen.
EDIT: once you have s-off, you need to change your CID to SuperCID to run the RUU
just make sure you're using a Sprint version RUU or custom ROM, as Sprint is different from ATT, international, etc.
nkk71 said:
Definitely get back s-off !!! It will have zero effect (now or in the future) about locked/unlocked, custom/stock rom, OTAs, etc. but it would allow you to flash unsigned firmware and/or downgrade, which is very important if you want to run a RUU.
If you flash a custom recovery, you can issue the revone ADB commands in the recovery screen.
EDIT: once you have s-off, you need to change your CID to SuperCID to run the RUU
just make sure you're using a Sprint version RUU or custom ROM, as Sprint is different from ATT, international, etc.
Click to expand...
Click to collapse
The only problem with that plan is that i am stuck in RUU boot, and i can only do fastboot commands. how do that?
altezza1 said:
The only problem with that plan is that i am stuck in RUU boot, and i can only do fastboot commands. how do that?
Click to expand...
Click to collapse
You can/have to flash recovery using fastboot anyway.
I believe it's "fastboot flash recovery <filename>"
Sent from my HTC One using xda app-developers app