Database Info

Droid Charge unroot ODIN

I recently rooted the Droid Charge using ODIN, no issues. I have a custom kernel and I decided to try a rom and it was awful. Anyways went back to my Backup through CWM, no issues. My phone is now lagging beyond belief. I can't do anything at all. I really want to unroot. I know how to use ODIN and have experience with it. All i need is the .tar file for the factory restore. If anyone has a download link or a place that has one that would be greatly appreciated.
Thanks in advance

Have you checked the development section? They have every file you could need with instructions.

Yea i have found one for the samsung pst but i need one for odin samsung pst wont work on my crappy computer.
Sent from my SCH-I510 using XDA App

I have complete step-by-step instructions on how to load stock EP4D back onto the phone complete with links to all of the files you need to do it.
http://www.toms-world.org/android/page/flashstockep4d.html

Thanks so far so good thanks again for the help u guys. i wont be messing with rooting again.
Sent from my DROID CHARGE using XDA App

i tried the odin restore and got this error
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.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> boot.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1
----now my phone is blank except a little cell phone with what looks like a teather to a computer.
what should i do?
thanks.
john

johnott said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.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> boot.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1
----now my phone is blank except a little cell phone with what looks like a teather to a computer.
what should i do?
thanks.
john
Click to expand...
Click to collapse
There are other threads on this issue, and it pretty much means that your internal memory is somehow corrupted.

John, not sure of your experience level or what you are trying to accomplish with that particular flash but make sure you have the basics covered. Correct and uncorrupt files. Phone in download and put battery back in and use of PDA in Odin.
Sent from my SCH-I510 using xda premium

@bwheelies
my experience is very little. i attempted to follow the post that gave step by step instructions on how to get a device back to stock. i thought i followed it perfectly. guess not... i purchased this device already rooted, and it wasn't working properly which was my reason for wanting to get it back...

johnott said:
my experience is very little. i attempted to follow the post that gave step by step instructions on how to get a device back to stock. i thought i followed it perfectly. guess not... i purchased this device already rooted, and it wasn't working properly which was my reason for wanting to get it back...
Click to expand...
Click to collapse
I have read a few people were able to fix this by running Odin with pit file over and over till it worked also you could have used the cwm install zips to get back to stock those seem to have less issues
Sent from my XT875 using xda premium

[Resolved] [Q] Note 3 Sm-n900 root error odin FAIL! HELP!

I tried to root my sm-n900 note 3 and followed all the instructions to the letter on the forum and when I tried to root through odin, it says writing cache.img and I wait for a few minutes then it says FAIL, I unplugged then restarted my phone and it says "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE, PLEASE SELECT RECOVERY MODE IN KIES AND TRY AGAIN" and now kies doesnt recognize my device anymore, So what can I do now? I really want to root but damn samsung wont let me!
I see this in odin btw
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-ha3g-ha3gxx-smn900.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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE!
I tried using odin 1.85 to root, and now its stuck at cache.img it hasnt changed for maybe an hour now what?
UPDATE2
phew unticked autoreboot in odin and manually rebooted and everythings good

Sorry I could not tag your question due to failure with the mobile app. For starters I did not worry about using the auto-root option since I am not worried about tripping Knox counter. I prefer to flash twrp or cwm via Odin and then flash the current version of supersu from the recovery or if you are looking to install a custom Rom you can just flash it instead. Nothing against CF auto-root but this has always worked for me.
sm-900t: Powered by X-Note V13

FFTony said:
Sorry I could not tag your question due to failure with the mobile app. For starters I did not worry about using the auto-root option since I am not worried about tripping Knox counter. I prefer to flash twrp or cwm via Odin and then flash the current version of supersu from the recovery or if you are looking to install a custom Rom you can just flash it instead. Nothing against CF auto-root but this has always worked for me.
sm-900t: Powered by X-Note V13
Click to expand...
Click to collapse
Could you please explain that in noob terms?

firmware upgrade encountered an issue. please select recovery mode in kies and try ag
hi
i have same problem.
pls help me..
willzhang0 said:
I tried to root my sm-n900 note 3 and followed all the instructions to the letter on the forum and when I tried to root through odin, it says writing cache.img and I wait for a few minutes then it says FAIL, I unplugged then restarted my phone and it says "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE, PLEASE SELECT RECOVERY MODE IN KIES AND TRY AGAIN" and now kies doesnt recognize my device anymore, So what can I do now? I really want to root but damn samsung wont let me!
I see this in odin btw
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-ha3g-ha3gxx-smn900.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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE!
I tried using odin 1.85 to root, and now its stuck at cache.img it hasnt changed for maybe an hour now what?
UPDATE2
phew unticked autoreboot in odin and manually rebooted and everythings good
Click to expand...
Click to collapse

Awesome... Your technique worked for me.
You just have to uncheck the auto reboot option. Its so simple.
Thanks a lot man!

i have this same problem..pls help me..even i unticked reboot option but its not working...stuck in da middle while rooting..pls help me..

need some help. Soft bricked i925 verizon note 10.1

So i recently rooted my i925 with this universal method...
http://forum.xda-developers.com/showthread.php?t=2403230
https://www.youtube.com/watch?v=QCBLOhWavT0
Then I decided to try and run the casuall "Jailbreak" software to get a custom recovery and unlocked bootloader and i just checked "I did it" during the root portion since I already was... and now I'm soft bricked. I can only get into the download mode and tried flashing with odin but no luck might be doing something wrong... Also tried following the cyanogen instructions which involve flashing a cwm recovery in download mode but still no luck. Any help would be greatly appreciated!!! If I hold power the screen will just flash the download mode screen on and off. I pulled the back off and pulled power. No difference.

Any ideas guys? This is the first time I've bricked anything since I've been here and it's got me pretty worried...

Still stuck is anyone has any ideas.

2rz_taco_sr5 said:
Still stuck is anyone has any ideas.
Click to expand...
Click to collapse
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.

tselling said:
I would retry ODIN with the original VRAMK1 firmware available from sammobile.com. If that doesn't work tell us what error you are getting.
Click to expand...
Click to collapse
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.

2rz_taco_sr5 said:
this is what i get in the message box.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if it helps im using odin3 v1.85 and then Kies v2.6.3.14074_11 to install the driver. also im running windows 8.1 if that matters.
Click to expand...
Click to collapse
Maybe try Heimdall commandline. You can flash individual pieces.

tselling said:
Maybe try Heimdall commandline. You can flash individual pieces.
Click to expand...
Click to collapse
I'm just going to warranty it out with verizon. Ive warrantied phones before with no issue. usually for amoled screens that get shadows before the year warranty is up. Hoping all goes well.

im having this same issue, device keeps starting and then fails out, is there a solution to this?

[Q&A] [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included

Q&A for [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Attempted to follow the guide here on my old Infuse to breathe some life back into it, but I can't get it to work. Installed the drivers through Kies, Odin detects my phone in yellow. I follow the guide to the letter, but after flashing 'reset' in blue and getting the green 'pass' my phone simply doesn't reboot, nor can I boot it manually. I've removed the battery a few times and it doesn't change the situation. I can still boot into download mode with no issue and have tried flashing a few times, but I'm having no success booting the phone after Odin is done, nor can I get into recovery mode.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> modem.bin
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Any ideas?

SG2Tiger said:
Attempted to follow the guide here on my old Infuse to breathe some life back into it, but I can't get it to work. Installed the drivers through Kies, Odin detects my phone in yellow. I follow the guide to the letter, but after flashing 'reset' in blue and getting the green 'pass' my phone simply doesn't reboot, nor can I boot it manually. I've removed the battery a few times and it doesn't change the situation. I can still boot into download mode with no issue and have tried flashing a few times, but I'm having no success booting the phone after Odin is done, nor can I get into recovery mode.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> modem.bin
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Any ideas?
Click to expand...
Click to collapse
I never tried this flash before, but I do have a couple questions before proceeding...
Is your phone AT&T or Rogers?
Are you able to get back into download mode (that is, by method of device fully turned off, holding down both Volume Buttons and inserting the USB cable)?

joel.maxuel said:
I never tried this flash before, but I do have a couple questions before proceeding...
Is your phone AT&T or Rogers?
Are you able to get back into download mode (that is, by method of device fully turned off, holding down both Volume Buttons and inserting the USB cable)?
Click to expand...
Click to collapse
AT&T, the model is I997. I can still get into download mode, but I can't boot normally, nor into recovery mode (by holding volume up + volume down + power button; Samsung logo never appears). I used the included version of Odin with both the UCLB3_Unbrick_1.1.zip and UCLB3_Unbrick_root_1.1.zip files on the linked thread (I tried both).

SG2Tiger said:
AT&T, the model is I997. I can still get into download mode, but I can't boot normally, nor into recovery mode (by holding volume up + volume down + power button; Samsung logo never appears). I used the included version of Odin with both the UCLB3_Unbrick_1.1.zip and UCLB3_Unbrick_root_1.1.zip files on the linked thread (I tried both).
Click to expand...
Click to collapse
I always recommend this one for AT&T (could never try it myself, as I was a Rogers user), but you may have more luck with this (option A or D).
http://forum.xda-developers.com/showthread.php?t=1613523

joel.maxuel said:
I always recommend this one for AT&T (could never try it myself, as I was a Rogers user), but you may have more luck with this (option A or D).
http://forum.xda-developers.com/showthread.php?t=1613523
Click to expand...
Click to collapse
Tried this a few times and it keeps failing. It'll get about 1/3 of the way there and then my computer will make the 'device disconnected' noise and Odin will fail. I left it in download mode, plugged in, without attempting the download to see if it was an issue with my cable or port, and it didn't disconnect...it seems to only be happening when I attempt to flash the md5.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.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> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!

SG2Tiger said:
Tried this a few times and it keeps failing. It'll get about 1/3 of the way there and then my computer will make the 'device disconnected' noise and Odin will fail. I left it in download mode, plugged in, without attempting the download to see if it was an issue with my cable or port, and it didn't disconnect...it seems to only be happening when I attempt to flash the md5.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.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> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Even with option D? I see C was used, based on the log...
Sent from my Asus MeMO Pad 8"

joel.maxuel said:
Even with option D? I see C was used, based on the log...
Sent from my Asus MeMO Pad 8"
Click to expand...
Click to collapse
For some reason option D is taking an unreasonable amount of time to download (it's been over an hour now), so I had initially skipped it and tried options A and C, with the same results. I'll report back once I am actually able to get option D downloaded.

Same problem with every option. Progress reaches about halfway, then fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex.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> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!

SG2Tiger said:
Same problem with every option. Progress reaches about halfway, then fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex.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> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Last thing I can think of, you are using the Odin that comes with the package right?

joel.maxuel said:
Last thing I can think of, you are using the Odin that comes with the package right?
Click to expand...
Click to collapse
Yes, it should be Odin3 v1.7.

The dev-host file mirrors are down? Does anybody have copies of them to upload?
I need the one with root.

Umaroth said:
The dev-host file mirrors are down? Does anybody have copies of them to upload?
I need the one with root.
Click to expand...
Click to collapse
Sorry, no option A here, but I do have option C (with CWM, deodex, etc) on mirror. See the following link:
http://forum.xda-developers.com/showpost.php?p=58392432
Hope this helps.

Link Are Broken
Umm the link cant be downloaded.. i m trying to restore my infuse but most of the downloadable file is broken or file not found

ZExNos said:
Umm the link cant be downloaded.. i m trying to restore my infuse but most of the downloadable file is broken or file not found
Click to expand...
Click to collapse
Good evening,
Try my mirror:
http://forum.xda-developers.com/showpost.php?p=58392432
Options are limited, only "Option C" but it should be enough to get the job done.
Cheers.

[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