Hi, my Samsung Galaxy Tab 3 Lite SM-T111 stuck at bootloop and keep restarting. So, I planed to do it myself. I downloaded the SM-T111 firmware and tried to flash it via Odin but fail. Below is the result :
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T111XXUANF3_T111OLBANF3_T111XXUANF3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> obm.bin
<ID:0/005> DTim.Recovery
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Need help for this matter
Related
My phone had many issue after upgrading to 4.3 , I tried to odin M919UVUEMK2_M919TMBEMK2_TMB.zip stock to fix it , now Odin fails everytime. Tried downloading new SW in case it was corrupt and using different ports same result. It also fails at different points , sometimes it fails right away and sometimes it goes all the way to the end then fails
knox 0x1
also said something about seandroid kernal
Any Ideas
re: flashing stock firmware
ransome7 said:
My phone had many issue after upgrading to 4.3 , I tried to odin M919UVUEMK2_M919TMBEMK2_TMB.zip stock to fix it , now Odin fails everytime. Tried downloading new SW in case it was corrupt and using different ports same result. It also fails at different points , sometimes it fails right away and sometimes it goes all the way to the end then fails
knox 0x1
also said something about seandroid kernal Any Ideas
Click to expand...
Click to collapse
The issue you are having has nothing to do with KNOX.
What I would do is to uninstall all samsung drivers as
well as kies from your computer.
Then reboot the computer and install the latest Samsung usb drivers.
Here is the direct download link for the samsung usb drivers:
https://www.dropbox.com/s/k7ut088zsc5g0un/Samsung USB Drivers.zip
Good luck!
Misterjunky said:
The issue you are having has nothing to do with KNOX.
What I would do is to uninstall all samsung drivers as
well as kies from your computer.
Then reboot the computer and install the latest Samsung usb drivers.
Here is the direct download link for the samsung usb drivers:
https://www.dropbox.com/s/k7ut088zsc5g0un/Samsung USB Drivers.zip
Good luck!
Click to expand...
Click to collapse
Did as you said uninstalled all samsung drivers including kies , reinstalled , reran odin same result
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUEMK2_M919TMBEMK2_M919UVUEMK2_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Odin will work if I do a recovery , but will not load the stock firmware to completion, just run it again and this time it went further before fail
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUEMK2_M919TMBEMK2_M919UVUEMK2_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
This time the green bar was all the way done and failed at 99%
<ID:0/005> Added!!
<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> M919UVUEMK2_M919TMBEMK2_M919UVUEMK2_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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
ransome7 said:
This time the green bar was all the way done and failed at 99%
<ID:0/005> Added!!
<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> M919UVUEMK2_M919TMBEMK2_M919UVUEMK2_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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
Try using a different usb port and/or cable, that has helped me in the past with random flash failures, both through ODIN and fastboot (for nexus devices).
klebs89 said:
Try using a different usb port and/or cable, that has helped me in the past with random flash failures, both through ODIN and fastboot (for nexus devices).
Click to expand...
Click to collapse
It was the cable , used a different samsung cable went though first time. Thanks for the input that was the nudge I needed
Hello,
I am trying to reflash my T999 from 4.3 to 4.1.2 with Odin version 3.09 but it is not working at all.
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> T999UVDMD5_T999TMBDMD5_T999UVDMD5_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> 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)
The downgrade always FAILS (Auth) ??? I don't know what this means....Can anyone explain???
Any help or advice would be greatly appreciated!!!!
Please Read this thread. This has been discussed before. If you continue trying, you will hardbrick your phone.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100ODDFNI1_N7100DDUFND1_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> tz.img
<ID:0/005> system.img
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:crying::crying::crying::crying::crying::crying:
plzz help
im flashing it with 4.4.2
007skhan said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100ODDFNI1_N7100DDUFND1_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> tz.img
<ID:0/005> system.img
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:crying::crying::crying::crying::crying::crying:
plzz help
im flashing it with 4.4.2
Click to expand...
Click to collapse
change the usb cable?
Probably you have the stock recovery now.
Reboot in to Recovery, Format your device.
Flash your rom using ODIN again.
Model: SM-N910A
This is what I get from ODIN.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_N910AUCU1ANIE_N910AATT1ANIE_CL2774708_QB2373670_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what I do. I have tried using two different MD5's but no joy.
Any suggestions?
Thank you
I'm literally having the same exact issue. I'm on ATT. If you figure out whats wrong i'd appreciate it.
Here's my error code (i think identical to yours):
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_N910AUCU1ANIE_N910AATT1ANIE_CL2774708_QB2373670_REV00_user_low_ship_MULTI_CERT.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> 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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If you took the latest update, YOU CAN NOT ROLL BACK. I believe it is OCD5.
thepoetlives89 said:
If you took the latest update, YOU CAN NOT ROLL BACK. I believe it is OCD5.
Click to expand...
Click to collapse
Ughhhhhh!!!!!!! That sucks man.
Did you get it to work?
Hey guys
I'm in the same boat as you. Been trying all morning to flash using several different odins and images. By chance did you guys figure out a solution?
NO luck
facing same problem. Latest update messed up my network. Any SIM CARD not working,..
Hi, I am trying to flash the stock firmware 5.1.1 for SM-920P (sprint s6) since I can't connect to the t-mobile network after buying a carrier unlock from a third party. I get this error:
<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> Added!!
<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> 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)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Removed!!
<ID:0/004> Added!!
I had issues as well. Try a new USB cord. I eventually got it.