Odin failed while updating to KitKat. I don't understand it as I have flashed roms before. Can anybody help on the message or what to do to restore it? It seems to be failing on a size issue but the MD5 checks are correct.
<ID:0/046> Removed!!
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> aboot.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl1.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ALD2355 said:
Odin failed while updating to KitKat. I don't understand it as I have flashed roms before. Can anybody help on the message or what to do to restore it? It seems to be failing on a size issue but the MD5 checks are correct.
<ID:0/046> Removed!!
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> aboot.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl1.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Looks to me like you need a PIT file. What variant are you running?
We are using Odin 3.09 and the tar file as above.
I don't think you need a pit file , have you re tried the odin flash ?
I used the polish NB3 version (multi csc)
It works on my BTU N9005
Sent from my SM-N9005 using xda app-developers app
---------- Post added at 10:34 PM ---------- Previous post was at 10:26 PM ----------
http://forum.xda-developers.com/showthread.php?p=50201265
Try the Poland multi csc
Sent from my SM-N9005 using xda app-developers app
There is no PIT file in the download from Sammobile. There is only one file for the PDA/PIT.
I have downloaded and tried a second copy and get the same as it gets to the end of the first section
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> sbl1.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> aboot.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ALD2355 said:
There is no PIT file in the download from Sammobile. There is only one file for the PDA/PIT.
Thanks for your help on this - this worked with the PIT file in place
Click to expand...
Click to collapse
ALD2355 said:
Odin failed while updating to KitKat. I don't understand it as I have flashed roms before. Can anybody help on the message or what to do to restore it? It seems to be failing on a size issue but the MD5 checks are correct.
<ID:0/046> Removed!!
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> aboot.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl1.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hv a look a this http://forum.xda-developers.com/showthread.php?t=2643572
Are trying to flash a carrier rom, it seems there's a problem when trying to flash these...
The reason I ask is carrier roms generally have the "hidden" partition and it almost always screws up there...
ultramag69 said:
Are trying to flash a carrier rom, it seems there's a problem when trying to flash these...
The reason I ask is carrier roms generally have the "hidden" partition and it almost always screws up there...
Click to expand...
Click to collapse
Thanks for the help in getting me out of the mess. I used these links:
Pit: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Files: http://forum.xda-developers.com/showthread.php?p=50201265
ALD2355 said:
There is no PIT file in the download from Sammobile. There is only one file for the PDA/PIT.
I have downloaded and tried a second copy and get the same as it gets to the end of the first section
<ID:0/046> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> sbl1.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> aboot.mbn
<ID:0/046> rpm.mbn
<ID:0/046> tz.mbn
<ID:0/046> sdi.mbn
<ID:0/046> NON-HLOS.bin
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> system.img.ext4
<ID:0/046> modem.bin
<ID:0/046> cache.img.ext4
<ID:0/046> hidden.img.ext4
<ID:0/046> FAIL! (Size)
<ID:0/046>
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
DBT NB4 is faulty. Pit file error.
XEF NB4 works just fine. At least on unbranded phones
Sent from my SM-N9005 using Tapatalk
mikkelrev69 said:
DBT NB4 is faulty. Pit file error.
XEF NB4 works just fine. At least on unbranded phones
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. It works with th PIT file. There is no note on the download site so that's why I posted the links above as other people will experience the same problem as me.
ALD2355 said:
Thanks for the help in getting me out of the mess. I used these links:
Pit: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Files: http://forum.xda-developers.com/showthread.php?p=50201265
Click to expand...
Click to collapse
No problem, happy you're back up and running... :good:
HI my phone was wokring perfect till i tried to dometic unlock my phone following a tutorial from here , when i when to flash the zip the odin fail now imstuck in a black screen i only can boot into download mode but cant go into my recovery , i tried diferent odin and stock tar file but odin keep failing. my phone had the 4.4.2 NG2 i tried that tar but no luck ether , in download mode i have something saying write protection enable i dont know if this is the reason i cant flash the tar. can anyone help me get my phone back to work pls .....
this is what im getting from odin
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
I'll try to help, not that good myself though. What happens when you try to go into recovery?
I'm having the same problem. Only this phone was dropped by my friend on its top left corner and hasn't booted since then.
I successfully flashed the stock NAE tar through Odin last night but it still won't boot. I also cannot boot into recovery. It simply vibrates but nothing shows up on the screen at all. I can only boot into download mode intermittently.
Can't figure out why it would flash but not boot.
After owning the phone for a grand total of five minutes I managed to go past go and straight to a soft brick after a root-gone-wrong.
Out of the box it was running 4.4.4, but I don't know which of the three Verizon firmwares it was. I've attempted using Odin to flash stock using all three of them and I can't get Odin to play nicely.
The latest/greatest attempt was to flash \G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar.md5. I'm getting the following Odin output:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm getting the same output regardless of which stock I'm trying to flash.
May I trouble you guys for some help?
... not that I expected it to work, but I tried the Verizon recovery software in a Windows VM. It seems great up until it hangs at 83% (repeatedly) before telling me the device has been disconnected. If anyone wants to try that rabbit hole, I'll get the precise error verbiage.
Selfish <bump>
I bought one galaxy s5 Verizon from eBay. I installed Subway surfer game and it reboot itself, now i will not able to boot and stuck on boot loop.
I tried to go in recovery but it not able to go in recovery (only show blue text on top booting recovery). also not able to boot in safe mode.
It able to boot in download mode so I tried to install lollipop firmware of Verizon through odin3.09, 3.1 but it always show fail.
I also tried changing computer and USB cable but still same issue.
Kindly help to resolve this issue.
update:
I flashed G900VVRU2BOE1 firmware through odin 3.10.7. flashind done properly and odin say pass but still phone not able to boot , only show samsung logo and not able to boot in recovery also.
i receive followig details from odin
<ID:0/036> 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/036> Odin engine v(ID:3.1100)..
<ID:0/036> File analysis..
<ID:0/036> SetupConnection..
<ID:0/036> Initialzation..
<ID:0/036> Get PIT for mapping..
<ID:0/036> Firmware update start..
<ID:0/036> SingleDownload.
<ID:0/036> aboot.mbn
<ID:0/036> NAND Write Start!!
<ID:0/036> sbl1.mbn
<ID:0/036> rpm.mbn
<ID:0/036> tz.mbn
<ID:0/036> sdi.mbn
<ID:0/036> NON-HLOS.bin
<ID:0/036> boot.img
<ID:0/036> recovery.img
<ID:0/036> system.img.ext4
<ID:0/036> cache.img.ext4
<ID:0/036> modem.bin
<ID:0/036> RQT_CLOSE !!
<ID:0/036> RES OK !!
<ID:0/036> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/036> Removed!!
So I've installed a custom ROM on this phone about 2 years ago. It's my girlfriends phone.
Every once in a while when she turns her phone on it would go into a boot loop several times, and eventually go into the system and function normally. It was very intermittent, but it wasn't a big deal. Yesterday the phone was stuck in a permanent boot loop. What was interesting is that i could not enter into a Recovery Mode, just download mode.
So i figured it was time to just simply flash the original stock ROM.
ODIN 3.12.7
ROM: FMC-G900W8VLS1DPF3-20160725152930 (Canadian Koodo Android 6.0.1)
Flash was completely successful (I've flashed and unbricked many phones so I am very familiar with the process). This is the ODIN log file
<ID:0/004> 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/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> modem.bin
<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)
Phone restarts with blue Recovery Booting message and is stuck in a boot loop again. Boot loop is always trying to go Into Recovery Mode (just like previously before flash). I know that flash was successful because I no longer have the yellow Warranty Bit message i did when custom ROM was installed, So then i figured maybe i need the PIT file. I found a pit file SM-G900W8_pit_16GB.
I've then re-flashed again with this PIT file (Auto-reboot, re-partition, and F. Reset Time checked) and got an error message
<ID:0/004> 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/004> Odin engine v(ID:3.1207)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know what else to do. The phone has been dropped quite a few times which is obvious by its appearance. Does anybody have any suggestions?
srdjmor said:
So I've installed a custom ROM on this phone about 2 years ago. It's my girlfriends phone...
Click to expand...
Click to collapse
I don't have this specific device but, your best bet is to post this question within the following Discussion thread for your specific device.
https://forum.xda-developers.com/showthread.php?t=3228804
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE