Related
Usually, for modifying boot images, I unpack boot images (either extracted from rooted phone, or from full system image) using Android Image Kitchen, make my changes in the ramdisk directory, repack and flash (using fastboot flash boot <image_new.img>).
However, this doesn't work for Pixel or Pixel XL. I could simply create a new file in the ramdisk directory, but it doesn't reflect in the phone's root directory. I suspect this has something to do with the partitioning changes for this device, although I haven't been able to find a good complete write up about what are the exact changes. I have noticed a few new partitions (like hosd.img, bootlocker.img, hyp.img, keymaster.img, etc) but I am not entirely sure what they are for.
Any ideas how I can make some simple changes to the boot image? I want to make changes to the rc files and add a few shell scripts (for some init.rc services), and make some changes to default.prop.
Edit: I have read a bit more online, and I figured out that the boot image's ramdisk is only used in recovery, and initramfs of the system image is used as the init and the root during the normal phone boot up. So I will be able to do what I want by modifying the system image? I tried going through Chainfire's boot image too, and I am not exactly sure how he manages to modify the content of the system using the boot image.
Hi, I'm a Galaxy S7 user and I've been trying to make sparse system.img from firmware tar file into a twrp-flashable zip file but I'm not sure which is the best way.
All operations are performed on latest linux mint and I'm not going to use any kitchen. All binaries used to convert images are compiled from latest AOSP sources.
Here are some of the methods I've tried.
a) Extract everything from system.img and set metadata infos in updater-script, just like any other "rom"s. (e.g. SuperMan Rom)
Probably one of the simplest ways, and system files inside the zip can be modified easily - extract, edit, recompress.
But this method has a potential of destroying unique permissions/owner infos, such as those of symlinks.
I'd like to flash the system.img "as-is," without making a mess with whatever's inside the image.
b) Extract raw system.img directly to /dev/block/platform/155a0000.ufs/by-name/SYSTEM.
Not so bad. Raw system.img can be easily generated with simg2img. But turns out to take too much time to flash and doesn't get along well with DualBoot patcher.
c) Sparse dat, like the ones used in most AOSP-based roms
Probably the most ideal one. But when I took the following steps to make it, I found out that system partition size gets kinda damaged or something.
- Convert system.img to raw system.img with simg2img.
- Convert the raw system.img to sparse image again with ext2simg, to make img2sdat.py work properly.
- Convert the sparse image to sparse dat with xpirt's img2sdat.py.
- Finally, convert the generated sparse dat to raw system image with sdat2img.py to check if partition size matches.
Then I get the following results.
- Size of original raw system.img : 4404019200
- Size of raw system.img generated in last step : about ~100MB smaller
I know I can loop mount system.img and then make a new sparse image with make_ext4fs,
but it also breaks some permissions and make_ext4fs won't recognize file_contexts.bin from nougat firmware whereas it worked well with marshmallow's.
If anyone's got a better method or a solution for method c please leave a reply. Thanks in advance.
kykint said:
Hi, I'm a Galaxy S7 user and I've been trying to make sparse system.img from firmware tar file into a twrp-flashable zip file but I'm not sure which is the best way.
All operations are performed on latest linux mint and I'm not going to use any kitchen. All binaries used to convert images are compiled from latest AOSP sources.
Here are some of the methods I've tried.
a) Extract everything from system.img and set metadata infos in updater-script, just like any other "rom"s. (e.g. SuperMan Rom)
Probably one of the simplest ways, and system files inside the zip can be modified easily - extract, edit, recompress.
But this method has a potential of destroying unique permissions/owner infos, such as those of symlinks.
I'd like to flash the system.img "as-is," without making a mess with whatever's inside the image.
b) Extract raw system.img and directly to /dev/block/platform/155a0000.ufs/by-name/SYSTEM.
Not so bad. Raw system.img can be easily generated with simg2img. But turns out to take too much time to flash and doesn't get along well with DualBoot patcher.
c) Sparse dat, like the ones used in most AOSP-based roms
Probably the most ideal one. But when I took the following steps to make it, I found out that system partition size gets kinda damaged or something.
- Convert system.img to raw system.img with simg2img.
- Convert the raw system.img to sparse image again with ext2simg, to make img2sdat.py work properly.
- Convert the sparse image to sparse dat with xpirt's img2sdat.py.
- Finally, convert the generated sparse dat to raw system image with sdat2img.py to check if partition size matches.
Then I get the following results.
- Size of original raw system.img : 4404019200
- Size of raw system.img generated in last step : about ~100MB smaller
I know I can loop mount system.img and then make a new sparse image with make_ext4fs,
but it also breaks some permissions and make_ext4fs won't recognize file_contexts.bin from nougat firmware whereas it worked well with marshmallow's.
If anyone's got a better method or a solution for method c please leave a reply. Thanks in advance.
Click to expand...
Click to collapse
What you're doing is quite complicated if you don't use kitchen. Simplify it for yourself and use kitchen.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
What you're doing is quite complicated if you don't use kitchen. Simplify it for yourself and use kitchen.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I know that kitchens can do that for me, but they also don't flash system.img as-is.
Maybe I should just take a more look into the sparse dat method and see what breaks the partition size.
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Mi A1 Only (Snapdragon Variants)..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Mi A1 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
FOR NEW FIRMWARES FOR WHICH THIS TOOL DOESN'T WORK, TRY THIS NEW TOOL here:
https://forum.xda-developers.com/mi-a1/themes/tool-tissot-splash-maker-mod-5-pngs-t3799701/
Also, try these if that didn't work:
https://forum.xda-developers.com/showpost.php?p=76713069&postcount=42
https://forum.xda-developers.com/mi...change-boot-logo-splash-t3681033/post75978168
(I don't know if it works; an user seems to have successfully used it to create splash.img for new bootloader)
I never had the latest splash.img from the latest firmware, so I can't create a proper unless someone sends me
For older firmwares, proceed below:
STEPS to create splash.img:
1. Download & Extract this: Mi_A1_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Mi A1 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:View attachment 4073256 can be edited to something like this: View attachment 4073257
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 4
2. @OtrovX who provided the stock splash.img of Mi A1.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Was searching for this thanks.
@GokulNC
I created splash with your demo logo image... Result: Same boot logo showing when booting
I created splash with Google and iphone pngs taken from rn4 thread... Result: Same boot logo showing when booting
So not working for me
@GokulNC
Splash not working bro in ma1
it create splash image and i flash via fastboot but not working
Kindly look into it asap
ravinder0003 said:
@GokulNC
I created splash with your demo logo image... Result: Same boot logo showing when booting
I created splash with Google and iphone pngs taken from rn4 thread... Result: Same boot logo showing when booting
So not working for me
Click to expand...
Click to collapse
rameshurfrnd1 said:
@GokulNC
Splash not working bro in ma1
it create splash image and i flash via fastboot but not working
Kindly look into it asap
Click to expand...
Click to collapse
Please send your stock splash.img and logo.img
I'll check what the problem is..
GokulNC said:
Please send your stock splash.img and logo.img
I'll check what the problem is..
Click to expand...
Click to collapse
Attached splash.img of stock and logo.img not available check enclosed screenshot
Hey, @GokulNC please add options like change bootloader image, charging animations etc, and give a proper way to unpack or extract decompile splash.img file.
Will this also change the 'your device bootloader has been unlocked' thingy?
Say goodbye to white
If there's enough interest I'll make a matching boot animation (Oreo flavor)
Tested and working through flashing via twrp on latest Oreo OTA
Tested and working through flashing via twrp on latest Nougat OTA
If you find yourself stuck in a twrp bootloop - look at the slot you are in
If in A choose reboot - than select slot B - then boot to system to get out of it
any way to remove bootloader unlock warning in mi a1?
need to find out how to remove or change to black
pedrazadixon said:
any way to remove bootloader unlock warning in mi a1?
Click to expand...
Click to collapse
There's already a couple of us looking into to this but so far no luck
I've combed through system dumps even and nothing to be found
If anyone knows where this screen is located please let us know
Stoutpuppy GFX said:
There's already a couple of us looking into to this but so far no luck
I've combed through system dumps even and nothing to be found
If anyone knows where this screen is located please let us know
Click to expand...
Click to collapse
@Stoutpuppy GFX, I was reading an earlier reply of yours on this thread, did you flash the splash.img in TWRP instead of fastboot flashing it?
Any luck on anyone getting this message removed?
I tried the splash maker, didn't do anything, instead of a white background screen with the text, anytime I made a splash image and installed it, the screen was then black with the bootloader unlocked text. Has anyone unlocked their bootloader and used this Splash Maker and had it work?
fastboot erase splash works, then we get a black screen and Tux... LOL
I've always considered a Splash image what you see on a bootup, running this command removes this message, but the Fastboot image is also removed in the Mi A1.
It would be nice to not erase the splash and someone comes up with a fix for this?
Please let us know...
Thanks
DoR3M3 said:
Any luck on this?
I tried the splash maker, didn't do anything, instead of a white background screen with the text, anytime I made a splash image and installed it, the screen was then black with the bootloader unlocked text.
Removing the splash image does work, then we get a black screen and Tux... LOL
It would be nice to not erase the splash and someone comes up with a fix for this?
Please let us know...
Thanks
Click to expand...
Click to collapse
No luck so far - but I read somewhere the some pixel & nexus devices have the same problem with no solution either
I'm hoping these screens will disappear once we get an official ROM for our device - fingers crossed I hate white screens
And I just flashed the splash screen through adb commands (fastboot splash splash.img) don't use brackets
but unfortunately if you have to leave your device in an unlocked state - all it will do is change the splash screen
to black with message saying your phone can't be checked bla bla - followed by that white unlocked screen shown in previous post
Stoutpuppy GFX said:
No luck so far - but I read somewhere the some pixel & nexus devices have the same problem with no solution either
I'm hoping these screens will disappear once we get an official ROM for our device - fingers crossed I hate white screens
Click to expand...
Click to collapse
@Stoutpuppy GFX
WOW fast reply, LOL...
Please look back and read over, I edited my previous reply...
Thanks
Any news about the splash solution for the tissot? Thanks.
PS: the problem seems to be the new splash format comes with the new bootloader.. Does anybody got luck to guess the format?
Since this tool is based on redmi note 4's tool and the redmi note 4 ones already have splash maker for newer firmware in that thread, can I use that for Mi A1 too?
robby_tan said:
Since this tool is based on redmi note 4's tool and the redmi note 4 ones already have splash maker for newer firmware in that thread, can I use that for Mi A1 too?
Click to expand...
Click to collapse
The new format for RN4 is:
python bin/logo_gen.py pics/logo.png 100864
mv output.img temp/logo.img
python bin/logo_gen.py pics/fastboot.png 613888
mv output.img temp/fastboot.img
python bin/logo_gen.py pics/logo.png 101888
mv output.img temp/logo2.img
cat bin/header.img temp/logo.img temp/fastboot.img temp/logo2.img bin/destroy.img > output/splash.img
rm output\*.raw
So, I'll test it today for Tissot
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Mi A1 Only (Snapdragon Variants)..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Mi A1 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Mi_A1_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Mi A1 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:View attachment 4073256 can be edited to something like this: View attachment 4073257
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 4
2. @OtrovX who provided the stock splash.img of Mi A1.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Click to expand...
Click to collapse
thanks
novic_dev said:
The new format for RN4 is:
python bin/logo_gen.py pics/logo.png 100864
mv output.img temp/logo.img
python bin/logo_gen.py pics/fastboot.png 613888
mv output.img temp/fastboot.img
python bin/logo_gen.py pics/logo.png 101888
mv output.img temp/logo2.img
cat bin/header.img temp/logo.img temp/fastboot.img temp/logo2.img bin/destroy.img > output/splash.img
rm output\*.raw
So, I'll test it today for Tissot
Click to expand...
Click to collapse
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
---------- Post added at 01:26 PM ---------- Previous post was at 01:11 PM ----------
novic_dev said:
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
Click to expand...
Click to collapse
Just use the correct scripts I've prepared: http://anikos.su/tissot_splash_scripts_new_novicdev.zip
PS:
SPLASH - is a so-called "structured" raw image of the splash device partition.
Each bootloader parses the splash partition as a set of images created in some different media formats and sizes.
So, the new updated bootloader of Tissot is now parses the splash as a set of 4 (four) parts: "header - image - fastboot image - image 2".
novic_dev said:
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
---------- Post added at 01:26 PM ---------- Previous post was at 01:11 PM ----------
Just use the correct scripts I've prepared: http://anikos.su/tissot_splash_scripts_new_novicdev.zip
PS:
SPLASH - is a so-called "structured" raw image of the splash device partition.
Each bootloader parses the splash partition as a set of images created in some different media formats and sizes.
So, the new updated bootloader of Tissot is now parses the splash as a set of 4 (four) parts: "header - image - fastboot image - image 2".
Click to expand...
Click to collapse
what's header image? The 5 second "device can'tbe checked" warning?
Note:
This is not bootanimation, this is the splash screen (the boot logo which is displayed when device is switched ON)
This is for Razer Phone Only.. (codename: cheryl)
(For other devices, please send me your splash.img so that I can create a tool for you too..)
Requirements:
1. Rooted Razer Phone (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: Razer_Phone_Cheryl_Splash_Maker.zip
2. Make sure you have a picture with resolution 1440x2560px.
Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
3. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@game_guy who provided the stock splash.img of Razer Phone (cheryl)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Splash screen is different from boot animation. The one which appears before boot animation
Oops sorry, brain fart.
I guess I wasn't paying attention all that well.
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed
eoghan2t7 said:
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed
Click to expand...
Click to collapse
Nope, the splash screen is just a BMP picture (in RGB24 format) with an empty 16kB header before the picture.
You could see that in the batch file's code.
linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
The warning message actually is from the bootloader itself.
Most probably, it will be present in the 'aboot' partition, but it's not as easy as changing splash screen.
The same issue was also present in Nextbit Robin. (a company acquired by Razer)
Because, the bootloader is just a raw file when dumped, which needs to be checked using hex editor or whatever tool to see if it has an image and find its offset and patch the image accordingly, or even, it might be possible to find the location of where the amount of warning time is present and make it 0.
But the problem is, since it's a raw dump and the bootloader is the code that brings up the kernel, it's highly possible that if we do something wrong, the device might be hard-bricked (even fastboot mode is from bootloader). Also, today's bootloaders might even be signed, so patching the bootloader for warning picture might not necessarily work since the device won't be able to verify the integrity of bootloader partition after its contents change.
So, if there's a tool with which you can flash and recover a hard-bricked phone, and if you're willing to test the modified bootloaders that I create, send me the bootloader partition dump. I'll take a look at it
@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)
linuxct said:
@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)
Click to expand...
Click to collapse
Lol I remember doing stuff with my Droid RAZR and Bionic for dhacker back in the day. It was worth it in the end, but took time for the recover from hard brick processes to come about.
RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Hi, can you please upload and share the default bootanimation here? I have deleted mine and would like to get it back.
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
Click to expand...
Click to collapse
You are awesome , genius , superb , intelligent , brilliant , excellent , superb:good::good::good::good:
thank You Sooooooo MUCH
How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...
kqixs said:
How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...
Click to expand...
Click to collapse
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.
GokulNC said:
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.
Click to expand...
Click to collapse
The reason wasbunderstood, but i couldn't find the solution...i didn't know much about programming (to edit .bat file) i tried to search it a bit but couldn't succeed so i just used another image for boot logo....
Thnx for you help though....?
Please make a flashable Google pixel logo and boot animation for Redmi note 5 pro
Google G icon splash screen for whyred.
splash.img
raw files
Wow. Thanks its so easy.
This is the flashable zip of my splash screen.
If anyone find it useful.
Thanks for making this guide and sharing this tool, I love it!
I have an issue though, I tried making some 1080x2160/18:9 splash screens but they got vertically squished down into 1080x1920/16:9 , is this meant to happen?
As a workaround I changed my images to 1080x1920/16:9 and made the background pitch black so there wouldn't be black bars at top and bottom.
I'm a loser who loves watching Twitch livestreams, so in lack of creativity I just made these my Splash screens
KuldeepShivankar said:
This is the flashable zip of my splash screen.
If anyone find it useful.
Click to expand...
Click to collapse
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing
sharmasrb said:
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing
Click to expand...
Click to collapse
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.
Can I request this picture for splash image, as my computer is broken..
Thank you
This is a test splash screen...
KuldeepShivankar said:
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.
Click to expand...
Click to collapse
Okay, i want it
@GokulNC I tried to edit the script and make the resolution 1080*2160 because I wanted a white splash without the black bars, and then resized all 3 images to the same resolution, and then made a splash and flashed it. Worked but instead of these images it shows a complete black screen.
You know why?
Rishi2906 said:
@GokulNC I tried to edit the script and make the resolution 1080*2160 [...] Instead of these images it shows a complete black screen.
Click to expand...
Click to collapse
The routine that displays the images is very simple, and just looks for them at certain offsets within the splash partition. When you change the dimensions, file sizes change as well, and the following images are no longer at the offsets they're expected to be, so they can't be found, and nothing is displayed.
If the BMP images are exactly 6,220,854 bytes each, they can just be concatenated together; smaller ones could possibly work with some padding in between them but if you want a larger resolution, the resulting bitmaps would be too large in size.
One way to make the files small enough to fit within their spaces so that the following ones could still start at the right offsets would be to reduce color depth. (Another way would be to find the code that displays the images and edit the offsets it looks for but this isn't trivial). But in the end, the routine might still not be designed to display anything else than 24-bit, 1080x1920 px anyway.
Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip via twrp
irfan.shikarpuri said:
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Is it flash able zip via twrp
Click to expand...
Click to collapse
No.
What is the maximum logo size that I have to make? thanks before
What is the maximum logo size that I have to make? thanks before