So, I unlocked the bootloader on my SM-G780G, downloaded the ROM that fits my model, region and all (triple checked it), however when I went to replace system.img, there is no system.img. I looked into all the files, AP and the others that I don't remember now, and the closest to system.img is super.img on AP, which is a huge file, as would system.img be I guess.
Any tips on what to do here?
You want to flash a custom ROM?
Also something about super.img:
Editing system.img inside super.img and flashing our modifications
I'm trying to modify my system.img (/system/build.prop) to include support for multi users. After struggling a lot, I've succeeded following your guide (that's an awesome work btw) to unpack, mount, modify, umount and repack super.img. Then...
forum.xda-developers.com
You need to run an Ubuntu Linux operating system virtual box (or use an online emulator of Ubuntu and transfer files via Google drive)
senpi0 said:
So, I unlocked the bootloader on my SM-G780G, downloaded the ROM that fits my model, region and all (triple checked it), however when I went to replace system.img, there is no system.img. I looked into all the files, AP and the others that I don't remember now, and the closest to system.img is super.img on AP, which is a huge file, as would system.img be I guess.
Any tips on what to do here?
Click to expand...
Click to collapse
files ending in .tar are archives you've got to open up. look in super for smaller archives.
Related
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
EDIT: If you can't run the script with the ./ command, chmod +x the file
Antonyb1995 said:
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
Click to expand...
Click to collapse
work on gt-i8200n to?
linklusitano said:
work on gt-i8200n to?
Click to expand...
Click to collapse
No reason why not, I'm just not able to test others
Antonyb1995 said:
No reason why not, I'm just not able to test others
Click to expand...
Click to collapse
testing
linklusitano said:
testing
Click to expand...
Click to collapse
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Antonyb1995 said:
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Click to expand...
Click to collapse
how do i run worker.txt?
linklusitano said:
how do i run worker.txt?
Click to expand...
Click to collapse
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Antonyb1995 said:
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Click to expand...
Click to collapse
windows 8.1
linklusitano said:
windows 8.1
Click to expand...
Click to collapse
Ah okay, If you install Cygwin you can run bash scripts in Windows.
LINK: https://www.cygwin.com/
Hello community,
I'm currently trying to modify the stock rom for my GT-I8200n. I didn't find cwm for the S III mini VE, and the version of twrp I found was very buggy. So I need an odin-compatible flash file for my rom. I tried to modify the stock rom by downloading the .tar.md5 from sammobile, unpacked it with winrar and copied the system.img into an ubuntu-VM. After that I created a sys.img (or sys.raw, same problem) out of system.img using the simg2img-file I found somewhere here on xda, mounted sys.img (or sys.raw) and modified it. Then I unmounted it and used img2simg to create my system_new.img. Copied it to my windows system, into the unpacked stock rom folder, renamed it to system.img, overwriting the old system.img and packed everything into a .tar file using ZArc. Now while flashing my ROM, odin works on the system.img for some minutes and then shows a fail.
Does anyone know what I'm doing wrong?
P.S.: I tried simply using simg2img on my stock system.img and then - without mounting and modifying - used img2simg kn the sys.img file. Same problem with odin and I noticed that my new system.img is approximately 50 mb smaller than the stock img, although I didn't modify it.
I hope I described my problem well (I'm not an english native speaker, but did my best to make this text understandable )
Any ideas or hints that could maybe solve this problem are welcome.
Thank you,
Chris
I have the same problem
any solution ?
Hey there,
I've tried searching about the forum and haven't been able to find the specifics about this:
I've got my un-encrypted .tar.md5 files from the last initialization, but there are 3 files and I'm wondering how I go about converting them into one image or what's actually necessary so that I can have the added convenience/stop burdening sammys server.
AP_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: system.img, recovery.img and boot.img.
BL_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: sboot.bin and param.bin
CSC_XAR_T710XAR2BOL3_CL6649608_QB7749942_REV03_user_low_ship.tar.md5 contains: hidden.img, GTS28WIFI_EUR_OPEN.pit and cache.img.
Let me know, thanks. :good:
wirelesskebab said:
Hey there,
I've tried searching about the forum and haven't been able to find the specifics about this:
I've got my un-encrypted .tar.md5 files from the last initialization, but there are 3 files and I'm wondering how I go about converting them into one image or what's actually necessary so that I can have the added convenience/stop burdening sammys server.
AP_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: system.img, recovery.img and boot.img.
BL_T710XXU2BOL6_CL6649608_QB7907593_REV03_user_low_ship.tar.md5 contains: sboot.bin and param.bin
CSC_XAR_T710XAR2BOL3_CL6649608_QB7749942_REV03_user_low_ship.tar.md5 contains: hidden.img, GTS28WIFI_EUR_OPEN.pit and cache.img.
Let me know, thanks. :good:
Click to expand...
Click to collapse
Old post i was just looking fo the answer myself for my Tab S4. Your post showed up in my Google search.. You don't need them in one image, as odin has AP BL and CSC.. So all you need to do is drop them in the right tabs and hit flash job done! Well i am just guessing will try and let you know!
Hi! I need a very specific system dump to try some mods, Unfortunately most of the tools I used no longer work. I tried with Ext2explore, Ext4Unpacker and some others but they all give a error message. What is the correct method for doing a Samsung system dump? I'm on Windows 8.1 (x64)
I guess I found the perfect tools right here on XDA: https://forum.xda-developers.com/s6...ol-tools-file-extraction-img-tar-md5-t3236605
Download the tool and unzip. Extract the system.img file using WinRAR o 7zip. Drag and drop system.img into NEWIMG2EXT2 This will convert the .img into a .ext4, to be opened with Ext2explore. Now that you have a complete dump you can deodex and start tinkering.
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
eliotargy said:
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Can anyone advise me further?
Click to expand...
Click to collapse
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Snowby123 said:
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Click to expand...
Click to collapse
My other implied question was: Did I do everything right?
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
search for lz4 on either xda or google.
( you need to unpack it)
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Why are you trying to patch? Please follow my guide for rooting the N9600.
christis said:
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Click to expand...
Click to collapse
No luck. Also no response to my post.
zxzxzxzxzxzxzxzxzx said:
Why are you trying to patch? Please follow my guide for rooting the N9600.
Click to expand...
Click to collapse
Where is your guide?
Again, where is your guide that you speak of?
eliotargy said:
No luck. Also no response to my post.
Click to expand...
Click to collapse
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
christis said:
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
Click to expand...
Click to collapse
Mine falls at patching with Magisk. N9600.