Galaxy A40 [SM-A405FN] Bootlogo mod.

[tys0n]

Hi. Got my A40 rooted and wasen't happy about the look of the boot logo & warning text, so I did some changes to it.

WARNING:
THIS WILL TRIP KNOX SO DON'T FLASH UNLESS YOU KNOW WHAT YOU'RE DOING.
THIS IS MEANT FOR USERS THAT UNLOCKED BOOTLOADER AND GOT KNOX WARRANTY BIT BLOWN ALREADY

UPDATE, TWRP METHOD
----------------------------------------------------------------------------------------------------------------------------------------------
Now with warning (booting_warning.jpg) completly removed so that we can use full screen custom logos.
1/ Flash "View attachment A405-red_warn_remover.zip".
2/ Reboot to recovery.
3/ Flash "View attachment A405_logo_leafes.zip"

----------------------------------------------------------------------------------------------------------------------------------------------
Wanna make your own logo mod?
Make sure that the images you're doing has the same characteristics as the original files.
Raplace the images in "A405_logo_leafes.zip" and rename the zip to whatever fits.
Edit the "ui_print" in the update-binary if you wish, but please keep the credit to @moluntic for this awesome script.
(Original thread):[Tutorial][Boot Logo Changer]
read the info there as you can easily brick your phone if it's done wrong.
Remember that param partition acts as an image cache for bootloader and is indeed part of the bootloader partitions.
With that said, please don't share files unless you've tested it yourself first.

----------------------------------------------------------------------------------------------------------------------------------------------

OLDER METHOD:

Original ---> Changed to:

Original---> Changed to:


This blacked out so that it won't show on the black logo background.

Unzip View attachment SM-A405FN-param_mod.tar.zip and put the tar.md5 in AP slot in Odin. Connect phone in download mode and start flash.
--------------------------------------------------------------------------------------------------------------------------------------------------------​

 

[Tony il Capo]

Hi
To flash this do we need to reset/wipe after? I spent already too much time customizing this device, don't wanna do everything all over again

The warning that warns about booloader and asks to press power couldn't also be blackened or even replaced it with something nicer ((maybe text in black "Custom firmware initializing" ))? If I don't press power device continues boot anyway after a few seconds.

Can you give any tips, or any special care when creating/modified bootlogo? Or, if you have time to make more versions it will be appreciated

Many thanks.

 

[pomaxa]

Please do for TWRP

 

[Tony il Capo]

Got no feedback, so I decided to create my own bootlogo and sucessfully flashed it using Odin.
Even put the Magisk logo on it :laugh:

A quick how-to using Windows:

You know the drill, if you manage to damage your device when doing this, it's your own fault!

1. Download the firmware for your device from your preferred server (samfrew updato , select region, version), alternatively jump to the end for faster approach, but you may need knowledge described in next steps anyway

2. Have installed 7zs

3. Right-click the firmware file > 7Zip ZS > Open Archive > then double-click (dc) file that starts "BL.." > again dc param.bin.lz4 > again dc param.bin > extract all files

4. Files to customize are:
booting_warning.jpg
logo.jpg
svb_orange.jpg

Use favorite image editor (Paint works!)
Make sure you keep the default resolution and do not create much bigger files than the originals, a little bit smaller or bigger it's okay, but not too much.

5. Again using 7zs create a tar archive format with the files you edited and the rest you have extracted before, name the archive param.bin (literal, NOT param.bin.tar)
(7Zip ZS > Add to Archive > Archive Format: tar > Archive (name): param.bin)

6. And then again, create another tar file with the param.bin in it (archive name may be anything)

7. Using Odin, load the tar file you created on the previous step to the AP slot, connect the phone in download mode and flash

Alternatively, to save data and time download bootlogo mod from first post, just extract files, edit and repack again using similar manner as described above
(in the end you should have a file with tar extension instead of MD5 because archive does not have MD5 checksum attached, so Odin will not check data integrity)

 

[Sparko612]

I tried to load file but says error binary is invalid

 

[Tony il Capo]

I tried to load file but says error binary is invalid

What are you trying to do? Flashing bootlogo mod from first post or creating your own?

 

[tys0n]

Please do for TWRP

I've been working some more on this "project" and twrp flashable is working. I will upload tomorrow hopefully.
I managed to remove the black warning as well so that we can have full screen custom logos, like this:


There will be two zip's to flash the first time.
One with stock param, but witout the "red warning" and one zip to finally change the logo / svb_orange by unpacking param in device and replace the images inside.
This will be easier, as we from there on only have to replace two images in a zip to get new flashable logo.

 

[pomaxa]

Have already done

 

[tys0n]

Have already done

Guess I was late then
Anyway, I've updated OP with new method, files and instructions.

 

[Tony il Capo]

I managed to remove the black warning as well so that we can have full screen custom logos, like this:
View attachment 4846485 View attachment 4846487

Couldn't we had 'fullscreen custom logos' before?
Why did you choose to leave the message of the "svb_orange"? We all know bootloader is unlocked, message is useless and undesirable since boot continues anyway after a few secs (no need to press power).

Anyway, that's what I've done on mine, replaced it with a nice screen, acting as second (boot)logo.

 

[tys0n]

Couldn't we had 'fullscreen custom logos' before?
Why did you choose to leave the message of the "svb_orange"? We all know bootloader is unlocked, message is useless and undesirable since boot continues anyway after a few secs (no need to press power).

Anyway, that's what I've done on mine, replaced it with a nice screen, acting as second (boot)logo.

That message doesn't really bother me so I just kept it.
We could have used full screen, but it would have looked like this cause the image is still there, just blacked out.

 

[Tony il Capo]

We could have used full screen, but it would have looked like this cause the image is still there, just blacked out.
View attachment 4847521

Yes, of course, I forgot that it just gets overlayed on top of logo image, because my logo is mainly black and booting_warning is black too, it's there but invisible.

 

[Sparko612]

What are you trying to do? Flashing bootlogo mod from first post or creating your own?

Sorry I was trying to flash mod from first post

 

[Bode327]

Thanks

Sent from my SM-A305GT using XDA Labs

 

[fredapied]

Got no feedback, so I decided to create my own bootlogo and sucessfully flashed it using Odin.
Even put the Magisk logo on it :laugh:

A quick how-to using Windows:

You know the drill, if you manage to damage your device when doing this, it's your own fault!

1. Download the firmware for your device from your preferred server (samfrew updato , select region, version), alternatively jump to the end for faster approach, but you may need knowledge described in next steps anyway

2. Have installed 7zs

3. Right-click the firmware file > 7Zip ZS > Open Archive > then double-click (dc) file that starts "BL.." > again dc param.bin.lz4 > again dc param.bin > extract all files

4. Files to customize are:
booting_warning.jpg
logo.jpg
svb_orange.jpg

Use favorite image editor (Paint works!)
Make sure you keep the default resolution and do not create much bigger files than the originals, a little bit smaller or bigger it's okay, but not too much.

5. Again using 7zs create a tar archive format with the files you edited and the rest you have extracted before, name the archive param.bin (literal, NOT param.bin.tar)
(7Zip ZS > Add to Archive > Archive Format: tar > Archive (name): param.bin)

6. And then again, create another tar file with the param.bin in it (archive name may be anything)

7. Using Odin, load the tar file you created on the previous step to the AP slot, connect the phone in download mode and flash

Alternatively, to save data and time download bootlogo mod from first post, just extract files, edit and repack again using similar manner as described above
(in the end you should have a file with tar extension instead of MD5 because archive does not have MD5 checksum attached, so Odin will not check data integrity)

Thank you Bro !!

It works like a charm.
Very happy with this mod

Fred.

 

[fredapied]

i know how to make it work with Odin but i was wondering if with the stock recovery it's possible to sign an update.zip containing this mod....
i tried an old zip signer with no luck ( probably it was with an old Android version).

 

[Val3r10]

OLDER METHOD:

View attachment 4790669 Original ---> Changed to: View attachment 4790670

View attachment 4790672 Original---> Changed to: View attachment 4790673

View attachment 4790671
This blacked out so that it won't show on the black logo background.

Unzip View attachment 4790675 and put the tar.md5 in AP slot in Odin. Connect phone in download mode and start flash.

Hello. I installed this patch last july (release without leaves):
- is that version (no-leaves) still available / usable with ASJ firmware ?
- in general, how could I revert mod to the original ? Flashing full stock firmware doesn't affect bootloader area, it seems

I don't have TWRP so I'm talking about Odin releases
Thanks a lot for your work

 

[Swordfishx86]

[...]

Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?

 

[fredapied]

Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?

Twrp with an update.zip style
Or flash with Odin
Perhaps files and directories are différents...

Envoyé de mon SM-A405FN en utilisant Tapatalk

 

[Swordfishx86]

Perhaps files and directories are différents...

There is no param.bin in the BL-file of A70s firmware ...