I don't know what format the image needs to be in. How can I find out?

Originally Posted by saleenman95

I don't know what format the image needs to be in. How can I find out?

If you open up a odin-flashable package, there should be a factoryfs file inside it. What I need to know is what filename extension is on the end of that file (.rfs, .img, or another), so I can properly create the image.

Ok, I feel stupid, but where do I get said ODIN flash-able package?

Your method can work. As for the pit, we don't have enough necessary files for a full restore files this is why I needed someone to make a print pit from heimdall. Also for the extension make a .img as the partiton is ext4 and not rfs.

Originally Posted by zaclimon

Your method can work. As for the pit, we don't have enough necessary files for a full restore files this is why I needed someone to make a print pit from heimdall. Also for the extension make a .img as the partiton is ext4 and not rfs.

Okay thanks, I wasn't sure about the filename extension. I am doing a rooted image for the 4.2 community first (as they beat you guys with an extracted image), but I will still have one up here today at some point.

Zaclimon, why does it have to be .img? .rfs works fine on ext4 Gplayer 4.0's, so I am curious as to the difference.

Originally Posted by zaclimon

... we don't have enough necessary files for a full restore files this is why I needed someone to make a print pit from heimdall...

how exactly does one do that?

Ok, I followed the instructions for the driver installation here. Yet I still get this error when I click on 'Print'.



What should I do? BTW, I am running Win 7 x64 w/ SP1.

I think your device is undetected
Have you followed this instructions:
Driver Installation Instructions:

1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite Device".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done

Yes I have followed the instructions. But no matter what I do, windows throws a "Code 10 - the device cannot start" error.

Originally Posted by hanthesolo

Okay thanks, I wasn't sure about the filename extension. I am doing a rooted image for the 4.2 community first (as they beat you guys with an extracted image), but I will still have one up here today at some point.

Zaclimon, why does it have to be .img? .rfs works fine on ext4 Gplayer 4.0's, so I am curious as to the difference.

The 3.6's kernel don't support rfs. The reason why ext4 works with .rfs is that because the initial /system partition is in rfs but then the recovery convert it to ext4. (or keeps it in rfs.)