i'm on ARHD 31.0 and have S-Off with Hboot 1.54 , i want to go back to stock 2.24.401.8 and do an OTA update will that S-on the device or will it remain S-Off??
and about google drive offer how can i claim it coz i have locked the bootloader but i still can't get it ??
amr-213 said:
i'm on ARHD 31.0 and have S-Off with Hboot 1.54 , i want to go back to stock 2.24.401.8 and do an OTA update will that S-on the device or will it remain S-Off??
and about google drive offer how can i claim it coz i have locked the bootloader but i still can't get it ??
Click to expand...
Click to collapse
S-Off will remain after the update.
not sure with the gdrive, haven't tried it yet
Unlock your bootloader,keep s-off and use htcguru reset ruu zip installed via fastboot to downgrade then receive all ota's back up to 2.24.401.8
Did this yesterday works a treat
Sent from my 801n M7_UL
steelmaggot said:
Unlock your bootloader,keep s-off and use htcguru reset ruu zip installed via fastboot to downgrade then receive all ota's back up to 2.24.401.8
Did this yesterday works a treat
Sent from my 801n M7_UL
Click to expand...
Click to collapse
Where can i find this can you give me link coz the search on xda is down right now
http://www.htc1guru.com
Sent from my 801n M7_UL
Can I go s-on with the latest 3.62 firmware or do I need to go back to 2.24.401.1 first?
Better one more stupid question then a bricked phone.Do I need s-on to send it to repairing the camera?
jaypeg123 said:
Can I go s-on with the latest 3.62 firmware or do I need to go back to 2.24.401.1 first?
Better one more stupid question then a bricked phone.Do I need s-on to send it to repairing the camera?
Click to expand...
Click to collapse
Nope. Just lock your bootloader using revone (it just shows the locked tag) and remove Tampered flag, you won't lose any data (I used Hasoon2000 toolkit for revone). This makes the phone look like it was bought that way.
Besides HTC doesn't pay so much attention to S-OFF, it's just the unlocked bootloader and tampered flag that may void your warranty
Once you S-OFF, I don't see a reason why you will S-ON again.
HussainQ said:
Nope. Just lock your bootloader using revone (it just shows the locked tag) and remove Tampered flag, you won't lose any data (I used Hasoon2000 toolkit for revone). This makes the phone look like it was bought that way.
Besides HTC doesn't pay so much attention to S-OFF, it's just the unlocked bootloader and tampered flag that may void your warranty
Once you S-OFF, I don't see a reason why you will S-ON again.
Click to expand...
Click to collapse
Ok thank's I have read about people sending it in with s.off and get it s-on in return. But do you know the drill about the s-on, Is it nessesery to have the original 2.24.401 installed to get it right. I did update it OTA so It is 100% now, just forgot about the s-off.
jaypeg123 said:
Ok thank's I have read about people sending it in with s.off and get it s-on in return. But do you know the drill about the s-on, Is it necessary to have the original 2.24.401 installed to get it right. I did update it OTA so It is 100% now, just forgot about the s-off.
Click to expand...
Click to collapse
I don't really know if they S-ON the device or not. OTA is fine since it is official. Just in-case, I would check rumrunner S-Off compatibility with your firmware. And check your HBOOT version as well.
Hi,
After going through a lot of threads created this one. I'm from India and my HTC ONE is of x.xx.707.x region.
I recently S-off'ed my One hboot 1.54 with rumrunner guide (http://forum.xda-developers.com/showthread.php?t=2488772)
Then i updated my firmware to fw_3.62.401.1_custom that i got from Vomer's guide (http://forum.xda-developers.com/showthread.php?t=2365506)
I also flashed custom recovery (TWRP).
I then flashed the stock 3.62.401.1.zip rom that i got from ARHD thread.
My main concerns are
1. Can i downgrade the hboot anytime ?
2. Can i get back to 100% stock? With S-on ? if so any help regarding this is greatly appreciated.
3. I'm now new to S-Off thing, and is there anything that i should take care of from now? (like what firmware i should not flash, or Rom or radio restrictions)
Thanks.
the same questions
coolshritz said:
My main concerns are
1. Can i downgrade the hboot anytime ?
2. Can i get back to 100% stock? With S-on ? if so any help regarding this is greatly appreciated.
3. I'm now new to S-Off thing, and is there anything that i should take care of from now? (like what firmware i should not flash, or Rom or radio restrictions)
Thanks.
Click to expand...
Click to collapse
dingnangen said:
the same questions
Click to expand...
Click to collapse
With S-Off:
1- Yes you can downgrade/upgrade anytime you see fit.
2- 100% Stock with S-Off!! With S-On, you can get pretty close but you can't make your bootloader say "LOCKED" it will only show "RELOCKED"
3- no restrictions, you can flash pretty much anything with S-Off (obviously you should stay away from Sprint or Verizon stuff as they are not GSM)
4- don't go S-On!
nkk71 said:
With S-Off:
1- Yes you can downgrade/upgrade anytime you see fit.
2- 100% Stock with S-Off!! With S-On, you can get pretty close but you can't make your bootloader say "LOCKED" it will only show "RELOCKED"
3- no restrictions, you can flash pretty much anything with S-Off (obviously you should stay away from Sprint or Verizon stuff as they are not GSM)
4- don't go S-On!
Click to expand...
Click to collapse
4- can i downgrade to 1.44 then s-on using revone?(for warranty)after that,can I get s-off again using revone?
Sent from my HTC One using Tapatalk 2
dingnangen said:
4- can i downgrade to 1.44 then s-on using revone?(for warranty)after that,can I get s-off again using revone?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
If you really need to go S-On again (though many people send in their phones with S-Off, cause some actually ship from HTC S-Off), here are the steps:
1- change CID & MID back to stock (in case you changed them)
2- remove TAMPERED using either revone or http://forum.xda-developers.com/show....php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/show....php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU
5- AFTER YOUR ARE 100% SATISFIED OF ABOVE RESULTS (ie no more tampered, bootloader LOCKED, 100% stock)
"fastboot oem writesecureflag 3" to get S-On.
Hit the thanks button if I helped
Nkk71 I have a similar question
I s offed then restored a nandroid backup of 4.1.2 and removed tampered and locked bootloader. I ota'd right up to the latest 3.62.306.7 version soiit's stock Rom, stock recovery and hboot 1.55
Can I s on for warranty purpose now?
stovie_steve said:
Nkk71 I have a similar question
I s offed then restored a nandroid backup of 4.1.2 and removed tampered and locked bootloader. I ota'd right up to the latest 3.62.306.7 version soiit's stock Rom, stock recovery and hboot 1.55
Can I s on for warranty purpose now?
Click to expand...
Click to collapse
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
nkk71 said:
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
Click to expand...
Click to collapse
One last question. If i give you my flow of what I did can you help, as I don't want to s-on and mess it up...
1. Rumrunner to obtain s-off on hboot 1.54
2. Downgraded my hboot to 1.44 - this was a stock hboot, but I modified the android.info part so I could flash it onto my model
3. Changed CID to HTC__032 and ran "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed" which reset my hboot, bootloader etc and completely stock. At this stage my bootloader is LOCKED and still s-off
4. With bootloader still locked, installed CWM Recovery and restored a nandroid backup CID O2__102 1.27.206.1 and stock recovery
5. Changed CID back to O2___001
6. Installed the various OTA updates right up to current 3.62.206.1 software version and hboot is 1.54
Now can I s-on??
---------- Post added at 08:11 PM ---------- Previous post was at 07:26 PM ----------
nkk71 said:
If the phone looks "out of the box" to you then yes, ie no TAMPERED, says LOCKED (not RELOCKED), no red text "this a developer bla bla bla", has a stock ROM and a stock recovery, correct CID and MID, then by all means, YES.
Otherwise fix anything that might be out of order, and only as the VERY LAST STEP go back S-On.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Does the cimmitno-bootloader: dirty-d959c75800 mean that if I s-on it will brick the phone as well?
nkk71 said:
If you really need to go S-On again (though many people send in their phones with S-Off, cause some actually ship from HTC S-Off), here are the steps:
1- change CID & MID back to stock (in case you changed them)
2- remove TAMPERED using either revone or http://forum.xda-developers.com/show....php?t=2477792
3- change to LOCKED using either revone or http://forum.xda-developers.com/show....php?t=2475914
4- AFTER ABOVE use the correct RUU.exe for your phone; you will not loose S-Off because of the RUU
5- AFTER YOUR ARE 100% SATISFIED OF ABOVE RESULTS (ie no more tampered, bootloader LOCKED, 100% stock)
"fastboot oem writesecureflag 3" to get S-On.
Hit the thanks button if I helped
Click to expand...
Click to collapse
when I get back my phone from HTC service center,i can get soff my phone(hboot1.44) again using revone,right?
Sent from my HTC One using Tapatalk 2
Now that I have latest updates but all of different region. I'm from x.xx.707.x but I have x.xx.401.x Rom and bootloader. The bootloader is custom so it says developer edition phone. I have a backup of just rom of my stock version.
What would be the best way to go to stock now. My current hboot version is 1.55 custom and rom is 3.62.401.1. I have rom backup of 2.24.707.3 that had hboot of 1.54.
Sent from my HTC One using xda app-developers app
guys no need for s-on for warranty and don't go s-on cause there can be a problem to go back to s-off.Secondly if u r concerned abt the service just flash 1.29 ruu use revone remove tampered lock ur bootloader and ota ur way to 4.2 update.Many guys have given their one with s-off and they got through service without a hitch.Hell even im gonna go on monday to service center cause my camera module has gone kaput and a dead zone in the mid section of touchscreen but with s-off , bootloader locked and everything stock and the red text doesn't come after u lock the bootloader . So what's the problem ???
---------- Post added at 04:27 PM ---------- Previous post was at 04:15 PM ----------
coolshritz said:
Now that I have latest updates but all of different region. I'm from x.xx.707.x but I have x.xx.401.x Rom and bootloader. The bootloader is custom so it says developer edition phone. I have a backup of just rom of my stock version.
What would be the best way to go to stock now. My current hboot version is 1.55 custom and rom is 3.62.401.1. I have rom backup of 2.24.707.3 that had hboot of 1.54.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Be careful if u wanna go stock here's what u should do:
1.) First of all flash a non modified stock hboot doesn't matter what version but it should be unmodified since custom hboot can lead to hard brick when going back to stock.
2.) Now after flashing stock unmodified hboot just flash the 1.29 ruu use revone remove tampered if there lock bootloader and ota ur way to 4.2.2 the latest available for us indian users.But don't s-on cause its risky cause i don't know whether u can go back s-off after s-on so just leave s-off as it is.
That's it ur done
Slim Shady said:
guys no need for s-on for warranty and don't go s-on cause there can be a problem to go back to s-off.Secondly if u r concerned abt the service just flash 1.29 ruu use revone remove tampered lock ur bootloader and ota ur way to 4.2 update.Many guys have given their one with s-off and they got through service without a hitch.Hell even im gonna go on monday to service center cause my camera module has gone kaput and a dead zone in the mid section of touchscreen but with s-off , bootloader locked and everything stock and the red text doesn't come after u lock the bootloader . So what's the problem ???
---------- Post added at 04:27 PM ---------- Previous post was at 04:15 PM ----------
Be careful if u wanna go stock here's what u should do:
1.) First of all flash a non modified stock hboot doesn't matter what version but it should be unmodified since custom hboot can lead to hard brick when going back to stock.
2.) Now after flashing stock unmodified hboot just flash the 1.29 ruu use revone remove tampered if there lock bootloader and ota ur way to 4.2.2 the latest available for us indian users.But don't s-on cause its risky cause i don't know whether u can go back s-off after s-on so just leave s-off as it is.
That's it ur done
Click to expand...
Click to collapse
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
stovie_steve said:
Does the cimmitno-bootloader: dirty-d959c75800 mean that if I s-on it will brick the phone as well?
Click to expand...
Click to collapse
No it will not brick, it's always "dirty", no worries.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
coolshritz said:
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
Click to expand...
Click to collapse
Yes you are right, the "Tell HTC" part will have the red text with S-Off and will only go away when you're 100% stock and then set S-On.
coolshritz said:
Well, I directly flashed RUU zip that i got from htc1guru.com, it matched the cid and mid, that were stock. Flashed with no issues and updated it to 4.1.2 (Yet to do 4.2.2). I dont see red text in hboot, but in the "Tell HTC" section. I'm still S-off, bootloader locked. Is this normal?
I read somewhere that only S-On can remove that text. Is that true??
Click to expand...
Click to collapse
Yes It's solely because you're S-OFF. Your device has all security disabled, thus it acts like a test device. Once you go S-ON, the red text will immediately disappear. Well have u mended everything else except the s-off like remove tampered restoring mid and cid if changed.Update to 4.2.2 go to service center turn in ur device and if they by chance ask (generally they don't) abt s-off tell i don't know and it was like that only when u bought it and voila have ur phone repaired/replaced as the situation demands for it.
Going back s-on is really ur choice though not recommended cause if u get the same phone back repaired complications might arise in going back to s-off.
dingnangen said:
when I get back my phone from HTC service center,i can get soff my phone(hboot1.44) again using revone,right?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
yes, for hboot 1.44 (pre June 2013) you can use revone for 1.54 you can use rumrunner.
nkk71 said:
yes, for hboot 1.44 (pre June 2013) you can use revone for 1.54 you can use rumrunner.
Click to expand...
Click to collapse
I saw that : WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you will receive back a non-s-offable device... YOU HAVE BEEN WARNED
In this post : http://forum.xda-developers.com/showthread.php?p=45270020
Sent from my HTC One using Tapatalk 2
dingnangen said:
I saw that : WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you will receive back a non-s-offable device... YOU HAVE BEEN WARNED
In this post : http://forum.xda-developers.com/showthread.php?p=45270020
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I agree with the S-Off part, as some phones ship S-Off. The important parts are 100% stock rom, firmware, recovery, hboot; no TAMPERED or red text on boot. and LOCKED not RELOCKED.
However some people have been denied warranty because of S-Off (really depends on country, service center, and probably most important the person in the center).
As for "you will receive back a non-s-offable device" this is no longer the case since rumrunner can now achieve s-off on hboot 1.54 and 1.55.
It's locked, OTA 4.3 update with S-On but after i did this:"fastboot oem writesecureflag 3" to get S-On.
It's ***tampered*** again....
What to do, everything is back to stock now, no root..
nkk71 said:
I agree with the S-Off part, as some phones ship S-Off. The important parts are 100% stock rom, firmware, recovery, hboot; no TAMPERED or red text on boot. and LOCKED not RELOCKED.
However some people have been denied warranty because of S-Off (really depends on country, service center, and probably most important the person in the center).
As for "you will receive back a non-s-offable device" this is no longer the case since rumrunner can now achieve s-off on hboot 1.54 and 1.55.
Click to expand...
Click to collapse
it's means that if I get back my phone with 4.1(hb1.44,i will tell HTC don't update my system),I can also get soff using revone?
Sent from my HTC One using Tapatalk 2
Why did you do it when you already had S-On??
I just S-Offed with Firewater. I know in the past (maybe in the revone days), I read a lot of warnings about not going back to S-On because you might never be able to gain S-Off again. Is this still the case? I think I need to have my phone serviced, and I'm worried they might not replace it--in that case, I don't want to be stuck with a devie whose firmware I can't ever upgrade.
fenstre said:
I just S-Offed with Firewater. I know in the past (maybe in the revone days), I read a lot of warnings about not going back to S-On because you might never be able to gain S-Off again. Is this still the case? I think I need to have my phone serviced, and I'm worried they might not replace it--in that case, I don't want to be stuck with a devie whose firmware I can't ever upgrade.
Click to expand...
Click to collapse
S-OFF is hard to achieve on hboot 1.56. If you turn s-on on hboot 1.55 and above, the tampered flag will come back after a few reboot. So only s-on on hboot 1.44-1.54.
alray said:
S-OFF is hard to achieve on hboot 1.56. If you turn s-on on hboot 1.55 and above, the tampered flag will come back after a few reboot. So only s-on on hboot 1.44-1.54.
Click to expand...
Click to collapse
Thanks! So the biggest problem is that people S-Off, then upgrade hboot, then turn S-On again? I suspected that... sounds like the problem with people that convert their phone to GPe, and then relock their bootloaders.
I have hboot 1.54, so I guess I'm good to S-Off and S-On at will? Thanks!
Sure, that's a good HBOOT to start with if you want to S-OFF.
But just to get back to the original topic of this thread, it's not particularly "safe" to go S-ON. Ever.
The danger is not about whether it's easy to change your mind and go back to S-OFF later.
The larger danger is you can brick the phone (for real-- hard brick, truly dead phone) if your HBOOT has been modified or damaged at some point before you attempt S-ON.
Going back and forth between S-OFF and S-ON "at will" is just asking for trouble.
My personal policy is never S-ON for any reason. Not even warranty repair.
Sent from my HTC One using xda app-developers app
NxNW said:
The danger is not about whether it's easy to change your mind and go back to S-OFF later.
The larger danger is you can brick the phone (for real-- hard brick, truly dead phone) if your HBOOT has been modified or damaged at some point before you attempt S-ON.
Click to expand...
Click to collapse
Oh, that makes sense. And I see that, for example, modifying HBoot would make it pretty easy to make it so you can't ever root. So I'll cross "hboot mod" off my list of options.