/space
Updated! 3:44pm JSTI did some research online how get root on an Android HTC Thunderbolt. Hopefully this thread will fill any knowledge gaps and confirm any data previously acquired prior to going through a whole process. This has been converted from what was a question. It is not meant to replace similar threads but instead further elaborate more on this topic for those who still did not fully understand after reading elsewhere. Revolutionary does not work until after downgrading your phone. In the future this may change. Downgrading to an older ROM will wipe your phone. Save photos, files and important data on your computer before proceeding. I am not aware of there being any programs that will do this for you until you have root access.
Here is what I had found:
- Downgrade to 2.11.605.5.
- Revolutionary
- HTC's Bootloader Unlock
- Clockworkmod (after gaining root)
- Titanium Backup [PRO] (after gaining root)
My phone specs were (2012-02-23):
HBOOT: 1.04.0000
RADIO: 1.48.00.0930w_3
L. Kernel: 2.6.35.10-g89eb00a
Software number: 2.11.605.9
/space
What is root (all lowercase)? Basically root is the highest user in Linux as well as some other Unix-like/based OSs like Macintosh. You could think of it as Administrator if you are a Windows user.
/space
/space
I kept on reading after I had originally created this thread. I skipped the Official HTC method. It does not disable S-On. I downgraded to 2.11.605.5 then used Revolutionary. Afterward I installed the stock ROM 2.11.605.9 with root access. Thank you developers! I hope this helped those who were still confused after reading a bunch of information about gaining root access on your phone.
addictivetips: What Is S-OFF & How To Gain It On HTC Android Phones With unrevoked forever said:
S-OFF – What And Why?
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Click to expand...
Click to collapse
HTCdev: FAQs said:
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse
Stop OTA updates:
RootzWiki: temporalshadows said:
IIRC the update app is com.smithmicro.dm (dm means device management)
I have frozen this app on my phone with no ill effects.
Sent from my ADR6400L using RootzWiki
Click to expand...
Click to collapse
RootzWiki: BuffoGT (OP) said:
This is correct. You can also remove the dmclient.APK to remove it permanently
Click to expand...
Click to collapse
/space
/space
Install then use Titanium Backup PRO prior to installing the latest ROM 2.11.605.9 to prevent future data loss after a wipe. You can use ClockwordMod with Titanium Backup PRO. It is up to you if you want to or not. Here is one link: Android Police: Titanium Backup PRO can now restore applications from ClockworkMod 5 Backup. You can find many more additional resources about this and more online after performing a Google search. Thank you for reading!
/space
/space
/space
/space
/space
I am not an owner, affiliate or sponsor of the products and services listed above. I, nor xda-developers.com, is responsible for any damages caused to you, personal property, devices and or anyone else's after using any of the information provided in this thread. You, or whomever else acted out after reading what was written here, are solely liable for your actions. Always proceed with caution before carrying out any steps provided on this or any other website.
/space
/space
Related
Anyone wanna try this on slide http://unrevoked.com/rootwiki/doku.php/public/forever ?and see if it works so we can finaly use root explorer and metamorph.
Quote:
unrevoked forever is a tool to set your Android phone's security level toS-OFF. The security level is a flag stored on the radio; when the flag isS-OFF, the bootloader (HBOOT) will no longer check the signatures of firmware images before flashing them. This allows custom firmware images to be uploaded, including unsignedboot,recovery,splash1, andhboot images (as well as official images that have been modified). When the system isS-OFF, the NAND flash memory protection is also reduced; this allows all partitions (including/system) to be written to while the operating system is booted. The most substantial benefit of unrevoked forever is that the change is stored in the radio's NV memory; noENG bootloader is necessary to continue to flash firmware images. Even if an “unrootable” OTA update is accepted, a device on which unrevoked forever has been run will still be able to reflash a customrecovery image
lviv73 said:
Anyone wanna try this on slide http://unrevoked.com/rootwiki/doku.php/public/forever ?and see if it works so we can finaly use root explorer and metamorph.
Quote:
unrevoked forever is a tool to set your Android phone's security level toS-OFF. The security level is a flag stored on the radio; when the flag isS-OFF, the bootloader (HBOOT) will no longer check the signatures of firmware images before flashing them. This allows custom firmware images to be uploaded, including unsignedboot,recovery,splash1, andhboot images (as well as official images that have been modified). When the system isS-OFF, the NAND flash memory protection is also reduced; this allows all partitions (including/system) to be written to while the operating system is booted. The most substantial benefit of unrevoked forever is that the change is stored in the radio's NV memory; noENG bootloader is necessary to continue to flash firmware images. Even if an “unrootable” OTA update is accepted, a device on which unrevoked forever has been run will still be able to reflash a customrecovery image
Click to expand...
Click to collapse
Did you look at the supported devices? Only Incredible and EVO are supported at the moment.
r0man said:
Did you look at the supported devices? Only Incredible and EVO are supported at the moment.
Click to expand...
Click to collapse
Yup, but they also say "We believe the mechanism behind unrevoked forever may work for other radios and devices, and will add support as radio images are made available to us."
Maybe we can hook them up with what they need to get S-OFF on the Slide?
lviv73 said:
Anyone wanna try this on slide http://unrevoked.com/rootwiki/doku.php/public/forever ?and see if it works so we can finaly use root explorer and metamorph.
Quote:
unrevoked forever is a tool to set your Android phone's security level toS-OFF. The security level is a flag stored on the radio; when the flag isS-OFF, the bootloader (HBOOT) will no longer check the signatures of firmware images before flashing them. This allows custom firmware images to be uploaded, including unsignedboot,recovery,splash1, andhboot images (as well as official images that have been modified). When the system isS-OFF, the NAND flash memory protection is also reduced; this allows all partitions (including/system) to be written to while the operating system is booted. The most substantial benefit of unrevoked forever is that the change is stored in the radio's NV memory; noENG bootloader is necessary to continue to flash firmware images. Even if an “unrootable” OTA update is accepted, a device on which unrevoked forever has been run will still be able to reflash a customrecovery image
Click to expand...
Click to collapse
Why havent you tried it yet? Doesnt seem right that you want someone else to try this but you havent. YOU should try it and report back to this thread and let us know what happens
I checked out the current version of unrevoked forever, and they are exploiting a program that is only used on CDMA phones. It isn't likely to work with GSM radios.
falken98 said:
I checked out the current version of unrevoked forever, and they are exploiting a program that is only used on CDMA phones. It isn't likely to work with GSM radios.
Click to expand...
Click to collapse
Didnt know its cdma only
Damn it,Chiefz just bricked his Slide tryin to do this,i guess its safe to say this wont work.
Since Chiefz tried this i would say its for cdma and gsm phones.
lviv73 said:
Damn it,Chiefz just bricked his Slide tryin to do this,i guess its safe to say this wont work.
Since Chiefz tried this i would say its for cdma and gsm phones.
Click to expand...
Click to collapse
or since he bricked it, maybe just CDMA?
We should donate to Chiefz for new slide cuz he definitely put in alot of work.
Here is a link for those that can donate https://www.paypal.com/us/cgi-bin/w...63663d3faee8d66edfb0b39be7838c6fe2b48d77d66ee .
NOTE: he dint ask for donations.
ChiefzReloaded RT @brownboyrx: Okay guys hes not gonna ask,
but I will! @ChiefzReloaded bricked his slide ... Click the link http://t.co/e51mlnS RT!
lviv73 said:
Damn it,Chiefz just bricked his Slide tryin to do this,i guess its safe to say this wont work.
Since Chiefz tried this i would say its for cdma and gsm phones.
Click to expand...
Click to collapse
If he was using the unrevoked forever method, the exploit is using something that is only for CDMA phones. I had wondered if it could communicate with the GSM radio as well.
If that is what did brick his phone, then the answer is yes, it can communicate with the GSM radio. Obviously not correctly out of the box however. As it bricked it.
Edit: I would be more than happy to donate for a new slide, however, as part of me wanted to try it but didn't want to risk a brick.
I have been noticing quite a few people asking, not just from HTC desire x sections but others as well, what s-off/on or cid is.
Here is what it is.
Info taken from here : http://forum.gsmhosting.com/vbb/f485/understanding-s-off-super-cid-s-read-b4-u-run-ruu-1505916/
S-ON, many users attempt at running ruu's on their devices without finding out if it will prompt an error or the restore will be successful.
Htc phones are protected and secured with this.
This prevents you from installing any ruu older than what you have in phone. e.g if your device came came with firmware version 2.33, you can only install 2.33, 2.34, 2.35 and above not below this value.
The ruu will return an error "get the correct rom for your device".
In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to.
The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root.
Furthermore, signature check for firmware images is also ensured by the S-ON flag.
S-OFF
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON.
Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory.
This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory.
However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
SUPER CID
Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky).
You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have.
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for.
HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed.
While SuperCID may seem handy, note that if you are only interested in debranding your phone, the OTA (over the air) updates which HTC sends will not be available for your phone, since there is no specific region defined.
So, in such cases, you should choose a specific CID for your region.
That's it.
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.
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.