Database Develop

[Q] How do I extract files from ROM?

Is it possible to extract an APK from a ROM File?
If i take the JM5 ROM, I can unRar it and then I can unTar the md5 file that is the ROM - but from there I just get a bunch of system files that I assume are images of partitions. The big one is the factoryfs.rfs - is there a way to pull an apk out of here, or do i have to install on a device first and save the APKs i want?
Thanks.

alphadog00 said:
Is it possible to extract an APK from a ROM File?
If i take the JM5 ROM, I can unRar it and then I can unTar the md5 file that is the ROM - but from there I just get a bunch of system files that I assume are images of partitions. The big one is the factoryfs.rfs - is there a way to pull an apk out of here, or do i have to install on a device first and save the APKs i want?
Thanks.
Click to expand...
Click to collapse
Just tell us what application your looking for(remember to follow the forum rules before replying )

[Q] What is inside hidden.img file?

Hi,
I want to flash XXLA4 ROM with OLBKL2 CSC and CF-Root LA4 using CWM Manager in one go.
I have these files:
N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5
N7000DXLA1_N7000OLBKL2_N7000DXKL2_HOME.tar.md5
CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.tar
Inside the ROM package there are:
factoryfs.img -> this is System files (PDA), I will use XXLA4
modem.bin -> this is Phone modem, I will use XXLA4
zImage -> this is Kernel, I will use CF-Root XXLA4
cache.img -> this is CSC files, I will use OLBKL2
hidden.img -> what is this? should I use the file from DXLA1 or XXLA4?
I searched but found conflicting answers. Some said that it's related to CSC, so I should use the file from DXLA1. But, leaked samsung rom only have cache.img inside MULTI-CSC tar file (for example GT-N7000-MULTI-CSC-OXALA3.tar).
I also noticed that some of the ROM package that I extracted have the same modified date for factoryfs.img and hidden.img, while different modified date for cache.img; meaning it's related to System files (factoryfs.img).
So, to know from which file should I use hidden.img from (DXLA1 or XXLA4), I want to know what is inside hidden.img.
Thank you so much in advance~!

V-Lix said:
Hi,
I want to flash XXLA4 ROM with OLBKL2 CSC and CF-Root LA4 using CWM Manager in one go.
I have these files:
N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5
N7000DXLA1_N7000OLBKL2_N7000DXKL2_HOME.tar.md5
CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.tar
Inside the ROM package there are:
factoryfs.img -> this is System files (PDA), I will use XXLA4
modem.bin -> this is Phone modem, I will use XXLA4
zImage -> this is Kernel, I will use CF-Root XXLA4
cache.img -> this is CSC files, I will use OLBKL2
hidden.img -> what is this? should I use the file from DXLA1 or XXLA4?
I searched but found conflicting answers. Some said that it's related to CSC, so I should use the file from DXLA1. But, leaked samsung rom only have cache.img inside MULTI-CSC tar file (for example GT-N7000-MULTI-CSC-OXALA3.tar).
I also noticed that some of the ROM package that I extracted have the same modified date for factoryfs.img and hidden.img, while different modified date for cache.img; meaning it's related to System files (factoryfs.img).
So, to know from which file should I use hidden.img from (DXLA1 or XXLA4), I want to know what is inside hidden.img.
Thank you so much in advance~!
Click to expand...
Click to collapse
cache is CSC
if you want to use another CSC file, just select cache in Mobile Odin OR in case of CWM, when it ask you to select file for Cache, you have to point to CSC file(OBL KL2 CSC e.g.)
I said you earlier too, that will wipe your data, as i remember you have not concern about losing data i think.

dr.ketan said:
cache is CSC
if you want to use another CSC file, just select cache in Mobile Odin OR in case of CWM, when it ask you to select file for Cache, you have to point to CSC file(OBL KL2 CSC e.g.)
I said you earlier too, that will wipe your data, as i remember you have not concern about losing data i think.
Click to expand...
Click to collapse
Yes, I know about cache.img is the CSC files, and I know how to use it with Mobile Odin or CWM Manager.
You are right, I don't mind factory wipe, infact I always full wipe before any firmware update.
What I want to know is about hidden.img...
Yes, I'm curious, I want to know and learn what is this image file contain.
Oh, and yes, I have flashed to XXLA4 using hidden.img from XXLA4...
It works.. But I'm still curious and want to know what is it..
Thanks again~

Bump. Any more info on what's inside the hidden.img file?

Shammyh said:
Bump. Any more info on what's inside the hidden.img file?
Click to expand...
Click to collapse
Use magic iso to mount that image file and see whats inside it

Well on my Motorola, it contains boot animation, wallpapers, carrier related settings (subsidy lock), and nvitems.
Hope that helps

It has binary counter trigger!! X10 lol
SHOT from my LOADED GT-N7000!!

Hidden.img is exclusive to carrier branded Stock ROM's.
In case of such ROM's cache.img + hidden.img together constitute the CSC. So my guess is hidden.img has some of the carrier specific bloat!
EDIT: Just saw that the hidden.img from the xwla4 ROM contains files related to the Samsung Gamehub (ngmoco)!
Thnx!

Delete hidden.img
The-Droidster said:
Hidden.img is exclusive to carrier branded Stock ROM's.
In case of such ROM's cache.img + hidden.img together constitute the CSC. So my guess is hidden.img has some of the carrier specific bloat!
EDIT: Just saw that the hidden.img from the xwla4 ROM contains files related to the Samsung Gamehub (ngmoco)!
Thnx!
Click to expand...
Click to collapse
Any idea if it's possible to delete "hidden.img" from the CSC tar file and then flash it to keep everything but the bloat?

sherbie said:
Any idea if it's possible to delete "hidden.img" from the CSC tar file and then flash it to keep everything but the bloat?
Click to expand...
Click to collapse
yeh mate;
rename extracted file from xxxxxx.tar.mtd to xxxxx.tar and it should turn into a winrar compressed file
then you can delete hidden.img
after you compress them together and the only way i know how to do that is with the Unified Android Toolkit

mojo_jodroid said:
yeh mate;
rename extracted file from xxxxxx.tar.mtd to xxxxx.tar and it should turn into a winrar compressed file
then you can delete hidden.img
after you compress them together and the only way i know how to do that is with the Unified Android Toolkit
Click to expand...
Click to collapse
Hello, I compressed them together and installed Unified Android Toolkit what I need to do on Unified Android Toolkit? what's the next step, please help

sherbie said:
Any idea if it's possible to delete "hidden.img" from the CSC tar file and then flash it to keep everything but the bloat?
Click to expand...
Click to collapse
Open the zip with Total Commander, delete hidden.img and rename the file without the .md5 extension.
Only leave .tar at the end of the file name.

vijai2011 said:
Use magic iso to mount that image file and see whats inside it
Click to expand...
Click to collapse
pure BS. MagicISO or Daemon tools cannot open this file.

vratnik said:
pure BS. MagicISO or Daemon tools cannot open this file.
Click to expand...
Click to collapse
Ignorance is a bliss. Go google yourself on simg2img instead of following a 4 year old tip

mojo_jodroid said:
yeh mate;
rename extracted file from xxxxxx.tar.mtd to xxxxx.tar and it should turn into a winrar compressed file
then you can delete hidden.img
after you compress them together and the only way i know how to do that is with the Unified Android Toolkit
Click to expand...
Click to collapse
Here's a detailed tutorial: http://www.droidviews.com/fixing-odin-firmware-installation-failed-at-hidden-img-issue-on-samsung/

[REQ] Extract baseband files from ROM

I would like to request some help in trying to extract the baseband from the latest ROM for the Samsung Galaxy SIII Mini I8190N.
I tried the method posted here -> http://forum.xda-developers.com/showthread.php?t=1658809
but cgywin keep on saying amss.mbn not found in archive.
Trying to extract the baseband from this ROM -> http://samsung-updates.com/details/11893/Galaxy_S_3_Mini/GT-I8190N/CHN/I8190NZCAMG2.html
Help anyone?

You just have to extract modem.bin from the tar.md5
Thats the baseband.
Sent through time and space from my s3mini/CM10.1

tys0n said:
You just have to extract modem.bin from the tar.md5
Thats the baseband.
Sent through time and space from my s3mini/CM10.1
Click to expand...
Click to collapse
And I use Odin to flash it?
Just like that?

kljs said:
And I use Odin to flash it?
Just like that?
Click to expand...
Click to collapse
You'll have to make a tar of it. IZArc should work fine if you're on windows.

tys0n said:
You just have to extract modem.bin from the tar.md5
Thats the baseband.
Sent through time and space from my s3mini/CM10.1
Click to expand...
Click to collapse
Where can I find modem.bin inside tar.md5 file? When I opened via 7zip. I found the following folders:
boot.img
cache.img.ext4
fat.bin
hidden.img.ext4
recovery.img
system.img.ext4

JJkly said:
Where can I find modem.bin inside tar.md5 file? When I opened via 7zip. I found the following folders:
boot.img
cache.img.ext4
fat.bin
hidden.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
Sorry, I have no idea. What device is it?

Is .tar.md5 the same as .img.tar?

So I tried to install Magisk via patching my boot image, but it failed, and I know from the instructions that I need my stock image rom to be a .img.tar if I want to flash through ODIN. However my stock boot image is a .tar.md5, and even trying to research the issue I just end up getting more confused. Does the rom need to end in .img? Can I convert/extract my .tar.md5 to an .img.tar(.md5?)? Is a .tar.md5 the same as a .tar (the hashing bit I understand) so that whenever someone refers to a .tar, either a .tar or a .tar.md5 is acceptable?
These Linux extensions driving me crazy and I really can't figure out what's what. It might be useful for the main Magisk thread to have a section that explains this kind of basic stuff for the less-savvy. If someone could straighten me out I would be highly appreciative, thanks in advance!

.tar.md5 is a text file which contains hash of the original file. It is used to check the integrity of files.
Compare the sizes of .tar and .tar.md5 files.

Sorry @Shished that has really not helped me at all, I'm just as confused as ever. Thank you for trying though. What is "the original file"? What am I comparing, should I have some other kind of file here? Can I get the original file out of my .tar.md5? I have one file that I believe is a factory boot image and it's a .tar.md5. Believe me when I say I am a complete noob on this and I need the basics of the basics.
Edit: The file originally came as a zip, is THAT the original file?
screenshot of files: https ibb.co/fas1o7

Questioneer said:
So I tried to install Magisk via patching my boot image, but it failed, and I know from the instructions that I need my stock image rom to be a .img.tar if I want to flash through ODIN. However my stock boot image is a .tar.md5, and even trying to research the issue I just end up getting more confused. Does the rom need to end in .img? Can I convert/extract my .tar.md5 to an .img.tar(.md5?)? Is a .tar.md5 the same as a .tar (the hashing bit I understand) so that whenever someone refers to a .tar, either a .tar or a .tar.md5 is acceptable?
These Linux extensions driving me crazy and I really can't figure out what's what. It might be useful for the main Magisk thread to have a section that explains this kind of basic stuff for the less-savvy. If someone could straighten me out I would be highly appreciative, thanks in advance!
Click to expand...
Click to collapse
.tar is the compression used for Samsung. If you extract the .tar, you will find an .img in it. A .tar.md5 is just the .tar with the hash file appended.

madbat99 said:
.tar is the compression used for Samsung. If you extract the .tar, you will a .img in it.
Click to expand...
Click to collapse
Does it mean that .img file can always be extracted from a .tar or .tar.md5 file?

A S Ovin said:
Does it mean that .img file can always be extracted from a .tar or .tar.md5 file?
Click to expand...
Click to collapse
There will likely be several .img files inside of it.

Modding SM-G780G

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.