[TOOL] [Linux / OSX] Splash Screen creator / flasher - myTouch 3G, Magic Android Development

Hello there!
This is a G1 / Magic tool to easily convert images in splash screen ones.
This tool is based upon ffmpeg and you need it installed on your system before proceeding (it will prompt you about the program missing in any case)
REQUIREMENTS
ffmpeg installed on your system
a 320x480 image
a 320x480 device (i.e. G1 / Magic) with engineering SPL
USAGE
Code:
./file [--help][-h]
Prints out how to use the script
Code:
./file your_image_file
Converts your image into a flashable splash screen, if you want the script will continue flashing the file directly.
NOTE: if you wish to make this script work with the Nexus One or any other device which doesn't share the same 320x480 resolution, just change these two variables:
Code:
size_check=307200
size_desc="320x480"
size_check is in bytes, size_desc is just a descriptive string.
I ASSUME NO RESPONSABILITY ABOUT THE USAGE OF THIS SCRIPT. USE IT "AS IS", LOOK AT THE OUTPUTS AND YOU'LL AVOID BRICKS!
Please, if you wish to redistribute this script, give the right credits and don't change the prog_header please (maybe link this discussion in a text file)!
Here the code is, just slap it in a text file, give it the executive permission (chmod +x filename) and use it!
Code:
#!/bin/bash
prog_header() {
echo "###############################"
echo "####### EleGoS's FFMPEG #######"
echo "# G1/Sapphire/MyTouch3G/Magic #"
echo "### Splash Screen converter ###"
echo "###############################"
echo "version 1.0"
echo ""
}
if [ "$1" == "--help" ] || [ "$1" == "-h" ]; then
prog_header
echo "Usage"
echo "$0 your_image_file"
exit 0
fi
warning() {
printf "\e[0;31m$1\e[0m \n"
}
check_ok() {
printf "\e[0;32m$1\e[0m \n"
}
ffmpeg_check=$(which ffmpeg)
size_check=307200
size_desc="320x480"
if [ "$ffmpeg_check" != "" ]; then
OUTPUT=$(echo "$1" | cut -d'.' -f1).raw565
clear
prog_header
ffmpeg -i $1 -f rawvideo -pix_fmt rgb565 $OUTPUT
clear
prog_header
FILESIZE=$(cat $OUTPUT | wc -c)
if [ $FILESIZE -eq $size_check ]; then
check_ok "$OUTPUT is ready to be flashed."
else
rm $OUTPUT
warning "$OUTPUT filesize mismatches! Wrong image size ($size_desc)? Aborted."
exit 0
fi
echo "In order to flash this image you have to plug your phone in fastboot mode."
read -p "Flash it now? (y/n) "
if [ "$REPLY" == "y" ] || [ "$REPLY" == "Y" ]; then
fastboot devices | grep -q "fastboot"
if [ $? -ne 0 ]; then
warning "The USB cable is not plugged, or the device is not in fastboot mode."
echo "To flash the splash screen, manually execute this command once in fastboot mode:"
echo "fastboot flash splash1 $OUTPUT"
exit 0
else
fastboot flash splash1 $OUTPUT
fi
else
echo "To flash the splash screen, execute this command once in fastboot mode:"
echo "fastboot flash splash1 $OUTPUT"
exit 0
fi
else
warning "ffmpeg not found! Please install it before running this script!\ni.e. (DEBIAN) apt-get install ffmpeg / (OSX) sudo port install ffmpeg"
fi
Some ready-to-flash raw565 images (link on the images):

Thanks, this simplifies the process Works great on my Mac OSX SL.

Where can i download it for the Mac would love to create my own Splash Screen..

You need:
- MacPorts installed
- ffmpeg installed via macports (sudo port install ffmpeg)
- Open the terminal -> nano splash_creator
- copy / paste the code
- [CTRL]+O, then [ENTER]. [CTRL]+X
- chmod +x splash_creator
- Put the image you want as splash screen in a folder where the script is (it is actually in your home)
- Open terminal -> cd your/folder/here
- ./splash_creator your_image_here.whatever

great tools
really great tools man .. works really nice on my ubuntu ..
anyway, have any idea how to create the boot animation?

nope, I only know it's in /system/media/bootanimation.zip (at least in the latest cyanogenmod), but I haven't figured out how's supposed to be created =\

splash
Thank you guys.
The best/simple guide to change boot splash screen in 1 minute!
I've only added "sudo" to my ubuntu terminal to run it!
my own splash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks!
Wow, thanks, works like a charm.
For anyone who happens to like Jeanne d'Arc (Joan of Arc), here is my splash screen, feel free to use it:
And an associated boot animation
(I wrote my undergrad thesis about her)
Thanks again!

ok where is the link lol?

elegos said:
You need:
- MacPorts installed
- ffmpeg installed via macports (sudo port install ffmpeg)
- Open the terminal -> nano splash_creator
- copy / paste the code
- [CTRL]+O, then [ENTER]. [CTRL]+X
- chmod +x splash_creator
- Put the image you want as splash screen in a folder where the script is (it is actually in your home)
- Open terminal -> cd your/folder/here
- ./splash_creator your_image_here.whatever
Click to expand...
Click to collapse
You don't necessarily need to download macports. Just grab an ffmpeg binary from wherever (included in lots of software distributions on Mac, like the KMTTG TiVo file decoder, Handbrake, etc) and just do it from the command line.
ffmpeg -i mygraphic.jpg -f rawvideo -pix_fmt rgb565 mygraphic.raw656

elegos said:
size_check=307200
size_desc="320x480"
Click to expand...
Click to collapse
I have an EVO the size is 480x800 the size _desc= would be 480x800 what would be the size_check=
Not sure how to calc the value
thanks

@mplaines: for 480x800 it needs to be 768000
Works great for my Desire, thanks for the script!

Very nice and useful, thanks a bunch, I will definately keep the header and credits. Also you may want to add to your OP to install ffmpeg just do $ sudo apt-get install ffmpeg

The low-dough ghetto version
I have a Mac and found an interesting way to work around...
Get an image editor (I used Gimp) and create a 320 x 480 BMP of your splash image.
Flip it vertically so that it looks upside down and backwards.
Save it as a bitmap (.bmp) and select the 565 setting.
Use a hex editor to strip off the first 70 bytes of the header. That's 70 in decimal, not hex! To confirm, the resulting file size should be 307,200 bytes exactly.
Flash away!
If you are flashing a 480 x 800 image to an HDPI device, the file size will be 768,000 bytes and not a nibble more.

gee one said:
I have a Mac and found an interesting way to work around...
Get an image editor (I used Gimp) and create a 320 x 480 BMP of your splash image.
Flip it vertically so that it looks upside down and backwards.
Save it as a bitmap (.bmp) and select the 565 setting.
Use a hex editor to strip off the first 70 bytes of the header. That's 70 in decimal, not hex! To confirm, the resulting file size should be 307,200 bytes exactly.
Flash away!
If you are flashing a 480 x 800 image to an HDPI device, the file size will be 768,000 bytes and not a nibble more.
Click to expand...
Click to collapse
I didn't have to mess around in gimp and rotate things, just us the script and you'll have no problems

Repost?
I have reposted this for the G1 section, just kept the OP from here the same as there and gave you all credits. Also here are my splash screens, more to come!

I'd really like if this would work on the Nexus One too... haven't found anything about!

if i read correctly what this does. it changes the UGLY green mytouch3g logo before the boot animation? if so i'm interested.. where can i get linux copies of fastboot and Adb?

Very Nice work .. Good instructions

Related

[TOOL] [Linux / OSX] elegos Splash Screen creator / flasher

I am simply reposting this from the mytouch thread by elegos, who is the creator of this script, I take no credit for this whatsoever.
Hello there!
This is a G1 / Magic tool to easily convert images in splash screen ones.
This tool is based upon ffmpeg and you need it installed on your system before proceeding (it will prompt you about the program missing in any case)
REQUIREMENTS
ffmpeg installed on your system
Code:
$ sudo apt-get install ffmpeg
a 320x480 image
a 320x480 device (i.e. G1 / Magic) with engineering SPL (S-OFF)
USAGE
Code:
./file [--help][-h]
Prints out how to use the script
Code:
./file your_image_file
Converts your image into a flashable splash screen, if you want the script will continue flashing the file directly.
NOTE: if you wish to make this script work with the Nexus One or any other device which doesn't share the same 320x480 resolution, just change these two variables:
Code:
size_check=307200
size_desc="320x480"
size_check is in bytes, size_desc is just a descriptive string.
I ASSUME NO RESPONSABILITY ABOUT THE USAGE OF THIS SCRIPT. USE IT "AS IS", LOOK AT THE OUTPUTS AND YOU'LL AVOID BRICKS!
Please, if you wish to redistribute this script, give the right credits and don't change the prog_header please (maybe link this discussion in a text file)!
Edit: I have added a already to use script for 320x480 devices only! Or you can make your own script using elegos's code. The script should already be marked as executable, if not then make executable:
http://www.mediafire.com/?wz83iff1eg3fv38
Usage for this script:
Code:
$ ./splash_creator fileimagename.whatever
Here the code is, just slap it in a text file, give it the executive permission (chmod +x filename) and use it!
Code:
#!/bin/bash
prog_header() {
echo "###############################"
echo "####### EleGoS's FFMPEG #######"
echo "# G1/Sapphire/MyTouch3G/Magic #"
echo "### Splash Screen converter ###"
echo "###############################"
echo "version 1.0"
echo ""
}
if [ "$1" == "--help" ] || [ "$1" == "-h" ]; then
prog_header
echo "Usage"
echo "$0 your_image_file"
exit 0
fi
warning() {
printf "\e[0;31m$1\e[0m \n"
}
check_ok() {
printf "\e[0;32m$1\e[0m \n"
}
ffmpeg_check=$(which ffmpeg)
size_check=307200
size_desc="320x480"
if [ "$ffmpeg_check" != "" ]; then
OUTPUT=$(echo "$1" | cut -d'.' -f1).raw565
clear
prog_header
ffmpeg -i $1 -f rawvideo -pix_fmt rgb565 $OUTPUT
clear
prog_header
FILESIZE=$(cat $OUTPUT | wc -c)
if [ $FILESIZE -eq $size_check ]; then
check_ok "$OUTPUT is ready to be flashed."
else
rm $OUTPUT
warning "$OUTPUT filesize mismatches! Wrong image size ($size_desc)? Aborted."
exit 0
fi
echo "In order to flash this image you have to plug your phone in fastboot mode."
read -p "Flash it now? (y/n) "
if [ "$REPLY" == "y" ] || [ "$REPLY" == "Y" ]; then
fastboot devices | grep -q "fastboot"
if [ $? -ne 0 ]; then
warning "The USB cable is not plugged, or the device is not in fastboot mode."
echo "To flash the splash screen, manually execute this command once in fastboot mode:"
echo "fastboot flash splash1 $OUTPUT"
exit 0
else
fastboot flash splash1 $OUTPUT
fi
else
echo "To flash the splash screen, execute this command once in fastboot mode:"
echo "fastboot flash splash1 $OUTPUT"
exit 0
fi
else
warning "ffmpeg not found! Please install it before running this script!\ni.e. (DEBIAN) apt-get install ffmpeg / (OSX) sudo port install ffmpeg"
fi
Edit:
elegos said:
- Open the terminal -> nano splash_creator
- copy / paste the code
- [CTRL]+O, then [ENTER]. [CTRL]+X
- chmod +x splash_creator
- Put the image you want as splash screen in a folder where the script is (it is actually in your home)
- Open terminal -> cd your/folder/here
- ./splash_creator your_image_here.whatever
Click to expand...
Click to collapse
Also feel free to post your splash screens here as well
Splash screens
So here's one that mjybarr made, and one I'm using right now, both very nice splash screens
Works like a dream! Thanks for providing this tut.

[UTILITY][v1112.3]MySplash - Splash screen backup and flash program for Sensation

Hi everybody. This is my first post on this amazing forum.
I've been doing all kinds of things on my Sensation (different ROMs, cooking up stuff at the Ultimate Online Kitchen etc.), and I love doing them!
Inspired by the work of TrueBlue_Drew I decided to write my own splash screen backup / flash utlility. It's working so well that I figured I should share with you all.
So here it is. Unpack the zip to a folder of your choosing, connect your (Rooted, S-Off) device and doubleclick on mysplash.cmd. It's pretty noob proof. Just follow the instructions on screen.
Make sure your own splash image is called 'splash.png' and that its pixel dimensions are 540x960 (qHD). Put it in the 'images-here' folder before flashing.
There will also be a 'splash.png' file in this folder after a backup operation.
The batch file itself contains explanatory comments, and you are free to make your own modifications.
I hope you enjoy using this utility as much as I do!
Here's the actual code in the script file itself:
Code:
@echo off
:: *********************************************************************************************
:: * Inspired by TrueBlue_Drew's EZ Splash Screen Flasher and Image Converter *
:: * Which can be found at http://forum.xda-developers.com/showpost.php?p=11393915&postcount=1 *
:: * *
:: * Totally reworked and adapted for HTC Sensation by rainiere *
:: * Version: 1112.3 (don't forget the version parameter in the parameter section!) *
:: * *******************************************************************************************
title MySplash - Splash screen backup and flash program for HTC Sensation
color 0A
mode con: cols=57 lines=23
:: ================================================================================
:: Before doing anything, make sure there's a connection first
echo Waiting for connection...
adb wait-for-device >NUL
echo ...device is connected!
:: Wait 2 seconds with this neat trick
:: An explanation can be read here: http://groups.google.com/group/alt.msdos.batch.nt/msg/804a9fa0f5864558
ping -n 3 127.0.0.1 >NUL
:: ================================================================================
:: Parameter section. Carefull editing here!
set version=1112.3
set imagefolder=images-here
set dimensions=540x960
:: ================================================================================
:: Display the menu
:menu
cls
echo.
echo MySplash version %version%
echo.
echo [b]ackup the current splash screen
echo [f]lash a new splash screen
echo [q]uit
echo.
set action=""
set /p action="Enter a choice: "
echo.
if %action%==b goto backup
if %action%==f goto flash
if %action%==q goto quit
if %action%=="" goto menu
goto menu
:: ================================================================================
:: Backing up the splash screen
:backup
echo Transferring splash image to sdcard...
:: The splash image resides in the mmcblk0p14 partition
:: More info at http://forum.xda-developers.com/showpost.php?p=15641532&postcount=1
adb shell dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/splash.img >NUL
echo Moving splash image to image folder...
adb pull /sdcard/splash.img %imagefolder% >NUL 2>&1
:: Deleting file on the sdcard
adb shell rm /sdcard/splash.img >NUL
echo Converting splash image to png format...
ffmpeg -f rawvideo -pix_fmt rgb565 -s %dimensions% -i %imagefolder%\splash.img -f image2 -pix_fmt rgb24 %imagefolder%\splash.png >NUL 2>&1
del %imagefolder%\splash.img >NUL 2>&1
:: open the image folder for easy access
start %imagefolder%
echo.
echo Done!
ping -n 6 127.0.0.1 >NUL
goto menu
:: ================================================================================
:: Flash a new splash image to the device
:flash
if exist %imagefolder%\splash.png goto pngOK
echo There is no splash.png file in the '%imagefolder%' folder!
ping -n 3 127.0.0.1 >NUL
start %imagefolder%
goto menu
:pngOK
echo Converting png image to splash image format...
ffmpeg -y -i %imagefolder%\splash.png -f rawvideo -pix_fmt rgb565 %imagefolder%\splash.img >NUL 2>&1
del %imagefolder%\splash.png >NUL 2>&1
echo Booting into fastboot mode...
adb reboot bootloader
echo.
echo WAIT until the device is in fastboot mode!
echo ONLY when in fastboot mode, press any key to continue...
echo.
pause >NUL
echo Flashing splash image...
fastboot flash splash1 %imagefolder%\splash.img
del %imagefolder%\splash.img >NUL 2>&1
echo.
echo Done! The device will now be rebooted...
fastboot reboot >NUL 2>&1
echo Waiting for reboot to complete...
adb wait-for-device >NUL
goto menu
:: ================================================================================
:: Cleanup and exit
:quit
echo Goodbye!
adb kill-server
set action=
set dimensions=
set imagefolder=
set version=
ping -n 3 127.0.0.1 >NUL
This thing works great, easy and fast! Thanks!
Good job, but this won't work with the new HBOOT 1.20 from the latest ICS firmware packages, extended fastboot commands are not allowed.
Sick tool! works great, very easy to use. Thanks! You just got a thanks
Splash screens can be changed easily from within the phone if you dont want to use a computer or cant because your hboot locks out fastboot commands
Sent from my HTC Sensation using XDA App
why not a bash script for linux ???? plz plz plz. also new hboot 1.20 is locked thereby not supporting extended fastboot command . Any way's out to unlock it???
---------- Post added at 08:32 AM ---------- Previous post was at 08:18 AM ----------
Skipjacks said:
Splash screens can be changed easily from within the phone if you dont want to use a computer or cant because your hboot locks out fastboot commands
Sent from my HTC Sensation using XDA App
Click to expand...
Click to collapse
Is there any app? or just type this commands in terminal ? I fear to use terminal on phone due to miss typing !!
mf2112 said:
Good job, but this won't work with the new HBOOT 1.20 from the latest ICS firmware packages, extended fastboot commands are not allowed.
Click to expand...
Click to collapse
Yes, I don't think there's a way around that. A bit above my pay grade, I'm afraid ;-)
hi all
Revolutionary firmware 3.24 for sensation is out with extendEd fastboot
Command.
Hope this will work.
Sent from my HTC Sensation using Tapatalk
musarraf172 said:
Is there any app? or just type this commands in terminal ? I fear to use terminal on phone due to miss typing !!
Click to expand...
Click to collapse
You type it in once. Check it 15 times to make sure it's correct. Then save it for an automated script runner to work it's magic 1000 times in a row perfectly.
Here's a full write up on what you need and how to do it. It will work no matter what firmware you're using (personally tested in on all 3), no matter what ROM you're running, no matter what kernel you're using, what day it is, boxers or briefs, etc etc etc. If you have a rooted sensation, this will work.
http://forum.xda-developers.com/showthread.php?t=1442872
You need 1 program to convert the pictures to IMG format. It's free. There's a link in my link.
You need 1 app from the market. It's free too.
Takes 10 minutes to set up the first time. Takes 10 seconds to change your splash the second time.
Splash screen Creater
rainiere said:
Yes, I don't think there's a way around that. A bit above my pay grade, I'm afraid ;-)
Click to expand...
Click to collapse
I have rewritten the windows script into a linux one. You can run this under any 32 bit linux environment.. I have compiled the original nbimg.c v1.1 and made the nbimg linux binary...
I have tested this with my sensation S OFF HBOOT 1.27 Revolutionary..
hope this will help some one..
My new splash screen just finished uploading onto xe...
You could have warned noobs like me that you need to manually boot into bootloader though...spent an hour waiting for it to do it itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And how it looks...
Cool utility
I had been hoping to write such a bat file but failed
Sweet! It's work very well, thanks dude

[GUIDE]To Unpack/Repack livesuit flashable images

While browsing XDA i didn't find anything for unpacking Livesuite images so i created this THREAD.
Things you need
Allwiner kitchen
Stock Firmware
Linux image tool
Ubuntu 64 bit
Click to expand...
Click to collapse
Lets start
Step 1
Extracting and building the stock image (Windows)
Extract a10_flash_kitchen_v1.zip and look inside the directory, you'll see packer_gb and packer_ics. packer_ics is for Android ICS, so that is the one you will be using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open packer_ics and you will notice a bunch of directories and a couple of .bat scripts. We will spend a lot of time in these directories.
Extract the stock firmware you downloaded earlier, and copy the .img file into this directory. Rename the file to original.img.
Run the extract_image.bat script, and a command window will pop up while it is extracting.
The command window will output like the following, it will display Press any key to continue . . . when it is complete. Press a key to close the window.
Once the command window is closed, open the _extract directory and all of the extracted files will be there. The three following files are the ones we are interested in: RFSFAT16_BOOT_00000000000.fex (the boot partition), RFSFAT16_RECOVERY_0000000.fex (the recovery partition), RFSFAT16_SYSTEM_000000000.fex (the system partition, ext4 sparse).
NOTE and WARNING Some systems may also have a RFSFAT16_BOOTLOADER_00000.fex, which may also be required for your device to boot properly. There are some vague instructions @ this TechKnow forums post. I (the reader) will attempt to clarify and modify this page with the updated additional instructions for these devices to aid in making these instructions more universal for anyone using LiveSuit.
Click to expand...
Click to collapse
Step 2
Extracting, modifying and building partitions (Linux)
Copy your Extracted files to ubuntu
Rename the files as follows:
RFSFAT16_BOOT_00000000000.fex -> boot.img
RFSFAT16_RECOVERY_0000000.fex -> recovery.img
RFSFAT16_SYSTEM_000000000.fex -> system.fex
Click to expand...
Click to collapse
Copy the tools.tar.gz archive you downloaded earlier into the same directory.
To extract the tools, right click on the file and click Extract here.
This will extract the tools into a tools subdirectory.
Type terminal to show the terminal application. Hit enter and the terminal will appear.
Boot partition
Code:
$ cd "custom image"
$ tools/split_bootimg.pl boot.img
$ ls
Now extract the ramdisk file into a ramdisk subdirectory.
Code:
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../boot.img-ramdisk.gz | cpio -i
$ ls
You are now able to modify the files as needed.
Once you have finished modifying the file, we will rebuild the image. Run the following commands.
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-boot.img
$ ls
Recovery partition
his follows the same process as the boot partition. Execute the following commands to extract the image:
Code:
$ tools/split_bootimg.pl recovery.img
$ rm -rf ramdisk
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../recovery.img-ramdisk.gz | cpio -i
$ ls
rebuild the image with the following commands:
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel recovery.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-recovery.img
$ ls
System partition
The process for the system partition is different, because it is not bootable and because it is ext4 sparse, so it cannot be mounted straight away. Execute the following commands to convert and mount the image:
Code:
$ tools/simg2img system.fex system.img
$ mkdir system
$ sudo mount -o loop system.img system
$ cd system
$ ls
Once you are done, execute the following commands to rebuild the system image:
Code:
$ cd ../tools
$ sudo ./mkuserimg.sh -s ../system ../new-system.fex ext4 ../tmp 300M
$ cd ..
$ sudo umount system
$ ls
Now switch back to the file browser and you will see many new files in your directory. The three files that you are interested in are new-boot.img, new-recovery.img, new-system.fex
Copy these to your Windows drive to the directory a10_flash_kitchen_v2/packer_ics/_input
Click to expand...
Click to collapse
Step 3
Building the new image (Windows)
Once the files are copied, jump back to Windows and rename the files as following:
new-boot.img -> root.fex
new-recovery.img -> recovery.fex
new-system.fex -> system.fex
Click to expand...
Click to collapse
http://i.imgur.com/klTA5.png/img]
Now we need to make some modifications to the image config file. Navigate to the files directory and you should see image.cfg.
[img]http://i.imgur.com/Wg6Ov.png/img]
Open this file using your text editor that supports Unix line endings. Using Notepad will break this file. Locate the two lines that reference OEM and VOEM as is highlighted below.
[img]http://i.imgur.com/YxczH.png
Comment these lines by adding a semicolon ( to the start of each line. Do not make any other modifications. Save the file once you have made the change.
http://i.imgur.com/urMMN.png/img]
Go back to the packer_ics root directory and find the create_image.bat script. It will open a console while it is creating the new image.
[img]http://i.imgur.com/X2O6l.png
Once the process is complete, you will see Press any key to continue . . . and you will have a new image called output.img.
AND JUST FLASH IT AND YOU ARE DONE
Click to expand...
Click to collapse
Credits
miniandwiki
To ME
To Everyone who helped me creating this one
do i have to use 64bit liux?? i only have a 32 bit computer?? thnx
Permission denied
Hey....
I installed Ubuntu on an external disk. But even logged at su (also tried sudo su) I dont have the permission to perform with the Linux-tool. When I click at the roo-folder, it is already set to rw permission for root.
What am I doing wrong?
Links are broken, can you kindly update them.
Links are broken Pls Upload to another host

[GUIDE] Changing boot splash image on the Huawei Y6

Hello Y6 users. Y6 ONLY
Today I am sharing a script I wrote that will run on your device (or linux with some small modifications) that gave me the ability to change my boot splash image.
So far tested on the following devices:
SCL-L02
After a lot of analysis of the oeminfo partition I found 2 locations that contain the boot splash image and found that if I extracted them and then added a bitmap header plus an empty 2 byte footer I now had a usable image.
I took this information to look at replacing the raw data in oeminfo and found that fthe second location was where the image displayed on my Scl-l02 was kept.
I wanted to make the process easier than hex editing the partition so wrote the script.
Anyway enough boring stuff lets get to it.
Risk of bricking is unknown so assume high, this will modify your oeminfo partition.
You know, this horrible thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No one wants to be stuck with a logo you can't change.
Download the attached zip, inside is the script and 2 ready made bitmap files if you like one of them.
and the one I'm using
The first step to getting rid of that huawei logo is creating the image that you want to see when you turn your phone on.
I am using photoshop to achieve this however I'm sure there are other applications that can do this for you as long as they can do the following. Create an image 720 pixels wide and 1280 high in RGB 8bit mode. Can save an image in bitmap (.bmp) format with 24 bits per pixel and can flip the row order.
So create your empty picture in the same manner shown below
Now once you have edited the image you want, making sure that the resolution does not change you want to save in the manner shown below.
Now we have the code below to follow, I used sdcard/oem as my directory.
Code:
D:\adb>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting adbd as root
D:\adb>adb remount
remount succeeded
D:\adb>adb shell mkdir /sdcard/oem
D:\adb>adb push oemlogo.zip /sdcard/oem/
3504 KB/s (3756616 bytes in 1.046s)
D:\adb>adb shell
scale:/ # cd sdcard/oem
scale:/sdcard/oem # unzip oemlogo.zip
Archive: oemlogo.zip
inflating: oemlogo
inflating: 1.bmp
inflating: 2.bmp
scale:/sdcard/oem # cp ./oemlogo /system/bin/
scale:/sdcard/oem # chmod 755 /system/bin/oemlogo
scale:/sdcard/oem # oemlogo
**********************************************************
* Huawei Y6 splash logo replacement script *
* *
* written by DestructoSphere *
* https://forum.xda-developers.com/member.php?u=7009748 *
* *
**********************************************************
usage: oemlogo [-e] [-c] [-p] [file ...]
oemlogo, tool to extract and replace boot splash screen on the Huawei Y6
NOTICE: Always extract first and view created files to ensure correct binary loc
ation. Failure to do so can BRICK your device... Use with caution.
Press [enter] to confirm you understand the risks.
-d Pull diskimage from partition to oeminfo.img
-e Extract logos from oeminfo.img into current directory
-c Insert logo [file...] into oeminfo.img in the current directory
-p Push oeminfo.img in current directory to partition
Exiting.
scale:/sdcard/oem # oemlogo -d
Dumping oeminfo partition
Diskmage dump succeeded
scale:/sdcard/oem # oemlogo -e
Extracting logos from ./oeminfo.img.
logo1.bmp created
logo1.bmp and logo2.bmp created, please ensure these are both valid images and t
hat at least one of them match your current splash screen.
scale:/sdcard/oem # oemlogo -c 1.bmp
Inserting 1.bmp into ./oeminfo.img, this will take a minute.
..................
Logo inserted, please reextract to ensure process completed successfully
scale:/sdcard/oem # oemlogo -e
Extracting logos from ./oeminfo.img.
logo1.bmp created
logo1.bmp and logo2.bmp created, please ensure these are both valid images and t
hat at least one of them match your current splash screen.
scale:/sdcard/oem # oemlogo -p
Pushing oeminfo.img to /dev/block/bootdevice/by-name/oeminfo
131072+0 records in
131072+0 records out
67108864 bytes transferred in 9.602 secs (6989050 bytes/sec)
Success, reboot your device to see your new splash image.
If you are unsure you got this correct please rename ./oeminfo.img.bak to oeminf
o.img and re run this command to restore
scale:/sdcard/oem # reboot
Now when you reboot you should see your brand new boot splash.
Nice guide, but the problem is resolution of images:
Invalid image dimensions, image must be 720 pixels wide and 1280 pixels high... Exiting
BTW i used your both images
Ruven03 said:
Nice guide, but the problem is resolution of images:
Invalid image dimensions, image must be 720 pixels wide and 1280 pixels high... Exiting
BTW i used your both images
Click to expand...
Click to collapse
for me too Y6 SCL-L01 brand "tim"
Nice guide thanks
Saber5311 said:
Nice guide thanks
Click to expand...
Click to collapse
How did you made it work?
Ruven03 said:
Nice guide, but the problem is resolution of images:
Invalid image dimensions, image must be 720 pixels wide and 1280 pixels high... Exiting
BTW i used your both images
Click to expand...
Click to collapse
That's odd it might be the way they were decompressed as it works for me.
Can you try this code on each file?
Code:
file=./1.bmp
width=$(dd bs=1 skip=18 count=2 if=$file | xxd -p) 2> /dev/null
echo $width
destructosphere said:
that's odd it might be the way they were decompressed as it works for me.
Can you try this code on each file?
Code:
file=./1.bmp
width=$(dd bs=1 skip=18 count=2 if=$file | xxd -p) 2> /dev/null
echo $width
Click to expand...
Click to collapse
i use your image and seccefull but with another image not work invalid image dimensions
Ruven03 said:
How did you made it work?
Click to expand...
Click to collapse
i found the problem you must install android 6 or 7
install android 7 and try it again
Hmm i noob (new) at this, so i will wait for camera fix on android 7 so I can change it
Saber5311 said:
i found the problem you must install android 6 or 7
install android 7 and try it again
Click to expand...
Click to collapse
worked for me with android 7
nice work! :good:
I can confirm it works if u have android 7
My bad guys, I forgot to check if busybox had the "xxd" applet.
As android 7 has moved to toybox instead of busybox it works there.
I'm going to edit the script and add a toybox install option with the binary included in the zip.
Who can help me? I'm stuck inside adb shell
adb shell
scale:/ # cd sdcard/oem
scale:/sdcard/oem # unzip oemlogo.zip
Archive: oemlogo.zip
inflating: oemlogo
inflating: 1.bmp
inflating: 2.bmp
scale:/sdcard/oem # cp ./oemlogo /system/bin/
scale:/sdcard/oem # chmod 755 /system/bin/oemlogo
scale:/sdcard/oem # oemlogo
until here ok but i have a strange final string.(scale:/sdcard/oem # oemlogo7[r[999;999H[6n8scale:/ #)
it is normal that string?
DestructoSphere said:
Hello Y6 users. Y6 ONLY
Today I am sharing a script I wrote that will run on your device (or linux with some small modifications) that gave me the ability to change my boot splash image.
So far tested on the following devices:
SCL-L02
After a lot of analysis of the oeminfo partition I found 2 locations that contain the boot splash image and found that if I extracted them and then added a bitmap header plus an empty 2 byte footer I now had a usable image.
I took this information to look at replacing the raw data in oeminfo and found that fthe second location was where the image displayed on my Scl-l02 was kept.
I wanted to make the process easier than hex editing the partition so wrote the script.
Anyway enough boring stuff lets get to it.
Risk of bricking is unknown so assume high, this will modify your oeminfo partition.
You know, this horrible thing.
View attachment 4009896
No one wants to be stuck with a logo you can't change.
Download the attached zip, inside is the script and 2 ready made bitmap files if you like one of them.
View attachment 4009900
and the one I'm using
View attachment 4009901
The first step to getting rid of that huawei logo is creating the image that you want to see when you turn your phone on.
I am using photoshop to achieve this however I'm sure there are other applications that can do this for you as long as they can do the following. Create an image 720 pixels wide and 1280 high in RGB 8bit mode. Can save an image in bitmap (.bmp) format with 24 bits per pixel and can flip the row order.
So create your empty picture in the same manner shown below
View attachment 4009897
Now once you have edited the image you want, making sure that the resolution does not change you want to save in the manner shown below.
View attachment 4009898
Now we have the code below to follow, I used sdcard/oem as my directory.
Code:
D:\adb>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting adbd as root
D:\adb>adb remount
remount succeeded
D:\adb>adb shell mkdir /sdcard/oem
D:\adb>adb push oemlogo.zip /sdcard/oem/
3504 KB/s (3756616 bytes in 1.046s)
D:\adb>adb shell
scale:/ # cd sdcard/oem
scale:/sdcard/oem # unzip oemlogo.zip
Archive: oemlogo.zip
inflating: oemlogo
inflating: 1.bmp
inflating: 2.bmp
scale:/sdcard/oem # cp ./oemlogo /system/bin/
scale:/sdcard/oem # chmod 755 /system/bin/oemlogo
scale:/sdcard/oem # oemlogo
**********************************************************
* Huawei Y6 splash logo replacement script *
* *
* written by DestructoSphere *
* https://forum.xda-developers.com/member.php?u=7009748 *
* *
**********************************************************
usage: oemlogo [-e] [-c] [-p] [file ...]
oemlogo, tool to extract and replace boot splash screen on the Huawei Y6
NOTICE: Always extract first and view created files to ensure correct binary loc
ation. Failure to do so can BRICK your device... Use with caution.
Press [enter] to confirm you understand the risks.
-d Pull diskimage from partition to oeminfo.img
-e Extract logos from oeminfo.img into current directory
-c Insert logo [file...] into oeminfo.img in the current directory
-p Push oeminfo.img in current directory to partition
Exiting.
scale:/sdcard/oem # oemlogo -d
Dumping oeminfo partition
Diskmage dump succeeded
scale:/sdcard/oem # oemlogo -e
Extracting logos from ./oeminfo.img.
logo1.bmp created
logo1.bmp and logo2.bmp created, please ensure these are both valid images and t
hat at least one of them match your current splash screen.
scale:/sdcard/oem # oemlogo -c 1.bmp
Inserting 1.bmp into ./oeminfo.img, this will take a minute.
..................
Logo inserted, please reextract to ensure process completed successfully
scale:/sdcard/oem # oemlogo -e
Extracting logos from ./oeminfo.img.
logo1.bmp created
logo1.bmp and logo2.bmp created, please ensure these are both valid images and t
hat at least one of them match your current splash screen.
scale:/sdcard/oem # oemlogo -p
Pushing oeminfo.img to /dev/block/bootdevice/by-name/oeminfo
131072+0 records in
131072+0 records out
67108864 bytes transferred in 9.602 secs (6989050 bytes/sec)
Success, reboot your device to see your new splash image.
If you are unsure you got this correct please rename ./oeminfo.img.bak to oeminf
o.img and re run this command to restore
scale:/sdcard/oem # reboot
Now when you reboot you should see your brand new boot splash.
Click to expand...
Click to collapse
Hello. I apologize for my English. Can you explain how to run your script? I understand to start it is necessary to use a Terminal Emulator. I created on the SD card folder OEM, put all three of your file from the archive, launched Terminal Emulator, what next? I have the honor 4X. This script is applicable to my device?
thanks again @DestructoSphere for making a beautiful script,i was successfully create the bitmap and repacked using ur script then flash to its partition back..but can you mod these script to pull out the power off charging animation image so we can replace with another? I would like to see the animation like s7 ,there are an animation near the charger port glowing when the cable plugged in..thanks in advance
not working on Y6 ii compact (LYO-L21) :S
Do you think this will work on Huawei P10?

Help:Error Executing updates binary in zip

I don’t know what to do - appreciate some help please. another Error is:”unknown command”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You probably don't have ro.product.device set.
If you're sure that you actually do have a "viennalte".
Code:
setprop ro.product.device viennalte
If that doesn't work you can always delete the first line or so of META-INF/com/google/android/updater-script in the zip.
Renate said:
You probably don't have ro.product.device set.
If you're sure that you actually do have a "viennalte".
Code:
setprop ro.product.device viennalte
If that doesn't work you can always delete the first line or so of META-INF/com/google/android/updater-script in the zip
Click to expand...
Click to collapse
Thanx for replying. Where I put that code?
Adb command on cmd?
Yes, adb shell.
Renate said:
Yes, adb shell.
Click to expand...
Click to collapse
My pc doesn’t recognise my p905 when I’m in download mode (it dosnt exist on device manager from some reason) so couldn’t unlock bootloader ..and didn’t unlock oem either cause I couldn’t find it/::
I do rooted my device with Odin.
Do you Think delete the first line or so of META-INF - will be enough?
Just delete the line that starts with getprop("ro.product.device")...
If there is a line before/after that includes getprop("ro.build.date delete that too.
Renate said:
Just delete the line that starts with getprop("ro.product.device")...
If there is a line before/after that includes getprop("ro.build.date delete that too.
Click to expand...
Click to collapse
amazing!!! thx!!!
trying to install nikgapps - same Error. wich line to delete here?
#!/sbin/sh
# Shell Script EDIFY Replacement
#Variables
OUTFD=/proc/self/fd/$2;
ZIPFILE="$3";
addToLog() {
echo "$1" >> "/tmp/NikGapps.log"
}
contains() {
case $2 in
*"$1"*) echo true ;;
*) echo false ;;
esac
}
decrypt() {
mkdir -p "$(dirname "$2")"
addToLog "- decrypting $COMMONDIR/busybox"
addToLog " -> source $1"
addToLog " -> destination $2"
unzip -o "$COMMONDIR/busybox" "$1" -p >"$2"
chmod 755 "$2";
}
ui_print() {
until [ ! "$1" ]; do
echo "ui_print $1
ui_print" >> "$OUTFD";
addToLog "$1"
shift;
done;
}
find_zip_type() {
addToLog "- Finding zip type"
if [ "$(contains "-arm64-" "$ZIPNAME")" = "true" ]; then
I don't know what's going on there.
It's obviously trying to be invoked like an Edify script.
You'll have to explicitly state the error and quote the entire shell script.
thanx!!!
Renate said:
You'll have to explicitly state the error and quote the entire shell script.
Click to expand...
Click to collapse
Apparently??? what you quoted above as a script is in a file named "update-binary"???
They're doing something goofy by using a shell script instead of an Edify script???
Or else update in recovery can run without an update-binary???
Apparently there is some problem with fstab so it can't remount system (right after it unmounted it)?
Does this thing have a super partition?
Renate said:
Apparently??? what you quoted above as a script is in a file named "update-binary"???
They're doing something goofy by using a shell script instead of an Edify script???
Or else update in recovery can run without an update-binary???
Apparently there is some problem with fstab so it can't remount system (right after it unmounted it)?
Does this thing have a super partition?
Click to expand...
Click to collapse
Super partition? I don’t know /: how I can check?
Please post a link to this NitGapps.apk
Renate said:
Please post a link to this NitGapps.apk
Click to expand...
Click to collapse
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/01-May-2021/NikGapps-stock-arm64-11-20210501-signed.zip/download
I thought that that would expedite matters, but I don't have any interest in downloading 600 Megs.
Just post the script, identify the file name and tell me if there is only one file in META-INF/com/google/android
I think we're exceeding the bounds of my expertise/interest.
2 files: update - binary, updater - script.
Updater-script text is:
#!/sbin/sh
# Shell Script EDIFY Replacement
#Variables
OUTFD=/proc/self/fd/$2;
ZIPFILE="$3";
addToLog() {
echo "$1" >> "/tmp/NikGapps.log"
}
contains() {
case $2 in
*"$1"*) echo true ;;
*) echo false ;;
esac
}
decrypt() {
mkdir -p "$(dirname "$2")"
addToLog "- decrypting $COMMONDIR/busybox"
addToLog " -> source $1"
addToLog " -> destination $2"
unzip -o "$COMMONDIR/busybox" "$1" -p >"$2"
chmod 755 "$2";
}
I don't believe that that's the entire extent of updater-script.
You're telling me that the size of that file is ~412 bytes?
@Daniel.aru I own a P900 and not a P905 but for me it seems that this LOS Rom needs a higher TWRP version.
3.0.2 is the latest official available.
That's what it says as well in #1 of the thread you downloaded it from.
The dev even offers it's own version so why don't you follow his suggestion?
bmwdroid said:
@Daniel.aru I own a P900 and not a P905 but for me it seems that this LOS Rom needs a higher TWRP version.
3.0.2 is the latest official available.
That's what it says as well in #1 of the thread you downloaded it from.
The dev even offers it's own version so why don't you follow his suggestion?
Click to expand...
Click to collapse
the 3.0.2 version is an IMG file and odin flash just a TAR. tried to convert the file drom img to tar but the odin process failed. what can i do ?
Daniel.aru said:
the 3.0.2 version is an IMG file and odin flash just a TAR. tried to convert the file drom img to tar but the odin process failed. what can i do ?
Click to expand...
Click to collapse
The TWRP installed should be able to flash the img.
Afaik all after 2.8.7 are able to.
Gotta select that option after selecting "install" in TWRP.
bmwdroid said:
The TWRP installed should be abtle to flash the img.
Afaik all after 2.8.7 are able to.
Gotta select that option after selecting "install" in TWRP.
Click to expand...
Click to collapse
it worked i have the right version . tried to flash the rom again and got eror number 1

Categories

Resources