Related
Here is the little bit modified version of bootanimation from system dump of Xperia Play.
This boot animation has been modified to run in loop and give better effect on DHD as I didn't like the one which came from dump...
As usual try at your on risk I am not responsible for anything....
Use root explorer to copy the bootanimation file into /system/media, or use adb to pust the file....reboot and enjoy...
Also attached is the splash screen matching to bootanimation.
Unzip the splash and copy the splash img to same folder as fastboot. connect the phone in fast boot mode and run "fastboot flash splash1 splash.img" to use the new splash screen.
Have you screens of this bootanimation
I ported my automatic boot image modifier from Linux/Ubuntu to Windows. As with the Ubuntu version, my auto-modifier redirects ROM filesystem mounts from emmc (internal memory) to SD card (external memory) in the boot image to more quickly boot a ROM hosted on SD.
Features
Simple, lightweight install. No need to separately install Cygwin and required packages.
As with the Ubuntu version, the boot image ramdisk directory is automatically modified to redirect filesystem mounts for /system, /cache and /data from emmc to SD card so you can quickly boot a ROM hosted on SD. No other changes are made, though the Perl code can be altered as necessary to further modify ramdisk.
Tested working on XP using NottachTrix 1.3.1 AT&T boot image file. For Win 7, you may need to tweak User Access Control (UAC) to launch Cygwin.
Note: The unpacker script is just a copy of “split_bootimg.pl“ found here: http://www.enck.org/tools.html (Thanks Bill.)
Instructions
1. Download cygwin-auto-modify-boot.zip (50MB) here: http://www.mediafire.com/?kz9fqzwznzizb1z
2. Unzip files to Windows c:\ . OR, if you already have a fully functioning c:\cygwin build that contains the Perl v5.14.2, cpio and gunzip binaries, you should only need to extract the directory: cygwin\home\modify-boot to c:\. In any event, you should backup your existing c:\cygwin directory prior to unzipping.
3. Copy the original boot image file (boot.img in this example) to c:\cygwin\home\modify-boot
4. Navigate to c:\cygwin and launch c:\cygwin\cygwin.bat . This opens a cygwin command window, and also generates a set of user configuration files if opened for the first time.
5. In the Cygwin command window, enter: cd ../modify-boot . Here is my directory listing after Cygwin configured my system:
6. In the Cygwin command window, enter the command: ./modify-boot.sh boot.img and press Enter at the prompts. For me, the entire process took ~30 seconds to modify a NottachTrix boot image.
If everything goes right, the system creates a “boot-repack.img” file based on the modified ramdisk and stores it in the modify-boot directory. Various log/debug data are presented on screen and stored in the modify-boot directory.
That’s all! From here you can “fastboot flash boot boot-repack.img” to boot your SD-based ROM, or store the modified image in a boot configuration directory. See http://forum.xda-developers.com/showthread.php?t=1645344
Please note: The size of my dev team has never exceeded one (me); yet I will try to field requests for help as I am able.
References and Credits
http://cygwin.com/install.html
http://www.enck.org/tools.html
http://forum.xda-developers.com/showthread.php?t=1630130
+++++
Linux/Ubuntu Version
Many have studied this excellent tutorial on how to unpack, modify and repack Android ROM boot images: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images. Its contents form a solid baseline for customizing ROM boot images and ROMs in general. Here I attempt to automate the process of modifying boot images.
Results thus far provide an efficient means of booting ROMs that are cloned to SD card (see my clone thread: http://forum.xda-developers.com/showthread.php?t=1764680 ), as shown in the example below.
modify-boot zip: http://www.mediafire.com/?luobv279pcv827k contains five files: three Perl scripts to unpack, modify and repack a boot image, the “mkbootimg” executable, and an executive batch file to run the three Perl scripts in sequence.
Boot image modifier script: modify-bootimg-atrix.pl features a useful example of how customizations can be pre-programmed by including code to redirect ROM filesystem mounts to SD card, thus enabling us to boot SD card-based ROMs --- almost on the fly.
Of course there are many references to customizing boot images, but to my knowledge this is the first published attempt to automate the process. And since there are some interesting projects related to hosting Perl on Android (see References below), I think it would be fun to develop a CWM-flashable zip (or similar tool) that loads a Perl script interpreter and then runs a pre-programmed boot image modifier --- all on phone, without computer aiding.
Preliminaries
Linux-based OS (Ubuntu 12.04 preferred --- it's still free)
Android SDK Platform Tools (includes adb and fastboot)
Perl (Ubuntu 12.04 includes Perl 5.14.2)
Example: Boot Neutrino V2.8 GT cloned to SD card
Suppose we have already cloned Neutrino V2.8 GT ROM (/system, /cache and /data) to SD card. To boot it:
1. Download modify-boot.zip: http://www.mediafire.com/?luobv279pcv827k to Desktop and extract directory: /modify-boot to ~/Desktop
2. Extract boot.img from Neutrino V2.8 GT ROM.zip and drop it in ./modify-boot
3. Open a terminal, get root and cd ~/Desktop/modify-boot
4. Enter: “sh ./modify-boot.sh boot.img” and follow prompts (Output file: boot-repack.img)
5. Boot to fastboot and connect phone to computer
6. fastboot flash boot boot-repack.img
7. fastboot reboot
Once phone is booted, we can run a sanity check by entering:
adb shell (access Android filesystems)
# mount
Results should include the highlighted device names for filesystem mounts:
Code:
[COLOR="Blue"]/dev/block/mmcblk1p2 on /system[/COLOR] type ext4 (rw,noatime,nodiratime,errors=continue,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
[COLOR="Blue"]/dev/block/mmcblk1p4 on /data[/COLOR] type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
[COLOR="Blue"]/dev/block/mmcblk1p3 on /cache[/COLOR] type ext4 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
We can now boot a cloned Neutrino V2.8 GT ROM from SD card, and/or save the modified boot image in a safe, visible location on SD card to configure dual boot (please see: http://forum.xda-developers.com/showthread.php?t=1645344 ). Or, we can roll the modified image into a flashable zip for a standalone boot push.
Standard disclaimers apply. In short, I am not responsible for any harm you or your phone may incur by using any or all of this material.
References
http://code.google.com/p/perldroid/
http://code.google.com/p/android-scripting/
http://forum.xda-developers.com/showthread.php?t=1585009
Credits
Many thanks to the Android Community Effort ( http://android-dls.com/wiki/index.php?title=Main_Page ), and to my friend and xda member ghost_og for his “mkbootimg” command-line fix that made boot image repacking work for Atrix.
Boot modifier script: modify-bootimg-atrix.pl includes logic to search both init.rc (Blur) and init.olympus.rc (CM) in ramdisk for ROM filesystem mounts.
Hi,
If you look at my Gobstopper for 2.3.6 I do exactly this kind of thing. I unpack the boot image into kernel and initramfs, modify init.rc, package it up again and flash back to boot. The binaries and source are included if you want to take a look.
Cheers!
Is it possible to modify partitions numbers? because i use different partitions because of webtop2sd and swap partition?
Adam
NFHimself said:
Hi,
If you look at my Gobstopper for 2.3.6 I do exactly this kind of thing. I unpack the boot image into kernel and initramfs, modify init.rc, package it up again and flash back to boot. The binaries and source are included if you want to take a look.
Cheers!
Click to expand...
Click to collapse
Elegant! Does it support multiple command lines? Also, does it support AT&T yet?
sendust7 said:
Elegant! Does it support multiple command lines? Also, does it support AT&T yet?
Click to expand...
Click to collapse
There is nothing Bell specific to it, static linked binaries so no rom dependence. It doesn't do anything about multiple command lines, no, the normal boot/recovery images have any at all, let alone multiple ones.
Cheers!
Is that right?
"5. Boot to fastboot and connect phone to computer
6. fastboot flash boot-repack.img
7. fastboot reboot"
Because my output is like this:
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools# ./fastboot flash boot-repack.img
unknown partition 'boot-repack.img'
error: cannot determine image filename for 'boot-repack.img'
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools#
and, of course, the boot-repack.img is in the same folder of fastboot
---
I've tried fastboot flash boot boot-repack.img. It softbricked
Reflashing the original boot.img de-bricked it without a hassle. Guess your solution is not compatible with Morrisoft CM7 ROM
GTMoraes said:
Is that right?
"5. Boot to fastboot and connect phone to computer
6. fastboot flash boot-repack.img
7. fastboot reboot"
Because my output is like this:
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools# ./fastboot flash boot-repack.img
unknown partition 'boot-repack.img'
error: cannot determine image filename for 'boot-repack.img'
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools#
and, of course, the boot-repack.img is in the same folder of fastboot
---
I've tried fastboot flash boot boot-repack.img. It softbricked
Reflashing the original boot.img de-bricked it without a hassle. Guess your solution is not compatible with Morrisoft CM7 ROM
Click to expand...
Click to collapse
Soft-brick is usually caused by one or more of the following:
1. The three ext partitions required to host ROM on SD card either do not exist, are not big enough or are corrupt.
2. The three ext partitions exist but no ROM is installed
3. ROM is not compatible with phone
4. User does not wait long enough for phone to boot after installing ROM. First boot usually takes 3 to 5 minutes as the phone is building cache. Subsequent boots should not take longer than a minute with a Class 4 or higher SD card.
And yes, the boot command should be: fastboot flash boot {boot-image}
Cheers
I ported my automatic boot image modifier from Linux/Ubuntu to Windows. As with the Ubuntu version, my auto-modifier redirects ROM filesystem mounts from emmc (internal memory) to SD card (external memory) in the boot image to more quickly boot a ROM hosted on SD.
Features
Simple, lightweight install. No need to separately install Cygwin and required packages.
As with the Ubuntu version, the boot image ramdisk directory is automatically modified to redirect filesystem mounts for /system, /cache and /data from emmc to SD card so you can quickly boot a ROM hosted on SD. No other changes are made, though the Perl code can be altered as necessary to further modify ramdisk.
Tested working on XP using NottachTrix 1.3.1 AT&T boot image file. For Win 7, you may need to tweak User Access Control (UAC) to launch Cygwin.
hi, the size from my original boot is 8 megas, after unpack and repack the size is 4.8 megas, and does not work, my boot is from motorola xt928, did you know why change the size,,thanks
Using CM10 from SD Card (Nottachtrix on internal)
For anyone looking to run Nottachtrix (or other rom) from internal memory and CM10 from external. You'll run into the same problem I did. The init.rc and init.olympus.rc files don't contain the partition information. You need to update the fstab.olympus file in the boot.img. I've attached mine for comparison. (note, after repartitioning my SD Card several times I ended up with a phantom partition (mmcblk1p4) therefore my data is actually on mmcblk1p5.
SD card partition sizes:
System: 340mb
Cache: 700mb
Data: 1.25gb
Additional notes about my partitioning experience:
The DD command in linux (and ADB) copies the entire partition exactly to the SD card's partition, therefore you lose space if you leave it this way. I used DD, but then used fsarchiver to backup all of the sd card's partitions, repartitioned the card again, and restored the partition info with fsarchiver. This made my SD card a lot cleaner and avoided wasting any space.
Everything's running great now. Thank you everyone who made dual booting possible!
Would this tool work on Desire HD?
Need some help. I pulled the boot.img created from ROM1 using copy-boot.img (until step 5 here) and when I ran modify-boot.sh on it, I got the below message:
Unpacking boot image...
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.
So, I got the boot-NottachTrix-1.3.1-att-sd-ext.img file from this thread and fastboot flashed it, thinking it is already modified, but my phone didn't boot. Then I tried running modify-boot.sh on it and then realized that it has a binary that won't run on mac.
Could someone tell me if I am on the right track with the 2nd steps above so that I can get hold of a ubuntu machine? I tried running it on a puppy linux livecd and it didn't work.
Why didn't the first step work? Is the boot.img created by the copy-boot.sh not in the right format?
Update: I forgot to mention this, but I have NottachTrix 1.3.1 installed on emmc but the size of the boot.img extracted by copy-boot.sh doesn't match that of the one attached to the above link. The one linked is size 3440640 while the one copy-boot.sh created is of size 8388608. For now, I fastboot flashed the later and got back into ROM1. I meanwhile got a livecd boot of ubuntu and ran modify-boot.sh on the one I downloaded and it created boot-repack.img successfully, but I had no success booting with it either.
irha said:
Need some help. I pulled the boot.img created from ROM1 using copy-boot.img (until step 5 here) and when I ran modify-boot.sh on it, I got the below message:
Unpacking boot image...
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.
So, I got the boot-NottachTrix-1.3.1-att-sd-ext.img file from this thread and fastboot flashed it, thinking it is already modified, but my phone didn't boot. Then I tried running modify-boot.sh on it and then realized that it has a binary that won't run on mac.
Could someone tell me if I am on the right track with the 2nd steps above so that I can get hold of a ubuntu machine? I tried running it on a puppy linux livecd and it didn't work.
Why didn't the first step work? Is the boot.img created by the copy-boot.sh not in the right format?
Update: I forgot to mention this, but I have NottachTrix 1.3.1 installed on emmc but the size of the boot.img extracted by copy-boot.sh doesn't match that of the one attached to the above link. The one linked is size 3440640 while the one copy-boot.sh created is of size 8388608. For now, I fastboot flashed the later and got back into ROM1. I meanwhile got a livecd boot of ubuntu and ran modify-boot.sh on the one I downloaded and it created boot-repack.img successfully, but I had no success booting with it either.
Click to expand...
Click to collapse
I have a newer thread: Dual Boot Atrix: Simplified and Standalone: http://forum.xda-developers.com/showthread.php?t=2124668
which presents my own custom standalone tools to do the following:
Partition SD card
Copy ROM from EMMC to SD
Flash boot image via Atrix Boot Emporium
Flash another ROM of choice to EMMC
No computer required.
On first boot, elapsed time from power-up to welcome screen can be several minutes --- especially for larger ROMs --- as the system is building cache.
Hope this helps
sendust7 said:
I have a newer thread: Dual Boot Atrix: Simplified and Standalone: http://forum.xda-developers.com/showthread.php?t=2124668
which presents my own custom standalone tools to do the following:
Partition SD card
Copy ROM from EMMC to SD
Flash boot image via Atrix Boot Emporium
Flash another ROM of choice to EMMC
No computer required.
On first boot, elapsed time from power-up to welcome screen can be several minutes --- especially for larger ROMs --- as the system is building cache.
Hope this helps
Click to expand...
Click to collapse
Thank you very much! I was able to directly go to the step 4, since I manually copied the partitions already and after verifying that I could boot into the sdcard, used the steps in the "Configuring Dual Boot" thread to get it switch between the two.
It looks like my sdcard is too slow to run android from it, so I will have to find another faster card
Note:
This is not bootanimation, this is the splash screen (the 'Coolpad' boot logo which is displayed when device is switched ON)
This is for Coolpad Cool1 Dual Snapdragon variants Only..
For other devices, please send me your splash.img so that I can create a tool for you too..
Requirements:
1. Rooted Coolpad Cool1 Dual (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: Coolpad_Cool1_Dual_Splash_Maker.zip
2. Make sure you have 4 pictures (same or different) in 1080x1920 px resolution in PNG format.
(It seems Coolpad displays any 1 picture from the 4 pictures randomly while switching ON, so I think you'll have to use 4 pictures)
3. Now rename your 4 pictures as logo1.png, logo2.png, logo3.png, logo4.png & replace it inside "pics" folder of the extracted folder.
(Similarly you can replace other pictures in it carefully if you wish)
4. 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:
1. Thanks to @Vikasspattel who provided the stock splash.img of Coolpad Cool 1 Dual ..
2. This is just a modified version of my tool here: [GUIDE] How to Change Boot Logo (Splash Screen) of LeEco Le 2 / Le S3
Hit the Thanks :good: button if it worked for you
You're welcome to share the splash images that you created
Thank You sir for reading my comment and helped by your quick effort ,
well i had no hope but thank you so much
hi
i installed custom recovery to cool 1 c 103
after it finished model number changed to 106
what i have to do?????
Note:
This is not bootanimation, this is the splash screen (the 'Huawei' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
Use this tool and instructions:
Huawei OEM_logo Changer
Note: Use a 1080x1920 pic, as .bmp file (in rgb565 format as specified in that post)
Old method:
STEPS to create boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly 1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Steps to backup your oeminfo.img:
Open Terminal Emulator, type the following command to save your stock oeminfo.img to your Internal Storage:
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo_stock.img
Now, choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_logo.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 oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo
c. To flash from Fastboot mode:
Code:
fastboot flash oeminfo oeminfo.img
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
2. @GokulNC (myself ) who wrote this script
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Doesn't work for me., same logo as before.
rebranded mine too
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
https://imgur.com/a/XAup4
just made this btw, it's already in the right format.
GokulNC said:
TESTING:
@CrimsonBloodfang
1. Can you please check if this tool is working??
2. Please check if flashing the zip from custom recovery works.
3. Please attach your 'oeminfo' partition backup. I guess it might have the logo inside it (if the above procedure doesn't work)
4. Are there different variants of P8 Lite like P8lite 2017 , etc. ?
Click to expand...
Click to collapse
1. I am able to create a new "oemlogo.mbn" and a "flashable_logo.zip" through your tool but unfortunately the stock boot logo of Huawei still shows up in every reboot, after using the two files.
2. The zip file works in TWRP Recovery and was flashed without errors but the stock boot logo still shows upon reboot then after rebooting, I checked /product/etc/logo/ and the stock oemlogo.mbn was not replaced with the new one.
3. Here is the oeminfo.img backup, by using this command in a terminal emulator
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo.img
and this one is the raw file itself. I only used two out of three methods of backing up the oeminfo partition based from this thread because I was unsure as to where in TWRP Recovery should I find the backup for oeminfo partition since it only has the options Boot, Cache, Data, System and Vendor for backup. Maybe in the "Vendor" partition, but the backup size is 394 MB.
4. I'm not sure for the variants of Huawei P8 Lite, maybe only Huawei P8 Lite (2017) and the ones on the "download section" in this link? If you meant the Huawei P8 Lite (2017) variants, the ones I know are Huawei P8 Lite (2017) PRA-LX1, PRA-LX2, PRA-LX3, PRA-LA1 and PRA-TL00. I'm using the Huawei P8 Lite (2017) PRA-LX2.
I've also tried copy pasting the new oemlogo.mbn then changed it to the correct permissions (-rw-r--r--). I even tried renaming it to "oemlogo.mbn.bak" to see if there's any change but it seems that this file is not in control of the boot logo. We also have the boot warning logo too by the way, the one that is caused by unlocking the bootloader.
Here is my own logo.bmp boot logo, 1080x1920 resolution, edited through Gimp 2 and exported as .bmp file format.
Edit: Does anyone know where is the exact location for our boot logo files? I've also found the same oemlogo.mbn file on some folders in /product/hw_oem
@CrimsonBloodfang
The oeminfo.img file had the pictures as I guessed.
I have updated the OP with the new tool. Please check if it's working
Also, I think the files in the '/product/hw_oem/whatever' directory are created from the oemlogo partition while booting (not sure though).
So maybe using the old tool, setting the permissions for oemlogo.bin as -r--r--r-- might have worked (since write access is denied).
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Thanks! I will be testing it now.
GokulNC said:
@CrimsonBloodfang
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Click to expand...
Click to collapse
Yes, it is called with different names from different countries and they are more or less, just the same devices.
In the Philippines, this phone is called the Huawei GR3 (2017).
Edit:
Maybe the users need to backup their own "oeminfo.img" first before using the tool and can you add it on OP? They might use my device's oeminfo.img if they forgot to backup and it might change their device's region settings then their stock updates would be based from my country.
I haven't rebranded my phone, just went straight to LineageOS 14.1 so I'm not sure about the consequences of flashing other oeminfo.
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
@GokulNC
It also didn't work for me. I've tested it six or more times with both the Terminal Emulator and the TWRP Recovery flash method.
Edit:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder. Then flashed the six different files of oeminfo.img and flashable_logo.zip with Terminal Emulator and TWRP Recovery, but on every reboot, the boot logo is still at stock.
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
CrimsonBloodfang said:
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
Click to expand...
Click to collapse
Nope, I don't think so..
MIcHiJK said:
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Click to expand...
Click to collapse
I'm not sure if the oeminfo partition is same across all the different firmwares.
I guess they all must be the same. If you can attach your stock 'oemlogo.img', I'll take a look at it.
CrimsonBloodfang said:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder.
Click to expand...
Click to collapse
My tool automatically converts everything to .bmp format, so it doesn't matter
Striike said:
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
Click to expand...
Click to collapse
I'm not sure about the rebranded device. Can you please attach your 'oeminfo' file?
I'll check that out.
GokulNC said:
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
Click to expand...
Click to collapse
Ok, I've flashed the flashable_logo.zip using the new tool and it seems to work. Boot logo is not anymore the stock one but instead, it's replaced by a "glitched image" with a color green background and two rectangles with colors pink and blue, not the boot logo I made. Boot warning sign is still there afterwards though.
It may be a wrong procedure on my part because I just placed my logo.bmp together with the logo1.png and logo2.png but I will continue tinkering and testing it or have a lower file sized image to see if I can finally get the desired boot logo.
---------- Post added at 11:04 PM ---------- Previous post was at 10:52 PM ----------
Also flashed my backup oeminfo.img through Terminal Emulator or TWRP Recovery and everything went back to normal.
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
CrimsonBloodfang said:
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
Click to expand...
Click to collapse
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
GokulNC said:
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
Click to expand...
Click to collapse
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (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 boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_logo.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 oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
c. To flash from Fastboot mode:
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
[email protected] (myself ) who wrote this script
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 bro
Very useful guide
CrimsonBloodfang said:
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
Click to expand...
Click to collapse
Hi, sorry for my late reply. Got stuck up with something lately.
I have attached a new tool, with little changes.
Please check if it's working.
If it doesn't, I'm not sure what else to do.
honorfan said:
Thanks bro
Very useful guide
Click to expand...
Click to collapse
Hi, did this work for you?
Thanks, I will be testing it later. I've also found out from another user that changing the boot logo using the tool, has stopped working in Nougat and Oreo.
Here is what he said, and this thread is also changing their Huawei device using the oeminfo partition.
Maybe you already know these?
@GokulNC
Tested it twice, it's still showing the glitched image.
My first attempt was replacing the logo2.png with another image as logo2.bmp. Flashed the files through TWRP Recovery, rebooted and the result is still the glitched image.
Second attempt was to not replace anything in the "pics" folder. Created the files, flashed them in TWRP Recovery, rebooted and the result is still the same.
I've been searching around xda forums for information about editing Huawei's oeminfo for its boot logo image and I noticed that their tutorials needs to follow a "specific RGB format" when editing the images to be used as a boot logo. (Bitmap file with color depth not less than 16 bit, supported color schemes: RGB555, RGB565, RGB888, RGB8888)
Although, I'm uncertain that this might be the cause of the problems and I haven't tried it yet.
- Follow any of the RGB formats to fix the problem.
I've only tried "RGB565" and "RGB888 with color depth of 24 bits".
On the other hand, seeing the "glitched image" as a boot logo, might just only be an indication of a corrupted oeminfo, when it's not properly recompiled or reconstructed?
Just to be sure, I'll place the links of the threads and posts, that I think might be useful for reference.
You might have already read these threads before.
- How To Change The Splash Screen or Boot Logo In Huawei Honor 7 at post #2
- Scroll down to Part VII - How To Change The Splash Screen
- Solution by Kostyan_nsk
- [HOW TO] Replace initial splash screen (logo) on Huawei P7
- [GUIDE] Changing boot splash image on the Huawei Y6
I will try changing the RGB formats for the image that I'll be editing, to see if it makes a difference.
Method developed by prokaryotic cell
I just extracted the bootanimation.zip from the MIUI 12 rom by Nebrassy, and right after that I edited the png image and converted it to .bmp I decided to make this splash customizable because I couldn't find this png image anywhere, and also to combine the logo.bin with the rom boot animation. Because I wanted an "original" MIUI logo.bin on my Mi A2. Sorry my bad english, I speak better portuguese hahaha.
Tutorial modified from the original tutorial of the topic: https://forum.xda-developers.com/mi-a2/themes/guide-custom-fastboot-image-splash-logo-t3885079
Prerequisites:
Mi A2 with unlocked bootloader
Windows machine with working fastboot executable
Tutorial:
1. Download MIUISPLASH.zip from this post and extract it to its own folder
2. Open cmd-here.exe
3. Put your phone in fastboot mode and run the command
Code:
fastboot flash splash newsplash.img
You may now reboot the phone and check the your new splash screen!