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
Related
Hi,
New NSS beta is available for download. It will implement installing and restoring
of the bootloader as single click solution. Although the Qcom loader could be
installed via normal flashing, it is much easier this way. Also recovery is intended
to save manual hex editing or cmd line commands.
1. Download the new version
2. Extract to a folder, start the program
3. Insert the 2 loaders in \loaders\special\wp7\ - the qualcom file: RM803_12w07_prod_generic_nokia_osbl.esco,
posted by xorizont here , second file: RM803_11w48_prod_raw_nokia_osbl.bin attached (unzip first)
4. Go to Flashing->WP7 Tools
You are ready to play. Quick description:
- Read PMM button - reads the PMM partition with Nokia specific values(product
code, MAC addresses, et), you can edit in the boxes
- Write PMM button - writes back to the partition a selected value (via Update
checkbox)
Install button - use this to quickly install Qcom loader on 710(no way to load on
800 as the cert is checked)
Parse FS button - you can use this to test NSS partition parser and compare
against 3rd party tool, to make sure something catastrophically wrong will not
happen during recovery
Restore button - This will attempt to recover the Nokia production loader (so called DLOAD)
via raw NAND write into partition 2 of the connected phone. Make
sure you start in Normal mode as NSS will need to check phone type and battery
value (to make sure wrong file is not written to 800, or if the battery is critically
low)
Please keep in mind, this is a Beta version, it has been tested only on one phone
and is possible to be a major phone killer, so thread lightly. It is offered as it is,
with the hope of being useful, and I can't be held responsible for fatal results.
My best recommendation is to check the partitions after write/recovery with
3rd party tool and make sure all is ok before restarting the phone power. All this
until some recovery method is found (if somebody has found flashing routines in
SECBOOT or other loader, pls PM me).
BR, Chris
Thanks for this nice tool!
I just wanted to stress that:
- Read PMM button - reads the PMM partition with Nokia specific values(product
code, MAC addresses, et), you can edit in the boxes
- Write PMM button - writes back to the partition a selected value (via Update
checkbox)
Click to expand...
Click to collapse
Are only possible when the phone has the qualcomm loader right? Because only then it's possible to overwrite the values using the NAND access mode (Qualcomm MSD).
Hi,
Yes, only in NAND mode, on phones that have it. If you have Nokia DLOAD loader
and not hacked phone, you can only read those value via JSON call to NCSD appl.
There isn't any method coded to change them in Normal mode(at least i did not
find one yet).
BR
Bph&co said:
Hi,
Yes, only in NAND mode, on phones that have it. If you have Nokia DLOAD loader
and not hacked phone, you can only read those value via JSON call to NCSD appl.
There isn't any method coded to change them in Normal mode(at least i did not
find one yet).
BR
Click to expand...
Click to collapse
It's good to see there is now a userfriendly way of doing stuff like this. Thanks again
now all we need is a tool to write an .nb file with one click. can one do it?
mariosraptor said:
now all we need is a tool to write an .nb file with one click. can one do it?
Click to expand...
Click to collapse
To be honest i have no idea how that exactly works - is there a need for a file
system parser and proper replacing of a file, or just writting to a const location
in the last partition.
The mount never worked on my Ubuntu install(and i am complete Linux newbie).
Bph&co said:
To be honest i have no idea how that exactly works - is there a need for a file
system parser and proper replacing of a file, or just writting to a const location
in the last partition.
The mount never worked on my Ubuntu install(and i am complete Linux newbie).
Click to expand...
Click to collapse
Thanks God. there is someone else like me in linux.( humor, no offense ofcourse ;-) )
mate i have no idea how it works. nobody wants to write a very accurate tutorial.
not being able to flash the custom rom was the reason that i reverted my bootloader.
To unlock bootloader I used to NCS and firmware posted by xorizont. So how make connection under Windows7 before flash xorizont's firmware if Nokia is in DLOAD mode?
this is very helpfull for many people to get to qulcomm on 710!
+1
So You are able to load Qualcomm B. via NSS even if on the moment I have got DLOAD?
Hi,
New Beta - 0.47.1 - with ability to write moded OS files(.nb).
OS File button - select .nb file
Write OS button - loads the file onto the last partition (change to OSBL mode first)
As with the previous beta - make sure you check the partion parser for errors.
Write will be verified, but not the exact write address, so maybe good to have a
look with WinHex before restarting the phone.
BR
Already a new version, you're working hard man! ;-)
So if i understand correctly, you have automated the process of 'block writing' (which without this tool requires using dd) the created custom roms to the correct partition on the Lumia?
Of course this requires Qualcomm bootloader; for the 710 your tool can load this even if the phone currently has the newer Nokia DLOAD.
Hi,
Yes, i work even in my sleep Right now killing myself with the baseband diss, but
decided to have a break and make this.
It seems the OsBuilder creates raw partition image, to fit exactly into the OS part
of the NAND chip. So all i do is open the usb device as physical disk, parse the
partition structure and do a low level read/write to absolute addresses.
Yes, it is mostly for 710, but write OS function should be working for 800 with
Qcom loader too, just can't test it as i don't have such phone.
Also the Install/Recovery should work forever on a 710, unless Nokia/MS release
some updated bootloader that somehow prevents loading of the signed Qcom
loader and the user does a full flash (or via sneak Zune update) and overwrite
the current DLOAD loader.
BR
Bph&co said:
Hi,
New Beta - 0.47.1 - with ability to write moded OS files(.nb).
OS File button - select .nb file
Write OS button - loads the file onto the last partition (change to OSBL mode first)
oh man you are a superstar. you did what i said it was missing. no more (hopefully) screwd phones.
@Mods please make this sticky.
Click to expand...
Click to collapse
Amazing tool!
I just used it to load Full Unlock Image for Lumia 710 by lucifer3006!
No more linux stuff needed, this is great and almost one-click windows solution!
Thank you!
When we talking about copy moded nb file into partition You mean sdx9 is default partition?
Hi,
The sdb thingi is something from Linux. On low level there are 4 primary partitions
in MBR, all the rest are logical, so the last entry in MBR points to the first logical one,
that for itself contains primary part and next one is logical as well. The last entry
in this linked list is the OS partition.
BR
1. OK I went through this. Tell me please how is possible to unlock bootloader if Lumia is in DLOAD mode? NSS can't reconized WP in this mode.
2. In case of relocking bootloader did I need copy Your specific RM803_11w48_prod_raw_nokia_osbl.bin or download an from navifirm?
I hope it's add backup and restore the "DPP.BIN" function!
like this!
{
"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"
}
Thank you very much!
djtonka said:
1. OK I went through this. Tell me please how is possible to unlock bootloader if Lumia is in DLOAD mode? NSS can't reconized WP in this mode.
2. In case of relocking bootloader did I need copy Your specific RM803_11w48_prod_raw_nokia_osbl.bin or download an from navifirm?
Click to expand...
Click to collapse
Hi,
1 - Maybe you have Zune running and NSS can't open the port ? Use the kill Zune
services option in NSS please
2 - Yes this specific loader is needed (its extract from an original file) and is hash
checked before writting to the second partition to prevent dead phones
BR
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
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 ???
Hello everybody
First i dont own a Mi5 but in the newer version of the MIUI V8 Android 7 there is the problem that
a modified splash.img does not change the bootlogo which is shown on boot.
A friend of me (**@[email protected]**) asked if i could try my luck to get a new bootlogo on his phone. So i screwed around build a kernel and tried and tested... till i opened the logo.img file from the rom with a hex editor and tried to understand its header data.
With help from **GokulNC** i figured out how the file is build ( Thank you for that Goku! )
So i was able to rebuild the file with a modified script.
It seems to work!
But i could only test it at Hoschis phone so please feel free to write if something do not work or if there are errors or bugs.
For Windows i edited Gokus tool that it reads 5 pictures from its "pics" folder. ( put your pictures there and name them logo1.png till logo5.png )
I am not familiar with the windows powershell ( ok i wasnt with python either... ) so if somebody could write it better please tell me.
I tested it in a virtual machine with windows7 and was logged in as admin ( if somebody want to know ).
Instead i wrote a tool with a gui for linux. You can use one picture for all or set every single one.
You can adjust the resolution of each picture if you like.
I tested it on Mint and on a nacked virtualized Ubuntu.
Both tools can build a update.zip to easily install your new bootlogo.
How to use Logo_img_Maker for Linux
download the Logo_img_Maker_Linux.tar and untar it to your homefolder.
In the Logo_img_Maker_Linux folder check that the makeLogo.sh script is marked executeable.
Now start the Script with a double click ( run in terminal ) or start it with "./makeLogo.sh"
On start the script check if all necessary additional software is installed and if not try to install it with the apt-get tool.
To run the script succesful following programms are needed:
python; python-imaging; python-pit; imagemagick; zenity; zip
If a error occur the script shows it in the terminal window and maybe ask for your superuser password to install the missing things.
You can also run: "sudo apt-get install python python-imaging python-pit imagemagick zenity zip -y" first to set up your system.
How it works:
At first you see a Welcome screen. Click ok to get to a file selection dialog where you can select the .png file which will get your new bootlogo.
After that you can adjust the resolution if you like. Your original picture dont get edited (the script copy it first to a temporary folder).
If you dont want to let the "keep_size" radiobutton active and only press ok then.
So now you can decide if you want to use the selected picture for all slots in the logo.img file or to put a different for every single slot.
If you want more to know about it read "logo.img explained" in this readme
If you select
one4all:
your before selected picture get used for logo Nr.1
The Script resizes the other 4 to 161x321 to save space on disc
add more:
you have to select the other 4 pictures one after another and set its size like you did with the first one. Of course the sizes can differ
for each picture.
When you are done with one of the two options the logo.img get build.
If that was successful you will get asked if you want to generate a update.zip for your custom recovery.
If you dont want to the logo.img can be found in the output folder.
If you click yes the flashable zip get generated in the output folder too.
How to use Logo_img_Maker for Windows
I only have Windows in a virtual machine to test it but it should work.
I have had it running with the administrator account and it build well... some others had proplems.
Download the Logo_img_Maker_Windows.rar and unrar it
then put your 5 .png pictures in the pic folder and rename them to logo1.png logo2.png logo.3png logo4.png logo5.png
start the CREATE_LOGO.bat to build your logo.img / update.zip after that
Ok i have took this script directly from **GokuINC**s work. the only difference is
that the batchscript estimates logo1.png till logo5.png directly and dont ask if there is a file.
The direct link to **GokuINC**s work:
https://forum.xda-developers.com/mi-5/how-to/guide-how-to-create-custom-splash-t3425054
logo.img explained:
the original logo.img header got explained by **GokulNC** from xda-developers.com - big thanks
- without him this all could not have been possible!
The header from ori file is:
SPLASH!!
Width (of 5 pictures)
Height (of 5 pictures)
SUPPORT_RLE24_COMPRESSIONT (of 5 pictures) (1 means it is RLE encoded, 0 means RGB24)
Payload size/4096 (of 5 pictures)
(Offset/4096)-1 (of 5 pictures)
And the funny thing my script do:
SPLASH!!
Width (of 5 pictures)
Height (of 5 pictures)
SUPPORT_RLE24_COMPRESSIONT (of 5 pictures) (1 means it is RLE encoded, 0 means RGB24)
(Offset/4096)-1 (of 5 pictures)
and it works on "MIUI V8 Android 7" with a Mi5 (gemini)
I first tried to rebuild it like Gokus example ( and of course - in the hex editor it was clear the same as in the original logo.img ..
ok different sizes but all was calculatebale and logical)
but it didnt work....
So i poked around and got this working solution - tested on **@[email protected]**s Mi5
There are many things that arent clear as they should - but it works somehow
It shows the bootlogo equal if you boot to your system or your recovery.
I dont know really if the 5 pictures are all the same but different sizes or if they are different.
The original resolutions are:
logo picture 1 = 161x321
logo picture 2 = 558x992
logo picture 3 = 178x350
logo picture 4 = 1080x1920
logo picture 5 = 1080x1920
Update 04.06.2017 :
Windows tool now v0.2 = fixed installer script
XDA:DevDB Information
Mi5_logo_img_Maker, Tool/Utility for the Xiaomi Mi 5
Contributors
Cynob, GokulNC, @[email protected]
Version Information
Status: Testing
Created 2017-05-09
Last Updated 2017-05-09
logo2 to logo5 seems useless
Only shows logo1 which doesn't show as 1080x1920 (if provided image), instead it shows as 1080x100
This is the logo i made for it
{
"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"
}
Gesendet von meinem MI 5 mit Tapatalk
---------- Post added at 08:27 PM ---------- Previous post was at 08:23 PM ----------
@[email protected] said:
Gesendet von meinem MI 5 mit Tapatalk
Click to expand...
Click to collapse
Thies is my Logo 1080x1920
Gesendet von meinem MI 5 mit Tapatalk
duxishere said:
logo2 to logo5 seems useless
Only shows logo1 which doesn't show as 1080x1920 (if provided image), instead it shows as 1080x100
This is the logo i made for it
Click to expand...
Click to collapse
Strange thing... i would understand if nothing is working but your pic 1080x100 sized? ok ... i have took your pic and build the logo.img - can you give it a try if it behave the same?
Where do the logo2.png till logo5.png got shown?
öhm i need more posts to upload files - i have saved your logo.img in the first contribution as update.zip
Cynob said:
Strange thing... i would understand if nothing is working but your pic 1080x100 sized? ok ... i have took your pic and build the logo.img - can you give it a try if it behave the same?
Where do the logo2.png till logo5.png got shown?
öhm i need more posts to upload files - i have saved your logo.img in the first contribution as update.zip
Click to expand...
Click to collapse
Well it is estimated to be about 1080x100 by eye, i will try to take a shot of it. It was built with Windows tool and i will try to test your one, will inform asap
logo2 to logo5 no where to be seen, cant check with stock recovery logo
---------- Post added at 09:30 AM ---------- Previous post was at 09:12 AM ----------
Here is the picture of the boot logo, sorry for potato webcam picture
As you can see it is trimmed to 1080x something about 100-200 px
The proplem is: the original logo.img has 5 pictures in it. I dont know where the other 4 pics get shown. They are there in the file but dont know where they are used.
Here a link to logos i build with Linux!
https://drive.google.com/open?id=0B78p1EKw_mzra1lLd00xVlBfalk
Google
Can someone upload the logo.img which contains Google Pixel Splash Screen? Thanks so much
emanuel.caesar said:
Can someone upload the logo.img which contains Google Pixel Splash Screen? Thanks so much
Click to expand...
Click to collapse
Senden meine a picture
Gesendet von meinem MI 5 mit Tapatalk
if its that google logo: try the update.zip
ok there was a error ... i investigate xD
News:
I rewrote the logo_gen.py to make a file with only one picture inside and deactivated the RLE compression = wont work.
Ok but i think i found out why some png images work and some others not.
Its because some information in the png header itself.
If you have a picture which wont work try:
Open Gimp image editor (https://www.gimp.org/)
Now open your existing png file.
Then use the "export as" function from dropdown menu
give it a "newname".png and click on export
Now you will get to a screen showing the export properties
deactivate every option and set the compression rate to 0
after that click "export" to generate a new picture which can be used for generating a logo.img
best result i got was when i used the same picture and copied it to logo2.png....>>logo5.png
Next step will be to edit the tools that they do it on their own
for testing which filesettings for the png will do it i have uploaded some test objects to github: https://github.com/Cynob/Mi5_logo_image_Maker/tree/master/logo_img_testing
feel free to download and test which one will work or not - if you want to help
Any update/progress on this?
duxishere said:
Any update/progress on this?
Click to expand...
Click to collapse
yes i wait for someone who test my uploaded files on github. If someone would say which works and which not i could finish my work... but till now nobody answered
I could try it tomorrow
Windows Logo maker works perfect!!
Gesendet von meinem MI 5 mit Tapatalk
duxishere said:
I could try it tomorrow
Click to expand...
Click to collapse
and have you tried some of the files?
The proplem is: not every picture gives a working logo.img. i want to know if its the pictures header fault or if it relay on the alpha channel and so on.
Cynob said:
and have you tried some of the files?
The proplem is: not every picture gives a working logo.img. i want to know if its the pictures header fault or if it relay on the alpha channel and so on.
Click to expand...
Click to collapse
None of those working on
firmware_miui_7.5.4_dev.zip
Click to expand...
Click to collapse
None of these working because i was flashing it into splash instead of logo, will try again in a sec
Okay so only glogo03 (one with something like inverted gradient of colors background) seems to be scaled down, something like scaled down to size of others glogo if you know what i mean...
Only one image in the logo.img file right? There was no fastboot image, was same as boot logo
No difference between logos so i suppose fastboot flash logo logo.img worked for every one as returned in CMD prompt
duxishere said:
None of those working on
None of these working because i was flashing it into splash instead of logo, will try again in a sec
Okay so only glogo03 (one with something like inverted gradient of colors background) seems to be scaled down, something like scaled down to size of others glogo if you know what i mean...
Only one image in the logo.img file right? There was no fastboot image, was same as boot logo
No difference between logos so i suppose fastboot flash logo logo.img worked for every one as returned in CMD prompt
Click to expand...
Click to collapse
Ok good - so the tool works if i understand you
only with picture glogo3 there was it shown wrong.
and yes the command "fastboot flash logo logo.img" is the right one.
Is in original logo.img a other logo for fastboot than at normal system boot?
In your logo images same pic for fastboot, but in stock, mi 5 unlocked on bootloader, fastboot text with android figure
duxishere said:
In your logo images same pic for fastboot, but in stock, mi 5 unlocked on bootloader, fastboot text with android figure
Click to expand...
Click to collapse
Did you try to put 5 different pictures in the logo gen tool?
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 ...