I have galaxy s3 I9300 16GB
yesterday my phone got in loop of "touchwiz has stopped",
and couldn't do anything.
I tried to wipe cache - but it didn't worked.
I tried to flash new rom, but it failed,
and the phone was stuck on a screen telling me to recover with kies
Kies didn't recognize my device - it just keep connected forever but nothing else
so I search the internet, and advised to repartition the phone using pit file.
I did it, and now samsung logo blinked, and I can't access the volume up menu - only to the download screen.
When I try to flash rom - it starts, and stack on NAND write start - forever
enclosed;
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGNB1_I9300JKUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
please advise
@yalaniv: I guess your internal storage is gone.
What does it mean?
rp158 said:
@yalaniv: I guess your internal storage is gone.
Click to expand...
Click to collapse
Can it be fix?
What should I do now?
@yalaniv: a regular reparation in a service center doesn't make sense. So either look for a cheep way to repair or another phone.
Please find and read this post I just made, follow the directions.
http://forum.xda-developers.com/showthread.php?t=2535367
Related
Hi all,
I bought my Galaxy Ace S5830i last month. I hadn't installed Samsung Kies until yesterday, when I launched it it prompted a firmware upgrade. First I tried to use kies to upgrade but whenever the upgrade process started (Kies started downloading the firmware files) my device automatically got disconnected..I tried reinstalling kies, restarting my phone but nothing worked.
I then decided to use odin(v1.87) to flash the firmware on my device but it kept failing at first step itself. Here's what it said :-
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLF3_S5830iODDLF1_RST_S5830iDDLF1_HOME.tar. md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> BcmCP.img
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am at my wits end now so can anyone please help me sort out this problem?
Thanx in advance
PS: The phone has been working as fine as ever. Kies never got to the step of INSTALLING the new firmware as whenever it started downloading the firmware files my phone got disconnected so no damage there.
With ODIN I entered download mode but here too it fails at the beginning, so I just switch off my phone and restart it and it works as if nothing ever happened (I've made several attempts)
i have same problem
Hey Guys,
i guess i need your help. I've flashed diffrent ROM's with Odin before so i got an rough idea how it works.
Story so far:
GT-I9100 4.1.2 Official ROM (I9100XWLSD_I9100DBTLS7_DBT) with PhilZ Kernel (PhilZ-cwm6-XWLSD-OXX-4.87).
Phone swithed itself off for any reason and i tried to reboot it. Phone started up and was stuck at the screen with "Samsung Galaxy S II". Nothing happened for like an hour. After waitin i decided to flash the ROM again. And here it just got worse.
Using Odin3 v1.85 (Kies tasks killed, original samsung usb cable) i selected the ROM mentioned above and tryed to flash it. At first everything was running good, but the i got stuck at:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
i left it for half an hour or even more... nothing happened. I tried to flash Philz Kernel again, but i got stuck too.
Same for ICS ROM and GB.
I can't get into recovery mode (which i should have done before thinking of flashing stuff )
Download mode is all i can choose now. I'm not getting any further right now.
Can anyone help me with this? I'm quite bummed out. I need my phone
Thanks in advance.
Daniel.
i.am.dirt said:
Using Odin3 v1.85 (Kies tasks killed, original samsung usb cable) i selected the ROM mentioned above and tryed to flash it. At first everything was running good, but the i got stuck at:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
i left it for half an hour or even more... nothing happened. I tried to flash Philz Kernel again, but i got stuck too.
Same for ICS ROM and GB.
I can't get into recovery mode (which i should have done before thinking of flashing stuff )
Download mode is all i can choose now. I'm not getting any further right now.
Click to expand...
Click to collapse
Odin flash fails? Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
immortalneo said:
Odin flash fails? Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Click to expand...
Click to collapse
Thanks for that fast reply. I've skimmed over that guide and i have to say i've already tryed nearly all of it... that's a bad sign, huh?
I'll try diffrent Odin versions but i've been reading nearly everywhere that v1.85 is the correct version for my GT-I9100...
i.am.dirt said:
Thanks for that fast reply. I've skimmed over that guide and i have to say i've already tryed nearly all of it... that's a bad sign, huh?
I'll try diffrent Odin versions but i've been reading nearly everywhere that v1.85 is the correct version for my GT-I9100...
Click to expand...
Click to collapse
It wouldn't hurt to try then, would it?
Believe me when I say this, but a lot of members have reported this issue before, which led to the creation of the above guide. And its instructions are based to an extent on the successes reported by some members. So try all you can and see what happens! :good:
I've tried to figure it out to what extend different ODIN versions will give different results. Here's what i've been encountered with:
v1.3:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> cache.img
got stuck at cache.img
v1.83:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> cache.img
got stuck at cache.img
v1.85:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
same sh!t here
v3.04:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
what a surprise!
v3.06:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
failed for any reason
v3.07:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
it doesn't get any better
Seriously what is going on with that device?
Seems like it doesn't matter which ODIN version i use... the results are poor.
Any suggestions?
i.am.dirt said:
Seriously what is going on with that device?
Seems like it doesn't matter which ODIN version i use... the results are poor.
Any suggestions?
Click to expand...
Click to collapse
Keep trying out everything in that guide and in every possible combinations you can, until you're absolutely sure that your phone's NAND is borked. Then take it to a Service Centre.
Flash a packaged ROM (modem, code & csc) with the 3.06 version.
Sent from...this is not even my S2
i91000 brick at cache
Any ideas for this thread ? I have a simmilar problem, my i9100 can't flash any software any kernel ?
milo_sc said:
Any ideas for this thread ? I have a simmilar problem, my i9100 can't flash any software any kernel ?
Click to expand...
Click to collapse
i have same problem with my s2. did you fix it ? please reply fast
Same issue. Was this ever resolved? I can't even get the tablet to stay powered off now!
NickSaul said:
Same issue. Was this ever resolved? I can't even get the tablet to stay powered off now!
Click to expand...
Click to collapse
Has anyone tried gastonw's advice yet?
I was having the exact problem described in the original post on my Galaxy Note Pro 12.2 (SM-P900 wifi). I was able to fix my device by flashing TWRP through Odin. This allowed me to reboot my device as normal.
After I was able to boot back into my device, I went into developer options and realized that USB Debugging was NOT enabled. I ticked the box and reset back into Download mode. This time, the Odin flash went smoothly and quickly and I now have a rooted Note Pro 12.2.
So for those of you who are having Odin fail at flashing cache.img, try my solution and let me know if it works.
#1. Download TWRP (I got mind from the official TWRP website)
#2. Flash TWRP through Odin in the same method that you flashed CF Auto Root
#3. Boot into your device normally and open Developer Options in the Settings Menu
#4. Enable USB Debugging
#5. Connect your tablet to your PC
#6. A pop-up window will arise on your tablet asking to Allow the connected computer to debug your tablet; tap OK to Allow it
#7. Reboot into download mode
#8. Reflash CF Auto Root using Odin
These steps worked for me so hopefully they can help someone else out as well
justb2 said:
I was having the exact problem described in the original post on my Galaxy Note Pro 12.2 (SM-P900 wifi). I was able to fix my device by flashing TWRP through Odin. This allowed me to reboot my device as normal.
After I was able to boot back into my device, I went into developer options and realized that USB Debugging was NOT enabled. I ticked the box and reset back into Download mode. This time, the Odin flash went smoothly and quickly and I now have a rooted Note Pro 12.2.
So for those of you who are having Odin fail at flashing cache.img, try my solution and let me know if it works.
#1. Download TWRP (I got mind from the official TWRP website)
#2. Flash TWRP through Odin in the same method that you flashed CF Auto Root
#3. Boot into your device normally and open Developer Options in the Settings Menu
#4. Enable USB Debugging
#5. Connect your tablet to your PC
#6. A pop-up window will arise on your tablet asking to Allow the connected computer to debug your tablet; tap OK to Allow it
#7. Reboot into download mode
#8. Reflash CF Auto Root using Odin
These steps worked for me so hopefully they can help someone else out as well
Click to expand...
Click to collapse
Thx! good answer for unbricking my phone but... still get the same error with enabled debugging mode
CryserCore said:
Thx! good answer for unbricking my phone but... still get the same error with enabled debugging mode
Click to expand...
Click to collapse
I have the same problem with my s3 neo! I tried to root my phone with Odin , and phone now is bricked. Firat i have installed TWRP , und everything was fine. Than , i tried to flasch superuser to get my phone rooted. Now i can´t reach TWRP (??) , and only thing that i can do ist download mode.
I am tryin to flasch stock firmware through Odin, but ever the same - cache.img error! Help please!
Hi
Please anyone help me
I am also having the same error. It stucks at cache.img. I am trying I9100XWLPT_I9100XXLQ6_I9100XEULPA_HOME.tar.md5 downloaded from sammobile.com
My model is GT-I9100 .
Can anyone help please ?
Earlier , i was having cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100.zip and one day, it all gone bad. I can only use Odin mode.
I cannot even go to Recovery mode.
I tried boot.bin alone and that runs fine and it shows me Samsung logo screen.
I then tried renaming cache.img to cache.img.tar and that also runs fine .
But overall, it does not run when i think it tries to write to Nand or whatever.
I have tried all version of odin and various cables as well.
Any help will be hugely appreciated.
best regards
I had the same problem.....resolved it by extracting the tar.md5 file to the c:/ directly instead of the desktop...
Yo.
Had the same issue on the GT-I9506.
The issue occurred for me after I had accidentally attempted to flash an auto-root file to bootloader in ODIN, can confirm that flashing CWMR as through PDA solved my issue, as I was then able to flash the same auto-root file direct through PDA.
Hope this helps somebody, as I wasted an hour ****ing around trying to figure out how to fix. ^^
I've been using OmniROM and TWRP for quite some time now.
I put the phone on charge and a few minutes later it was stuck on Samsung initial Screen with the usual red triangle. (Showing SAMSUNG Galaxy SIII GT-I9300)
I removed the charger and battery and restarted, it was still stuck on Samsung Boot Screen.
Any ideas how to recover the phone?
I have tried going through some of the other forum threads but most of them can't go to download mode. I can go into TWRP and download mode both. I tried recovering the phone using Kies "Firmware Initialization" but it generates "your phone cannot be upgraded to the latest version" and stops.
falconflyer82 said:
I've been using OmniROM and TWRP for quite some time now.
I put the phone on charge and a few minutes later it was stuck on Samsung initial Screen with the usual red triangle. (Showing SAMSUNG Galaxy SIII GT-I9300)
I removed the charger and battery and restarted, it was still stuck on Samsung Boot Screen.
Any ideas how to recover the phone?
I have tried going through some of the other forum threads but most of them can't go to download mode. I can go into TWRP and download mode both. I tried recovering the phone using Kies "Firmware Initialization" but it generates "your phone cannot be upgraded to the latest version" and stops.
Click to expand...
Click to collapse
Download stock rom from Sammobile and flash in Odin..
tallman43 said:
Download stock rom from Sammobile and flash in Odin..
Click to expand...
Click to collapse
Downloaded latest stock rom ML4 and this is what I get in Odin 3.09:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XWUGML4_I9300ODDGML4_I9300DDUGMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/038> Added!!
<ID:0/038> Odin v.3 engine (ID:38)..
<ID:0/038> File analysis..
<ID:0/038> SetupConnection..
<ID:0/038> Initialzation..
<ID:0/038> Get PIT for mapping..
<ID:0/038> Firmware update start..
<ID:0/038> SingleDownload.
<ID:0/038> sboot.bin
<ID:0/038> NAND Write Start!!
<ID:0/038> FAIL!
<ID:0/038>
<ID:0/038> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
falconflyer82 said:
Downloaded latest stock rom ML4 and this is what I get in Odin 3.09:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XWUGML4_I9300ODDGML4_I9300DDUGMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/038> Added!!
<ID:0/038> Odin v.3 engine (ID:38)..
<ID:0/038> File analysis..
<ID:0/038> SetupConnection..
<ID:0/038> Initialzation..
<ID:0/038> Get PIT for mapping..
<ID:0/038> Firmware update start..
<ID:0/038> SingleDownload.
<ID:0/038> sboot.bin
<ID:0/038> NAND Write Start!!
<ID:0/038> FAIL!
<ID:0/038>
<ID:0/038> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Nand write fail usually means dead emmc chip. You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I think you need to send it fto service for repair.
tallman43 said:
Nand write fail usually means dead emmc chip. You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I think you need to send it fto service for repair.
Click to expand...
Click to collapse
I tried the rescue firmware, similar result:
Code:
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I finally took to a repair shop, they say it is my fault since I rooted it (they can see the red exclamation mark), and will charge extra for "software change".
Any idea how to reset the counter in download mode, revert to stock recovery and remove the red exclamation mark in bootloader?
P. S. I read somewhere in case of dead emmc I shouldn't be able to see the device version in download mode. But I can..
bricked device i9300..
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
dupri11 said:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
Click to expand...
Click to collapse
Did you try Odin 3.09? I too get the same result as you with Odin 3.07. With 3.09 I get the write fail error.
falconflyer82 said:
Did you try Odin 3.09? I too get the same result as you with Odin 3.07. With 3.09 I get the write fail error.
Click to expand...
Click to collapse
I used the 3.09 still same problem am stuked up really
If the rescue firmware and pit didn't flash then your emmc chip is damaged, either new motherboard or phone.
Sent from my GT-I9300 using Tapatalk
falconflyer82 said:
I finally took to a repair shop, they say it is my fault since I rooted it (they can see the red exclamation mark), and will charge extra for "software change".
Any idea how to reset the counter in download mode, revert to stock recovery and remove the red exclamation mark in bootloader?
Click to expand...
Click to collapse
There must be a way to reset the download count by installing stock recovery. Maybe @Chainfire can help here.
Sent from my XT1033 using Tapatalk
dupri11 said:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
Click to expand...
Click to collapse
what @boomboomer said is what you should consider.
If you keep on insisting, you will just damage the phone more ( i am talking from experience ) .
change motherboard or in some places, people can replace the emmc Chip for you.
Salam
Hello,
My wife has this phone and the phone accidentaly turned off and after that he was not able to boot. It was stucked on samsung logo. I tryied recovery mode and wipe phone, but it not helped. After that phone started stucking on galaxy S2 logo (before samsung logo). I was able only to go into download mode. I tried to follow this guide: wccftech.com/install-latest-android-412-jelly-bean-galaxy-s2-i9100-official-firmware but in odin (v3.07) it failed after some time (while progress bar is not moving from beginning, I see only one px of it). And now phone is showing message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Please can you help me how can I recover phone back? thanks a lot for any help
it is czech version bought in samsung shop. So I downloaded XEZ-I9100XWLSD-20130301125313 (but I am not totaly sure about version, this should be for czech)
On load PDA
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100XEZLS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
After press Start
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> cache.img
After some time
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dawee said:
Hello,
My wife has this phone and the phone accidentaly turned off and after that he was not able to boot. It was stucked on samsung logo. I tryied recovery mode and wipe phone, but it not helped. After that phone started stucking on galaxy S2 logo (before samsung logo). I was able only to go into download mode. I tried to follow this guide: wccftech.com/install-latest-android-412-jelly-bean-galaxy-s2-i9100-official-firmware but in odin (v3.07) it failed after some time (while progress bar is not moving from beginning, I see only one px of it). And now phone is showing message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Please can you help me how can I recover phone back? thanks a lot for any help
it is czech version bought in samsung shop. So I downloaded XEZ-I9100XWLSD-20130301125313 (but I am not totaly sure about version, this should be for czech)
On load PDA
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100XEZLS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
After press Start
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> cache.img
After some time
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Seems like you have brick bug but I have no idea how to fix it.
Next I have tried to follow this guide: http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
I am not totaly sure about kernel version, but because this phone was pursached on his release, I have downloaded GINGERBREAD VERSION. I have tried to flash it but without success too. Green progress bar is moving to the end and after some time it writes "fail"
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Kernel_I9100XXKI3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> zImage
<ID:0/010> NAND Write Start!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
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.md 5 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.
I've also tried different usb cables, along with trying out different ports, none of them have worked.
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 !
Reply
Kiddzu said:
<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.md 5 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!
Click to expand...
Click to collapse
Hi, after NAND Write Start!! and this double !! means it start to WRITE on your Device Flash Memory when this fails it means that the cable dont transfer correct data / Cable Connection OK but wrong cable cannot write correctly on your device
I recommend you to use Original cable when flashing or a other cable but look for the compatibility to devices:good:
as far as I know it cant be a other opportunity to fix this because in the Download Mode of the s3 is the only way to Flash Original Firmware when this fails i dont now how to continue and i cannot help you more than that
And sry for my bad as fu** English