[BOOTLOGO][GUIDE][Param.lfs] Custom bootlogo for Galaxy Ace 2 - Galaxy Ace II Android Development

Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this guide.
Well, let's cut to the chase. Following method was inspired by this guide.
Credit goes to @tys0n for original guide.
Programs/scripts needed for this method:
param editor
Python interpretator (2.7.x)
Any graphical editor
Choose graphical editor by yourself as editiing picture won't be described here.
1) Create image image_new.jpg with resolution of 480x800 pixels and size not bigger than 64673 bytes.
2) Take image that you want to replace from /mnt/.lfs (logo.jpg for example, which is bootlogo) and rename it to image_orig.jpg .
Although using this method any picture in param.lfs can be replaced (but with not bigger size than original ones), logo.jpg is only was tested by author.
3) Then dd your param.lfs:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/param.lfs bs=512000
4) create any empty folder (on PC), put here param_editor.py, param.lfs, image_orig.jpg and image_new.jpg
5) run param_editor.py. If everything was done successfully, in the same folder param_mod.lfs will appear, otherwise message that describe why it has failed will be shown.
Okay, lets to test param_mod.lfs. Of course, you can flash and reboot once it done, but there's a simple method(without having to wait until bootlogo appears... or doesn't) to check whether param.lfs is correct:
1) unmount /mnt/.lfs:
Code:
umount /mnt/.lfs
2) flash param_mod.lfs
Will be careful with typing following command. DON'T type wrong number of partition, otherwise your phone probably will be bricked. Better if you just copy/paste this line.
Code:
dd if=/sdcard/param_mod.lfs of=/dev/block/mmcblk0p1 bs=512000
3) now mount it again:
Code:
mount -t j4fs /dev/block/mmcblk0p1 /mnt/.lfs
4) if you can see your custom bootlogo instead of stock one then everything is ok. Now can reboot and have fun
5) how to restore original param.lfs? Flash param.lfs, dd'd in step 3 ("3) Then dd your param.lfs:")
ToDo: despite of that I have successfully replaced bootlogo, one thing I wanted to check is how to repair the phone in case if something went wrong. For some reason I was not able to flash neither param.tar.md5 nor param.tar . I had to flash three-file stock 4.1.2 to restore it. I would be glad if anyone will provide flashable param.tar.md5 to avoid flashing stock for those who have failed to change bootlogo.
Okay, lets see what bootlogo can be done(custom param.lfs attached below):
{
"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"
}
Why exactly this bull***t (or whatever you can think)? Answer is that everything that I've done (including this guide) is just for fun, and it's first idea that came to my mind. Have fun

Chrono . I was trying do this tutorial. But recently I had a lot of work . Many Thanks , you spared me the time : D

Does not work here... Don't know what went wrong...
Tested logo_nfc.jpg and also logo.jpg
Files are as instucted in one folder...
There is no log or mod output... I got only this (with CMD and param_editor.py)..
Code:
opened param.lfs
opened ./image_orig.jpg
opened ./image_new.jpg
With normal double klick on *.py the cmd window closes to fast to see anything....
Just for test I tried to use original logo.jpg as image_orig.jpg AND image_new.jpg... But I got the same "output" and no mod file nor log...
I Installed Python 3.4.3 from webseite... Is this correct?
EDIT
Installed now Python 2.7.9 - and now param_mod.lfs was created! - Looks like 3.4.3 does not work...

fluffi444 said:
I Installed Python 3.4.3 from webseite... Is this correct?
EDIT
Installed now Python 2.7.9 - and now param_mod.lfs was created! - Looks like 3.4.3 does not work...
Click to expand...
Click to collapse
It should have been to work... probably I missed something as it should not exit without prompt.

ChronoMonochrome said:
It should have been to work... probably I missed something as it should not exit without prompt.
Click to expand...
Click to collapse
Yeb - it's working also with logo_nfc.jpg.
As I said I needed to used Python 2.7.9...
For those with 8160P - It's just a test with "powered by android" logo..
EDIT
And as the logo_nfc.jpg is a bit bigger (65194 bytes) I had to modify the py-script according to this - But as I said it works.
So its not limited to exactly 64673 bytes - But for sure its the best to stay with the same or below original size!
EDIT2
Added "powered by cyanogenmod"

bro i need helpppppppppp

ask
how to use/apply it ??

mavis2032 said:
how to use/apply it ??
Click to expand...
Click to collapse
Omg, for whom Chrono wrote instruction? Just read them, it's so easy...

Custom boot logo for codina I made probably no one wants
thank for @dugeriss for wallpaper
flash from recovery

someone can help me with a samsung chat.? model GT-B5330L, it have the same problem; logo jpg draw failed

really great guide, transformed my old ace.

how to see image in param.lfs?

Related

Nexus one bootscreen for Tattoo

Hi all,
Before you say something I just "ported" a boot screen from Nexus One to Tattoo (this included resizing the picture to our screen res). Here it is:
Nexus One Bootscreen for HTC Tattoo
Here is how you backup your old boot screens and how you set up the new one to be used (u must be root and I also think that Android 2.1 has a different location for these files, but I have only 1.6. If someone know how to do this on 2.1 tell me how and I will update my post!):
1. Unpack the zip file (a new folder named 'boot' should be created)
2.
Code:
adb shell
# cd /system/media/bootscreen
# mkdir /sdcard/bootscreen_backup
# cp /system/media/bootscreen/* /sdcard/bootscreen_backup
# rm *
# exit
3. Now perform
Code:
adb push pathtobootfolder\boot /system/media/bootscreen
That's it. If you're tired of the Nexus Onbe Bootscreen and you want the old one, do:
1. adb shell
Code:
rm /system/media/bootscreen/*
cp /sdcard/bootscreen_backup/* /system/media/bootscreen
Finito!
Have fun!
/Edit1: I have set Audio=0 in the xml-config because I'm tired of the boot sound...
/Edit2: Changed screenX to 0, thanks to coolbits for this
/Edit3: For those guys having problems understanding what to do - look at this post
Thanks for this
Also change:
screenX="0"
to not get empty first 40 pixels of the screen
Working
Good Work, it's all good on my Tattoo
to have this in my tattoo, it has to be rooted?
djhancks said:
to have this in my tattoo, it has to be rooted?
Click to expand...
Click to collapse
Yes! Root is required.
How to do this in Android 2.1? There is no /system/media/bootscreen folder.
aam.. because i'm a newbie here where do i have to unpack those files?
and where should i write those commands?
djhancks said:
aam.. because i'm a newbie here where do i have to unpack those files?
Click to expand...
Click to collapse
My dear fellow Tattoo user, you can unpack the zip file wherever you like, eg. Desktop.
djhancks said:
and where should i write those commands?
Click to expand...
Click to collapse
First, you need to have working connection from PC to your phone trough ADB. Those commands you must type in Terminal i.e. Command Line, like this (this is Terminal in Ubuntu, don't be confused - menu is localized in my native language):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks a lot m8
i think you should edit your first post and add this for all us newbies to understand
thanks again
dejandekic said:
My dear fellow Tattoo user, you can unpack the zip file wherever you like, eg. Desktop.
First, you need to have working connection from PC to your phone trough ADB. Those commands you must type in Terminal i.e. Command Line, like this (this is Terminal in Ubuntu, don't be confused - menu is localized in my native language):
Click to expand...
Click to collapse
Nice explanation
dejandekic said:
Yes! Root is required.
How to do this in Android 2.1? There is no /system/media/bootscreen folder.
Click to expand...
Click to collapse
Sorry, I don't have Eclair Tattoo build installed (will flash it when FM Radio and Camera are working). I have updated my 1st post with requirements and restrictions...
those commands work on windows cmd ???
sure they do, but you have to be in the same folder with adb.exe and type adb.exe instead of adb
NForce25 said:
sure they do, but you have to be in the same folder with adb.exe and type adb.exe instead of adb
Click to expand...
Click to collapse
thanks m8, i'm a lil' newbie for all that stuff, but thanks to this guide i can manage
to do this
nice bootscreen, biggest win is turning that F***ing sound off
havok123 said:
nice bootscreen, biggest win is turning that F***ing sound off
Click to expand...
Click to collapse
i like this sound
What am I doing wrong?
I've done a similar bootscreen, but I kept the proportions on the logo and it's oriented the right way (top left to bottom right: blue, red, yellow & green).
Also, I kept the green little buddy and its sound but I removed the annoying sound when the htc-logo should appear.
I attached the zip-file which contains everything (boot.gif, boot1.gif, boot2.gif, boot_bg.gif, boot_animation.xml and boot.mp3)
sheik_yerbouti said:
View attachment 319318
What am I doing wrong?
Click to expand...
Click to collapse
Did you remount RW?
worked for me great
same error by mine,
someone tell me how to "Did you remount RW?"
Greets
"adb remount"
in terminal...

I feel like I'm taking crazy pills, please help a non n00b here unroot

Pre-question summary: I had an eris for about a year. Trackball took a ****, got a refurb at verizon yesterday and like a big idiot didn't even check to make sure the microphone worked before rooting? (how dumb am I?)
so here I am, on a rooted refurb with just the "eris21official-root.zip" running (not the leak)
1) I tried running the ruu but got the error 140 / bootloader version error
- ok , so I found that I need to follow jcase's flash any ruu steps here:
http://forum.xda-developers.com/showthread.php?t=726885&highlight=unroot
2) I get stuck like everyone else at point cmd promt 4 which attempts to flash the misc.img to the phone, I get a not found error, wtf!!!!! Am I supposed to be unzipping this misc.img.zip file or leaving as is? I feel like I have tried everything
{
"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"
}
3) I just tried running the last PB00IMG.zip (v3) through bootloader and got the error stating my current getup is newer than what I'm trying to 'update' it with
***my bootloader = HBOOT-1.49.0000
***error = Main Version is Older! Update Fail!
please help me
anybody
for the record here is my current tools directory:
Ruu epic fail
last thing, I am using the ruu from shipped-roms website
"RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with
_driver.exe"
it's showing up as 124 mb
http://shipped-roms.com/shipped/Desire/RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe
Chicago Ben said:
2) I get stuck like everyone else at point cmd promt 4 which attempts to flash the misc.img to the phone, I get a not found error, wtf!!!!! Am I supposed to be unzipping this misc.img.zip file or leaving as is? I feel like I have tried everything
Click to expand...
Click to collapse
Try reading the post a little further - jcase had a typo in his instructions which he never fixed. It was subsequently corrected in post # (lucky) 13
the original typo was
Code:
adb shell /data/local/flash_image misc misc.img
which should have been
Code:
adb shell /data/local/flash_image misc /data/local/misc.img
As to the question about "img.zip" versus ".img", the answer is obvious from looking at the (now corrected) instructions - you push "misc.img" to /data/local/misc.img, not misc.img.zip to /data/local/misc.img.zip
bftb0
[ Edit ] PS: I just looked through that post ("HowTo: Flash Any Ruu")
What a friggen comedy of errors!
Poster #1 gives some almost correct instructions
Poster #13 tries to correct the fault in instructions given in #1, and in so doing, introduces a new mistake in the same line he corrected
Posters thereafter repeat different variations of #1 or #13 variously claiming $hit like "you need to keep trying it until it works".
LOL.
The correction that I gave above to line #4 should work. When you do an "adb shell" the current directory of the shell is "/", and
- "flash_image" is not in the shell's $PATH
- misc.img is not stored at /misc.img - it is not in the current directory (namely, "/")
So, you need to explicitly give the full path to both the program you are trying to execute ("flash_image"), as well as the full path of the file that program is supposed to read ("misc.img"), as in:
adb shell /data/local/flash_image misc /data/local/misc.img
.
Thank you for the reply but I'm still struggling hard here. It didn't work. Here is a new snapshot of my local tools directory. You can see I have the zip and the uncompressed .img files there just to make sure
****...
I got somewhere ....
I was now looking at jcase's "How To Install Engineering bootloader FOR LEAK ROOTERS"
and downloaded the custom.img
http://forum.xda-developers.com/showthread.php?t=725047
flashed engtools3.zip
rebooted in bootloader and it got past the error I was receiving before about the current version being newer
Wow. It worked. So I followed steps 2, 3, 4 (used v3 (most recent) PB00IMG), 5 the "flashed engtools3.zip code"
rebooted holding vol down (bootloader) then BLAMO
going back to verizon tomorrow to show them I have a faulty refurb that I haven't even rooted
Haha yeah I don't proof read. My bad. Glad my old work is still sorta useful.
REALLY glad bftb0 is here cleaning up my mistakes.
thx broham

{mod}(eh09) samsung boot splash/image change 10.17.11

*edit 10.17.11 compatible with ei20
*im not responsible for your phone melting*
this is an update to the mod here, originally posted by kmalinich for froyo, and my version for ec09 here, but this is for eh09 gingerbread only!!!
if you are like me and hate the SAMSUNG boot splash, then this is a way to change it...unfortunately its not as easy with htc and moto phones..but heres a way to do it
things needed (taken from og thread)
*Rooted Samsung Fascinate (should work fine on mesmerize/showcase as well since its the same file on all) running eh09
*Android SDK/ADB
*Latest Heimdall (i believe its possible to to use odin for this, but apparently on other sgs it soft bricks, but if i get a chance ill tar up a version of this and try it)
*Edited/hacked param.lfs to flash
*New jpg boot logo size 480x800 (others have recommended it be less than 64k..but idkl)
How to Install:
*download file
*use 7zip/file manager to extract param.lfs file
*Enter download mode on your phone
*Install heimdall driver (if you haven't already)
*Flash new param.lfs IN HEIMDALL IN THE BOX THAT SAYS PARAM.LFS, NOT FACTORYFS (if you are using frontend)
*Reboot normally, if it boots into recovery/cwr just reboot again
*Ignore garbled text on bootup (you may even see weird 8 bit cwr logo spread all over screen, no big deal)
*Copy your new boot jpg to the root of your sdcard...must be named logo.jpg
*Open terminal
*Enter these commands:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl6 /mnt/.lfs
cp /sdcard/logo.jpg /mnt/.lfs/logo.jpg
reboot
i have attached the "Google" boot logo in the zip or a tsm one down there
credits:
Rodderik (for the epic4g mod)
kmalinich (eb01/froyo version)
How to Install:
{
"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"
}
*download file
*use 7zip/file manager to extract param.lfs file
*Enter download mode on your phone
*Install heimdall driver (if you haven't already)
*Flash new param.lfs IN HEIMDALL IN THE BOX THAT SAYS PARAM.LFS, NOT FACTORYFS (if you are using frontend)
*Reboot normally, if it boots into recovery/cwr just reboot again
*Ignore garbled text on bootup (you may even see weird 8 bit cwr logo spread all over screen, no big deal)
*Copy your new boot jpg to the root of your sdcard...must be named logo.jpg
*Open terminal
*Enter these commands:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl6 /mnt/.lfs
cp /sdcard/logo.jpg /mnt/.lfs/logo.jpg
reboot
Download: http://www.multiupload.com/AP0I9U0JEJ
md5: 8746425befb30724ad847d1a5a1a8828
good job, too bad i dont have a fascinate anymore!
but i like what u guys are doing on my droid inc 2 (especially pool party)
Nice work! Although a flashable zip would be even better for noobs like me
droidstyle said:
Nice work! Although a flashable zip would be even better for noobs like me
Click to expand...
Click to collapse
there are ways to avoid heimdall for the param, but would still need to do some terminal commands regardless
update: works with ei20
Nitsuj17, may I ask how you are doing this man? are you like just using a hex editor or something for a special byte or something?
Because I would love to see this for the Continuum
Sent from my SCH-I400 using xda premium
trailblazer101 said:
Nitsuj17, may I ask how you are doing this man? are you like just using a hex editor or something for a special byte or something?
Because I would love to see this for the Continuum
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
the original how to link was either in the i9000 forums or epic (it was since removed when the guy left xda) thankfully i had pastied it...if u cant find it lmk
Hey man, I can't find that article you talked about can you hook me up please
Thanks in advance
Sent from my SCH-I400 using xda premium
trailblazer101 said:
Hey man, I can't find that article you talked about can you hook me up please
Thanks in advance
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
i had this saved in my "notes" folder, lol
use a hex editor open params
and change every instance of this: 6C 6F 67 6F 2E 6A 70 67' (logo.jpg)
to 6C 30 67 30 2E 6A 70 67 (l0g0.jpg)...thats pretty much it
Wow man, that worked! Thanks a lot!
Wasn't too hard either, haha..
nitsuj17 said:
update: works with ei20
Click to expand...
Click to collapse
Work with eh03?
yzaker said:
Work with eh03?
Click to expand...
Click to collapse
I didn't test it...but i pretty sure it does
can I use to others samsung devise? ex: Galaxy Ace
7.7.7.7.7.7.7 said:
can I use to others samsung devise? ex: Galaxy Ace
Click to expand...
Click to collapse
no, but the edits would be similiar

MTK yaffs2

Hi!
Story goes like this. I have here clone Samsung S4 that I wanted to update the software trough CWM. Unfortunately phone died at some point and now is dead. But, I made backup of the flash with MTKDroidTools and with SP flash tool... and here comes the problems... I can not flash backup back to phone because yaffs2 files are not good page/spare ratio. Thanks to members rua1 and Alex1948 now it is more clear how to change spare ratio on yaffs2 files. Unfortunately I'm not very good with Linux, last night I boot Mint 16 from USB stick and was trying to repair my files but without success.
So, my question is: is someone willing to repair my files in Linux (who understand Linux terminal better)?
Here are some details from phone
View attachment 2574910
View attachment 2574911
{
"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"
}
I only have problem with flashing yaffs2 files and secro.img all other are OK. If I try to flash those files I get this error
In attachment is mtd, dumchar_info, MTKDroidTools log and Sp flash tool log so you can see my file structure.Log from MTKDroidTools is from version 2.5.2 because I was using this version when I was making backup from my original phone (you will see other phones data just scroll down to MT6575)
I'm uploading original yaffs files to google drive so later I will update this post with some links.
Thank you all in advance.
Best regards
P.S. INFO FROM MTKDroidTools IS TAKEN FROM SAME PHONE LIKE MINE (FRIENDS PHONE) YES, SAME ONE HARDWARE AND SOFTWARE IS 100% SAME.
Files on Google drive link
https://drive.google.com/file/d/0Bx8Xjd1q6dr3YnFISVJBZFZPSUU/edit?usp=sharing
Little update (memory type)
View attachment 2575196
from guide:
Аttention! Yaffs2 type blocks from this backup can't be Downloaded to phone, they aren't correct! Use backup on 9th step if phone have yaffs2 type blocks!
Click to expand...
Click to collapse
files from archive is wrong
from your log:
10/02/14 11:43:23 Free space: system- 113.7M; data- 54.3M; sdcard- 16.7M; D:\ 170861M
10/02/14 11:43:46 - ERROR - tar: write error: No space left on device
Click to expand...
Click to collapse
it was necessary to release the free memory on SD card before
Hi!
First, thank you for your reply.
Yes , I did figure it out that my files are not OK. I was trying to make them manually in "yafey" for windows (software to create and edit yaffs2 images) but this software have to much bugs so one time it create system.img with full lib folder second time only half of lib files are there and also there is no option for spare ratio change.
So, MTKDroidTools did make my system backup in a folder on my PC but I can not make yaffs2 file from it because there is no software for windows that works fine (I don't use Linux). On Linux it is easy to do (at least for someone who understand Terminal commands).
So, I can send you my backuped system folder if you are willing to make yassf2 file from it (in Linux). Data and Cashe files I have create in yafey and thay are ok.
In yafey if I make new yaffs2 file and insert lib,etc,app,framework... it will not create all files in folders... and after that when I try to flash that created system.yaffs2.img I have error from BROM s_ft_readlen_not_page_aligment (4017) again problem with spare ratio.
I still have here my friends phone so if you have any idea what to do and how to do please tell. I made backup from my friends phone but same thing data,cache,system,secro files are not created correctly. I don't know why is this is it because of the MTKDroiTools or is it because of the phone?
Aaaaaaaaaarghh!!!!!
You wouldn't beleive what I just discover I just try to put my friends phone in recovery so I give a try to make backup.
NORMALY my friends phone don't want to go in recovery (just light on screen), so I have call my friend to ask him does he do something with phones recovery and he said YES i flash some recovery from net trough CWM and after that he can not go in the recovery.
CAN YOU BELEIVE HOW UNLUCKY I AM????????
If someone have any idea???

[Solved]Custom Splash galaxy a5. Help me how to modify it.

Hi friends, I need help on how to change the splash screen on my galaxy a5 because I am bored seeing the same bootup logo everytime. Thanks
I've used hex editor to change boot logo on a few samsung devices. It can also be done with script if you're good at it. I'm not [emoji14]
You need to locate the logo.jpg inside param partition, and with hex editor you can insert/overwrite the original with a new logo.jpg with exact same resolution,dpi, and size as the original.
tys0n said:
I've used hex editor to change boot logo on a few samsung devices. It can also be done with script if you're good at it. I'm not [emoji14]
You need to locate the logo.jpg inside param partition, and with hex editor you can insert/overwrite the original with a new logo.jpg with exact same resolution,dpi, and size as the original.
Click to expand...
Click to collapse
Yeah, but how can I pull param.lfs?, I dont have param in my firmware pkg. But according to my PIT, param partition id is 'mmcblk0p12'
You can use "dd if=/dev/block/mmcblk0p12 of=/sdcard/param.lfs" from terminal emulator or adb shell, or download a 4-file repair firmware and take it from there.
Edit: for SM-A500H it should be param.bin. Not param.lfs
tys0n said:
You can use "dd if=/dev/block/mmcblk0p12 of=/sdcard/param.lfs" from terminal emulator or adb shell, or download a 4-file repair firmware and take it from there.
Edit: for SM-A500H it should be param.bin. Not param.lfs
Click to expand...
Click to collapse
will try it.. thank you very much
akil777 said:
will try it.. thank you very much
Click to expand...
Click to collapse
No problem
I downloaded a 4-file for A500HXXU1CPH8 but there wasn't any param.bin in it. Don't know why it's not included.
You'll probably have to pull it from device. If you zip it and share it, then I can probably help you locate the logo if needed.
tys0n said:
No problem
I downloaded a 4-file for A500HXXU1CPH8 but there wasn't any param.bin in it. Don't know why it's not included.
You'll probably have to pull it from device. If you zip it and share it, then I can probably help you locate the logo if needed.
Click to expand...
Click to collapse
yeah me too.. i had pull param.lfs, now how can I modify it via hex editor?
akil777 said:
yeah me too.. i had pull param.lfs, now how can I modify it via hex editor?
Click to expand...
Click to collapse
It depends a bit on what software is used. I use 010 Editor, but the tools are pretty much the same in other editors as well.
This is the param for SM-A310F so your values will be different from the pictures, but it's easier to understand with a picture.
Load param.bin in editor and make a TEXT search for logo.jpg (yellow)
Result is marked in red. That's not the start position of logo.jpg ,but you will be pretty close.
All .jpg images start with ffd8 in hex and the one nearest will be start position (green)
Write down start position.
{
"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"
}
To find the end of logo.jpg I make a new search from ffd8. This time I search downwards for HEX ffd9 which always mark an end for a .jpg
Now you got start and end positions. Select that whole range in the edit menu and copy/paste it in to a new file in hexeditor.
Save the file as logo.jpg at your desktop and you'll find the bootlogo there
Check properties as resolution, dpi, and byte size and make a new picture with same properties, and a size no greater than original.
Make a new file in hex editor and set it to same bytesize as original logo. Fill it with zeroes, then insert/overwrite the new logo there. Save as logo.jpg. It doesn't matter if there's a bunch of zeroes at the end.
Now you will have a new logo.jpg with same size as original. (double check that!!)
Insert/overwrite the new logo.jpg into param, in the same range as the original is. Save param.bin and make sure its same size as the unmodified param. (double check!!)
You can also extract it from the new param to double check that it's where it should be and can be opened.
Be carefull. This partition is a part of the BL-package and stores image cache for bootloader and other parameters.
Done wrong, in best case you'll have a scrambled picture at boot.
At worst case you'll need a usb-jig to force it to download mode. It happend to me once.
A few other times i've had problems to boot because of what I believe was because of some incompatible exif data in jpg.
I couldn't find anything wrong in the modified param so it must have been it.
Those times it was enough to hold power/vol down, and at the same time insert charger to make it boot to download.
Keep a copy of your original param.bin. Tar it so it can be flashed in odin.
I also have an old tutorial for i8190 with a few pictures using HxD editor here: [HOW-TO]-[param-mod]-[BOOTLOGO]
Pretty much same procedure, but as said, all devices will have different values.
Hit the thanks button if it helped you
I attempted. But i failed.i got the solution when I used a flashable zip from the galaxy a510 one then edited the updater-binary. Replaced "dev/block/platform/...../byname/param" to "dev/block/platform/s.../byname/param" something like that. I had a backup of param.lfs or .bin whatever by copying mmcblk0p12 to my sdcard.
akil777 said:
I attempted. But i failed.i got the solution when I used a flashable zip from the galaxy a510 one then edited the updater-binary. Replaced "dev/block/platform/...../byname/param" to "dev/block/platform/s.../byname/param" something like that. I had a backup of param.lfs or .bin whatever by copying mmcblk0p12 to my sdcard.
Click to expand...
Click to collapse
Ok good you got it solved.
I havn't looked at that zip, but I will. It sure would be easier with a script

Categories

Resources