Error while Flashing Stock ROM - Galaxy S III Q&A, Help & Troubleshooting

I am trying to flash the Stock ROM on my Galaxy S3 i9300. Constantly I am getting this Error.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Note:
1)Device GT-i9300
2)I can ONLY goto the Download Mode.
3)Using Original Data Cable.

---

**this is "a last port to call" this is the last thing you should try**
Try flashing this via recovery: https://drive.google.com/file/d/0B4vTiHTBB629d2syOEV1MkdmTjg/view?usp=drivesdk
Then flash your stock rom via odin.
Beamed in by telepathy.

---

Try different USB cables and USB 2.0 ports.

---

potatoknight8 said:
I am trying to flash the Stock ROM on my Galaxy S3 i9300. Constantly I am getting this Error.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Note:
1)Device GT-i9300
2)I can ONLY goto the Download Mode.
3)Using Original Data Cable.
Click to expand...
Click to collapse
Another EMMC brickbugged i9300. Unless you replace the EMMC chip on the PCB, your phone is kaput. Or get another motherboard. And don't even think about getting your stuff back. They're either done for or locked because what EMMC brick bug, as the name suggests, it's a bug of a specific batch of EMMC chips that after some number of IO operations or some other condition, it just locks, leaving only the first part of the EMMC working, < 1 megabyte in my researches. In reality, your EMMC is not done with, it could be accessed IF you have a device which can reset the EMMC controller or something like that.
Or just flash a .pit file for your device model and capacity, something like i9300 xxg.pit, replacing the xx with the capacity of the EMMC, 16, 32 or 64 gigabytes.
---------- Post added at 20:17 ---------- Previous post was at 20:16 ----------
shivadow said:
**this is "a last port to call" this is the last thing you should try**
Try flashing this via recovery: https://drive.google.com/file/d/0B4vTiHTBB629d2syOEV1MkdmTjg/view?usp=drivesdk
Then flash your stock rom via odin.
Beamed in by telepathy.
Click to expand...
Click to collapse
There is no pit and you suggest flashing a bootloader? Non, non, non, you're wrong. And the man said he can ONLY ACCESS DOWNLOAD MODE. Read before you post.
---------- Post added at 20:19 ---------- Previous post was at 20:17 ----------
audit13 said:
Try different USB cables and USB 2.0 ports.
Click to expand...
Click to collapse
Don't think so.

---

I have been flashing the captivate, s2, s3,s4,s5, note 1, note 2, note 3, note 4, etc. for several years and have often revived the "no pit partition" error when using incompatible it USB cables and ports.
If using the original USB cable doesn't work, try flashing with a pit file.

---

In my experience flashing a pit file will 9 times out of 10 doorstop the device. Flashing that bootloader "might" allow the emmc to reset, or it may doorstop the device. So, the choices are your way (90% chance of killing it) or my way (50% chance of killing it).
So logically thinking me chose not to reveal the ultimate killing method just yet. I also presumed that the ol' cable and port routine was already done seeing as he already has a response from the device.
I also presumed that after doing some research on the matter before I suggested it that, seeing as many other people have reported that it has fixed a no pit condition on "thought to be dead" devices, it would be a better option than attempting the said ultimate device killing option.
I also believe that there is a method for flashing the bootloader via download mode should a minor amount of research be done on Google.
So, it would be better if YOU did the research before commenting instead of coming out with useless, degrading, ignorant, self righteous, arsehole (full of s**t) posts like yours before taking random potshots at people who have actually spent a couple of years with the device in their hand and are still learning new things to this day. Maybe a more constructive comment like "you missed the bit where he can only get to download mode, maybe he could use the .tar version".. But no. Too much..
Beamed in by telepathy.

---

I am getting the exact same error in Odin while Flashing the Stock ROM.

---

西村大一 said:
Another EMMC brickbugged i9300. Unless you replace the EMMC chip on the PCB, your phone is kaput. Or get another motherboard. And don't even think about getting your stuff back. They're either done for or locked because what EMMC brick bug, as the name suggests, it's a bug of a specific batch of EMMC chips that after some number of IO operations or some other condition, it just locks, leaving only the first part of the EMMC working, < 1 megabyte in my researches. In reality, your EMMC is not done with, it could be accessed IF you have a device which can reset the EMMC controller or something like that.
Or just flash a .pit file for your device model and capacity, something like i9300 xxg.pit, replacing the xx with the capacity of the EMMC, 16, 32 or 64 gigabytes.
---------- Post added at 20:17 ---------- Previous post was at 20:16 ----------
There is no pit and you suggest flashing a bootloader? Non, non, non, you're wrong. And the man said he can ONLY ACCESS DOWNLOAD MODE. Read before you post.
---------- Post added at 20:19 ---------- Previous post was at 20:17 ----------
Don't think so.
Click to expand...
Click to collapse
Thanks for an Honest answer and making me lose my **** :laugh:

---

shivadow said:
**this is "a last port to call" this is the last thing you should try**
Try flashing this via recovery
Then flash your stock rom via odin.
Beamed in by telepathy.
Click to expand...
Click to collapse
Well Sir i don't have access to Recovery Mode.I can only goto Dowonload Mode.

---

audit13 said:
Try different USB cables and USB 2.0 ports.
Click to expand...
Click to collapse
Yes sir i have tried Three Samsung Original Data Cables and two different Laptops with Different Operating Systems (Win 10,Win 8.1).
:crying:

---

shivadow said:
In my experience flashing a pit file will 9 times out of 10 doorstop the device. Flashing that bootloader "might" allow the emmc to reset, or it may doorstop the device. So, the choices are your way (90% chance of killing it) or my way (50% chance of killing it).
So logically thinking me chose not to reveal the ultimate killing method just yet. I also presumed that the ol' cable and port routine was already done seeing as he already has a response from the device.
I also presumed that after doing some research on the matter before I suggested it that, seeing as many other people have reported that it has fixed a no pit condition on "thought to be dead" devices, it would be a better option than attempting the said ultimate device killing option.
I also believe that there is a method for flashing the bootloader via download mode should a minor amount of research be done on Google.
So, it would be better if YOU did the research before commenting instead of coming out with useless, degrading, ignorant, self righteous, arsehole (full of s**t) posts like yours before taking random potshots at people who have actually spent a couple of years with the device in their hand and are still learning new things to this day. Maybe a more constructive comment like "you missed the bit where he can only get to download mode, maybe he could use the .tar version".. But no. Too much..
Beamed in by telepathy.
Click to expand...
Click to collapse
Edit: you're suggesting flashing a bootloader and then a stock ROM, and then vo on to say that MY advice with flashing a .pit, which by the way, IS MISSING, can killi it? And where did you get those numbers? 50 per cent, 90 per cent? Don't mess with me, KILLING OPTION? Go tell that to the Samsung Service Centre in Tokyo, they will laugh at you. Spare me of this please, and don't bother to quote this post, i will not provide further assistance, happy bricking devices, no, "fixing" devices. Oh, and I solved an efs problem some time ago on my i9305, everything was ok, serial no, imei, but no network. Found a backup, extracted it and flashed it dirrctly through ADB with the dd command. Working like new since then.
I guess you have YEARS of experience in flashing devices. Ok. But i might want to get gour attention to remove the last paragraph and show what part of my post was "useless", "degrading" or "self righteous" before starting to throw accusations around. I try to help here, so please, I have had Android devices in my hand, rooted, flashed stock and custom ROMs since the days of the Galaxy Mini. I have even revived many low end Mediatek devices with "irrecoverable" errors, and have a part time job at a GSM service here. Why didn't YOU tell him what to do if you are so HIGH and MIGHTY that you can't take another opinion but your own. And every time someone came into the GSM store i worked with a Samsung device with those symptoms, it was an eMMC brickbugged device which could not be recovered. I have tried bootloaders, pit files, cables, ports, machines, laptops, you name it. None worked. I even desoldered the eMMC and tried to access it via some instructions i found online. Nada. Nothing. So please stop talking like you know everything. I don't and have never said I know anything. FIN

---

Guys lets not let this turn into a flame war please, ALL OPINIONS are welcome and we also welcome debate but keep it polite please. Just because someone has a different opinion to you doesn't give you the excuse to be rude.
I'm surprised no one has suggested trying kies/smartswitch emergency firmware recovery btw, If i only had download mode that would be my first port of call
Regards
Sawdoctor

---

sawdoctor said:
Guys lets not let this turn into a flame war please, ALL OPINIONS are welcome and we also welcome debate but keep it polite please. Just because someone has a different opinion to you doesn't give you the excuse to be rude.
I'm surprised no one has suggested trying kies/smartswitch emergency firmware recovery btw, If i only had download mode that would be my first port of call
Regards
Sawdoctor
Click to expand...
Click to collapse
Hello there Sir could you be more specific about kies/smartswitch emergency firmware recovery.
Sorry I'm a noob.
:|

---

Some older phones are not supported by Smartswitch so you would need to use Kies.
http://www.samsung.com/us/smart-switch/
Download and install Kies first. Once installed, there is an upgrade/recovery under the options.
If your phone is not supported by Kies, try SmartSwitch.
Good luck.
Remember, we were all newbies at one point.

---

西村大一 said:
Edit: you're suggesting flashing a bootloader and then a stock ROM, and then vo on to say that MY advice with flashing a .pit, which by the way, IS MISSING, can killi it? And where did you get those numbers? 50 per cent, 90 per cent? Don't mess with me, KILLING OPTION? Go tell that to the Samsung Service Centre in Tokyo, they will laugh at you. Spare me of this please, and don't bother to quote this post, i will not provide further assistance, happy bricking devices, no, "fixing" devices. Oh, and I solved an efs problem some time ago on my i9305, everything was ok, serial no, imei, but no network. Found a backup, extracted it and flashed it dirrctly through ADB with the dd command. Working like new since then.
I guess you have YEARS of experience in flashing devices. Ok. But i might want to get gour attention to remove the last paragraph and show what part of my post was "useless", "degrading" or "self righteous" before starting to throw accusations around. I try to help here, so please, I have had Android devices in my hand, rooted, flashed stock and custom ROMs since the days of the Galaxy Mini. I have even revived many low end Mediatek devices with "irrecoverable" errors, and have a part time job at a GSM service here. Why didn't YOU tell him what to do if you are so HIGH and MIGHTY that you can't take another opinion but your own. And every time someone came into the GSM store i worked with a Samsung device with those symptoms, it was an eMMC brickbugged device which could not be recovered. I have tried bootloaders, pit files, cables, ports, machines, laptops, you name it. None worked. I even desoldered the eMMC and tried to access it via some instructions i found online. Nada. Nothing. So please stop talking like you know everything. I don't and have never said I know anything. FIN
Click to expand...
Click to collapse
You missed the bit where I "didn't say" you were wrong about the brickbug but if you've tried everything why suggest a known defunct method aka pit file knowing that it won't work.
If you came here for an argument you need to give your head a wobble, you won't get one. I couldn't care less who you've worked for or been with, you know jack about my background which "could" be more than yours.
So "Mr HIGH and MIGHTY", I say that because the bully always projects their insecurities on others as you have, no one said who was better than anyone so I suggest you climb down out of that Ivory tower before someone knocks it down around you. "no more fixing bricks" blah blah.. That is a PERFECT example of how much of a whiny little tart you are. Grow up and grow a pair of balls. "High and mighty".. D**khead comment that m8. Your true colours are showing.
Your personal interaction skills leave "A LOT" to be desired.
** waits for the post that says "tried flashing a pit file and now the device is dead"**.
Beamed in by telepathy.

---

@shivadow @西村大一 @audit13

---

Use Z3x flasher, forget Odin!.It happened to me,exactly we had the same situation..Finally I just flashed stock firmware and recovered.

---

Is Z3x flasher free?

---

Thread cleaned up.
Please don't talk about cracked versions here on XDA. It is considered as Warez.
The XDA Rulesforum.xda-developers.com/announcement.php?a=81 #6 clearly states
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
Now let's get the thread back on topic.
Regards
Vatsal,
Forum Moderator.

---

potatoknight8 said:
Well Sir i don't have access to Recovery Mode.I can only goto Dowonload Mode.
Click to expand...
Click to collapse
same with me sir, when powered on normally it goes to a white screen. sometimes with multicolored dots. I also tried flashing with pit files only and pit files with the roms but no luck.
Is there any other way to revive this phone? Kies tries to connect but never completes connection, suggesting to reboot the device then all the same thing happens. It would really be a big help and I know that many will benefit if and when someone will have a clear solution. Cheers to the XDA community!!!