Related
Has VZW or HTC ever issued an update or other means by which they have remotely flipped the switch back to S-On? Why is there so much concern about this posted in various threads? Am I missing something?
godhamba said:
Has VZW or HTC ever issued an update or other means by which they have remotely flipped the switch back to S-On? Why is there so much concern about this posted in various threads? Am I missing something?
Click to expand...
Click to collapse
There are a few who are worried. But overall there is nothing to be afraid of.
Just whatever you do, DON'T take any OTAs!
godhamba said:
Has VZW or HTC ever issued an update or other means by which they have remotely flipped the switch back to S-On? Why is there so much concern about this posted in various threads? Am I missing something?
Click to expand...
Click to collapse
Basically, it is technically possible to turn a phone S-ON with an OTA. I don't believe it has ever been done however.
Sent from my HTC One
GrayTheWolf said:
There are a few who are worried. But overall there is nothing to be afraid of.
Just whatever you do, DON'T take any OTAs!
Click to expand...
Click to collapse
I was one of those worried. The only reason I had asked is because if I sent my phone in to get S-Off (which I'm pretty sure I will) and development never really takes off after that, I don't want to be stuck on 4.2.2 for the entirety of my time with this phone. I wanted to know if I COULD take that OTA at some point without bricking the phone. I was told if I changed the CID back to VZW__001, then I wouldnt brick if I did an OTA...
crazyg0od33 said:
I was one of those worried. The only reason I had asked is because if I sent my phone in to get S-Off (which I'm pretty sure I will) and development never really takes off after that, I don't want to be stuck on 4.2.2 for the entirety of my time with this phone. I wanted to know if I COULD take that OTA at some point without bricking the phone. I was told if I changed the CID back to VZW__001, then I wouldnt brick if I did an OTA...
Click to expand...
Click to collapse
When 4.3 is released, a rooted version will be available within a day or two. There is literally no reason to take an OTA ever.
sent from my HTC one
m4rk0358 said:
When 4.3 is released, a rooted version will be available within a day or two. There is literally no reason to take an OTA ever.
sent from my HTC one
Click to expand...
Click to collapse
That's what I figured. But better to know than not know
Sent from my Nexus 7 using Tapatalk 4
The fuss is if your phone is ever turned back to S-ON after having been S-OFF, there is a high chance that it will instantly brick itself if you have loaded unsigned firmware onto the device.
If I go S-OFF, proceed to unlock boot loader, install clockwork mid recovery and just debloat my phone or flash a ROM, I should fear bricking if S-ON is switched back on?
CNexus said:
The fuss is if your phone is ever turned back to S-ON after having been S-OFF, there is a high chance that it will instantly brick itself if you have loaded unsigned firmware onto the device.
Click to expand...
Click to collapse
godhamba said:
If I go S-OFF, proceed to unlock boot loader, install clockwork mid recovery and just debloat my phone or flash a ROM, I should fear bricking if S-ON is switched back on?
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but no, no worries with a custom ROM and recovery. Only for unsigned firmware, something like a custom hboot for example.
peteschlabar said:
Someone correct me if I'm wrong, but no, no worries with a custom ROM and recovery. Only for unsigned firmware, something like a custom hboot for example.
Click to expand...
Click to collapse
This is correct. If you flash an unsigned HBOOT and the flag goes S-ON somehow, the phone will refuse to boot because of the failed security check on the HBOOT. Besides that you're fine.
I got my HTC One M8 about a month or more ago switching from my Xperia Z2, and of course, the first thing I had to do with it was root it. Since I had to unlock the bootloader first, I went into bootloader mode and saw the info on the top of the screen. As expected, it says LOCKED, but the funny thing is, it says S-OFF instead of S-ON. Is there any way that this can happen to brand new phones? How can I make sure I am S-OFF, other than going into bootloader mode? I want to convert my phone to GPE but don't want to brick it in the process. Thanks :good:
Schwaggmeister said:
I got my HTC One M8 about a month or more ago switching from my Xperia Z2, and of course, the first thing I had to do with it was root it. Since I had to unlock the bootloader first, I went into bootloader mode and saw the info on the top of the screen. As expected, it says LOCKED, but the funny thing is, it says S-OFF instead of S-ON. Is there any way that this can happen to brand new phones? How can I make sure I am S-OFF, other than going into bootloader mode? I want to convert my phone to GPE but don't want to brick it in the process. Thanks :good:
Click to expand...
Click to collapse
You got lucky, I traded in my m8 for the nexus 6 and left it s-off for the next person that gets it ^^
If it says S-OFF in bootloader you are indeed S-OFF. There's an adb shell/terminal command to unlock the bootloader if you don't want to go through htcdev, although htcdev is safer. But either way, once you bootloader unlock you can convert to gpe if you want or whatever you wanna do.
Sent from my Nexus 6 using Tapatalk
I wonder if the phone was returned the point of sale, repackaged, and shipped to you? Perhaps the previous owner relocked the bootloader but left the phone S-OFF.
HolyAngel said:
You got lucky, I traded in my m8 for the nexus 6 and left it s-off for the next person that gets it ^^
If it says S-OFF in bootloader you are indeed S-OFF. There's an adb shell/terminal command to unlock the bootloader if you don't want to go through htcdev, although htcdev is safer. But either way, once you bootloader unlock you can convert to gpe if you want or whatever you wanna do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah, I already unlocked bootloader, rooted a long time ago, but I'm not sure if this phone is brand new because it did come with the wrapping around it and not a scuf or scratch was found on the phone, however the sticker sealing the box was already cut, but I presume it's just my uncle checking that all the parts are there because he was the one who got the phone for me since he works at a pretty big shop where they sell phones . Either way, thanks, also great ROMs you're doing for the M8 :good:
WorldIRC said:
I wonder if the phone was returned the point of sale, repackaged, and shipped to you? Perhaps the previous owner relocked the bootloader but left the phone S-OFF.
Click to expand...
Click to collapse
Bootloader wasn't relocked. If it was it would say **RELOCKED**, but mines said **LOCKED**.
Schwaggmeister said:
Bootloader wasn't relocked. If it was it would say **RELOCKED**, but mines said **LOCKED**.
Click to expand...
Click to collapse
It is very easy to make it say "locked" instead of "relocked" since the device has S-OFF.
Schwaggmeister said:
Is there any way that this can happen to brand new phones?
Click to expand...
Click to collapse
Yes, I've seen reports of this happening from time to time. It pretty rare, but it does happen.
Hi all -
Had this HTC One M9 stock for about a month now. I've been reading and reading and reading, and have the big itch to root, but also have some questions I'm hoping folks can answer that I'm a bit confused about. So I'll just get right to my questions.
I've had android phones for years, and I get the general concept of this stuff, but is this clip method so different, in that if I haven't done it before I pose a significant risk of bricking my phone or struggling to figure out the process if I've never done this method?
Does the clip method just get me S Off, or can it unlock the bootloader too?
Should I just use clip to S Off and follow instructions in this thread to unlock bootloader (http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036)?
Can I return this phone to 100% stock if I need warranty service? From what I can gather from the unlock bootloader thread above, I can lock and unlock, and I assume with clip I can S on. Is there a way to flash image to OEM stock, and is there any other Knox-like things I need to worry about that I can't trip back?
I believe I read I can install TWRP recovery, but how do I do that once I have S Off and unlocked bootloader?
My goal is really just to flash a custom rom. I don't know I want to change all the in depth things that I think I'm reading I can do with S off. Is it possible, or does it make sense, to S off, unlock bootloader (which I think is all I need for TWRP and to load ROM), then S on again?
I know obv people are sending their phones to folks to S off, but there's a few reasons I'm thinking about the clip method (please correct any misunderstanding):
I can get clip for just under $100. Comparatively if I send it off, I'd probably do a $30 donation plus fast shipping both ways...I'm already over half the cost of the clip.
If I need the clip to return phone to true stock, I'd like that have that ability myself.
I know there's a few highly recommended people on here, but I'm still uneasy about sending a $600 phone to someone I don't know.
If the process is easy enough, I could try and recoup the money by doing a few phones in my area.
I'm mysteriously not seeing many website recommendations for the clip.
Sorry for the 1001 questions, but thank you SO much in advance for anyone that can offer advice!!!
crackface said:
Hi all -
Had this HTC One M9 stock for about a month now. I've been reading and reading and reading, and have the big itch to root, but also have some questions I'm hoping folks can answer that I'm a bit confused about. So I'll just get right to my questions.
I've had android phones for years, and I get the general concept of this stuff, but is this clip method so different, in that if I haven't done it before I pose a significant risk of bricking my phone or struggling to figure out the process if I've never done this method?
Does the clip method just get me S Off, or can it unlock the bootloader too?
Should I just use clip to S Off and follow instructions in this thread to unlock bootloader (http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036)?
Can I return this phone to 100% stock if I need warranty service? From what I can gather from the unlock bootloader thread above, I can lock and unlock, and I assume with clip I can S on. Is there a way to flash image to OEM stock, and is there any other Knox-like things I need to worry about that I can't trip back?
I believe I read I can install TWRP recovery, but how do I do that once I have S Off and unlocked bootloader?
My goal is really just to flash a custom rom. I don't know I want to change all the in depth things that I think I'm reading I can do with S off. Is it possible, or does it make sense, to S off, unlock bootloader (which I think is all I need for TWRP and to load ROM), then S on again?
I know obv people are sending their phones to folks to S off, but there's a few reasons I'm thinking about the clip method (please correct any misunderstanding):
I can get clip for just under $100. Comparatively if I send it off, I'd probably do a $30 donation plus fast shipping both ways...I'm already over half the cost of the clip.
If I need the clip to return phone to true stock, I'd like that have that ability myself.
I know there's a few highly recommended people on here, but I'm still uneasy about sending a $600 phone to someone I don't know.
If the process is easy enough, I could try and recoup the money by doing a few phones in my area.
I'm mysteriously not seeing many website recommendations for the clip.
Sorry for the 1001 questions, but thank you SO much in advance for anyone that can offer advice!!!
Click to expand...
Click to collapse
OK...so when you s-off it's completely reversible and does not require a clip or card to revert. Just some simple commands. If you have a clip the best bet is to s-off and then use the adb command to unlock. The clip can unlock but it uses the HTC Dev method which let's HTC know what you've done.
Once s-off you leave it s-off. You definitely do not want to turn it on while on a custom rom. Some system write protection is turned on/off by the s flag and boot loader lock status. There's no such thing as Knox on HTC. Using already posted commands you can simply lock the boot loader, flash an ruu (like Odin image) and turn s back on.
What I normally do is s-off, then unlock via the adb command. Flash twrp. Flash supersu. Flash rom.
If you don't understand all of this and why it works this way you probably should NOT be meeting local folks to work on their phones. Sometimes things go wrong and you would be stuck in a really bad situation.
Sent from my Nexus 6 using Tapatalk
dottat said:
OK...so when you s-off it's completely reversible and does not require a clip or card to revert. Just some simple commands. If you have a clip the best bet is to s-off and then use the adb command to unlock. The clip can unlock but it uses the HTC Dev method which let's HTC know what you've done.
Once s-off you leave it s-off. You definitely do not want to turn it on while on a custom rom. Some system write protection is turned on/off by the s flag and boot loader lock status. There's no such thing as Knox on HTC. Using already posted commands you can simply lock the boot loader, flash an ruu (like Odin image) and turn s back on.
What I normally do is s-off, then unlock via the adb command. Flash twrp. Flash supersu. Flash rom.
If you don't understand all of this and why it works this way you probably should NOT be meeting local folks to work on their phones. Sometimes things go wrong and you would be stuck in a really bad situation.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Makes sense, and loud and clear on the advice on doing others' phones. Thank you so much....
Keep in mind that any clip/javacard will mark the device, so HTC will know that you had S-OFF anyway (if you ever return it for warranty).
Sent from my Nexus 5 using Tapatalk
efrant said:
Keep in mind that any clip/javacard will mark the device, so HTC will know that you had S-OFF anyway (if you ever return it for warranty).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
dottat said:
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Says someone who reverse-engineered the process, and who I believe.
I'm not saying it will be a problem, only that it could, if HTC decides to get picky. (I have never RMA'd anything ever so I certainly can't speak from experience. )
Yes, I agree that if you use HTC Dev to unlock, it makes it more of a problem than using a javacard (although there's nothing preventing a non-Verizon device from using a javacard - - your comment sort of implies non-Verizon HTCs need to go the HTC Dev route).
Sent from my Nexus 5 using Tapatalk
efrant said:
Says someone who reverse-engineered the process, and who I believe.
I'm not saying it will be a problem, only that it could, if HTC decides to get picky. (I have never RMA'd anything ever so I certainly can't speak from experience. )
Yes, I agree that if you use HTC Dev to unlock, it makes it more of a problem than using a javacard (although there's nothing preventing a non-Verizon device from using a javacard - - your comment sort of implies non-Verizon HTCs need to go the HTC Dev route).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep...second part of my comment pertains to the unlocking of a boot loader. It's probable that a higher number of non-vzw HTC phones use software methods to s-off. Of all of the phones I have s-offed using a card, 90% were vzw. I unlock all boot loaders using adb. Most of the folks out there who do card s-offs use supercid and dev unlock afterwards. I never really understood why when you can do it without letting HTC know. The built in boot loader unlock method on the clip also uses HTC Dev. Since all vzw HTC phones are banned from dev we have to s-off first.
Sent from my Nexus 6 using Tapatalk
dottat said:
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
True dat - I am one helped by @dottat to return to s-on, locked, and stock for a warrantee replacement. No problem.
dottat said:
I unlock all boot loaders using adb. Most of the folks out there who do card s-offs use supercid and dev unlock afterwards. I never really understood why when you can do it without letting HTC know.
Click to expand...
Click to collapse
Out of curiosity, once you have S-OFF using your javacard, how do you unlock the bootloader using dd when you don't have root? Or how do you get root?
Sent from my Nexus 5 using Tapatalk
efrant said:
Out of curiosity, once you have S-OFF using your javacard, how do you unlock the bootloader using dd when you don't have root? Or how do you get root?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Depends on the device. On m9 you simply flash twrp (don't need to be unlocked on m9 to do so) and then use adb shell in twrp. On the m8, I have twrp packaged up that it will flash in ruu mode with a locked bootloader. Then same as above.
In twrp, adb shell is root already....no need to su.
Sent from my Nexus 6 using Tapatalk
dottat said:
Depends on the device. On m9 you simply flash twrp (don't need to be unlocked on m9 to do so) and then use adb shell in twrp.
Click to expand...
Click to collapse
Thanks! I had no idea you didn't need to be unlocked to flash the recovery partition. Is it only recovery, or do you have fastboot access to other partitions as well while locked?
efrant said:
Thanks! I had no idea you didn't need to be unlocked to flash the recovery partition. Is it only recovery, or do you have fastboot access to other partitions as well while locked?
Click to expand...
Click to collapse
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
hgoldner said:
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
Click to expand...
Click to collapse
Thanks. So to confirm, with S-OFF and a locked bootloader on an M9, you have fastboot access to all partitions other than system and sp1??
efrant said:
Thanks. So to confirm, with S-OFF and a locked bootloader on an M9, you have fastboot access to all partitions other than system and sp1??
Click to expand...
Click to collapse
Why don't you want to bootloader unlock? if you're already S-OFF you can do it in adb shell. Don't hold me to what partitions are fastboot accessible with bootloader locked. I've always had an S-OFF unit with bootloader unlocked. Some partitions aren't writable in fastboot even with bootloader unlocked, although they can be flashed by aboot with an appropriate zip file. For instance, I have a custom splash screen on both my test M9 and my own M9. I keep my test M9 system partition unwritable to ease taking OTA's on the device, but my own M9 runs Fluent.
hgoldner said:
Why don't you want to bootloader unlock? if you're already S-OFF you can do it in adb shell. Don't hold me to what partitions are fastboot accessible with bootloader locked. I've always had an S-OFF unit with bootloader unlocked. Some partitions aren't writable in fastboot even with bootloader unlocked, although they can be flashed by aboot with an appropriate zip file. For instance, I have a custom splash screen on both my test M9 and my own M9. I keep my test M9 system partition unwritable to ease taking OTA's on the device, but my own M9 runs Fluent.
Click to expand...
Click to collapse
It's not that I don't want to unlock. I'm just insatiably curious as to how things now work with HTCs. (Last HTC I owned was 5 years ago.)
Sent from my Nexus 5 using Tapatalk
efrant said:
It's not that I don't want to unlock. I'm just insatiably curious as to how things now work with HTCs. (Last HTC I owned was 5 years ago.)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The M9 is very different from any prior HTC handset. Instead of an hboot which contains fastboot access, it uses an aboot which is very limited in what it can do, that leads to either a "download" mode or a "recovery mode." Only download mode supports fastboot, and only for some partitions. Some things, like splash screens, can only be flashed in aboot from a properly compiled zip file. Some things can only be flashed in download mode via fastboot. I don't believe \system can ever be flashed on an M9, only altered in recovery or via a rooted system (actually, it can if you are installing a fresh custom ROM). And I believe more changes are afoot in HTC handsets in that regard.
With my M8, Rezound and Incredible, you unlocked bootloader and you got S-OFF. Okay, it was a little more complicated on the Rezound because of that infernal "wire trick," but still, you could fastboot write to any partition once you unlocked bootloader and were S-OFF. That is decidedly different on the M9, and the Verizon variant is locked down even tighter.
hgoldner said:
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
Click to expand...
Click to collapse
System part is the other way around while locked on this phone.
Write protected in os ....accessible via twrp.
Boot loader lock flag controls system rw on this phone. On the m8 it was the s flag.
Sent from my Nexus 6 using Tapatalk
Can I run an ruu zip with s-on, after renaming and putting on root of sd card, and UNLOCKED bootloader?
Or, do I have to relock bootloader?
Not got round to s-off yet.
I did that and it worked for me with unlocked bootloader.
10rdan said:
Can I run an ruu zip with s-on, after renaming and putting on root of sd card, and UNLOCKED bootloader?
Or, do I have to relock bootloader?
Not got round to s-off yet.
Click to expand...
Click to collapse
Gr8man001 said:
I did that and it worked for me with unlocked bootloader.
Click to expand...
Click to collapse
You should never need to relock your bootloader to do anything with this device (like run an official RUU or firmware zip). There MAY be somethings you can't do with an unlocked bootloader while s-on, but running RUU or taking an OTA is not included in that list.
Anyone that tells you otherwise is going off of old information and even that might not have been accurate. Back in the day, everyone said you needed to lock bootloader to do these things. It may have been true then, I honestly don't remember, but it's certainly not true now.
Relocking bootloader usually only leads to trouble, IMO.
jollywhitefoot said:
You should never need to relock your bootloader to do anything with this device (like run an official RUU or firmware zip). There MAY be somethings you can't do with an unlocked bootloader while s-on, but running RUU or taking an OTA is not included in that list.
Anyone that tells you otherwise is going off of old information and even that might not have been accurate. Back in the day, everyone said you needed to lock bootloader to do these things. It may have been true then, I honestly don't remember, but it's certainly not true now.
Relocking bootloader usually only leads to trouble, IMO.
Click to expand...
Click to collapse
Bunch of us had this debate the other night and we believe the requirement went away during the m8/m9 transition...though I haven't had the free time to fire up an m8 and test yet.
Sent from my HTC6545LVW using Tapatalk
Hello,
I ve got new M8 few day ago, and want to root it, I know that unlocking bootloader MIGHT void warranty depending on carrier, but Ive seen something about "relocking" it while S-Off - not "re-locked" sign but actually "locked". So there is actually no traces of unlocking/rooting.
Is that possible? And if, is that possible for "un-voiding" warranty?
"It depends"
It depends on whether your warranty is through the carrier, or HTC. And it may even depend on what region/country, etc.
Yes, you can make the IMEI say LOCKED. And if that is what they are checking, there will be no trace of it being bootloader unlocked.
But also remember that HTC has a record of you unlocking the bootloader via HTCDev.com (linked to your device's IMEI) and they can check that as well.
Carriers probably won't go that length. HTC may or may not. I'd say its "probably" okay (HTC will honor warranty) to have bootloader LOCKED. But its not a sure thing, for the reason stated above.
Are you sure you have a warranty to begin with? The phone came out over 2-1/2 years ago. I'd be surprised if they were still selling this as "new" with a valid warranty, and its not refurbished, second hand, etc.
redpoint73 said:
"It depends"
It depends on whether your warranty is through the carrier, or HTC. And it may even depend on what region/country, etc.
Yes, you can make the IMEI say LOCKED. And if that is what they are checking, there will be no trace of it being bootloader unlocked.
But also remember that HTC has a record of you unlocking the bootloader via HTCDev.com (linked to your device's IMEI) and they can check that as well.
Carriers probably won't go that length. HTC may or may not. I'd say its "probably" okay (HTC will honor warranty) to have bootloader LOCKED. But its not a sure thing, for the reason stated above.
Are you sure you have a warranty to begin with? The phone came out over 2-1/2 years ago. I'd be surprised if they were still selling this as "new" with a valid warranty, and its not refurbished, second hand, etc.
Click to expand...
Click to collapse
Well, I don't have it through carrier nor HTC, just e-shop, and I hope it is new, seems like new (got last one) So, theoretically, I can unlock bootloader + root, and when I need to do warranty repair just to "lock" it same as unlocking it, or for "locked" do I always need S-Off? And also,how do I get that S-off?
Sharp852 said:
So, theoretically, I can unlock bootloader + root, and when I need to do warranty repair just to "lock" it same as unlocking it, or for "locked" do I always need S-Off?
Click to expand...
Click to collapse
To make it say "LOCKED" you need s-off. Instruction to do so are here: http://forum.xda-developers.com/showthread.php?t=2708571
Sharp852 said:
And also,how do I get that S-off?
Click to expand...
Click to collapse
Sunshine app ($25): http://theroot.ninja/
And sunshine is the only way (if you are going to ask). No other working method currently.
redpoint73 said:
To make it say "LOCKED" you need s-off. Instruction to do so are here: http://forum.xda-developers.com/showthread.php?t=2708571
Sunshine app ($25): http://theroot.ninja/
And yes (if you are going to ask), sunshine is the only way. No other working method currently.
Click to expand...
Click to collapse
1. What is difference between "locked" and "re-locked", isn't that technically the same?
2. one "license" in Sunshine is for 1 device ("unlimited" S-On/Off locks/unlocks) of 1 S-Off unlock?
Sharp852 said:
1. What is difference between "locked" and "re-locked", isn't that technically the same?
2. one "license" in Sunshine is for 1 device ("unlimited" S-On/Off locks/unlocks) of 1 S-Off unlock?
Click to expand...
Click to collapse
1) RELOCKED by definition means you previously unlocked the bootloader, then relocked it. It will actually say RELOCKED on the bootloader screen. This is not what you want, if you want HTC to think the phone has never been bootloader unlocked. The main reason for making it RELOCKED, is to run RUU or signed firmware (will not flash if bootloader is unlocked, unless you have s-off). You can make it RELOCKED while s-on, with the command: fastboot oem lock
LOCKED is the condition you want, if you want to make the bootloader look like you never unlocked it. S-off is required to make it LOCKED; using the guide I linked in my past post. You can basically think of this as a hack.
2) The license is for the device. From what I understand, you should be able to use the app to s-off, unlock the bootloader as much as you want; even if its been relocked or made s-on again.
redpoint73 said:
1) RELOCKED by definition means you previously unlocked the bootloader, then relocked it. It will actually say RELOCKED on the bootloader screen. This is not what you want, if you want HTC to think the phone has never been bootloader unlocked. The main reason for making it RELOCKED, is to run RUU or signed firmware (will not flash if bootloader is unlocked, unless you have s-off). You can make it RELOCKED while s-on, with the command: fastboot oem lock
LOCKED is the condition you want, if you want to make the bootloader look like you never unlocked it. S-off is required to make it LOCKED; using the guide I linked in my past post. You can basically think of this as a hack.
2) The license is for the device. From what I understand, you should be able to use the app to s-off, unlock the bootloader as much as you want; even if its been relocked or made s-on again.
Click to expand...
Click to collapse
Okay,so far I understand, last thing is, while I am rooted, do I have some limitations? Ive heard something about Snapchat, etc....
Sharp852 said:
while I am rooted, do I have some limitations? Ive heard something about Snapchat, etc....
Click to expand...
Click to collapse
I don't use Snapchat, so I have no idea on that. Apps may look for root, on an app-specific basis. For instance, Pokémon Go won't run on rooted devices (and don't think methods to "hide" root work in this case) to prevent players from cheating.
redpoint73 said:
I don't use Snapchat, so I have no idea on that. Apps may look for root, on an app-specific basis. For instance, Pokémon Go won't run on rooted devices (and don't think methods to "hide" root work in this case) to prevent players from cheating.
Click to expand...
Click to collapse
And is there any workarounds?
Sharp852 said:
And is there any workarounds?
Click to expand...
Click to collapse
For Pokémon Go, no. I haven't seen any workaround, except to unroot. But are you asking about Pokémon, in particular? If you are asking about apps in general (which look for root), and whether you can hide root or not; its going to vary on an app by app basis, and I can't really answer that.
redpoint73 said:
For Pokémon Go, no. I haven't seen any workaround, except to unroot. But are you asking about Pokémon, in particular? If you are asking about apps in general (which look for root), and whether you can hide root or not; its going to vary on an app by app basis, and I can't really answer that.
Click to expand...
Click to collapse
Well, i dont play PoGo, i am looking more for Snapchat and bank app, but bank app, i must try that on myself i think
Can u tell most popular ones which wint work with root?
Also, how tk unroot? As superuser app i want SuperSU by Chainfire, that one have full unroot i think, will that work?
Sent from my HTC One (M8) using XDA Labs
Sharp852 said:
Can u tell most popular ones which wint work with root?
Click to expand...
Click to collapse
No, I have no idea. Why don't you Google or XDA search the apps you use, instead of asking questions that can't be answered?
Sharp852 said:
Also, how tk unroot? As superuser app i want SuperSU by Chainfire, that one have full unroot i think, will that work?
Click to expand...
Click to collapse
Unroot with SuperSU will still show the system as "modified".
Easy way to unroot, is make a TWRP backup before you root. Then you can just restore that backup, to "unroot" (you are restoring the ROM that was never rooted in the first place).