Related
Source @Koush (Original Article)
Source @HTCDev (Original Article)
Bootloader Locking, Unlocking, S-On, S-Off - Questions and Answers
It seems this is confusion in the community about what S-OFF is and why it's needed on some phones but not others. I endevour to educate and explain why some HTC devices need S-OFF while others do not to Flash Roms and recovery images.
[Q] What does S-ON/S-OFF mean? Is it on all phones?
[A] This is Manufacturer specific to HTC branded devices ONLY. S-On and S-Off means Security On/Security Off. HTC devices are set to S-ON by default for a good reason. There are partitions such as hboot which controls access to all other partitions which if made fully accessible could compromise security and very possibly allow for irreversible changes that could render your device inoperable. For warranty and device support purposes alone it would be to your benefit to keep Security-ON. Another partition that is secured is the radio. It is not advisable to alter or customize the radio and most custom roms will not need to. The radios are fine tuned to the specific carrier(s) they are designed to support and with the specifications as prescribed by law. Moreover altering them may not only also cause irreparable damage to your device but it could very well interfere with the normal communications possibly affecting other devices.
[Q] What does Unlock mean in the bootloader flag?
[A] What is meant by unlocking the bootloader is that certain partitions are unlocked to provide write access without turning device security off for all partitions. Specifically: Kernel, system and recovery partitions are allowed to be modified. There are more partitions (e.g. the radio and hboot) but these are the minimal necessary to overwrite a default stock rom with a custom built Android based rom.
[Q] Then why do Devs ask for S-OFF when flashing a Rom?
[A] Some carriers lock down the ability to Unlocked the partitions. For example US customers of Verizon are unable to use HTCDev to unlock their devices to access the needed partitions for Custom Rom and Recovery writing. In this Case S-OFF fixes this issue but also unlocks ALL partitions for writing. A Verizon phone with S-OFF will have the ability to now write to the Recovery and Boot partitions.
Devs ask for S-OFF for multiple reasons:
1. So that Devices Restricted by HTCDev whom normally can't get write access to the Boot and Recovery Paritions can use there ROM
2. Because forum behavior made S-Off appear to be needed
3. Laziness and/or ignorance (not trying to be rude)
[Q] So do I really need S-OFF to install ROMS or Recovery Images?
[A] Yes, If you have a HTCDev Restricted Device which will not allow you to use a Unlock Token you will need to S-OFF in order to write to your boot/system/Recovery partitions. NO, if you have a devices that can be unlocked using HTCDev Token to Unlock your device.
[Q] So Unlocking my devices has nothing to do with S-ON/S-OFF?
[A] A tricky question. Yes Unlocking a None Carrier restricted device with HTC Dev has Nothing to do with the Security of the Device from the S-OFF/S-ON perspective. If your on a Carrier Restricted HTCDev devices (I.E. Verizon HTC One Max) then in order to Write to the Partitions you need to you will need to be S-OFF as that is the only way to Unlock the bootloader.
[Q] So why do I need to Change my Bootloader Flag to get some things working?
[A] The short answer is that some hardware in the HTC Phones are told to look into the Security Partition to determine if the phone is Locked or Unlocked for Development. As an example on the HTC One Max the Fingerprint Reader will be disabled if the Bootloader Flag is set to "Unlocked" but function if the Flag is Set to "Locked". When your Bootloader is Flagged "Locked" the partitions are not accessible and will prevent Recovery and Boot Partition Modifications.
[Q] What if I want to return my device for warranty work how can I return it to S-ON and Locked Status?
[A] You will need to find your Model Phones RUU and Restore your phone to it original stock state. The RUU is used to restore a device to its Factory State. See the Question below about S-ON.
[Q] I would like to know if its still possible to achieve s-on after you have turned it off specially using the Rumrunner tool as I am Verizon device?
[A] Consumers that use Rumrunner to S-OFF will have the option of turning Device Security ON again. This typically is not a deal breaker for Warranty repairs if you restore the device software (Recovery, Room) back to it's default stock state and flag the bootloader Locked again as some devices are shipped S-OFF. It has been accomplished on the HTC One by running a command in Fastboot mode.
HTC One users achieve S-ON again by running this command with fastboot. I have not yet confirmed it works on the HTC One Max. (Note: If you are trying to return to a out of the box state use your device's RUU after S-ON to restore the Recovery, Kernel and Rom to Stock with a Encrypted/Signed RUU then run the command below) (If you want to test and report back on the HTC One Max please let us know.
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
[Q] What is the difference between an Encrypted RUU vs Decrypted RUU?
[A] A Encrypted RUU is a RUU file that has been signed by HTC (Carrier or Country). Encrypted RUU's can be run on S-ON or S-OFF devices to restore the device. A Decrypted RUU is a RUU that has had the signature stripped(in case of JB or older RUU's) and these can be typically ONLY run on S-OFF Devices. (Be careful to use the RUU for your device as these are hardware specific)
In conclusion:
S-OFF/S-ON is conditional based on your HTC device and carrier restrictions. If you are not able to unlock your partitions with HTCDev due to Carrier restrictions or country restrictions then S-OFF is you alternative.
If you can unlock your phones bootloader then you can flash kernels, roms and recovery images with S-ON. S-OFF is ONLY needed on devices that want full Partition access and/or HTCDev will not allow to unlock.
Do you you have a question? Reply with your question on this thread about S-ON/S-OFF/Bootloader Security. NOTE: This is not a General Question Thread.
P.S.
Please remember that unlocking your bootloader may void all or parts of your warranty and your device may not function as intended by HTC. Unlocking the bootloader is for development purposes only.
DeadPhoenix said:
[Q] So why do I need to Change my Bootloader Flag to get some things working?
[A] The short answer is that some hardware in the HTC Phones are told to look into the Security Partition to determine if the phone is Locked or Unlocked for Development. As an example on the HTC One Max the Fingerprint Reader will be disabled if the Bootloader Flag is set to "Unlocked" but function if the Flag is Set to "Locked". When your Bootloader is Flagged "Locked" the partitions are not accessible and will prevent Recovery and Boot Partition Modifications.
Click to expand...
Click to collapse
Thank you for researching and providing answers.
This is very informative, sure would be nice if us on Verizon could just unlock instead of having to go s-off. I came from the Rezound where we could just unlock, but oh well such is the way it goes.
mods should sticky this thread, as it answers alot of newbie questions..
great write up,not much to add at all
on carrier restricted phones,s off is neccessary to unlock the bootloader,but the device does not need to remain s-off. one could even legitimately unlock via htcdevs website if the cid or mid is changed after achieving s off. after htcdev unlock is achieved,you techincally could turn the radio secure flag back on,but please dont do it. with a lack of signed ruus,doing so could leave you in an unrecoverable jam. i just wanted to clarify that the the functionality of the device itself does not need the secure flag to be off.
while it may not be "needed",it is my personal opinion s-off is better. at least as long as youre a responsible individual who is capable of learning,and exercising good judgment as to what to flash and why,and is able to check the integrity of any downloaded files that could potentially leave the phone unusable(for example,anything that contains a bootloader,as a bad bootloader flash will leave you unrecoverably bricked)
being s off offers many safety advantages:
-you can flash an unsigned ruu to get your device "unbricked"
-you can install older ruus if needed
-you can install a "patched" or engnieering hboot to gain the use of extra fastboot commands
-it lets you dump and modifiy partitions you couldnt with an s on device
not to mention,it lets you eliminate the telltale relocked watermark that lets htc or your carrier know that you have messed with your phone
its also an awsome safety net for those of us who run stock in order to capture OTA packages that provide upgrade firmware and provide rom devs with files to create new custom roms,and update their current versions.
sure staying s on techncally will keep you from accidentally overwriting your bootloader with the "lets golf" .apk, if you find yourself in a bind with a non booting phone and no signed ruu to run,being s on offers no advantage whatsoever.
Scotty, so what you are saying is even if I am S-OFF I can still get the OTA updates from Verizon, like hopefully the Kit Kat update? I was wondering because I was wanting to try the Viper rom as I loved that on my Rezound but didn't want to miss the official Kit Kat.
JBS976 said:
Scotty, so what you are saying is even if I am S-OFF I can still get the OTA updates from Verizon, like hopefully the Kit Kat update? I was wondering because I was wanting to try the Viper rom as I loved that on my Rezound but didn't want to miss the official Kit Kat.
Click to expand...
Click to collapse
The Function of Device Security (S-OFF and S-ON) is to Lock or unlock ALL partitions.
OTA updates are signed by the carrier. So Running Stock Roms will allow the Stock updates from Verizon to work. If your running a Custom Rom then this is dependent on the Rom creator. In most cases OTA updates are not delivered to devices running Custom Roms.
JBS976 said:
Scotty, so what you are saying is even if I am S-OFF I can still get the OTA updates from Verizon, like hopefully the Kit Kat update? I was wondering because I was wanting to try the Viper rom as I loved that on my Rezound but didn't want to miss the official Kit Kat.
Click to expand...
Click to collapse
dont worry about getting the kit kat update; once its actually released, the great dev's here will make it work for our rooted/unlocked phones!
Thank you for your reply DeadPhoenix, I am mostly concerned with getting the official updates from VZW/HTC. I am understanding that if I just use Rumrunner to S-OFF and stay completely stock I will still receive them, now what about putting TWRP on? Will that affect the ability to receive the updates? Thanks again for answering my questions as I'm sure you tire of getting these noob type questions, but I really appreciate the time you all put into this stuff and taking the time to answer.
generally speaking, you can NOT get OTA updates when you have a custom recovery installed..
wase4711 said:
generally speaking, you can NOT get OTA updates when you have a custom recovery installed..
Click to expand...
Click to collapse
Correct. An OTA update relies on the fact that you have a stock Recovery installed as that is the expected delivery method for their scripting.
DeadPhoenix said:
Correct. An OTA update relies on the fact that you have a stock Recovery installed as that is the expected delivery method for their scripting.
Click to expand...
Click to collapse
thanks teacher, I didnt know this was a quiz! :cyclops:
ok.. so I now fully understand what an s-off and s-on mean, however, I would like to know if its still possible to achieve s-on after you have turned it off specially using the rumrunner tool as I am verizon device?
is there a security risk if I kept s-off and have restored back to Verizon's RUU and have locked the bootloader?
afsandiego said:
ok.. so I now fully understand what an s-off and s-on mean, however, I would like to know if its still possible to achieve s-on after you have turned it off specially using the rumrunner tool as I am verizon device?
is there a security risk if I kept s-off and have restored back to Verizon's RUU and have locked the bootloader?
Click to expand...
Click to collapse
Thank you for asking this. These are exactly the questions I know exist out there and would like truly "knowledgeable" people to answer.
afsandiego said:
ok.. so I now fully understand what an s-off and s-on mean, however, I would like to know if its still possible to achieve s-on after you have turned it off specially using the rumrunner tool as I am verizon device?
is there a security risk if I kept s-off and have restored back to Verizon's RUU and have locked the bootloader?
Click to expand...
Click to collapse
From the research I have done with Android/Linux Partition Table Devs and HTCDev directly I derived the following:
The RUU just restores the software to the Factory state. S-OFF is desired however you can use the fastboot command to turn it on in theory. You can S-ON again however this isn't usually a deal breaker for warranty repair as long as you restore the kernel, recovery and Rom to stock. But your mileage may vary with HTC.
Thank you for your question.
Sorry but I believe flashing an encrypted ruu will actually s-on your device. The ruu's we have are decrypted and likely have been provided as they are so that no one fully s-on locks their device again
* fastboot oem writesecureflag 3 will s-on after flashing full stock ruu. Do not attempt if you do not know what you are doing!
As always I am happy to be corrected. Just really want the complete correct information out there, not just as it relates to our device.
---------- Post added at 02:37 PM ---------- Previous post was at 02:27 PM ----------
My apologies if my response seems like an ambush as I posted something earlier. I was just happy others were taking an interest then just did not have a chance to get back to this until a moment ago.
Jiggity Janx said:
Sorry but I believe flashing an encrypted ruu will actually s-on your device. The ruu's we have are decrypted and likely have been provided as they are so that no one fully s-on locks their device again
* fastboot oem writesecureflag 3 will s-on after flashing full stock ruu. Do not attempt if you do not know what you are doing!
As always I am happy to be corrected. Just really want the complete correct information out there, not just as it relates to our device.
---------- Post added at 02:37 PM ---------- Previous post was at 02:27 PM ----------
My apologies if my response seems like an ambush as I posted something earlier. I was just happy others were taking an interest then just did not have a chance to get back to this until a moment ago.
Click to expand...
Click to collapse
I will attempt to get this clarified as it seems we are seeing 2 different answers and I want this to be as accurate as possible.
DeadPhoenix said:
I will attempt to get this clarified as it seems we are seeing 2 different answers and I want this to be as accurate as possible.
Click to expand...
Click to collapse
Agreed. Source: http://forum.xda-developers.com/showthread.php?t=2475216
Jiggity Janx said:
Agreed. Source: http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
From the Feedback I have gotten so far. They explicitly state RUU's do not turn S-OFF to S-ON however in the directions you sourced a command is run outside of the RUU to turn it on.
(Still awaiting several replies to queries.)
This Appears to be the fastboot command to run AFTER the RUU has restored but before a normal boot but is Not part of the RUU process itself.
This is also if CID is modified from what I gathered thus far. (Feel free to correct)
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
DeadPhoenix said:
From the Feedback I have gotten so far. They explicitly state RUU's do not turn S-OFF to S-ON however in the directions you sourced a command is run outside of the RUU to turn it on.
(Still awaiting several replies to queries.)
This Appears to be the fastboot command to run AFTER the RUU has restored but before a normal boot but is Not part of the RUU process itself.
This is also if CID is modified from what I gathered thus far. (Feel free to correct)
Click to expand...
Click to collapse
Did you ask 'them' specifically about flashing stock encrypted htc ruu's? I am digging more but believe the encrypted ones have the writesecure flag already set to 3(s-on). Encrypted ruus would be what htc has given manufacturers to install on phones before shipping them to vendors.
Also you would want your device to be completely stock (no changed cid) before using fastboot to s-on. You would use this command after flashing a decrypted (but still completely stock) ruu.
I unlocked via the htc site, rooted running a gpe rom (not the conversion)
I know that s-off can grant a completely unlocked phone. But i dont really need that. I guess what I'm trying to ask is, what are the advantages? Im not into xposed or gravity box and i dont need my phone carrier unlocked.
will my lack of s-off hinder me from flashing radios and/or newer versions of twrp?
if someone can break this down for me, I would appreciate it
S-off isn't needed to:
- Flash TWRP
- To achieve root
- Flash ROMs
S-off benefits:
- Needed to flash radios (SuperCID also needed to flash a radio that does not match your version)
- Needed to SIM unlock
- Needed to flash modified hboot (such as to remove the red warning text form boot screen)
- Needed to flash firmware components (not the ROM)
- Allows you to run any RUU (other carriers, or even previous RUUs, which is not normally allowed by version check)
The last one is important, since s-off essentially gives you more recovery options if things go south.
But s-off means all security checks are off by definition. This even includes device check, which means flashing a ROM or mod for another device is possible. I've seen folks flash a ROM for a different device with s-off, and brick their phones (due to different partitioning, etc.). As long as you are very careful to only flash things intended for our device, you will be fine. But anyone with s-off (or interested in s-off) needs to understand this.
sheek360 said:
I unlocked via the htc site, rooted running a gpe rom (not the conversion)
I know that s-off can grant a completely unlocked phone. But i dont really need that. I guess what I'm trying to ask is, what are the advantages? Im not into xposed or gravity box and i dont need my phone carrier unlocked.
will my lack of s-off hinder me from flashing radios and/or newer versions of twrp?
if someone can break this down for me, I would appreciate it
Click to expand...
Click to collapse
I'm new to HTC coming from Samsung but I believe for a permanent Uninstall on system apps you need S-OFF. Freezing bloat doesn't always do it for me. Some junk I'd just rather get rid of it.
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
S-off isn't needed to:
- Flash TWRP
- To achieve root
- Flash ROMs
S-off benefits:
- Needed to flash radios (SuperCID also needed to flash a radio that does not match your version)
- Needed to SIM unlock
- Needed to flash modified hboot (such as to remove the red warning text form boot screen)
- Needed to flash firmware components (not the ROM)
- Allows you to run any RUU (other carriers, or even previous RUUs, which is not normally allowed by version check)
The last one is important, since s-off essentially gives you more recovery options if things go south.
But s-off means all security checks are off by definition. This even includes device check, which means flashing a ROM or mod for another device is possible. I've seen folks flash a ROM for a different device with s-off, and brick their phones (due to different partitioning, etc.). As long as you are very careful to only flash things intended for our device, you will be fine. But anyone with s-off (or interested in s-off) needs to understand this.
Click to expand...
Click to collapse
Thanks for the explanation
Bsmith0731 said:
I'm new to HTC coming from Samsung but I believe for a permanent Uninstall on system apps you need S-OFF. Freezing bloat doesn't always do it for me. Some junk I'd just rather get rid of it.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
you only need r/w access to completely unistall apps.
I'm aware of the OTA update next week that'll update me to Sense 6.
Currently displays in recovery:
Tampered
Unlocked
S-OFF
Currently on stock 4.4.2 rooted, no other kernel changes, etc. but the ROM I'm using has custom black boot screens added (literally just black instead of default white boot background).
Rooting is nice and all but getting tired and would just like to revert to pretty much locked bootloader, unrooted, factory condition, etc. and be able to also do OTA for future updates.
Any help is appreciated. Baby steps please.
Anyone?
First, relock your bootloader. To do that, start your phone in bootloader mode, connect your phone to pc via usb cable and type "fastboot oem lock" on command prompt. Next, download the proper ruu exe file from htc1guru.com. By proper,I mean the one that matches your phones actual model number and custom id. Execute the ruu while connecting your phone to pc in fastboot mode. Follow the on screen instructions and when finished, you will have s phone that says re locked and s-off. You will get ota in this condition and will be able to install ota and upgrade to Sense 6.0 without any problems.
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
SaHiLzZ said:
If you are only rooted with stock ATT software, unroot using the SuperSU app, make sure you have stock recovery, and you are golden. DO NOT turn S-ON, and also no need to lock bootloader, as with S-OFF, you will get updates with unlocked bootloader
Click to expand...
Click to collapse
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Yes you can flash the decrypted ruu. It is the same as using the ruu exe.
If you haven't changed your mid and/cid,then what you need to is just lock the bootloader and flash the ruu (zip or exe). You will be on stock with s-off which is fine for getting ota.
Yes you can convert to developer edition. The DE and the at&t version are the same hardware-wise (except DE have 64gb storage instead of 32gb on at&t version) and have the same radio bands. You will get faster Android upgrades with no at&t bloats.
mch277 said:
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Click to expand...
Click to collapse
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
mb_guy said:
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
Click to expand...
Click to collapse
My understanding is that, if there's any modification in system files, applying OTA may result in a bootloop/brick. I agree that rooted devices remain rooted after OTA. As the OP said that s/he us using a rom with modified boot animation, I suggested him/her to return to stock first.
Hi I basically want to trade in my HTC desire 610 (EU addition) at CEX.
It is currently S-ON, deodexed & modified stock rom with JMZ kernel.
I want to be able to unroot and relock bootloader without signs of tampering as I will get less for it if they find it has been rooted.
I am fine to flash an odexed stock rom (im pretty sure there is one in the dev thread), but does anyone know how to get the bootloader back to its original state, when I have tried with other phones it always says "re-locked" instead of locked and is obvious it has been tampered with.
Any ideas?
W1LD3G30RG3 said:
Hi I basically want to trade in my HTC desire 610 (EU addition) at CEX.
It is currently S-ON, deodexed & modified stock rom with JMZ kernel.
I want to be able to unroot and relock bootloader without signs of tampering as I will get less for it if they find it has been rooted.
I am fine to flash an odexed stock rom (im pretty sure there is one in the dev thread), but does anyone know how to get the bootloader back to its original state, when I have tried with other phones it always says "re-locked" instead of locked and is obvious it has been tampered with.
Any ideas?
Click to expand...
Click to collapse
You can do "fastboot oem lock" to re-lock the bootloader. This will change it from saying "unlocked" to "Locked". However it will still say "Tampered" above it and there is no way to get rid of that once it has been unlocked.
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it. I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
My device has S-ON from what I saw on HBOOT, is using the Skydragon custom kernel, and I'm using TWRP custom recovery. I still have the RUU I downloaded from AT&T to return my device to stock 5.0.2 firmware. My question is, shall I just run the RUU and it will all be back to stock? Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have. Could anyone point me in the right direciton? thanks!
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
sarxion said:
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it.
Click to expand...
Click to collapse
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
sarxion said:
I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
Click to expand...
Click to collapse
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
sarxion said:
My question is, shall I just run the RUU and it will all be back to stock?
Click to expand...
Click to collapse
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
sarxion said:
Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
Click to expand...
Click to collapse
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
sarxion said:
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have.
Click to expand...
Click to collapse
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
redpoint73 said:
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
Click to expand...
Click to collapse
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy, or don't apply, such as this one that requires S-OFF http://forum.xda-developers.com/showthread.php?t=2708571
sarxion said:
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Click to expand...
Click to collapse
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
sarxion said:
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy
Click to expand...
Click to collapse
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
redpoint73 said:
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
Click to expand...
Click to collapse
Thank you very much. So I can run the RUU with my M8 on bootloader mode? Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel. (I'll be running the exact same RUU version I ran before installing the custom rom)
sarxion said:
So I can run the RUU with my M8 on bootloader mode?
Click to expand...
Click to collapse
The RUU will run with the phone in bootloader-fastboot mode, yes.
sarxion said:
Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel.
Click to expand...
Click to collapse
That is correct. And in fact, as far as I know, the phone is rendered unable to boot into OS after relocking the bootloader, even if you were on the stock ROM.
OP,
Were you able to go back to stock?