I have installed custom ROM (lineage os) for one-plus 9 pro android device. I have unlocked the boot-loader and changed the boot-animation image.
Now I want to lock the boot-loader again to get rid of annoying message that comes at the start. In order to lock the boot-loader , I have to flash the signed boot image .
I am struggling to find the steps required to sign the boot image.
I have tried some post but it did not work.
Appreciate if someone can help me?
Re-locking the bootloader forces to run device's Stock ROM only.
jwoegerbauer said:
Re-locking the bootloader forces to run device's Stock ROM only.
Click to expand...
Click to collapse
I just want to remove boot loder warning message screen. is it possible ?
maneeshsin said:
I just want to remove boot loder warning message screen. is it possible ?
Click to expand...
Click to collapse
It is possible by editing your logo.IMG or logo.bin file (you can backup your logo partition using any tool like partition backup and restore on playstore)
It is not possible to get rid of that message of an unlocked bootloader.
That message is part of the secure boot process and happens long before boot animation. That message is part of the bootloader itself.
When you flash a ROM you do not flash the bootloader.
The only way to get rid of that message is with a signed bootloader that doesn't display it. That does not exist. If you have an unlocked bootloader, you live with the message.
tech_head said:
It is not possible to get rid of that message of an unlocked bootloader.
That message is part of the secure boot process and happens long before boot animation. That message is part of the bootloader itself.
When you flash a ROM you do not flash the bootloader.
The only way to get rid of that message is with a signed bootloader that doesn't display it. That does not exist. If you have an unlocked bootloader, you live with the message.
Click to expand...
Click to collapse
I have an unlocked bootloader on my phone and I have edited my phones image to remove the message
areallydumbperson said:
I have an unlocked bootloader on my phone and I have edited my phones image to remove the message
Click to expand...
Click to collapse
And FYI logo partition isnt the boot animation
areallydumbperson said:
I have an unlocked bootloader on my phone and I have edited my phones image to remove the message
Click to expand...
Click to collapse
I seriously doubt this. The warning is a part of aboot itself and has nothing to do with the splash.img or logo.img you're referring to.
Ways around this in the past were done by hex editing aboot to set the delay of the warning to 0-1 seconds, that way it essentially just skips it. But that hasn't been done since OP3 series afaik.
AnierinB said:
I seriously doubt this. The warning is a part of aboot itself and has nothing to do with the splash.img or logo.img you're referring to.
Ways around this in the past were done by hex editing aboot to set the delay of the warning to 0-1 seconds, that way it essentially just skips it. But that hasn't been done since OP3 series afaik.
Click to expand...
Click to collapse
Oh my bad I was talking about Motorola phone
maneeshsin said:
I have installed custom ROM (lineage os) for one-plus 9 pro android device. I have unlocked the boot-loader and changed the boot-animation image.
Now I want to lock the boot-loader again to get rid of annoying message that comes at the start. In order to lock the boot-loader , I have to flash the signed boot image .
I am struggling to find the steps required to sign the boot image.
I have tried some post but it did not work.
Appreciate if someone can help me?
Click to expand...
Click to collapse
This guide should help you. Little complicated. But i think somewhere in the thread there is mention of it being easier now.
[GUIDE] Re-locking the bootloader on the OnePlus 8t with a self-signed build of LOS 18.1
What is this tutorial? This tutorial will: Creating an unofficial build of LineageOS 18.1 suitable for using to re-lock the bootloader on a OnePlus 8t Take you through the process of re-locking your bootloader after installing the above This...
forum.xda-developers.com
Related
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 possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
I believe you're not able to relock the bootloader until Motorola release a signed bootloader. I had the page once before I'll see if I can find it again and add an edit if I do.
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
Don't relock your bootloader unless you want a brick. Technically you can relock it, but everything has to be legit. You've already voided the warranty, relocking won't reinstate that, all that will happen is you'll be bricked with nothing to do about it because you've locked the bootloader.
Why do you want to relock it?
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
jeffritz1 said:
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
Click to expand...
Click to collapse
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Uzephi said:
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Click to expand...
Click to collapse
So, I did a "fastboot oem lock" and it re locked the bootloader. Restart bootloader, shows locked. Restart phone and still getting a splash screen similar to the one when your unlocked but this time it says "Device has loaded a different Operating System". Continues to boot normally into the system without issues. This was odd so I unlocked again did a Flashall w/ "XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and "fastboot oem lock". Both times said the lock was successful. But I'm still getting this boot splash screen with test reading "Device has loaded a different Operating System". System boots but still fails SafetyNet.
What gives? What am I missing?
From what I can muster up on XDA I can see that "you need a signed boot.img". Does this mean something and how can I find this?
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
jeffritz1 said:
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
Click to expand...
Click to collapse
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
jeffritz1 said:
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
Click to expand...
Click to collapse
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Marcowe said:
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Click to expand...
Click to collapse
Yeah, I was trying to find out if the phone could be reverted back to an out of back state. Another words, no splash screen saying "HEY! I HAVE BEEN MESSED WITH!" like you can on any other phone I have ever owned.
Thanks!
Yes you can
thomas.raines said:
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Click to expand...
Click to collapse
Yes you can , I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
EddiePR said:
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
Click to expand...
Click to collapse
If you do that OTAs will fail
Marcowe said:
If you do that OTAs will fail
Click to expand...
Click to collapse
Yes, you are rigth
So, which of the methods to re-lock did finally work? I was running on Android 8 before, OTA failes for at least 10 times, but suddenly it worked to upgrade to Android 9. Now I am weirdly not passing SafetyNet-check anymore (was working fine on Android 8, GooglePay etc).
Any recommendations? I just need the stupid GPay thing working
Boot prompt：your device software can't be checked for corruption, please lock the bootloader....
How delete or modify boot Unlock the tips ?
who knows tell me ，thanks .
I think this isn't possible. Had the same on my Nexus 6P. It it due to the bootloader not being able to verify the signature of your kernel, ROM and recovery as well as the bootloader being unlocked. Unless you go full stock with a locked bootloader, you will have to live with that message that unfortunately makes the device boot 5 seconds slower. That I tested myself
(Your warranty now is void) you can back void with reinstall stock AndroidOne and lock bootloader Code in Fastboot fastboot oem lock for unlock fastboot oem unlock
---------------------------------------------------------
now installation instructions it's easy
Enter to fastboot mode type in command
fastboot flash splash splashpixel.img
Download Link https://drive.google.com/file/d/1G3cTRjjDSnkZx2JVFQ7i5Yu9N5wQ2CUr/view?usp=drivesdk
Credits to 4PDA Developers?
Is there a way to replace the "cant check for corruption" message that appears on unlocked bootloader.
Or to hide it ?
underdoq said:
Is there a way to replace the "cant check for corruption" message that appears on unlocked bootloader.
Or to hide it ?
Click to expand...
Click to collapse
If you can get the pictures you can make your own splash.img.
https://forum.xda-developers.com/mi-a2-lite/themes/splash-image-maker-t3914702
I don't know how easy it is to extract images from a splash.img...
underdoq said:
Is there a way to replace the "cant check for corruption" message that appears on unlocked bootloader.
Or to hide it ?
Click to expand...
Click to collapse
yes
App isnt installed
using android 10 GSI
sry wrong comment
The splash.img is the "guaranty is void" or the "android one" ?
Will flashing splash.img prevent the OTAs?
Thanks
peter_baz said:
The splash.img is the "guaranty is void" or the "android one" ?
Will flashing splash.img prevent the OTAs?
Click to expand...
Click to collapse
It's more of a warning that you are doing something outside the normal.
A custom splash does not prevent OTAs.
a1291762 said:
It's more of a warning that you are doing something outside the normal.
A custom splash does not prevent OTAs.
Click to expand...
Click to collapse
I mean which image is splash referred to : the warning screen or the android one logo.
Thanks
peter_baz said:
I mean which image is splash referred to : the warning screen or the android one logo.
Click to expand...
Click to collapse
The point of the unlocked message is to allow people to easily identify unlocked phones. Service centres want this for warranty purposes. End users users want this to identify modified phones (like those reflashed redmi pro 5s people are getting).
Previous phones I've had did not allow splash flashing so you couldn't remove the message.
This phone let's me have a dark splash (and a dark bootanim) so reboots don't blind me
You possibly need to have an unlocked bootloader to flash the splash. I didn't try this until I was unlocked.
peter_baz said:
The splash.img is the "guaranty is void" or the "android one" ?
Will flashing splash.img prevent the OTAs?
Thanks
Click to expand...
Click to collapse
Splash image is the screen warning (I guess you did unlock it) and the blinding Android One screen is the bootanimation.
what partition did you use A - B?
mhuyhua said:
what partition did you use A - B?
Click to expand...
Click to collapse
You don´t have to target to any of the slots in the case of splash just flash it through fastboot using
Code:
fastboot flash splash splash.img
thanks a lot I dit it...looks nice.
(Your warranty now is void) you can back void with reinstall stock AndroidOne and lock bootloader Code in Fastboot fastboot oem lock for unlock fastboot oem unlock
---------------------------------------------------------
now installation instructions
Enter to fastboot mode type in command
fastboot flash splash splashpixel.img
Download Link https://drive.google.com/file/d/1G3cTRjjDSnkZx2JVFQ7i5Yu9N5wQ2CUr/view?usp=drivesdk
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