Related
sorry if this is stated in a million threads but i searched and couldnt find it
Anyways, i have a rezound but am borrowing a nexus and want to try unlocking it BUT its not mine so i have to be able to get it back COMPLETELY to stock. So, my question is if you relock the bootloader, does it say relocked like it does on the rezound or is it undetectable
It will say locked when you relock the bootloader.
atesc said:
It will say locked when you relock the bootloader.
Click to expand...
Click to collapse
so then if you run the RUU no one will ever know correct?
werdna87 said:
so then if you run the RUU no one will ever know correct?
Click to expand...
Click to collapse
There's no RUU. The way of returning to stock is unlocking the bootloader (which is probably unlocked if you messed with anything), flashing all of the stock images, radio, etc., then relocking the bootloader.
No one will know the difference. This device is meant to be able to be regularly (and dead simply) unlocked.
martonikaj said:
There's no RUU. The way of returning to stock is unlocking the bootloader (which is probably unlocked if you messed with anything), flashing all of the stock images, radio, etc., then relocking the bootloader.
No one will know the difference. This device is meant to be able to be regularly (and dead simply) unlocked.
Click to expand...
Click to collapse
Thanks, i have wanted to unlock my rezound for a while but its not nearly as simple with that phone and it very easily detectable. Anyways, time to unlock
werdna87 said:
Thanks, i have wanted to unlock my rezound for a while but its not nearly as simple with that phone and it very easily detectable. Anyways, time to unlock
Click to expand...
Click to collapse
fastboot oem unlock
it's that easy on the Nexus
martonikaj said:
fastboot oem unlock
it's that easy on the Nexus
Click to expand...
Click to collapse
if only HTC was so nice... i was like that with the Dinc but times have changed
werdna87 said:
if only HTC was so nice... i was like that with the Dinc but times have changed
Click to expand...
Click to collapse
Yaaaa I won't expect anything like that from HTC.
I have a G2, so I know what you're talking about haha.
I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags. Can't find an encrypted RUU or figure out how to encrypt the one I have to get this rolling again, can anybody give me a clue or anything on how to go about doing this or getting this thing functional again?
You can get the ruus at the bottom of this post. http://forum.xda-developers.com/showthread.php?p=46506621
cmlusco said:
You can get the ruus at the bottom of this post. http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Yes, it always says:
FAILED (status read failed (too many links))
Probably because its 2.10 RUU and mine is on 3.11?
Yeah an s-on phone wont allow you to flash an ruu version older than the one already on the phone. And unfortunatley, we do not have the newest ruu available yet.
So there's nothing I can do but wait? I was pretty sure I had everything flashed back to stock but once I turned S-ON it wouldn't let me go past the bootloader. My phone's sound completely stopped working so I was going to take it in to get it taken care of, but I guess I can't do anything at all now.
You can probably still flash the RUU if you get the correct one i would assume. I've reset the tampered flags before also. I always made it a point to flash the older RUU's before flipping s-on for a warranty return, because it is so much easier to get s-off in case I mess something up, so not sure how being on that newer firmware is going to play out.
ccarr313 said:
You can probably still flash the RUU if you get the correct one i would assume. I've reset the tampered flags before also. I always made it a point to flash the older RUU's before flipping s-on for a warranty return, because it is so much easier to get s-off in case I mess something up, so not sure how being on that newer firmware is going to play out.
Click to expand...
Click to collapse
Yeah I'm just keeping an eye open and checking for the latest RUU. First time getting into this stuff, so lesson learned. Just sucks I'm without a phone even just to text/apps until then.
I have the same issue
GrayFalcon11 said:
Yeah I'm just keeping an eye open and checking for the latest RUU. First time getting into this stuff, so lesson learned. Just sucks I'm without a phone even just to text/apps until then.
Click to expand...
Click to collapse
I was S-Off and unlocked and rooted, I was trying to flash back to stock for a warranty exchange. Now I'm Locked, S-On and flagged Tampered and stuck in the bootloader. I'm on 3.11.605.10 as well. I only have 4 days left to send this back to verizon.. Any suggestions? or I'm I butt ****ed with no lube.
keith7120 said:
I was S-Off and unlocked and rooted, I was trying to flash back to stock for a warranty exchange. Now I'm Locked, S-On and flagged Tampered and stuck in the bootloader. I'm on 3.11.605.10 as well. I only have 4 days left to send this back to verizon.. Any suggestions? or I'm I butt ****ed with no lube.
Click to expand...
Click to collapse
What happen? I have 3 days left to send back to Verizon and I'm still s-off and unlocked and I don't wanna mess it up.
Do an older ruu.
Lock bootloader using fastboot.
Go s-on using fastboot.
Do a signed ruu.
cmlusco said:
Do an older ruu.
Lock bootloader using fastboot.
Go s-on using fastboot.
Do a signed ruu.
Click to expand...
Click to collapse
Why 2 ruu?
Probably not really needed, but just to be sure the phone got wiped out.
Let Me Make sure I understand
cmlusco said:
Probably not really needed, but just to be sure the phone got wiped out.
Click to expand...
Click to collapse
Can I or can I not flash an older RUU?
How do I get a hold of a signed RUU? Is it the one that says decrypted?
Will this at least allow me to wipe the phone to where it does not say tampered?
I could have sworn I have tried these RUU's but I get a remote signature error.
No if you are s-on you can not flash an ruu which is an older version than the phone is currently on.
The signed and decrypted (not signed) ruu's can be found at the bottom of the second post of santods rom radio kernel thread in development. http://forum.xda-developers.com/showthread.php?p=46506621
In order to remove the tampered flag you would need to get s-off again. I believe there is a new exploit for 4.2.2 http://forum.xda-developers.com/showthread.php?p=51481200, if you want to go that route.
Remote sig error is because you were trying to flash an unsigned ruu while s-on.
oh well
cmlusco said:
No if you are s-on you can not flash an ruu which is an older version than the phone is currently on.
The signed and decrypted (not signed) ruu's can be found at the bottom of the second post of santods rom radio kernel thread in development. http://forum.xda-developers.com/showthread.php?p=46506621
In order to remove the tampered flag you would need to get s-off again. I believe there is a new exploit for 4.2.2 http://forum.xda-developers.com/showthread.php?p=51481200, if you want to go that route.
Remote sig error is because you were trying to flash an unsigned ruu while s-on.
Click to expand...
Click to collapse
Welp, a couple seconds in the microwave solved my dilemma. I hope. It won't come back on.
Next question, my replacement device has 4.4.2 on it. Will the current S-off tools work to flip it from S-on to S-off?
keith7120 said:
Welp, a couple seconds in the microwave solved my dilemma. I hope. It won't come back on.
Next question, my replacement device has 4.4.2 on it. Will the current S-off tools work to flip it from S-on to S-off?
Click to expand...
Click to collapse
Yup, just follow the directions on the WeakSauce thread. -> http://forum.xda-developers.com/showthread.php?t=2699091
eman7131 said:
Yup, just follow the directions on the WeakSauce thread. -> http://forum.xda-developers.com/showthread.php?t=2699091
Click to expand...
Click to collapse
Thanks, I'm now S-Off
how would i go about going S-On in fastboot? my fiance device was thought to be returned to stock but we found out that it says Relocked but still says S-Off and when we try to use Firewater it stops after we say Yes cause for some reason its already showing S-off but the bootloader is actually locked.
Stuck Bootloader
Hi i need help. I am stuck in bootloader with s On and relocked. Ive read everything and no go. Please help any one
Hello fellow TMO brethren....
I just got the M8 maybe a week ago... I was busy and had to wait before I could pull up XDA and start reading about this phone (getting root, etc.). Before this, I unfortunately allowed a few updates (2 maybe?) to install, which I believe will prevent me from using Firewater for S-Off... but no big deal....will get sunshine when I need it. However, though firewater won't work, I had no problem using HTCDev to unlock the bootloader (didn't know of towelroot at the time), flashing TWRP 2.8.0.1, and installing SuperSU....so I am currently rooted with stock Rom...
Further...I have not touched any applications. And although I have unlocked the bootloader using HTCDev, my calculator and flashlight are still available. I have read in this M8 general forum that the flashlight and calculator are deleted when you unlock the bootloader using HTCDev... This did not happen to me. Does anyone know if this is this just a T-Mobile thing? or has this changed for all carriers?
Anyway, I am now getting notice for yet another update...So I might as well install it. As we all know, I need to re-flash the stock recovery to get the OTA. Here is where I am confused. My current firmware is 2.22.531.5. I don't know what firmware I had a week ago when the phone was purchased.
This was the info on the bootloader screen yesterday, immediately prior to unlocking the BL or rooting the phone:
[btw, can someone tell me how to do a info dump from the bootloader?? is it just an option I missed?]
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio-1.19.213311491.03G
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.22.531.5
eMMC-boot 2048MB
Jul 16 2014,03:33:24.0
1. My first question is what version of the stock recovery do I use?? On the page that contains the stock recoveries, it only shows these two:
Stock Recovery - 1.12.531.19
Stock Recovery - 1.57.531.7
2. Secondly, and I am really irritated about this.... but I never went and accepted the Google Drive free 65GB promo offered by HTC. When I start google drive it states it cannot determine the user (or something like that). I read elsewhere that this is because I unlocked the bootloader. I will do whatever it takes to get HTC to give me this because I think it is pretty low that they would invalidate the offer to anyone who has unlocked the bootloader pursuant to their website, their instructions, and their so-called "open atitude". Obviously I can re-lock the bootloader, but I do not know if that will matter. Plus... if they say that I requested a token .bin file to unlock, I can say that I changed my mind and decided not too. OR, I can get Sunshine, get s-off, and use the s-off ability to relock the bootloader. Does anyone have any advice on any of this?
3. Any general advice from anyone based on the info above??? (lI don't want to foreclose any other options by upgrading or whatever... ).
Thank you very much in advance!
P
NB: Wanted to mention that last night I was about to use Titanium to freeze and/or uninstall some crap software I didn't want, and to that end, disabled Amazon, Facebook, Facebook for HTC, and Kid Zone (and uninstalled Amazon MP3, which is not a system app). Just an FYI... disabling one (or more) of these apps (maybe Kid Zone?) prevented Wifi calling from functioning correctly...it would not let me call and every in-call received while on wifi calling went straight to VM. I have renabled the above apps to get wifi-calling working again, but also because I want to install this update and figured that disabling/freezing any original stock apps might cause problems. I will look around for a thread on safely deleting apps after I get this udpate...
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
phil.culler said:
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
Click to expand...
Click to collapse
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
syntropic said:
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
Click to expand...
Click to collapse
It looks like you will need S-Off to factory lock the bootloader. S-Off allows you to make changes to otherwise protected areas of the file system. To clarify, I haven't tried this method myself as I haven't had a need to factory relock my device yet. I ran full stock for months before I rooted. As for HTC knowing whether or not you unlocked your bootloader, if you used the HTCDEV method then they have record of you receiving an unlock token from them but if they go into bootloader for any reason and see Locked instead of Relocked they shouldnt give you any trouble I would think. I believe you can also reset it to S-On but again I've never tried and I'm not sure its entirely safe. You'll have to look into that.
I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!
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).