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!
Related
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
There is a Perl script which can unpack boot and recovery (CG35 & CG47) in this thread: http://forum.xda-developers.com/showthread.php?t=443994
Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
CG64.smg & CG65.smg: partition tables that you can open using fdisk/sfdisk
CG33.smg is a CDROM ISO file!
iirc one or two of them are the splash image (not 100% sure now)
Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
rachit2588 said:
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
Click to expand...
Click to collapse
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
^very good idea
danimagrin said:
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
Click to expand...
Click to collapse
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
rachit2588 said:
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
Click to expand...
Click to collapse
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
danimagrin said:
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
Click to expand...
Click to collapse
with mkyaffs2image its jus showing me a cmd windows for some less thn 1 sec and its jus goes away...please upload the version you are using...also let me know if it needs any prerequisite software to be installed.
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
oh , ok.. its working..thanks
danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
ok last doubt...after creating system.img can it be restored via custom recovery..??
how to add md5 check sums for that so that custom recovery can identify as proper nandorid..!!??
rachit2588 said:
oh , ok.. its working..thanks
Click to expand...
Click to collapse
You welcome!
Sure you can use it with nandroid, you must download md5sum.exe, place it together with mkyaffs2image, after you used mkyaffs2image then type "md5sum system.img" and it will generate checksum. Create a file called "nandroid.md5" and paste what md5sum returned. You can open a nandroid.md5 file of another backup and you'll understand better how it's done..
excellent..i got it
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
rachit2588 said:
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
Click to expand...
Click to collapse
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
danimagrin said:
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
Click to expand...
Click to collapse
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
rachit2588 said:
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
Click to expand...
Click to collapse
I'll test it as soon as I get home and then I tell you!
There you go
http://www.lgmobiles.com/gsm/download/P920 V20B (Gingerbread Version).zip
To root the bin file (instructions based on the one here)
Requirements: WinHex, a Linux distro (VMs work fine), drivers and flasher.
Instructions
1. Extract and open LGP920AT-00-V20b-ESA-XXX-JAN-10-2012+0_AP.bin in WinHex or any other hex editor.
2. Use WinHex to dump the content from offset B80000 (hexadecimal) to the end (select B80000 as start block and 22ABFFFF as end block and copy it to a new file), and save the dump as system.img.
3. Copy the .img to your Linux distro. Place it in the desktop. Now open terminal, cd to Desktop and enter the following commands one by one:
sudo mkdir temp
sudo mount -o loop system.img temp
Click to expand...
Click to collapse
What this does is mount the img into the temp folder. However, the files are read only. To copy su and superuser.apk, download both file, place them in the Desktop and enter the following commands:
sudo cp superuser.apk temp/app
sudo cp su temp/bin
Click to expand...
Click to collapse
Now, you have to set permissions for su and superuser.apk.
cd temp/app
sudo chmod 0644 superuser.apk
cd
cd Desktop/temp/bin
sudo chmod 6755 su
Click to expand...
Click to collapse
To save the changes, enter this:
sudo umount temp
Click to expand...
Click to collapse
Now, copy image.img back to Windows or whichever environment you prefer.
4. Copy the contents of the img file in WinHex. Go back to the bin file in WinHex and remove any data from offset B80000 onwards. You should be left with offsets 0 to B7FFFF. Right click block B7FFFF, select clipboard data > paste and accept all the prompts. You can now save the .bin file.
5. Now, it's time to flash the .bin. Extract the drivers somewhere and install "LGUnitedMobileDriver_S497CA20_WHQL_ML_Ver_1.0 .exe" and "LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.exe". Then, extract the flasher to another location.
6. With the .bin and .fls (found in the zip file containing the .bin as well) in hand, turn your phone off and remove both SD and SIM cards.
MAKE A BACKUP BEFORE PROCEEDING. THIS PROCEDURE WIPES SYSTEM AND APPS. DATA SUCH AS MUSIC AND IMAGES WILL REMAIN INTACT.
Click to expand...
Click to collapse
7. Hold volume up button while inserting the usb cable. When your computer detects the phone, let go of the button.
8. Once the driver installs, run B_SmartFlashTool_Extern.exe, go to the ROM copy D/L tab
9. Select the .bin file under CP bin and the .fls file under AP .bin.
10. Click start. Don't touch anything.
11. Once it's done, close the flasher, unplug your phone and insert the SIM and SD cards and turn it on.
12. Done
Zip file contains both .fls and .bin files.
So it seems roms based on v20B might be in the works
EDIT: Not going to upload, has been superseded by v20E and the Megatron exploit.
Hello! Please laid out links to the program.
http://file.karelia.ru/3jw96r/
LGP920AT-00-V20e (no patched)
Please patch file!
Sent from my LG-P920 using xda premium
he's uploading the v20b bin as we speak, also someone might need to make a thread on "patched firmware" if people are finding more .bin files
I'm 30% through the second zip file, Mediafire only allows maximum 200MB per file so I had to split up the .bin. It should be up in about an hours' time.
SnegovikRZN said:
http://file.karelia.ru/3jw96r/
LGP920AT-00-V20e (no patched)
Click to expand...
Click to collapse
Can somebody patch this bin. I think this is newest ROM 18.01.2012.
dr_jerremy said:
Can somebody patch this bin. I think this is newest ROM 18.01.2012.
Click to expand...
Click to collapse
I'm downloading it now, download speeds are really slow. I'll take a look once it finishes downloading.
pandaball said:
I'm downloading it now, download speeds are really slow. I'll take a look once it finishes downloading.
Click to expand...
Click to collapse
I'm almost done with dowloading,but i dont know how to patch :S..... I will try
EDIT: Bin. V20E 18.01.2012
Follow the updated instructions, they should be concise enough to follow.
In other news, I realised I forgot to set permissions for superuser.apk and su. So, I have to reupload everything due to my mistake. Sorry guys, I can only upload everything tomorrow as it's getting late
@SnegovikRZN If you could create patched ROMs for P920 as you did with the P970 that would be great
pandaball said:
Follow the updated instructions, they should be concise enough to follow.
In other news, I realised I forgot to set permissions for superuser.apk and su. So, I have to reupload everything due to my mistake. Sorry guys, I can only upload everything tomorrow as it's getting late
@SnegovikRZN If you could create patched ROMs for P920 as you did with the P970 that would be great
Click to expand...
Click to collapse
Can I say I'm first?
pandaball said:
Can I say I'm first?
Click to expand...
Click to collapse
i'll bring my thumbdrive over jk
Я не могу создать прошивку для p920, так как там немножко другая структура...
Ohh the ANDROID! string is missing... ok, no problem
in the 20e the entry 22ABFFFF is missing..
Maybe for V20E:
2249FFF0
I can't flash patched rom with Lg flash tool..
Oh I figured out what's the problem
Seem V20B having more options to root it.
hondymondy said:
Seem V20B having more options to root it.
Click to expand...
Click to collapse
Not really, most new roms would be rebased on v20E so I would recommend those
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
Stock splash screen without the warning message for rooted S10+ devices
Completely stock splash screen
All warnings have been removed
WARNING: Flash at your own risk!
Directions
Download attachment
Place attachment into download folder in internal storage
Check md5sum - c2a9b95389b037800693638d4a1c4fc6
Flash splash screen with a terminal emulator
- Check md5sum
Code:
su -c md5sum /storage/emulated/0/Download/up_param.zip
- Flash splash screen
Code:
su -c dd if=/storage/emulated/0/Download/up_param.zip of=/dev/block/platform/13d60000.ufs/by-name/up_param
Excellent work ! Thanksss
It works great but there are some red pixels visible. You couldn't paint these text well, lol thanks anyway. Hope you can fix it soon.
ulasx said:
It works great but there are some red pixels visible. You couldn't paint these text well, lol thanks anyway. Hope you can fix it soon.
Click to expand...
Click to collapse
Fixed :good:
For S10 how can i do?
Ivymike52 said:
For S10 how can i do?
Click to expand...
Click to collapse
I not sure if it's the same path but try enter code in terminal and upload up_param.zip from your internal storage and I'll do it for you.
Code:
su -c cp /dev/block/platform/13d60000.ufs/by-name/up_param /storage/emulated/0/up_param.zip
thank you, i had just made extracting up_param from your archive, modifying 3 files and recreating archive, but good for next time.
Can this be flashed via twrp? as i've never in my years flashing roms etc, used terminal
Thank you
Wingchundub said:
Can this be flashed via twrp? as i've never in my years flashing roms etc, used terminal
Thank you
Click to expand...
Click to collapse
No, it's not a zip file you can flash with twrp, you could maybe use the terminal in twrp.
Easier just to download Terminal Emulator from Playstore, just uninstall it if not needed afterwards.
Sorry, i'm lost here, installed terminal you linked too, downloaded zip and its in download folder, as i start to type the check md5sum code, most of it disappears and leaves just the / icons,then when i press enter, it says not found or something like that
Also tried putting internal storage instead of storage, as that's where mine is located and it comes up with "Can't execute"
Wingchundub said:
Sorry, i'm lost here, installed terminal you linked too, downloaded zip and its in download folder, as i start to type the check md5sum code, most of it disappears and leaves just the / icons,then when i press enter, it says not found or something like that
Also tried putting internal storage instead of storage, as that's where mine is located and it comes up with "Can't execute"
Click to expand...
Click to collapse
Type su then enter and grant su permission in magisk dialog that pops up. Then just copy and paste the commands.
I type su and usual magisk window doesn't show, losing will to live lol
Just to be clear, phone is in root mode.
Wingchundub said:
I type su and usual magisk window doesn't show, losing will to live lol
Just to be clear, phone is in root mode.
Click to expand...
Click to collapse
You must of dismissed it. Just enable it in magisk manager, side menu, superuser.
I haven't bud, Terminal never requested root access
Will this work on s10 plus snapdragon sm-g9750?
Thanks
I also want to know this (9750)
Loco007 said:
Will this work on s10 plus snapdragon sm-g9750?
Thanks
Click to expand...
Click to collapse
twiice said:
I also want to know this (9750)
Click to expand...
Click to collapse
Enter code in terminal and upload up_param.zip from internal storage so I can check
Code:
su -c cp /dev/block/platform/13d60000.ufs/by-name/up_param /storage/emulated/0/up_param.zip
hinxnz said:
Enter code in terminal and upload up_param.zip from internal storage so I can check
Code:
su -c cp /dev/block/platform/13d60000.ufs/by-name/up_param /storage/emulated/0/up_param.zip
Click to expand...
Click to collapse
Seem to get an error message
hinxnz said:
Enter code in terminal and upload up_param.zip from internal storage so I can check
Code:
su -c cp /dev/block/platform/13d60000.ufs/by-name/up_param /storage/emulated/0/up_param.zip
Click to expand...
Click to collapse
Hi, I have found this on my s10 plus sm-g9750 Snapdragon but at the location below:-
/dev/block/platform/soc/1d84000.ufshc/by-name/param
Attached param file as a rar file, this is all i could see, will this work?
Loco007 said:
Hi, I have found this on my s10 plus sm-g9750 Snapdragon but at the location below:-
/dev/block/platform/soc/1d84000.ufshc/by-name/param
Attached param file as a rar file, this is all i could see, will this work?
Click to expand...
Click to collapse
That's not it but try this location
Code:
/dev/block/platform/soc/1d84000.ufshc/by-name/up_param
Hello
How is a bootloader available as a tar.md5 file to flash in Odin? Is it possible to take the bootloader out of a Stock or Rooted ROM? Does it come from the boot.img file in some way ? Any help would be great.
Thanks in advance
[Guide] How and Where to Ask a Question on XDA
[Guide] How and Where to Ask a Question on XDA Read the Forum Rules Announcement: Forum Rules by MikeChannon (Forum Admin) Search before asking Use the XDA search to see if your device has it's own Subforum or Enhanced Device Tag e.g...
forum.xda-developers.com
Fixed title of the thread, but this is a general Android question and not for a specific phone so I hope it is in the right section
seskanda said:
... not for a specific phone...
Click to expand...
Click to collapse
Not really, odin is a Samsung only tool.
So you must have a Samsung device.
And most android devices, the bootloader would need to be unlocked, to pull a copy of the bootloader.
sd_shadow said:
Not really, odin is a Samsung only tool.
So you must have a Samsung device.
Click to expand...
Click to collapse
Wow I had no idea Odin is a Samsung only tool
Yes it is Sprint Galaxy S5, does thread need to be moved now?
I see is any way to know if the bootloader is unlocked? And if not,
then can it be done?
If device's Android is rooted a device's bootloader typically gets extracted by means of a Windows CMD script what is simlar to this one
Code:
adb devices
for /F %%a in ('adb shell "su -c 'ls -l /dev/block/platform/msm_sdcc.1/by-name/boot'"') do (set blk_device=%%a)
adb exec-out "su -c 'dd if=%blk_device% bs=4096'" > "C:\boot.img"
My Sprint Galaxy S5 is rooted what kind of file does this command output? Is it an IMG file? I'm looking for a TAR.MD5 file, and need it from a firmware/ROM that is not on the phone.
seskanda said:
My Sprint Galaxy S5 is rooted what kind of file does this command output? Is it an IMG file? I'm looking for a TAR.MD5 file, and need it from a firmware/ROM that is not on the phone.
Click to expand...
Click to collapse
A tar.md5 should just be a text file for the checksum from the .tar file you are trying to flash?
sd_shadow said:
A tar.md5 should just be a text file for the checksum from the .tar file you are trying to flash?
Click to expand...
Click to collapse
I'm not really sure but let's say you are right I will be needing at least a .tar file of the bootloader from a firmware/ROM
seskanda said:
I'm not really sure but let's say you are right I will be needing at least a .tar file of the bootloader from a firmware/ROM
Click to expand...
Click to collapse
I would look for firmware for your exact model here something like SM-G90xx
Samsung Galaxy S 5
The Samsung Galaxy S 5 is the successor to the popular Galaxy S 4. The 5.1" Super AMOLED display has a resolution of 1080x1920. The Galaxy S 5 is powered by a 2.5 GHz Qualcomm Snapdragon 801 processor with 2GB RAM. Internal storage comes in at either 16GB or 32GB, with a microSD slot up to...
forum.xda-developers.com
sd_shadow said:
A tar.md5 should just be a text file for the checksum from the .tar file you are trying to flash?
Click to expand...
Click to collapse
A TAR.MD5-file ( used by firmware update and kernel flashing applications like Odin and Heimdall for Samsung Android devices ) contains a TAR archive that has been verified with an MD5 checksum; the TAR file contains firmware and other system data, while the .MD5 extension verifies that no data is corrupted.
sd_shadow said:
I would look for firmware for your exact model here something like SM-G90xx
Samsung Galaxy S 5
The Samsung Galaxy S 5 is the successor to the popular Galaxy S 4. The 5.1" Super AMOLED display has a resolution of 1080x1920. The Galaxy S 5 is powered by a 2.5 GHz Qualcomm Snapdragon 801 processor with 2GB RAM. Internal storage comes in at either 16GB or 32GB, with a microSD slot up to...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok it is SM-G900P w/ Android 4.4.2 NE5 rooted and Knox 0x0. I'd like to upgrade to Android 5.0 OA6 and keep Knox and root.
Yes that is a good explaination of what the TAR.MD5 file is. I'm never able to find a TAR file without MD5 as that verifies it. I've read that to upgrade to Android 5.0 with root and Knox may need a TAR.MD5 of the bootloader for the OA6 firmware. I have OA6 ROM file but no clue how to get bootloader from it.
If a .TAR.MD5 suffixed archive file is needed, then change archive file's .TAR suffix to .TAR.MD5
I do not have a .TAR or .TAR.MD5 file of any bootloader and that command you gave does not work it says "%%a was unexpected at this time" after the second line.
seskanda said:
command you gave does not work it says "%%a was unexpected at this time" after the second line.
Click to expand...
Click to collapse
Put the code example shown above into a Windows command file ( .BAT-file ) and it should work.
seskanda said:
I have OA6 ROM file but no clue how to get bootloader from it.
Click to expand...
Click to collapse
If ROM comes as .ZIP-file then extract the .ZIP-file with any ZIP software: the boot.img file should be right there at the root of the archive.
jwoegerbauer said:
Put the code example shown above into a Windows command file ( .BAT-file ) and it should work.
Click to expand...
Click to collapse
No, I get 'error: closed' when I run the .bat file as Administrator and it outputs a boot.img file that is 0 bytes in C:\
jwoegerbauer said:
If ROM comes as .ZIP-file then extract the .ZIP-file with any ZIP software: the boot.img file should be right there at the root of the archive.
Click to expand...
Click to collapse
Yes the OA6 ROM is a ZIP file that Windows is able to open by itself, and I see a boot.img file in there. But even if this is the boot loader how can it be turned into a .TAR or TAR.MD5 file to flash in Odin?
seskanda said:
Yes the OA6 ROM is a ZIP file that Windows is able to open by itself, and I see a boot.img file in there. But even if this is the boot loader how can it be turned into a .TAR or TAR.MD5 file to flash in Odin?
Click to expand...
Click to collapse
Look inside here:
How To Use Tar On Windows 10
How To Use Tar On Windows 10
www.addictivetips.com
jwoegerbauer said:
Look inside here:
How To Use Tar On Windows 10
How To Use Tar On Windows 10
www.addictivetips.com
Click to expand...
Click to collapse
Ok let's say I make a .TAR file from boot.img all I have to do is rename it to TAR.MD5 and Odin will flash it ?