Related
I recently put together a tutorial on how to extract files from a stock TAR.MD5 and one of the questions that came up most was “how do I create my own TAR.MD5’s?” I’m going to show you how to do that here.
The standard disclaimer applies here. This tutorial is just the beginning. It does not make you into a Elite Developer, it does not give you everything you need to conquer the world or even make your own ROM. What it does do is give you some of the tools to get you headed in that direction.
So what does this do for you? Well if you have the information from this thread and a few other places you could in fact build a full ROM that is flashable through Odin rather than through a custom recovery. No more need to root your phone beforehand, you could just plug it in to your computer and flash a custom ROM. I myself am not going to show you how to do a custom ROM but I promise you that the tools and resources are out there. That's how I learned this!
Before we dig in I have to make one thing clear – This tutorial does not show you how to make an Odin One-Click.exe. I will most likely never post instructions on how to do so. Most people don’t realize this but whenever you flash an Odin One-Click.exe you are taking a substantial risk and have the very real and distinct possibility that it will in fact completely brick your phone. Now, if it is done correctly there is absolutely no chance of it bricking your phone but the process of creating the One-Click.exe is very detailed and complex, one wrong variable or incorrect field and the whole thing is ruined. Now that I’ve scared you, you can rest assured that every One-Click on my site has been very thoroughly tested and are safe. Those who work on those One-Clicks (myself included) are exceptionally detail oriented and test all of their work before posting them. A huge thanks goes to Garwynn, Mohogalore and Sfhub for taking the One-Click process and making it as safe as it is for all of us!
I will also not be showing you how to make your own ROM. Yes, you could use this as a step in creating your own ROM but it involves more Linux than I know how to teach. The good news is that someone else far more talented than I has already put together the tools how to do it. For instructions on how to build your own factoryfs.img (this is where 99% of the ROM is stored in a TAR.MD5) please visit Chris41g's thread at http://forum.xda-developers.com/showthread.php?t=1750295.
Now for the fun stuff!
If you feel you already have a working knowledge of what a TAR.MD5 is and how it works you can skip all the rest of this and go directly to www.rwilco12.com for the rest of the tutorial on how to create your own TAR.MD5.
In order to create a flashable TAR you should first understand the way they work. I’ll give you a semi-brief rundown.
Each Samsung device is setup with several partitions. These partitions all control different aspects of each device. AdamOutler put together a good list of all of them when the Epic 4G Touch first came out. I’ve used his list (http://forum.xda-developers.com/showpost.php?p=17949633&postcount=8) as a base for my explanations.
For the Epic 4G Touch (SPH-D710) the partitions are as follows:
boot.bin – The first piece of the Bootloader. It initiates the activation of your device's memory and starts the SBL.bin.
SBL.bin – The second piece of the Bootloader. This is essentially its own operating system and can control the building and changing of all other partitions. When you flash something through Odin this is what Odin is communicating with.
param.lfs – This is the third and final piece of the Bootloader. This houses Download Mode, startup images and is where SBL.bin stores all of its information.
zImage – The kernel.
recovery.bin – Generally this is where the recovery is stored. However, in the E4GT the recovery is included in the kernel. For all intents and purposes this partition is just wasted space.
cache.img – Your cache partition. Apps and the system store data here to speed up loading times and responsiveness.
modem.bin – The modem. Interestingly enough AdamOutler explains that the modem.bin is essentially a mini operating system all by itself and this is the reason we can talk, surf and play with apps all at the same time.
factoryfs.img – This contains all of the system folders from your device.
data.img – This is where all your app data as well as some other information is stored.
hidden.img – This is your preload folder.So now we know what’s in the partitions themselves. Now what does this have to do with creating a TAR.MD5? Well each time you flash a TAR.MD5 it contains a given set of files. If you look at one of my Modem TAR.MD5’s you’ll see they contain only a modem.bin file. If you look at the kernel TAR.MD5’s you’ll just see a zImage. If you look at a full ROM (leaked or otherwise) you’ll generally see a full set of files with the same names as the partition files in the TAR.MD5. The reason for this is that each of those files in the TAR.MD5 is in fact a partition image. When you flash the TAR.MD5 it completely overwrites the existing partition and replaces it with the new one.
Now the other question I get is, “How is this different from flashing a ROM in a ZIP format?” The biggest difference is in how they flash. A TAR does one thing and the ZIP does another.
Essentially the TAR.MD5 is what is known as a TAR Ball. A TAR Ball is a compilation of multiple files into an ordered archive. You may not see the order when you open the archive as an archive but the way it is digitally signed determines the order the files are stored and accessed within the TAR (this is important when using Odin to flash). As we previously covered each of those files corresponds to a specific partition on the device. What you don't see is that the way that Odin works is it takes that partition image and completely replaces everything currently on the partition with the new partition image. That there is the major reason why a full TAR build will always wipe all data. The way around this is to remove the data.img and cache.img files. However, removing them from the TAR ball ruins the digital signature and corrupts it. So you can't just manually remove them from the TAR ball but you can pull out the files you need and rebuild a new one.
Now a ZIP ROM. Essentially the ZIP is a standard ZIP archive. The only difference is that CWM (or its variants) has a specific area that they look for a script. These are a bit trickier to understand. That script controls the flashing process. Generally you would write it in the script that a batch of files (based on file structure) goes to the same folder on a specific partition. For example, you have an app you want to flash to the system/apps folder. You create a folder within your ZIP archive that is called system, within that folder you create another called apps, and then you place the app in that folder. When CWM looks at the script in the archive it will tell CWM to mount the factoryfs.img partition and allow you to write to it. It then copies all the files from that given location to the same location on the device. In theory you could write a script that would pull the app from whatever folder in the archive and move it to another folder on the device but that just gets WAY too complicated. When flashing to factoryfs.img or data.img you generally are good to just flash, however there are times where you may want to flash a full ROM. In those cases it is better to wipe the partition (using CWM) before flashing so that there isn't any carryover or overlap between the two ROMs.
If you go into a modem or kernel ZIP archive you'll see that we just took the corresponding partition file and placed it directly in the ZIP. The script in this case acts much the same way as Odin and just replaces the full partition with the new image. Generally you only see four partitions mounted through CWM, modem.bin, zImage, factoryfs.img and data.img. You could mount the others but there isn't often a need to.
Now that there my friends gives you a basic understanding of how these work. Now if you still feel comfortable proceeding please go to www.rwilco12.com for the rest of the tutorial.
Before we dig in I have to make one thing clear – This tutorial does not show you how to make an Odin One-Click.exe. I will most likely never post instructions on how to do so. Most people don’t realize this but whenever you flash an Odin One-Click.exe you are taking a substantial risk and have the very real and distinct possibility that it will in fact completely brick your phone. Now, if it is done correctly there is absolutely no chance of it bricking your phone but the process of creating the One-Click.exe is very detailed and complex, one wrong variable or incorrect field and the whole thing is ruined. Now that I’ve scared you, you can rest assured that every One-Click on my site has been very thoroughly tested and are safe. Those who work on those One-Clicks (myself included) are exceptionally detail oriented and test all of their work before posting them. A huge thanks goes to Garwynn, Mohogalore and Sfhub for taking the One-Click process and making it as safe as it is for all of us!
Click to expand...
Click to collapse
Wait - you are sure to be asked the above ^ by someone I'm sure.
Thanks RWILCO12 for this excellent tutorial and write up. I may have more free time in the next few months and may be digging back in to the world of coding and compiling.
It's folks like you and all the other devs and contributors that make this such an awesome community! Thanks again.
leaderbuilder said:
Wait - you are sure to be asked the above ^ by someone I'm sure.
Thanks RWILCO12 for this excellent tutorial and write up. I may have more free time in the next few months and may be digging back in to the world of coding and compiling.
It's folks like you and all the other devs and contributors that make this such an awesome community! Thanks again.
Click to expand...
Click to collapse
Lol truth be told I think I get a PM or email at least once a week asking...
I would love to share with everyone but I myself bricked my phone as part of the learning process. I would hate to see it rushed and have someone brick their own and other people's devices.
When you get back into the game hit me up and we'll see if we can get you going.
Cool thanks for your time I'm learnin... yeah
Sent from my SPH-D710 using xda premium
Thanks for all the work you put in for all of us.
Sent from my SPH-D710 using Tapatalk 2
rwilco12 said:
Ice Cream Sandwich (ICS) TAR Ball flashing order:
param.lfs
boot.bin
zImage
recovery.bin
cache.img
data.img
hidden.img
factoryfs.img
modem.bin
Jelly Bean (JB) TAR Ball flashing order:
boot.bin
cache.img
data.img
factoryfs.img
modem.bin
hidden.img
param.lfs
recovery.bin
Sbl.bin
zImage
Click to expand...
Click to collapse
i have a T999L and am trying to get a working stock rooted odin flashable rom built, the only problem i see in your what needs to be written into the tarball is the T999L has sbl1 sbl2 sb3 and is the zmage the same as the Tz or no, i know how to dump all of the partitions but i dont know about zimage or the hidden img factory fs is the system partition right so it would be dd if=/dev/block/mmcblk0p14
MotoDefier said:
i have a T999L and am trying to get a working stock rooted odin flashable rom built, the only problem i see in your what needs to be written into the tarball is the T999L has sbl1 sbl2 sb3 and is the zmage the same as the Tz or no, i know how to dump all of the partitions but i dont know about zimage or the hidden img factory fs is the system partition right so it would be dd if=/dev/block/mmcblk0p14
Click to expand...
Click to collapse
The steps in this guide are specific to the Sprint Epic 4G Touch but with a little creativity could in theory be applied to all Samsung related.
Good news is that not all devices have a hidden.img so if it's not there I wouldn't worry about it.
The sbl being in multiple positions isn't uncommon either. Add them to the TAR ball in numeric order and that should take care of that.
I'm mobile right now so I can't confirm the exact devblock but Factoryfs is equivalent to system.img on other devices so you should be good.
As for the question on zImage, I've not heard of a tz partition. Is that the kernel on the t999? If so I would assume it would go in the place of the zImage.
Hopefully this helps a bit!
rwilco12 said:
The steps in this guide are specific to the Sprint Epic 4G Touch but with a little creativity could in theory be applied to all Samsung related.
Good news is that not all devices have a hidden.img so if it's not there I wouldn't worry about it.
The sbl being in multiple positions isn't uncommon either. Add them to the TAR ball in numeric order and that should take care of that.
I'm mobile right now so I can't confirm the exact devblock but Factoryfs is equivalent to system.img on other devices so you should be good.
As for the question on zImage, I've not heard of a tz partition. Is that the kernel on the t999? If so I would assume it would go in the place of the zImage.
okay after reading further on a few things related to the T999 which is the non lte version of the s3 i found this thread http://forum.xda-developers.com/showthread.php?p=30781353 that is based around bootloader unlocking and discoery of how, if it is a direct corelation between the data on the device the TZ patition stands for Trust Zone and is part of the initial boot sequence in which this allows the device to check for secure boot so now i am wondering if the kernel is included in the system which would explain why when i dump it with dd the system.img comes out to 1.48GB instead of the tradtional size of around a gig for the entire rom for a T999
Hopefully this helps a bit!
Click to expand...
Click to collapse
here is a list of all partitions, zimage is not one of them.
aboot p5
backup p20
boot p7
cache p17
efs p11
fota p19
fsg p21
grow p23
modem p1
modemst1 p12
modemst2 p13
pad p9
param p10
persist p16
recovery p18
rpm p6
sbl1 p2
sbl2 p3
sbl3 p4
ssd p22
syste p14
tz p8
userdata p15
all are on mmcblk0
im guessing since it doesnt have a zimage that the tz is the kernel
rwilco12 said:
Ice Cream Sandwich (ICS) TAR Ball flashing order:
param.lfs
boot.bin
zImage
recovery.bin
cache.img
data.img
hidden.img
factoryfs.img
modem.bin
Jelly Bean (JB) TAR Ball flashing order:
boot.bin
cache.img
data.img
factoryfs.img
modem.bin
hidden.img
param.lfs
recovery.bin
Sbl.bin
zImage
Click to expand...
Click to collapse
Thank you for such comprehensive tutorials,,
I got 3 question here..
1) How could I tell that the tar file created use the correct order if I was not the one who create it?
2) Could I use this command line to tar all dumps that I extracted from the ROM (by using wild star):
Code:
tar -H ustar -c *.img *.bin zImage > package.tar
3) And another query, after creating tar, I checked the permissions given to files by opening the tar by 7-zip.. In this created tar, all files are given the full permissions (0rwxrwxrwx); however, in the shipping original one, each file has different permissions!!!. The following is just an example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this going to affect the flashing process later on?
majdinj said:
Thank you for such comprehensive tutorials,,
I got 3 question here..
1) How could I tell that the tar file created use the correct order if I was not the one who create it?
2) Could I use this command line to tar all dumps that I extracted from the ROM (by using wild star):
Code:
tar -H ustar -c *.img *.bin zImage > package.tar
3) And another query, after creating tar, I checked the permissions given to files by opening the tar by 7-zip.. In this created tar, all files are given the full permissions (0rwxrwxrwx); however, in the shipping original one, each file has different permissions!!!. The following is just an example:
Is this going to affect the flashing process later on?
Click to expand...
Click to collapse
In answer to your questions:
1) How could I tell that the tar file created use the correct order if I was not the one who create it? This one is really hit and miss. The best method is to find a stock from the manufacturer TAR and flash it. Odin will flash it in the correct order. Take note of what Odin shows in the progress section and then use that as your flashing order. If you don't have that available it is a lot harder. You have to take them and put them in what you think is the best order and flash to see if you boot. If you don't try again. If you do? Awesome! You've got the boot order!
2) Could I use this command line to tar all dumps that I extracted from the ROM (by using wild star):
Code:
tar -H ustar -c *.img *.bin zImage > package.tar
In theory yes, but in practice no. The order that you put them in the TAR is what determines the flashing order. If you were to flash all the .img files and it grabbed the wrong .img file as the first item it could cause the device to not boot. I have played with the wild cards and have decided that best practice is to always to type them out one by one.
3) And another query, after creating tar, I checked the permissions given to files by opening the tar by 7-zip.. In this created tar, all files are given the full permissions (0rwxrwxrwx); however, in the shipping original one, each file has different permissions!!! Is this going to affect the flashing process later on? Long story short? Don't worry about it. Odin applies the correct permissions during the flash process. Each file within the img files (or bin, etc) comes with their own set of permissions and these are not inherited from the permissions within the TAR.
If you have any other questions or need any help let me know. More than happy to help.
Thanks!
rwilco12 said:
If you have any other questions or need any help let me know. More than happy to help.
Thanks!
Click to expand...
Click to collapse
Thanks a lot for this spirit man,, that's why I love xda tooooooo much :laugh:
I am planning to make a utility for win users by which you will be able to do partitions dumps and then TAR them as flashable odin file.. It will be good idea especially for dumping some ROM leak versions. of course I will include linux reader tool to be able to extract the dumped img for custom ROM cooking..
In the meantime, I will concentrate on studying since I have promotion exam coming after 18 days..
Thanks again
[QUESTION] so I have been working on an odin flashable rom for the T999L with another developer, when I tarball my files, if I open it in 7zip it doesn't show any permissions for the files, what am I doing wrong in the tar command? Also do all odin roms have to be tarballed in a certain order, or is that for the device you wrote this for only?
Sent from my SGH-T999L using xda app-developers app
MotoDefier said:
[QUESTION] so I have been working on an odin flashable rom for the T999L with another developer, when I tarball my files, if I open it in 7zip it doesn't show any permissions for the files, what am I doing wrong in the tar command? Also do all odin roms have to be tarballed in a certain order, or is that for the device you wrote this for only?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
Permissions really aren't important for the TAR file as Odin sets them as it is flashing the TAR. All Odin ROM's have to be TAR balled in a specific order that is unique to that device. However, the order is generally bootloader, kernel, data, system, modem (or very close to that).
Is it possible to find that order with out a stock firmware to flash in odin? Would it follow the boot sequence, example: boot, sbl1,rpm, tz, sbl2, sbl3, cache, system. This is pretty much the boot tree for the T999L, its been a while since I looked at it but I think that's right. Is there Any way flashing order follows boot tree order?
Sent from my SGH-T999L using xda app-developers app
MotoDefier said:
Is it possible to find that order with out a stock firmware to flash in odin? Would it follow the boot sequence, example: boot, sbl1,rpm, tz, sbl2, sbl3, cache, system. This is pretty much the boot tree for the T999L, its been a while since I looked at it but I think that's right. Is there Any way flashing order follows boot tree order?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
Generally they are pretty close to the same but I have run into a few cases where they haven't been. In those cases trial and error are the only route I've found.
rwilco12 said:
Generally they are pretty close to the same but I have run into a few cases where they haven't been. In those cases trial and error are the only route I've found.
Click to expand...
Click to collapse
Let me ask you this, would it work for me to tar the files with the wildcards and use the pit file and then I can get the correct order of the flash based on how odin flashes it with the pit file?
MotoDefier said:
Let me ask you this, would it work for me to tar the files with the wildcards and use the pit file and then I can get the correct order of the flash based on how odin flashes it with the pit file?
Click to expand...
Click to collapse
I honestly haven't tried that. If you want to give it a shot let us know if it works. Thanks!
how to make a wipe able csc for samsung phone
i m using this below command for making odin flash able file but it doesnt wipe data after flash
$ tar -H ustar -c cache.img.md5 hidden.img.md5 > csc.tar
$ md5sum -t csc.tar >> csc.tar
$ mv csc.tar csc.tar.md5
i want to know how to put a (wipe data/factory default) command in that to erase all phone after flash or automatically perform a full wipe after flash
like here is some sample of csc files these below files erase all phone after flash
CSC_ITV_I9505ITVAMDB_526507_REV06_user_low_ship_MU LTI_CERT.tar.rar
https://mega.co.nz/#!vENDyA6D!cMY2Ws...qx0PuHq hByU
CSC_ITV_I9505ITVAMDB_526507_REV06_user_low_ship_MU LTI_CERT.tar.md5
CSC_OJV_S7560OJVAMF5_1231180_REV02_user_low_ship.t ar
i dont know the exact name of these kind of csc files but i think some people call it multi csc
please help me
Odin flash just system
What if I just want to flash the system portion of the phone? is that possible or do I still need to make a TAR ball
kalanir said:
What if I just want to flash the system portion of the phone? is that possible or do I still need to make a TAR ball
Click to expand...
Click to collapse
Depends on what you have setup. You could flash it as a ZIP file through recovery and not have to do it as a TAR ball. If you want to flash through Odin or Mobile Odin you would need to do it as a TAR ball. You could do it in a TAR ball with just the system image though.
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?
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Zen Arcade said:
1 - Install the USB drivers for the i317m (from samsung web site)
2 - Download the latest Heimdall package from here - http://www.glassechidna.com.au/products/heimdall/
3 - Extract Heimdall to a folder on your PC and open a command window there
4 - Connect the phone in download mode to your PC. From windows go to the drivers folder and run zadig. Consult the readme or search XDA on instructions on how to configure the heimdall driver. The device you are looking for might be shown as "Gadget Serial" for the i317.
5 - Now go back the the command window you opened and enter the following commands:
5a - heimdall detect [this will tell you whether the interface is working]
5b - heimdall download-pit --output i317m.pit --no-reboot
6 - check your heimdall folder, you should have a file called i317m.pit if everything worked
7 - If this allows you to successfully repartition your phone, upload the resulting pit here for others to use
Click to expand...
Click to collapse
hellocng said:
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Click to expand...
Click to collapse
Did you ever find a good download? I am trying to pull a pit file from a newly upgraded i317m Stock 4.3 but it is failing during the pit download... I have another i317m that is in the same boat as yours so any help/info you have would be helpful
Cheers
full flash?
Any progress in acquiring a full flash for this phone?
hellocng said:
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Click to expand...
Click to collapse
emutter said:
Any progress in acquiring a full flash for this phone?
Click to expand...
Click to collapse
The pit file is here - http://forum.xda-developers.com/showthread.php?t=2609871
The 4.1.2 and 4.3 stock firmwares are available from sammobile.com and do contain bootloader and tz (and most everything else except param and tombstones).
I've not seen a param file for the i317m... if someone wants to extract them from stock rooted 4.1.2 and 4.3 and share them I will resize and post them.
To do so run these commands from terminal emulator on phone:
Code:
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/param.bin
PM me and let me know what firmware you were running and what specific phone - i.e. i317-rogers or bell or ...
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.
I'm trying to flash stock ROM on my Galaxy Tab A with Heimdall 1.4.0 (Odin doesn't work - see thread https://forum.xda-developers.com/galaxy-tab-s/help/samsung-t550-galaxy-tab-unlock-t3665660)
The first part of Heimdall (as far as I can tell) is to install drivers and then download the PIT file. The drivers have installed without issue but when I try and download the PIT file i get the error below. I have read similar issues online and they suggest using a newer, unreleased version 1.4.2 of Heimdall and something about a the latest commits and master? I'm totally lost with this!! I'm not sure if this will work so I'm open to any ideas... and some guidance
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
jimmisavage said:
I'm trying to flash stock ROM on my Galaxy Tab A with Heimdall 1.4.0 (Odin doesn't work - see thread https://forum.xda-developers.com/galaxy-tab-s/help/samsung-t550-galaxy-tab-unlock-t3665660)
The first part of Heimdall (as far as I can tell) is to install drivers and then download the PIT file. The drivers have installed without issue but when I try and download the PIT file i get the error below. I have read similar issues online and they suggest using a newer, unreleased version 1.4.2 of Heimdall and something about a the latest commits and master? I'm totally lost with this!! I'm not sure if this will work so I'm open to any ideas... and some guidance
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Click to expand...
Click to collapse
Are you using Heimdall on a native Linux machine or Windows?
You need a native Linux PC and the command line version of Heimdall.
ashyx said:
Are you using Heimdall on a native Linux machine or Windows?
You need a native Linux PC and the command line version of Heimdall.
Click to expand...
Click to collapse
Oh I'm using Windows 10. I don't have access to a Linux PC... Where does that leave me? Totally flummuxed?
jimmisavage said:
Oh I'm using Windows 10. I don't have access to a Linux PC... Where does that leave me? Totally flummuxed?
Click to expand...
Click to collapse
Unless you can dual boot a Linux distro with W10 or download one of the Live Bootable from disk Linux distros. There's plenty about.
https://help.ubuntu.com/community/LiveCD
Finding time to try this is proving troublesome. What are the chances this will actually work (more than Odin)?
I'm just trying to work out if it's actually worth the time/hassle?
Hi,
I finally managed to find some time and i'm currently on a lunix machine (from usb boot).
Now, do i need a 'Heimdall Firmware Package' or do i use the Samsung firmware for the SM-T555 you posted before?
jimmisavage said:
Hi,
I finally managed to find some time and i'm currently on a lunix machine (from usb boot).
Now, do i need a 'Heimdall Firmware Package' or do i use the Samsung firmware for the SM-T555 you posted before?
Click to expand...
Click to collapse
Just flash the stock firmware.
Okay, I had a nightmare on this last night.
I was using Ubuntu 14.04 but when i opened a terminal and typed 'heidmall-frontend' it would tell me that it wasn't installed and to try (something like) 'sudo apt install heimdall-flash-frontend' but then it would tell me that it doesn't exist.
What version/build of Linux should i be using (as a USB boot) and how do i install heimdall frontend?
Also, when reading instructions on flashing a rom they all say to use a heimdall firmware but you're saying i can use the stock firmware? How would i install that? Will heimdall recognise the .zip file?
Thanks again, i know i'm being a pain but i was up until 1am last night (waiting for the longest firmware download ever!!) trying to flash this!
jimmisavage said:
Okay, I had a nightmare on this last night.
I was using Ubuntu 14.04 but when i opened a terminal and typed 'heidmall-frontend' it would tell me that it wasn't installed and to try (something like) 'sudo apt install heimdall-flash-frontend' but then it would tell me that it doesn't exist.
What version/build of Linux should i be using (as a USB boot) and how do i install heimdall frontend?
Also, when reading instructions on flashing a rom they all say to use a heimdall firmware but you're saying i can use the stock firmware? How would i install that? Will heimdall recognise the .zip file?
Thanks again, i know i'm being a pain but i was up until 1am last night (waiting for the longest firmware download ever!!) trying to flash this!
Click to expand...
Click to collapse
Don't try and use a fronted. Use the command line. There is no such thing as Heimdall Firmware as far as I'm aware.
Heimdall flashes images which can be extracted from the stock firmware.
If you search Google for Heimdall flash commands you will find the correct syntax required to flash images.
Thanks for that.
I'm not at home to try right now, but i want to be as sure as possible i'm getting this right. I'm going to...
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-select-model?record=3EFD4C401EE211E7963AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware)... only my downloaded firmware is .zip rather than .img ???? https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
Do i unzip the firmware file i've downloaded? I've tried to do that in linux but it failed, maybe i need to unzip in windows?
jimmisavage said:
Thanks for that.
I'm not at home to try right now, but i want to be as sure as possible i'm getting this right. I'm going to...
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-select-model?record=3EFD4C401EE211E7963AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware)... only my downloaded firmware is .zip rather than .img ???? https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
Do i unzip the firmware file i've downloaded? I've tried to do that in linux but it failed, maybe i need to unzip in windows?
Click to expand...
Click to collapse
That's more or less correct. You should be able to extract the image from the zip using the stock utility in Linux. Ensure md5 is changed to tar.
If not then Peazip for Linux or 7zip for Windows.
Thanks again! I'll have one more go at this tonight... if it doesn't work then it's going in the bin and I can go back to living my life
Whilst in work i decided to download the firmware again and see if i could extract the image from the zip.
I have successfully completed that. It's currently named 'T555XXS1BPL4_T555BTU1BPE2_T555XXU1BPD7_HOME.tar.md5'. Do i simply delete the .md5 on the end to leave the .tar or is there something more complicated than that? Shouldn't it be a .img or am i just being overly concerned about details?
My head is going to explode!
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-s...3AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware) WHEN I DO THIS I GET A MESSAGE SAYING HEIMDALL IS NOT INSTALLED. HOW DO I INSTALL IT?
jimmisavage said:
My head is going to explode!
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-s...3AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware) WHEN I DO THIS I GET A MESSAGE SAYING HEIMDALL IS NOT INSTALLED. HOW DO I INSTALL IT?
Click to expand...
Click to collapse
It seems you are making this more complicated than it needs to be. Admin is the root user on a Linux system.
The instructions at the link below pretty much explain what you need to do.
http://www.dudleymediagroup.com/Detail/id/installing-using-heimdall-on-with-linux-3547
It seems i'm using Ubunto 16.04 and I cannot see a heimdall version for that? I guess I need to try Ubuntu 13.04?
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
jimmisavage said:
It seems i'm using Ubunto 16.04 and I cannot see a heimdall version for that? I guess I need to try Ubuntu 13.04?
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
Click to expand...
Click to collapse
I should think you'll be fine with 16.04 or 14.04
ashyx said:
I should think you'll be fine with 16.04 or 14.04
Click to expand...
Click to collapse
I don't see 16.04 or 14.04 in the download options though. Only 13.04 or 12.10.
What am I missing here? If I download ubuntu13.04-heimdall_1.4.0-0_amd64.deb and click install nothing seems to happen. The same goes for ubuntu12.10-heimdall_1.4.0-0_amd64.deb (I'm running Ubuntu 16.04 Live x64 from a USB drive).
jimmisavage said:
I don't see 16.04 or 14.04 in the download options though. Only 13.04 or 12.10.
What am I missing here? If I download ubuntu13.04-heimdall_1.4.0-0_amd64.deb and click install nothing seems to happen. The same goes for ubuntu12.10-heimdall_1.4.0-0_amd64.deb (I'm running Ubuntu 16.04 Live x64 from a USB drive).
Click to expand...
Click to collapse
From the directory where it is located try:
sudo dpkg -i ubuntu13.04-heimdall_1.4.0-0_amd64.deb
Got heimdall installed but i cannot flash anything.
Time to give up. Thanks for all the help