Re-locking bootloader on pixel 4 - Google Pixel 4 Questions & Answers

Re-locking bootloader on pixel 4 - Google Pixel 4 Questions & Answers

Hi! I am flashing AOSP on a pixel 4 and pixel 4a device, but once after flashing the AOSP into the device, it works fine until the device is in flashing unlock state but when I tried to re-lock the bootloader, the pre-installed AOSP would not load and the device shows error "Invalid OS" failed to load OS.
Can you guide me on how to re-lock after flashing especially in pixel 4 and 4a devices?
Attached below is the issue I'm facing right now
Waiting for your response.
Thank You

Re-locking the bootloader forces it to boot into pre-installed ROM.

jwoegerbauer said:
Re-locking the bootloader forces it to boot into pre-installed ROM.
Click to expand...
Click to collapse
HI! Thank you for your valuable suggestion but the problem I am facing is that when I flash the AOSP into the device specifically pixel 4 and pixel 4a, it works properly in flashing unlock state but when I try to re-lock the bootloader with the command "fastboot flashing lock", the device will not load the pre-installed OS and show an Invalid OS error.
Could you help me out in this scenario?

You didn't get it for whatever reason.
The pre-installed OS got removed - means overwritten by the one you flashed.

UsamaBinAmir said:
Hi! I am flashing AOSP on a pixel 4 and pixel 4a device, but once after flashing the AOSP into the device, it works fine until the device is in flashing unlock state but when I tried to re-lock the bootloader, the pre-installed AOSP would not load and the device shows error "Invalid OS" failed to load OS.
Can you guide me on how to re-lock after flashing especially in pixel 4 and 4a devices?
Attached below is the issue I'm facing right now
Waiting for your response.
Thank You
Click to expand...
Click to collapse
If you want to lock the bootloader, but not run stock OS, you can try Graphene OS. https://grapheneos.org/

The bootloader lock checks to see if the operating system has been modified. By flashing anything other than official Google firmware (ie factory images/full ota) you fail those checks.

Related

[Q] bootloader issues

So a while ago I rooted my phone but messed it up because I uninstalled a few too many system apps. I just dealt with it for a few months since I could still make calls (but not much else). I finally bit the bullet to look into flashing the stock rom again, but to do so it looked like I had to install a custom recovery, but to do that, unlock the bootloader. So I first unlocked the bootloader using motopocalypse (batch file didn't work but apk did), and got the expected BOOTLOADER UNLOCKED message at bootup, with fastboot saying unlocked, code 3. I then tried flashing CWM recovery via Rom Manager, and it seemed successful, but I was unable to boot to it either from the UI of ROM manager or from holding the buttons during bootup, it would just hang for a few more minutes than normal at the BOOTLOADER UNLOCKED screen, then boot up like normal. So I kept reading, found RSDlite, and was able to flash the stock rom, which I downloaded from the internet and the phone boots up fine, but now fastboot says locked, status code 2, and motopocalypse does not unlock it again (either the batch file or the apk), but I still get the BOOTLOADER UNLOCKED message at bootup. So I'm not sure if my bootloader is unlocked or not and if I can proceed with installing CWM recovery again, so i can make a full backup in case I mess something up again.
So how do I reunlock the bootloader, or verify if it's locked or not?

First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk

RikRong said:
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FB screen:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 00:54:39)
eMMC Info: Size 8GB
Device is LOCKED. Status code: 2
Battery OK
Transfer Mode:
USB connected
Fastboot reason: Reboot to bootloader
usb connected
I've tried reflashing with RSD previously but no change. I could try it once more if you want.
Not entirely sure what you're asking for with the firmware version, but the image I used was for android 4.4.2, version 183.46.10.XT907Verizon.en.US.

modemman11 said:
Device is LOCKED. Status code: 2
Click to expand...
Click to collapse
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!

To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Code 3 as well.
Sent from my XT907 using XDA Free mobile app

rahimali said:
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
Click to expand...
Click to collapse
Yes, that's why I'm asking. So I've got one vote for unlocked, one for locked. As I said though, motopocalypse isn't working a 2nd time.
AndyYan said:
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Click to expand...
Click to collapse
I would like to flash custom ROMs later down the road, but for now I just want to get the stock stuff going.
On a side note, the version of the image I downloaded was 183.x.x, but my mother, who has the same phone, purchased at the same time, and has never rooted it or anything, has version 182.something, and that is also the version I had before I started messing with the bootloader/recovery stuff. The two versions were released at the same time, but I don't know what determines which version you got if you just did OTA updates, or if it even matters. Speaking of OTA updates, the version I downloaded is prompting me to do an OTA update now to another 183.x.x version. I wonder if I'd be able to grab the 182.x.x ROM from my mom's phone without rooting it via fastboot or something.

The 182/183 does not matter regarding root/boot loader unlock its the .10/.15 that matters do not take the .15 without unlocking your boot loader....
We cannot teach people anything; we can only help them discover it within themselves.

So no other thoughts? What would happen if I flashed a custom rom/recovery with a locked bootloader? I tried flashing the ROM again and fb still says locked, code 2, and motopocalypse still doesn't do anything like it did the first time.

modemman11 said:
What would happen if I flashed a custom rom/recovery with a locked bootloader?
Click to expand...
Click to collapse
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
modemman11 said:
So how do I reunlock the bootloader, or verify if it's locked or not?
Click to expand...
Click to collapse
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock

lem22 said:
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
Click to expand...
Click to collapse
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.031s]
finished. total time: 0.031s
Still locked code 2 though. Looks like it wants an unlock code from Motorola's website, I tried following the steps to get the code but it says I'm not eligible for bootloader unlock. So unless there's another way to get the unlock code...

modemman11 said:
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
Click to expand...
Click to collapse
A "Code 0" locked device would refuse flashing an unofficial or older recovery. I have no idea about Code 2 though.

From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Same here, I can see what it means but cannot find any way to get back to code 3 other than using the unlock code from Motorola, which I am unable to obtain because it says I am not eligible. Surprising that someone hasn't cracked the unlock code yet or made a keygen, people are so eager to do it with pirated computer software before the software is even released.

I've read of someone getting locked status code 2 b4 from flashing an older gpt with rsd (if I remember correctly) I think all that was required to fix it and get unlocked again was to flash the latest gpt. Very important..... Are you sure when you were unlocked you didn't ota update to .15? Because flashing .10 gpt while on .15 may be what caused your false relock

Nope, no OTA update to .15. The ZIP I have of the rom does include the gpt.bin file with the same timestamp as all the other files. I suppose I could try reflashing the whole rom once again later...

Hmm strange, I went to find the old thread I read about the gpt relock issue but it's not exactly the same as your situation.
http://forum.xda-developers.com/showthread.php?p=51436123
Until now I didn't think relock was possible due to the way unlocking works. It's a physical change, a qfuse was blown when the motopocalypse apk was run the first time. It can't be unblown lol. Wish I knew what went wrong here.

Unlock bootloader on non-booting device?

I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?

tin2001 said:
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
Click to expand...
Click to collapse
Seriously? No one reads thread online?! I quote to NEVER, EVER, FLASH OREO/NOUGAT ROMS AFTER UPDATING TO PIE!!!

I downloaded the latest OFFICIAL ROM when it was already bootlooping.... Seriously? I'm supposed to go searching online for 3rd party information rather than the official?
Now how about people with useful information instead of arrogance?

If I'm not wrong you just need to boot into bootloader and fastboot oem unlock. With unlocked bootloader, go fastboot mode and flash official stock pie fastboot rom

Super Stucked, Nothing Helps now.

I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".

What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...

echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.

mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).

Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory: