Develop Bugs

How to Remove Boot freeze (warning screen) after unlocking bootloader

Hey there, is there possible to remove that ugly black screen after unlocking bootloader that appears every boot and freezes 5 sec? Thanks in advance.

LaurynasVP said:
Hey there, is there possible to remove that ugly black screen after unlocking bootloader that appears every boot and freezes 5 sec? Thanks in advance.
Click to expand...
Click to collapse
Do you want to relock the bootloader or you want to let it unlocked?

I would keep it unlocked and skip the black screen if possible...

I'd like to keep it unlocked since I need root, is it possible to remove it somehow?

LaurynasVP said:
I'd like to keep it unlocked since I need root, is it possible to remove it somehow?
Click to expand...
Click to collapse
I don't think that this is possible to do, even changing the splash logo you can't do that. You could try to relock the bootloader but I never tried doing that on a custom ROM, only on the stock one. I don't remember if after relocking the bootloader with the bootloader status as relocked the initial boot menu is shown. Anyway you could try. I suggest the mauronofrio's tool if you're on Windows. If you are on Linux you have to use the adb and fastboot commands

re
DD3Boh said:
I don't think that this is possible to do, even changing the splash logo you can't do that. You could try to relock the bootloader but I never tried doing that on a custom ROM, only on the stock one. I don't remember if after relocking the bootloader with the bootloader status as relocked the initial boot menu is shown. Anyway you could try. I suggest the mauronofrio's tool if you're on Windows. If you are on Linux you have to use the adb and fastboot commands
Click to expand...
Click to collapse
I assume [re]locking your BL on custom ROM will cause hard-brick. I need root so can't lock BL

LaurynasVP said:
I assume [re]locking your BL on custom ROM will cause hard-brick. I need root so can't lock BL
Click to expand...
Click to collapse
I never tried it but at the end maybe yes. I don't think hard brick but it depends on what you exactly mean with hard brick (all the people think the hardbrick as something different lol)

DD3Boh said:
I never tried it but at the end maybe yes. I don't think hard brick but it depends on what you exactly mean with hard brick (all the people think the hardbrick as something different lol)
Click to expand...
Click to collapse
I tried this and yes it cause hard brick to my zuk z2 plus. But i somehow make my exit from hard brick.

I used to have a ZTE Axon 7 that used pretty-much the exact same warning screen as the ZUK Z2. For certain ROMs on the device you had to flash a different bootloader, as provided by developers on XDA. I remember in one of the flashable bootloaders, the developer was able to remove the warning screen somehow. So I think it is possible to do this on the ZUK as well. It just needs someone to look into it.

rajatsinghsp said:
I tried this and yes it cause hard brick to my zuk z2 plus. But i somehow make my exit from hard brick.
Click to expand...
Click to collapse
Yeah just a thing, you can now relock bootloader on z2, on specific Roms. I made a guide for it and it works 100%

DD3Boh said:
Yeah just a thing, you can now relock bootloader on z2, on specific Roms. I made a guide for it and it works 100%
Click to expand...
Click to collapse
That sounds great. Although I just went and read your guide and I noticed it says the 5-second bootloader warning will still be there. Is there no way of getting rid of the warning completely even with a locked bootloader?

Is it safe to relock the bootloader?

Hi, I recently unlocked bootloader, than flashed a kernel which gave me root also, and then installed some apps than need root.
Since I unlocked the bootlader, every time I turn on the watch, a waring error appears and booting time has largely increased.
1) If if follow the same procedure to unlock, is it possible in the menu to lock it again?
2) If n.1 is possible... is it safe with a watch rooted and a custom kernel? Or do I brick something?
3) Will root and kernel still work if I lock again the watch?
Thanks

titomax82 said:
Hi, I recently unlocked bootloader, than flashed a kernel which gave me root also, and then installed some apps than need root.
Since I unlocked the bootlader, every time I turn on the watch, a waring error appears and booting time has largely increased.
1) If if follow the same procedure to unlock, is it possible in the menu to lock it again?
2) If n.1 is possible... is it safe with a watch rooted and a custom kernel? Or do I brick something?
3) Will root and kernel still work if I lock again the watch?
Thanks
Click to expand...
Click to collapse
It's completely safe. If the watch runs properly before lock, it will run properly after lock. The only thing that will change is your ability to flash unsigned images using fastboot. Keep in mind though that it will automatically factory reset if you choose to unlock it again.
Lock it using the command fastboot oem lock

If it will reset, this won't realize what I need. Thanks for this useful advise!

How to Lock Bootloader

Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.

Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I do have a computer, a Windows 10 Pro

Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.

sliding_billy said:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
Click to expand...
Click to collapse
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.

eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.

eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.

coolhandz said:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
Click to expand...
Click to collapse
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".

sliding_billy said:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
Click to expand...
Click to collapse
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.

Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.

sliding_billy said:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
Click to expand...
Click to collapse
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.

eec007 said:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Click to expand...
Click to collapse
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.

bobby janow said:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
Click to expand...
Click to collapse
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.

eec007 said:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
Click to expand...
Click to collapse
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.

eec007 said:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
Click to expand...
Click to collapse
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.

eec007 said:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Click to expand...
Click to collapse
They're right to mention that relocking a modified device can result in a brick.
Your best bet is to go to https://developers.google.com/android/images#taimen
Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.
Would suggest to do this anyway, no matter future unlock status.

TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.

TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...

Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said.

turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.

Bootloader locking not working

Op3, stock recovery and official 9.0.2 rom.
Eveything elese is fine but bootloader is unlocked and when starting phone the dm-verity says that bootloader is unlocked.
I can go to fastboot and command fastboot oem lock and phone Will show that yes and no screen, but even If I select yes phone just boots and shows that bootloader is still unlocked.
I can not fine any info for this kind of problem or how to solve this. Anybody has any ideas how to get bootloader locked?

Have you tried selecting no, instead of yes?
When I tried the first CB, I had something similar where, with the new bootloader, the responses were inverse.

morphvale said:
Have you tried selecting no, instead of yes?
When I tried the first CB, I had something similar where, with the new bootloader, the responses were inverse.
Click to expand...
Click to collapse
Yes I did try that also but did not work.
But I know figured a way to do that. I used the MSM Download tool program. That flashed some very old software but did not lock the bootloader (like I think it should do?) But after that fastboot oem lock worked. Then I sideloaded newest 9.0.2 and now bootloader is locked and phone is completely stock and works fine. So no idea what was wrong, but luckily there is this MSM.
I also found out that newest windows10 has the qualcomm 9008 drivers so no need to install them separately like the instructions says.

You probably used MSM with 3.2.8 or similar. Newer ones also lock the bootloader.

Pie 9.0.2 cannot lock the bootloader. Potentially a bug.
Works fine on 5.0.8; simply downgrade, lock and install Pie again

Question Cannot set lock screen code after rooting

Am I just having a bunk phone or is anyone else having this issue?
Whenever I try to set up the lock screen code on the reconfirm the code screen it freezes after I put in the code and will not proceed.

This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking

JPower123 said:
This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking
Click to expand...
Click to collapse
Like no root or anything?

cabagekiller said:
Like no root or anything?
Click to expand...
Click to collapse
Yeah, it's super weird. Just unlocking the bootloader causes this. But yeah from what I understand you should be completely unrooted and with stock boot images and or init boot images when relocking.

I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?

mvincent2k said:
I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
That is unlocked the unlock setting greys out on mine too. I got my lock screen to work as well. Super weird bug though.

mvincent2k said:
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
Only over fastootd or with msm tool (msm tool need authentication )

I just flashed the whole OS on Oneplus 11 using software called Fastboot enhance.
Actually, my op 11 was bootlooping but by using fastboot enhance software I flashed my original OS on the phone. Let everyone know, they don't need Odin or MSM for that. It's very easy and one-click process.

Same problem, was advised to lock and unlock the bootloader. I locked it and didn't realize that I had to go back to stock first and now I'm stuck in a boot loop. I can get into recovery with vol down and power, but cannot get into fastboot with vol up and power. Where do I go from here?

Sorry, I want to identify that this issue happen even I have not rooted?

PowerPC 604e said:
Sorry, I want to identify that this issue happen even I have not rooted?
Click to expand...
Click to collapse
Only when you have a convertet op11 (china ) and flash this to oos than after an oos Update you have flash back an image from coloros without this image the op 11 will bootloop
And when you have root and lock with root the bootloader than you have an bootloop