Greetings!
I downloaded the GALAXY Tab 4 7.0 firmware for Slovakia and I am trying to put it to my SM-T230NU with Odin. No SD card in device, rooted.
When I click start on Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0ANE6_T230OXX0ANE2_T230XXU0ANE6_HOME.tar.md 5 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> SingleDownload.
<ID:0/005> timh.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How can I solve this problem? Thanks a lot!
Related
I was flashing a firmware from "I9100GZCKH4" to "I9100GDXLP6_I9100GOLBLP6_XME" on my Samsung S II GT-I9100G, and it failed. Now the screen shows "SOFTWARE UPDATE FAIL"
Odin says...
Message
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GDXLP6_I9100GOLBLP6_I9100GDXLP6_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> cache.img
<ID:0/005> NAND Write Start!!
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
<ID:0/005> MLO
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Happen to me once..make sure KIES not running in background..if u dont know how to check, just uninstall KIES..dont worry, u can get KIES installer later with just google it..
Sent from my GT-I9100G using xda premium
I am trying to flash my S III with I9300ZCUBMK2_I9300CHNBMK2_I9300ZCUBMK2_HOME.tar with Odin (tried different versions) on Windows 7. Here is the log from Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300ZCUBMK2_I9300CHNBMK2_I9300ZCUBMK2_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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I am coming from JB 4.1.2 for the first time.
Please help me.
Thanks.
Fail at Nand
Download a new stock rom and try.
Fails its a replacement motherboard Nand damaged .
It would be worth restoring your backed up EFS folder as a try anyway .
I've Samsung Galaxy S3 (GT-I9300T) purchased from Australia-Telstra.
The phone is stuck at Samsung Boot Up logo and is unable to proceed further.
However i've downloaded all the firmware versions from the below mentioned location:
.sammobilecom/firmwares/d...GT-I9300T/TEL/[/url]
2014-04-01_Australia_(Telstra)_4.3_I9300TDUUGNC1_I9300TTEL GNC1_YES
2013-11-01_Australia_(Telstra)_4.1.2_I9300TDUEMJ1_I9300TTE LEMJ2 YES
2013-01-01_Australia_(Telstra)_I9300TDUELL2_I9300TTELELL2_ YES
2012-11-01_Australia_(Telstra)_I9300TDUDLK2_I9300TTELDLK2_ YES
2012-08-01_Australia_(Telstra)_I9300TDUBLH1_I9300TTELBLH1_ YES
After using the Odin3 i get the error message mentioned below (NAND WRITE START....FAIL):
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300TDUUGNC1_I9300TTELGNC1_I9300TDUUGNA2_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Desprado_14 said:
I've Samsung Galaxy S3 (GT-I9300T) purchased from Australia-Telstra.
The phone is stuck at Samsung Boot Up logo and is unable to proceed further.
However i've downloaded all the firmware versions from the below mentioned location:
.sammobilecom/firmwares/d...GT-I9300T/TEL/[/url]
2014-04-01_Australia_(Telstra)_4.3_I9300TDUUGNC1_I9300TTEL GNC1_YES
2013-11-01_Australia_(Telstra)_4.1.2_I9300TDUEMJ1_I9300TTE LEMJ2 YES
2013-01-01_Australia_(Telstra)_I9300TDUELL2_I9300TTELELL2_ YES
2012-11-01_Australia_(Telstra)_I9300TDUDLK2_I9300TTELDLK2_ YES
2012-08-01_Australia_(Telstra)_I9300TDUBLH1_I9300TTELBLH1_ YES
After using the Odin3 i get the error message mentioned below (NAND WRITE START....FAIL):
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300TDUUGNC1_I9300TTELGNC1_I9300TDUUGNA2_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Tens of threads on this subject: Search results
Hi , I Just had a problem while flashing official ROM for SM-G530h Egypt ,Odin Gives me this error :
_________________________
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
_______________________________
Note : The device is Dual SIM , not rooted , It's completely clean ..
The ROM http://www.sammobile.com/firmwares/d...HOJV1AOF1_EGY/ ,
Any solution ?
Hello, my phone recently powered off by itself and when I powered it back on again it was stuck on the flashing Samsung logo. When I try to flash the stock firmware in odin it fails and I get the log below, help!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
debuffs said:
Hello, my phone recently powered off by itself and when I powered it back on again it was stuck on the flashing Samsung logo. When I try to flash the stock firmware in odin it fails and I get the log below, help!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You are flashing an older bootloader. That's why odin fails at sboot.bin.
You need to flash the latest firmware and it will work.