Hi to all.
Right now I'm trying to figure out how stock JB is packed.
I found great tool that can pack/unpack stock rom.
But it contains some errors.
I fixed all the errors, and I found out that:
1) It contains some unknown 256 bytes. I guess it some sign.
2) I packed to zip by some magic app. Because right now I unpacked blob file, the packed it. I used compare tool to compare original blob file with newely created and it says they are the same. Packed to ZIP and tried to install. Installation failed. So, I assumed, that they use some application to pack
Maybe someone tried to do the same? Some ideas?
PS: Right now I seems like the only wat to get root. Because current permissions in android allows to write only to /proc/procID/ folder and /sdcard that's all.
We wont help you until its out of development so move it and we can help, DEVELOPMENT ONLY!
I recently did this for the E4GT and have been asked to do it here as well.
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs, nor does it show you how to make your own Odin One-Clicks. What it does do is show you how to pull files from those stock leaked/official ROMs so that you can proceed to make yourself into a Super Duper Developer!
In essence if the Developer knows what they are doing they could use this method to extract all the files from the build and could then add them to a ZIP and have a stock odexed ROM within minutes and do it all through Windows! Depending on time I may or may not do a tutorial on that as well...
So let's begin!
We've all seen those pesky TAR.MD5 packages that we can flash through Odin. How often have you wanted to look inside them and see what is inside before flashing? There are several ways to do it and the most common answer requires Linux and Dsixda's Kitchen utility. This tutorial gives you the ability to do that through Windows and without having to extract the full ROM. These instructions are specific to the Samsung Galaxy S3 (all variants) but can be used on most Samsung Galaxy phones.
Each TAR.MD5 release contains multiple files. Each of these files corresponds to a specific partition on your device. These files are formatted to be mounted by your device but not by a computer. We will be converting them from a .img.ext4 partition type to an ext4.img type partition so we can mount them and read them through Windows. For this tutorial we will be opening up the system.img.ext4 (the system files partition).
Before you dive in there are a few things you'll need.
- A PC running Windows.
- A stock TAR.MD5 release. Several are available at www.rwilco12.com.
- DiskInternals Linux Reader (must be installed on the Windows PC). You can download DiskInternals Linux Reader here.
- SGS2toEXT4 Utility available here. *Be sure to extract the JAR file from the ZIP archive.
- 7-Zip available here.
For the rest of the tutorial please visit my site: www.rwilco12.com
Enjoy!
Reserved.
Awesome! First!
Sent from my SPH-L710 using xda app-developers app
great it's work fine with me on windows8
if you let me a noop question
can we cook the rom in this way ? i mean after upack the image we can edit the files or the apk or the font and repack it again as a md5.tar extension
is that possible
regards
IRoN MaN9 said:
great it's work fine with me on windows8
if you let me a noop question
can we cook the rom in this way ? i mean after upack the image we can edit the files or the apk or the font and repack it again as a md5.tar extension
is that possible
regards
Click to expand...
Click to collapse
Unfortunately no. That part does require Linux but this could help simplify the process if you prefer a Windows environment.
رد: [TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-L710)
rwilco12 said:
Unfortunately no. That part does require Linux but this could help simplify the process if you prefer a Windows environment.
Click to expand...
Click to collapse
Relly sad hope that you can develop this threat in the future so we can cook the stock roms anyway thank you very much for your answer
Regards
IRoN MaN9 said:
Relly sad hope that you can develop this threat in the future so we can cook the stock roms anyway thank you very much for your answer
Regards
Click to expand...
Click to collapse
I might have some other stuff in the works for you guys here soon.
رد: [TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-L710)
rwilco12 said:
I might have some other stuff in the works for you guys here soon.
Click to expand...
Click to collapse
I can't wait to see your next work
Hey after installing linux reader on windows it shows mf5 file in HEX manner , it dont convert it in .zip file..
any way to do it?
mjp93 said:
Hey after installing linux reader on windows it shows mf5 file in HEX manner , it dont convert it in .zip file..
any way to do it?
Click to expand...
Click to collapse
You need to extract it from the img file by saving it. After extracting you'll need to package it in a ZIP.
I followed the guide to the t and its saying that the image is invalid. Any ideas?
macasus76 said:
I followed the guide to the t and its saying that the image is invalid. Any ideas?
Click to expand...
Click to collapse
What device and what files are you using?
Using windows Vista x64 the file is a I537UCUCNE3 stock odin image. I created a .img file using ext4 tool you posted but the Linux viewer says invalid
The image here shows my created .img file on the left, the Linux reader on the right and the error in the middle
This tutorial is no good anymore.
Finally !!
I found how do that after to waste a day to search one real solution.
Is only to use the ClassyKitchen free version for windows.
I found it here:
https://forum.xda-developers.com/chef-central/android/tool-classykitchen-android-roms-t3862584
Basically, after to open the program, you will choose "create new project" on the tab "Projects utils", and choose the firmware from PC or from mobile root. So, the program will extract the folders and files to PROJECT/system folder, and you will can access them by windows explorer, including the app folder with all original apks.
I was looking for a way to restore the calculator apk after delete it before to find another to replace it.
[ ].
in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors
can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or other?
If anyone can try and unpack the bootloader-flo-flo.4.04.img file I am not sure why I keep getting bad file descriptor errors when trying to unpack it using imgtool
with that unpacked it should be easy to make a flashable bootloader, and there are a bunch of people all over that need this that either do not have access to a machine or like myself the USB port is not working at all on the device.
I second this!
Please!
Pleeeeeease!!!!
OPO Yeauh!!!
Agreed! I currently donr have a computer so i cant update rhe bootloader
The recovery flashable bootloader can now be downloaded from the link posted in this thread http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
Be sure to thank @eksasol I bugged him so much I feel really bad now, awesome work!
Good day all,
I am hoping someone can help me out and explain what I am not doing correct or point me in the right direction.
I have been reading the forums for quiet some time and have learned alot and want to thank everyone for their posts.
My question is I have taken apart the combination file and have been able re create the tar ball and successfully push it back onto the phone. ( I know some of these eng boot and combination files are digitally signed and I have not figured out how to confirm this). The issue is when I push this file with odin it wipes the user data which is the issue.
I then began digging deeper into the img files and located within the cache.img/recovery/command:
--carry_out=csc_factory
--wipe_data
Which will wipe the data. I have tried removing this along with changing the csc_home which would not wipe the user data if I understand this correctly. Once I modify the file I change the permissions back to read only and convert the cache.img to an android sparse file and create the tar-ball. I am now going through the system.img and boot.img to see if I can possibly modify these to bypass mounting the cache.img.
I am not sure if any of this will work and not sure why its not working so any advice would be very helpful.
Thanks,
San
Hi sorry to ask but this tutorial wont work. To create a combination firmware to bypass Google FRP I'll summarize it for you all. First rename the AP and BL files to .zip next extract them using 7zip to their own folders. Copy only certain files to a folder, zip it back up, and install it with Odin.
Now the problem is It seems Samsung has messed with these images since 2020. The BL (once extracted) has had all the images just broke into smaller parts so you cant tell what is what anymore. No more 3 files now its a giant mess and the data that holds the FRP info must be in there.
The AP has also changed but the file is just named super.img.lz4 instead of system.img.lz4 so nothing much.
Any path two lead me in the right way would be greatly appreciated. Thanks and have a great summer everyone.