Database Info

How I cook a ROM

My Guide to cooking requested by a few of my ROM users.
- IMPORTANT -
Make sure you have Visual C++ 2008 and M$ .Net Framework and it's Service Pack.
- NOTE TO COOK -
These Sys and Xip files are for 96 dpi devices only or commonly known as QVGA. So Please if you want to cook for your device using my guide, please make sure your device is as such.
- THE PREP _ Gathering Your Ingredients-
You can download my kitchen.
(Extract my kitchen to the C:\ directory (the root of your harddrive))
-OR-
Download the kitchen files below and create your own kitchen.
Create a directory C:\kitchens\
(Go into the C: drive and right click in an open area. Hover over 'New' and the select 'New Folder' and name it kitchens.)
Then download these kitchen files:
Link 1
Link 2
Link 3
Link 4
Link 5
Link 6
Link 7
(These links were brought to you by JustKitchen.info)
These links are archived with 7-zip.
When you have all these files downloaded, and you have 7-zip installed, Select all of the files you've downloaded. Then right click on one of the highlighted files and hover over 7zip in your dropdown menu and then click on 'Extract Here.'
{
"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"
}
This will create a directory that looks similar to this:
As you also see in that picture (The 'Working_Folder' archive) you'll need my Sys & Xip files. And as you know me, I will always try to keep this folder updated so that when a new build comes out you guys can cook with it too, Which you guys can find HERE or any of my ROM threads. Right now I have all the newest builds. So you guys are set
_If you downloaded my kitchen instead, then it will have come with build 23545 & build 23563 only (Which are Windows Mobile 6.5.5 - the latest Windows Mobile Builds)._
After you download my Working_Folder.7z then just extract the files as shown (Just right click on the file and hover over 7zip and you can click on 'Extract Here.'
And yes, lol, my computer is names Muff - PC because me and my wife's pet names are Muffin, lol.
Now, click 'Yes' when it prompts you asking if you want to Merge the folders and then also click 'Yes' to Overwrite the files there if necessary.
Once you have the kitchen setup the way you want it, (you'll also notice the PagePool Changer I have in there) then go up one level in the folder to where you see Working_Folder and send a shortcut to the desktop as you see below:
Here is where you'll need to make changes to your files (Because my files have my background image and watermarks and all of my GUI changes..etc..).
Navigate to C:\kitchens\SuperJustKitchen\Working_Folder\SYS\23563\dpi_96\COMMON\Base_DPI_96
You can download this Base_DPI_96 folder here if you want the original files..
Just drag and drop over the Base_DPI_96 folder in the C:\kitchens\SuperJustKitchen\Working_Folder\SYS\23563\dpi_96\COMMON directory.
After you're all set in making your GUI changes then navigate to
C:\kitchens\SuperJustKitchen1\Working_Folder\EXT\SHARED\THEMES_QVGA
This is where you are going to change your background images. The most important part about making these images is the fact you need to keep them perfectly proportioned to your device. If you have a qvga, like my Wing/Herald, then its going to be 240 x 320 (portrait) and 320 x 240 (landscape).
When you're done making your images make sure to rename them respectively.
Now navigate to C:\kitchens\SuperJustKitchen1\Working_Folder\EXT\SHARED\Control Panel\HTCAnimation_1_3_5_0\files
This is where you'll change the splash screens. And Please do ^>^ because we each should have our own unique style of cooking, lol.
Just find an animated .gif image - Also 320 (tall) x 240 (width) - and just rename it Animation2.gif
Then Find a still image of whatever you'd like and rename it welcomehead.96.png
Just take mine out and dispose of them..
- End of Prep -
Part two below.​

- PART TWO _ More Prep -
Okay. First thing is navigate to your Working_Folder, which should be on your desktop continuing from the last post. Open the ErviusKitchen.exe
Let it load, then click on the drop down menu in the picture and land it on Herald. It will go crazy for a second, but, that is normal.
Next, click on the dropdown menu for the XIP and SYS and land them on the build you're using. I am using, the included, 28223 build.
Next, you're going to add your ROM version number. In the picture is how I normally label mine.
Should look like this:
Using LZX Compression is useful when you notice your ROM is too big. The Max size a ROM can be is about 80MB or so. If you plan on not flashing by SDCard then the minimum size of the ROM should be 50.1MB. When you are ready to cook, you'll see the size in bytes. So, in bytes, 50.1MB is 52,567,531
- - -
Next, click on Show Editor.
This will bring up all the .rgu files that are located in the kitchen. Scroll down to where you see the .rgu file located in the Shell.
Double click on it and it will open up the editor. Locate line 419. This is where you can 'brand' your ROM. All my ROMs I create usually have the branding '- Trib.' Put anything you want after the '- ' (and you also have to leave space right after the '- '). Then make sure to save. Then close out of the editor. Then go back to the main kitchen window.
- - -
Next, click on Extra Buttons.
This will bring up a menu with large buttons. Click on the CABtoEXT button.
That will bring up a command prompt window as shown:
Minimize all the other windows. Then hit the Enter key. This will open up a large window.
Then navigate to any of the cab files that you might want that are not listed in the kitchen. Select and Right-Click on the cab files that you want then click on Copy.
Then Right-Click and Paste the cab files into the window that popped up.
When all the cab files have been placed go back to the other command prompt window and then press Enter where you see Press any key to continue . . .(and make sure to only put up to four at a time.. for some reason it doesn't work right).
A prompt will follow asking if it will be used for 96dpi devices. Make sure you select the respective digit for 96dpi then hit enter. Another message will prompt you to select what devices can use the programs. Make sure to select All devices.
Your cabs you import into the kitchen will be located in the 0096 Category in the list
- - -
Now head back to the kitchen's main window. Next we are going to Save the ROM so far. Make sure you save with a version number (sometimes if I save before I put a version number I'll forget to put one all together. Basically a ROM won't flash without one.
Now Close out of the kitchen all together then re-open it. Reason being is because the cab files you've just installed won't show up until you do. Then Load your previously saved ROM.
Now it's time to make your selections of what is going to go into your ROM. Double click on each file/module to toggle the enabling/disabling of packages.
These are my selections:
Once you've made your selections make sure to save once more.
- End of Part Two_ More Prep-
Cheers,
Trib
​

- PART THREE _ Cooking -
Now you are ready to cook. Press the Create ROM button.​
You will see more craziness:
This process can take up to an hour depending on how many cores your computer has - it's a logical based kitchen ^>^
Once the process is complete, navigate to C:\kitchens\SuperJustKitchen\Working_Folder\RELEASE_HERALD and click on the ROM Update Utility. Or you can use the PagePool Changer to change the pagepool to something other than the default, which is 6MB. Changing it to 3MB will give you about 5MB more Ram. But it also has a trade-off of slowing your ROM down a bit.
Put your device into the bootloader by soft-reseting it (by pressing in, with your stylus, the little hole on the left side of your device) and also holding down the camera button. You will then be in a, what we call a tri-colored, screen.
Then check off the check box and press next. Do this again. Then it will pause. Then the utility will pop up again and click on next twice and then UPDATE.
Once you flash the ROM to your device, upload it with RGhost.Net
Then post the link in this thread. I would like nothing more than to see the fruits of yours and my own labour.
Cheers,
Trib.
-End Part Three _ Cooking -
​

An excellent and to the point start!
Let me be the first to congratulate you! This tutorial is going to help people like me tremendously!

Hm. i just realized I forgot to mention that these Sys and Xip files are for 96 dpi devices only or commonly known as QVGA. So Please if you want to cook for your device using my guide, please make sure your device is as such.

Long time viewer, first time poster.
I am also looking very forward to this tutorial. I've been messing around in the "kitchen", just getting the feel of it.
Looking forward to a better understanding.
Thanx for all the hard work.

Thank you for this!! I will try to.

Your welcome. I can't wait to see what your ROMs will be like.

WOW! Nice tutorial!!
If I mess it up now, it could only be due to my own un-geekness.
Just one question: Would it be too much trouble to outline just the files needed to create a "bare-bones" rom; i.e. a rom that will work (duh), but have as little "fluff" as possible?
Excellent work!! Donation is on the way!

Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.

nothing
not appear
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]...
img: http://cwmobile.webcindario.com/nothing.PNG
what is the error?
thanks in advance..

Hm. Didn't realize that it wasn't in there. You can manually enter it in there. But I'll include it for you... Just redownload

Tribulattifather said:
Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.
Click to expand...
Click to collapse
Ah, OK, excellent.
Please pardon my noobness.
I'm at work right now. I'll hit that PayPal button when I get home (I don't want to be typing logins/passwords on this PC, for obvious reasons).
It can't be said often enough: Thank you for your work.

I surrender, thanks for try help me...

Don't surrender, lol. I'm uploading the files you'll need right now.
I'll post back here when its uploaded.
UPDATE: Added the correct files to the SYS folder; you will now be able to 'brand' your ROM now.

Tribulattifather said:
Thank you for your kindness.
And that is exactly what I did - If you select the selections i've made you'll come out with a barebones system with all the necessary files.
Click to expand...
Click to collapse
i have to disagree with you there. You have included many unneeded things for the average user.
To name a few unneeded:
ADC, Adobeflash/codecs, DRM, Entertanment, ipsecvpn, SQLCEMobile, Transcriber, Voicecommand, HTC animation, SIM_Tkit, Net CF.
Just my 2 cents
Granted your roms are more geared towards everyone. Many know mine were not

Oh yeah, I know what you mean. I only meant that this was a barebones ROM that I would make. I guess one could construe that I meant barebones for an average user. My apologies :1
But best thing one can do is cook , cook , cook and cook some more until you get the ROM you want, lol.

thanks, but if I yield to truth, and you can not download the files because they are heavy and my internet is 256 and download speed is + / - 30 kbs.
thanks... thanks... and thanks...

What build would you like me to upload separately for you? I think you said you needed 28223.
This file is only 30MB and contains only 28223 with the updated Shell folder:
http://rghost.net/download/980604/6a9cbd59a9d861179da20ac3f06349b222d8cfda/Working_Folder.7z

Cellomancer said:
Ah, OK, excellent.
Please pardon my noobness.
I'm at work right now. I'll hit that PayPal button when I get home (I don't want to be typing logins/passwords on this PC, for obvious reasons).
It can't be said often enough: Thank you for your work.
Click to expand...
Click to collapse
Thank you so much Cell for your kindness. I will prioritize your needs if you do need anything.

[WINDOWS] {05/22} WET_ANDY * a UNIVERSAL splash screen converter and flashing tool

Meet Wet Andy, a UNIVERSAL splash screen tool.
{
"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"
}
Yes, you heard right, this is a tool that can take any standard image (jpg, png, bmp), convert it to the exact screen size of your device, and flash it to your device.
Custom splash screens have never been easier! It will work with API7 through API15 without issue (on the 8 different devices I tested). This is a self-contained package, no installers, and can be used from a flash drive with no additional downloads required. All the tools are right there!
STEPS:
1. Connect your Device and enable USB Debugging. Start the "Wet Andy" program by clicking it.
2. Hit the "TEST ADB" button, it will tell you if your device is connected. (output can be seen as ADBTEST.txt in the folder)
3. Hit "PICK" and you must pick an image file that is JPG, BMP, or PNG using the file chooser.
4. Hit "CONVERT", you will not see the progress on screen, but when you see your image, display.txt, and splash.img in the program folder it has worked!
* This program auto converts the image to the size of your screen, so you can use any image. If your phone does not display its screen size in the props, the default is 480x800
5. Close the program. (ffmpeg has something weord where it keeps going, but don't worry as it WORKED.
6. Restart the program and "TEST ADB"
7. Once you see it is connected, hit "Install"
* The phone will freeze, then reboot into the bootloader. From there, it will do the install.
* Once you see the screen go blank and the program show "Installing", it has installed and is rebooting
* You will see the new image as it boots!
TO REUSE AND FLASH ANOTHER IMAGE TO THE SPLASH, DELETE THE SPLASH.IMG !!!!
DOWNLOAD: http://dl.dropbox.com/u/58849669/WetAndy.windows.zip
Say THANKS and/or DONATE if you like the program!!!
NOTICE: BY USING THIS PROGRAM, YOU AGREE TO THE RIGHTS AND PRIVILAGES OF GOOGLE AND THEIR SDK TOOLS

Good
Sent from my GT-I9100 using xda premium

Very cool. Thanks
**EDIT** Works fantastic on my evo 3D. thanks again.

^^OP
This works for all phones?
My boot.img contains logo in form of rle
That is initlogo.rle
Then?
What if I want splash screen in form of initlogo.rle?

This is not your boot.img, this is the system splash which is before your kernel and such. Messing with your Boot.img is a different matter.
Works on all devices that use the splash standard set forth by Android.
This is not a boot animation. This is just an image at startup.
Requires Root, shell, and fastboot access. SGS2 users need to be running AOSP packages that use the base system standards.

What?
I have Micromax A70 and we have first boot logo inside the kernel i.e zimage and second bootlogo is from boot.img which is initlogo.rel
We dont have any splash partition to flash splash.img via fastboot
So this is not for our device?

This is unfortunately, not going to rip your boot image, replace the image and zip it all up again. Kernel code requires that you compile your own after doing the conversion.
I can make a converter and compiler for kernel code that puts your image in there with links to the source code.
They basically made those areas blank and put no beginning splash. What you are seeing with the kernel start and boot start is not a splash image. Your images are built into your running code, so not your boot splash.
Running as the zImage and uImage pieces is not true native Android code and does not really adhere to the base code standard. They basically put a micro layer between the OS and the hardcoded chip firmware. They run it as a standard OS.

Great tool, do you know if this works on the Toro Galaxy Nexus?

Just try it. There is literally no harm that can come from this program. If you have no splash ability on your devices, well can't help you there just yet.
Its just using fastboot to flash the splash image. The fancier bits are in the device recognition with display specs and file conversion.
For the SGS2 users and those whose boot images are in the kernel, I can make a image converter that automatically compiles the kernel, then pushes it and flashes the new kernel. I can also add some fuctionality for rle image conversion for some of the more odd implementations.
Tell me if you want it. I can do it. Not that hard.

How long does it take for a file to be converted? It has said file loaded for a while and seems to stay there?
Ok never mind I restarted it duh LOL and it seemed to install but the splash screen is the same, will try again

Open the folder that contains the program. When it is finished, you will see a new file called splash.img. Then, close wet Andy, and restart it. And select install. Bada bing Bada boom...

You got it Bill!
Hopefully this takes the guess work out.
Its really a GREAT way to insure your device has another layer of safety because you can make an image that has your name and personal contact information that the person who finds it can you to get a hold of you. Also, regardless of if someone manages to boot into recovery mode and completely wipe your data or flash a new image, they CAN'T wipe this. That is unless they are a very diligent thief and find this tool!

Thats just the thing how long do you have to wait for the file to convert? I left my device connected for roughly 30 mins and all I saw was a text file created, no splash.img??
billbowers said:
Open the folder that contains the program. When it is finished, you will see a new file called splash.img. Then, close wet Andy, and restart it. And select install. Bada bing Bada boom...
Click to expand...
Click to collapse

Strange.. Mine took about 10 seconds...max

You have to PICK a file for it to convert. You must pick, then convert. It only works on PNG, JPG, and BMP file formats for the pictures. PICK loads the file into the program and then hit CONVERT. I would double check that your device is connected. If you are also only seeing display.txt and NOT the splash.img or a copy of the picture you are converting and flashing, you did not hit the PICK option first. That or your internal windows tools are super-broke.
Also check that ffmpeg isnt running rampant on your processes.
There just isn't a good reason why its worked for everyone else and your computer is having issues, unless something is wrong.
Please outline exactly what you are doing and seeing.
camblue said:
Thats just the thing how long do you have to wait for the file to convert? I left my device connected for roughly 30 mins and all I saw was a text file created, no splash.img??
Click to expand...
Click to collapse

Ok I connect my device to my computer and just to be sure I check my ADB connection by running a command prompt and typing adb devices and my devices shows up. Then I back out of that and go into the wet andy program and test the ADB connection and it says device connected! Then I pick a picture of my car (dont judge me its a corvette LOL) it is a jpg file and it says file loaded! Then I hit convert and it just sits there and does nothing? I have tried several other pics and nothing happens after I hit convert?
Childofthehorn said:
You have to PICK a file for it to convert. You must pick, then convert. It only works on PNG, JPG, and BMP file formats for the pictures. PICK loads the file into the program and then hit CONVERT. I would double check that your device is connected. If you are also only seeing display.txt and NOT the splash.img or a copy of the picture you are converting and flashing, you did not hit the PICK option first. That or your internal windows tools are super-broke.
Also check that ffmpeg isnt running rampant on your processes.
There just isn't a good reason why its worked for everyone else and your computer is having issues, unless something is wrong.
Please outline exactly what you are doing and seeing.
Click to expand...
Click to collapse

camblue said:
Ok I connect my device to my computer and just to be sure I check my ADB connection by running a command prompt and typing adb devices and my devices shows up. Then I back out of that and go into the wet andy program and test the ADB connection and it says device connected! Then I pick a picture of my car (dont judge me its a corvette LOL) it is a jpg file and it says file loaded! Then I hit convert and it just sits there and does nothing? I have tried several other pics and nothing happens after I hit convert?
Click to expand...
Click to collapse
After that, you should see your img file in the folder for the program.
Close Wet Andy, restart it, check your adb connection, and Then run INSTALL.
It will install and reboot your device!

[APP][LOGO] Moto X/G/E boot logo command line tool

Here is a small command line tool to manage boot logo on motorola phones with unlocked bootloader on Jelly Bean, Kitkat and Lollipop.
With this tool you can mainly create your own custom boot logo and/or remove warning message.
You can also list, extract, replace, remove image from a boot logo file or create a new one from scratch.
The tool can accept a large variety of image format, but prefer using a non-destructive format like BMP or PNG.
Images are exported as PNG.
Code:
[B]Usage:[/B]
mlogo <logo_filename> command [arguments]
[B]Commands:[/B]
mlogo <logo_filename> list
list logo contents
mlogo <logo_filename> extractall
extract logo contents
mlogo <logo_filename> create
create a new empty logo
mlogo <logo_filename> append <name> <image_filename>
append image to an existing logo
mlogo <logo_filename> replace <name> <image_filename>
replace image in an existing logo
mlogo <logo_filename> remove <name>
remove image in an existing logo
mlogo <logo_filename> extract <name>
extract image from an existing logo
Create a custom logo on Kitkat/Lollipop (android 4.4.x/android 5.x):
Your image can have any size less or equal to your phone's native which is:
Moto X 2014: 1080x1920
Moto X 2013: 720x1280
Moto G (2013/2014): 720x1280
Moto E: 540x960
If your image resolution is less than phone's native:
Changes are done by the phone not by this tool
- it will be centered vertically and horizontally
- the background color not covered by your image will be the same as the top-left pixel of your image.
List the content of your current logo:
mlogo logo.bin list
Replace the image you want to change with yours:
Start logo on unlocked bootloader:
mlogo logo.bin replace logo_unlocked mylogo.png
Empty battery logo:
mlogo logo.bin replace logo_battery mylogo.png
Low power logo (moto E):
mlogo logo.bin replace logo_lowpower mylogo.png
Unplug logo (moto E):
mlogo logo.bin replace logo_unplug mylogo.png
Create a custom logo on Jelly Bean (android less than 4.4):
Same as above but your image must have a size of 540x540
Use 'mlogo (old format)'
Thanks to:
Carock, for explanations on boot logo RLE image encoding.
Changes:
- v1.01 change errorlevels behavior,
return errorlevel 0 on succes and errorlevel 1 on error.
- v1.02 correct an error when there is no padding,
bug found by caitsith2 in this post.
Downloads:
Kitkat/Lollipop (Windows)
Windows version for new logo format (android 4.4.x/android 5.x)
mlogo v1.02.zip SHA-1:
6C63079E15993915A778B53259FD960D09A33687
Kitkat/Lollipop (Linux)
Linux version for new logo format (android 4.4.x/android 5.x)
mlogo-linux v1.02.tar.gz SHA-1:
91A2773F16E47691A171F4A84E741C0E3C471725
Jelly Bean (Windows)
Windows version for old logo format (android less than 4.4)
mlogo (old format) v1.02.zip SHA-1:
7BA3689CE35FCD1CE27E6690703D05A599473962
Jelly Bean (Linux)
Linux version for old logo format (android less than 4.4)
mlogo-linux (old format) v1.02.tar.gz SHA-1:
8F2A520C0C4733F20B8D2A78BA6B9229AF2CC5E0

This tool appears to be dealing only with Logo.bin... and not CLOGO... so you might want to clarify this is for unlocked bootloaders only.
Does this tool resize any images that are larger than 1280x720? And does it take into account needing a solid border around the edges if there isn't one?

Yes the tool only manage logo.bin container and don't care of image size or number.
KidJoe said:
And does it take into account needing a solid border around the edges if there isn't one?
Click to expand...
Click to collapse
Are you sure for the solid border around the edges ?
I generate random noise image and it display without problem.

marmottepoilue said:
Yes the tool only manage logo.bin container and don't care of image size or number.
Are you sure for the solid border around the edges ?
I generate random noise image and it display without problem.
Click to expand...
Click to collapse
Yup. I am very sure.. See -> http://forum.xda-developers.com/showpost.php?p=49179887&postcount=150
and more recently a specific example with walk through and samples -> http://forum.xda-developers.com/showpost.php?p=53712454&postcount=408
And over sized images (greater than 1280x720) will also cause issues, at least when replacing the unlocked bootloader warning message.

KidJoe said:
and more recently a specific example with walk through and samples -> http://forum.xda-developers.com/showpost.php?p=53712454&postcount=408
Click to expand...
Click to collapse
I make the test on moto G (android 4.4.4) with IMAG0434.bmp (legoland toy story without border) from your post and it works.
I think the carock's script you used has issues.

marmottepoilue said:
I make the test on moto G (android 4.4.4) with IMAG0434.bmp (legoland toy story without border) from your post and it works.
I think the carock's script you used has issues.
Click to expand...
Click to collapse
Ok. I just took the logo.bin from the Verizon 4.4.2 rom, placed it in the folder with your tool. Added IMAG0434.bmp to the folder, then ran the following... mlogo logo.bin replace logo_unlocked imag0434.bmp
I then used mfastboot to flash the resulting logo.bin. It does work. So is it an issue in Carock's script itself? or FFMPEG which he is using?
Btw, doing the same using an oversized image (i.e. greater than 1280x720) with your tool does result in a scrambled screen when booting, but at least it boots and doesn't get hung.
Doing a mlogo logo-chrimbus.bmp.bin extract logo_unlocked (from a previously created logo.bin I made using carock's script) works. I get the proper 1280x720 png image.
Are there any conditions to changing the battery graphic?

KidJoe said:
Are there any conditions to changing the battery graphic?
Click to expand...
Click to collapse
I've not tested but it should be the same.
If you want to automatically reduce images greater than phone resolution you can use XnView nConvert:
nconvert.exe -ratio -rtype lanczos -rflag decr -resize 720 1280 image.png
I also updated my first post to explain how images with resolution lesser than phone's are managed.

Is this tool also available for Linux OS??

@TheStrix
You can try this (Compiled and tested on ubuntu)
Edit: moved to first post

marmottepoilue said:
@TheStrix
You can try this
Click to expand...
Click to collapse
How to execute that file??
I can see only oe file in the zip folder!
Please tell the steps

@TheStrix
It works exactly the same as the windows version.
Unzip, untar to the folder of your choice (with read/write access)
Copy your logo.bin alongside
Open a terminal and navigate to the folder
Then execute the command of your choice, for example:
./mlogo logo.bin extractall

marmottepoilue said:
@TheStrix
It works exactly the same as the windows version.
Unzip, untar to the folder of your choice (with read/write access)
Copy your logo.bin alongside
Open a terminal and navigate to the folder
Then execute the command of your choice, for example:
./mlogo logo.bin extractall
Click to expand...
Click to collapse
Its woking mate! Thank you!
Here's mine!
{
"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"
}

GUI
Hey Guys, I have made a simple GUI in java for this tool for replacing boot logo, This will make it user friendly and the process is much easier.
you can download it from link below screenshots:
you just need to keep this tool and downloaded file in same folder as shown in screenshots below.
Download Link

any way use on Razr HD ?

s27moto said:
any way use on Razr HD ?
Click to expand...
Click to collapse
I believe the logo.bin is a different format

One thing worth noting for a Moto G, and maybe the other phones, is that the logo partition max size, and therefore, the max size of logo.bin, is 4MiB. This means you could get by with only one complex 1280x720 logo. (worst case about 3MiB).
This means if you wish to do a complex normal logo, and a complex 0-3% battery logo, you will want to make sure the combined size of the 2, does not cause logo.bin to exceed 4MiB.

s27moto said:
any way use on Razr HD ?
Click to expand...
Click to collapse
I just release 'mlogo (old format)' to manage logo on phones without android 4.4.x like Razr HD (XT925).
You can download it in the first post.

I think I found a bug in your tool for the android 4.4.x logo.bin creator.
What I was trying to do, was make sure the moto g/x/e could find logo_boot, in the event that it needed to, but actually have it pretty well removed. Seems if the exact size of the compressed data happens to line up on a 512 byte boundary, the program errors when you try to append any additional data onto logo.bin If said file is replacing something in logo.bin, then the error completely destroys logo.bin
One way you can reproduce this bug, is to create an empty one color 100x100 bmp file, and feed that as one of the inputs. As long as the RLE compressed image size is not a multiple of 512, then the program will correctly work.
The main reason of wanting logo_boot to be as small as possible, while still existing, is to give as much space as possible within the 4MB max size of logo.bin for logo_battery and logo_unlocked.

Thanks OP for the tool. I appreciate the Linux support as well.

@caitsith2
Thank you for your feedback.
I make a version 1.02 that correct the bug you found.

[TOOL][1.0.0] Change bootlogo (and other images) with imgdata tool

What is imgdata tool?
It is a tool to extract images like the bootlogo from the partition called imgdata. Then you can change these images with gimp or photshop then repack them into a new imgdata image and flash it to your device and see your new custom bootlogo or fastboot menu.
Instructions
Download imgdata tool from here or from the attachments.
Run start.bat script if you are a windows user or run start script if you are a linux or mac user.
Verify your phone's model by exactly typing NEXUS 5X.
{
"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"
}
Select option number 1 called Extract imgdata.
Drag and drop the imgdata.img file from stock folder to imgdata tool or type the path to imgdata.img.
The folder with the extracted images should pop-up. If it does not happen you will find the images in the images folder.
Edit the desired images.
Edit pos.txt:
Never change the entries line and never remove any line.
First column is the name of the image second column is the position of the image.
0x0 means the image will be shown on your screen in the top left corner.
If it is 0x1 the image move 1 pixel down.
If it is 1x0 the image will move 1 pixel right.
If it is 244x858 the image will move 244 pixels right and 858 pixels down.
You can check your changes in option number 2 called Preview from the main menu in the imgdata tool. It should open the image you selected or open the preview folder if you selected the option View all. If it does not happen then the preveiw images can be found in the folder called preveiws.
When you finished editing the images you can build a new imgdata from the images you edited by selecting option number 3 called Build imgdata from the main menu in the imgdata tool.
After the building finished you can flash the zip called flash-me.zip to flash the new imgdata to your phone or if you want you can flash it using imgdata tool.
Notes
Only 24 bit bmp files are acceptable.
You can find the custom imgdata image in the folder called custom after the building.
The maximum file size of the imgdata.img is 3145728 bytes (3 MiB). The tool will show you an error if that happens and it will ask you do you want to reduce the color depth of an image from 24 bit to 16 bit. If you still exceed the 3 MiB limit you can resize other images which are not important to you to a 1x1 pixel image.
If you want to use full screen images in the fastboot menu, then it will cover the system texts.
To revert the changes download stock.zip from the attachements and flash it.
If a new bootloader is released stop using the tool until I check whether the imgdata changed or not.
Working with bootloader version BHZ11b or older.
Changelog
1.0.0
First release
Click to expand...
Click to collapse
Sources
https://github.com/bitdomo/imgdata/tree/bullhead
Technical details
Structure of imgdata
Partition header
DATA1: 8 byte string. It says IMGDATA!. It is similar to the begining of boot.img and recovery.img that says ANDROID!
DATA2: I don't know.
DATA3: Number of images. It is 12.
8 bytes of 0: I dont know the purpose of that
Click to expand...
Click to collapse
Image headers
DATA4: 16 byte string. Tells the name of the image.
DATA5: image width in pixel
DATA6: image height in pixel
DATA7: X position of the image in pixel
DATA8: Y position of the image in pixel
DATA9: it tells where is the begining of the picture on imgdata
DATA10: size of the image
Click to expand...
Click to collapse
This pattern goes on, from DATA4 to DATA10.
Structure of the images
It consist of 4 bytes of chunks.
First byte: count number
Second byte: R value
Third byte: G value
Fourth byte: B value
Example:
05 00 00 00 02 FF FF FF
05: count number = 5
00 00 00: RGB value = black
02: count number = 2
FF FF FF: RGB value = white
So from the top left corner of your screen you would see 5 black pixels then 2 white pixels.
Thanks for @gee one for tesiting it on his Nexus 5X.

This is really nice.... good work :good:

Oh this looks promising. It reminds me of the old windows mobile days!

Will this get rid of the triangle bootloader unlocked warning?

Baldilocks said:
Will this get rid of the triangle bootloader unlocked warning?
Click to expand...
Click to collapse
Well you can change those triangle images to anything. I dont have nexus 5x so I have no idea how the booting goes on on a custom rom or with a custom kernel, but if you have to press power key to confirm booting non google android or kernel then that cannot be skipped, you can just change those images.

Just tested, and yes you can visually remove the warnings, but note flashing a custom imgdata file will cause the bootloader to boot to the red error screen instead of the yellow one, so you will want to update the images for all of the warning messages to remove it.

Thank you for creating this @bitdomo ! Very simple to use.
And a thank you to @ddggttff3 for saving me from what would've been several minutes of swearing and confusion.
I've created a couple versions of this that swap out the ugly bootloader verification messages for something more minimal. I'll pull this out to another thread if you'd prefer, but thought I'd share here.
Opted to retain something visual to let you know if you've accidentally paused your boot, but otherwise it just displays the google boot logo.
Changes:
I've added a flashable zip and .img for the subtle version that includes the unlocked padlock icon. These are named as subtle-padlock-BHZ10i-n5x in the attachments.
Preview Images:
Image that shows during boot:
"Visible" version that clearly shows if you've paused the boot process:
"Subtle" Version that shows if you've paused the boot process. Hopefully suitable for minimalists
There is also a subtle-padlock version which is the same as the above, but includes the unlocked padlock that you've seen before.
And the paused state:
Downloads and installation for bootloader BHZ10i:
All attached. .img files can be flashed via fastboot:
fastboot flash imgdata theimageyouchose.img
Zips are flashable in recovery (but I have been testing with fastboot).
You will also want to keep a copy of stock.zip from the first post too - just in case!
MD5 checksums here:
Code:
b61d23cdd9071d03eb73c6066c06bf87 *visible-BHZ10i-n5x.img
01136452f5b4b5567ad9ca6efabd90db *visible-BHZ10i-n5x.zip
6002edd267341caec555edcdbfe4ec96 *subtle-BHZ10i-n5x.img
b1f8c3bb87f150a3f70ef6c608d6a263 *subtle-BHZ10i-n5x.zip
6eca6a058fcc272cbb3355dd4f70b521 *subtle-padlock-BHZ10i-n5x.img
a4c9ca6ba44bef3d629c8178bcec8ec3 *subtle-padlock-BHZ10i-n5x.zip

PhoenixTank said:
Thank you for creating this @bitdomo ! Very simple to use.
And a thank you to @ddggttff3 for saving me from what would've been several minutes of swearing and confusion.
I've created a couple versions of this that swap out the ugly bootloader verification messages for something more minimal. I'll pull this out to another thread if you'd prefer, but thought I'd share here.
Opted to retain something visual to let you know if you've accidentally paused your boot, but otherwise it just displays the google boot logo.
Preview Images:
Image that shows during boot:
"Visible" version that clearly shows if you've paused the boot process:
"Subtle" Version that shows if you've paused the boot process. Hopefully suitable for minimalists
Downloads and installation for bootloader BHZ10i:
All attached. .img files can be flashed via fastboot:
fastboot flash imgdata theimageyouchose.img
Zips are flashable in recovery (but I have been testing with fastboot).
You will also want to keep a copy of stock.zip from the first post too - just in case!
MD5 checksums here:
Code:
b61d23cdd9071d03eb73c6066c06bf87 *visible-BHZ10i-n5x.img
01136452f5b4b5567ad9ca6efabd90db *visible-BHZ10i-n5x.zip
6002edd267341caec555edcdbfe4ec96 *subtle-BHZ10i-n5x.img
b1f8c3bb87f150a3f70ef6c608d6a263 *subtle-BHZ10i-n5x.zip
Click to expand...
Click to collapse
If I flash the subtle version, is that all I need to do to get rid of the bootloader warning screen?

kbbeer said:
If I flash the subtle version, is that all I need to do to get rid of the bootloader warning screen?
Click to expand...
Click to collapse
Yes, but bear in mind that it will still cause the same delay and can be manually paused, just like the normal warning screen.
I've also just uploaded a new set of subtle images for anyone who would like the matching unlocked padlock icon.

Worked, but it actually still showed the unlock image at the bottom. Still happy to get rid of the warning screen.

Confirmed working on mdb08m

kbbeer said:
Worked, but it actually still showed the unlock image at the bottom. Still happy to get rid of the warning screen.
Click to expand...
Click to collapse
Depending on which you flashed, the effect is a little different:
With subtle-BHZ10i-n5x, visually it will show A and then B afterwards.
With subtle-padlock-BHZ10i-n5x, visually, it only shows B, and then the lovely google boot animation as normal.

Does this modify the /system partition at all? Where are these images that are being modified?

Doesn't seem to modify the system partition. I updated and flashed the M firmware and this modification remained unchanged.

I can sleep better at night now.

Works on 6p?

troymz1 said:
Works on 6p?
Click to expand...
Click to collapse
It will not work.

bitdomo said:
It will not work.
Click to expand...
Click to collapse
Please make a 6P tool, I really want to get rid of the boot Warning

eudemonky said:
Please make a 6P tool, I really want to get rid of the boot Warning
Click to expand...
Click to collapse
Not possible. I dont see any partition which could hold the images. However the aboot partition is 3,2 mb larger than on any other phone so probably the images on the aboot partition and it is part of the aboot code. Which means you cannot change a single pixel's color of any image because aboot has a signiture check. Even changing 1 bit of the aboot code will result in a hard brick of the phone.

bitdomo said:
Not possible. I dont see any partition which could hold the images. However the aboot partition is 3,2 mb larger than on any other phone so probably the images on the aboot partition and it is part of the aboot code. Which means you cannot change a single pixel's color of any image because aboot has a signiture check. Even changing 1 bit of the aboot code will result in a hard brick of the phone.
Click to expand...
Click to collapse
I read this thread, http://forum.xda-developers.com/nexus-6p/orig-development/mod-change-splash-screen-warning-t3260264
then I use this tool, replace the PNG and rebulid a splash.bin
but I can not flash it, when I flash it use "fastboot flash logo splash.bin" , I get error said“permission denied”

[BOOT] Remove Boot Warning - All Exynos Devices - After Root - Tutorial - 14th December 2020

Hello everyone ...
I hope you all are fine...
Merry Christmas and Happy New Year in Advance, like really really in advance lol ...
First, I'd like to say God Bless @Dr.Ketan, @geiti94 & @ianmacd as a Samsung Device owner, I've always rooted my device through their hard efforts in making guides and flashables and God Bless @topjohnwu for Magisk...
God bless all developers contributing to XDA Forum too...
Right, so after getting the root on the phone, especially in the new Android OS or the majority of Android devices or so,
The boot-up screen wasn't like what we were used to,
There are many warnings which kind of screams ROOTED device aside from not being beautiful...
I decided on my Samsung Galaxy Note 10 to fix that, experimented and I loved it, but one thing happened...
Just like I did with the SoundMod to enable Duel Speaker on my previous phone, Many members posted asking if it can be done for their device...
So here I am, Opening another tutorial thread that hopefully would be helpful to many of you on how to handle the problem of removing the annoying boot warning...
So let's get started but first:
Important Notice (Hijack not intended):
I did search in XDA thread for different devices (randomly selected) and some had a thread and some did not for fixing the warning...
What I want to say is, I am sharing my own experience and experiment from my Galaxy Note 10 Plus and Galaxy Note 20 Ultra...
My Intentions are to simply support all Devices with a solution as much as I can (I sadly don't have time to check the Snapdragon but I did try with @louforgiveno & I thank him for experimenting with me, forgive me for not being able to help snappy users, if I get the time, I will defiantly look into making it possible)...
Click to expand...
Click to collapse
ok now, next is getting your files ready, you will need:
7-Zip Zstandard Edition credits go to Tino Reichardt...
Your Original ROM (You mainly need the BL aka Bootloader file but it's good to have the original ROM), get it from the website or XDA, if you just want to remove the boot warning and don't want to download the entire ROM then regardless of the CSC version, make sure the ROM or the BL you will grab has the exact boot screen of yours, again, you only need the BL (Bootloader) file which would look like BL_****_****_****_***_***_why_so_long_name.tar.md5 or so...
Now the instructions, LET'S GO:
BACKUP YOUR PHONE BEFORE FLASHING ANYTHING, ok sorry for yelling, I just don't want to see any of you go through the hustle of going into boot loops or anything else...
Install the 7zip Zs edition...
now right-click on the BL file and to 7-Zip ZS -> open archive...
Drag the file up_param.bin.lz4 outside anywhere you want...
now right-click on the up_param.bin.lz4 and 7-Zip ZS -> extract here, you will have up_param.bin...
now right-click on the up_param.bin file and 7-Zip ZS -> open archive...
Inside 2 images are important, 1 is the warning in red font and the other is the logo if you wish to customize your boot screen, make it cool or keep it as it is stock...
So drag the following "logo.jpg" and "booting_warning.jpg" to anywhere you want and minimize the window...
Some of you may ask & wonder about "svb_orange.jpg" as this is the bootloader warning , yes true, but there is no need for it if you wish to have a normal boot screen
Click to expand...
Click to collapse
Edit with paint "booting_warning.jpg" and make it completely black...
Now for "logo.jpg" you have 2 options:
If you want to show the stock logo instead of bootloader warning, rename "logo.jpg" to "svb_orange.jpg" and you're done...
If you want a custom logo, edit the logo without resizing or changing its dimensions, make a duplicate, one will be "logo.jpg" and the other is "svb_orange.jpg"...
Now open the minimized window or if you closed the window then right-click on the up_param.bin file and to 7-Zip ZS -> open archive...
Drag the images back into the up_param.bin and close the window...
Now right-click on up_param.bin and 7-Zip ZS -> Add to archive...
Change Archive format to tar, change nothing else, and hit ok...
Feel free to change the name from up_param.tar to whatever you want like "I_am_cool_I_fix_bl_warning.tar" in my case I would write the device name and version with meaningful description "STOCK_NOTE_20_ULTRA_OS10_FIX_BL.tar", IT IS VERY IMPORTANT TO NOT USE SPACE, DOTS OR SPECIAL CHARACTERS WHEN NAMING THE FILE, ok ok, I am calm now...
Now Flash the tar file treating it as a BL file when flashing (NOT RECOVERY FLASHABLE)...
I think I said "now" a lot but don't worry we are done lol ...
Enjoy looking at your phone, no more warning or annoying press to continue, it will boot up like it used to ...
Here is an example of before and after for Samsung Galaxy Note 10 plus 5G, you should be able to tell which is before and which is after and what I mean by stock (10.1) and center (custom) (10.2)...
Spoiler: Show Example
{
"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"
}
<-- Before & After -->
Don't Forget to Smash the THANKS Button
and
if you're very happy, support or buy me a cup of coffee through a donation, that would be nice ...
... Happy Modification ...​

F.A.Q
Q. Is it safe?
A. If you follow my instructions, yes, very safe, you are simply replacing images, of the bootloader, you just need to flash it as BL and not somewhere else...
Q. Do I need to backup?
A. ALWAYS BACKUP, ALWAYS BACKUP, ehm, ok ok I am calm, you always must have a backup when you want to flash anything...
Never experiment without backing up...
Q. What could go wrong?
A. Probably boot loop and you might need to reflash the stock and go through the process of rooting everything again unless you have a backup you can restore through your custom recovery...
Q. Can I have a custom boot screen?
A. Absolutely, you can have anything, just use the same dimensions of the image and don't make it heavy sized (seriously don't make it big, stick to its range like 200 Kbs is fair)...
Q. While I am there changing images, can I change other images?
A. You can but don't be surprised if you can't read anything written on the screen later lol...
Q. What is the impact of this on my Device?
A. Nothing, you just replaced your phone boot images...
Q. If I reflash the ROM, will it reset and go away?
A. Yes it will go and it will show you the bootscreen of the flashed ROM (stock or custom)...

Changelog:
-- 14th December 2020 - Written the instructions...
To be Done in the Future:
-- Video Tutorial...

Thank you man for the detailed steps… really appreciated…

me7tarfeek said:
Thank you man for the detailed steps… really appreciated…
Click to expand...
Click to collapse
You're most welcome...

I have a snapdragon N20 Ultra, to test it should I follow the same steps or there is something else?

Oni-X said:
I have a snapdragon N20 Ultra, to test it should I follow the same steps or there is something else?
Click to expand...
Click to collapse
This is Exynos solution...
I didn't have time for Snapdragon...
I'm trying to find some time and then I'll find a Snapdragon volunteer and work on finding a solution...

Dante63 said:
This is Exynos solution...
I didn't have time for Snapdragon...
I'm trying to find some time and then I'll find a Snapdragon volunteer and work on finding a solution...
Click to expand...
Click to collapse
I can help

Oni-X said:
I can help
Click to expand...
Click to collapse
Please DM me, and when i have time, i will message you with potential ideas on how to locate the boot images, keep in mind that you may have to reinstall the ROM or restore nandroid backup in case of any flashing failure or something goes wrong after successful flashing...

Would it be the same on the snapdragon USA version if its rooted and I am able to odin?

t2noob said:
Would it be the same on the snapdragon USA version if its rooted and I am able to odin?
Click to expand...
Click to collapse
No, as I mentioned, this is only for Exynos, I still didn't find any snapdragon user that wish to test with me and find a way to remove the annoying warning...

Dante63 said:
No, as I mentioned, this is only for Exynos, I still didn't find any snapdragon user that wish to test with me and find a way to remove the annoying warning...
Click to expand...
Click to collapse
I'm willing to you just need a boot from my device? It's a n9750u VZW note 10 +

t2noob said:
I'm willing to you just need a boot from my device? It's a n9750u VZW note 10 +
Click to expand...
Click to collapse
You need to pull a file from your phone, because snapdragon ROM is not easy to navigate through, files are uncompressed and installed by the device itself, unlike Exynos, we can extract and view files... the risks are when pushing back the file (that is if the file was found), will it boot normally, or will it end up in bootloop or make the system no longer functional, hence why I said take a backup and nandroid, it might be a long journey...

Dante63 said:
You need to pull a file from your phone, because snapdragon ROM is not easy to navigate through, files are uncompressed and installed by the device itself, unlike Exynos, we can extract and view files... the risks are when pushing back the file (that is if the file was found), will it boot normally, or will it end up in bootloop or make the system no longer functional, hence why I said take a backup and nandroid, it might be a long journey...
Click to expand...
Click to collapse
I have a backup from today I was messing with weta mod earlier. If your willing to give it a go I'll try my best

t2noob said:
I have a backup from today I was messing with weta mod earlier. If your willing to give it a go I'll try my best
Click to expand...
Click to collapse
Alright then, DM me please...

Let me know if I can help in any way I have US Galaxy Note 10+ (SM-N975U)

New Note 20 Ultra Firmware - N985FXXU1DUB6 Causes a boot loop. Could you have a look to check what has been changed ?
I did it successfully on the CU firmwares, but this has some sort of an issue..

Does it work on galaxy note 10 lite?
I'll take a chance on my note 10 lite.

It didn't work on the Galaxy Note 10 Lite, it looped infinitely, so I put the original images back in their proper locations and reinstalled the file up_param.tar, so the phone went back to work without needing to reinstall the Stock Rom.

hy sir iam using galaxy s20 fe exynos version with one ui 3.1 but iam not able unlock bootloader and oem unlock is disable as oem lock = lock(L) in download mode ,frp lock is off when ever i try to flash rom through odin it stucks and i get warning on download mode stating that ,custom binary blocked ,and kg state is = normal , what to do ?