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"
{
"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"
}
----------------------------------------------------------------------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------------------------------------------------------------------------------
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.
Please do for TWRP
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)
I tried to load file but says error binary is invalid
Sparko612 said:
I tried to load file but says error binary is invalid
Click to expand...
Click to collapse
What are you trying to do? Flashing bootlogo mod from first post or creating your own?
pomaxa said:
Please do for TWRP
Click to expand...
Click to collapse
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.
Have already done
pomaxa said:
Have already done
Click to expand...
Click to collapse
Guess I was late then
Anyway, I've updated OP with new method, files and instructions.
tys0n said:
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
Click to expand...
Click to collapse
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.
Tony il Capo said:
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.
Click to expand...
Click to collapse
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.
tys0n said:
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
Click to expand...
Click to collapse
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.
Tony il Capo said:
What are you trying to do? Flashing bootlogo mod from first post or creating your own?
Click to expand...
Click to collapse
Sorry I was trying to flash mod from first post
Thanks
Sent from my SM-A305GT using XDA Labs
Tony il Capo said:
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)
Click to expand...
Click to collapse
Thank you Bro !!
It works like a charm.
Very happy with this mod
Fred.
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).
tys0n said:
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.
Click to expand...
Click to collapse
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
tys0n said:
[...]
Click to expand...
Click to collapse
Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?
Swordfishx86 said:
Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?
Click to expand...
Click to collapse
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
fredapied said:
Perhaps files and directories are différents...
Click to expand...
Click to collapse
There is no param.bin in the BL-file of A70s firmware ...
Related
Here are some splash images that can be flashed to the htc evo view. It should work on the flyer but I don't have one to test on.
** Credits go to the original creators of these images. Unfortunately I don't know who they are **
splash-hand.img
{
"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"
}
splash-android.img
splash-androidpissonapple.img
splash-droideatingapple.img
godzson.zip
GODZSON said:
I designed these 2 (View/Flyer) clean and simple splash images today, Feel free to use in custom roms, or personal usage..
Click to expand...
Click to collapse
** Your device must be s-off (nand unlocked) in order to flash/install this image **
Installation instructions:
1. Download nameofsplash.img
2. Reboot your device to bootloader.
3. In a command/terminal prompt enter
Code:
fastboot flash splash1 nameofsplash.img
4. Reboot your device and enjoy your new splash screen.
=================================================
-- Instructions to make your own splash image for flyer/view --
-- For windows --
1. Create an image with the dimensions 1024 height 600 width. Save your image as splash.extension (splash.bmp for example, png works, jpg may but I haven't tested it).
2. Rotate your image 90 degrees counterclockwise (windows image viewer is the easiest/fastest).
3. Download splash.zip and extract to a location of your choice.
4. Open new-splash.txt and edit "splash.png" to reflect your image extension (splash.bmp for example).
5. Save the file as new-splash.bat.
6. Move your image (from step 1) into the directory with the .bat and ffmpeg files.
7. Double click new-splash.bat. You should now have a file in the same directory named splash.img
8. Flash the image via fastboot and enjoy!
** Some Notes **
You will notice two files called pull-480x800.txt and pull-1024x600.txt.
These two files are essentially the same except for the size dimensions.
You will want to save these files as .bat (just like in step 5) after editing the size dimensions and image output extension (bmp instead of png) inside the text file.
After pulling you will have a file named splash.extension in the same directory.
The files use the name splash.extension (splash.img, splash.png, etc.) when pulling/creating
When creating a splash.img, the .bat file will look for an image named splash.extension (where extension is what you specified in step 4)
When pulling an image from splash.img, the .bat file will look for splash.img, rename it to splash-orig.img, and output the image according to the size dimensions and extension specified.
I hope this little writeup was easy to follow. If not please feel free to ask any questions!
Heh.... Cool! Just wish I had a View right now....
Is it works with flyer 3G too???
rrk said:
Is it works with flyer 3G too???
Click to expand...
Click to collapse
The device doesn't matter - the fact that the Flyer is displaying "evo view" is the problem.
ikingblack said:
The device doesn't matter - the fact that the Flyer is displaying "evo view" is the problem.
Click to expand...
Click to collapse
I can make the .img files if you provide the image you want. I'm not the best graphic artist but I can make the splash.img with no effort.
I stated evo view because that's the device I have and test on.
Can you make this an .img file for me?
MagicalSandwich said:
Can you make this an .img file for me?
Click to expand...
Click to collapse
See op for link.
Can you make this into splash for me
Can you make these into splash for me? would be much appretiated. are you using photoshop or what to create the .img file?
EDIT:
FYI the splash-android.img file won't download in your link
Bubbled said:
FYI the splash-android.img file won't download in your link
Click to expand...
Click to collapse
I just downloaded it now from the link. Works fine.
Edit: running behind in everything. I will try to have them up before this weekend is up. Sorry
Bubbled said:
Can you make these into splash for me? would be much appretiated. are you using photoshop or what to create the .img file?
EDIT:
FYI the splash-android.img file won't download in your link
Click to expand...
Click to collapse
OP updated. Enjoy!
lovethyEVO said:
I can make the .img files if you provide the image you want.
Click to expand...
Click to collapse
can you replace the HTC EVO 4G with HTC Flyer in the first image? I would like to install on my flyer. Thanks in advance
ovigt71 said:
can you replace the HTC EVO 4G with HTC Flyer in the first image? I would like to install on my flyer. Thanks in advance
Click to expand...
Click to collapse
I'm not the best graphic artist. If you can find someone who is a photoshop pro to edit the image I can make the splash. Sorry .
Can I ask how you made these? What tool did you use? What size image?
I've been using nbimg.exe to make these for all of my devices, but everything I make for my Flyer looks completely distorted when I flash. I've successfully flashed all of the .imgs you've created, so I know it's not my device.
here's a good tutorial -
Edit: link broke
You can also use any of the splash screens or boot animations from the Nook Color and there are a bundle of them out there if you do a search. The Nook color and HTC flyer /View screen are the same size.
I will try to have a write up by the end of the week of how I make the splashs as well as the files I used for anybody who wants to try their hand at making splash screens for this device or any other device.
lovethyEVO said:
I will try to have a write up by the end of the week of how I make the splashs as well as the files I used for anybody who wants to try their hand at making splash screens for this device or any other device.
Click to expand...
Click to collapse
Cool.
Also, I have a question. The splash screen is the HTC screen right? Once the quietly brilliant comes on it is just boot animation.zip correct?
So those who use fast boot this won't work.
ikingblack said:
Cool.
Also, I have a question. The splash screen is the HTC screen right? Once the quietly brilliant comes on it is just boot animation.zip correct?
So those who use fast boot this won't work.
Click to expand...
Click to collapse
You are correct. Whenever you shutdown the tablet completely the splash screen is the first image you see when it powers on. For people like me it's nice to change it since I don't use fastboot in the event I need to get into recovery or bootloader.
lovethyEVO said:
You are correct. Whenever you shutdown the tablet completely the splash screen is the first image you see when it powers on. For people like me it's nice to change it since I don't use fastboot in the event I need to get into recovery or bootloader.
Click to expand...
Click to collapse
Once I get a really good splash I will stop using fast boot then.
lovethyEVO said:
I will try to have a write up by the end of the week of how I make the splashs as well as the files I used for anybody who wants to try their hand at making splash screens for this device or any other device.
Click to expand...
Click to collapse
Can you tell me if this is the method you're using..?
Create image 600 pixels wide and 1024 high.
Save it as a 24 bit bmp file called splash1 (any name works)
Put the bmp in the nbimg tool directory.
Open cmd and cd to that directory then run command:
Code:
nbimg -F splash1.bmp -w 600 -h 1024
Take the output file and change the extension to .img
Make sure device is in fastboot and run command:
Code:
fastboot flash splash1 C:\nbimg\splash1.img
Thanks in advance.
While flashing a rom, sometimes we get a "status 7 error". This Guide helps you to get out from it, and flash your favourite rom. Let's get started.
Move to META_INF > COM > GOOGLE > ANDROID by extracting the rom.
Here you will find a file "updater-script". Rename this file as updater-script.doc (microsoft word format) or use notepad++ (preferably)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
Double click to open it( microsoft word preferred)
delete text, starting from "assert ....... till the semicolon ( of the last getprop command).
(See the image in the attached file for carefully deleting the lines. Click this link.)
Save the file now.
Again rename the file, and delete the .doc extention
Now go back and zip these files again. and you will get a zipped rom.
And the status 7 error has now been removed!
---
Siddharth121 said:
hey!
while flashing roms, many times we get a "status 7 error". while searching in many threads, we do not get how to resolve it. i will tell you each and every thing step by step
so i made a NOOB FRIENDLY WAY TO RESOLVE STATUS 7 ERROR
make sure that the rom you have downloaded matches your phone model, if you flashed some other rom, you may hard brick your device.
1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.
and the status 7 error has now been removed!:good:
happy flashing :victory::victory:
at last, as you read in every post, i am not responsible for any bricked device.
Click to expand...
Click to collapse
have you already try to cook rom using android kitchen?
I saw android kitchen. But it didn't supported my p3100. Ive rooted my htc day before yesterday. I'll try that surely :thumbup:
But why?..
Sent from my HTC One X+ using xda premium
Siddharth121 said:
I saw android kitchen. But it didn't supported my p3100. Ive rooted my htc day before yesterday. I'll try that surely :thumbup:
But why?..
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
because every time i use that to cook rom for my samsung galaxy gio the installation is aborted and error status 7 when i am flashing it
Do the above mentioned, actually the recovery checjs for the device version and all before flashing.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Do the above mentioned, actually the recovery checjs for the device version and all before flashing.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
yeah maybe that is the main problem dude it is really hard to work with kitchen
Yepp. It is, but it reduces your harwork.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Yepp. It is, but it reduces your harwork.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
maybe in deodexing a stock rom should the first one that really helps
flash the zip ,go to advanced option "show logs"
delete the lines which shows error like no file or directory in updater script
simple way
percy_g2 said:
flash the zip ,go to advanced option "show logs"
delete the lines which shows error like no file or directory in updater script
simple way
Click to expand...
Click to collapse
is that method is tested and proven?
badagila said:
is that method is tested and proven?
Click to expand...
Click to collapse
Yeah
Sent from my LT22i using Tapatalk 2
percy_g2 said:
Yeah
Sent from my LT22i using Tapatalk 2
Click to expand...
Click to collapse
have you try to cook rom using dsixda kitchen?
so the advice is to remove the device check?
How about a tip on how to use the proper device id or name?
So where do I look in the device to use the name that works?
That would be better imho.
I did try to use the values in the build.prop file from the running device, but that did not work eiter.
Now i'm getting status 4 error
i was getting status 7 error. Searched the forum and found this thread. I followed the directions to take off the lines from updated script files, but now i'm getting status 4 update. Can anyone recommend me how i can take care of status 4 error?
I can't flash any custom rom from recovery. Please help.
nulfinis said:
Hi,
I still get status 7 after using this guide.
any advice?
Click to expand...
Click to collapse
My Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Error 7
xsenman said:
My Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
I have had Error 7 due to delete many apps and unnecessary files in the rom. I resolved my problem flashing again the rom (previous rom) that I was removing apps and files. Then, I flash the new rom and problem resolved. Regards.
P.D. I have FXP238 CM10 installed and running ok.
Click to expand...
Click to collapse
Siddharth121 said:
1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.
Click to expand...
Click to collapse
hi, i follow all the instruction, but im still getting error, this time its "status 6"
wrong thread lol
thx for good work
this guide shows how to change the boot logo, not the boot animation
boot logo is the logo that is shown before the animation
Tools required:
1. LogoBuilder --- http://d-h.st/k96
2. Stock logo.bin --- Get the file from your device (/dev/logo)
3. Required boot logo files, in png format
4. Common sense duh!!!
once you have the required files, extract LogoBuilder
Rename the file from your device (logo) to logo.bin and proceed to the next post
1. Open LogoBuilder.exe
{
"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"
}
2. Click Create New Project
3. Select the logo.bin file you extracted from the device
4. Make a new folder for the project, any name will do
5. Select the folder and click on OK
You will see a progress bar running down. After finishing, you will get a whole bunch of images in the above selected folder
1. Open the folder containing all the images
2. Make a note of the sizes of img1.png and img39.png
The desired boot logo file must be a png file having resolution same as that of img1.png
3. Delete only img1.png and img39.png
4. Rename the desired boot logo file to img1.png and paste it in the folder
5. Make a copy of img1.png and rename it to img39.png
6. Click on Make button
In the selected folder, you'll get a file named update.zip
Flash that file using cwm and enjoy the new boot logo
Credits: @ankadnikov
Google search which got me to an unknown site instead of XDA
Nice one! I was thinking to set canvas 4 boot logo it looks awesome thanks for the guide.
unable to copy /dev/logo
hey i'm unable to copy /dev/logo file to my sdcard. it says operation unsuccessful when i tried through root browser/es explorer. even tried to copy via terminal too. it starts copying and goes on and goes on. when i check the size of copying size it is in GBs and yet it is copying and size is gradually increasing so i've to force stop it. Help pls.
SaketJoshi said:
1. Open LogoBuilder.exe
2. Click Create New Project
3. Select the logo.bin file you extracted from the device
4. Make a new folder for the project, any name will do
5. Select the folder and click on OK
You will see a progress bar running down. After finishing, you will get a whole bunch of images in the above selected folder
Click to expand...
Click to collapse
SaketJoshi said:
1. Open the folder containing all the images
2. Make a note of the sizes of img1.png and img39.png
The desired boot logo file must be a png file having resolution same as that of img1.png
3. Delete only img1.png and img39.png
4. Rename the desired boot logo file to img1.png and paste it in the folder
5. Make a copy of img1.png and rename it to img39.png
6. Click on Make button
Click to expand...
Click to collapse
The main developers is AnkadNikov , who actually developed this cool software. I request everyone who are making additional guides for LOGO BUILDER , at least give necessary credit to the main developer @ankadnikov
I also request @SaketJoshi to press thanks in following thread
Thanks @ankadnikov for your development.
http://forum.xda-developers.com/showthread.php?t=1953726
cmahendra said:
The main developers is AnkadNikov , who actually developed this cool software. I request everyone who are making additional guides for LOGO BUILDER , at least give necessary credit to the main developer @ankadnikov
I also request @SaketJoshi to press thanks in following thread
Thanks @ankadnikov for your development.
http://forum.xda-developers.com/showthread.php?t=1953726
Click to expand...
Click to collapse
thanks for posting that. i was directed to a different site rather than xda, so didn't know who the dev is
added the credits
SaketJoshi said:
thanks for posting that. i was directed to a different site rather than xda, so didn't know who the dev is
added the credits
Click to expand...
Click to collapse
When making guide, everyone should be careful, at least to post SOURCE of information of software you are suggesting. You mentioned it as "different site", the link to that site was also missing. Wherever credit is due, is due. I hope you will take care next time.
PS: Be kind to main developer @ankadnikov and post your credit on 1st post, not fourth post.
what is the size of logo.bin? in my Alcatel SPOP 4030A is like 300mb o.o
Thanks man
Messed something up
Hello, I know this thread is about a year old, but I hope I can get some help here. I was trying to change the logo on my MTK device and I did not pay attention to the part where you were supposed to flash the finalized file with CWM, I instead just extracted the logo.bin file from the Update.zip and then just pushed it to /dev/ but before doing that I rename the original file to logo.nn Now my device won't go pass the original boot logo. I can get to adb but only to sideload. I've tried the update.zip generated from the LogoBuilder_v1.4 and still cannot boot up. I do not have the image for this device to just flash it and restore everything to factory. I have tried to clear cache and factory defaults thru stock recovery but it still doesn't boot up.
Any ideas?
Thank you!
blackbeard said:
In the selected folder, you'll get a file named update.zip
Flash that file using cwm and enjoy the new boot logo
Credits: @ankadnikov
Google search which got me to an unknown site instead of XDA
Click to expand...
Click to collapse
How I can change bootanimation inside repack folder logo, I already change the image inside there as default image (see picture number 1) with my custom image (see picture number 2) but after the folder is rebuild to logo.bin an flash it, nothing change except img1.png and img2.png.
I hope somebody can solved this issue
How to modify Samsung Galaxy S Advance GT-I9070 bootlogo
{
"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"
}
***Warning***
I'm not responsible for any brick/damage to your phone (e.g. if you want to manually flash modified file and by mistake you flash it on another partition and not in PARAM's)
The original method for this mod goes from here, I have searched and found block and its size where is present bootlogo on GT-I9070, which is different from GT-I8190.
Let's start!
First, download a HEX editor (for this tutorial we'll use HxD)
Make your own logo.jpg using any tool that you want, following these parameters: 480x800 pixels and not bigger than 65.246 bytes
Download attached stock_param and extract it where you want. We will use always this param, others may have the bootlogo in different offsets
Open downloaded original param in HxD and set octal value
Now select Edit>Select block: Start 660000 - End 1057335
Go to File>New (set again octal value as the first screenshot!), then select Edit>Insert bytes and put 177336 as number
Now we have an empty block with the same lenght than original block in param.lfs
Open your created logo.jpg with HxD, right mouse button click and first choose "Select all" then choose "Copy"
Go back to the empty file that we made, return at the start of code (offset 00000000) then right mouse button click and choose "Paste (Overwrite)"
Example of the new start/end after overwrite
Now after overwrite click right mouse button, choose "Select all" then "Copy"
Return to param.lfs, click right mouse button, choose "Paste (Overwrite)" and finally save the file
Example of old logo's block start/end
Example of new logo's block start/end
To flash the new param.lfs look in 2nd post
Flash modified param.lfs
To flash modified param you have some different ways:
Use my Param Flasher (best and safest way, you need only device drivers)
Download empty_param, put modified param inside it and flash with recovery
Manually way (can be dangerous if you're not experienced, so I'll not write how to do)
To restore original param:
Use Param Flasher choosing "Restore stock param.lfs"
Or download stock_param and flash with recovery
If something goes wrong with modified param.lfs, bootlogo can be ruined (you see only pixels, coloured lines...) or after power on vibration you get just a black screen, you can have one of these two scenarios:
ROM doesn't boot but device boots itself in recovery when you press power button: use Param Flasher to restore stock param or flash stock_param with recovery
ROM and recovery don't boot: Use Param Flasher in "Odin Mode" and follow the instructions.
where can i find d stock bootlogo image in my GSA ??? i mean in which directory
or else can anyone provide me the .jpg formate of bootlogo image of GSA
psycho_boy52 said:
where can i find d stock bootlogo image in my GSA ??? i mean in which directory
or else can anyone provide me the .jpg formate of bootlogo image of GSA
Click to expand...
Click to collapse
See the first three steps and copy that block of code in a new file saving as jpg
Inviato dal mio GT-I9070
bro having problm with flashing my own made boot logo!!!!...
when i flash it...... it fhashes successfully bt the jellybean logo wont appear n the black background gets hezy n noisy!!...
plz tell me how to fix it....
i hv uploaded d hex editor img of dat custom logo dat i have mode!!!....
plz chk it out n tell me where is d fault
psycho_boy52 said:
bro having problm with flashing my own made boot logo!!!!...
when i flash it...... it fhashes successfully bt the jellybean logo wont appear n the black background gets hezy n noisy!!...
plz tell me how to fix it....
i hv uploaded d hex editor img of dat custom logo dat i have mode!!!....
plz chk it out n tell me where is d fault
Click to expand...
Click to collapse
The end of image block in param.lfs is not correct
Inviato dal mio GT-I9070
OH BOY!!! Thanks i needdeeedd itt!!! :3
Tesla-MADAL93 said:
The end of image block in param.lfs is not correct
Inviato dal mio GT-I9070
Click to expand...
Click to collapse
ohkey!!! so how to fix it :silly:
psycho_boy52 said:
ohkey!!! so how to fix it :silly:
Click to expand...
Click to collapse
Just follow again guide without distraction
Tesla-MADAL93 said:
The end of image block in param.lfs is not correct
Inviato dal mio GT-I9070
Click to expand...
Click to collapse
Tesla-MADAL93 said:
Just follow again guide without distraction
Click to expand...
Click to collapse
Will I get d same value in d end of the img blck of param.lfs???
N in with editor should I edit d image which came out frm the param.lfs n should I hv to save it *.jpg format or in different format
I thng bcz of the image format the whole value got chngd....
dr9103 said:
Will I get d same value in d end of the img blck of param.lfs???
N in with editor should I edit d image which came out frm the param.lfs n should I hv to save it *.jpg format or in different format
I thng bcz of the image format the whole value got chngd....
Click to expand...
Click to collapse
Only if you create an image with the exact byte size than original, in other cases first you need to create an empty block with the same lenght as image block in param.lfs, like specified on guide. Use only jpg and not other formats, you can use GIMP, IrfanView, Photoshop to create them... To get original Samsung logo just select image block like on first part of the guide, copy it and paste on a new file saving as a jpg file, then to try this mod before creating your own image/logo/signature I suggest to invert the image (black/white->white/black) and finally follow the whole guide
Inviato dal mio GT-I9070
AntaresOne said:
Only if you create an image with the exact byte size than original, in other cases first you need to create an empty block with the same lenght as image block in param.lfs, like specified on guide. Use only jpg and not other formats, you can use GIMP, IrfanView, Photoshop to create them... To get original Samsung logo just select image block like on first part of the guide, copy it and paste on a new file saving as a jpg file, then to try this mod before creating your own image/logo/signature I suggest to invert the image (black/white->white/black) and finally follow the whole guide
Inviato dal mio GT-I9070
Click to expand...
Click to collapse
sorry, i used this guide, but i wasn't able to to install my custom "splash screen", afther flashing it, my phone only boot on recovery. so. i keep the guide ( odin set on the downloaded folder, don't work , so i installed it from another web site). i keep the guide, but phone continue to start in recovery.....(i tried to reinstall the original param.lfs, either with odin, either with flash zip,as written in the guide)
, but nothing....
so i reflash the cyanogen mode 11 that i had in my sdcard, , (i had done a buck up with titanium before), but is a hassle to reinstalll all app and data.... but , here is the miracle, i just flash the cyanogen 11 that i have flashed several time(i risked several time in the past to brick my phone). and my phone was as before all, i have all my app, all my setting, all my data, even if i don't have restore my buck up with titanium!
ommitting the flash of custom splash screen, (may be you could help me, to found what i wrong), could someone explain me how this could possible?!(it is a miracle, because when i reinstall cyanogen, time ago, i had to use titanium to restore my buck up)
enricomarc said:
sorry, i used this guide, but i wasn't able to to install my custom "splash screen", afther flashing it, my phone only boot on recovery. so. i keep the guide ( odin set on the downloaded folder, don't work , so i installed it from another web site). i keep the guide, but phone continue to start in recovery.....(i tried to reinstall the original param.lfs, either with odin, either with flash zip,as written in the guide)
, but nothing....
so i reflash the cyanogen mode 11 that i had in my sdcard, , (i had done a buck up with titanium before), but is a hassle to reinstalll all app and data.... but , here is the miracle, i just flash the cyanogen 11 that i have flashed several time(i risked several time in the past to brick my phone). and my phone was as before all, i have all my app, all my setting, all my data, even if i don't have restore my buck up with titanium!
ommitting the flash of custom splash screen, (may be you could help me, to found what i wrong), could someone explain me how this could possible?!(it is a miracle, because when i reinstall cyanogen, time ago, i had to use titanium to restore my buck up)
Click to expand...
Click to collapse
Because you didn't formatted /data partition, so you have all your apps, settings, data... The procedure for custom splash image is this only and works 100/100 times if you do all correctly. You have to check your custom image size (shold be as the guide) before modifying param.lfs
AntaresOne said:
Because you didn't formatted /data partition, so you have all your apps, settings, data... The procedure for custom splash image is this only and works 100/100 times if you do all correctly. You have to check your custom image size (shold be as the guide) before modifying param.lfs
Click to expand...
Click to collapse
i tried again, just now,but nothing , phone boot on recovery, and i have to reflesh the rom
for images , i chose the image on the 2 post in the first page, (i modified it ) it is 480 x800, and less than 65k bite, i use guide, but nothing,
the image coul be right, isn'it? i only write my name above "samsung galaxy...."
could you help me please ?
@enricomarc
Instead of reflashing stock with Odin everytime, extract param.lfs.md5 from 'Param Flasher' in 2nd post of this thread and flash with Odin as PDA... Read again the guide, for sure you made something wrong have you created empty block with the same size of the splashscreen's block in param.lfs? Here you paste your custom image's code by overwriting option, then select all and copy, paste into param.lfs overwriting original logo's block.
Always use the param that I have attached, other params may have splashscreen in different offsets.
Important thing: check always that you are using octal value
Inviato dal mio GT-I9505
AntaresOne said:
@enricomarc
Instead of reflashing stock with Odin everytime, extract param.lfs.md5 from 'Param Flasher' in 2nd post of this thread and flash with Odin as PDA... Read again the guide, for sure you made something wrong have you created empty block with the same size of the splashscreen's block in param.lfs? Here you paste your custom image's code by overwriting option, then select all and copy, paste into param.lfs overwriting original logo's block.
Always use the param that I have attached, other params may have splashscreen in different offsets.
Important thing: check always that you are using octal value
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
I'm sure i used octal value ; i tried to use Odin And reflash param.lfs original file, but Phone continue to start only on Recovery, so i have to reflash rom. I'm using cyanogenmod 11, based on Android 4.4.2 i'm sure i' m Not wrong, but i will try again
enricomarc said:
I'm sure i used octal value ; i tried to use Odin And reflash param.lfs original file, but Phone continue to start only on Recovery, so i have to reflash rom. I'm using cyanogenmod 11, based on Android 4.4.2 i'm sure i' m Not wrong, but i will try again
Click to expand...
Click to collapse
Hmm this is strange, because when I had S Advance and I created this guide, stock_param.zip for recovery and Param Flasher (Odin mode too) I made them perfectly working... I'm still using them for my friends
P.s. I pushed Thanks by mistake. :silly:
Inviato dal mio GT-I9505
I had black screen and no logo.. Could this have happened because I used png files instead of jpg?
Sent from Italy using Tapatalk
Toni5830 said:
I had black screen and no logo.. Could this have happened because I used png files instead of jpg?
Sent from Italy using Tapatalk
Click to expand...
Click to collapse
Sure, you need to create your logo as JPG
Without wasting anytime, I would straight go to the main topic.
P.S - Boot Logo NOT to be confused with Boot Animation.
P.P.S - This is for Samsung Devices only.
What is param.lfs?
Well, it is one of the files found in the stock firmware (tar.md5) file. Looks like it contains various images used by bootloader or kernel. (It may contain other functionalities also, but its what I can tell you because it is what I have understood by exploring it).
Where can I find param.lfs?
In stock firmware, just browse its contents using WinRAR or 7zip etc. It will look like :
{
"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"
}
What is there inside param.lfs?
There are many jpg files which is used by bootloader. (Once you go through them, you will find relevance). It will look like :
How is param.lfs related to boot logo?
If you explore param.lfs, you will find a file called logo.jpg. Thats it, the BOOT LOGO.
Is Samsung showing its 'class' here again?
Well, in various other phones, the boot logo is present in the root folder of ramdisk, however, in this case, boot logo is compressed inside param in respective partition. Changing boot logo in other devices seems pretty easy, but in this case, the param block must be decompressed, then make necessary changes and then recompress it back.
But the good thing is that, images are present in simple jpg format in our case, but in others, they are in .rle format, which is needed to be converted to jpg for modification. It is obviously possible through certain tools.
About the boot logo changing utility, the main job was done by the OP of this thread. My job was to identify correct partition and make necessary changes in the script.
Installation :
1. Flash it using CWM v6.
2. Now reboot to recovery (option in Advanced Menu).
3. Once you reboot to recovery again, now perform normal reboot.
The zip file has stock image, so if you modify, mod that very image. The image must be of 240x320 resolution and of 72DPI. Also the file name must be logo.jpg
Download : Here
In case you mess up, you should be able to use button combos.
Will this work with SMP -900 Samsung Galaxy Note pro 12.2?
corphish said:
Without wasting anytime, I would straight go to the main topic.
P.S - Boot Logo NOT to be confused with Boot Animation.
P.P.S - This is for Samsung Devices only.
What is param.lfs?
Well, it is one of the files found in the stock firmware (tar.md5) file. Looks like it contains various images used by bootloader or kernel. (It may contain other functionalities also, but its what I can tell you because it is what I have understood by exploring it).
Where can I find param.lfs?
In stock firmware, just browse its contents using WinRAR or 7zip etc. It will look like :
What is there inside param.lfs?
There are many jpg files which is used by bootloader. (Once you go through them, you will find relevance). It will look like :
How is param.lfs related to boot logo?
If you explore param.lfs, you will find a file called logo.jpg. Thats it, the BOOT LOGO.
Is Samsung showing its 'class' here again?
Well, in various other phones, the boot logo is present in the root folder of ramdisk, however, in this case, boot logo is compressed inside param in respective partition. Changing boot logo in other devices seems pretty easy, but in this case, the param block must be decompressed, then make necessary changes and then recompress it back.
But the good thing is that, images are present in simple jpg format in our case, but in others, they are in .rle format, which is needed to be converted to jpg for modification. It is obviously possible through certain tools.
About the boot logo changing utility, the main job was done by the OP of this thread. My job was to identify correct partition and make necessary changes in the script.
Installation :
1. Flash it using CWM v6.
2. Now reboot to recovery (option in Advanced Menu).
3. Once you reboot to recovery again, now perform normal reboot.
The zip file has stock image, so if you modify, mod that very image. The image must be of 240x320 resolution and of 72DPI. Also the file name must be logo.jpg
Download : Here
In case you mess up, you should be able to use button combos.
Click to expand...
Click to collapse
Will this work with Samsung galaxy note pro 12.2 ?
corphish said:
Without wasting anytime, I would straight go to the main topic.
P.S - Boot Logo NOT to be confused with Boot Animation.
P.P.S - This is for Samsung Devices only.
What is param.lfs?
Well, it is one of the files found in the stock firmware (tar.md5) file. Looks like it contains various images used by bootloader or kernel. (It may contain other functionalities also, but its what I can tell you because it is what I have understood by exploring it).
Where can I find param.lfs?
In stock firmware, just browse its contents using WinRAR or 7zip etc. It will look like :
What is there inside param.lfs?
There are many jpg files which is used by bootloader. (Once you go through them, you will find relevance). It will look like :
How is param.lfs related to boot logo?
If you explore param.lfs, you will find a file called logo.jpg. Thats it, the BOOT LOGO.
Is Samsung showing its 'class' here again?
Well, in various other phones, the boot logo is present in the root folder of ramdisk, however, in this case, boot logo is compressed inside param in respective partition. Changing boot logo in other devices seems pretty easy, but in this case, the param block must be decompressed, then make necessary changes and then recompress it back.
But the good thing is that, images are present in simple jpg format in our case, but in others, they are in .rle format, which is needed to be converted to jpg for modification. It is obviously possible through certain tools.
About the boot logo changing utility, the main job was done by the OP of this thread. My job was to identify correct partition and make necessary changes in the script.
Installation :
1. Flash it using CWM v6.
2. Now reboot to recovery (option in Advanced Menu).
3. Once you reboot to recovery again, now perform normal reboot.
The zip file has stock image, so if you modify, mod that very image. The image must be of 240x320 resolution and of 72DPI. Also the file name must be logo.jpg
Download : Here
In case you mess up, you should be able to use button combos.
Click to expand...
Click to collapse
Thanks for the help it did really worked on my samsung Galaxy Star Duos. :laugh::laugh::good:
But as I'm new to these forum so I don't know how to donate. can suggest me how to dontate so that I can donate you .
May I use this zip for my experiment on S5 Snapdragon and S4
Can't work on s5 snapdragon,I can't find any .ifs file in the stock firmware
Sorry for my bad English.
cwyj said:
Can't work on s5 snapdragon,I can't find any .ifs file in the stock firmware
Sorry for my bad English.
Click to expand...
Click to collapse
Snapdragon use splash.img which is easiest to edit than others ???