Related
Hey all,
I am in the US I bought this I9300 that won't boot thinking I could simply reflash it and use it/resell it.
It won't boot into custom recovery or the OS. Last night it was stuck on the Samsung screen but I did some reading and found this guide: widefide (dot) com/mobile/galaxy-s3-boot-problem-solution (spam filter)
I was able to use Odin to reflash the PIT that was linked there so now the phone gets to the Firmware/Kies screen.
I have tried flashing any stock ROM (I'm not even sure which 1 I should be flashing) and/or installing CMW and Odin either gets stuck on SetupConnection.. or <ID:0/003> NAND Write Start!!
Is there anything I can do to recover this phone? I'm pretty savvy so as long as the tools exist I anticipate that I can fix this.
Can you please post in the correct sections?.
Thread closed.
Hello everyone,
I have a few questions about the repartition and the pit file.
1. Is Kies software does repartition with pit file while flashing?
2. When to use pit file?
3. Where can I download the pit file?
4. How can I know what pit file to use and is there a difference?
Thank you.
Do not flash pit do not tick repartition.
Stay well away from pit files or you will brick your phone .
Suggest you read the faqs and guides and learn the very basics first .
jje
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.
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
honzicek69 said:
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
Click to expand...
Click to collapse
If I'm not mistaken boot.img is the bootloader, not the recovery. Are you sure you can't get into recovery using the 3-button-combo? If not I would try flashing this recovery via ODIN. And then try to reboot into it using the combo. Then flash CM zip from there again.
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
honzicek69 said:
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
Click to expand...
Click to collapse
Ah, I'm sorry I misunderstood. I thought that was just a snippet of the log... Try flashing the recovery I provided and see if it flashes. If not, maybe you can flash stock firmware with pit file (new partition table). If nothing flashes, I have no further ideas.
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
rp158 said:
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
Click to expand...
Click to collapse
I could be mistaken but I believe the 3-part-roms (csc / pda / phone) is the "old style" how roms where put out by sammy. You would have to search but I would think you can also use the version you get from sammobile nowadays (one zip) and additionally just use the gt-i9300 pit file found somewhere here in the forums.
@Hawaiihemd: be shure, you're wrong.
honzicek69 said:
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
Click to expand...
Click to collapse
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
rp158 said:
@Hawaiihemd: be shure, you're wrong.
Click to expand...
Click to collapse
@rp158 Well, I think I only made a small error in my assumption.
Here are the details on the sammobile download. It seems to hold everything a "3-part-version" holds. I downloaded the file and a look at the .tar file inside the single .zip seems to confirm that.
This post suggests that flashing the .tar with the pit file should work.
I don't know because I haven't tried myself, maybe you have. Or I'm missing a piece of the puzzle. If so, maybe you could point me to it!?
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
rp158 said:
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
Click to expand...
Click to collapse
You didn't, don't worry. I was a little stumped maybe, but only because your answer was so terminal. Actually I only wanted to start a discussion about this, because you seemed to know more about said process than me and I always try to gain knowledge here to better help solving problems. I haven't been in this forum for long or into android for that matter...
That said, I have done the "3-files" version of this process with a .pit file thrice already on different gt-i9000s. Always worked flawlessly.
Looking at the ones in the post @tallman43 suggested, I found the contents of those 3 .tar.md5 files in summary(!) similar to the ones in the 1 .zip from sammobile. That's why I thought it could work in the first place.
One thing I'm sure of is that in both cases the repartition info is in the .pit file. If you choose none, the MMC should not be repartioned. If partitions are reformatted... that's another deal.
Concerning the efs partition, to/from where that info is stored/restored during repartitioning of the MMC... that's a very interesting question!
tallman43 said:
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
Click to expand...
Click to collapse
Thank you very much for this hint. It worked well. I used the all files from KOR zip and 1.85 ODIN. Now i have the Korean version but at least i have something to start with and phone which works now.
I don't have high hopes that this is fixable, but my Verizon Galaxy S4 phone was bricked after taking the OC1 update.
Long story short, I flashed the stock Lollipop OC1 firmware to my phone via Odin3 (v3.10) instead of the neutered one with the NK4 bootloader, by accident... I stupidly didn't read the full file name in a hurry. So, now I have an unrooted stock OC1 lollipop firmware on my machine.
Not doing all my research and thus not knowing that the OC1 bootloader is locked, I tried to use Odin to re-flash an NC5 boot.img (the old NG6 to NC5 downgrade method). This actually flashed just fine. But, it put me in a bootloop.
So, I tried to re-flash the full stock OC1 firmware. This failed as per the Odin output below:
File analysis...
SetupConnection...
Initialization...
Get PIT for mapping...
Firmware update start...
SingleDownload.
boot.img
NAND write start!!
recovery.img
system.img.ext4
__XmitData_Write
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I get similar failing results whenever I try to flash any firmware via Odin.
So I can only access download mode. My recovery won't boot, and when I just try to boot it up normally it gave a screen saying:
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
So I download Kies, it recognizes there is a device there, but doesn't recognize it as a compatible device.
I use the Kies option under tools "Emergency firmware recovery," but the device doesn't pop up as one in need of recovery.
So I use the "Firmware Upgrade and Initialization" tool. I type in Galaxy S4, it downloads the firmware, starts updating... and has an unexpected error. It says to run recovery. But I already tried that, and the device isn't recognized.
However, now on boot there is a slightly newer screen, saying:
Software Update Failed
Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update.
(sorry I don't have a picture)
Now, I can't install the Verizon Software Upgrade/Repair Assistant because apparently you can't download it from their site, since it is supposed to install automatically when you plug your phone into your computer via USB. That obviously isn't happening with my phone in the state it's in.
On XDA here, I found someone posting this software Repair Assistant as "SUA_ar" tool. It installed on my computer, but the software doesn't even recognize my device when it is plugged in, so it won't even try to recover.
By the way, both in download mode and when I try to boot up, the top left of the screen says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
At this point, I don't care about root, tripping KNOX, or anything. I just want to know if there is a way I can get it working as a phone again.
I definitely deserve mockery for my stupidity, but if you can help, too, that would be great.
@KaosMaster (I think)has a special little ZIP that may work. It is the full wipe, but it also contains files for re partition and whatnot. That MIGHT work.
You must use the following files:
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
If you want to revert to NK1 please use this image!
https://docs.google.com/file/d/0B4RU_ZH5QUAST1M5WkRNcy1Xek0/edit?usp=docslist_api
This is to repair to OC1:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
In the ODIN you just downloaded, select the CSC button, and select the extracted ALl_VZW_I545****.tar.md5
Then select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS Clear
Hit START
Wow, thanks for the quick responses!
Unfortunately, the phone doesn't seem to want to let it do the NAND erase all for some reason! Or at least that's what I gather from this output:
Odin v.3 engine (ID:5)
File analysis...
SetupConnection...
Initialization...
Erase...
Complete(Write)operation failed.
All threads completed. (succeed 0 / failed 1).
This happened with both the NK1 and the OC1. Strange, I don't know what is limiting that Erase procedure...
In the top left corner of the phone, under all the ODIN MODE data, now it says:
START[224,1440]
ERASING USERDATA PARTITION...
And there is just a tiny bit of progress bar under the android logo.
If that matters.
Just uncheck the erase all for now, but I would try one more time with that setup...
It should just work
---------- Post added at 05:56 AM ---------- Previous post was at 05:55 AM ----------
And you didn't select re partition...
That is important
I did select re-partition, sorry I forgot to include that part in the output.
I unchecked "NAND erase all" and it had this failure after Initialization...
Set PIT file...
DO NOT TURN OFF TARGET!!
Get PIT for mapping...
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
You have to use the OC1 lollipop file then
Pull battery, re insert, then ODIN mode on power
Yes, this is actually with the OC1 file you provided, in the CSC slot. Should I try it in the AP slot with same options (except NAND erase)?
Oh...you can try that!! But I am worried about your hardware NOW.
If you just let it start, it gets to the emergency screen?? If yes, ODIN flash with that screen on the device.
Also they battery must be above 80% or it might not flash.
Oh, you mean do not flash it in Download mode? I should flash it in the screen where it says "Software Update Failed" ?
Yes try that
Also..I am working on a set of repair files
It made it farther!
I haven't tried AP slot yet. This is with OC1 file, in CSC slot, selecting NAND Erase All (and the other ones you said too)
Initialization..
Erase..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
sbl2.mbn
sbl3.mbn
rpm.mbn
Complete(Write) operation failed.
etc...
Pull battery...go into ODIN...repeat
Ughh. Now Odin isn't even recognizing my phone in the emergency screen. It still recognizes it in download mode, though.
It was seeing it before in the emergency screen, obviously. Restarted Odin, restarted my phone a couple times, still nothing. Trying a couple more times.
Go to where you hold the buttons to download...This is ODIN. Will have the boot to flash in 5 mins
Good things happening! I just took it out and inserted it a couple more times after restarting Odin.
It's now flashing system.img.ext4 and hasn't failed yet. Fingers crossed...
Awesome!! All the checkboxes marked also??
Yes, even NAND Erase All.
That's how we ROLL!! Enjoy! Your device is like brand new!
You are very much the man, Kaos! It's back up!
I've been addicted to root for the past 4 years with various devices, but I think I'll chill out with that after this craziness. ... for now.