Welcome. Today I am going to teach you how to modify your android boot logo!
Modify at your own risk! I strongly recommend that you do not try this. But if your going to attempt this, make a BACKUP! I will explain the backup process down the page!
This method has been tested on the Galaxy S6. I RECOMMEND you do NOT attempt this method on any other smartphone other than the S6!
I own a Samsung Galaxy S6 [SDK21 ARM64] and my carrier is Straighttalk. This method might possibly work with the newer Android smartphones. In other words, attempting to do my method will probably not work with androids running 4.4.2 or lower. I will first explain why.
According to what I researched, there is a file in the root directory of the Android system that contains a file called "initlogo.rle". That is your boot logo. Older Android phones had this. The .rle is a bitmap extension and cannot be edited with Android. Actually, let me rephrase that, the .rle COULD MAYBE possibly be edited if you were to download the right tools off of the Play Store but computers can identify .rle as a bitmap very easily and can be opened. Windows computers can open .rle according to what I researched.
The initlogo.rle is also part of the boot.img. The boot.img contains the kernel and the boot files (like init.rc), that are necessary for the phone to boot up. Modifying your boot.img requires a computer. You can't just replace the initlogo.rle with another one. To make changes to a boot.img, you need to unpack the ramdisk, replace or modify the files, repack, and THEN flash the modified boot.img to make the changes.
Newer Android smartphones don't have initlogo.rle. Or at least MINE doesn't. Instead, I had to search for my boot logo which took my quite a while. After searching deep into the android system and messing around with the files, I came accross PARAM.
If you were to go in the /dev/block/platform directory, you would come accross a file called PARAM. Mine was in the directory /dev/block/platform/15577000.ufs/by-name. Inside that directory is basically the whole system. You will find files like BOOT, EFS, OTA and all that. You will also notice that all those files look empty. They all show 0.00B. I don't know exactly why that is, but they aren't really empty files.
My official boot logo was in the file "PARAM". What I did was copied it to my internal directory and attempted to extract it. After trying different extensions, I founded out that .tar is the correct extension. So to extract it, I renamed "PARAM", to "PARAM.tar". After doing that, you will be able to actually extracted it and be left with files with .jpg. Basically pictures inside it. I used root browser. :good:
Inside, you should find "logo.jpg". And whatta ya know! It's your boot logo!
I used PicArt to create a custom boot logo. It is a really great app! You can get it off the Play Store. Then I renamed it to logo.jpg and replaced the original logo.jpg with my newer one. Make sure it is named "logo.jpg" or there will be errors!
Now the last step is to archive the files through .tar format. I used root browser to do that. To correctly archive the files, multi-select the .jpg files. In other words, DON'T SELECT THE "PARAM" FOLDER!!!
When archiving the files, use LZMA compression option along with tar.(Look for that with root browser). This will not compress the files as much which will reduce the risk of errors.
Once it's archived, rename the new archive file to just "PARAM".
LAST STEP! Before overwriting your PARAM, copy your modified PARAM into the /system folder and set the correct attributes (PERMISSIONS) to -rwxrwxrwx. Now you are ready. Copy "PARAM" to the same director where you originally got your unmodified PARAM file. It will ask you if you want to overwrite. Say yes.
I was now introduced with a different boot logo. My phone never got bricked during the process. However, with Android, ANYTHING can happen, so I will give you some advice. If you have a custom recovery, you can easily restore PARAM. Make a copy of your original PARAM and put it in your internal directory. If something ever goes wrong, you can use the file manager (like with TeamWin) and replace the currupt PARAM with your backup PARAM. Then set the permissions to -rwxrwxrwx or 0777
I strongly recommend that you do not try this. Yes, I took the risk and was able to safely change my boot logo. However, not all Android devices are the same so be very careful if you are attempting to do this one an Android device OTHER than the Galaxy S6.
Leave comments if you have any questions!
Related
I can't copy or move files stored in device ROM.
I've tried with Resco Explorer and Total Commander, but without success.
I didn't understand if there's a registry hack that allows these operations.
I've notice (or so it seemed to me) that I was able to substitute/copy/move some files having the ROM attribute, but many others not (eg: I've tried to copy the nleddrvr_sec.dll, obviously without success, otherwise I'd post this here!).
Surfing in many forums, I read many others asking for the same thing, unfortunately I haven't seen answers to their question about this.
Hope someone explains to me how to do or why is impossible to do.
Mersì bo q.
Gubbài.
You can not copy / move / delete files in ROM. Thats the point of "Read Only Memory"
These files are not stored as individual files but are in fact packed in a special way as part of the device image which can only be written (flashed) by special tools.
If you want to extract OS files you need to use a ROM dump tool.
I suggest you look in the WiKi.
What you can do is overwrite one or more "ROM files". What will happen in reality is that a copy of the file with the same name will be placed in storage memory and the system will go there. If you hard reset your device or rename the file it will go back to the original file.
levenum said:
You can not copy / move / delete files in ROM. Thats the point of "Read Only Memory"
These files are not stored as individual files but are in fact packed in a special way as part of the device image which can only be written (flashed) by special tools.
If you want to extract OS files you need to use a ROM dump tool.
I suggest you look in the WiKi.
What you can do is overwrite one or more "ROM files". What will happen in reality is that a copy of the file with the same name will be placed in storage memory and the system will go there. If you hard reset your device or rename the file it will go back to the original file.
Click to expand...
Click to collapse
As you said here and here (Changing Files in Windows Dir )
it's impossible to move/copy ROM files, just overwrite 'em.
Doing so the system looking for these overwritten copies.
So now the question are:
- there's a registry entry that points to this substitute ROM files?
- to modify an existent file resident in ROM I MUST dump my ROM or another one same or similar?
Mersì bo q, anyway.
Gubbài.
for those who do not know how to do this yet, follow directions given here.
Just took this info from the web. None of this except for the guide is written by me.
I am not responsible for anything please do not contact me if a green sludge starts attacking your neighborhood eating one person at a time.
************************************************************
************************************************************
************************************************************
http://code.google.com/p/unyaffs/downloads/list
made for linux, but if you know a bit of c, you can probably change it to work with windows, maybe I will do that if I have some time this week.
********OR********
http://jiggawatt.org/badc0de/android/unyaffs-x86-win.zip
or http://www.4shared.com/get/fgryPnPx/unyaffs-windows.html
for windows..... instructions below apply for both
if not included in the zips above, cygwin1.dll and unyaffs.exe are included as an attachment of this reply.
open up a command line, in windows vista/7 just press start and then type cmd press enter and change the directory to the folder with the unyaffs and the img in it. in xp press start>run>cmd... then the same
the usage is: unyaffs /path/to/img
example:
(if unyaffs.exe and system.img are both in c:\temp)
"c:\temp> unyaffs /temp/system.img"
note: the '/' is the way linux determines the pathname of a file and since it is built using cygwin(a file allowing for windows) it is preferrable that the path to the actual file is in unix POSIX format ie: / instead of \ between folders and files.
*********WARNING************
this will extract to directory that unyaffs binary is in.
That's so weird -- I was gonna post the same thing tonight. Thx for writing this up. It's odd that more people don't talk or ask about this tool!
I remember reading this stuff back when I got my G1, and tonight I was trolling the themes and apps section cause I couldnt sleep. (which I rarely look at)
I was baffled that this wasnt common knowledge. I figured if there was no threads about it that people just knew how and didnt have any problems with it. My mistake lol...
enjoy.
can you please explain what is it? what it does? thanks
ericizzy1 said:
can you please explain what is it? what it does? thanks
Click to expand...
Click to collapse
Umm, it expands nandroid img files not sure how else to explain it. Clockworkmod backups are in the img file format. This process allows you to extract those files to get stuff out of them
Sent from my SPH-D700 using XDA App
When you create a backup in Clockwork recovery, it leaves you with a folder like this:
2010-11-18.08.52.49
As you can prob figure out, I made that backup on 11/18 at 8:52am
Inside that folder are .img files, such as: data.img and system.img
Those files basically contain your data (like apps you've installed from market) and system (..system apps that might've come with the phone).
In the orig post, he's explaining how to extract the files from these large .img files.
To give an example, I had a couple of corrupted clockwork backups, and wanted to ONLY pull out some database files (like text messages and call logs) which were not corrupted. Even tho the backup was messed up, I could still extract the files I needed by using the method above, then copied them manually to my phone.
decalex said:
When you create a backup in Clockwork recovery, it leaves you with a folder like this:
2010-11-18.08.52.49
As you can prob figure out, I made that backup on 11/18 at 8:52am
Inside that folder are .img files, such as: data.img and system.img
Those files basically contain your data (like apps you've installed from market) and system (..system apps that might've come with the phone).
In the orig post, he's explaining how to extract the files from these large .img files.
To give an example, I had a couple of corrupted clockwork backups, and wanted to ONLY pull out some database files (like text messages and call logs) which were not corrupted. Even tho the backup was messed up, I could still extract the files I needed by using the method above, then copied them manually to my phone.
Click to expand...
Click to collapse
thx
Sent from my SPH-D700 using XDA App
smeyerhuky said:
Umm, it expands nandroid img files not sure how else to explain it. Clockworkmod backups are in the img file format. This process allows you to extract those files to get stuff out of them
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Right, like if you wanted a file or a few files from clockworkmod img backup, then this process would give you an extended file system, other than what you would normally use to extract the img files. Just trying to understand this so, please correct me if im wrong.... I've been trying to get more knowledge of this, so im still learning.
I prolly sound like a complete idiot, lol...
Sweet! Thanks for this man. I'd been looking for how to do this for some time and kept ending up learning about emulation or some other tangential topic. This is the basic functionality I was looking for. Thanks for posting!
Np. I'm working on writing some stuff on top of the source code that should allow you to browse and pull just one our more file
Its been a but since I looked theory source code so it might take a while... Maybe in between semesters?
Sent from my SPH-D700 using XDA App
Dode you saved my as** thx big thx
Great, now how can I re-compress back to .img after I've made the changes that I want?
EDIT: Nevermind. I just made a zip of the new system folder and flashed it in CWM.
This worked great for me.
Thanks,
Bud
Man, I do not know how to thank you. I was able to recover some important stuff off of my cwm recovery backup. THANKS!!
Hello everyone,
I'm new to low-level Android hacking, so I guess I need some help.
What I am trying to do is getting the stock files from an LG E400, and modify 1-2 things, repack, flash, and see if it works for me.
My first step:
1) Rooting the LG E400
2) Flash CWM Recovery
3) Create a backup
4) Get boot.img from the backup.
So I have a boot.img (which I think is stock, because rooting does not modify the contents of the boot image as far as I know.)
After that, I followed this tutorial to extract the kernel and the ramdisk.
I used a hex editor for this. I saved the kernel and the ramdisk as separate files, and I tried to gunzip the ramdisk. That seemed to work. However, after that, when I try to run cpio on the file, I get a lot of "Malformed number" errors, and only two empty folders are extracted.
And that is where I'm stuck at.
Are the LG phone boot.img-s encrypted somehow? Am I doing something wrong?
If anyone can help me, I would be really grateful.
Thanks in advance
How to download the removed ext_unpacker.exe
Recently, I have came back to android ROM rooting, and found myself unable to download the files that allow ext4 unpacking on windows. And if you are using a laptop with windows, or a small windows setup on desktop, or just are not that tech savvy, and dont know or dont have the space, to create a dual-boot setup for pc, you can just use this unpacker!
WARNING: I DO NOT CREATE OR OWN PROGRAM, ITS CONTENTS, OR ITS FILES, I AM SIMPLY REDISTRIBUTING FILES THAT LOST SUPPORT FOR THEM, USE THEM AS YOU WISH, AND I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR TO YOUR DEVICE, SYSTEM, FILES, OR ANYTHING ELSE THE PROGRAM INTERACTS WITH, AND TAKE NO RESPONSIBILITY FOR DAMAGES THAT DO OCCUR. THIS PROGRAM HAS PROVEN TO BE SAFE FOR ME, THAT DOES NOT MEAN IT WILL BE SAFE FOR YOU.
First Method Of Obtaining Files:
The first what you are able to obtain the ext4 unpacker is by going to this XDA thread and downloading the GS-Kitchen RELOADED. I am not going to add the download for there file, as to give them support for there files, and there work. But if you download there ZIP file, and extract it, you can find the 2 files you should need to run the unpacker, those files are located in the tools folder, and called:
ext4_unpacker.exe
ext4_unpacker.ini
After grabbing those files, you should just be able to run the ext4_unpacker.exe, but you may want to run it as admin.
Second Method Of Obtaining Files:
The second method, and the easiest way to get the files, is to just download the zip file containing the two files from here. Just simply unzip, and use the .exe file! I got the file from the same place as method 1, although method 1 got it from somewhere else, if im not mistaken.
Enjoy the ability unpacking on windows!
Hello, I´m a newbie on this matters.
I´m trying to cook a custom rom from a stock rom for this android pc with RK3328 chip. The rom I´ve downloaded is an 8.1 android image version, an the app I used is RK3xxx_firmware_tools_5.78.35.00 that I´ve downloaded from the chinagadgetsreviews.
When I uncompressed the rom.img, system.img and boot.img with this app, I got three folders called: "Android", (with a "Image" subfolder with the boot.img, kernel.img, recovery.img... and a package-file file), "boot", (with a boot.img.unkrnl.dump folder who contains many folders and .rc files, boot.img.unkrnl.cfg file and boot.img.cfg file), and "system", (with the app, etc, bin... folders and the build.prop, compatibility_matrix.xml, manifest.xml and vendor files). Also got a system_statfile with these 3 folders.
I´d like to remove some apps from this rom and include others, and if it is possible, changing the recovery.img from it. The recovery partition has 64MB of size, and the original recovery.img has only 9057 KB. The recovery.img I´d like to install is the twrp_RK3328_v3110 adapted for this chip (who has only 5258 KB), but I wonder if I could simply replace the original recovery.img with this twrp one on the "Image" subfolder I said (renaming it first to recovery.img) and after repack the rom, or, like I'm afraid, more things have to be done.
Thanks a lot in advance.
Anybody doesn't know how?
porkero said:
Hello, I´m a newbie on this matters.
I´m trying to cook a custom rom from a stock rom for this android pc with RK3328 chip. The rom I´ve downloaded is an 8.1 android image version, an the app I used is RK3xxx_firmware_tools_5.78.35.00 that I´ve downloaded from the chinagadgetsreviews.
When I uncompressed the rom.img, system.img and boot.img with this app, I got three folders called: "Android", (with a "Image" subfolder with the boot.img, kernel.img, recovery.img... and a package-file file), "boot", (with a boot.img.unkrnl.dump folder who contains many folders and .rc files, boot.img.unkrnl.cfg file and boot.img.cfg file), and "system", (with the app, etc, bin... folders and the build.prop, compatibility_matrix.xml, manifest.xml and vendor files). Also got a system_statfile with these 3 folders.
I´d like to remove some apps from this rom and include others, and if it is possible, changing the recovery.img from it. The recovery partition has 64MB of size, and the original recovery.img has only 9057 KB. The recovery.img I´d like to install is the twrp_RK3328_v3110 adapted for this chip (who has only 5258 KB), but I wonder if I could simply replace the original recovery.img with this twrp one on the "Image" subfolder I said (renaming it first to recovery.img) and after repack the rom, or, like I'm afraid, more things have to be done.
Thanks a lot in advance.
Click to expand...
Click to collapse
All I can say is, extract the ROM until you get to the system folder then look for /system/app and /system/priv-app folders, delete the apps you don't want and add the ones you want. Then, remove your recovery.img and place your TWRP.img in its place then repack everything into the file format that you need then try flashing it.
If that doesn't work, you'll have to start doing your own research to get your ROM put together correctly.
Sent from my SM-S767VL using Tapatalk