In the KA7 ROM I downloaded, theres the .tar file, a .bin file, but no PIT file. DO I just flash with no PIT? Also, what do I do with the .bin? Thanks!
After an attempt to root with Odin3, which by the way ended with a Fail.
(Note: When I tried to root the phone I didn't click PDA and designated a .tar)
My phone turns on and goes to a screen with an exclamation mark in a triangle with the message of "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I haven't found a solid post on how to fix this.
any help?
-------------FIXED------------
I used the wrong PDA file for my Skyrocket. It is not a 1777. GOES TO SHOW, BE CAREFUL, the smallest and dumbest mistake can waste you a lot of time...
This happens when you flash a bad tar file. I have had it happen with a bad param.lfs in the PDA slot. I'm not really sure, but I think it depends on what you actually had in the bad tar file. My problem was solved by flashing a good param.lfs tar. So I hosed the param.lfs with a bad tar, and then fixed it by flashing a good tar.
I can't say any more about your situation without knowing exactly what you tried to flash with Odin. You say you did not put anything in the pda slot, but what exactly was the configuration? What were you flashing with odin? A kernel?
So this is what I did to get me in this situation.
I followed these instructions...
http://forum.xda-developers.com/showthread.php?t=1309293
and instead of a success, I got a red Fail!. I forgot whether I put in a .tar or not, i very well might have not. If that means anything. But now when I put in a .tar is still says fail regardless.
That tar file contains zedomax's kernel for rooting and ClockworkMod Recovery. It only contains the zImage which is the kernel.
I think you can recover by flashing Entropy512's Unbrick/Return to Stock plus root using Odin. You can find his thread in the development forum, or use the instructions and the one-click downloader in step 2c of my guide. This will also give you the root you are trying to get.
Let us know if you have success.
I get a Fail! on the Odin One Clicker.
"<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)"
The error is beyond my knowledge. At this point I am only speculating. Maybe one of the developers will help.
I'm thinking that somehow some other part of the file system was damaged during the first Odin flash. The Unbrick/Return to Stock package does not flash the secondary bootloader or the param.lfs. You could try flashing those two files one at a time, starting with param.lfs first, to see if one of them is the problem. There is always risk when flashing bootloaders or the param.lfs. And again, I am only speculating. And further, while I've learned quite a lot from reading and doing, I am not a developer.
If you want to try those options, downloads and instructions are available in the Download Repository.
Alright, if worst comes to worst I can try exchanging it. I got the phone about 2 weeks ago so I still have a 30 day return/exchange.
You really shouldn't have to exchange it. You are soft bricked, as it is called. As long as you can get into download mode, you can recover the phone.
Since you can boot into download mode, it is clear that your bootloaders are still good. You have already attempted to flash --factoryfs --kernel and --modem. That leaves the following sections of the file system that could be causing the problem. --cache --dbdata --param and the partition table.
If it was my phone, I would next try flashing the param.lfs using Odin. After that I think I would switch over to Heimdall command line and flash --factoryfs --kernel --modem and --param together.
Maybe Entropy will see this and have some suggestions.
I hate to potentially put this burdon on you, but could you link me to those files your refering to?
ashaiba said:
I hate to potentially put this burdon on you, but could you link me to those files your refering to?
Click to expand...
Click to collapse
For param.lfs, downloads and instructions are available in the Download Repository, both the tar for odin, and the file for heimdall.
For the stock rom parts, extract factoryfs.img, zImage and modem.bin from downloads available in Entropy512's UCKH7 Return/Unbrick to Stock thread in the development forum.
How to flash Entropy512's Return/Unbrick to Stock, Kernel + Non-Rooted System Package with the param.lfs and the modem from the command line using Heimdall
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
Download Entropy512's Return/Unbrick to Stock kernel plus non-rooted system package and the modem package. Extract the PDA.tar files from this package to a directory on your hard disk drive, then extract the three component files from the tar - zImage, factoryfs.img and modem.bin.
Place zImage, factoryfs.img, modem.bin and param.lfs in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --factoryfs factoryfs.img --param param.lfs --kernel zImage --modem modem.bin
First try flashing just the param.lfs tar using Odin. Try the Heimdall flash if that doesn't work.
OHHHH DO I FEEL STUPID. i don't have the galaxy s2 1777. i have the 1727 Skyrocket. -_- sorry man.
peace.
Does anyone have Odin Maker? If so do I need to use a pit file with the tar file it generates when flashing in Odin?
check the kgb repo at github.com
I'm trying to recover my device from a brick state by flashing the original firmware with heimdall, like this guide tells.
Because I want to bring everything back to the original state, I need these following files:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
On another guide in this same forum I found a link to this page, where it's supposed to be downloaded the firmware. However, I cannot get any of those files.
Moreover, I cannot find any place where these files can be downloaded.
Thanks in advance.
EDIT: Please ignore this, it turns out I did not have the correct PIT file. Admin please delete post if necessary.
I have recently moved to EE in the UK and would like to take advantage of the wifi calling.
I've looked up lots of guides but can't seem to get the re-partitioning to work. I have the latest UK EE firmware from sammobile, and the latest (I think) version of ODIN (3.12.7), as well as correct USB drivers.
I had have the correct PIT file for my model with a 100MB hidden partiton.
When I run Odin with the re-partition option, it reports that it is getting the PIT information and proceeds with the flash, but when it gets to hidden.img it fails.
I don't get any error regarding the Pit file itself, tt's like it's either ignoring the PIT file, or reading it but not applying it. I've tried setting the pit file using the Pit tab in Odin, and by adding the Pit file to the firmware tar file, but neither work.
Odin itself states that it will use the Pit information as defined in the CSC file, but the firmware from Sammobile doesn't include a CSC file, just a single tar file that is supposed to be selected in the AP option in Odin.
Does anyone have an up to date guide on how to get the PIT file to work? Or any information at all, I'll be most grateful.
I have same problem with S6 edge plus , it doesn't accept pti file at all . i need help please
professormobile said:
I have same problem with S6 edge plus , it doesn't accept pti file at all . i need help please
Click to expand...
Click to collapse
On EE network?