Is there a way to put bootloader in 'Locked' instead of 'Relocked' ? My phone was unlocked and S-off. I put it back to S-on, and tried to locked the bootloader with cmd 'fastboot oem lock', but in the bootloader it says 'relocked'. I wonder if there's a way to put it in 'locked', and not flashing RUU....
thank you!
you need to lock your bootloader while you are putting the phone back to s-on... there's a guide somewhere let me find it for you..here's the thread about how to lock the bootloader and s-on the phone
The only way I know of is to be s-off then flash the stock RUU. It will read "Locked" after its completed.
Related
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
shawnten said:
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
Click to expand...
Click to collapse
If the RUU doesn't work, the other two alternatives are to attempt to flash the stock system.img and stock boot.img through fastboot .. although I'm not sure this will work with S-ON, depends on whether or not the device is locked/unlocked via HTC's official method.
Also, the second alternative, could use the PG*zip file which is stored inside the RUU. the zip file can be extracted from the RUU and placed on the root of the sdcard. Then the bootloader will grab this file and flash, essentially performing the same thing as the RUU would.
can any one help please.
i bricked my phone but did the ruu after relocking the bootloader. Now it says relocked in the fastboot mode.
i tried google to look for answers but could not find any.
by the way i have s-off which i guess is a problem.
so could anyone tell the way around it to reunlock the bootloader so i can root and install updated roms .
thanks in advance.
a
kishanyonzan said:
can any one help please.
i bricked my phone but did the ruu after relocking the bootloader. Now it says relocked in the fastboot mode.
i tried google to look for answers but could not find any.
by the way i have s-off which i guess is a problem.
so could anyone tell the way around it to reunlock the bootloader so i can root and install updated roms .
thanks in advance.
Click to expand...
Click to collapse
The method is the same for S-OFF as S-ON. Since, you are S-OFF you can use the Guru Bootloader Reset tool in TWRP after you unlock it the HTCDev method.
You do not have to relock your bootloader to run RUU or firmware when you are S-OFF.
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...??
BBEgo said:
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
Click to expand...
Click to collapse
Wonders_Never_Cease said:
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...
Click to expand...
Click to collapse
That's weird.... I thought I posted this in the Q&A forum. I was just in there looking for it and I thought it'd gotten deleted or something. Oh well.
Mods, please feel free to correct my goof.
I didn't use HTCDev to unlock. I just did Sunshine and it handled everything. S-off, unlock, and root - Talk about painless! After that I installed a custom recovery (Philz) and I was off to the races.
So I decided to SuperCID my phone so I can install whatever I want. No problem.
Then I tried to install 5.0.1 firmware (4.16.1540.8) so I could run SkyDragon, but the firmware posted on page 1 in the thread would not install- 4.16.1540.8
Kept giving me "FAILED (REMOTE:24 parsing android-info fail)"
I was able to install 4.16.401.9 with no major headaches, once I found a sensible upgrade path. That one is working fine, but I don't understand why 4.16.1540.8 would not install.
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
So now I'm S-off, locked bootloader, PhilZ recovery (put it back on with Flashify), SuperCID, on Lollipop, and I guess everything is ok. But I still don't understand why the phone wouldn't take the firmware.
Any ideas? Thanks in advance.
If you ran sunshine on it,you can run it again i believe on that same device. It should unlock it again,if not then can try htcdev as it also uses fastboot to unlock as long as you can get adb to show needed code.
BBEgo said:
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
Click to expand...
Click to collapse
In the past (at least on my One X EVITA) my understanding was that s-off meant that all security was bypassed. Meaning that bootloader check was effectively bypassed.
This isn't the case for the M8. From what I can tell a LOCKED bootloader still prevents you from flashing anything that isn't signed (anything "unofficial") even if s-off.
However, having an UNLOCKED bootloader doesn't seem to affect anything while s-off. Meaning you can do things like RUU when UNLOCKED (which normally needs to be LOCKED or RELOCKED if s-on).
In short, I don't ever recommend relocking the bootloader if s-off on this device. There isn't any reason to, as far as I can tell. Meaning, having an UNLOCKED bootloader doesn't prevent you from doing anything. However, a RELOCKED bootloader does (even when s-on) prevent some things.
I need to return my Nexus 9 to stock to get a warranty return from HTC. I know exactly what to flash, and how to relock the bootloader, my question is does it leave any evidence of being relocked? Does the text at the top of Hboot say Locked, or relocked. How about the "this is a development device" red text? Will flashing the stock bootloader, recovery, system, etc fix that? Finally, will there be any evidence if they run "fastboot oem device-info " on hboot?
I just want to be 100% clear that there wont be any evidence of bootloader unlock when I'm done.
Thanks!
thekalby said:
I need to return my Nexus 9 to stock to get a warranty return from HTC. I know exactly what to flash, and how to relock the bootloader, my question is does it leave any evidence of being relocked? Does the text at the top of Hboot say Locked, or relocked. How about the "this is a development device" red text? Will flashing the stock bootloader, recovery, system, etc fix that? Finally, will there be any evidence if they run "fastboot oem device-info " on hboot?
I just want to be 100% clear that there wont be any evidence of bootloader unlock when I'm done.
Thanks!
Click to expand...
Click to collapse
Did you get any answer? I just bricked mine (still locked) by trying to wipe /cache. Thinking about unlocking it, but I want wo return it next month because the Back is dissolving
Hi, i ejecute "fastboot oem lock" and my bootloader gets "Relocked", how i can get "Unlocked" again? i tryed to donwgrade from 5.02 to 4.1, but i fail, now i want to get unlock again, help me plese. :crying:
carma66 said:
Hi, i ejecute "fastboot oem lock" and my bootloader gets "Relocked", how i can get "Unlocked" again? i tryed to donwgrade from 5.02 to 4.1, but i fail, now i want to get unlock again, help me plese. :crying:
Click to expand...
Click to collapse
to unlock your bootloader you have to use the method made for your bootloader, if there is one.
downgrade is only possible while s-off, btw.
el_venga said:
to unlock your bootloader you have to use the method made for your bootloader, if there is one.
downgrade is only possible while s-off, btw.
Click to expand...
Click to collapse
Hi. Many thanks. I used sunshine to unlock and s-off. When I open sunshine again it says it's already rooted and I can't unlock bootloader. Any idea?
carma66 said:
Hi. Many thanks. I used sunshine to unlock and s-off. When I open sunshine again it says it's already rooted and I can't unlock bootloader. Any idea?
Click to expand...
Click to collapse
if you used sunshine s-off, you are already able to downgrade. if you are s-off with that method, and most others, you dont need to relock to downgrade. just flash ruu through fastboot. for that issue, contact sunshine. never been in that situation but you should still downgrade if S-OFF'ed.