Originally Posted by Doky73
md5 does not count. (and can be skipped)
The crucial point is to pack with tar util which handled by Odin right.
That's why I made the Windows version with Cygwin, because I haven't found any tar for Windows, which creates proper 'ustar' format.
md5 is just for have check-sum for exuding file corruptions eg by download errors...
Damn. I see it now. I think I made a mess switching between OS X and Linux for unpacking/packing and Windows for Odin. Once I made Odin working (showing Loke but then getting a writing error before flashing) I made the tarballs with OS X BSD tar instead of Linux.
Also I just checked it now. There is a "gnutar" in OS X Lion. it is probably possible to use that for Mac users (in case anyone is interested). I made a couple of tar files with Linux and gnutar and checked with HexEdit they seem to differ only on few things in the header, like the timestamp, uid and guid and stuff like that.
Last thing: What is so peculiar about the One Package ROM format? WinZip (the one I have is an old version, though) could unpack them, and with "unzip" in both OS X and Linux I get something like this:
BlueMoon:eek:dinatrix Michele$ unzip -l S5570IXILB2_S5570iITVLB2_S5570IXXLB3_HOME.tar.md5 | head
warning [S5570IXILB2_S5570iITVLB2_S5570IXXLB3_HOME.tar.md5]: 225962496 extra bytes at beginning or within zipfile
(attempting to process anyway)
Length Date Time Name
-------- ---- ---- ----
0 02-14-12 15:40 META-INF/
71 02-14-12 15:40 META-INF/MANIFEST.MF
0 02-14-12 15:40 system/
0 02-14-12 15:40 system/csc/
3346 02-14-12 15:40 system/csc/others.xml
6144 02-14-12 15:40 system/csc/contents.db
10181 02-14-12 15:40 system/csc/customer.xml
It fully unpacks the system.img file. But it ends there, it ignores all other files. In other words.. Which format is Samsung using for the One Package ROM files?
BTW where is the "thanks" button? Or it doesn't show because my post count is too low?