I tried to use the HTC dev method to root my phone. (Stupid, I know, I should have read more into it). However, I only got as far as unlocking it. http://forum.xda-developers.com/showthread.php?t=1225974 <- I got up to step 17.
So my question is, when the Revolutionary method is changed to work for 1.50 Hboot (which I have) will this affect my ability to fully root my device? My phone is now unlocked, so will I have to do something different to root it later?
Yntamin said:
I tried to use the HTC dev method to root my phone. (Stupid, I know, I should have read more into it). However, I only got as far as unlocking it. http://forum.xda-developers.com/showthread.php?t=1225974 <- I got up to step 17.
So my question is, when the Revolutionary method is changed to work for 1.50 Hboot (which I have) will this affect my ability to fully root my device? My phone is now unlocked, so will I have to do something different to root it later?
Click to expand...
Click to collapse
Short answer: If your phone is unlocked, you can provide root access now.
Long answer: To provide some clarification of terms:
1) rooting or root provides superuser access to the device
2) HTC unlock/revolutionary provide write access to the internal memory.
Details: Revolutionary's approach, specifically their methods and code are all closed. HTC's approach is also very closed.
Due to the closed nature of Revolutionary's and HTC's work, it is near impossible to predict how these approaches would work on top of each other. If I were to speculate, I would think these approaches *could* be mutually exclusive or if done on top of each other, revolutionary's approach would unlock more internal memory write access than HTC's.
After providing this information, to circle back to your original questions, if you have unlocked the internal memory write protection, you can provide a permanent root solution now. You don't need to wait for anything in the future.
I've taken a fairly narrow, specific, and high level approach to answering your question w/o making any assumptions as to the depth of your knowledge.
If you have any other questions, please post and we'll do our best to answer!
Hope that helps!
So what should I do? I'm not able to finish with HTC's method. Will the Revolutionary way work now?
If you have a HBOOT 1.5 then no you cant use the Revolutionary Unlock method as it onlys supports HBOOTS 1.3 & 1.4. If you want root access with a 1.5 HBOOT you will have to use the HTC unlock method for now. If you have a 1.3 or 1.4 HBOOT then yes you should be able to root using the Revolutionary hack.
Related
I rooted mine with the very first one that came out, but with their being 2 known methods (Evo4GLTERoot & RegawMOD), I'm wondering if one method is preferred over another for any particular reason. I take it both are compatible with LazyPanda's S-OFF utility, but noticed many have issues with different things which makes me wonder if the different root methods have anything to do with that.
I am wondering so that in the even that I ever unroot my phone and need to root it back, which option would be better. Currently though, I'm trying to hold out on any more changes until the new firmware is self-rootable (not having to flash a ROM)
Also, is there any way to remove *** TAMPERED *** off the device if you don't want to S-OFF ?
I rooted using both methods EVO4GLTE ROOT and RegawMOD as I had issues with the token for HTC bootloader unlock.
Once you root it says -TAMPERED- for now it's permanent, I'm sure that someone will find a “fix" if high enough demand. Look at is ur badge for unlocking full access to ur phones potential.
Sent from my EVO using Tapatalk 2
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
It seems to me that we would first need a modified bootloader or /system to attempt to flash, but I doubt "fastboot erase ..." is allowed without dev unlock on the bootloader, and "fastboot flash ..." most likely needs a signed image.
Does anyone with more expertise on this topic have any input?
JaSauders said:
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
Click to expand...
Click to collapse
What those tools do is use an exploit to write the su and superuser.apk to /system and/or a modified recovery for flashing ROMS and kernels on unlocked bootloader devices.
google has properly patched those exploits as they should as we don't want a malicious app installing Root and hacking data on just anyone's phone.
Some phones with locked bootloaders have had exploits to install custom recovery and/or hacked/leaked bootloaders in order to allow us to use the phone like it was unlocked. HTC fixed this issue with their latest phones.
Their bootloaders now do not run all of the adb commands until unlocked by HTC dev, which limits us a lot. They also made it so that even if we DID manage to find a software exploit and start flashing stuff, the locked bootloader would know, via a signature check, that something was modified... and refuse to boot (Bricked Phone).
HTC Dev unlock is not true unlock either. We still can't modify the HBOOT w/o triggering it to brick the phone. An unlocked HTC bootloader limits changing the kernel to HBOOT mode only, which means u need a PC and extra steps to finish flashing any ROM.
Some brilliant Dev's managed to use RUU files to update the kernel only, but that also causes issues. If one Dev uses a newer RUU, you can't use the another Dev's older RUU to flash a kernel because the unlocked HTC Bootloader doesn't allow you to "Downgrade" firmware. This leads to headaches with people ignoring the kernel step and screaming because their phone won't boot.
The ultimate Holy grail for is is what is known as "S-OFF"
This allows full access to the HBOOT Recovery and system for all of our awesome devs to work their magic. This was obtained (long after HTCDev unlock) with the Rezound only through a HARDWARE exploit. We needed root exploit (which we had on the GB stock ROM), and to physically short out a pin on the mainboard to ground at precise times while the SOFF program ran on your PC.
We have to wait for the less popular HTCDev unlock (which HTC Did give us on the rezound with a middle finger to verizon), or for some1 to find another Exploit that would bypass the signature check of the HBOOT and give us "S-OFF".
Either will give us Root, custom recoveries, and ROMs.
I am no dev, but this is my understanding of what's happening with these devices. This is my 9th android device, 5th HTC, but I am always learning more. Dev's feel free to correct me, or expand on anything I have written here ^^
Is there? i cant find any solution and i tried several tools.
Or way to unlock after OTA to ics without getting back to gingerbread and using revolutionary. And not the official way..
thx
jojkos said:
Is there? i cant find any solution and i tried several tools.
Or way to unlock after OTA to ics without getting back to gingerbread and using revolutionary. And not the official way..
thx
Click to expand...
Click to collapse
Are you GSM or CDMA?
I'm not sure exactly what you are trying to accomplish, but if your phone is the CDMA model and you've never unlocked your bootloader you can get S-OFF and then root without unlocking the bootloader using the Revolutionary method in closeone's thread in the stickies of the CDMA development forum. Some people have even gotten it to work with the Sprint ICS (2.89.651.2) build installed, but it requires "bricking" the phone twice.
OTOH, the JuopunutBear S-OFF method resets the bootloader status from "unlocked" to "locked" so there is no indication on the phone that you ever did the HTC unlock, and that works for both GSM and CDMA.
It sounds like you've already done some homework so you must have a specific reason for wanting to do it another way?
ramjet73
ramjet73 said:
Are you GSM or CDMA?
I'm not sure exactly what you are trying to accomplish, but if your phone is the CDMA model and you've never unlocked your bootloader you can get S-OFF and then root without unlocking the bootloader using the Revolutionary method in closeone's thread in the stickies of the CDMA development forum. Some people have even gotten it to work with the Sprint ICS (2.89.651.2) build installed, but it requires "bricking" the phone twice.
OTOH, the JuopunutBear S-OFF method resets the bootloader status from "unlocked" to "locked" so there is no indication on the phone that you ever did the HTC unlock, and that works for both GSM and CDMA.
It sounds like you've already done some homework so you must have a specific reason for wanting to do it another way?
ramjet73
Click to expand...
Click to collapse
i forgot to mention, my bad. I have GSM. I didnt want to loose warranty because of the official method, but if you say that there is a way to revert it (i thought they would keep record of me unlocking phone but i dont really know), then it would be ok to unlock it that way. Also i wanted to know if ther is easy and fast way to make root/temp root so i could only do a backup.
jojkos said:
i forgot to mention, my bad. I have GSM. I didnt want to loose warranty because of the official method, but if you say that there is a way to revert it (i thought they would keep record of me unlocking phone but i dont really know), then it would be ok to unlock it that way. Also i wanted to know if ther is easy and fast way to make root/temp root so i could only do a backup.
Click to expand...
Click to collapse
If you htcdev unlock, HTC will know that you requested a token, but not whether you actually unlocked or not. I'm not sure how they handle that for the purpose of warranty claims, but maybe someone else here has experience with that.
Regarding temp root, it's possible, but not on the the ICS releases since HTC has patched the vulnerablility used for the "tacoroot" method. I've also heard that the phone is very unstable while temp rooted and sometime won't boot. You might be better off using a tool like MyBackup Pro that doesn't require root and has a 30 day trial with full functionality.
ramjet73
ramjet73 said:
If you htcdev unlock, HTC will know that you requested a token, but not whether you actually unlocked or not. I'm not sure how they handle that for the purpose of warranty claims, but maybe someone else here has experience with that.
Regarding temp root, it's possible, but not on the the ICS releases since HTC has patched the vulnerablility used for the "tacoroot" method. I've also heard that the phone is very unstable while temp rooted and sometime won't boot. You might be better off using a tool like MyBackup Pro that doesn't require root and has a 30 day trial with full functionality.
ramjet73
Click to expand...
Click to collapse
well thank you very much for all your help i think ill try htcdev unlock method
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.
Ok I have 2.49 and no money to buy sunshine at the moment. Is there a way to root and install recovery without S-off? I am on 2.49 Hboot. Verizon HTC Max
very much so sir! i m not sure about carrier versions like your verizon device, but i am using the international one max...and the outline of the procedure is standard and you can find many tutorials on it. here it is briefly:
1. goto htc's dev site, register your device as a dev device, and you will get an unlock code
2. use the unlock code to quickly unlock the bootloader
3. with bootloader unlocked, you can flash any recovery you want
4. with recovery, you can flash the superuser or supersu packages to root
thats it!
s-off gives you some more flexibility, but its not necessary for most modding/tinkering purposes. i have done all but s-off, and haven't yet found a compelling use case for myself in which i would be forced to get s-off...so far!
all the discussions you see on the forum talking about troubles with hboot 2.49 are in the context of achieving s-off. hboot 2.49 does NOT keep you from unlocking bootloader and all that jazz. its specifically a hurdle in the steps to achieve s-off.
finally, there are some doubts about htc's stated versus effective policy regarding warranty status of devices that have received unlock codes from htc's dev site. might want to read up about the pros and cons if you want to be sure about the effect of the bootloader unlocking steps on your warranty.
edit: and i'll also mention here for completeness that unlocking bootloader disables the fingerprint scanner. as always, theres a lot of topics/discussions here on the forum about all the details. i believe the consensus is to lock the bootloader AND clear the "tampered" flag. some say the bootloader status must be "locked" as opposed to "relocked", which is where s-off might become necessary...or some such! haven't quite done any steps yet to enable my fingerprint scanner. don't want to hijack your thread, but that would be my next question if i was you and had just read my post!
Sent from my HTC One max using XDA Free mobile app
ASCIIker said:
very much so sir! i m not sure about carrier versions like your verizon device, but i am using the international one max...and the outline of the procedure is standard and you can find many tutorials on it. here it is briefly:
1. goto htc's dev site, register your device as a dev device, and you will get an unlock code
2. use the unlock code to quickly unlock the bootloader
3. with bootloader unlocked, you can flash any recovery you want
4. with recovery, you can flash the superuser or supersu packages to root
thats it!
s-off gives you some more flexibility, but its not necessary for most modding/tinkering purposes. i have done all but s-off, and haven't yet found a compelling use case for myself in which i would be forced to get s-off...so far!
all the discussions you see on the forum talking about troubles with hboot 2.49 are in the context of achieving s-off. hboot 2.49 does NOT keep you from unlocking bootloader and all that jazz. its specifically a hurdle in the steps to achieve s-off.
finally, there are some doubts about htc's stated versus effective policy regarding warranty status of devices that have received unlock codes from htc's dev site. might want to read up about the pros and cons if you want to be sure about the effect of the bootloader unlocking steps on your warranty.
edit: and i'll also mention here for completeness that unlocking bootloader disables the fingerprint scanner. as always, theres a lot of topics/discussions here on the forum about all the details. i believe the consensus is to lock the bootloader AND clear the "tampered" flag. some say the bootloader status must be "locked" as opposed to "relocked", which is where s-off might become necessary...or some such! haven't quite done any steps yet to enable my fingerprint scanner. don't want to hijack your thread, but that would be my next question if i was you and had just read my post!
Sent from my HTC One max using XDA Free mobile app
Click to expand...
Click to collapse
So I am on Verizon and when I try to unlock through HTC dev it gives me error. I have used the htc dev to unlock many htc devices over the years. I dont remember the error but I am 100% sure HTC dev unlock will not work with my version which is 2.49 and 4.4.2. So I wish you were right I would already be there. Thank you for your in depth post
Problem solved!
Bought sunshine!