Database Info

[GUIDE] Pre-Root ROM and Rebuild into Odin Flashable Package!

Odin ROM Package Builder v1.3 for 64-bit Linux based systems
-------------------------------------------------------------
---------------------
Pre-Rooting Process:
---------------------
Extract the pre-root_rel_1.3.tar.gz to your Home folder to create a 'pre-root_rel_1.3' working directory.
Extract and place ALL files from a Stock Odin flashable package to the 'source' folder.
Open a Terminal and navigate to the pre-root working folder.
For Example: cd /home/*username*/pre-root
---------------------------------------------------------
Then make sure the binaries have executable permissions:
---------------------------------------------------------
chmod 777 ./rebuild_system
chmod 777 ./build_rom
chmod 777 ./build_kernel
chmod 777 ./build_modem
chmod 777 ./build_csc
-----------------------------------------------
To rebuild the 'System Image' as 'Pre-Rooted':
-----------------------------------------------
You must first edit the param.cfg file and change the variables to match your ROMs files.
Save the file and type the following in the Terminal:
./rebuild_system
Notice that the correct system image size used for rebuilding is calculated for you automatically during the process.
Note: You will then be prompted to enter '[sudo] password'. This is the password you chose when you installed Linux.
When the process has finished, the Original 'System Image' in the 'source' folder will be replaced by the newly created 'Pre-Rooted' 'System Image'.
-------------------------------------------------------------------
To Rebuild 'source' files back into an Odin flashable ROM package:
-------------------------------------------------------------------
Type the following in the Terminal:
./build_rom
You will then be guided to name your Odin package before rebuilding.
'Enter Device Model' - For Example: I9505
'Enter Sales Code' - The CSC letters for example: 'BTU' for UK.
'Enter PDA Version' - For example: 'XXUBMGA_PRE-ROOTED'.
'Enter Phone Version' - Version of Modem. For example: 'XXUBMGA'.
'Enter CSC Version' - For example 'OXXBMG3'.
The package will then be rebuilt and finally an MD5 checksum will be added.
Your finished package will be then placed in the 'output' folder.
-----------------------------------
Other binaries within this package:
-----------------------------------
build_kernel - Allows you to package the Kernel file into an Odin Package.
build_modem - Allows you to package the Modem file into an Odin Package.
build_csc - Allows you to package the CSC files into an Odin Package.
----------------------------------------------------
This package is configured for I9505 by default.
----------------------------------------------------
If you get any errors you may have missing packages
just look at the error and install the relavant
package. Everything should then work fine.

thanks a lot for ur script can u plz make a video for this because i will install linux but im confuse

Ah great work! thanks, but it seems to work just for GT-I9505? It asked me to put a system.img.ext4 to source folder from original Odin pack or shall I convert original system.img to ext4 file?

nicemblem said:
Ah great work! thanks, but it seems to work just for GT-I9505? It asked me to put a system.img.ext4 to source folder from original Odin pack or shall I convert original system.img to ext4 file?
Click to expand...
Click to collapse
You need to edit the scripts and change the filenames.
Sent from my GT-I9505 using Tapatalk 4

Odin ROM Package Builder has now been updated to v1.3

SGH-I467 - ATT Note 8
Hello lyriquidperfection,
Thank you for your efforts.
I am trying to root my I467 (ATT Samsung Note 8). I was able to flash the image and reboot after some trial and error. When I try to run SuperSU I get a message "There is no SU binary installed, and SuperSU cannot install it. This is a problem".
I am using pre-root version 1.3 and Ubuntu server 12.04TLS
I ran the scripts;
./rebuild_system
./build_rom
I did not package the kernel, modem, or csc. I already have them from Samsung. Am I missing something?
Thanks again,
./rebuild_system stdout
---------------------------------------------------
--- Odin System Image Builder v1.3 (C) Gaz 2013 ---
---------------------------------------------------
Converting: 'system.img' from Sparse EXT4 Image to Standard EXT4 Image...
Okay!
Loop Mounting './system_image/system.img' to './system' Folder...
Okay!
Rooting 'system.img'...
system/xbin/[
system/xbin/[[
system/xbin/ash
....
system/xbin/zcat
system/app/Superuser.apk
system/xbin/busybox
system/xbin/su
Okay!
Getting required image size...
Size = 2048M
Rebuilding 'system.img' as Odin Flashable System Image...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 2173/131072 inodes and 346014/524288 blocks
Okay!
Unmounting './system'...
loop: can't delete device /dev/loop0: No such device or address
Okay!
Cleaning up folders...
Okay!
Removing Original 'system.img' from './source' Folder...
rm: remove write-protected regular file `./source/system.img'? y
Okay!
Moving Pre-Rooted 'system.img' to './source' Folder...
Okay!
Finished.
./build_rom stdout;
----------------------------------------------------
---- Odin ROM Package Builder v1.3 (C) Gaz 2013 ----
----------------------------------------------------
Enter Device Model: SAMSUNG-SGH-I467
Enter Sales Code: ATT
Enter PDA Version: I467UCAMF1-ROOT
Enter PHONE Version: I467UCAMF1
Enter CSC Version: ATT_I467ATTAMF1
-----------------------------------------------------
-------- Building '.tar.md5' Odin Package... --------
-----------------------------------------------------
Creating TAR Archive...
boot.img
param.bin
recovery.img
sboot.bin
system.img
tombstones.img
tz.img
Okay!
Calculating MD5 Checksum...
Okay!
Moving file to: './output' folder...
Okay!
Odin ROM Package:
'SAMSUNG-SGH-I467_ATT_SAMSUNG-SGH-I467I467UCAMF1-ROOT_SAMSUNG-SGH-I467I467UCAMF1_SAMSUNG-SGH-I467ATT_I467ATTAMF1.tar.md5'
Built successfully in './output' folder.
Finished.

thanks a lot

Works with Samsung Galaxy S3 Mini and Samsung Galaxy Chat.
Thanks for this tool!

@ZeroxCorbin
Don't AT&T and Verizon lock their bootloaders? If so then you would need to unlock it before you can flash ROMs.
Sent from my GT-I9505 using Tapatalk 4

SGH-I467 - ATT Note 8
lyriquidperfection said:
@ZeroxCorbin
Don't AT&T and Verizon lock their bootloaders? If so then you would need to unlock it before you can flash ROMs.
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
I believe they do, but I am able to flash the new system.img. I can even flash the factory bootloader, csc, and modem using Odin.
I can run SuperSU after flashing the modified image. I just get the error that the binary is not installed. I have tried using the stock recovery to load SuperSu from a zip file, after flashing, but Samsung only allows self signed files.
I also noticed that I can not get a data connection via LTE with the modified system.img flashed. If I flash everything back to factory LTE data works.
What do you think could cause the binary to not be available even though it is there? Permissions? If so, is the bootloader changing them after the flash is complete?
Thanks for any advice, and the prompt reply.

Thanks!
Why I'm I getting the following error:
bash: ./rebuild_system cannot execute binary file
Thanks

zabumba said:
Thanks!
Why I'm I getting the following error:
bash: ./rebuild_system cannot execute binary file
Thanks
Click to expand...
Click to collapse
Have you read the guide?
Sent from my GT-I9505 using Tapatalk 4

lyriquidperfection said:
Have you read the guide?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes. And gave the binaries executable permissions but keep getting same error...I'm on Suse.
Thanks

zabumba said:
Yes. And gave the binaries executable permissions but keep getting same error...I'm on Suse.
Thanks
Click to expand...
Click to collapse
Ahh right, is bash installed on your setup as my binaries rely on this. I built and tested these binaries on the latest Ubuntu.
Sent from my GT-I9505 using Tapatalk 4

I have Linux Mint installed and also have bash installed. And I am also getting the same error........ Suggestions?
Code:
[email protected] ~/Downloads/pre-root $ ./rebuild_system
bash: ./rebuild_system: cannot execute binary file

Cheers for the guide

Dubzie said:
Cheers for the guide
Click to expand...
Click to collapse
No worries it has been long over due! Needed to make them more user friendly first though!
Sent from my GT-I9505 using Tapatalk 4

ZeroxCorbin said:
I believe they do, but I am able to flash the new system.img. I can even flash the factory bootloader, csc, and modem using Odin.
I can run SuperSU after flashing the modified image. I just get the error that the binary is not installed. I have tried using the stock recovery to load SuperSu from a zip file, after flashing, but Samsung only allows self signed files.
I also noticed that I can not get a data connection via LTE with the modified system.img flashed. If I flash everything back to factory LTE data works.
What do you think could cause the binary to not be available even though it is there? Permissions? If so, is the bootloader changing them after the flash is complete?
Thanks for any advice, and the prompt reply.
Click to expand...
Click to collapse
Are you packing with "aboot"?

SGH-I467 - ATT Note 8
Hello lyriquidperfection,
Thanks to you and many other I was able to get root access to my SGH-i467. Thanks for the tools.
As a note, I had to convert, mount, and "chown root:root" the supersu.pk file after running ./rebuild_system. The permissions where set to my username. Not sure if your binary is correctly changing the permissions of the file?
Thanks again, :good:

ZeroxCorbin said:
Hello lyriquidperfection,
Thanks to you and many other I was able to get root access to my SGH-i467. Thanks for the tools.
As a note, I had to convert, mount, and "chown root:root" the supersu.pk file after running ./rebuild_system. The permissions where set to my username. Not sure if your binary is correctly changing the permissions of the file?
Thanks again, :good:
Click to expand...
Click to collapse
That doesn't matter as you are the one who will be launching it anyway. Works on my device on I9505.
Sent from my GT-I9505 using Tapatalk 4

[TUTORIAL] [Developer Edition] How to make an update tar

Hi guys,
In this thread, I will teach the Developer Edition owners how to make a tar file to update your device, and prevent your bootloader from being locked.
Requirements:
-Linux (It's possible on Windows with Cygwin, but I won't cover that here.) (Also possible on OS X but you need the GNU version of tar, you can get it with brew)
-Firmware tar
The most important step we will take in precaution is backing up your precious Developer Edition aboot. If your device accidentally gets locked, and you have this file, you can re-unlock your device.
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.bak
Move aboot.bak somewhere safe and hang on to it!
1. Extract the tar file using a file archiver like Engrampa or Archiver
You will have NON-HLOS.bin, modem.bin, sbl1.mbn, sdi.mbn, aboot.mbn, rpm.mbn, tz.mbn, boot.img, recovery.img, cache.img.ext4, system.img.ext4, and possibly a .pit file or a couple other files, but the latter listed are the important ones.
2. Open a terminal and change your directory to where you extracted your tar
Code:
cd /home/ryan/Downloads/firmware/
This is just an example
3. DELETE aboot.mbn
Code:
rm aboot.mbn
Or just right click and delete
4. Tar the files
Code:
tar -H ustar -c NON-HLOS.bin modem.bin sbl1.mbn sdi.mbn rpm.mbn tz.mbn boot.img recovery.img cache.img.ext4 system.img.ext4 > update.tar
You should now have a file called update.tar and it should roughly be the size of all the images combined.
5. Calculate MD5 for your update.tar
Code:
md5sum -t update.tar >> update.tar
6. Change the file name of update.tar to update.tar.md5 to reflect our new MD5
Code:
mv update.tar update.tar.md5
7. Flash your freshly baked update.tar.md5 in ODIN!
I will be making improvements to this tutorial and possibly adding a Windows tutorial with cygwin. Questions or comments, post and I shall answer!

I confirm this works with the latest 4.4.4 NI2 and the stock Kernel will boot!
Here is a ODIN flashable file:
https://www.androidfilehost.com/?fid=95784891001608429
This will flash boot.img, modem.bin, NON-HLOS.bin, rpm.mbn, sbl1.mbn, sdi.mbn and tz.mbn.
This will NOT flash, the bootloaded and the recovery

ryanbg said:
Hi guys,
In this thread, I will teach the Developer Edition owners how to make a tar file to update your device, and prevent your bootloader from being locked.
Requirements:
-Linux (It's possible on Windows with Cygwin, but I won't cover that here.) (Also possible on OS X but you need the GNU version of tar, you can get it with brew)
-Firmware tar
The most important step we will take in precaution is backing up your precious Developer Edition aboot. If your device accidentally gets locked, and you have this file, you can re-unlock your device.
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.bak
Move aboot.bak somewhere safe and hang on to it!
1. Extract the tar file using a file archiver like Engrampa or Archiver
You will have NON-HLOS.bin, modem.bin, sbl1.mbn, sdi.mbn, aboot.mbn, rpm.mbn, tz.mbn, boot.img, recovery.img, cache.img.ext4, system.img.ext4, and possibly a .pit file or a couple other files, but the latter listed are the important ones.
2. Open a terminal and change your directory to where you extracted your tar
Code:
cd /home/ryan/Downloads/firmware/
This is just an example
3. DELETE aboot.mbn
Code:
rm aboot.mbn
Or just right click and delete
4. Tar the files
Code:
tar -H ustar -c NON-HLOS.bin modem.bin sbl1.mbn sdi.mbn rpm.mbn tz.mbn boot.img recovery.img cache.img.ext4 system.img.ext4 > update.tar
You should now have a file called update.tar and it should roughly be the size of all the images combined.
5. Calculate MD5 for your update.tar
Code:
md5sum -t update.tar >> update.tar
6. Change the file name of update.tar to update.tar.md5 to reflect our new MD5
Code:
mv update.tar update.tar.md5
7. Flash your freshly baked update.tar.md5 in ODIN!
I will be making improvements to this tutorial and possibly adding a Windows tutorial with cygwin. Questions or comments, post and I shall answer!
Click to expand...
Click to collapse
Dude! Please I beg you to make this a youtube video.

razzrmaxx said:
Dude! Please I beg you to make this a youtube video.
Click to expand...
Click to collapse
there is a flashable file in post #2

Downgrade
B"H
So, using your methodology, can I take a Verizon developer edition phone (4.4.4 or 4.4.2), take a stock Consumer edition 4.4.2 version ROM, Tar it up, and flash to my developer edition?
This would be something important as I have software that needs 4.4.2 version, but can only find new Verizon S5 that are on 4.4.4.
Would this method also flash the 4.4.2 modem as well as kernel?
Thank you,
Dovid

dovid said:
B"H
So, using your methodology, can I take a Verizon developer edition phone (4.4.4 or 4.4.2), take a stock Consumer edition 4.4.2 version ROM, Tar it up, and flash to my developer edition?
This would be something important as I have software that needs 4.4.2 version, but can only find new Verizon S5 that are on 4.4.4.
Would this method also flash the 4.4.2 modem as well as kernel?
Thank you,
Dovid
Click to expand...
Click to collapse
Yes, you should be able to downgrade to 4.4.2, including modem and kernel.

dovid said:
B"H
So, using your methodology, can I take a Verizon developer edition phone (4.4.4 or 4.4.2), take a stock Consumer edition 4.4.2 version ROM, Tar it up, and flash to my developer edition?
This would be something important as I have software that needs 4.4.2 version, but can only find new Verizon S5 that are on 4.4.4.
Would this method also flash the 4.4.2 modem as well as kernel?
Thank you,
Dovid
Click to expand...
Click to collapse
As long as you don't touch aboot on a Dev Edition (always delete aboot.mbn from any tar you make), the answer is YES! :good:

razzrmaxx said:
Dude! Please I beg you to make this a youtube video.
Click to expand...
Click to collapse
It's rather easy to do. Just download an Ubuntu live cd image and burn it to a USB drive. Boot up, access your hard drive, extract tar to a folder, delete aboot.mbn, and then follow the instructions verbatim on my tutorial. It's a great learning experience, and figuring out how to do it is half the fun.

Two questions: First, where in ODIN do I flash the TAR? Second, do I flash the firmware first, or the ROM? Thanks in advance!

HTC-8690 said:
Two questions: First, where in ODIN do I flash the TAR? Second, do I flash the firmware first, or the ROM? Thanks in advance!
Click to expand...
Click to collapse
- Flash in ODIN using the AP button
- I don't think it does really matter, but you'll need both for proper behavior.

I am having difficulties flashing the file in post 2, tried downloading it from a different mirror as well.
Getting this in ODIN 3.09.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> G900V_DevEd_FirmwareOnly_NI2.tar.md5 is invalid.
<OSM> End...

neodawg said:
I am having difficulties flashing the file in post 2, tried downloading it from a different mirror as well.
Getting this in ODIN 3.09.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> G900V_DevEd_FirmwareOnly_NI2.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
My bad, I renamed the file after I processed the md5.
I will re upload a valid version. In the meantime you can remove the .md5 at the end of the file name and flash it like this. It will not verify the md5 and proceed though.

timeToy said:
My bad, I renamed the file after I processed the md5.
I will re upload a valid version. In the meantime you can remove the .md5 at the end of the file name and flash it like this. It will not verify the md5 and proceed though.
Click to expand...
Click to collapse
Thanks that worked, however it didnt fix the issue i was hoping it would have.
http://forum.cyanogenmod.org/topic/101909-verizon-dev-device-not-able-to-call/
if your interested in what my actual issue is.

Why do you delete the aboot?
Sent from my SM-G900V using XDA Premium 4 mobile app

Zooandbio4me said:
Why do you delete the aboot?
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you don't you will lock your bootloader. You can avoid this by backing it up with the beginning of this thread. Also remember that the aboot is specific to each device so you have to have your own. Back it up, actually just backup all partitions for safe keeping.

First off, thanks for the tip on backing up my bootloader! I used Terminal Emulator to pull the backup.
Could I use Terminal Emulator to repackage the firmware? I.e. download the firmware on your phone (or Windows PC), extract, delete the aboot (and maybe recovery), and use Terminal Emulator on your phone to repackage it.
I do have a jump drive with Ubuntu but I rarely use it. So rarely, that I end up spending a ton of time tinkering with Bios to get it to boot into it. It would be quicker for me to carefully type the command in on my phone since it is Linux based.
Not that anyone here would be brave (or dumb) enough to overwrite their $600 bootloader, but if so, how would we restore the backup?

Does anyone have a copy of the flashable zip for backing up the partitions and aboot? the link is dead.

ryanbg said:
Hi guys,
In this thread, I will teach the Developer Edition owners how to make a tar file to update your device, and prevent your bootloader from being locked.
Requirements:
-Linux (It's possible on Windows with Cygwin, but I won't cover that here.) (Also possible on OS X but you need the GNU version of tar, you can get it with brew)
-Firmware tar
The most important step we will take in precaution is backing up your precious Developer Edition aboot. If your device accidentally gets locked, and you have this file, you can re-unlock your device.
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.bak
Move aboot.bak somewhere safe and hang on to it!
1. Extract the tar file using a file archiver like Engrampa or Archiver
You will have NON-HLOS.bin, modem.bin, sbl1.mbn, sdi.mbn, aboot.mbn, rpm.mbn, tz.mbn, boot.img, recovery.img, cache.img.ext4, system.img.ext4, and possibly a .pit file or a couple other files, but the latter listed are the important ones.
2. Open a terminal and change your directory to where you extracted your tar
Code:
cd /home/ryan/Downloads/firmware/
This is just an example
3. DELETE aboot.mbn
Code:
rm aboot.mbn
Or just right click and delete
4. Tar the files
Code:
tar -H ustar -c NON-HLOS.bin modem.bin sbl1.mbn sdi.mbn rpm.mbn tz.mbn boot.img recovery.img cache.img.ext4 system.img.ext4 > update.tar
You should now have a file called update.tar and it should roughly be the size of all the images combined.
5. Calculate MD5 for your update.tar
Code:
md5sum -t update.tar >> update.tar
6. Change the file name of update.tar to update.tar.md5 to reflect our new MD5
Code:
mv update.tar update.tar.md5
7. Flash your freshly baked update.tar.md5 in ODIN!
I will be making improvements to this tutorial and possibly adding a Windows tutorial with cygwin. Questions or comments, post and I shall answer!
Click to expand...
Click to collapse
I understand that to execute the dd command you have to do it in the phone itself through terminal emulator or something like this , right? when I do it I get the message "Permission denied". What am I missing?
On the other hand I need a little help on this as I find myself trying to follow this guide through the rooting one: http://forum.xda-developers.com/showthread.php?t=2784880
That guide says that this is to not to get a locked bootloader, but I see that in this guide you appliy an update and I am not sure how this works (new at rooting phones) . Can you enlighten me on really what I have to do? I would really appreciate it.
Thanks a lot!

_msl_ said:
I understand that to execute the dd command you have to do it in the phone itself through terminal emulator or something like this , right? when I do it I get the message "Permission denied". What am I missing?
On the other hand I need a little help on this as I find myself trying to follow this guide through the rooting one: http://forum.xda-developers.com/showthread.php?t=2784880
That guide says that this is to not to get a locked bootloader, but I see that in this guide you appliy an update and I am not sure how this works (new at rooting phones) . Can you enlighten me on really what I have to do? I would really appreciate it.
Thanks a lot!
Click to expand...
Click to collapse
Based upon your posts in other threads, you cannot use this guide. The guide in this thread is for the developer edition of the Verizon Galaxy S5, which could only be bought through Samsung I believe. From what I can tell from your other posts, you most likely have the retail version. The retail version has a locked bootloader, the developer edition does not. That is why this operation can be performed on the developer edition and not the retail version. If you bought your phone privately and not from Verizon, it would have been clearly identified as a developer edition by the seller. If it was not identified as a developer edition by the seller you definitely have the retail version. And like I said, you cannot use this guide. That's why the title of this thread is clearly identified for the developer edition only.

landshark68 said:
Based upon your posts in other threads, you cannot use this guide. The guide in this thread is for the developer edition of the Verizon Galaxy S5, which could only be bought through Samsung I believe. From what I can tell from your other posts, you most likely have the retail version. The retail version has a locked bootloader, the developer edition does not. That is why this operation can be performed on the developer edition and not the retail version. If you bought your phone privately and not from Verizon, it would have been clearly identified as a developer edition by the seller. If it was not identified as a developer edition by the seller you definitely have the retail version. And like I said, you cannot use this guide. That's why the title of this thread is clearly identified for the developer edition only.
Click to expand...
Click to collapse
I had no idea about this developer and not developer edition. Thanks a lot for the info, it makes sense now.

[TUT]Custom Splash screen - S7 Flat/Edge

Hi all. I just want to share how to change your splash screen, if ever you want a customized one. I created my own, for SuperMan-Rom. So without further ado, here's the tutorial:
NOTE: Tested perfectly on SuperMan-Rom without any problems.
Pre-requisites:
- PC
- Android SDK
- ADB
- Knowledge in adb codes
- Rooted device
- Back up!
Steps:
1.) Open CMD on your PC - make sure your phone is connected and has usb debugging enabled.
2.) Now type adb devices - this will serve as confirmation that your device is detected in adb.
3.) Allow any request for superuser permission in your phone.
now for the codes:
4.)On CMD, type:
adb shell
Click to expand...
Click to collapse
5.)Now type:
su
Click to expand...
Click to collapse
6.)Now it's time to pull out the param.bin, which contains the splash logo:
dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096
Click to expand...
Click to collapse
7.)Now we must create a folder on main sd card:
mkdir /sdcard/param
Click to expand...
Click to collapse
8.)Then enter the directory:
cd /sdcard/param
Click to expand...
Click to collapse
9.)And untar the param.bin into the created folder:
tar xf /sdcard/param.bin
Click to expand...
Click to collapse
If all goes well, you can see a param folder in your main sdcard (mine is in internal memory), which has all the bootloader's images. Just copy the logo.jpg to your PC.
10.)Now you can edit the logo.jpg to your liking - note that the background should remain black, and the size should not be more than 400KB.
11.)Once done editing, copy your customized logo.jpg on main sd card
12.)Then, we have to paste it inside /sdcard/param folder, and retar param.bin:
cp -f /sdcard/logo.jpg /sdcard/param/logo.jpg
rm -f /sdcard/param.bin
cd sdcard/param
tar cf - `ls | sort -t.` > /sdcard/param.bin
Click to expand...
Click to collapse
13.)Lastly, we need to return param.bin in system:
dd if=/sdcard/param.bin of=/dev/block/sda4 bs=4096
Click to expand...
Click to collapse
After these steps, reboot!
VOILA! Now you have your won splash image!
I created some for SuperMan-Rom below for those who want it. Also attached default splash image.
Credits to all that needs to be credited!

Bro I need S7 Stock Boot Logo

parth111999 said:
Bro I need S7 Stock Boot Logo
Click to expand...
Click to collapse
Here it is.

@MitoTakatori where's your stock param.bin? i need that, thanks

MitoTakatori said:
Here it is.
Click to expand...
Click to collapse
Bro i Need S7 boot Logo
Not Animation

Hello
it does not work .
I receive this mistake
Tar: warning_L. Jpg: cant open: Read-only file system
Tar: chow 1000: 1000 'warning_L. Jpg ': No such file or directory

HELP! I can't untar the param.bin file!
MitoTakatori said:
Hi all. I just want to share how to change your splash screen, if ever you want a customized one. I created my own, for SuperMan-Rom. So without further ado, here's the tutorial:
NOTE: Tested perfectly on SuperMan-Rom without any problems.
Pre-requisites:
- PC
- Android SDK
- ADB
- Knowledge in adb codes
- Rooted device
- Back up!
Steps:
1.) Open CMD on your PC - make sure your phone is connected and has usb debugging enabled.
2.) Now type adb devices - this will serve as confirmation that your device is detected in adb.
3.) Allow any request for superuser permission in your phone.
now for the codes:
4.)On CMD, type:
5.)Now type:
6.)Now it's time to pull out the param.bin, which contains the splash logo:
7.)Now we must create a folder on main sd card:
8.)Then enter the directory:
9.)And untar the param.bin into the created folder:
If all goes well, you can see a param folder in your main sdcard (mine is in internal memory), which has all the bootloader's images. Just copy the logo.jpg to your PC.
10.)Now you can edit the logo.jpg to your liking - note that the background should remain black, and the size should not be more than 400KB.
11.)Once done editing, copy your customized logo.jpg on main sd card
12.)Then, we have to paste it inside /sdcard/param folder, and retar param.bin:
13.)Lastly, we need to return param.bin in system:
After these steps, reboot!
VOILA! Now you have your won splash image!
I created some for SuperMan-Rom below for those who want it. Also attached default splash image.
Credits to all that needs to be credited!
Click to expand...
Click to collapse
So I tried multiple times your steps and deleted the files all over again. I keep getting stuck at this part
[email protected]:/sdcard/param # tar xf /sdcard/param.bin
tar: invalid tar format
1|[email protected]:/sdcard/param #

silentwind827 said:
So I tried multiple times your steps and deleted the files all over again. I keep getting stuck at this part
[email protected]:/sdcard/param # tar xf /sdcard/param.bin
tar: invalid tar format
1|[email protected]:/sdcard/param #
Click to expand...
Click to collapse
Hi. So you are using T Mobile? I have not tried it with T Mobile, but were you able to fetch your param.bin file?

pendor24 said:
Hello
it does not work .
I receive this mistake
Tar: warning_L. Jpg: cant open: Read-only file system
Tar: chow 1000: 1000 'warning_L. Jpg ': No such file or directory
Click to expand...
Click to collapse
Hi. What ROM are you in and what device model do you have?

zainifame said:
@MitoTakatori where's your stock param.bin? i need that, thanks
Click to expand...
Click to collapse
Why do you need my param.bin?

parth111999 said:
Bro i Need S7 boot Logo
Not Animation
Click to expand...
Click to collapse
I'll try to extract the image. Remember, it is in qmg format.

MitoTakatori said:
Hi. What ROM are you in and what device model do you have?
Click to expand...
Click to collapse
S7 bord nougat XXU1DPLT

pendor24 said:
S7 bord nougat XXU1DPLT
Click to expand...
Click to collapse
You mean stock nougat?

Yes Slightly deified with deodex, 3 minit, and other customizations

pendor24 said:
Yes Slightly deified with deodex, 3 minit, and other customizations
Click to expand...
Click to collapse
I see. S7 flat?

G935f ,
flat?

pendor24 said:
G935f ,
flat?
Click to expand...
Click to collapse
Oh, sorry. It should work as long as you are rooted and usb debugging is enabled. On your PC, you should have adb installed, with android SDK.

Param.bin
MitoTakatori said:
Hi. So you are using T Mobile? I have not tried it with T Mobile, but were you able to fetch your param.bin file?
Click to expand...
Click to collapse
Yes I can extract the param.bin file and also put it on my pc if you need me to. I just need to unzip it. It keeps failing for some reason. Maybe Im grabbing the wrong file and naming it param.bin within the code you provided?

silentwind827 said:
Yes I can extract the param.bin file and also put it on my pc if you need me to. I just need to unzip it. It keeps failing for some reason. Maybe Im grabbing the wrong file and naming it param.bin within the code you provided?
Click to expand...
Click to collapse
Hi. When you extract param.bin, it will be on your main sd card(internal memory), and it's name will be param.bin. When you execute the code, check first in your internal memory if it copied the param.bin. And no need to copy it to PC for extraction.
Just to be sure you can attach the param.bin you extracted and I'll take a look!

MitoTakatori said:
Hi. When you extract param.bin, it will be on your main sd card(internal memory), and it's name will be param.bin. When you execute the code, check first in your internal memory if it copied the param.bin. And no need to copy it to PC for extraction.
Just to be sure you can attach the param.bin you extracted and I'll take a look!
Click to expand...
Click to collapse
Well yeah. I see the file. When I try to extract the file from the param.bin to /sdcard/param/ it fails. HELP!

Conversion of one file type to another for purposes you will not be informed of. (intentionally vague)

HOW, in detail, step by step, can I take stock firmware in the Samsung 4 file format tar.md5, and somehow, with minimal extra steps, create a flashable zip file with it?

If you're on a Windows computer, use 7Zip tool to untar & zip an archive
More info here:
https://allthings.how/how-to-use-7-zip-in-windows-11/
BTW:
You can untar a .TAR via Windows command prompt, too:
Code:
tar -xf <TAR-FILE>

jwoegerbauer said:
If you're on a Windows computer, use 7Zip tool to untar & zip an archive
More info here:
https://allthings.how/how-to-use-7-zip-in-windows-11/
BTW:
You can untar a .TAR via Windows command prompt, too:
Code:
tar -xf <TAR-FILE>
Click to expand...
Click to collapse
So it is that easy? No special hand coded files to direct things or anything like that? So when people say a "flashable zip", it's no different internally than the tarballs are? Just decompress one and compress into the other? I had a suspicion it might be that way, but everyone has been so cryptic with other users, and just refusing to answer, I thought it must be more complicated than that. Thank you very much for the straight answer, I am very grateful.
So i state this as overtly as possible for posterity: nothing signifies a flashable zip as different than an ordinary zip other than the contents, which are identical to the contents of a tar archive. Easy.

Can I unpack Huawei firmware UPDATE.app, repack and flash it?

Hi this might be the strangest request or question you will ever see but, can I unpack Huawei firmware UPDATE.app, repack it and flash it successfully (I know unpacking then repacking and flashing could cuse problems)? I want to unpack it becuase I want to change permission of system partitons, by doing that I will be able to root my Honor 6x from PC via USB becuase of cours system files are read-only, means system files can't be modfied / Android be rooted.
Why I need to do that? because there is a adb command requires root that will let me able to access and show bootloader unlock code.
Here is the command:
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"

muhammadbahaa2001 said:
Hi this might be the strangest request or question you will ever see but, can I unpack Huawei firmware UPDATE.app, repack it and flash it successfully (I know unpacking then repacking and flashing could cuse problems)? I want to unpack it becuase I want to change permission of system partitons, by doing that I will be able to root my Honor 6x from PC via USB becuase of cours system files are read-only, means system files can't be modfied / Android be rooted.
Why I need to do that? because there is a adb command requires root that will let me able to access and shows bootloader unlock code.
Here is the command:
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
Click to expand...
Click to collapse
Modifying the app won't allow you to root your device, that isnt how it works. Anything you try to flash using the update app won't work unless the bootloader is unlocked before it is applied.

Droidriven said:
Modifying the app won't allow you to root your device, that isnt how it works. Anything you try to flash using the update app won't work unless the bootloader is unlocked before it is applied.
Click to expand...
Click to collapse
Can I at least unpack recovery.img and patch recovery_ramdisk.img using magisk and repack it again in recovery.img/UPDATE.APP then flash it?

muhammadbahaa2001 said:
Can I at least unpack recovery.img and patch recovery_ramdisk.img using magisk and repack it again in recovery.img/UPDATE.APP then flash it?
Click to expand...
Click to collapse
You can't flash it with locked BL...
Try getting it unlocked tho - There are guys that do unlocks for 20/30$ just search for it

Can
Rstment ^m^ said:
You can't flash it with locked BL...
Try getting it unlocked tho - There are guys that do unlocks for 20/30$ just search for it
Click to expand...
Click to collapse
Can't restore it from SD card through download mode until BL is unlocked?

muhammadbahaa2001 said:
Can
Can't restore it from SD card through download mode until BL is unlocked?
Click to expand...
Click to collapse
Nope it's modified hence the signature is changed... Probably there is no verified boot since it's older device but either way you'd have to pass signature check when flashing with built in updater...
Idk much about how in built updater works tbh , but if it's older android maybe there are some exploits you could use to gain root access that don't involve flashing

muhammadbahaa2001 said:
Can I at least unpack recovery.img and patch recovery_ramdisk.img using magisk and repack it again in recovery.img/UPDATE.APP then flash it?
Click to expand...
Click to collapse
You cannot flash modified or customized software, you can only flash unmodified stock software, a locked bootloader will not allow flashing or booting anything except the software created by the manufacturer for the device.
You keep asking the same question in different ways. It doesn't matter how you change your question, the answer is still no. You will not be able to flash anything that is modified until you unlock the bootloader.
There are some PC programs and android apps that can root some devices without having to unlock the bootloader or flash modified files.
Do a Google search for:
"Universal android rooting programs for PC"
And
"Universal rooting apps for android"
If your device has android 7 or newer, these programs and apps probably won't work on your device.