Develop Bugs

Samsung Galaxy Gio GT-S5660M Discussion - Rooted Stock ROM, Partition Mapping

(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado

Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!

Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado

Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado

Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.

I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.

Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.

red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?

Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!

steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty

Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.

red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425

I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)

Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks

Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?

steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App

Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....

Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...

ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..

waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.

[Q] Extract Boot.img from Stock ROM

Hi guys, I would like to extract boot.img from a Stock ROM without the need of installing it on my (Galaxy Note 2 T-mobile). All I found on the internet is how to extract it from an installed ROM.
So I would like to:
1. Extract the boot.img
2. Then flash it through ODIN to my custom ROM (Jedi Master 14)
Thanks in advance and please help me :crying:

Why would you do that?
Hastily spouted for your befuddlement

I don't know how you going to use boot.img to fix your problem. But the .md5 rom files are just zipped files. unzip and you will find the boot.img file. Are you sure that this will fix your problem?
Are you trying to change your boot image?

Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.

Thanks a lot. Thats exactly what I am looking for.
Sent from my SGH-T889 using xda app-developers app

Darkshado said:
Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.
Click to expand...
Click to collapse
and how do we do?
i flash the file without pepacking it so i can t bot, kernel error!
I'm really annoyed if you can explained to me how do we do it
thx

PIT file for GT-N5110 ¨[solved]

I need the PIT file from a GT-N5110 PLEASE!! My partitions are messed up , did a little to much of flashing and testing.
Edit: solved
Solved , ha I saved my tablet the second time from a near hardbrick.
I need to stop my flash addiction . But it is so thrilling, Oh the tablet is dead :crying: , Ah it is back a live .....
More info , I tought I messed up partition as I got stuck in bootloop (again) and restoring EFS didn't solve the problem.
I noticed I marked "NAND erase all" in odin by accident and that was the reason why I got myself in this mess.
So never use that thing in Odin.
How I figured out what was wrong , well that was easy , I had stock recovery on my tablet as I installed a official samsung firmware.
So I started up recovery (stock) and it gave me some info , data partition could not be mounted.
I used the stock recovery to do a data/factory reset and it solved the problem.
Next thing I will do is get my PIT file , you need to do that from within linux but that is no problem got both running on my system. Just need to find out on how to extract it, google will help me...
I want to know everything about this tablet , and make sure it is unbrickable if you just got the right files.
So the PIT file is the next I want , that is what you need when you mess up partitions.

civato said:
So the PIT file is the next I want , that is what you need when you mess up partitions.
Click to expand...
Click to collapse
Hi civato, you can extract the pit using heimdall on windows as well.
On my device this corresponded exactly to the file I get directly from the device as root with
Code:
dd if=/dev/block/mmcblk0 of=n5110.pit bs=1 skip=17408 count=8192
I have never used the pit, the emergency has not happened yet for me, so I can't.recommend anyone to use this, but someone could compare to verify theirs is the same. Attaching the pit and text description of pit for n5110 ONLY obtained from heimdall:

davp said:
Hi civato, you can extract the pit using heimdall on windows as well.
On my device this corresponded exactly to the file I get directly from the device as root with
Code:
dd if=/dev/block/mmcblk0 of=n5110.pit bs=1 skip=17408 count=8192
I have never used the pit, the emergency has not happened yet for me, so I can't.recommend anyone to use this, but someone could compare to verify theirs is the same. Attaching the pit and text description of pit for n5110 ONLY obtained from heimdall:
Click to expand...
Click to collapse
Oh thanks , will give it a try , best that we start collecting these files as I see a lot of users of samsung devices at one point need it.
I had some strange stuff going one but was able to save the device every time.

This is my PIT file of my GT-N5110 , it is the same as yours but I took it with the latest Heimdall so I think that is why some names are different in the print out text.
If you look at the block sizes you see they are the exact same size as yours. So I'm guessing this is a good backup for the GT-N5110 16GB , now it is up to other users with other devices to do the same.

Had the same problem and followed your instructions, thanks man now my note is back to live. And running your rom and kernel.
Sent from my GT-N5110 using Tapatalk 4 Beta

I have a 5100 and is also soft briked
Hi,
I have almost the same problem. i don't have the pit file, but I have a N5100 (the 3G model). My problem is that I can't get into reocvery either. I can get into download mode though. Do you think I can use this pit file on my N5100?

I need pit file for n5120 please where I can download it

civato said:
This is my PIT file of my GT-N5110 , it is the same as yours but I took it with the latest Heimdall so I think that is why some names are different in the print out text.
If you look at the block sizes you see they are the exact same size as yours. So I'm guessing this is a good backup for the GT-N5110 16GB , now it is up to other users with other devices to do the same.
Click to expand...
Click to collapse
How do i run this in odin?

Komic11 said:
How do i run this in odin?
Click to expand...
Click to collapse
I use Odin 3.07... you have to unzip the pit file, and select PIT file and open your pit file you unzipped. Tick the repartition box and start the upload.

gooberdude said:
I use Odin 3.07... you have to unzip the pit file, and select PIT file and open your pit file you unzipped. Tick the repartition box and start the upload.
Click to expand...
Click to collapse
hey sorry for the delay havent been working on this. will try tonight thanks for responding relatively quickly. i feel like a dummy, I didnt understand the tar file but i see theres a rar file i didnt see the rar before i know what to do

GT-N5100 PIT can't be flashed
davp said:
Hi civato, you can extract the pit using heimdall on windows as well.
On my device this corresponded exactly to the file I get directly from the device as root with
Code:
dd if=/dev/block/mmcblk0 of=n5110.pit bs=1 skip=17408 count=8192
Click to expand...
Click to collapse
Hi, using heimdall with Arch-Linux.
Problem: PIT can't flash on GT-N5100.
Question:
Does it right, that the right using of dd is in this case:
Code:
dd if=/dev/block/mmcblk0 of=[B]NAME_OF_THE_PIT[/B].pit bs=1 skip=17408 count=8192
A few years ago i'd crashed a hard disk and with the help of robi (Linux-Club.de) i fixed it. (Look here: linux-club.de/forum/viewtopic.php?f=90&t=118487
So i know, prinzipally i can get an image from the Tablet with dd.
But I'm not a freak.
And I think, maybe it's better to safe the image first, bevore repairing.
That was the way with the harddisk, so no dates has been lost.
I think, the synthax to get an image from the Tablet is like this:
Code:
dd if=dev/sdx of=/mnt/sdx/sicherung/image_Tablet.img
Right?

Need pit file for at&t s3

Before I talk about my issue let me just say that im a noob compared to you guys. I decided to post here because I thought I would be able to get some helpful information. Please do not hate on me.
So I have been trying for a while to root my phone and it has been hard because the only computer I own is a chromebook. I was finally able to get my hands on my dads work laptop which is running linux (zorin os 7 based off ubuntu 13.04) and I decided to try a method I found called jodin3 which is like odin in the web browser. Everything went fine until I clicked to flash. It said that I needed a pit file and it said it could get it off my device. I clicked to do that and it said it failed. I then proceeded to try and find the pit file by going to google and when I had found a link it said that there was an error as you can see in the screenshot (it was taken on my chromebook but its exactly the same on the other computer). Can someone please give me a good link to download the pit file because im gonna need it to root my phone.

Welcome to the site. You don't want to flash a .pit file unless you really know what you are doing. The pit file will repartition your phone and if you use the wrong file, you are likely to end up with an expensive paperweight i.e. an unbootable phone that is difficult or perhaps impossible to fix.
I am not familiar with the jodin tool you refer to or why it needs a .pit file. In Odin you would normally ensure that repartition is unchecked and you would not need a .pit file to flash. Pit files are not usually needed unless you are recovering from a brick or (expertly) reallocating memory. Or flashing a full factory ROM, which will already incorporate a safe .pit file. The .pit file that you want will likely differ depending on your phone's memory size and you didn't specify things like your memory size, OS version or EFS format.
If I am missing something and you truly need a .pit file, then you should be doing a lot more reading so that you understand what a .pit file is and the risks of using one. There are threads on this forum that explain how to create .pit files although I can't personally vouch for their accuracy.
In your place though, I'd use a safer rooting method e.g
http://forum.xda-developers.com/showthread.php?t=2538991
.

PIT file for Galaxy G925T TMOBILE (ROM)-G925T_OC3_Stock_Restore

WHAT IS THE USE OF .pit FILE?
.pit FILE IS USED TO DIRECT THE PARTITION OF THE WHOLE ANDROID SYSTEM..JUST LIKE WE ARE DOING GRUB IN PC...HERE ALSO WE NEED TO PARTITION THE SYSTEM FOR FLASHING THE FIRMWARE PROPERLY.. AND HERE THE .PIT IS USED
1. Get your phone into download mode..
2. connect to computer. Make sure that usb drivers installed and you have the firmware.tar file.
3. Now open odin 3.10
4. click on PIT and select ZEROLTE_USA_TMO.pit
5. Make sure that partition is tick
6. click on PDA and select firmware.tar file
7. Now start button and wait...You are done
link:
https://drive.google.com/folderview...tmV3YxMTB4WGpSZU5ReEI1WjZtUXM&usp=sharing_eid

Mhhh could be useful great job Op

The link doesn't work for me, could you reupload it? Also does this contain data about your /data partition? If so this might be specific to your model (16/32/64 GB)

update the file
update the file

SHATTAH said:
update the file
Click to expand...
Click to collapse
Just requested permission for the file.

SHATTAH said:
WHAT IS THE USE OF .pit FILE?
.pit FILE IS USED TO DIRECT THE PARTITION OF THE WHOLE ANDROID SYSTEM..JUST LIKE WE ARE DOING GRUB IN PC...HERE ALSO WE NEED TO PARTITION THE SYSTEM FOR FLASHING THE FIRMWARE PROPERLY.. AND HERE THE .PIT IS USED
1. Get your phone into download mode..
2. connect to computer. Make sure that usb drivers installed and you have the firmware.tar file.
3. Now open odin 3.10
4. click on PIT and select ZEROLTE_USA_TMO.pit
5. Make sure that partition is tick
6. click on PDA and select firmware.tar file
7. Now start button and wait...You are done
link:
https://drive.google.com/folderview...tmV3YxMTB4WGpSZU5ReEI1WjZtUXM&usp=sharing_eid
Click to expand...
Click to collapse
Can you please explain how you got the pit file? from what I understand you cannot simply dump the pit anymore unless I missed something.

requested access to this as well-- can you post somewhere other than Google Drive as people cant get to this file?!

can you please grant my request to download the file? I have a soft bricked phone and I really need the Pit file. thanks so much

looking a pit file for latest firmware 5.1.1 G925TUVU2COF6 does anyone have?

onlineunlocks said:
looking a pit file for latest firmware 5.1.1 G925TUVU2COF6 does anyone have?
Click to expand...
Click to collapse
According to: http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
Requirement: To be able to use any of the methods described below [to extract the PIT file], you must have root privilege on your Galaxy device. Both the methods have been tested on the Samsung Galaxy S5.
Click to expand...
Click to collapse
This means that, unless someone gets it directly from Samsung somehow (leak, release, or otherwise), you'll need to wait for root on the 5.1.1 stock ROM.
I don't know a whole lot about the PIT file, and why someone would ever need it (apart from screwing around so much that you overwrite your partition information on the device... which would be hard for the average user to accidentally do).
Have you tried Samsung Smart-Switch? I don't know if it's capable, but it might download the PIT info from the internet before restoring stock firmware on a 100% borked device.

Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it

onlineunlocks said:
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
Click to expand...
Click to collapse
Let us know if this worked. I need to restore back to 5.0.2 also from 5.1.1. Thanks

will not work to restore to 5.0.2 from what I know and might also damage it,so do not recommend to try that

onlineunlocks said:
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
Click to expand...
Click to collapse
I'm in the same situation.
Have you found a solution?

Aou said:
According to: http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
This means that, unless someone gets it directly from Samsung somehow (leak, release, or otherwise), you'll need to wait for root on the 5.1.1 stock ROM.
I don't know a whole lot about the PIT file, and why someone would ever need it (apart from screwing around so much that you overwrite your partition information on the device... which would be hard for the average user to accidentally do).
Have you tried Samsung Smart-Switch? I don't know if it's capable, but it might download the PIT info from the internet before restoring stock firmware on a 100% borked device.
Click to expand...
Click to collapse
is this gonna fix my phone if efs is not mounted??? me and my buddy have no idea how he broke his phone.