After lock bootloader need change slot ? For booting
In 10.0.13 booting fine with unlocked BL
I locked and not booting stuck in android one logo change slot from adb A To B ? Thanks
You should only lock the bootloader as part of flashing a complete stock ROM. There's no need to switch slots after that, both slots get flashed.
If you locked without being completely stock the system won't boot. Unlock from fastboot and then you can flash.
Related
• Purpose of this thread is Just to know
• What would be the consequences to take if I flashed a custom recovery with locked bootloader
• eMMC of my old LG G3 had gone to techiy heaven when I didn't unlock the bootloader
no its not possible to flash custom stuff with locked BL how ever its possible to switch between openbeta rom and stable oos rom ( stock )
With a locked bootloader, the phone will refuse to flash any file not signed with OnePlus's key. The bootloader only prevents you flashing an image through fastboot thought, so you could technically still flash images if you manage to load a custom recovery on the phone while the bootloader is locked. Certain phones with unlockable bootloaders may have exploits that allow users to install a custom recovery, though this is highly unadvisable as there is a real chance that you'll brick your phone. If you try to flash a custom recovery while the bootloader is locked, you'll just get an error message.
Thanks Lads !
Quite couraged me to get back to work
Hey everyone,
My nexus 5x froze shutdown yesterday.
My phone uses TWRP and Cyanogenmod. After it happen I couldn't even boot into *recovery* ! The phone just "turns off" and I cannot turn it on for quite a while.
Eventually I was after to get into bootloader to use fastboot.
I tried to reflash the recovery. The flashing worked but I still couldn't boot into recovery.
I read somewhere someone who wrote that he/she locked and than unlocked the OEM lock and it worked for some reason, so STUPIDLY I locked my OEM, and when I try to unlock again it says I cannot unlock it (although I did enable OEM unlock in the first place, that's how I flashed in the first place).
SO HERE's the bottom line:
I am stuck with OEM lock enable and ONLY fastboot (cannot load into recovery).
I thought I installing OTA (which I can install with OEM lock), but I need ADB for that which I don't have.
ANY IDEAS????
THANKS A LOT IN ADVANCE GUYS!
Hello everyone, so my phone is rooted with stock recovery.
After searching here and on other forums about how to relock bootloader I still haven't seen a clear step by step guide.
So here are my questions:
1- Does trying to lock bootloader while rooted will break the device ?
2- Do I have to flash the factory image then run both lock and lock_critical ?
3- If yes, do I have to flash the factory image on both slots or is it done automatically while running the flash-all command?
If you were rooted and got back to stock with locked bootloader please share the exact steps you took .
Thanks a lot.
youssefkr said:
Hello everyone, so my phone is rooted with stock recovery.
After searching here and on other forums about how to relock bootloader I still haven't seen a clear step by step guide.
So here are my questions:
1- Does trying to lock bootloader while rooted will break the device ?
2- Do I have to flash the factory image then run both lock and lock_critical ?
3- If yes, do I have to flash the factory image on both slots or is it done automatically while running the flash-all command?
If you were rooted and got back to stock with locked bootloader please share the exact steps you took .
Thanks a lot.
Click to expand...
Click to collapse
1. Yes. Locking the bootloader while rooted usually will brick your device.
2. You only need to the locking command. No need for critical.
3. The flash-all with the -w intact will flash to both slots.
While I have not locked the bootloader, the procedure by several others has been....
Remove all things root, including modules and magisk manager.
Do a factory reset.
Flash the factory image with fastboot.
Leave the OEM unlocking and USB debugging turned on.
Lock your bootloader.
Be advised, many of us usually don't recommend locking the bootloader because we've seen a few bricks come out of this procedure. However, it is your call. Just make sure your device is full stock before fastbooting the locking command :good:
Badger50 said:
1. Yes. Locking the bootloader while rooted usually will brick your device.
2. You only need to the locking command. No need for critical.
3. The flash-all with the -w intact will flash to both slots.
While I have not locked the bootloader, the procedure by several others has been....
Remove all things root, including modules and magisk manager.
Do a factory reset.
Flash the factory image with fastboot.
Leave the OEM unlocking and USB debugging turned on.
Lock your bootloader.
Be advised, many of us usually don't recommend locking the bootloader because we've seen a few bricks come out of this procedure. However, it is your call. Just make sure your device is full stock before fastbooting the locking command :good:
Click to expand...
Click to collapse
Got it.
thanks a lot for a thorough answer.
Just wanted to update:
So here are the steps I took to re lock the bootloader on a rooted Pixel 2 XL:
1- Flashed the latest android 10 image; just executed the flash-all bat file (that will take care of flashing everything in both slots)
2- Booted the phone and enabled USB debugging in the developer settings.
3- Booted again in download mode and typed only this command : fastboot flashing lock.
4- And that's it.
Hope this helps anyone in the future.
Anyone know how to lock the bootloader successfully? Clarification - I can lock the bootloader successfully but then can't boot normally.
I have a Frankenstein LG G7 emw from Aliexpress.
I have crossflashed it with an open EUR 10 Q kdz (G710EM)
After flashing the V35 onto abl_a and using "fastboot oem lock" the command is successful.
If I then restore my backed up original abl_a I then get a red triangle bootloop. I also sometimes get an unpatched fastboot screen with correct model type (G710EMW instead of the V35 one)
However I am unable to boot normally and then have to restore the V35, unlock the bootloader again, restore original abl, get into download mode and then reflash kdz using LGUP.
What do I need to lock the the bootloader and then boot normally? I want to be able to use Google pay and banking apps
Any help, ideas, tips or clues appreciated
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
sourabh7625 said:
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
Click to expand...
Click to collapse
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
gridmuncher said:
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
Click to expand...
Click to collapse
It was running on competely stock just booted into fastboot from using "adb reboot bootloader" and entered "fastboot oem lock" and everything worked fine.
What's state your phone currently in ? And what is your desired state ?
I have cross flashed the phone with an Android 10 kdz (european 30f). The bootloader is unlocked, but I cannot relock the bootloader. I have erased the laf_a partition to enable fastboot, but then "fastboot oem lock" doens't work. If I flash the v35 to abl_a then th command works but then the phone is in a red triangle bootloop.
I have tried extensively to google it but I have no idea how to make it work. I backed up numerous partitions using QFIL and tried to restore them once bootloader was locked but nothing seemed to help. The only way out of the bootloop was to return to download mode a reflash a kdz using LGUP
Hi I have the wifi only gt310 and when I go to developer options there is no OEM unlock feature. I can get to recovery though using power and vol up on boot. Im just wondering if I can proceed to flash a new rom or if I need to unlock the bootloader - as I have not been successful with finding those instructions on how to do this
I was able to use adb to see my device but fastboot bootloader restart did not work. It seemed to hang on waiting for device.
You don't need to unlock bootloader on wifi only versions