Hello,
I wanted to ask if there is a way to remove the unlocked bootloader message. I find this message very annoying and ugly. On my older OnePlus X there was a way to get rid of this message, so I thought that there might be a way on the OnePlus 5T.
Yes, simply re-lock the bootloader and it's gone.
dreinulldrei said:
Yes, simply re-lock the bootloader and it's gone.
Click to expand...
Click to collapse
Thats not what i want to do, i want it to be unlocked and that message gone
No way. The price to pay for benefits of root...
I don't think you can do it unless you want to risk a hard brick.
On the phones I know of if it being eliminated its not actually eliminated, its just hidden. The message is replaced with an image of something else.
Here is an example utility (Nexus 5X)
Just looks like the boot image needs unpacked, modified, repacked, and flashed?
well, you can change it by flashing splash image... see in Moto G5s plus thread there is a solution....
yourSKD said:
well, you can change it by flashing splash image... see in Moto G5s plus thread there is a solution....
Click to expand...
Click to collapse
No, it works differently in the OP5T. I don't think it's possible on our device. There's already a thread about this somewhere that explains it in more detail.
bramgus12 said:
Thats not what i want to do, i want it to be unlocked and that message gone
Click to expand...
Click to collapse
I understand that's what you want. So be a man, live with it or re-lock the bootloader. It's not like you would have to stare at that notice for hours.
yourSKD said:
well, you can change it by flashing splash image... see in Moto G5s plus thread there is a solution....
Click to expand...
Click to collapse
Yes because on the Moto this very message is a graphic in a separate partition. On the OP it's baked into the bootloader. Since this is the thing that's also signed with private keys etc., it's (as of today and someone else finds a way) impossible to change.
dreinulldrei said:
Yes because on the Moto this very message is a graphic in a separate partition. On the OP it's baked into the bootloader. Since this is the thing that's also signed with private keys etc., it's (as of today and someone else finds a way) impossible to change.
Click to expand...
Click to collapse
The Nexus 5X link I posted, they are modifying the bootloader.
So you have such tool for the OP5? Not seen before.
OhioYJ said:
The Nexus 5X link I posted, they are modifying the bootloader.
Click to expand...
Click to collapse
No they're not, not really. They're modifying dumps of the imgdata partition, which is flashed as part of the factory bootloader.img but it's not an actively run bootloader partition (like aboot, xbl, sbl, etc are), and so not verified the same on-device and can be changed without bricking the device.
See here: https://forum.xda-developers.com/on...ader-warning-boot-t3749808/page2#post76002163
Related
My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?
Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.
Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...
Good luck. Will Google not rma it?
Hey guys,
so i got my 5x a few days ago and set up root etc. A few laters i wanted to listen to music and realized that my jack is not working ( cant put my earphones all the way in, no contact).
So i wanted to send it back and get another one, Using the awesome nexus 5x toolkit i went back to stock and locked the bootloader, but now everytime it boots up i get that ugly message that my device is corrupt and i dont want to have any troubles because of it. any help? (flashed the mhc19j, it came with an older version).
Thanks!
levibuko said:
Hey guys,
so i got my 5x a few days ago and set up root etc. A few laters i wanted to listen to music and realized that my jack is not working ( cant put my earphones all the way in, no contact).
So i wanted to send it back and get another one, Using the awesome nexus 5x toolkit i went back to stock and locked the bootloader, but now everytime it boots up i get that ugly message that my device is corrupt and i dont want to have any troubles because of it. any help? (flashed the mhc19j, it came with an older version).
Thanks!
Click to expand...
Click to collapse
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Hinesight 20/20 said:
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Click to expand...
Click to collapse
so there is no official way to dismiss the warning? only replacing it with the tool?
levibuko said:
so there is no official way to dismiss the warning? only replacing it with the tool?
Click to expand...
Click to collapse
nope. That warning will appear on devices with an unlocked bootloader. The only way around it is to re-lock the bootloader or cover it up with a bootloader skin like the material design one available on this site
levibuko said:
so there is no official way to dismiss the warning? only replacing it with the tool?
Click to expand...
Click to collapse
No. In fact someone put up a bounty to get ride of it.
Hinesight 20/20 said:
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Click to expand...
Click to collapse
clcdev said:
nope. That warning will appear on devices with an unlocked bootloader. The only way around it is to re-lock the bootloader or cover it up with a bootloader skin like the material design one available on this site
Click to expand...
Click to collapse
Well. i didt lock my bootloader and it is till there.
i am not talking about ""Your device software can't be checked for corruption. Please lock the bootloader." (Orange)"
but about this one:" Your device is corrupt. It can't be trusted and may not work properly." (Red)"
levibuko said:
Well. i didt lock my bootloader and it is till there.
i am not talking about ""Your device software can't be checked for corruption. Please lock the bootloader." (Orange)"
but about this one:" Your device is corrupt. It can't be trusted and may not work properly." (Red)"
Click to expand...
Click to collapse
Ah. Sorry, I misunderstood the error you were getting. I believe that second one is due to a mismatch between the particular rom you are running and the vendor version. If you flashed back to stock using the latest stock images, I'm not sure why you are getting it as the vendor version should match (unless something else went wrong during the flash).
Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?
My plan was to unlock the bootloader before configuring the new phone - just in case I might need it later, then use the phone as out-of-box. I unlocked the bootloader for the new Moto G7 Play, following the official procedure via the Motorola Accounts page, resulting in:
- Fastboot page shows: "flashing unlocked"
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
- I could not try TWRP, as there is no TWRP for the G7 Play yet (so not sure if flashing would work)
My concerns now are that I will not be able to update the phone, and that the "bad key" issue might cause other problems.
So my plan would be to roll back and lock the phone again, to use it as out-of-box (not worrying about warranty loss that might already have happened - I did accept these terms). However, that does not work, too:
- Locking bootloader requires factory images, which are not available for the G7 Play
- Locking bootloader with fastboot OEM lock will not work without complete images
Any suggestions how bring the phone back to normal? I am disappointed by Motorola, as they officially offer the unlock procedure - which then does not produce the expected outcome, breaks updating, and provides no way to go back? Mind you, I did not apply any "hacks", nothing but the official Motorola unlocking steps.
Thanks for advice
I have the same problem and i cannot fix it.
I tried to get advice from Motorola support - but replies are very generic, referring to the bootloader unlock page (we obviously found that) or to the Motorola Forum (where the answer isn't). Will now just live with the unlocked phone and hope for the opportunity to OTA / update in a while
CoffeeMachineSwitch said:
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
Click to expand...
Click to collapse
Unlocking any Motorola bootloader will cause the bootscreen to display "Bad Key". This is normal. It is a warning that the bootloader has been unlocked and the phone may not be "safe". Once you root a Motorola phone, it will display "N/A" instead of "Bad Key". Again, this is normal behavior. There are image makers that can replace the "splash" image and "hide" the "N/A", but since this phone doesn't have TWRP yet, you'll have to live with it for now.
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
mn1968 said:
Unlocking any
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
Click to expand...
Click to collapse
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
CoffeeMachineSwitch said:
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
Click to expand...
Click to collapse
That would be an unfortunate change if true. Prior devices could be unlocked and still get OTA updates. They won't install if certain changes are made but still get notified of updates.
You still can install full ROM using fastboot commands and regain root by patching boot.img from updated ROM
I did it on both G6 and G7
Where did you get the ROM images from. I understand there are no officials?
CoffeeMachineSwitch said:
Where did you get the ROM images from. I understand there are no officials?
Click to expand...
Click to collapse
Have you tried the LMSA tool? It's a tool you download from Motorola. There is a discussion here about it. It has a rescue button with which, I understand that you can download stock images directly from Motorola, but I haven't used it myself.
umbrisle said:
Have you tried the LMSA tool? ....
Click to expand...
Click to collapse
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
CoffeeMachineSwitch said:
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
Click to expand...
Click to collapse
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Should've read the thread here before i go buy g7 play, not my phone get softbricked.
Unblocked bootloader successfully following the official doc but failed to install magisk by copying the wrong build number of boot.img of OTA from here mirrors.lolinet.com/firmware/moto
now my g7 says
Code:
failed to load kernel, no Bootable A/B slot,
Failed to book Linux
falling back to fastboot.
I downloaded `RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC` which i think this is the right build number when i see error like
Code:
river/retail corrupted
(can't remember exactly, but it's RETAIL not RETUS)
and make my own version of fastboot command stemming from servicefile.xml, still with unlucky.
there is no recovery.img and google has limited resource to make g7 play back to stock orm, i'd like to see if community has any idea or i have to give it to moto to fix it.
========================update=================================
update: i finally get the correct stock ORM which is exactly matching my build number "XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" i was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict, "second time rooting in my life".
not i has flash all of the original orm into my phone then fastboot reboot works, it give me the original error like
Android Recovery
motorola/channel_retail/channel9/PPY29.105-36/d7abeuser/release-keys
Use volum up/down and power
can't load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform a factory data
reset and erase all user data stored on this device
=====
Try again
Factory data reset
Click to expand...
Click to collapse
now i need to figure out what to do next
===============update=========
lol, turns out just press Factory data reset will bring the brick back to life!!!!!
just want to post my process for anyone having my issue.
the key point to find the correct build number
umbrisle said:
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Click to expand...
Click to collapse
.
The G6 Play is really slow, at least the Boost one. I was kind of sorry I bought one to put on Sprint's free unlimited plan. At least Sprint unlocked it for me after 60 days.
Give the G7Play some time, it just came out.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
gedster314 said:
.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
Click to expand...
Click to collapse
Yeah, but there is inconsistency in Motorolas communication, they actively offer the option to unlock the bootloader (with T&C and all) incl. a link to a rollback feature. Which then does not work. So in a scenario where a developer buys the device because it actively offers this features, they dont get what they paid for. Mind you, we are not discussing hacking a device here or jailbraking - we are discussing features that Motorola actively promotes with a dedicated webpage.
wallace_mu said:
was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict
Click to expand...
Click to collapse
You completely missed the wrong code name "river" in RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC it is for another device, while "channel" is the right one
Where did you get the correct Rom from? Thanks
I don't own Moto G7 Play and can not confirm, however this one worked for wallace_mu
wallace_mu said:
XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
realsine said:
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
Click to expand...
Click to collapse
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
CoffeeMachineSwitch said:
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
Click to expand...
Click to collapse
Hello,
I'm glad to read that I could help.
I have "my" image of 'https :// mirrors.lolinet.com/firmware/moto/channel/official/RETEU/'. There are also some others - just have a look. And please remove the spaces around '://'. I'm currently not allowed to post (external) links, so this way.
* Every 'LOCK' deletes all data and the system is "clean" again.
* The same applies (unfortunately) to EVERY 'UNLOCK'.
I don't care at the moment because I haven't set up my smartphone yet. But it's not nice.
Best regards
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Is it what happen to your device ? Hopefully you could recover ?
Steve0007 said:
Is it what happen to your device ? Hopefully you could recover ?
Click to expand...
Click to collapse
No, someone else's, we're trying to see if there's anything we can do via edl currently
craznazn said:
No, someone else's, we're trying to see if there's anything we can do via edl currently
Click to expand...
Click to collapse
Hope it's not a one way street...
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
hllywd said:
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
Click to expand...
Click to collapse
Yeah, we can get to the bootloader and EDL mode. However, we can't fastboot oem lock/unlock because OEM lock/unlock option is not togged in the System -> Dev options -> OEM Unlocking. This is a T-Mobile device, so not only that, we need to flash cust-unlock first which is not possible with OEM unlocking disabled in dev options.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
The MSM for the 2127 is actually available now via remote support, just nobody has posted it online yet. That's where this warning comes from. Another user was able to run the 2127 MSM on his phone, and now it's bricked
I thought there was a command for the oem tick switch?
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
ssjucrono said:
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
Click to expand...
Click to collapse
When did this happen? What device did you have?
craznazn said:
When did this happen? What device did you have?
Click to expand...
Click to collapse
Oneplus 9 pro green 256gb. Happened last Wednesday
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
Might be a good idea to update the thread title as it's misleading. Makes it look like the normal MSM tool is going F someone's normal variant device. Most people don't have the crappy T-Mobile variant. I understand saving a quick Buck is important though.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
Is this the Camera app from APKmirror? The one that you'd have to move to... privapp, I think? Because they failed to sign it correctly?
avid_droid said:
Don't understand when people say "save a quick buck on Tmo," when it's exactly the same $1069 right across. It's about getting it in hand instead of waiting for shipping. And the thread is not misleading as it is for the 2127 which is the Tmo variant but it doesn't say that haha
Click to expand...
Click to collapse
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
avid_droid said:
Yes. Root is needed.
Click to expand...
Click to collapse
How is it so far? Is it worth trying out?
Burt Squirtz said:
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
Click to expand...
Click to collapse
It's not misleading, because ANY device where you modify a partition that is not usually touched my the MSM tool can result in a hard brick if it's checked by avb
avid_droid said:
@craznazn , it's only if you edit partitions correct? My unlock token should be here in a few days and plan on only rooting for a couple apps. This won't affect my re-locking would it?
Click to expand...
Click to collapse
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
craznazn said:
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
Click to expand...
Click to collapse
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
drozd128 said:
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
Click to expand...
Click to collapse
Once the bl is locked due to msm, you can't flash anything again.
craznazn said:
Once the bl is locked due to msm, you can't flash anything again.
Click to expand...
Click to collapse
I see. Thank you.
Is there any tool or option to get rid of that warning message whenever you turn on your pixel 6 pro when your bootloader is unlocked and software integrity message?
nofroyo said:
Is there any tool or option to get rid of that warning message whenever you turn on your pixel 6 pro when your bootloader is unlocked and software integrity message?
Click to expand...
Click to collapse
Simple answer .. no (or at least very difficult) ... the price you pay for unlocking ;-)
foobar66 said:
Simple answer .. no (or at least very difficult) ... the price you pay for unlocking ;-)
Click to expand...
Click to collapse
+1
IIRC,the only phone mfg that I ever saw where that was possible was HTC.
I don't know if it's been done on other mfgs devices, but, none that I can recall, including Motorola/OnePlus/Huawei/Honor/Samsung & LG.
It was kinda cool to be able to do that on the HTC phones, but, as the cat & mouse game gets more involved as time marches on, I'm just happy w/Root & safety net passing.
Anything much beyond what is currently available/present is gravy.
foobar66 said:
Simple answer .. no (or at least very difficult) ... the price you pay for unlocking ;-)
Click to expand...
Click to collapse
I recall this discussion in one of the OnePlys forums 2 or 3 years ago. I actuall found back where this message was on the phone (but don't recall the details now).
But - at least on OnePlus devices - there is a check baked into the boot process which will trip over, even when you would be able to change the message. The images are signed with a key from the manufacturer and the result is somehow baked into the phone. When the phone boots, the signature is checked on the actual images and compared with the result from Google. If different, the phone will not boot. So my understanding is that without the Google key, you will never be able to remove that message.
This would require a modified abl.img (part of the bootloader), but the secure boot chain will fail if you just modify that image and you system will not boot. What would be needed is a way to modify and resign the image and all other related bootloader images to maintain the integrity of the secure boot chain.
craigacgomez said:
This would require a modified abl.img (part of the bootloader), but the secure boot chain will fail if you just modify that image and you system will not boot. What would be needed is a way to modify and resign the image and all other related bootloader images to maintain the integrity of the secure boot chain.
Click to expand...
Click to collapse
Thanks for the input much appreciated
It's pretty much here to stay on most unlocked devices.
Just close your eyes for a few seconds. ..
galaxys said:
It's pretty much here to stay on most unlocked devices.
Just close your eyes for a few seconds. ..
Click to expand...
Click to collapse
Indeed, small price you have to pay for being a naughty boy ;-)