Can't seem to find any into on relocking the bootloader with S-on
other than HTC has disabled the oem lock in 7.0
So is there anyway I can downgrade to with a TWRP backup, flash a stock recovery file relock the bootloader and then run the latest RUU to update everything or do I need S-off to downgrade the bootloader to relock?
It's not for a warranty claim, I just want to use Android pay since it works with my bank now.
I'm assuming a ***RELOCKED*** flag would pass it's security check?
I don't have sunshine since I never went S-off.
Vonrottes said:
Can't seem to find any into on relocking the bootloader with S-on
other than HTC has disabled the oem lock in 7.0
So is there anyway I can downgrade to with a TWRP backup, flash a stock recovery file relock the bootloader and then run the latest RUU to update everything or do I need S-off to downgrade the bootloader to relock?
It's not for a warranty claim, I just want to use Android pay since it works with my bank now.
I'm assuming a ***RELOCKED*** flag would pass it's security check?
I don't have sunshine since I never went S-off.
Click to expand...
Click to collapse
You may want to look into flashing a custom kernel, like ElementalX. Hides the bootloader unlocked status from safetynet. You'd also need to have an untouched system partition as well for Android Pay to work.
You can simply relock the bootloader, no need to downgrade. But you will have to flash a RUU >= your current version. Done it several times, it works
The command world be "fastboot oem lock". Phone needs to be in download mode, obviously...
Relock flag passes safetynet, yes.
bopsch said:
You can simply relock the bootloader, no need to downgrade. But you will have to flash a RUU >= your current version. Done it several times, it works
The command world be "fastboot oem lock". Phone needs to be in download mode, obviously...
Relock flag passes safetynet, yes.
Click to expand...
Click to collapse
You sure?
I've tried it 3 times with a 2.41 RUU the command does what it should, but reboot still shows unlocked.
Vonrottes said:
You sure?
I've tried it 3 times with a 2.41 RUU the command does what it should, but reboot still shows unlocked.
Click to expand...
Click to collapse
Enable OEM unlocking option in developer options from settings. Then the command.
A breadcrumb for anybody on the same trail...
If your bootloader status is still "unlocked" even after flashing a stock RUU and passing a seemingly successful "fastboot oem lock", try removing your SD card and "fastboot oem lock" again. After a load of messing around this immediately allowed me to gain "Relocked".
I loved my HTC10 in it's heyday but I'm so over all these HTC quirks
Related
Hello, just a quick question. I had my One rooted, s-off, and unlocked when my microphone went. So I relocked, s-on, and flashed an RUU via http://forum.xda-developers.com/showthread.php?t=2475216. Just making sure that before I pack it in the box, there is nothing else that could trip the people at Verizon that I had messed with my phone. I took the OTAs up to 4.3. I'm just paranoid about info not matching up such as the baseband version and build number etc. Thanks
Does the bootloader say locked or relocked? Locked is good relocked not so much. Other than that you should be fine. Ruu's wipe everything and install it all fresh, including the firmware (baseband, hboot, recovery, etc), so everything will match up.
In the bootloader I have "Locked" also s-on. I noticed though with the refurbished phone I received (not happy about having to get refurbished but thats besides the point) the CID number shows in the bootloader screen whereas on my original phone it is not displayed. Not sure if I even need to be this worried, but I'm just paranoid. Thanks
Are both phones on the same hboot version? I dont remember if it showed in older hboots or not. Either way i wouldn't worry, locked and s-on is all you need.
No they weren't. I'm just going to stop worrying too much about it. Thanks
If i send my phone back to verizon do i have to be on the original ROM? i understand that i need to lock my bootloader and have s-on, but what about the software itself?
It can be on stock rom/firmware of any version. Just no custom roms or anything.
Just to confirm, if I have a phone that is S-OFF, unlocked:
1. Do I need to lock the bootloader before flashing an RUU?
2. Does flashing an RUU revert the phone to S-ON?
3. Does anything special otherwise need to be done to the phone prior to flashing the RUU?
Thanks so much in advance.
I also have to return a phone to VZW due to a hardware issue (the autofocus issue finally too much for me to bear).
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Fantastically clear, Clumsco, thanks! Three quick additional questions
1. is there any advantage to flashing the signed RUU, and adding danger by locking the bootloader beforehand? In your links below your signature is a path to both decrypted and signed versions of the latest RUUs. So I thought to ask before going with one or the other. If there is no advantage then I guess the decrypted version would be the safer bet, right?
2. Is there a danger that locking after the RUU will result in a "relocked" versus the desired "Locked" status?
3. Will the RUU flash wipe my /sdcard area? If so I'll back everything up before embarking on this.
I VERY much appreciate the help. I ran rumrunner several months back and have forgotten a lot of the nuances. Thanks for the quick primer!
cmlusco said:
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Click to expand...
Click to collapse
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Thanks, everything worked. For future knowledge, can you flash signed RUU's with an S-ON device?
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
cmlusco said:
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
Click to expand...
Click to collapse
I'm trying to learn here too, that is dependent on the hboot correct? So if you were to downgrade your hboot via the thread somewhere in the VZW HTC One forum, you should be able to flash any RUU right?
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Your responses are clear and helpful. Thanks a bunch!
cmlusco said:
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Click to expand...
Click to collapse
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
My phone is current S-Off and relocked, how can I change it to unlocked?
Thank you.
UPDATE: Nevermind, I got it here: http://forum.xda-developers.com/showthread.php?t=2470340
So, I'm setting my phone to 100% stock for a reparation at HTCs EU Repair in Poland.. unfortunately they're pretty strict when it comes to unlocked phones..
I've changed my HBoot, Recovery and ROM to stock, now I need to get my bootloader locked and get S-On.
Problem is, if I follow THIS METHOD I wont be able to get S-On afterwards, and if I follow THIS METHOD (fastboot oem writesecureflag 3) on getting S-On, I wont be able to get my bootloader relocked.. they're depending on each other... How do I get around this loop?
andreglud said:
So, I'm setting my phone to 100% stock for a reparation at HTCs EU Repair in Poland.. unfortunately they're pretty strict when it comes to unlocked phones..
I've changed my HBoot, Recovery and ROM to stock, now I need to get my bootloader locked and get S-On.
Problem is, if I follow THIS METHOD I wont be able to get S-On afterwards, and if I follow THIS METHOD (fastboot oem writesecureflag 3) on getting S-On, I wont be able to get my bootloader relocked.. they're depending on each other... How do I get around this loop?
Click to expand...
Click to collapse
Do you have an RUU?
if yes, the general way is:
1- remove TAMPERED
2- set LOCKED
3- run full RUU
4- bootup make sure all is OK
5- set S-ON if absolutely necessary (S-ON should be the last thing you do, do NOT go S-ON unless you are sure everything is OK)
also, as a side note, scotty's commands can be run while in TWRP (custom recovery will give you a "rooted" adb shell), on the M8 you can even "fastboot boot <name of recovery>.img" (which boots the custom recovery without flashing it)
(on the M7 this was only possible on hboot 1.44, and on the M9 it's not possible at all)
EDIT: also setting S-ON (fastboot oem writesecureflag 3), has nothing to do with locked/relocked/unlocked bootloader
I went back to stock, but I am still S off, shouldn't android pay work now? It is not. Can anyone tell me what I can do.
I just went through this a few days ago, you need to lock your bootloader to be able to use Android Pay, S-Off doesn't affect it. S-Off + Locked works the same as S-Off + Unlocked. First you need to relock your bootloader then, turn S-Off ON, flash SU to be able to use Sunshine, and when given the option, select S-off / Locked, and you should be able to use Android Pay without any problems.
haZethew0rld said:
I just went through this a few days ago, you need to lock your bootloader to be able to use Android Pay, S-Off doesn't affect it. S-Off + Locked works the same as S-Off + Unlocked. First you need to relock your bootloader then, turn S-Off ON, flash SU to be able to use Sunshine, and when given the option, select S-off / Locked, and you should be able to use Android Pay without any problems.
Click to expand...
Click to collapse
So aside from relocking bootloader and getting this back to s on, i need to flash SU to use sunshine? How would I flash if I have stock recovery and phone has a locked bootloader? Am I misunderstanding something here?
PaoloMix09 said:
So aside from relocking bootloader and getting this back to s on, i need to flash SU to use sunshine? How would I flash if I have stock recovery and phone has a locked bootloader? Am I misunderstanding something here?
Click to expand...
Click to collapse
Oh yeah sorry I, it was such a hassle last time I forgot some steps. Once you're relocked and s-on, you need to unlock your bootloader again, then You'll need to flash twrp to be able to flash SU of course, and then proceed with sunshine.
It is all good now. You can keep S-off and unlocked and flash this kernel and your good to go! [KERNEL] [October 23] ElementalX-HTC10-0.23
I'll take a shot at making a fully stock kernel with the no-check patch.
I unlocked bootloader HTCdev, but I want to install stock ROM from HTC site but can not due to bootloader is unlocked.
How can I lock again bootloader?
S-on is there.
I found many instructions but all of them requires s-off, is there any way to relock bootloader with s-on?
You need to be aware of the fact that re-locking the bootloader isn't the same as locking the bootloader in HTC's terminology. You need S-OFF for locking the bootloader but not for re-locking it.
I hope you read the following and know what kind of problems re-locking the bootloader of a modified phone can cause:
Flippy498 said:
I highly discourage everyone from (re-)locking the bootloader unless you have a working RUU at hand and know that you're able to flash it (via HTC_fastboot or an SD card if it's a *.zip). Security features of the M9 prevent the phone from booting if anything is modified and the bootloader is (re-)locked. You can't even enter TWRP, anymore, in this situation. In addition, you can't re-unlock if "OEM Unlock" (introduced with firmware 2.x) isn't activated in the developer options. You've been warned about the risks.
[...]
It seems like HTC changed its encryption keys between firmware 3.x and 4.x. Therefore, you cant flash 4.x RUUs if your phone is currently using a 3.x firmware. You either need to flash a NoWipe/Full-Wipe Firmware Pack beforehand (only possible with S-OFF) or you need to use a 3.x RUU for the same SKU and install the 4.x OTA, afterwards.
Click to expand...
Click to collapse
I personally recommend using the SD card method for flashing RUUs since it can be used with an unlocked bootloader, as well. Instructions for extracting the *.zip files from the *.exe can be found in the ReadMe thread.
However, if you insist on re-locking the bootloader and using the *.exe you can find the needed command in the following hide tag.
Code:
fastboot oem lock
Flippy498 said:
You need to be aware of the fact that re-locking the bootloader isn't the same as locking the bootloader in HTC's terminology. You need S-OFF for locking the bootloader but not for re-locking it.
I hope you read the following and know what kind of problems re-locking the bootloader of a modified phone can cause:
I personally recommend using the SD card method for flashing RUUs since it can be used with an unlocked bootloader, as well. Instructions for extracting the *.zip files from the *.exe can be found in the ReadMe thread.
However, if you insist on re-locking the bootloader and using the *.exe you can find the needed command in the following hide tag.
Code:
fastboot oem lock
Click to expand...
Click to collapse
Where can I find instructions for extracting .zip from .exe
As explained in the post that you quoted, you'll find all needed information in the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
How do you do the above for warranty claim
I need to send the phone in for replacement / maintenance
it is unlocked US version running Verizon ROM on Verizon network
How do I unroot, lock the bootloader, and s-on?
I know they might not care, I still would like to restore everything to prevent any surprises or rejection
please list the steps. Thank you very much
ahgahg said:
How do you do the above for warranty claim
I need to send the phone in for replacement / maintenance
it is unlocked US version running Verizon ROM on Verizon network
How do I unroot, lock the bootloader, and s-on?
I know they might not care, I still would like to restore everything to prevent any surprises or rejection
please list the steps. Thank you very much
Click to expand...
Click to collapse
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
donkeykong1 said:
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
Click to expand...
Click to collapse
Does this remove the red text on the start up screen? One look at that and HTC knows the phone has been altered. On Samsung devices once Knox is tripped you get a message saying so and it's permanent. Just curious.
comstockload said:
Does this remove the red text on the start up screen? One look at that and HTC knows the phone has been altered. On Samsung devices once Knox is tripped you get a message saying so and it's permanent. Just curious.
Click to expand...
Click to collapse
Red text will be removed after you flash a RUU. HTC is much simpler than Samsung regarding that. Just to be on the safe side, check bootloader status after each step. It's a quick procedure, but you're safe
S-off should be ok just make sure its locked not unlocked.
https://www.xda-developers.com/htc-...gn=Feed:+xda-developers/ShsH+(xda-developers)
donkeykong1 said:
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
Click to expand...
Click to collapse
Did all that (installing the RUU) and received only "re-locked" since it already was S-ON. Sunshine now cannot be used, because the RUU was installed. What did I do wrong, then?
Matt.Murdock said:
Did all that (installing the RUU) and received only "re-locked" since it already was S-ON. Sunshine now cannot be used, because the RUU was installed. What did I do wrong, then?
Click to expand...
Click to collapse
You can use Sunshine. But, if I understood correctly, your phine was never s-off. If that's true, you need to unlock your bootloader again, use Sunshine to get s-off, and then follow my steps
donkeykong1 said:
You can use Sunshine. But, if I understood correctly, your phine was never s-off. If that's true, you need to unlock your bootloader again, use Sunshine to get s-off, and then follow my steps
Click to expand...
Click to collapse
I see, so the only way to have the phone LOCKED is to root it and use Sunshine?
Matt.Murdock said:
I see, so the only way to have the phone LOCKED is to root it and use Sunshine?
Click to expand...
Click to collapse
Tecnicaly, you only need to unlock the bootloader and use Sunshine. No need to root, but, in general, the answer is yes
rooting without s-off
donkeykong1 said:
Tecnicaly, you only need to unlock the bootloader and use Sunshine. No need to root, but, in general, the answer is yes
Click to expand...
Click to collapse
how do you even get a verizon htc 10 with oreo installed rooted in the first place if the HTCdev site is unable to unlock your bootloader, Sunshine is unable to unlock your bootloader or S-Off? There is nothing on the internet that has this "Solved" issue that I've read. However after reading your response, are you sure anyone can unlock bootloader and then use sunshine without root?
pearson_1974 said:
how do you even get a verizon htc 10 with oreo installed rooted in the first place if the HTCdev site is unable to unlock your bootloader, Sunshine is unable to unlock your bootloader or S-Off? There is nothing on the internet that has this "Solved" issue that I've read. However after reading your response, are you sure anyone can unlock bootloader and then use sunshine without root?
Click to expand...
Click to collapse
If you read the first post, you will see that OP is running an US unlocked with Verizon ROM. In that case my steps are correct. If you have Verizon phone, you can't even unlock bootloader, so this is of no use for you
donkeykong1 said:
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
Click to expand...
Click to collapse
Hi. Sunshine .Pay once Or pay every time you use.
osakajung said:
Hi. Sunshine .Pay once Or pay every time you use.
Click to expand...
Click to collapse
Once
pearson_1974 said:
how do you even get a verizon htc 10 with oreo installed rooted in the first place if the HTCdev site is unable to unlock your bootloader, Sunshine is unable to unlock your bootloader or S-Off? There is nothing on the internet that has this "Solved" issue that I've read. However after reading your response, are you sure anyone can unlock bootloader and then use sunshine without root?
Click to expand...
Click to collapse
Only way is to mail your phone to the sunshine team
donkeykong1 said:
Once
Click to expand...
Click to collapse
I pay on the first to s-off/unlock bootloader.
I flash other rom.
I set "fastboot oem writesecureflag 3" to s-on.
I download Sunshine to set s-off/Lock bootloader is not pay?
osakajung said:
I pay on the first to s-off/unlock bootloader.
I flash other rom.
I set "fastboot oem writesecureflag 3" to s-on.
I download Sunshine to set s-off/Lock bootloader is not pay?
Click to expand...
Click to collapse
No. Once you pay for Sunshine, it's free for you to use as many times sa you need, as long as you don't change your motherboard
donkeykong1 said:
No. Once you pay for Sunshine, it's free for you to use as many times sa you need, as long as you don't change your motherboard
Click to expand...
Click to collapse
Thank you