Getting this so far
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
Should I pull the cable or what? Very confused.
It's just stuck there and the blue thing is no longer moving on the device.
Probable bad firmware file .
Skander1998 said:
Getting this so far
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img
Should I pull the cable or what? Very confused.
It's just stuck there and the blue thing is no longer moving on the device.
Click to expand...
Click to collapse
Happen to me long time ago when flashing another region firmware...what I do I just pull out the battery and re-enter again download mode...when it stuck just pull out the battery and flash again until it show pass...
danierakes said:
Happen to me long time ago when flashing another region firmware...what I do I just pull out the battery and re-enter again download mode...when it stuck just pull out the battery and flash again until u success...
Click to expand...
Click to collapse
That worked.
Solved.
Related
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLPU_I9100XXLQ6_I9100XEZLP3_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> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
While Flashing Latest Stock ODIN getting stuck again and again on same MSG "cache.img" any solution ????
IAmRizzler said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLPU_I9100XXLQ6_I9100XEZLP3_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> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
While Flashing Latest Stock ODIN getting stuck again and again on same MSG "cache.img" any solution ????
Click to expand...
Click to collapse
If you did NOT check repartition and did NOT select a .pit file then you are safe. Then you can just try again. Or try again with a different rom and/or a different USB cable.
Sounds like the tar file you downloaded might be corrupt. Try downloading it again, and once you've done so/unpacked the tar, use 7Zip to test the integrity of the archive. If it comes up all files OK/no errors then that isn't your problem.
i am flashing CM9 Resurrection Edition for use with Odin:
20120420: Download
this method Download CM9 Resurrection Edition
- Download GApps and put it onto your internal sdcard
- Open Odin
- Choose cm-9-XXXXXXXX-ODIN-galaxys2.tar.md5 as PDA
- Boot your phone into download mode
- Connect your device via usb to your computer
- Wait till Odin has fully recognized your phone
- Hit the start button and wait till the flash process is finished
but now odin id stuck at
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.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> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> modem.bin
<ID:0/004> factoryfs.img
<ID:0/004> data.img
what should do unplud close odin what
its about 15 mins
what i do any body i am freaking out
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300ZSEMB1_I9300OZSEMB1_899179_REV00_user_low_ship.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
What should I do now? It stucks and I don't want to lose my data.
Remove battery make sure Kies is not running in the takbar .
Flash again
Same problem download firmware and flash .
You may have lost your data rule one back up efs rule two backup data
jje
JJEgan said:
Remove battery make sure Kies is not running in the takbar .
Flash again
Same problem download firmware and flash .
You may have lost your data rule one back up efs rule two backup data
jje
Click to expand...
Click to collapse
Think those rules need to be made in to a banner for XDA
How long has it been stuck on system for?
try other verson of odin
Sent from my GT-I9300 using xda premium
I got a problem with my Note-2. Stuck on the samsung logo screen. (flash rom long time ago, i can't remember that rom but it's 4.1.2)
Can boot in CWM and download mode. I tried to wipe data/cache/dalvik but didn't work.
- Abyss kernel : not work
- pit file 16 gb : not work
- use 3 computers : not work
Here is log when i tried to flash stock rom.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME1_N7100OLBDMD2_N7100DXDLK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
nookdee said:
I got a problem with my Note-2. Stuck on the samsung logo screen. (flash rom long time ago, i can't remember that rom but it's 4.1.2)
Can boot in CWM and download mode. I tried to wipe data/cache/dalvik but didn't work.
- Abyss kernel : not work
- pit file 16 gb : not work
- use 3 computers : not work
Here is log when i tried to flash stock rom.
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N7100XXDME1_N7100OLBDMD2_N7100DXDLK5_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
sboot.bin
NAND Write Start!!
FAIL!
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Read droidstyles post in Development, its stickied, and follow the section on returning to stock.
Try the alternate ROM with and without the PIT first and if that doesn't work try the others.
Sent from my SCH-I605 using XDA Premium HD app
Hi
i updated my S III with stock firmware with 4.3 (I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5) via Odin. It was successful and worked fine for a few days, but after 3 or 4 days my phone get stucked on Samsung logo screen, i tried wiping data and cache from recovery, but problem is same. So i am trying to re flash my phone with same stock rom. But i am not able to do it.
I am using Odin 3.07,
Here is the Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I also used to Root it with cf auto root,
Here is the Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried using different USB ports and USB cables?
audit13 said:
Tried using different USB ports and USB cables?
Click to expand...
Click to collapse
Yes Tried, Recently my S III was updated via same port and USB Cable,
Have you tried flashing the stock ROM with a pit file?
It's also possible that the internal memory chip is damaged.
audit13 said:
Have you tried flashing the stock ROM with a pit file?
It's also possible that the internal memory chip is damaged.
Click to expand...
Click to collapse
Yes I tried, Here is result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Stuck on Get PIT for mapping,
Since it is stuck on the pit file, this leads me to believe that the cable is not compatible or the internal memory is damaged.
I have flashed many different Samsung phones over several years and I find that USB cables can cause the flash to fail when Odin is trying to read the partition information (PIT), flash a bootloader, or flash the system image.