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
I unlocked my bootloader, installed twrp and several roms to try them out, then decided to go back to stock. Currently have OOS 3.5.4 installed with stock recovery (that came with the toolkit). However, whenever I try to lock the booltloader again, the phone won't boot up. It will bootloop, or just stay off with the led glowing white. I tried to sideload the stock ROM from OnePlus, but it fails after about 45% completion. I tried both 3.5.3 and 3.5.4 and both fail after about 45%. The only way to get the phone to boot again is by unlocking the bootloader again, then it boots just fine. Tried unlocking with the toolkit as well as fastboot oem lock. Both give me the prompt on the phone, then wipe the phone and go into the bootloop.
Any suggestions on how to re-lock the bootloader? I want to be able to get the OTA update, which I think will fail with an unlocked bootloader. Note, I have also tried loading the Nougat update from settings - system update - local upgade (both full and update) and they also fail to load shortly after booting to recovery.
Thanks,
TR
Instead of using the toolkit, try just doing it manually.
fastboot oem lock IS the correct way to lock the bootloader.
If you're running into all those issues, try to reflash the stock rom from the official site. OR try this
NOTE: This WILL wipe everything on your phone so make a backup first!
First Unlock booloader1. On your phone go into Developer screen (Settings --> Developer Options)
If you don't have this go back to Settings --> About Device. Tap "Build number" 7-10 times to unlok developer options
2. In Developer Options turn on "USB Debugging" and "OEM Unlock"
3. Open ADB in command prompt and go to the directory where ADB is.
Type adb reboot bootloader
4. Once your device is in fastboot mode, type in fastboot devices to make sure your device is listed
5. Type in fastboot oem unlock to unlock your device bootloader
You can check to make sure it was properly unlocked by typing in fastboot oem device-info.
6. Reboot into your system
Files we need7. Download the following files:
TWRP - https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.2-0-oneplus3t.img
No-verity-opt-encrypt - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
Magisk - http://tiny.cc/latestmagisk
Phh-Superuser - https://forum.xda-developers.com/attachment.php?attachmentid=3988488&d=1483407725
Latest Stable Nougat Rom - http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
8. Copy all the files to your phone (keep the original on your pc just in case)
9. Load back up to fastboot mode
In ADB type adb reboot bootloader
10. Flash twrp img we downloaded above by typing
fastboot flash recovery twrp-3.0.2-0-oneplus3t.img
11. After this reboot into the system
Install all of our downloaded files through TWRP12. Now boot into recovery by issuing the following ADB command
adb reboot recovery (you should go into TWRP)
13. Once you're in twrp flash the "no-verity-opt-encrypt-5.0.zip" file OR you can format the data partition to f2fs to prevent the dm-verity error.
14. Now install the stock stable nougat rom we downloaded above
15. Do a factory system wipe / cache & dalvik
16. Install magisk through TWRP
17. Wipe cache/dalvik
18. Install phh SuperUser
19. Now reboot into the system normally.
NOTE: This *COULD* take a while since you did a clean install of nougat so just be patient and you should be good to go after this.
Thanks for the reply.
I did do fastboot oem lock, and it results in an unbootable system. fastboot oem unlock makes it bootable again. Not sure why. Also, whenever I do adb sideload <any_rom> it fails after about 45%. Not sure what's happening. Your instructions would get me to Nougat with TWRP and an unlocked bootloader, which may be what I end up doing, but I was trying to get back to fully stock, and locked again, so that OTA's will work properly. If nothing else works, I will go the route you suggest above.
Thanks again!
I just figured I'd try to get you to a working system/phone. After you get all that working you can probably lock your bootloader back to default. Now, I'm not 100% sure, but I believe that if you have a custom recovery you will need to restore that to stock as well before setting the bootloader back to locked.
TXRangerXDA said:
I unlocked my bootloader, installed twrp and several roms to try them out, then decided to go back to stock. Currently have OOS 3.5.4 installed with stock recovery (that came with the toolkit). However, whenever I try to lock the booltloader again, the phone won't boot up. It will bootloop, or just stay off with the led glowing white. I tried to sideload the stock ROM from OnePlus, but it fails after about 45% completion. I tried both 3.5.3 and 3.5.4 and both fail after about 45%. The only way to get the phone to boot again is by unlocking the bootloader again, then it boots just fine. Tried unlocking with the toolkit as well as fastboot oem lock. Both give me the prompt on the phone, then wipe the phone and go into the bootloop.
Any suggestions on how to re-lock the bootloader? I want to be able to get the OTA update, which I think will fail with an unlocked bootloader. Note, I have also tried loading the Nougat update from settings - system update - local upgade (both full and update) and they also fail to load shortly after booting to recovery.
Thanks,
TR
Click to expand...
Click to collapse
I also have the same problem, after the bootloader lock the phone does not start.
I tried with all the possible procedures, also even the rom flash in local and sideload it does not work, It comes to 45% and then fails.
we will highlight the problem, so everyone will know and maybe there is a solution
m0d hipp¥ said:
I just figured I'd try to get you to a working system/phone. After you get all that working you can probably lock your bootloader back to default. Now, I'm not 100% sure, but I believe that if you have a custom recovery you will need to restore that to stock as well before setting the bootloader back to locked.
Click to expand...
Click to collapse
But of course, you can't relock phone with a non standard recovery. Replace TWRP with the ROMs real recovery and relock will work again.
That's what I figured. Thanks for the confirmation.
Use the unbrick tutorial to go back to stock
This is what i did
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
pitrus- said:
But of course, you can't relock phone with a non standard recovery. Replace TWRP with the ROMs real recovery and relock will work again.
Click to expand...
Click to collapse
I'm sorry, even with the stock recovery but does not work, it was the first thing I did
You can a unbick tutorial. It worked for my OnePlus 3T. Just search up How to unbrick (whatever OnePlus device you have) on Google. Then follow all the instructions carefully. If you need help with it I could try to do a remote session with you. Edit: It will erase all data and you will boot with oos 3.5.3 ( I also had the same issue as you. But I couldn't install any zip with stock recovery or adb side load.
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
enokack said:
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
Click to expand...
Click to collapse
Only if you have modified the phone in some way or another (like rooting and installing twrp) before trying to re-lock.
If you keep it stock, you should be able to re-lock. Or else, just use the Qualcomm restore method to re-lock.
tried this
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
I think the problem in re-locking it is the modified boot image. Locked bootloaders don't support those.
re-locking bootloader will getback the warranty ???
No solutions till now
enokack said:
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
Click to expand...
Click to collapse
Its three easy steps, no need to use any toolkit just follow the instructions. https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Abrar123 said:
re-locking bootloader will getback the warranty ???
Click to expand...
Click to collapse
Unlocking the bootloader does not void the warranty on this device:
https://oneplus.net/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
Once I have root, is there a command to re-lock and later eventually unlock the bootloader again?
I remember this was possible with google nexus devices, there was a shell command (require root) that was able to change bootloader status
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
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
Hi,
I recently bought a Redmi 8 and installed Magisk through TWRP. It gets installed successfully but relocks the bootloader at the software level (unlock status in developer options says the phone is still locked, but the boot animation says the phone is unlocked).
My Issue is that I cannot perform any root action and I believe the relocked bootloader is the cause. How can I fix this?
I've tried pulling the unlocked the boot.img through adb and patching it through the magisk app but that also has the same result.
Any help will be greatly appreciated.
uz3390 said:
Hi,
I recently bought a Redmi 8 and installed Magisk through TWRP. It gets installed successfully but relocks the bootloader at the software level (unlock status in developer options says the phone is still locked, but the boot animation says the phone is unlocked).
My Issue is that I cannot perform any root action and I believe the relocked bootloader is the cause. How can I fix this?
I've tried pulling the unlocked the boot.img through adb and patching it through the magisk app but that also has the same result.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
If anyone is having the same problem, it took me a while but I was able to fix it. Another is issue was the recovery kept getting wiped with every reboot and I think this was causing the above issue.
These are the steps I took to fix it-
1. Download the respective rom for your phone (I used a stock global rom)
2. Extract the rom, in it there is a folder called images and in that folder there is a file called vbmeta.img. Save this file to your fastboot folder.
3. After you flash the recovery, flash the vbmeta.img using this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
After doing the above, I was able to flash magisk and get the root working.
Thanks to @J0SH1X (For the fastboot command to disable the avb)