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 ^^
Related
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
el_ochito said:
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
Click to expand...
Click to collapse
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
el_ochito said:
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
Click to expand...
Click to collapse
There is no reason that having an unlocked bootloader will interfere with being able to obtain s-off in the future because we can always relock the bootloader when (or if) it comes down to it.
Binary100100 said:
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Click to expand...
Click to collapse
Your words helped me a lot. I was thinking about the diff between s-on/off and lock.unlock bootloader for long. Thanks so much
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.
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
some_douchebag said:
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
Click to expand...
Click to collapse
Once you unlock the boot loader no update can relock it. HTC offers a lot more freedom than samsung, but at the price of no warranty. So if you unlock it and shatter your screen, don't be upset like other people when htc will not warranty it. As long as you have a custom recovery, your phone cannot even physically take an ota update so nothing to worry about either way.
The Magnuson–Moss Warranty Act is in place for us consumers for this reason. The company has to prove that any modification you did, is the cause of the trouble. So if you unlock your bootloader, root, etc, then crack your screen, as the poster above mentioned, the company can not void your warranty since what you did has nothing to do with cracking your screen.
This was huge for me when I modified my car and I found this here on XDA after doing more searching
http://www.xda-developers.com/xda-tv-2/your-warranty-is-not-void-xda-tv/
Oh and yeah,,if you are outside the US, it wont work lol
some_douchebag said:
if HTC allows downgrading the bootloader
Click to expand...
Click to collapse
That depends on what you mean by "allow". You cannot downgrade the bootloader by any "official" means. You will fail version check when you try to install, as you can "normally" only flash a equal or great version number hboot.
But if you are s-off, version check is bypassed, and any hboot version can be flashed.
Similar to a previous response, my advice would be to unlock the bootloader (required if you want to flash custom ROMs anyway) and S-off the phone soon after you get it. Neither of those can be changed by any OTA.
Also, accepting OTA is not recommended on a modded phone, anyway. Whatever came in the update will usually get posted in a stock rooted form in the Development forum, and/or incorporated into custom ROMs, often within days of the OTA rolling out. And OTA will not install on a modded phone (stock recovery needs to be present). OTAs also may plug existing s-off or other exploit; preventing you from doing them if you haven't already (but as mentioned, can't make the phone s-on again). Moral of the story, I strongly recommend against OTA on any modded phone.
Some of these terms/concepts are HTC specific, so may be a bit confusing for you. I would suggest reading up on these forums, if you aren't familiar with s-off, HTC's bootloader unlock process, etc.
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.