Related
UPDATE 11/25/2013 - scotty1223 posted a method by which you can change your UNLOCKED flag back to LOCKED which then re-enables the fingerprint senser. I'd recommend to just avoid HTCDev.com for unlocking and go straight to this thread: http://forum.xda-developers.com/showthread.php?t=2540004
On a personal note:
It makes sense really. Your fingerprint is like a unique password that you cannot change so HTC is doing everything prudent to protect that password for you. I don't see a problem with this personally.
On a technical note:
I believe the TZ partition (mmcblk0p11) has a check for whether the device is LOCKED, UNLOCKED, or RELOCKED. If it is anything other than LOCKED then the fingerprint scanner is automatically disabled.
I believe there are two possible ways to re-enable the fingerprint scanner:
Issue the command fastboot oem lock from the bootloader then run a factory RUU for your carrier
Hex edit the TZ partition to remove the unlock check, then fastboot oem lock and subsequently unlock the device again
The first method would most likely require that you also flash the stock recovery from fastboot before relocking.
The second method would require S-OFF to function as it is very unlikely that mmcblk0p11 is writable with S-ON.
I am by no means an expert with HBOOT or TZ so I may be way off base here, but that's how I see it right now. I'll see if I can get a warning posted in the threads about the fact that unlocking the bootloader with HTC Dev method will disable the fingerprint scanner.
yes ... pretty sad situation here... dont want to lock it again at the moment ... maybe i will relock it when i found a good rom ( i hope there will be roms for this phone, mike wont do one )
damn its a great phone !!
B-Man2005 said:
yes ... pretty sad situation here... dont want to lock it again at the moment ... maybe i will relock it when i found a good rom ( i hope there will be roms for this phone, mike wont do one )
damn its a great phone !!
Click to expand...
Click to collapse
relocking didn't work for me
I can confirm relocking dosent enable it.
Odd HTC would put a check on that function there....
Sent from my EVO using Tapatalk
@navalynt i have an app which also does not work after boot-loader unlocking.
This app is "Du Transport" and it is an app which is used to replace smart cards in pubic transport. This requires a special sim from the telecom provider and with this SIM as authentication the app uses NFC to replace the smart cards.
i think it goes back to the secure partition which you talked about. your solution logically makes sense that it's a bug in the firmware/hboot or where ever which needs to be fixed rather than these individual apps fixed.
This should have also behaved the same way as in HTC One.
For the s-off solution, do you think we could we just reuse the tools/scripts which were created for HTC One?
Has someone here contacted HTC or know if HTC/HTCDev are aware or working on this issue?
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
I am not sure if this is a bug or that's the way it is meant to work. we could possibly contact HTC/HTC Dev for a fix about it if we are sure it is a bug. i have read that HTC dev's attitude is bad but we could possibly contact the service center managers and demand a new phone under warranty.
I am not worried warranty and BL unlocks as i have dealt with such a situation before.
Hello
So the solution to make it enable state again is to flash a RUU ?
so i contacted HTC customer care via the website and i got this response.
Thank you for contacting HTC support.
As per your mail, we understand that after unlocking the bootoader of your HTC One Max, the finger print sensor is not working.
In this regards, we request you to please visit our nearest service-center to resolve the issue.
We would like to inform you that as, you have manually rooted and installed customized OS, the warranty of your device may get void, kindly provide us with the device details like IMEI or Serial number and your location so we can direct you to the service-center accordingly.
You can get the IMEI number by dialing *#06# or you can get the Serial number or IMEI number on the invoice or you can find the IMEI number or Serial number on your HTC handset box as well.
Please read the disclaimer given below:
Disclaimer: Unlocking your device allows you to install custom Operating Systems (“OS”) onto your device. Custom OS’s are not tested as thoroughly as your original OS, and unlocking your device may void all or parts of your warranty. HTC disclaims any and all liability for proper functioning of your device after the bootloader has been unlocked and for data lost in the unlocking process. To prevent unauthorized access to your data, unlocking the bootloader will delete all personal data from your device including applications, text messages and personalized settings.
Click to expand...
Click to collapse
Send you to service center to have RUU flashed.... Has nothing to do with custom OS... I'd hit up Jason and Mo from HTC on Twitter.... likely get a better logical response there.
Sent from my EVO using Tapatalk
sgt. slaughter said:
Send you to service center to have RUU flashed.... Has nothing to do with custom OS... I'd hit up Jason and Mo from HTC on Twitter.... likely get a better logical response there.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yeah thanks, that's what i am thinking of doing... i was wondering if there is going to be some kind of solution to this issue or we just have to live without root ? it's not only fingerprint sensor which seem to stop working... its some kind of secure flag/partition which goes bonkers on BL unlock i have a very similar issue with another app after BL unlock.
Paul O'Brien of Modaco confirmed that HTC is aware of the issue and he raised it with HTC
has anyone with s-off tried setting the bootloader back to "locked" (not "relocked") to see if that fixes it?
I would try it but the only one max I have access to belongs to my dad and he's considering returning it and getting something else so I can't do anything that could cause problems with returning it.
hotaru2k3 said:
has anyone with s-off tried setting the bootloader back to "locked" (not "relocked") to see if that fixes it?
I would try it but the only one max I have access to belongs to my dad and he's considering returning it and getting something else so I can't do anything that could cause problems with returning it.
Click to expand...
Click to collapse
We don't have definite guides of making it to "locked" yet.
Given that our device is almost the same as HTC One, i am guessing methods of HTC One might work.
I found this on the HTC One forum - http://forum.xda-developers.com/showthread.php?t=2497712
Woot woot! it worked!!!
I removed my TAMPERED flag and also set it to LOCKED and the fingerprint scanner works!
Thanks to @scotty1223 for this! i would let scotty1223 to post the commands and make a thread for resetting the flags.
If this is true, this would be amazing.
JohnnyGipsy said:
If this is true, this would be amazing.
Click to expand...
Click to collapse
Yes it does work mate, works well! you would need S-Off and would need to follow the commands for locking and unlocking
pradeepvizz said:
Yes it does work mate, works well! you would need S-Off and would need to follow the commands for locking and unlocking
Click to expand...
Click to collapse
Than post the commands, please.
JohnnyGipsy said:
Than post the commands, please.
Click to expand...
Click to collapse
oh well, All credits to @scotty1223
My phone is a T6UL, I had provided the dump of my partitions to Scotty, which the dev worked on.
The commands that worked for me is the same as
http://forum.xda-developers.com/showthread.php?t=2477792
and
http://forum.xda-developers.com/showthread.php?t=2475914
i would suggest to hold on to your patience till Scotty makes a thread, just in case.
standard disclaimer : this might brick your phone, me nor scotty would not be responsible.
I can confirm it's working. My phone is now s-off and I have a working fingerprint sensor.
Gesendet von meinem HTC One mit Tapatalk
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.
ok i have a htc one M8 AT&T i have 4.4.4 android o.s. its rooted and unlocked (network).
I just need some help ive tried to update it with ruu but i get a connection error 170 and when i turn my phone off and boot to fast boot usb it verifys info on my device and starts to update but never gets passed 1/7 update signatures
also another thing id like help with is my m8 is AT&T but if i could id like to flash it(if thats correct termi) to a tmobile rom because i have tmobile also for mms capabilities please someone help and be as thorough as possible im not stpid but i cant follow steps if you skip something
Is your bootloader locked or unlocked? Is S-on or S-off?
troysyx said:
Is your bootloader locked or unlocked? Is S-on or S-off?
Click to expand...
Click to collapse
boot loader is unlocked but tampered and s-on
Have you verified the CID is correct?
sniper7777777 said:
boot loader is unlocked but tampered and s-on
Click to expand...
Click to collapse
RUU you alway fail with an unlocked bootloader.
You need to relock the bootloader with fastboot command: fastboot oem lock
---------- Post added at 10:14 AM ---------- Previous post was at 10:10 AM ----------
sniper7777777 said:
also another thing id like help with is my m8 is AT&T but if i could id like to flash it(if thats correct termi) to a tmobile rom because i have tmobile also for mms capabilities please someone help and be as thorough as possible im not stpid but i cant follow steps if you skip something
Click to expand...
Click to collapse
Those statements don't tell me what you actually want to do. You should be able to get MMS working on T-Mobile by one of the following:
1) Enter the proper T-Mob APN. Although I think I might recall that some folks still have trouble with MMS on T-Mob using the AT&T version M8, even when the correct APN is used (so that may be what you are talking about).
2) Flash a custom ROM that specifically supports the T-Mob network.
3) "Fully convert" your phone to the T-Mob version. This may be the most desirable option, as it allows you to get future OTA updates for the T-Mob version, ensures the best compatibility with T-Mobs network. In order to fully convert, you need s-off (by sunshine), and to change the CID and MID. The following thread describes the process. But you only have to do steps 1 and 2 (change to T-Mob CID and MID) and after that you can flash the latest T-Mob RUU: http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...any senior members willing to point me in the right direction? I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
HTCFAN0923 said:
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...
Click to expand...
Click to collapse
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
HTCFAN0923 said:
I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Click to expand...
Click to collapse
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
HTCFAN0923 said:
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
Click to expand...
Click to collapse
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
redpoint73 said:
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
Click to expand...
Click to collapse
Thanks for the help and sorry for the confusion.
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
thanks again!
HTCFAN0923 said:
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
Click to expand...
Click to collapse
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
HTCFAN0923 said:
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
Click to expand...
Click to collapse
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
redpoint73 said:
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
Click to expand...
Click to collapse
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
HTCFAN0923 said:
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
Click to expand...
Click to collapse
I gave previous advice to stop using the toolkit, so I don't know why you insist on ignoring that advice.
Older versions of TWRP don't work on newer hboots; and the opposite is true where older hboots don't work with newer TWRP builds. This is the most frequent reason for TWRP not working properly.The toolkit worked fine at the time it was updated. But it hasn't been updated in a very long time, and therefore won't work on many M8 versions now. The issue is more your lack of understanding, and lack of following advice given to you.
Flashing TWRP is just a matter of downloading the proper version, and flashing with a single fastboot command (2 commands, if you want to be thorough and wipe cache before flashing TWRP). You don't need a toolkit for that, and again I advise stopping its use altogether.
Its not clear whether you chose to update before TWRP and root (current device status) and once I know the main version (OS number on bootloader screen) and present hboot number I can probably advice what version TWRP you need to flash.
And you're absolutely right about that. It was my fault for not listening. I was being lazy about it honestly.
I did end up using the lollipop pre rooted RUU and that worked after two atttempts. I think the issue was that the toolkit flashed the recovery without root. Add that to the fact that the toolkit caused the SD card issue to pop up made it a nightmare. Thankfully, I was able to fix it and now I'm running the AT&T lollipop ROM rooted.
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
HTCFAN0923 said:
I think the issue was that the toolkit flashed the recovery without root.
Click to expand...
Click to collapse
I don't follow. Root isn't needed to install custom recovery; nor does flashing custom recovery automatically root the phone (this has to be done as an additional step, usually by flashing SuperSU in TWRP).
I think the main issue was that the toolkit flashed an old TWRP version that was not compatible with the software/firmware that was on your phone.
HTCFAN0923 said:
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
Click to expand...
Click to collapse
I appreciate the thought; but your thanks is all I expect in return. I've benefited plenty from XDA from folks that don't ask for any monetary compensation; so I just like to give back to the community by helping how I can.