yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] Goose247:
Making the image

1. Now that you have established the image size make sure the image you intend to use for a boot logo is the exact same resolution.

2. Open Gimp and open the image you want to use as a boot logo.

2b. Click on "Image", "Mode", "Indexed".

2c. Set Maximum number of colours to 224 (very important). Then click "Convert".

If you find that the quality of the image isn't as good play around with the colour dithering settings

but never change the Maximum number of colours from 224.

2d. Click on "File" then "Export as".

2e. Click on "Select File Type (By Extension).

2f. Scroll down and select "PPM Image" then "Export"

2g. Data formatting select "ASCII" (Very Important), then "Export"

Getting easier, isn't it :). Off to Importing image to kernel.
[MTCB Software Development] Goose247:
Importing image to kernel

1. Using RK3xxx click on "Logo tools", then "Run Logo Changer"

2. Click "File" then "Select kernel.img" and load the kernel.img you modified earlier.

3. Click on "File" then select "PNM logo image" and load the PPM image you created in Gimp.

4. If both loaded ok

Simply click on "Replace" and the image in the right side box should change to your custom logo. Click "Exit"

Forgot to take a screenshot of it but it will move the image in the left box over to the right.

And that my pedigree chums is your kernel.img ready to be installed on your unit.

Last but not least . Installing kernel to system.
[MTCB Software Development] Goose247:
Installing kernel to system

There is a difference between kitkat and lollipop so please make sure you follow the correct instructions.

1. Copy kernel.img to external_sd.

2. Open terminal emulator.

3a. If you are using Kitkat Android 4.4.4.

Type the following. Make sure to press enter between each line:

su

cd /mnt/external_sd

dd if=kernel.img of=/dev/block/mtd/by-name/kernel

3b. If you are using Lollipop Android 5.1.

Type the following. Making sure to hit enter between each line:

su

cd /mnt/external_sd

dd if=kernel.img of=/dev/block/platform/emmc/by-name/kernel

Regardless of which one you use, you should get a few lines of confirmation. Forgot to take another screenshot but it should look something like this:

12345+1 records in
12345+1 records out
12345 bytes transferred in 0.198 secs

If it failed then it will look something like this:

12345+0 records in
12345+0 records out
12345 bytes transferred in 0.198 secs

Fingers crossed that you have the 1st output result.

You can simply type "Reboot" in terminal emulator and it will reboot the system and again, fingers crossed you will see your nice new boot logo.

I have taken a lot of time and effort to put this guide together. I know it's not perfect but I hope it helps :good:
[MTCB Software Development] psxsnake:
GREAT
[MTCB Software Development] Jaihoidundso:
Example Boot Logos for Head Units

New Boot Logos on Request! Be sure, that you use the correct resolution! All files are optimized to PPM format. So you can skip Step 2 "making the image"! All downloads are direct downloads from my server!

TOYOTA

DOWNLOAD 1024x600

VAUXHALL

DOWNLOAD 1024x600

VAUXHALL ASTRA

DOWNLOAD 1024x600
[MTCB Software Development] cat2115:
Will this work with "Update_4_4_4_FUSE_800X480_RK3066_40_MAL_12_06_2016_FIX_RADIO_MTCB" - Last modified 26-Jun-2016?

Thanks
[MTCB Software Development] Goose247:
Read the OP
[MTCB Software Development] Goose247:
I think I did say in the OP that it was only tested on MTCB units. I don't know what the differences are between the 2 so I really can't comment or give you advice on MTCD units.
[MTCB Software Development] zoxenrbg:
I use an 5.1.1 RK3188 China directly.

MCU GS 1.6...

MTCD. I help you ?

Tell me what I have to tell you please do and how to put the logo annimé (I can not find procedure).

Thanks for your help !
[MTCB Software Development] jacobreed222:
Hey man! I would really appreciate it if you could make a Toyota boot logo for me please? Thank you so mcuh!
[MTCB Software Development] bsavoir22:
I believe this was meant so anyone could change the 1st boot logo. It is very simple as I have finished mine a couple hours ago. This post is not a request for logo but for a user make his/her own. Follow the OP procedures and you will not have any issues. This is my first time to extract anything from a ROM and change something and make it work.
[MTCB Software Development] Goose247:
It's the 1st time I've written a guide so how did it go for you following the procedure?
[MTCB Software Development] bsavoir22:
It was pretty straight forward. The steps were easy to follow and I had no issues with the guide. The only issue i had was with GIMP and resizing my image, for some reason i only got it to 800x500, but after playing around with it i found that I had already created and save a 800x480 resolution copy.
[MTCB Software Development] Jaihoidundso:
Which resolution do you have?
[MTCB Software Development] jacobreed222:
I have the JOYING 1024x600
[MTCB Software Development] Jaihoidundso:
You can find your image here: http://xdaforums.com/showpost.php?p=68535050&postcount=7 #7
[MTCB Software Development] jacobreed222:
Thank you so much man!
[MTCB Software Development] Goose247:
Even though your unit is 1024x600 make sure to check what the resolution of the boot screen in your kernel is. A lot of 1024x600 unit have 800x480 boot logos.
[MTCB Software Development] chompi-xda:
Hi, thanks for the great topic.

I managed to create a new kernel.img with new boot image from 800X480_RK3066_41_MAL_18_09_2016_MTCB rom.

Using terminal emulator doing reboot will show my new image, but after turning the car off (HU shutdown) and on again, only default Malaysk image shows.

I tried to create new update.img and flashed successfully but it still shows the old boot image.

Is that because the Rom is after Apr 2016 or am I missing something?

Many thanks.

Chompi
[MTCB Software Development] Goose247:
Yeah, I have never been able to figure it out. There is something being checked during boot and if the kernel is different from what is in the backup.img then I think it reverts back to the original which is stored in the backup.img.

I have tried decompiling the backup.img and changing the boot logo in the kernel.img and then rebuilding the backup.img but it has always ended up in a soft brick situation.

I wish I could help more but I spent months trying to work around it.
[MTCB Software Development] chompi-xda:
I finally got the boot logo showing, thanks to your hints. I did pretty much what you mentioned: extracting backup.img, copying over new kernel.img, rebuild backup.img and update.img. Not sure why you end up in bricks.

Now my concern is restoring data after rom flash. TIBU is great and does most of the job, except for few things, e.g. bluetooth paired devices and Torque pro settings.
[MTCB Software Development] Goose247:
I'll maybe add an extra bit to the original OP detailing how to extract backup.img and adding new kernel.img to it but adding a big warning to do at your own risk.

If you are installing a rom the same as what is already on your unit then you don't need to do any wipe and your data and settings should still be there.
[MTCB Software Development] sarruma:
We'd be very gratefull to you if you added indeed that extra information, describing those missing steps! Please show us, how could we try and change that boot logo according to our needs? (of course the risk is ours!)

Thank you in advance! :good:
[MTCB Software Development] Goose247:
Modifying kernel.img inside backup.img

I think this next step will work on any rom of any date.

If you find that after you have completed steps in the OP and your new boot logo only loads on the 1st boot but goes back to the original boot logo then you can attempt these next step.

I cannot stress enough. DO AT YOUR OWN RISK!

1. Using RK3xxx click on "Single tools".

2. Click on "Next tools".

3. Under "backup.img file tools", Click on "Select file". The backup.img will be located in "temp\Android\backupimage".

3a. Then click on "Extract"

All going well you should see this message.

4. You will now have an extra folder named "backupimage" in your "temp". Inside "backupimage" you will have 2 folders and 2 files. We will only be concentrating on "Image" folder.

5. You need to copy the "kernel.img" file you created in the OP to "temp\backupimage\Image". This will overwrite the "kernel.img" that is already there.

6. Recompile "backup.img".

6a. All going well you should receive this message.

7. In the root of RK3xxx tools folder will be a file named "new_backup.img". Rename it to "backup.img and move it to "temp\Android\backupimage". This will overwrite the old one.

8. We need to rebuild the firmware now. If you're not on the main page of RK3xxx tools go there and click on "Build".

8a. A new window will open with a dropdown menu. Select the correct option for your unit. Then click on "Confirm".

9. All going well you should have a 2 new files. 1 named "firmware_new.img" and the 2nd named firmware_new.md5.txt. Rename "firmware_new.img" to "update.img" and install it like a normal firmware.

If you are installing it over the same firmware that is already on your unit you don't need to do a wipe and it should keep all your settings and data but if the firmware that is on your unit is a different version then I strongly advise doing a full wipe before and after installing.

NOTE. All the steps mentioned in the OP and here should in theory work for changing the "recovery.img" boot logo but I can't guarantee it.
[MTCB Software Development] sarruma:
[MENTION=2070494]Goose247[/MENTION]

You are great, thank you! Your guide is idiot-proof and very comprehensive!

I have a 4.4 android HU, so after these additional steps you posted, I'll try and see if this procedure will work, finally changing the boot logo...

Two quick questions:

1. In step 5.5 (just before recompiling backup.img), my guess is that you mean "temp\Android\Image" instead of "temp\Android\backupimage\Image", right?

2. As I see it, following the guide till the very end and rebuilding the firmware, removes the necessity to install kernel.img to system, as flashing the update.img will do that anyway, correct?

Once again, thank you so much for your hard work and help to the community!
[MTCB Software Development] Goose247:
It's actually a typo on my part but have corrected it. It should be "temp\backupimage\image". After you decompile backup.img, it creates the folder "backupimage"You aren't going to modify kernel.img that is stored inside backup.img. You are simply copying the original kernel.img that you modified from the original steps in the OP.

If you followed the steps in the OP and the boot logo didn't work by updating using terminal emulator and you have to do the above steps then you have to install it as a full rom. If it worked after the original steps (installing kernel.img to system) then you don't need to do the above steps.
[MTCB Software Development] Johny DJ:
I tried to open karnel.img from this image: DIY_JY_FUSE_AllCPU_KK444_AllRes_160223_root_mod_boo_2016-03-30_v1.0.1 its from: booroondook RK3188 1024x600 (karnel is the same for both images 800x480)

I failed:

KernelPass:rkdroid

This is no Kernel.img or zImage file

I also can't find the logo password like you wrote for HxD.

I successfully changed karnel from another image and import new image, but I don't know if I can also import this karnel to my image or recompile update.img with new karnel...and yes I used the same resolution.
[MTCB Software Development] Goose247:
Looks like he completely removed the entry for rk logo password. I made the modifications and it works now but I take no responsibility if something goes wrong.

All you need to do is change the boot logo now.
[MTCB Software Development] Johny DJ:
Thank you! Will try.

Edit:

did work, I replaced and first boot was my new logo, but second boot still old logo, like the system copied over new one, strange... Do you know how to solve this?

Will try another solution I read on the forum...to replace kernel in bootimage too and then flash the firmware again.

Can this also be done through terminal or not?

Edit2: [MENTION=2070494]Goose247[/MENTION] it worked! I unpacked backup image and replace karnel there also, then packed again and flashed update.img and now I have new logo each time! Thanks!

I also tried to change recovery image but unseccessfull, I got blank screen, but I recovered with SD recovery tool...
[MTCB Software Development] Marius B:
Hi Goose247 !

Can you make latest changes for boot from Malay update rk3188 hd ? I tried your tutorial but after restart show again. I tired to put file in backup but I recived some error when install in unit about verification. What I don't do well ?
[MTCB Software Development] Goose247:
I'm not sure. All I can do is try it for you. If you let me know the exact rom (date etc.) and upload the boot logo that you want to use. I can't guarantee it will work and I have had problems when trying to change the logo in the backup so use at your own risk.
[MTCB Software Development] Marius B:
this rom https://yadi.sk/d/6SsG-C243B34wx .

for image what you use for vw
[MTCB Software Development] Goose247:
I think for a start the ppm image was set to use too many colours and not sure if it was saved as ascii.

I will upload just the kernel.img and backup.img when I'm finished and assuming you are using rk3xxx firmware tools, save them to the correct locations.

"Android/image" for kernel.img

"Android/backupimage" for backup.img

Then rebuild the rom.
[MTCB Software Development] Marius B:
I use your tutorial and pictures is extract from your rom that you post for all cars .
[MTCB Software Development] Goose247:
Try these. Remember I take no responsibility if it causes any unusual behaviour.

new_boot_logo.rar
[MTCB Software Development] pa.ko:
There is some hard coded check in Chinese and Malaysk ROM which verify checksum of boot logo images. If they don't have particular checksum then ROM displays error. If backup image is OK, then boot process copies backup over boot (thus it gets reverted if you just change in boot but not in backup partition).

That check is, I believe, somewhere in recovery!

So in order to enable logo replacement you have to also reverse / decompile Recovery, search for error text you get disable or change that verification to suit your image.
[MTCB Software Development] Marius B:
I find logo in kernel, backup and recovery.

Where I can find file that offer error install ? Right now work but I thing if make factory settings reverse to first image. I ask Malay to see if can make like option to change that.

Trimis de pe al meu SM-G920F folosind Tapatalk
[MTCB Software Development] pedromaiaz:
hi there, soo i am trying to change the initial logo to something more hardcore, well i have this issue:

KernelPass:rkdroid

Kernel image size: 800 * 480

Supported Image Size: 800 * 480

LogoFile:bootlogo44.ppm

LogoSize:800 * 480

Replace»...

kernel logo: 800 * 480 clutsize:224

picture: 800 * 480 clutsize:208

kernelÐÂlogo:800 * 480

Supported Image Size: 800 * 480

Complete

there is something wrong with the image?....btw , after messing a bit with the tools ive found there are 3 places with kernel bootlogo(one of them i had to put *.img to change the image)?...i have to change them all?

*i was curious* after checking the kernel on hex ive found my string has just one number diferent from yours...is normal?

the rom used was the latest update_4_4_4_FUSE_800X480_RK3188_21_MAL_19_02_2017_MTCB

my goal is to have a proper sequence: bootlogo and 2º bootlogo similar.... i have to finish the second logo :P

can you guide me a bit?
[MTCB Software Development] pedromaiaz:
hi there, an update

i did with your tutorial and it worked, but with one error flashing.

soo i went checking all the kernel.img found 4 off them (2 kernel files i had to add img extension to change the bootlogo)

i think there are 4 places where the bootlogo is stored

one thing i notice, all kernel.img files have the same exact size, soo i suppose changing one and them replace the 3 them will work? i did not flashed the kernel in terminal but i rebuilt all the firmware then i flashed it normal way....

thanks!!
[MTCB Software Development] pedromaiaz:
Done! I am a happy guy! :) I leave here a few screenshots(bootlogo & bootanimation)

latest Malaysk firmware, used the software here discribed, + photoshop, reading a few times, coffee and pacience( a few try´s and errors)

Files also shared! :)800x480

Rock On Mates
[MTCB Software Development] Goose247:
Glad you got it working :good:

All you need to do now is pray that Malaysk doesn't release a newer rom for a while :p
[MTCB Software Development] pedromaiaz:
....if it release it, well.....more coffee and pacience!....this is a learning process! more you do; more you learn! :)

Rock On Mate!

update:

still working ! update_4_4_4_FUSE_800X480_RK3188_22_MAL_26_08_2017_MTCB
[MTCB Software Development] nemesisandforce:
hi 1024x600 kernel.img necassery.help me please.rk3188
[MTCB Software Development] nemesisandforce:
"Making the image" program need.
[MTCB Software Development] fur0n:
there is a tutorial for mtcd HU somewhere ? thanks
[MTCB Software Development] mickchip:
I have tried this with "nupdate_Android_7_1_2_v_4_1_MALAYSK_11_06_2018_MTCD_MTCE_PX3"

and have successfully changed the logo in A: the kernel, B: the recovery and C: the backup image (kernel & recovery) to my own however I still get the original logo! any ideas anyone, where else could it be stored.
[MTCB Software Development] f41sal:
Hi

Do you have a stock AMG logo for 1280 X 480 resolution?

Thanks

Faisal
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
i want to know how can is install cm12.1 on s2 i9100

full guide plz n where can i get files that u need plz tell me what files i need

my device running android 4.0.3

i want cm12.1 on it plz help me out

which recovery i need to install

plz tell me the precedure. pleaseee
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
plz someone help me hmmm
[Galaxy S II Q&A, Help & Troubleshooting] mixchan:
First update your phone to the latest official firmware which is 4.1.2 jellybean

Then Partition Guide

Later, you need to download & flash ...latest Rom of your choice, GApps & TWRP Rec (Image) or TWRP Flashable ZIP.

Have a look also for this guide....
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
Hi [MENTION=5992993]EMONESSboy[/MENTION],

Before doing anything, you need to update your phone to the latest official firmware which is 4.1.2 jellybean. You should be able to obtain this update via Kies or OTA or manually via ODIN.

Then, we will be able to guide you through the rest of the required steps.

gsstudios
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
there is no ota update... it say your device up to date...

there is any way aroud...? which i can perform without pc....?

flashable jellybean rom on this 4.0.3

any way aroud plz tell..?
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
it will work if i download latest firmware for i9100 and flash it through mobile odinn..???

will it work fine..?

please tell me

thanks
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
my device is indian and there i found only 4.0.3 or 4.0.4 not 4.1.2 :(

can you please provide me the link where can i ger this 4.1.2 firmware..?
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
http://samsung-updates.com/device/?id=GT-I9100&details=Galaxy_S_2

which one should i download

this is my device kernel version right now I9100XWLP7 which is 4.0.3

which firmware should i install plz tell me
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
Download the one for your region. To see which country the region code belongs to, just hover your mouse over one of them.

You should be using the PC version of ODIN and not mobile ODIN.

gsstudios
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
soo this is the latest which i have 4.0.3 there is no 4.1.2 for my device india region i dont know(what is it?) version that i mentioned is other post

now what to do?
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
I believe you have missed it. The region code for India is INU (version I9100XWLST). Please note that you can flash any firmware region on your phone, but for best mobile carrier compatibility, your region will be the best (modem flash after update may be sufficient if you have chosen to flash some other region).

gsstudios
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
i got one 4.1.2 firmware which is for galaxy s2 i9100 india but there kernel name and pda csc name are diffrent from my device....

can i install it...? will it work or not..?
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
i got it.... i am downloading it and will flash it....

please tell me what is the next step

will i have to use odin after it agin..?

because i dont have pc with me i will use my friends pc..

tell me other things which i have to do to get cm12.1 working please sir n thanks
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
You can follow this guide for flashing official firmware here:

Instruction link

Follow the "Instructions For Flashing Firmware:" guide.

Once completed, I will step you through the custom ROM/recovery flashing.

gsstudios
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
using mobile odin ota/update cant do this..?

i will use pc odin and install jelly bean

tell me next steps which i have to perform

if odin steps neened more please guide me for cm12.1

i have downloaded cmblack's cm12.1 unofficial

and official cm12.1 from cm

and downloaded flashable zip file from github for re partitioning pit file http://xdaforums.com/galaxy-s2/orig...ta-sparing-t3311747/post65252583#post65252583 downloaded from here

and i have twrp manager for flashing twrp recovery

and also downloaded a twrp recvery

the gangsters lanchons

hmm plz guide me steps i am waiting

i want to get cm12.1 working today
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
also downloaded opengapps pico and nano for arm 5.1.1
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
i have downloaded this INU firmware

i still have to follow that instruction??

for CSC

if yes i dont get that app on playstore

(samsung galaxy s/s2 CSC)

plz tell me

and other is please tell me after flashing this firmware i still have need or pc ..?

please tell
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
CSC instruction should not be followed as I never mentioned this earlier.

It is still required for you to have PC nearby so you can flash custom recovery via ODIN.

Here is the next thing you will need to flash in ODIN, just download the latest Philz kernel and flash it under PDA:

Philz recovery thread

You will be able to use the repit tool from lanchon. The link you gave me is a flashable pit file and should be avoided. This is the repit tool you should download from:

https://github.com/Lanchon/REPIT

Follow the documentation to repit your device, then flash CM12.1 and Gapps normally in recovery. You will need to flash a Isorec recovery from here:

Isorec TWRP recovery download

gsstudios
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
in philz recovery thread... there is a signed version of philz which can be flashed thruogh stock recovery what about that...?
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
i dont get that re pit lanchad progran cab u plz guide me easy way..?
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
this file...? for re partitioning this zip file have to install via recovery...?

please tell
[Galaxy S II Q&A, Help & Troubleshooting] EMONESSboy:
which kernel is isorec compatible.... o.O it is soo confusing... iso kernel iso recovery... there is not simple a easy way :,(:'(