Related
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
happimeal said:
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
Click to expand...
Click to collapse
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Thank you for a great explanation.
If you ask the people at xposed modules they may be able to do something maybe....
5.1 still displays bootloader unlocked message.
cschmid44 said:
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Click to expand...
Click to collapse
I have installed h815 KDZ files using LGUP. When i reboot it still displays Bootloader unlocked message. I can not use bootloader unlock/lock guide as I have bootloader unlocked.
Any other means to get rid of the message.
bump for way to relock h815
Hi, i'm new on huawei phones, always had samsung before, i buy a p9 vie-al10c00 from china.
Last week i unlock the bootloader of my phone and made root.
yesterday i receive an update and install it.
After that my bootloader is locked again!
Is it normal? Because to unlock it again it needs a factory reset again right?
If you update with the "full" package then BL will be locked again...and that seems to be the only way to update the official packages for rooted phones now (first flash Full 192 then OTA 195).
Before unlock the BL do a full backup on the phone, once unlocked immediately install TWRP and do a full restore on the phone...
Of course if you don't care about root, then just leave the BL locked...
I remembered some people also mentioned before you can just flash back the official Recovery and run the update and flash back TWRP after, that way BL won't be locked, however I am not sure how I can save a copy of the official recovery first for flashing back.
Stock recovery, found in another thread
P9 Plus Stock Recovery
zhuanyi said:
If you update with the "full" package then BL will be locked again...and that seems to be the only way to update the official packages for rooted phones now (first flash Full 192 then OTA 195).
Before unlock the BL do a full backup on the phone, once unlocked immediately install TWRP and do a full restore on the phone...
Of course if you don't care about root, then just leave the BL locked...
I remembered some people also mentioned before you can just flash back the official Recovery and run the update and flash back TWRP after, that way BL won't be locked, however I am not sure how I can save a copy of the official recovery first for flashing back.
Click to expand...
Click to collapse
so if i unlock the bootloader and install twrp and then do a regular ota update will the bootloader be locked forever again since you can't unlock it on newer emui, or will i be safe from it relocking in any way once twrp has been flashed?
suppose I unlock my bootloader, install custom recovery like TWRP and now, If I wish to RE LOCK my bootloader ( dont ask why), is it necessary to have the STOCK recovery installed before relocking or custom recovery will be fine?
Thanks.
Relocking the bootloader is NOT recommended. That said, you can and should keep TWRP if you choose to lock it.
Oh okay. I read somewhere that if you choose to re lock your bootloader you have to go FULL STOCK ( ROM + Recovery). I guess that might not be the case for nexus devices?
Relocking the bootloader will wipe your data, but it doesn't play cop and make sure everything is stock. All the bootloader does is pass off control of the device from the low level firmware that we cannot access to either the recovery or Android itself. Locking the bootloader only ensures that the possessor of the device cannot change the contents of the partitions from outside the device using ADB. A device with TWRP and a locked bootloader can still install custom ROMs, and possibly even root.
However, there is practically zero reason to ever lock the bootloader once unlocked, leaving people to wonder why you would want to.
Note, this is my first attempt at rooting and flashing a custom rom.
I unlocked the bootloader and attempted to flash cm. Also used SuperSU and twsp to backup. The flash did not go through, as far as I could tell. The phone would still boot, with the warning, however once I attempted an OTA update from 4.4 to 5.0 the phone is now stuck on the unlocked bootloader warning. HELP!!!
naboyd32cp said:
Note, this is my first attempt at rooting and flashing a custom rom.
I unlocked the bootloader and attempted to flash cm. Also used SuperSU and twsp to backup. The flash did not go through, as far as I could tell. The phone would still boot, with the warning, however once I attempted an OTA update from 4.4 to 5.0 the phone is now stuck on the unlocked bootloader warning. HELP!!!
Click to expand...
Click to collapse
When in fastboot mode, device is UNLOCKED, Status Code 3, Software Status Modified. Any help would be appreciated!
I'm returning my phone to Three, so need to return to stock
I plan on:
- uninstall Magisk
- remove pin/fingerprint/face unlock
- factory reset
- boot to eRecovery and flash stock
- lock bootloader.
Is this the correct order to do things?
Will I still have adb access to lock the bootloader after flashing stock?
If not, will I still be able to get to eRecovery if I've locked the bootloader first?