Question How to flash stock ROM without PIT file - Samsung Galaxy A02s

Recently I soft bricked my phone attempting to debloat some files on my phone. I was dumb and did this while there were files on the phone I wanted. I have seen from other posts on XDA that you can recover these files by flashing the stock ROM for my device. I used Odin to attempt this after downloading official stock firmware, but after attempting to flash the AP/ADP it said it required a PIT file for flashing. I know that it stands for Partition Information Table, and assuming PIT modifies the partitions in some way, I would prefer not to mess with the current partitions what so ever. Assuming PIT doesn't modify the partitions, after I obtained the PIT file Odin said that the PIT file was corrupted, even though I had just used Heimdall for obtaining the PIT file.
Is there a way to avoid using a PIT file at all?
Why do the PIT files for my device all give the "corrupted file" error on Odin?
Is there a better way to recover my device's files?
Does using a PIT file erase the current partitions or do I have to check "re-partition" in Odin for it to erase my files?
Using the latest version of JOdin3 with the correct .tar.md5 img files for my device from a trusted source.

bump

bump

Try using a different version of odin

Related

[Q] Got a file I have to ODIN to my Vibrant; it's a .RAR, can I turn it into a .TAR?

Hi all. In an effort to search for the original SGH-T959 bootloaders that one can flash after flashing any of lidroid's ROMs, I came across the bootloaders. One problem, however. They came in a .RAR file. It contained 2 files: boot.bin and sbl.bin. I trust that they are correct and flashable. However, I need to flash it via ODIN. Therefore I un-RARed the file and then re-compressed it, but as a .TAR file this time around.
The .TAR file I created contains ONLY 2 files.
boot.bin
sbl.bin
My question is: am I missing anything in the .TAR or can I just go ahead and flash the .TAR to my Vibrant via ODIN?
EDIT: Also, I flash this in the BOOTLOADER section of ODIN, right? I know it sounds stupid, but I've heard of bootloaders being flashed in the PDA section of ODIN.

What is the best way to restore param.lfs?

I wanted to make an odin flashable tar of the stock param.lfs posted in Entropy's Return/Unbrick to stock thread. I made the tar file using terminal on my phone, as I have done in the past, but I did it wrong, and when I tested it, the flash failed and now my phone boots to the phone-!-pc screen.
I looked in the tar, and I had built it with the param.lfs in a directory named sdcard. Doh. So I tried to create the tar using 7zip on my Windows pc, and the resulting file is built correctly, but when I tried to flash it, the flash froze on param.lfs. So I don't know if the tar I made with 7zip is bad, or what.
Shouldn't it be possible to just tar the param.lfs file and then flash it in the PDA slot? I should be able to get the phone back by flashing just the param.lfs, shouldn't I? But now I don't know if I can make a working Odin flashable tar on Windows.
So if someone can post an odin flashable tar of Entropy's stock param.lfs, that would be helpful. Thanks.
creepyncrawly said:
I wanted to make an odin flashable tar of the stock param.lfs posted in Entropy's Return/Unbrick to stock thread. I made the tar file using terminal on my phone, as I have done in the past, but I did it wrong, and when I tested it, the flash failed and now my phone boots to the phone-!-pc screen.
I looked in the tar, and I had built it with the param.lfs in a directory named sdcard. Doh. So I tried to create the tar using 7zip on my Windows pc, and the resulting file is built correctly, but when I tried to flash it, the flash froze on param.lfs. So I don't know if the tar I made with 7zip is bad, or what.
Shouldn't it be possible to just tar the param.lfs file and then flash it in the PDA slot? I should be able to get the phone back by flashing just the param.lfs, shouldn't I? But now I don't know if I can make a working Odin flashable tar on Windows.
So if someone can post an odin flashable tar of Entropy's stock param.lfs, that would be helpful. Thanks.
Click to expand...
Click to collapse
I believe 7zip creates bogus tars in Windows.
Try cygwin - or use Heimdall to flash
I was pretty sure that 7zip made bad tar files. I also downloaded peazip, and found that it also makes bad tar files.
I found a good flashable I777 stock param.lfs in Connexion2005's Custom Boot Screen thread. I had never looked inside his attachment and had assumed it was a modified param.lfs. I used it to flash my phone back successfully.

[Q] Odin Questions

Hello Forum,
I have downloaded ODIN for flashing and recovery, and as of the moment I have the Samsung Galaxy 5 (USA) Model. Now, I have previously flashed and recovered stock with it but I don't know which files do what.
I have a PIT file, a BOOTLOADER, and a PDA file. Could someone give me a depth description of what each one does? I doubt I'm suppose to use all three all the time in case I've bricked my device or flashing.
Thanks in advance.
PIT stands for Partition Information Table. It basically tells odin how big each partition is, how their arranged, etc. It doesn't contain the actual contents of those partitions, just how they're laid out on the drive.
The PDA file is your actual system image, and is usually compressed as a .tar (or tar.md5) file. It will contain a kernel and one or more partition images which contain the actual contents of the partitions that're described in the .PIT file.
To flash with Odin (or Heimdall, for that matter) you need a .pit and one or more partition images. I'm not too sure how you'd use the separate bootloader file in Odin. I'm still something of a n00b at this.
JrixZero said:
Hello Forum,
I have downloaded ODIN for flashing and recovery, and as of the moment I have the Samsung Galaxy 5 (USA) Model. Now, I have previously flashed and recovered stock with it but I don't know which files do what.
I have a PIT file, a BOOTLOADER, and a PDA file. Could someone give me a depth description of what each one does? I doubt I'm suppose to use all three all the time in case I've bricked my device or flashing.
Thanks in advance.
Click to expand...
Click to collapse
dstarfire said:
To flash with Odin (or Heimdall, for that matter) you need a .pit and one or more partition images. I'm not too sure how you'd use the separate bootloader file in Odin. I'm still something of a n00b at this.
Click to expand...
Click to collapse
You actually don't need a .pit file to flash with odin. All you need is the .PDA file. I believe the .pit file is only for if you want to re-partition the drive as well. Forgot to mention make sure only Auto Reboot and F.Reset Time are checked when flashing in odin with a .pda file or you will brick your device.
Thank you guys for that, I figured more or less what you are saying. I just needed confirmation! :good:
Using Odin to flash the TerraSilent Kernel
I would like to flash TerraSilent Kernel 1.3.5 for Galaxy 4.0 (YP-G1) USA. I have downloaded Odin3 v1.7, and would just like to confirm the steps, as this is the first and only Android device I have and wouldn't like to brick it. (This is the also my initial step to flashing the EtherealRom V2.4 ROM.)
I have the Samsung Drivers installed. That is all I need to use Odin right?
Steps:
Download the TerraSilent_usa-1.3.5.tar file
Put Galaxy Player in download mode (Power Button + down)
Connect the Galaxy Player to the computer
Start Odin
Ensure only Auto Reboot and F.Reset Time are checked.
Select PDA and choose the "TerraSilent_usa-1.3.5.tar" file that I previously downloaded
Then click start.
I have some other questions, I have been reading up the forums and would like to clarify something with the .pit file. Is it only required when you would need to to re-partition the drive? and therefore installing a kernel does NOT require a re-partition of the drive, am I correct?
Which of the following scenarios would REQUIRE a re-partition of the drive (and thus a .pit file when using Odin)?
- Flashing a Full STOCK ROM (with Recovery) for e.g here http://forum.xda-developers.com/showthread.php?t=1531850
- Flashing a Stock-based ROM such as EtherealRom V2.4 ROM
- Flashing a Recover such as CWM
I'm new to this Android ROM scene so I just trying to get a better understanding of this all.
Thanks in advance.
jonnysdroid said:
I would like to flash TerraSilent Kernel 1.3.5 for Galaxy 4.0 (YP-G1) USA. I have downloaded Odin3 v1.7, and would just like to confirm the steps, as this is the first and only Android device I have and wouldn't like to brick it. (This is the also my initial step to flashing the EtherealRom V2.4 ROM.)
I have the Samsung Drivers installed. That is all I need to use Odin right?
Steps:
Download the TerraSilent_usa-1.3.5.tar file
Put Galaxy Player in download mode (Power Button + down)
Connect the Galaxy Player to the computer
Start Odin
Ensure only Auto Reboot and F.Reset Time are checked.
Select PDA and choose the "TerraSilent_usa-1.3.5.tar" file that I previously downloaded
Then click start.
I have some other questions, I have been reading up the forums and would like to clarify something with the .pit file. Is it only required when you would need to to re-partition the drive? and therefore installing a kernel does NOT require a re-partition of the drive, am I correct?
Which of the following scenarios would REQUIRE a re-partition of the drive (and thus a .pit file when using Odin)?
- Flashing a Full STOCK ROM (with Recovery) for e.g here http://forum.xda-developers.com/showthread.php?t=1531850
- Flashing a Stock-based ROM such as EtherealRom V2.4 ROM
- Flashing a Recover such as CWM
I'm new to this Android ROM scene so I just trying to get a better understanding of this all.
Thanks in advance.
Click to expand...
Click to collapse
True all you need is the .tar file to flash. The pit file is usually unneeded when flashing a custom rom. However, make sure you turn on USB debugging first (Settings->Applications->Development-> Check USB debugging) before flashing anything. Sometimes just not having that checked gets you into bootloops and cause problems.
PIT files are used when you get your partition tables messed up. I believe this means you're not able to boot into the device or access download mode anymore (basically for Bricked devices). So you 90% (made up statistic =P but you get the point) of the time when you are flashing back to stock, you just need again the .tar file (unless as I said previous your device is bricked). You almost never need a PIT file to flash a custom rom from stock, and Flashing from CWM only requize a .zip file that's still in the zip form (meaning don't unzip it with winRAR, 7zip, and similiar programs
For more on PIT Files go here http://forum.xda-developers.com/showthread.php?t=999097
Remember to hit the thank button if you find this information useful =D

Galaxy s3 Odin Pit for bricked device

Hi to all!
Yesterday i bricked my phone flashing a new rom. I was on philz recovery and wiped everything,boot,modem,etc... flashed the rom and after bootloader the phone was on black screen.
Fortunately i found a pit file for my s3 16gb. I placed it on odin with pda tar md5 and successfully got out of the brick.
My question is.
There are 2 sections in odin. Phone and csc. I didn't have such files. Did i need them because of the brick and because of using pit ?
Nope. Those are if you're going to flash the files independently from the *_HOME.tar.md5 from sammobile. You can ignore those check boxes. You just need the *.pit file, and the *_HOME.tar.md5 file you want to flash.
I thought because of the brick those 2 partitions were also corrupted. . In fact pit file re partitiones also modem but i didn't have one selected in odin.. strange it worked all finely. .

[GUIDE][NoobProof] PARTITION i777 PHONE FOR MORE DATA STORAGE

This guide is to help those who may want to have more data storage including system partition for much more.​
NOTE: DOING THIS WILL DEFINITELY VOID WARRANTY AND ANYTHING THAT HAS TO DO WITH IT. I WILL NOT BE HELD LIABLE SHOULD
ANYTHING GO WRONG.
THERE HAS BEEN REPORTED SUCCESS SO FAR BUT SHOULD YOU END UP WITH AN EXPENSIVE PAPERWEIGHT, THAT IS YOUR OWN DOING. PROCEED WITH CAUTION.....YOU ARE WARNED.​
I HAVE PERSONALLY DONE THIS WITH SUCCESS. BELOW IS IMAGES AFTER I AM DONE WITH EVERYTHING.​
PRE-REQUISITE​
PATIENCE.............LOTS OF IT INCLUDING A STONE COLD HEART TO GO THROUGH THIS
A samsung S2 (i777/attain......to be more precise)
Backup, Backup, Backup...........that includes the phone internal memory.
Acceptance to loose everything stored in the phone internal memory.....if you need them, perform the step above.
A couple of files which i have provided the links to in the procedure and also below the post. Please use only what is provided here. Thanks.
PROCEDURE ​
1. Enter download mode (NOT through the reboot menu.)
Rather, hold in volume up and down and then while doing so plug in the usb cable to the phone from the computer.
2. Use Odin to install the full Samsung UCMD8 release (Already has pit file).
3. Flash the downloaded stock rom above using Odin.
4. Reboot to recovery and factory reset when done.
5. Boot device, install framaroot, enable usb debugging before rooting device.
6. Install mobile odin. Reboot.
7. In mobile odin, install new kernel w/ recovery (since this method is for i777, you can use Shift kernel....which i used, need to extract only the "zImage.img" file from the .zip file, if file is named something else rename it to "zImage" and place it on the device for Mobile Odin to read.
8. In Mobile Odin, install the modded .pit file attached below. Thanks to [-Stash-]
Read more about the partitions here and here.
NOTE: Using odin for pc for STEP 8 is also very much working.....espercially for those having issues flashing pit file with the mobile odin version.
9. Reboot to recovery; format / wipe partitions (this includes system, data, internal sd, cache, dalvik).
10. If internal cannot format or gives error, connect phone to pc and mount storage, you can then format as fat32 from windows or whatever operating system you are using (recommended system). When done, unmount and try step above again just to be certain.
11. Flash any new ROM of choice (I use SlimSaber by Cyril279), Gapps (I use slim full gapps,) modem for AOSP roms (I used UCMD8, works best for me but may not be the same for your location, please use what works best for you), and any other addon packages.
12. Optional........enable ART runtime in developer options. Reboot, and wait a long time for it to compile apps ahead of time.
13. Just enjoy :good::good:
Another link for my personal files used(same as those here)
CREDIT IN NO PARTICULAR ORDER​
Gabes Dad............................... for most of the guide and also making me take the dive.
Cyril279
Chainfire
RockRatt
mtpi
[-Stash-]
alephzain
creepyncrawly​
Mobile Odin .pit file
Great guide and idea! Thanks for your work!
I'm having trouble at step #8, Using Mobile Odin to install the modded .pit file.
I can't get Mobile Odin to see the .pit file, either as provided, in the .rar container, or as the bare .pit file.
I saw in the posts on this by [-Stash-], which you reference, that regular Odin was used to install the .pit file.
I've read elsewhere that Mobile Odin can't work with .pit files, but I gather you have found a way.
Your guide worked great up until #8, and also after #8.
I was able to continue on and install a great KitKat rom, TheGeekyNimrod's new Unofficial Carbon Rom and the RB-Shift kernel, just without the new partition sizes.
Thanks again for posting this guide, and doing the work necessary to come up with it. I'm looking forward to this better partition scheme.
I would be grateful for any help you could provide.
DanViolaMan said:
Great guide and idea! Thanks for your work!
I'm having trouble at step #8, Using Mobile Odin to install the modded .pit file.
I can't get Mobile Odin to see the .pit file, either as provided, in the .rar container, or as the bare .pit file.
I saw in the posts on this by [-Stash-], which you reference, that regular Odin was used to install the .pit file.
I've read elsewhere that Mobile Odin can't work with .pit files, but I gather you have found a way.
Your guide worked great up until #8, and also after #8.
I was able to continue on and install a great KitKat rom, TheGeekyNimrod's new Unofficial Carbon Rom and the RB-Shift kernel, just without the new partition sizes.
Thanks again for posting this guide, and doing the work necessary to come up with it. I'm looking forward to this better partition scheme.
I would be grateful for any help you could provide.
Click to expand...
Click to collapse
I would imagine you could still use regular ODIN for step 8, just put the phone back into download mode. Take this with a grain of salt as this is just a guess.
DanViolaMan said:
Great guide and idea! Thanks for your work!
I'm having trouble at step #8, Using Mobile Odin to install the modded .pit file.
I can't get Mobile Odin to see the .pit file, either as provided, in the .rar container, or as the bare .pit file.
I saw in the posts on this by [-Stash-], which you reference, that regular Odin was used to install the .pit file.
I've read elsewhere that Mobile Odin can't work with .pit files, but I gather you have found a way.
Your guide worked great up until #8, and also after #8.
I was able to continue on and install a great KitKat rom, TheGeekyNimrod's new Unofficial Carbon Rom and the RB-Shift kernel, just without the new partition sizes.
Thanks again for posting this guide, and doing the work necessary to come up with it. I'm looking forward to this better partition scheme.
I would be grateful for any help you could provide.
Click to expand...
Click to collapse
Sorry for the late reply............using odin to flash in download mode also works perfectly. the pit does not harm in anyway (at least for me so far).
When done with pit flash in download mode,.............wait for for a minute or two.
Boot to recovery and format all partitions including internal. Had to mount internal partition and format with pc.
Hope this helps
worked
Thanks. I did this. Although, when the phone boots the initial 'Samsung galaxy sii' splash is now changed to 'SAMSUNG' with the flash of the stock JB, i think. (actually, i dont remember if it was that, or if it was the ICS Semi_v18 ROM I flashed earlier for a different purpose). That splash screen seems to stay longer than before. Anyways, I used mobile odin (need the i777 flash kernel) to flash shift-v4.8 kernel, and then odin to flash the pit file from my computer. I did not have to format with the computer as the recovery seemed to do it fine.
anyone tried this on the SGH-S959G I curently run @cyril279 slimsaber and want to be able to install the full slim gaaps instead of the mini gapps. Plus I feel eventually we will all need bigger system partition if we keep these phones. Or do I need a different pit file?
Figured it out. Modified original pit.
Thanks a lot for the guide.
This worked fine for me. Initially, I didn't get a cellular signal but then I realized that I missed that instruction embedded in step #11. I'm currently using CM11 M10 build with it.
I assume this will work with any custom ROM, but would it work with stock ROMs that are flashed via Oden, or would this kind of flash put the old partition table back?
Hey, could reupload the .pit file? It's 404'd.
leeroyjenkins11 said:
Hey, could reupload the .pit file? It's 404'd.
Click to expand...
Click to collapse
Sure. Where I hosted the files has been down for weeks now. Thanks for alerting me.
hey i want to just use the stock rom with stock kernel. So could i just stop at which step. Please help me
virajjjj said:
hey i want to just use the stock rom with stock kernel. So could i just stop at which step. Please help me
Click to expand...
Click to collapse
I think the safest way would be to follow his steps all the way through step 10, then in step 11 re-install the UCMD8 stock firmware using desktop Odin.
Just wanted to say thanks for the writeup! I was frustrated with having to install PA Nano Gapps, so this guide and your modded .pit file were perfect. Just finished installing LS 3.2 Milestone with PA Stock Gapps! :highfive:
Confused & stuck at step 7
Updated: I finally succeed to re-partition; however, I could not go back to SHOstock3 v4 (4.1.2)
If my phone already has a recovery installed and is rooted, can I go ahead and install the modified pit file with mobile odin and proceed from there? why exactly would I need to flash ucmb8 through odin?
bleggy said:
If my phone already has a recovery installed and is rooted, can I go ahead and install the modified pit file with mobile odin and proceed from there? why exactly would I need to flash ucmb8 through odin?
Click to expand...
Click to collapse
Same question.
Sent from my SGH-I777 using XDA Free mobile app
When you flash a new pit through odin everything gets erased except external sd card so use a computer and follow the instructions.
Thanks. I'm attempting to follow the instructions, but I need to use Heimdall instead of Odin. If anyone is familiar with Heimdall, I'd greatly appreciate your help.
I downloaded I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z file and extracted the contents to a folder.
[email protected]:~/heimdall$ ls
boot.bin I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 Sbl.bin
cache.img I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z zImage
factoryfs.img modem.bin
hidden.img param.lfs
and then boot into download mode and ran: sudo heimdall flash --kernel zImage --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --param param.lfs --modem modem.bin
I receive the following:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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...
PIT file download successful.
ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
What should I be doing differently?
EDIT: looks like partition names are capitalized! , so it should be sudo heimdall flash --KERNEL zImage --FACTORYFS factoryfs.img --CACHE cache.img --HIDDEN hidden.img --MODEM modem.bin
To be safe, I shouldnt mess with boot.bin, param.lfs, Sbl.bin, right? or is this necessary here?
Looking forward, does anyone know the exact command to flash the modified .pit file? Would it be:
sudo heimdall flash --repartition --pit .pit ?
Problem
Okay i did something wrong and just i had softbricked my phone and i can just enter into download mode but it fails and gives me write failed error. What can i do now. Help needed please
alright. this got me where I wanted to be:
sudo heimdall flash --KERNEL zImage --FACTORYFS factoryfs.img --CACHE cache.img --HIDDEN hidden.img --MODEM modem.bin
I still cant figure out how to flash the .pit in heimdall.
I receive this:
[email protected]:~/Downloads/heimdall$ sudo heimdall flash --repartition --pit i777_4GB\ data\ -\ 45mb\ preload\ -\ 1GB\ system.pit
[sudo] password for bleggy:
Action: flash
Arguments:
--repartition --pit <filename>
--<partition name>|--<partition identifier> <filename> [...]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
or:
--<partition name>|--<partition identifier> <filename> [...]
[--pit <filename>]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
any ideas?
Edit: Just read it in i9100 thread that this method should not be used if you want to run stock rom. So flashed backed original pit file from i9100 thread and now the phone is running like as it should be running.

Categories

Resources