Possible to edit/replace boot logo.bin after unlocking bootloader?

Search This thread
By:
Advanced…
M

mn1968

Senior Member
Nov 7, 2011
596
161
I received my Mi A2 Lite yesterday (yay!). I have unlocked the bootloader and have rooted. I opted not to install TWRP since backups can't be restored. The only issue I have is with the unlocked bootloader...when I boot up I get the warning message that the system has been unlocked. Is it possible to edit the logo.bin with a different image so I (we) don't need to see that anymore? I am coming from a long use of several Moto phones where I could easily create a new logo.bin with a custom picture to hide the unlocked bootloader warning. I used a program called Moto Boot Logo Maker. It appears to be catered to the Moto line but may work with the Xiaomi. If anyone can provide the stock logo.bin I can try editing it. Or at least tell me how to extract the logo.bin from my phone. I tried extracting it with Terminal Emulator but it failed saying the location didn't exist. So what I need to find is the location.
Thanks!
 
M

mac12m99

Senior Member
Dec 17, 2014
192
167
inside stock rom there's a file called splash.img, that i think is the bootimage, but i'm not sure the warning can be removed, i think only the bootimage could be modified.
Also take care of what you are doing because flashing splash may brick your phone in a way that only edl mode can fix.
Let me know if you find a way :)
 
M

mn1968

Senior Member
Nov 7, 2011
596
161
I found this for the Xiaomi Mi A1. I replaced image #5 with the same Android One image that starts off the boot animation. I then resized all the images to 1080x2280 to match our device, and had to compress image #2 smaller for the program to run...but it completed without errors and gave me a splash image! I am hesitant to flash it though - the path for most devices appears to be:
/dev/block/bootdevice/by-name/splash
The path for splash image I found is:
/dev/block/platform/soc/7824900.sdhci/by-name/splash
I have included the resulting splash image for anyone brave enough to try. It is NOT flashable. It will have to be done manually through adb or Terminal Emulator.
 

Attachments

  • splash.zip
    427.9 KB · Views: 430
M

mn1968

Senior Member
Nov 7, 2011
596
161
I haven't been brave enough to flash my "new" splash.img yet. I have extracted the stock splash.img from the stock firmware download and am hoping/trying to find a way to extract/view the files/pictures on it before proceeding. I haven't had any luck using winiamge or other similar programs. Anyone have an idea to open/view the splash.img?
 
M

mn1968

Senior Member
Nov 7, 2011
596
161
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
 

Attachments

  • IMG_20181030_194350.jpg
    IMG_20181030_194350.jpg
    243.9 KB · Views: 681
N

ncar123

Senior Member
Mar 16, 2018
133
10
mn1968 said:
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
Click to expand...
Click to collapse
Lol success!?
 
M

mac12m99

Senior Member
Dec 17, 2014
192
167
mn1968 said:
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
Click to expand...
Click to collapse
I have already seen that, it happens when spash image is wrong(i think on all qualcomm devices).
 
M

mn1968

Senior Member
Nov 7, 2011
596
161
ncar123 said:
Lol success!?
Click to expand...
Click to collapse
I said "Kind of" :p

mac12m99 said:
I have already seen that, it happens when spash image is wrong(i think on all qualcomm devices).
Click to expand...
Click to collapse
Wrong how? What would be needed to make it right?
I have replaced many logo.bin on Moto phones (qualcomm variants). It is easier though with Moto though since there is tool designed specifically for editing Moto logos. The tool I used from the Mi A1 may need to be tailored for the Mi A2 Lite but that is beyond my capability.
 
M

mn1968

Senior Member
Nov 7, 2011
596
161
Does anyone know any more about how to do this? I found that when I flashed the splash.img from post #3, aside from booting with a black screen with the Linux penguin, it also messes up the image on the fastboot screen (which is nothing special as it is). That being said, fastboot still functions with ADB, just the image on the phone is messed up. I wound up reflashing the stock spash.img and am dealing with the unlocked bootloader message.
 
  • Like
Reactions: Embeeweezer
E

Embeeweezer

Member
Feb 24, 2017
44
7
mn1968 said:
Does anyone know any more about how to do this? I found that when I flashed the splash.img from post #3, aside from booting with a black screen with the Linux penguin, it also messes up the image on the fastboot screen (which is nothing special as it is). That being said, fastboot still functions with ADB, just the image on the phone is messed up. I wound up reflashing the stock spash.img and am dealing with the unlocked bootloader message.
Click to expand...
Click to collapse

Did you manage to get any further on this? I'm considering to flash your image and get the Linux pinguin, it's better than the warning screen.
 
M

mn1968

Senior Member
Nov 7, 2011
596
161
locovibe said:
I found this on Motorola One forum, it should work with A2 Lite. I didn't test it tho, I don't have unlocked bootloader.
Click to expand...
Click to collapse
I am 99.9% certain that won't work. Moto phones use a logo.bin. The Xiaomi uses a splash.img. FInding a program to edit the splash.img is the problem.

Chrono Leggionaire said:
I am using splash.img from
https://translate.googleusercontent...JrhgOvxxsyFr7imjXOCYKUEm6Y9lTRw#entry83388689[/url]

Flashed via fastboot, works on Oreo as well.
Click to expand...
Click to collapse
Your link goes to a 400 error.
 
You must log in or register to reply here.

Similar threads

robotusr
[PORT][BUILD][UNOFFICIAL] LineageOS 16 to daisy
Replies
77
Views
40K
M
misakim3i
G
device unable to boot Error - mdtp image is corrupted
Replies
22
Views
17K
M
Mumxek
W
Bluetooth & WIFI problems (slowness) after PIE update
Replies
55
Views
26K
L
luka18697
R
Double tap to wake
Replies
72
Views
61K
nikoman1987
nikoman1987
A
SIM Card Issue after downgrading from PIE 9.0
Replies
66
Views
22K
autokoise
autokoise

Top Liked Posts

24 Hours All time

New posts