ok yeaaa i read this
27.What is the .pit file? Why are there different versions?
The .pit file contains information regarding the partitioning of the internal ROM (note, that this is NOT the internal SD card! They are different memory chips!) and it is used during the flashing procedure. There are currently two version of the .pit file, respectively ending on 512.pit and 513.pit. They differ in that they have different partition sizes stored for each of the partitions that is created on the ROM. As of now, all ROMs seem to be functioning without any problems when the 512.pit file is used, whereas ROMs from version XWJG5 on do not work when the 513.pit file is used.
Not that these describe the partition of the ROM, however, they only actually change the sizes of the partitions if the 'repartition' option is checked in Odin3 during flash. You can flash providing the 513.pit file while your device is formatted according to the 512.pit file, however, this can cause unforeseen complications and it is advised to either use the .pit file according to which your phone is partitioned or alternatively select the 'repartition' option during flash.
now, i have Odin from 2 diffrent places 1 from Akaskrilla's website then the one from XDA in a post here(got this one first) but they both have diffrent .pit files 1 being "s1_odin_20100512.pit(came with the odin i got from xda)" other being "s1_odin_20100513.pit(akaskrilla)", i dont wanna use the wrong .pit as far as i can tell that seems very important that you dont get this wrong so i had to ask so ask me what u need to ask so i can keep the rite one. thx for the help in advance cause i wanna flash some roms!!!!
RanT476 said:
ok yeaaa i read this
27.What is the .pit file? Why are there different versions?
The .pit file contains information regarding the partitioning of the internal ROM (note, that this is NOT the internal SD card! They are different memory chips!) and it is used during the flashing procedure. There are currently two version of the .pit file, respectively ending on 512.pit and 513.pit. They differ in that they have different partition sizes stored for each of the partitions that is created on the ROM. As of now, all ROMs seem to be functioning without any problems when the 512.pit file is used, whereas ROMs from version XWJG5 on do not work when the 513.pit file is used.
Not that these describe the partition of the ROM, however, they only actually change the sizes of the partitions if the 'repartition' option is checked in Odin3 during flash. You can flash providing the 513.pit file while your device is formatted according to the 512.pit file, however, this can cause unforeseen complications and it is advised to either use the .pit file according to which your phone is partitioned or alternatively select the 'repartition' option during flash.
now, i have Odin from 2 diffrent places 1 from Akaskrilla's website then the one from XDA in a post here(got this one first) but they both have diffrent .pit files 1 being "s1_odin_20100512.pit(came with the odin i got from xda)" other being "s1_odin_20100513.pit(akaskrilla)", i dont wanna use the wrong .pit as far as i can tell that seems very important that you dont get this wrong so i had to ask so ask me what u need to ask so i can keep the rite one. thx for the help in advance cause i wanna flash some roms!!!!
Click to expand...
Click to collapse
Actually, it's less important than you'd think unless you plan to repartition (in most cases I'd say you shouldn't). In fact, don't even bother including the .pit at all, as it will automatically check repartition if you do. This will make you unhappy if you forget to uncheck it .
As for the differences between the pits.....it seems that it's basically a matter of what amount of space it allocates to each of the mounts. What's better for what rom? Not sure anyone can tell you for sure, but it's not going to brick your phone if you pick the "wrong" one or anything. I think most people feel the 512 is best suited for 2.1 roms, whereas the 513/813 ones are for froyo, and the 831 is possibly meant for 2.2.1 or 2.3 roms (it's been reported to be reserved for the Vibrant 4G atm, no idea how accurate that is).
Hope that helps.
MWBehr said:
Actually, it's less important than you'd think unless you plan to repartition (in most cases I'd say you shouldn't). In fact, don't even bother including the .pit at all, as it will automatically check repartition if you do. This will make you unhappy if you forget to uncheck it .
As for the differences between the pits.....it seems that it's basically a matter of what amount of space it allocates to each of the mounts. What's better for what rom? Not sure anyone can tell you for sure, but it's not going to brick your phone if you pick the "wrong" one or anything. I think most people feel the 512 is best suited for 2.1 roms, whereas the 513/813 ones are for froyo, and the 831 is possibly meant for 2.2.1 or 2.3 roms (it's been reported to be reserved for the Vibrant 4G atm, no idea how accurate that is).
Hope that helps.
Click to expand...
Click to collapse
+1 I have used the 512 and 513 not sure of the difference looked like i got a little more ram 513 but I just stick with the 512 and the now the 831 (when I need). It will not hurt if you are using Odin to experiment, then you can evaluate the results for yourself....... good explaining MWBehr
MWBehr said:
Actually, it's less important than you'd think unless you plan to repartition (in most cases I'd say you shouldn't). In fact, don't even bother including the .pit at all, as it will automatically check repartition if you do. This will make you unhappy if you forget to uncheck it .
As for the differences between the pits.....it seems that it's basically a matter of what amount of space it allocates to each of the mounts. What's better for what rom? Not sure anyone can tell you for sure, but it's not going to brick your phone if you pick the "wrong" one or anything. I think most people feel the 512 is best suited for 2.1 roms, whereas the 513/813 ones are for froyo, and the 831 is possibly meant for 2.2.1 or 2.3 roms (it's been reported to be reserved for the Vibrant 4G atm, no idea how accurate that is).
Hope that helps.
Click to expand...
Click to collapse
that definatelly helps man thx, and i was talking about the whole flashing back to stock but i it seems that your telling me, jus use 512.pit for 2.1 but what if i wanna flash a 2.2 rom? use the 513.pit? or no pit at all? or just use the CWM to flash them. I wanna kno how to do it in case i have to odin back to stock(T959UVJFD) if something goes wrong but i alrdy kno you dont need a .pit to flash a kernel(if im not mistaken) so thats all i need answered then i can have fun.
and yes thx for helping me you helped out alot, now everything is straight : ).
Related
Hi all,
I am just wondering if anyone has information on what repartition does in the ODIN interface. When do we use it?
I am a complete newbie and any guidance is much appreciated.
Thank you
ardabelati said:
Hi all,
I am just wondering if anyone has information on what repartition does in the ODIN interface. When do we use it?
I am a complete newbie and any guidance is much appreciated.
Thank you
Click to expand...
Click to collapse
what i know about it is that dont ever use it while flashing mate every tutorial is advising to dont use it in order to keep your phone alive
ardabelati said:
Hi all,
I am just wondering if anyone has information on what repartition does in the ODIN interface. When do we use it?
I am a complete newbie and any guidance is much appreciated.
Thank you
Click to expand...
Click to collapse
It repartitions.
Repartition does exactly what it means, it repartitions.
Your ROM is xx amount of size big, it is continuous, you partition it to seperate it.
Here's a random example.
16GB = 1GB BOOT, 1GB CACHE, 2GB SYSTEM ROM, 2GB USERDATA, 10GB STORAGE.
Now instead of 1 whole chunk of 16GB, you have 5 partitions which adds up to 16gb.
Im using repartition and Pit file on every reflash so far and having no problems.
Its only going to allot the partition sizes as mentioned in the pit file and nothing more.
bala_gamer said:
Im using repartition and Pit file on every reflash so far and having no problems.
Its only going to allot the partition sizes as mentioned in the pit file and nothing more.
Click to expand...
Click to collapse
The problem is not the repartitioning, the problem is the pit file, some people don't have the correct pit file.
The other problem is bootloader and where it is placed. Just imagine if the bootloader is placed in a partition, and your pit file is not for the SGS2, and does not create a partition for the bootloader. No bootloader, no boot, no download mode. That would be a pretty fun situation.
Hi!
I know that I'm asking about forbidden subjects but I have no intention of doing something stupid just want to understand some things about S2.
That's what I think I understand:
- PIT is a file that contains partition layout on our device, that partitions are later flashed with files from rom package (files are partition images in fact)
- Normally we do not need to re-partition because there is only one partition description available on S2 - so all ROM share it (also it's not recommented coz if sth goes wrong we have big problem - device without partitions)
- EFS is one of the partitions and it shouldn't be touched (contains IMEI etc)
Here is my question:
Some people flash ROM with PIT and repartition and still have working device - how is it possible ?? - re-partition should wipe everything including EFS.
EDIT:
One more thing - when exploring XXKP8 rom package from sammobile.com noticed that there is PIT file and some file named
I9100_EFS_I9100XXKP8_CL42141_REV02_user_low_ship.tar.md5
that contains efs.img file I wonder what is this file for. Some generic EFS image ??
Regards
Slig
The pit is used for partition mapping, basically telling the program which block device is which partition. You dont need to use the pit as Odin can pull it from the phone, this also prevents people from using i9000 pits (sgs1, and yes this has happened)
Efs has both generic files and device specific files, I think.
Sent from my GT-I9100 using Tapatalk
Thanks for response !
veyka said:
this also prevents people from using i9000 pits (sgs1, and yes this has happened)
Click to expand...
Click to collapse
Yeah I read about that epic failure. That is why I'm asking - want to know everything before doing anything.
Regards
Slig
slig said:
Hi!
Here is my question:
Some people flash ROM with PIT and repartition and still have working device - how is it possible ?? - re-partition should wipe everything including EFS.
The recommendation is not to flash PIT file or repartition unless you know what you are doing .
PIT does not wipe EFS .
Their is a PIT file description post on the forum .
jje
jje
Click to expand...
Click to collapse
Hi ! Thank You for Your response.
JJEgan said:
The recommendation is not to flash PIT file or repartition unless you know what you are doing .
Click to expand...
Click to collapse
Yes, I'm fully aware of that. I'm just the kind of person that like to know why so I decided to investigate this subject deeper. Another thing is that I'll probably try to use heimdall and that program requires better understanding than "use PDA field in Odin".
You can just flash a .pit file and check repartition. You just have to make sure your flash won't fail. If you have faulty drivers or a damaged usb cable, then it will brick your phone.
If you want to try it, make a flash without .pit and repartition and if it works you can use them. Its just something unexperienced users should not use.
Unless something changes, we don't need to repartition, (one case might be if android plus tw is bigger than 500 ish megs Samsung would need to make the system partition bigger) so we just don't need to use it, and making the risks sound worse it keeps newbies away.
Sent from my GT-I9100 using Tapatalk
I've found Odia's thread GT-9100 PIT v Flash analysis
http://forum.xda-developers.com/showthread.php?t=1104139
Very interesting informations that answers many of my questions.
Hey guys.. Odin3 version3 and higher has gz support. I've been working with this for a bit and tonight I found that Odin will accept tar.md5.gz files. This is important for GNote2 users as the stock ROM is 1.2Gigs! You can get an extra 10-40% compression and 100% gaurantee that the files arrive to your users computer in the condition that you packaged them using this method. I have not found a guide on using the gz format so I thought I would write one up.
You will need:
A Linux computer
Your rom (we will call it MyROM)
How to package for Odin on Windows
I will cover packing into a single file, adding an MD5, and compressing the file down. For the purposes of this, we are working with "MyROM". You will want to call your ROM whatever you like. Just make sure to add version information to the file name so users don't get confused. Also note, the name MUST be consistent throughout the process. If you change the name, Odin can fail.
Another good tip is to put a model number in the name so there is no confusion as to what device your Odin package goes to. Several users, myself included, have 20+ Odin packages on their computer.
So first you want to turn the ROM into a single tar file and then make sure changes are written to the disk.
Code:
tar -H ustar -c boot.img hidden.img modem.bin param.bin recovery.img system.img tz.img sboot.bin>./MyROM.tar;sync;
Next we want to add an MD5 to the file so Odin can check its consistancy.
Code:
md5sum MyROM.tar >> MyROM.tar;
Now we will change it into a tar.md5 file so Odin knows it has an MD5 attached to it.
Code:
mv MyROM.tar MyROM.tar.md5; sync;
Finally we will compress it with GZip. GZip is the only compression method supported by Odin.
Code:
gzip MyROM.tar.md5 -c -v > MyROM.tar.md5.gz;
You will now have a file called MyROM.tar.md5.gz.
Conclusion
The first time the file is flashed, Odin will uncompress it into MyROM.tar.md5, then check its consistancy, then flash the file. Using this method you will be transferring the smallest file possible and adding integrity checks.
notes
Note to Verizon GNote2 users: Stay away from using Odin after IROM unlock as flashing a package intended for another device will perma-lock your device into another carrier's bootloaders. Especially stay away from GS3 as the displays are not compatible.
good ****! this is def useful
Awesome news! Any test results with the older versions? If not one click solutions may not benefit.. but servers and users will by cutting the downloads even more!
Sent from my SPH-L900 using Tapatalk 2
Windows OS
How can I do it on a Windows computer?
MAQ7 said:
How can I do it on a Windows computer?
Click to expand...
Click to collapse
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
cygwin.
Mine all work
imnuts said:
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
Click to expand...
Click to collapse
adrynalyne said:
cygwin.
Mine all work
Click to expand...
Click to collapse
I managed to make tar on Windows using cygwin :good:.
Thank you
Interesting adam, I always compressed the whole odin package into a rar file (same effect but one step extra). Also I made an article about odin a while ago:
http://broodplank.net/?p=496
Btw, did you know that you can put cwm backups (ext4.tar) inside an odin package? It's the first odin image I ever saw, filled with a CWM backup, and yes it works XD
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Last thing, Odin packages can be a last resort fix, believe me, many users reported that flashing my rom broodROM_RC5.tar.md5 (which contains about 13 files, you can imagine how many partitions it includes) fixed their phone when nothing else worked.
So thank you Samsung for leaking your tool, A world with Samsung Kies only would be a very sad "softbricky" world
broodplank1337 said:
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Click to expand...
Click to collapse
TAR files preserve file permissions.
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
mrRobinson said:
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
Click to expand...
Click to collapse
Only on the Verizon Galaxy Note. All others are IROM locked. The IROM lock prevents flashing of an improper SBOOT. An unlocked VZWGNote 2 can flash any SBOOT.
Other than this specific case, adding third party tools other than ZIP compression means your user must download special tools.
Extra files?
If I were to pack an extra README.txt file into the tar before prepping it for Odin, would Odin then ignore it during the flash? Obviously there's no entry for what to do with an extraneous text file in the pit, so hopefully Odin would just disregard it.
I happened to find out today that heimdall has support for "Heimdall Firmware Packages." You can read and write them from the heimdall frontend (the 1.3 FE binary is forward compatible with my source built 1.4 heimdall). What's interesting, is that the format is almost identical to odin's format. It is still packaged in a tar file, and it contains the same system.img, boot.bin, recovery.bin etc. files you'd find in the Odin tar. By default it's format is Package.tar.gz. The only significant difference is the addition of a firmware.xml file that identifies the proper partition for each image file, as well as the target platform, the author, and other details like that.
So I got curious. I took a Package.tar.gz file generated by heimdall, and repackaged it as a Package.tar.MD5.gz file. Heimdall has no problem reading this! So the upshot is, Odin now handles the .gz, so as long as Odin isn't bothered by an extra firmware.xml file inside the tar, the same format would be compatible with either tool.
PS> Don't flame me about flash counters or bricked phones. I do understand that Odin/Heimdall are only particularly relevant for returning a phone to stock, but that's still a very important functionality and it would be great to have a unified format.
This is most likely a really newbie question..
But does anyone know how I can extract the .zip ROM file from an Android phone. The best I could find were people that were doing a backup of there phone (I don't know if they are .zip or not). But I want to somehow extract the .zip from the phone and be able to flash like a custom ROM.
Thanks in advance!
Sparrow40k said:
This is most likely a really newbie question..
But does anyone know how I can extract the .zip ROM file from an Android phone. The best I could find were people that were doing a backup of there phone (I don't know if they are .zip or not). But I want to somehow extract the .zip from the phone and be able to flash like a custom ROM.
Thanks in advance!
Click to expand...
Click to collapse
I understand what you are looking for, but there is not a way to do that. The backup and restore method would be as close as you could get, but the method to backup leaves the various partitions in .img file formats which the custom recovery (has to be a custom recovery like ClockWorkMod, TWRP, etc) would be able to read, copy, and restore. Does the same thing that you are looking for, just in a different way.
es0tericcha0s said:
I understand what you are looking for, but there is not a way to do that. The backup and restore method would be as close as you could get, but the method to backup leaves the various partitions in .img file formats which the custom recovery (has to be a custom recovery like ClockWorkMod, TWRP, etc) would be able to read, copy, and restore. Does the same thing that you are looking for, just in a different way.
Click to expand...
Click to collapse
If I am unable to extract a .zip of the ROM, how do I work on the ROM and do things like port it?
All the websites I look at say to download the .zip, but my phone (JiaYu G4s) doesn't have a ROM available. The closest would be the JiaYu G4; which to my (very small) knowledge is no good to me because the internals are all different.
That's one of the major downsides to having a phone that isn't supported by the manufacturer or the dev community. Technically, the manufacturer is supposed to release the source code per GPL, but most of the ones that use MediaTek chips never do.
http://www.xda-developers.com/android/have-you-paid-your-linux-kernel-source-license-fee/
I'm not sure how devs that work on those devices do it...
Edit: Found it
http://phonegist.blogspot.com/2014/02/how-to-make-stock-rom-of-mediatek.html
es0tericcha0s said:
That's one of the major downsides to having a phone that isn't supported by the manufacturer or the dev community. Technically, the manufacturer is supposed to release the source code per GPL, but most of the ones that use MediaTek chips never do.
http://www.xda-developers.com/android/have-you-paid-your-linux-kernel-source-license-fee/
I'm not sure how devs that work on those devices do it...
Edit: Found it
http://phonegist.blogspot.com/2014/02/how-to-make-stock-rom-of-mediatek.html
Click to expand...
Click to collapse
So, by following the steps on the link provided. I actually am able to create a .zip from the ROM installed on the phone?
That's the idea. I dunno if that one is compatible with your chipset, but you will have to find the version that does and should be able to get started.
hello. i would like to repartition my device due to some problems but i can not find the right pit file. i guess i should install the one for my corresponding rom and device. I installed one which works for me so far i guess but i could not transfer some files from my pc (tested on two) properly so i guess its not 100% functional... also will my data stay put? Thanks in advance!