ok so my bootloader was unlocked with s-on and i was trying to do the wire trick but i got a bootloop so i did a RUU and no i have s-off but my bootloader is locked? could i just unlock my bootloader and root or should i redo the s-off??
cwa542 said:
ok so my bootloader was unlocked with s-on and i was trying to do the wire trick but i got a bootloop so i did a RUU and no i have s-off but my bootloader is locked? could i just unlock my bootloader and root or should i redo the s-off??
Click to expand...
Click to collapse
I'm confused here:
"and no i have s-off but my bootloader is locked? could i just unlock my bootloader and root or should i redo the s-off"
So do you have s-off or do you not have s-off
Just unlock the boot loader add a recovery and flash away...if it says s-off on hboot then there is no need to redo s-off, a ruu will not remove s-off
Sent from my SGH-I997 using Tapatalk 2
I'm s-off even though I messed up on the wire trick and have to RUU, but my bootloader is locked
Sent from my HTC PH39100 using xda app-developers app
lf your s-off just unlock the bl and proceed
Do fast boot OEM relock then flash the ruu and redo everything to get s off and root
Sent from my GT-N700 using xda app-developers app
So I have converted my device into a Google Edition and am S-Off and Unlocked. My problem is Google Movies will not work because the DRM keybox in inaccessible due to the unlocked bootloader. I want to try and relock and see if it works. Anyway will my device brick if I attempt to relock the bootloader and can I just keep it locked because I have S-Off?
Yes you can, there is a command in revone to relock your bootloader. You will keep s-off, it will only relock your bootloader. Until you're not trying to get back to s-on with a custom hboot you should be save
Hello guys,
I'm currently running pure stock 4.2.2, never rooted, never s-offed, never unlocked bootloader. As it is now possible to S-OFF using rumrunner s-off, my question is whether I'll be able to re-lock my bootloader without any evidence of unlocking it through HTCDev. I know it is possible to do with revone tool, but that only works on 1.44 Hboot. As far as I know, I should be able to downgrade Hboot after obtaining S-OFF with rumrunner, but I'm not sure.
TLDR : I want to unlock bootloader on 4.2.2 using HTCDev, can I get it back to state "Locked" then ? Any guide ?
Thanks
amozonesk said:
Hello guys,
I'm currently running pure stock 4.2.2, never rooted, never s-offed, never unlocked bootloader. As it is now possible to S-OFF using rumrunner s-off, my question is whether I'll be able to re-lock my bootloader without any evidence of unlocking it through HTCDev. I know it is possible to do with revone tool, but that only works on 1.44 Hboot. As far as I know, I should be able to downgrade Hboot after obtaining S-OFF with rumrunner, but I'm not sure.
TLDR : I want to unlock bootloader on 4.2.2 using HTCDev, can I get it back to state "Locked" then ? Any guide ?
Thanks
Click to expand...
Click to collapse
Hmm rumrunner tool requires an unlocked bootloader to work so I guess you would need to unlock it through HTCDev
But once S-OFF you can set it back to "Locked" instead of "Relocked". Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2475914
Worked for my HTC One and I'm now back on a "Locked" bootloader.
jerronchua55 said:
Hmm rumrunner tool requires an unlocked bootloader to work so I guess you would need to unlock it through HTCDev
But once S-OFF you can set it back to "Locked" instead of "Relocked". Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2475914
Worked for my HTC One and I'm now back on a "Locked" bootloader.
Click to expand...
Click to collapse
Thank you for your answer. I know that unlocking the bootloader will void warranty by my carrier (Orange Slovakia) but if it is possible to downgrade Hboot after S-OFF, I'd be able to get back status "Locked", there are many guides to do that. So the question is if I can downgrade from 1.54 to 1.44 after S-OFFing the 1.54. Also, will my carrier be informed about my unlocking through HTCDev ? Can they check whether it was unlocked once via HTCDev (although it is "Locked" now) ?
Hello,
I have just managed to unroot my htc one m7 successfully after a lot of difficulty.
However, the bootloader still shows "RELOCKED" although TAMPERED is gone but I would like it to show "LOCKED" as it was before I had rooted it for the first time. Is it possible to get it back to show LOCKED while you are S-ON?
Any help will be highly appreciated.
Thanks.
singh_harman said:
Is it possible to get it back to show LOCKED while you are S-ON?
Click to expand...
Click to collapse
No
Only possible with S-OFF.
alray said:
No
Only possible with S-OFF.
Click to expand...
Click to collapse
How about if you unlock the bootloader to go S-OFF in order to get it locked and then lock the bootloader again to show S-ON?
Is this possible.
Also, even if it remains relocked, does this void warranty at all? Or does it still get recognized as never been rooted.
singh_harman said:
How about if you unlock the bootloader to go S-OFF in order to get it locked and then lock the bootloader again to show S-ON?
Is this possible.
Click to expand...
Click to collapse
Yes, you'll need to unlock the bootloader, achieve s-off, set back the bootloader to locked and remove the tampered flag, flash a RUU and then turn back s-on.
Also, even if it remains relocked, does this void warranty at all?
Click to expand...
Click to collapse
Relocked means your bootloader was unlocked and locked back. Unlocking the bootloader might void your warranty light explained on htcdev.com/bootloader.
Or does it still get recognized as never been rooted.
Click to expand...
Click to collapse
Only a phone showing S-ON and ***LOCKED*** (and without ***tampered*** or ***security warning*** flags showing) is under warranty. And even if your phone only shows S-ON and LOCKED like if it was never unlocked, they (HTC) can still look for your IMEI# in their database and know if you already requested an Unlock_code.bin file from htcdev.com to unlock your bootloader (not a problem if you are dealing with your carrier but might be a problem if dealing directly with HTC).
alray said:
Yes, you'll need to unlock the bootloader, achieve s-off, set back the bootloader to locked and remove the tampered flag, flash a RUU and then turn back s-on.
Relocked means your bootloader was unlocked and locked back. Unlocking the bootloader might void your warranty light explained on htcdev.com/bootloader.
Only a phone showing S-ON and ***LOCKED*** (and without ***tampered*** or ***security warning*** flags showing) is under warranty. And even if your phone only shows S-ON and LOCKED like if it was never unlocked, they (HTC) can still look for your IMEI# in their database and know if you already requested an Unlock_code.bin file from htcdev.com to unlock your bootloader (not a problem if you are dealing with your carrier but might be a problem if dealing directly with HTC).
Click to expand...
Click to collapse
That is what I did, when going from root to unroot I had to first lock the bootloader and when I did so, the S-OFF went to S-ON by itself, so its not like I had to do something specific in order to achieve S-ON, similarly when you unlock the bootloader S-OFF comes by itself. Suppose I just unlocked and it is S-OFF, what fastboot commands will I need to input to lock it while S-OFF remains unchanged and does not go S-ON after locking?
When I locked the bootloader, tampered flag went away by itself too...
I want to lock it ensuring its S-OFF so that it shows locked rather than relocked. What commands will I need to achieve this output?
singh_harman said:
That is what I did, when going from root to unroot I had to first lock the bootloader and when I did so, the S-OFF went to S-ON by itself, so its not like I had to do something specific in order to achieve S-ON, similarly when you unlock the bootloader S-OFF comes by itself. Suppose I just unlocked and it is S-OFF, what fastboot commands will I need to input to lock it while S-OFF remains unchanged and does not go S-ON after locking?
When I locked the bootloader, tampered flag went away by itself too...
Click to expand...
Click to collapse
There is no possible way that happened. When you unlock your bootloader, you don't automaticaly get s-off, and only way to get back to s-on from s-off is with "fastboot oem write secureflag 3" command. You got something very wrong there my friend
singh_harman said:
I want to lock it ensuring its S-OFF so that it shows locked rather than relocked. What commands will I need to achieve this output?
Click to expand...
Click to collapse
with s-off it will be very easy to remove tampered and locked your device by using Guru reset tool , it has aroma ..
http://forum.xda-developers.com/showthread.php?t=2471869
I return back to full stock with no tampered and locked status for at least 3 m7 phones.
singh_harman said:
That is what I did, when going from root to unroot I had to first lock the bootloader and when I did so, the S-OFF went to S-ON by itself, so its not like I had to do something specific in order to achieve S-ON, similarly when you unlock the bootloader S-OFF comes by itself. Suppose I just unlocked and it is S-OFF, what fastboot commands will I need to input to lock it while S-OFF remains unchanged and does not go S-ON after locking?
When I locked the bootloader, tampered flag went away by itself too...
Click to expand...
Click to collapse
donkeykong1 said:
There is no possible way that happened. When you unlock your bootloader, you don't automaticaly get s-off, and only way to get back to s-on from s-off is with "fastboot oem write secureflag 3" command. You got something very wrong there my friend
Click to expand...
Click to collapse
^^This
Unlocking the bootloader doesn't set it S-OFF and re-locking it doesn't set it S-ON neither. Its 2 completely different things.
So I thought that being S-OFF allowed you to bypass the normal locked bootloader requirement.
But I've never been able to RUU while S-OFF and unlocked - still had to relock first.
And I've never been able to flash recovery while S-OFF and locked - still had to (re) unlock first.
Any insight?
Thanks