Getting rid of the unlocked bootloader warning message

[Sizzlechest]

The way to get rid of the warning caused by unlocking the bootloader on other phones would be to flash the proper bootloader logo in fastboot using:

fastboot flash logo logo.bin

This is how I did it on my old LG Nexus 5X.

Does anyone have the correct logo for the V20? Has anyone tried this on the V20?

 

[androiddiego]

It's not a logo file. It's located in aboot and you can't change it.

 

[Sizzlechest]

It's not a logo file. It's located in aboot and you can't change it.

That wasn't true on the 5X: https://forum.xda-developers.com/ne...-change-bootlogo-images-imgdata-tool-t3240052

Are you positive that it's different now?

 

[hotcell]

That wasn't true on the 5X: https://forum.xda-developers.com/ne...-change-bootlogo-images-imgdata-tool-t3240052

Are you positive that it's different now?

Here is the tool that might be useful to search for and dump the relevant partition, mount it and investigate the source of the picture and text warning:

Partitions Backup & Restore
https://play.google.com/store/apps/details?id=ma.wanam.partitions

In the best case scenario, even use reverse engineering to skip the warning and its delay altogether, anyone?
Or is aboot non-writable?

 

[runningnak3d]

You modify aboot in any way / shape / or form, and you better open a ticket with LG. When you unlock your bootloader, that stops aboot from verifying the signature of boot, laf, and recovery. XBL still very much does verification of all the other pieces of firmware. One of the first things it checks is the signature of aboot. If aboot has been modified, or wasn't signed with the same RSA cert that matches the RSA key that is in your model's QFPROM, then the phone goes into 9008 mode. At this time, there is no fixing that -- except sending it back to LG (and there may never be now that LG uses UFS nand in their phones).

-- Brian

 

[Still_living714]

I've personally looked into this and looks like it can't be changed.

 

[askermk2000]

I'm pretty sure the images is in the *raw_resources* partition. Look here.
It must be very hard to modify though considering LG use it for (all?) many models, since I've only found a single development thread for it, and as you'll see that didn't go very far.

 

[runningnak3d]

@askermk2000 You are correct. Every single boot, charging, download mode, etc image is on that partition, and it isn't signed / checked, so modify away with no risk of bricking your phone.

There is an index with offsets for each image, but the format of the images isn't immediately obvious.

-- Brian

 

[ozkaya]

@askermk2000 You are correct. Every single boot, charging, download mode, etc image is on that partition, and it isn't signed / checked, so modify away with no risk of bricking your phone.

There is an index with offsets for each image, but the format of the images isn't immediately obvious.

-- Brian

so it is indeed possible to change the unlocked bootloader warning?

 

[runningnak3d]

Security wise, there is no reason that you can't change them. It looks like LG is using RLE encoding, so finding the start and end of an image is going to be interesting. There are offsets in the index, but they don't seem to align.

Also, while I don't think having a corrupt raw_resources partition would give you a 9008 brick, you might want to have a backup ready to flash if you decide to modify it. But, (and there is always a but), since aboot loads this, if aboot pukes and doesn't load, that WILL give you a 9008 brick.

If I were you, I would buy a used V10 off of eBay, and test on that since you can recover from a 9008 with an SD card.

-- Brian