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
Related
Hello team,
I had 4.03 with unlocked BL and TWRP installed. I reinstalled the stock N recovery first. When I use the command "fastboot oem lock" it ask me to say yes and I do, it reboots and flashes the white symbol and reboots, stuck in this bootloop. Anybody seen this before or have a fix? I am trying to restore to stock to sell.
thanks,
Nope I didn't have an issue like you. 2 attempt of going back to stock and never had an issue. Did you successfully flash the stock recovery?
Just use the unbrick meathod it resets everything
kingheri1 said:
Nope I didn't have an issue like you. 2 attempt of going back to stock and never had an issue. Did you successfully flash the stock recovery?
Click to expand...
Click to collapse
Yes- I did flash the stock recovery. But when I do the "fastboot oem lock" it just boot loops- any ideas?
aaronc_98 said:
Hello team,
I had 4.03 with unlocked BL and TWRP installed. I reinstalled the stock N recovery first. When I use the command "fastboot oem lock" it ask me to say yes and I do, it reboots and flashes the white symbol and reboots, stuck in this bootloop. Anybody seen this before or have a fix? I am trying to restore to stock to sell.
thanks,
Click to expand...
Click to collapse
You should never lock the bootloader with non stock recovery or boot image. The security in newer devices is a lot meaner.
There are two ways you can resolve this:
Method 1:
You'll need to unlock the bootloader first. Try getting into fastboot and run "fastboot oem unlock".
If it allows unlocking you're done, just flash everything stock (first the recovery and then OOS 4.0.3 via the ADB option in the recovery). Then, go to fastboot and relock the bootloader. Should work since it worked many times for me.
Method 2:
If it doesn't allow and you're in TWRP you can't do any flashing since the locked bootloader won't allow TWRP to boot.
In this case, contact OnePlus Support via Live Chat and tell them you got a software issue with your phone.
They'll give you links to three files needed for flashing the device. Download those and let them know. They'll flash your device via remote support within a week. No matter what S/W state it is in.
Hope it helps
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!
After using the motorola smart tools and trying to flash the smartfone
the device only starts up to the bootloader
the bootloader is locked
I'm not in the recovery mode he always jumps back to the boot loader.
if I connect the device to the pc then it starts without turning up in the boot loader.
is there still a solution, or do i have a new paperweight
tomtom_38 said:
After using the motorola smart tools and trying to flash the smartfone
the device only starts up to the bootloader
the bootloader is locked
I'm not in the recovery mode he always jumps back to the boot loader.
if I connect the device to the pc then it starts without turning up in the boot loader.
is there still a solution, or do i have a new paperweight
Click to expand...
Click to collapse
Did you try blank flash yet?
Forget everything, and try to manually boot into TWRP.
Download TWRP for payton from the TWRP site (Img and Zip files for V3.2). Download and install Minimal ADB, Copy TWRP img file into the ADB install directory, put your phone into bootloader mode, connect to PC and run "fastboot boot twrp-3.2.3-1-payton.img" on the ADB commandline. The phone will boot into TWRP. You'll have to mount the storage and copy the TWRP .zip file into your phone and flash that from TWRP. Now you got TWRP flashed as the recovery.
Now it's a matter of flashing a ROM. I'm not really sure about stock firmware because i haven't flashed them before, but if you want to flash a custom ROM, make sure you flash TWRP after flashing the ROM without rebooting into system or recovery.
PS: I assumed you know how to do this with this explanation. Let me know if you need more instructions.
the bootloader is locked and I cant unlock them
because oem unlock option is not activ
the last time my pattern was requested, nevertheless
I havent access to twrp. it was blocked
is there another option?
tomtom_38 said:
the bootloader is locked and I cant unlock them
because oem unlock option is not activ
the last time my pattern was requested, nevertheless
I havent access to twrp. it was blocked
is there another option?
Click to expand...
Click to collapse
Do you try to get the unlock code on Moto website to unlock bootloader?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
yes the problem ist that you have to switch on the oem bootloader option in the dev menü, but I cant do that anymore
Hello, owner of a Xiaomi Mi A2 running the June update.
I recently unlocked the bootloader through "fastboot oem unlock" command. Ever since I am stuck in bootloop. I have managed to boot in TWRP using a specific img for the device, but I am not sure how to proceed. Is it possible to install a stock rom and start all over?
thymiosK said:
Hello, owner of a Xiaomi Mi A2 running the June update.
I recently unlocked the bootloader through "fastboot oem unlock" command. Ever since I am stuck in bootloop. I have managed to boot in TWRP using a specific img for the device, but I am not sure how to proceed. Is it possible to install a stock rom and start all over?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/help/strange-issue-mi-a2-t3945125
thymiosK said:
Hello, owner of a Xiaomi Mi A2 running the June update.
I recently unlocked the bootloader through "fastboot oem unlock" command. Ever since I am stuck in bootloop. I have managed to boot in TWRP using a specific img for the device, but I am not sure how to proceed. Is it possible to install a stock rom and start all over?
Click to expand...
Click to collapse
You should read this flashing guide first and then proceed further...
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
There is a link of how to unlock bootloader properly in the same thread so read that too... I think you missed the flashing unlock critical part during unlock bootloader process so if you are still in stock then do it first so that you can able to flash stock later or else it would be difficult for you to flash back stock..
Since I was able to get int fastboot I tried countless times locking and unlocking bootloader. After numerous retries I have also managed to install a stock rom I found online using the TWRP. And it did work. I got my phone back to working. Thank you anway.
I was locking my bootloader to try to reroot and pass safetynet. So, I factory reset it, set it up, and then went into the bootloader and typed "fastboot flashing lock". I selected yes to confirm the locking of my bootloader and then my phone rebooted. But now my phone says "Can't find valid operating system" and I can't boot into Android. i was able to unlock the bootloader again but now i don't have magisk installed and I can't even boot into Android to install anything. Is there anything i can do to fix this?
Yes, if you're bootloader is unlocked then you can fastboot flash (or use Chrome web based Android Flash Tool) factory images from https://developers.google.com/android/images
If you want to root extract the boot.img from the zip and patch with Magisk, then fastboot flash boot magisk_patched.img after you boot the phone once on stock unrooted kernel.
Thank you. I did it with the flash tool. Then later, it happened again and I realized I could use the boot.img. I'm glad these Google pixels are noob friendly.
Never lock your bootloader unless you know for a fact that you are on bone stock OEM firmware.