Database Info

GT-P5100 Firmware upgrade encountered an issue

Hi everybody, I tried to upgrade my GT-P5100 to 4.2.2 but something went wrong and now I have a black screen with this message:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably I have selected Re-Partition but I didn't have a PIT file
The tablet had the stock rom and was not rooted.
I have Odin 3.07 and this PDA file but the procedure fails:
P5100XXDMJ2_P5100VFGDMJ2_P5100XXDMG1_HOME.tar.md5
Code:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMJ2_P5100VFGDMJ2_P5100XXDMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can't start Recovery or Download mode.
Can you help me?
Please if I need some more files write me all the links to download them, because many of them were hosted by hotfile and are no more downloadable...

"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
That´s the Black-Screen of Death! Downloadmode is on in this window Connect to your PC, Odin will get your device
There should be no Problem with the file itself "<OSM> Checking MD5 finished Sucessfully.." - bad download will give another output because the MD5 is not valid if it´s broken.
Make sure you uninstall KIES before using Odin and run Odin as Administrator !!!

Kies in installed and Odin is executed as administrator
So what should I do?

GT-P5100 restore stock rom firmware odin
SOLVED using this guide and this file

dylan6662 said:
SOLVED using this guide and this file
Click to expand...
Click to collapse
Hello, i have the same your prblem with my galaxy tab 2 10.1 !!!...
do you remember how you managed to solve?
Do you remember what was the file of "this link" (http://www.bergfiles.com/i/bf5bdebbf2hci0) that is no longer active?...
I have absoluty need !!
THANKS !!!

Still on trouble
I still can find the right link to download the necessary file to flash on my gt-p5100 like this case , my screen just still say "Firmware upgrade encountered......"
cant log into download mode
but still detect on odin
please help me.

Hi all. I have the same problem. A message "Firmware .... an issue" Tried different Odin versions. With 3.07 and 3.10 versions looks like flashing is ok, Odin shows no errors. But nothing on the tablet, there's not status bar. And when flashing finished, Odin shows no errors. But tablet really not flashed. What the problem can be? Who can help?

HELP HELP

andrezerotwo said:
HELP HELP
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...opment/odin-gt-p5100-4-2-2-stock-rom-t3022183
try this link, it is stock firmware.
further if it can't solve by just flashing firmware, you can try pit file. but be careful before flashing this with odin, be sure of what it will do, there are guides to explain the proper process.
http://forum.xda-developers.com/showthread.php?t=2552155

I have the exact same problem, tried different odin versions, flashed the stock firmware, also tried different pc's, but no solution.
this is the error I keep getting on odin, Tried Kies it says P3100 does not support initializing. A friend says maybe its a motherboard issue, is that possible or just a firmware problem? What should I do next?
This is the error I get in ODIN.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100DDCNA3_P3100ODDCNB1_P3100DDCLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

v1v14n said:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi! With my tablet the same. I understand that eMMC has died, need a replacement and reflashing of the programmer.

GT-P5100 Firmware upgrade encountered an issu
Hi All,
I have the exact same problem with GT P5100, I cannot update my 5100,Itried different odin (1.85,307,309,1,7) versions, flashed different firmwares, but no solution.
this is the error I keep getting on odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMD1_P5100DBTDMD1_P5100XXDLL2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> modem.bin
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
Many thanks in advance,

[Q] Win7 GT-P5110 Kies drivers & Odin - try to recovery stock image

I got a Samsung Galaxy Tab (GT-P5110) of which the tablet did not startup anymore, and know nothing about the prehistory.
I downloaded stock firmware from samsung site: http://samsung-updates.com/device/?id=GT-P5110
and downloaded the latest EUR version named : P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5
With Odin 3.07 I installed that image in download mode with default options left on. After that I got the following screen message on the tablet:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably something went wrong. Then I downloaded Kies from samsung site, installed it with all extra drivers and I got the problem that Kies never recognized the tablet. Reinstalled many times, tried different options, but the problem persisted (took me 8 hours totally). Battery of the tablet was fully loaded and before this problem I saw that it was loading correctly.
Then I read this excellent document : http://forum.xda-developers.com/showthread.php?t=1652398
Tried again with Odin 3.07 and 1.85 and could install the image with only the reboot option on in Odin, flashed successfully the image, but still the problem:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I do not have much options left to look for. I was thinking about:
- driver issue
- wrong image
- wrong method
Can somebody help me to have this problem fixed ? I am willing to reinstall Windows 7 on this laptop.

Really nobody knows ?

never had problems here on Windows 8.
Maybe try flashing using Heimdall

But will I need a Heimdall image for that, because it does not accept the samsung image.

proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
Click to expand...
Click to collapse
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?

proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
Click to expand...
Click to collapse
I am located in The Netherlands, and downloaded the specific image for the Netherlands, region PHN, used Odin 3.07 to install it, but still the same problem.
What can I do, wait for somebody who can give me a hint ? This is the first time I do a recovery of a Samsung tablet, and don't know how to continue with it.
Your help will be very much appreciated.

Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery

Joery360 said:
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Click to expand...
Click to collapse
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.tar.md5 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> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.

proconsoles said:
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.tar.md5 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> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Do you think that this problem is hardware related ??

Nobody knows ?

Same for me
I'm dealing with almost the same issue, except for my ODIN flashes it doesn't even succeed. I know this happened to it after I tried to use heimdall to update my CWM, but I have had no success getting anything to work. I've been without a tablet for like a week now, doing everything I can think of or find a walk through for. I mean for me, I wouldn't mind going back to stock as long as it works again. Here's what my ODIN is doing:
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm about to try the TWRP someone recommended above, I'll let you know how it goes
---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------
I tried flashing a different version of TWRP and it looked like it was going to do something, but it isn't going. Here's what it did this time:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_TWRP_2.7.0.1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Forgot to mention that I'm using Odin 3.09 on a p5113. Not that it makes huge difference.

Two things to try:
If you can boot into recovery, try the factory reset.
If not, have you tried Kies recovery mode?

The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.

Maybe because Samsung / KIES Process running in background on your PC?

A Case of bad partitions
Deucethehero said:
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Click to expand...
Click to collapse
Try flashing with .pit file, partitioning set to on. Should correct partition problems. Somebody might have installed a non-android OS that botched. Look for a .pit file around the forum, you should find one. Good luck.

Thank you
Thanks for the tip, I'll give it a shot and post back with results!

Sorry for the late reply
Hey guys, I could have sworn that I posted back on Friday, but it's not here. Anyway, it's been a crazy few days for me traveling and school starting and all that.
About the tablet, I downloaded a pit file and it looked like it was going to work, but unfortunately it did not. I'm working on getting the tablet charged and set up to try again because I got a zip that had 2 pit files, so I'll try the other one soon. I'll post the results when I get them, thanks again for all the help!

Still not working, but I think some progress
Sorry to take so long responding, it's been a busy week.
So I just attempted to flash the .pit again, and it failed. Here's what Odin gave:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
It says, "There is no PIT," but that's what I'm trying to flash, right? I'm a little confused, but I hope someone knows what that means.
Thanks for all the help guys!

New info!
So today I was messing around with the .pit file that I had, and I used an editor to make it exactly the same as one I found in another forum. After Odin told me that it failed, I went to reset the tablet, and it showed me the Galaxy Tab 2 screen, which it has not done for a few weeks now. Then I plugged it in and it shows the battery charging symbol. Currently it is a 18%, so I'm going to let it charge and then try booting it up again and see what I get. Hopefully all is well now, but we shall see here in a few hours.
I also was not aware that I needed to flash the system along with the pit, and once I had that going it made a little more sense to me.
I'm going to try to post that pit here if anyone wants it. Hopefully it will help someone else in the future.

Odin Flashed, but failed
So I got into normal old download mode on the device using that .pit file. Yay! However upon attempting to flash the stock os back on Odin gave me this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UEBLH3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm going to look into other avenues, but this did set me back to the "Firmware upgrade encountered an issue... blah blah"

Can not flash official firmware

Hello,
I want to flash to G920FXXU1AOD4 from G920FXXU1AOE3.
I tried to use Odin 1.85 and 3.04.
This is the error that I'm getting in Odin 1.85:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOD4_G920FOJK1AOD4_G920FXXU1AOCZ_HOME.tar.md5 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> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Why can't I flash to this firmware?
Help...

r'n'b said:
Hello,
I want to flash to G920FXXU1AOD4 from G920FXXU1AOE3.
I tried to use Odin 1.85 and 3.04.
This is the error that I'm getting in Odin 1.85:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOD4_G920FOJK1AOD4_G920FXXU1AOCZ_HOME.tar.md5 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> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Why can't I flash to this firmware?
Help...
Click to expand...
Click to collapse
Did you turn on USB DEBUGGING?

Hello again
I had the same problem with flashing rom with odin... I found a solution and explained it how to fix mine...
I hope it be helpful
http://forum.xda-developers.com/galaxy-s6/help/help-odin-stuck-start-write-nand-t3127992

k2evil said:
Hello again
I had the same problem with flashing rom with odin... I found a solution and explained it how to fix mine...
I hope it be helpful
http://forum.xda-developers.com/galaxy-s6/help/help-odin-stuck-start-write-nand-t3127992
Click to expand...
Click to collapse
Ok... I Solved my problem finally... I spent almost 3 days in forums to find a solution... So i give you guys a summary what I do:
1) Find my phone's pit file according to model and storage capacity (Mine is G920F 32GB)
2)Then the trick is use ODIN V3.10.6 insist of V3.09... http://forum.xda-developers.com/showthread.php?t=2711451
3)If you face with hidden.img problem, extract the rom's file and rename the file hidden.img to hidden.img.tar and flash it by ODIN (Put this file on AP)...
Wait for some minutes and there is where magic happens
Click to expand...
Click to collapse
I don't understand your solution.
What do I need to do with the pit file?
My device is also G920F 32GB.
The USB DEBUGGING is on.

r'n'b said:
I don't understand your solution.
What do I need to do with the pit file?
My device is also G920F 32GB.
The USB DEBUGGING is on.
Click to expand...
Click to collapse
I heard from someone that Stucking in Start Write NAND is because of pit file...
but forget about it.. try without pit file. download the lastest odin v 3.10
usually process fails when it try to flash hidden.img... if it happen for you, do the 3th step

k2evil said:
I heard from someone that Stucking in Start Write NAND is because of pit file...
but forget about it.. try without pit file. download the lastest odin v 3.10
usually process fails when it try to flash hidden.img... if it happen for you, do the 3th step
Click to expand...
Click to collapse
Finally I managed to flush the ROM
Odin3_v3.10.6 did the job.
Thanks!

Your welcome buddy... just don't forget to hit the thank button

Rooting attempt on S6 G920F running on 5.0.2

So I was following this guide :
http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
And I think I flashed CF-Root correctly. Tried to boot, Recovery is not seandroid enforcing. I then flashed TWRP 2.8.7.1 (the .img one) and now it proceeds to recovery after boot screen.
I tried restarting to system with TWRP and it went into a bootloop.
Am I on the right track? I mean is it supposed to be like that until I do a factory reset? I'm scared cause the ROM is still downloading lol how do I put it in the device's internal memory? Will I be able to in Download Mode?
On a PC running Windows XP right now, Samsung's USB Drivers don't seem to work whatsoever. I'll try it on my laptop and we'll see.
(p.s. should I have opted for the one-click rooting and stuff? Idk the guide tells me to do it via Odin so yea lol)

Since you were on 5.0.2 you could've used the PingPongRoot to easily root your phone. I did that but then after a while I thought I want a custom ROM so I updated to 5.1.1 and tried to use odin to root my phone but got the same issue as you.
After a few hours of struggeling I got out of the bootloop by doing an emergency software recovery from Smart Switch. However I'm not sure if it will recover to 5.0.2 or download the latest 5.1.1 in your case.
Nonetheless when I got my phone to work again I just flashed UniKernel with TWRP and then I was rooted.
I wont touch odin ever again I'm too nooby for that and it caused me to panic so hard with that goddamn bootloop.
I hope you get it solved!

[Completed] Odin fails to flash stock rom onto S3

I'm having trouble with flashing the stock rom for the Samsung Galaxy S3 on Odin, as I get a fail everytime I try to flash the rom onto my device.
This comes up everytime I try to flash:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOK1_I9300NZCGOK1_I9300XXUGOK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The model number is a GT-i9300, and no stock roms so far have succeeded.
I have used Odin 3.07 and Odin 3.09, my samsung drivers are up to date and Odin still fails to flash the rom.
On the S3 it's currently running TWRP version 3.0.2-1, it also asks me whether or not I keep it "System Read only" whenever I go in recovery mode. And each time I always choose the option of keeping it read only. I don't know if these has anything to do with Odin failing to flash the rom but might as well mention it. I was also running CyanogenMod13 for roughly a month before the brick happened.
Any help would be appreciated !

Hello
Thank you for using XDA Assist.
Please use the below link to register a XDA Account first, prior to start posting and replying onto our forums.
Join the Experts
When you complete your registration, I invite you to post over your request in the below forum as our team of experts there should be able to help you:
Galaxy S III Q&A, Help & Troubleshooting
Best regards and good luck.
.
XDA Visitor said:
I'm having trouble with flashing the stock rom for the Samsung Galaxy S3 on Odin, as I get a fail everytime I try to flash the rom onto my device.
This comes up everytime I try to flash:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOK1_I9300NZCGOK1_I9300XXUGOK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The model number is a GT-i9300, and no stock roms so far have succeeded.
I have used Odin 3.07 and Odin 3.09, my samsung drivers are up to date and Odin still fails to flash the rom.
On the S3 it's currently running TWRP version 3.0.2-1, it also asks me whether or not I keep it "System Read only" whenever I go in recovery mode. And each time I always choose the option of keeping it read only. I don't know if these has anything to do with Odin failing to flash the rom but might as well mention it. I was also running CyanogenMod13 for roughly a month before the brick happened.
Any help would be appreciated !
Click to expand...
Click to collapse