Hello everyone,
I have a few questions about the repartition and the pit file.
1. Is Kies software does repartition with pit file while flashing?
2. When to use pit file?
3. Where can I download the pit file?
4. How can I know what pit file to use and is there a difference?
Thank you.
Do not flash pit do not tick repartition.
Stay well away from pit files or you will brick your phone .
Suggest you read the faqs and guides and learn the very basics first .
jje
hi all
I just downloaded a package room for GT-i9200 v.4.2.2.
and when i tried to flash it using odin it give me fail error and pit file required
so please some body help me by sending the pit file
and many thanks
here is the room name
Gt-i9200xxuamed
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
honzicek69 said:
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
Click to expand...
Click to collapse
If I'm not mistaken boot.img is the bootloader, not the recovery. Are you sure you can't get into recovery using the 3-button-combo? If not I would try flashing this recovery via ODIN. And then try to reboot into it using the combo. Then flash CM zip from there again.
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
honzicek69 said:
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
Click to expand...
Click to collapse
Ah, I'm sorry I misunderstood. I thought that was just a snippet of the log... Try flashing the recovery I provided and see if it flashes. If not, maybe you can flash stock firmware with pit file (new partition table). If nothing flashes, I have no further ideas.
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
rp158 said:
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
Click to expand...
Click to collapse
I could be mistaken but I believe the 3-part-roms (csc / pda / phone) is the "old style" how roms where put out by sammy. You would have to search but I would think you can also use the version you get from sammobile nowadays (one zip) and additionally just use the gt-i9300 pit file found somewhere here in the forums.
@Hawaiihemd: be shure, you're wrong.
honzicek69 said:
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
Click to expand...
Click to collapse
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
rp158 said:
@Hawaiihemd: be shure, you're wrong.
Click to expand...
Click to collapse
@rp158 Well, I think I only made a small error in my assumption.
Here are the details on the sammobile download. It seems to hold everything a "3-part-version" holds. I downloaded the file and a look at the .tar file inside the single .zip seems to confirm that.
This post suggests that flashing the .tar with the pit file should work.
I don't know because I haven't tried myself, maybe you have. Or I'm missing a piece of the puzzle. If so, maybe you could point me to it!?
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
rp158 said:
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
Click to expand...
Click to collapse
You didn't, don't worry. I was a little stumped maybe, but only because your answer was so terminal. Actually I only wanted to start a discussion about this, because you seemed to know more about said process than me and I always try to gain knowledge here to better help solving problems. I haven't been in this forum for long or into android for that matter...
That said, I have done the "3-files" version of this process with a .pit file thrice already on different gt-i9000s. Always worked flawlessly.
Looking at the ones in the post @tallman43 suggested, I found the contents of those 3 .tar.md5 files in summary(!) similar to the ones in the 1 .zip from sammobile. That's why I thought it could work in the first place.
One thing I'm sure of is that in both cases the repartition info is in the .pit file. If you choose none, the MMC should not be repartioned. If partitions are reformatted... that's another deal.
Concerning the efs partition, to/from where that info is stored/restored during repartitioning of the MMC... that's a very interesting question!
tallman43 said:
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
Click to expand...
Click to collapse
Thank you very much for this hint. It worked well. I used the all files from KOR zip and 1.85 ODIN. Now i have the Korean version but at least i have something to start with and phone which works now.
Hello, I'm trying to downgrade from android 7.0 to 6.0.1 with odin but it doesn't work. My current CSC is the official 7.0 TPH (Portugal) and I've tried to flash the UK EE (EVR) which is android 6.0.1.
First error encountered is the well-known hidden.img. Tried to flash without the hidden.img file with few odin versions but everytime it got stuck at the "Nand Write Start". I also tried to flash just the hidden.img with .tar extension. It works but after the first restart when it says Erasing, the phone won't reboot again.
If anyone could tell me if there's another way to downgrade the firmware or what I'm doing wrong, please....
Nvmind it worked flashing both EVR firmware and PIT file
Can you share more details?
I wanted to downgrade the TPH 7.0 so I picked the EVR 6.0.1 firmware and tried to flash it with Odin but I got the hidden.img error. And to solve this problem I had to download the PIT file of that firmware and flash it at the same time and it worked. After the first reboot though it showed me an partition error but I got rid of that by factory resetting the device from recovery.
Do you can flash hidden.img alone after. Just rename it to hidden.img.tar and use odin on PDA field.
I'm also trying to downgrade my S6 Edge 925F from Nougat 7 to 5.0.2 or 6.0.1. After my upgrade to Nougat my S6 stop to accept Brazilian Carriers. I want to downgrade to try to fix this.
All my tryes stuck on sboot.bin.
Cya.
shAkur195 said:
Hello, I'm trying to downgrade from android 7.0 to 6.0.1 with odin but it doesn't work. My current CSC is the official 7.0 TPH (Portugal) and I've tried to flash the UK EE (EVR) which is android 6.0.1.
First error encountered is the well-known hidden.img. Tried to flash without the hidden.img file with few odin versions but everytime it got stuck at the "Nand Write Start". I also tried to flash just the hidden.img with .tar extension. It works but after the first restart when it says Erasing, the phone won't reboot again.
If anyone could tell me if there's another way to downgrade the firmware or what I'm doing wrong, please....
Click to expand...
Click to collapse
ztcoder said:
Do you can flash hidden.img alone after. Just rename it to hidden.img.tar and use odin on PDA field.
I'm also trying to downgrade my S6 Edge 925F from Nougat 7 to 5.0.2 or 6.0.1. After my upgrade to Nougat my S6 stop to accept Brazilian Carriers. I want to downgrade to try to fix this.
All my tryes stuck on sboot.bin.
Cya.
Click to expand...
Click to collapse
sboot.bin means your flashing an old bootloader and it won't allow you to downgrade. Try the steps mentioned above. Flash the UK EVR firmware with correct PIT file. Or try UK BTU with pit file
Downgrade your phone Nougat to Marsmallow. Download this firmware and flash with pit file use odin 3.12.5.
Samfirm Info:
Model: SM-G920F
Region: EVR
PDA: G920FXXS5DQE2
CSC: G920FEVR5DQA7
Phone: G920FXXU5DQB8
Pit File:
Odin Pit File tab select this file.
Hello, but with Odin and this method, the E fuse burn?
Thank you
i have searched for pit file for my samsung galaxy s3 (SHV-E210k) 16 GB but i could not find this file so please help me, anyone who have pit file for this device or who is able to extract pit from running device.
Post the Odin flash log. This will help isolate the problem.