I am from India, and I was using the Galaxy s2 with Jelly Bean 4.1.2(installed from KIES). The phone suddenly crashed and only download mode is accessible. I downloaded the stock firmware from sammobile and tried odin3 v3.07, but it isnt working and the 0:[com3] background is blue.
The firmware i tried booting it with is I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5
i uploaded this by clicking on the PDA button and this how far it got to:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSK_I9100ODDLSA_I9100DDLS9_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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've run out of ideas and forums that I've gone through ! Some one please help!
Look for @Hopper8 thread. Great thread lots of info on Odin problems
No Luck!
andrewwright said:
Look for @Hopper8 thread. Great thread lots of info on Odin problems
Click to expand...
Click to collapse
Hi,
I read through and tried flashing with siyah v6 but even that failed.
Not really sure what the issue is!
mosesadarsh said:
I am from India, and I was using the Galaxy s2 with Jelly Bean 4.1.2(installed from KIES). The phone suddenly crashed and only download mode is accessible. I downloaded the stock firmware from sammobile and tried odin3 v3.07, but it isnt working and the 0:[com3] background is blue.
The firmware i tried booting it with is I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5
i uploaded this by clicking on the PDA button and this how far it got to:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSK_I9100ODDLSA_I9100DDLS9_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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've run out of ideas and forums that I've gone through ! Some one please help!
Click to expand...
Click to collapse
Doesnt seem like the phone is charging either!!
Flash philz kernel and then you should be able to get to recovery then flash a custom Rom
Read this bro
http://forum.xda-developers.com/showthread.php?t=2101610&page=2
Hope it helps !!
I tried everything possible but nothing worked. . I got stuck at factoryffs every time then hit xmit data failure. . M sure I hard bricked it now! ! Must be the motherboard. .
can someone please post links to the philz kernel and a stable india version JB firmware !! Please please ... im desperate!!
Search!! Dont be lazy its not hidden or hard to find.
seriously bro?? I found the thread to that kernel but that list is never ending.. God knows which kernel is for my phone!!
Only comment if you have answers please !!!!
All the videos that i watched online show how to install philz kernel on a working phone.
My phone is kinda dead... so what needs to be done after flashing philz kernel? Tell me the next steps please..
Does it still go to download mode? Does odin still see it?
I tried flashing my phone with philz kernel but even that failed...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSK-ODD-4.92.8.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> zImage
<ID:0/005> NAND Write Start!!
<OSM> All threads completed. (succeed 0 / failed 1)
Make is easy on your self and flash lss firmwear and flash lss kernel "near the top of download list" chances are you dont have an os now odin has failed to flash. Hooper8 thread has good info on flashing problems! Read that before you try.
Pics clicked a minute back... does this help...
Pls read hooper8 thrsad
Any joy now op?
Nope.. No luck... nothing goes beyond the nand write start! message.. Im done trying stock rom from sammobile, siyah v6, philz kernel.. nothing succeeded
mosesadarsh said:
Nope.. No luck... nothing goes beyond the nand write start! message.. Im done trying stock rom from sammobile, siyah v6, philz kernel.. nothing succeeded
Click to expand...
Click to collapse
Same problem here, my phone was working fine then all of a sudden i noticed it was dead, tried rebooting it, nothing happened, boot loop, tried to access CWM, i got the lower section menu of CWM but nothing else, a black screen with the buttons.
So next i said, let me use odin to flash a new kernel. That failed and ever since that failed, i cannot do anything except enter download mode. If i power the phone on, i get a [phone-problem-computer] image in yellow with text that says somehting like problem loading software, please conntect to kies recovery mode. of course that never works.
And everytime i try to flash absolutely anything on this device, Odin DOES see the device, and the second i press flash/start, when it reacher nand write start, it hangs there, stuck doing nothing.
I took the phone to a friend who has an Riff jtag box, he soldered his jtag to the phone and said the memory chip is not dead, i can read its capacity normally. But when he tried to write to it, it did not work, kept giving him errors, he said he has never encountered such a behavior before. And then i had to leave.
Up to now, my phone is still dead and i have no idea what to do. It only enters download mode, but at the same time, this is useless since flashing anything simply does not work. Anyone knows what the reason could be?
FYI, i was on NeatROM 5.5, which comes with Philz Kernel.
NAND is stuffed/corrupted. How/why - who knows ? Motherboard replacement if you've already tried JTAG. Could be something hardware going on that caused the chip to become 'damaged'.
So this happened this morning, I noticed my phone was rebooting and thought it was a bit strange. Now it just gets to the 'Samsung Galaxy SIII' logo and restarts. I have a UK i9300 16Gb on Orange, and I did replace the screen myself when I broke it - but that was about 6 months ago. Please don't say that's related :angel:
When in Odin / Download mode it shows the product name - am I right in thinking that this means that there's hope yet? The flash counter shows 1, which is correct. The last two fields show 'custom'.
I've tried flashing a newly downloaded stock firmware from Sammobile but it fails when it gets to start writing the NAND. I've tried flashing a PIT (yes, for my exact model) but that also fails. I'm getting this:
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> Removed!!
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I'm currently on hold to Orange to see what they can do. Obviously I'm not going to tell them about the rooting, self-repairing business but I'll see what they say. If I can fix it myself and avoid the delay of having to send it away I'd much rather do that.
Thanks in advance dudes.
Sounds like NAND failure, you've already tried all the recommended fixes (correct version of odin?) -new motherboard required.
Hmm, what are the different versions of Odin? I just figured the latest revision number would be the most reliable.
Just tried flashing Clockworkmod Recovery to try and get recovery mode working again - same problem.
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Are you sure you were on ME7? You might need to flash a newer firmware.
Sent from my NCC-1701 using Tapatalk.
Definitely need to flash newer firmware
degradedtree69 said:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Click to expand...
Click to collapse
This has happened to me about four times with my phone. I was able to fix through a process of Kies and Odin. It seems that if you do all that you can in Kies, as far as attempting to re-install the stock firmware. Kies has the drivers you need in order for Odin to work. You will need to run through the Kies process (it will fail), but you will get the drivers you need. You will then need to boot into download mode and do the Odin flash process. This is all assuming you have the correct files for Odin. You will need to flash the stock build afterwards unless you have a backup and are able to access safestrap which i doubt you will have.
First, apologies if this has been solved somewhere on the forum, as I haven't been able to find it.
My rooted Verizon S4 became unstable a few weeks ago; random re-starts, bizarre battery draining, inability to re-start unless connected to a charger, etc.. I did a factory reset and the problems persisted. I installed Kies and downloaded the original stock ROM, but Kies was unable to connect to my device. After poking around online, I ran Odin and tried to flash the stock ROM that way. Here's how that went:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when I start the phone, I get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message. Only Kies won't connect to my phone so I have no idea how to proceed.
If anyone has any suggestions, please help! I'm sure I left out some pertinent details, so let me know what else I need to tell you...
Had your phone been updated with any of the OTAs? It appears that you attempted to flash the original MDK firmware. You cannot downgrade to MDK, if the phone had been updated.
Actually I do think it got the latest update after I'd done the factory reset.
Are you saying I have the wrong tar.md5 file?
so I tried this, based on another recommendation: http://forum.xda-developers.com/showthread.php?t=2735172
the phone is at least operational again. however it's still re-starting randomly, but will not stay on after a re-start unless plugged in to a charger (battery at 80+%). not sure how the OS can still be corrupted if I just re-installed it; could something else be causing it to be so unstable?
My mom broke her Galaxy S III (T-Mobile SGH-T999) somehow. Overnight, it just randomly stopped working and won't boot past the logo screen. I tried getting into recovery mode, but every time I actually get it to say "recovery booting," it immediately vibrates and then goes back to logo cycling and won't let me do anything in recovery. I can, however, get it into Odin mode, so I tried going into it and flashing the firmware with Odin 3.10.6. Every time I do, I get the big red FAIL and it throws this error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea what's going on with this, and would appreciate any help anyone can offer on what to do next.
Did you try Odin older versions ?
Cooldato said:
Did you try Odin older versions ?
Click to expand...
Click to collapse
Yeah, I went through three of them.
heatherly84 said:
Yeah, I went through three of them.
Click to expand...
Click to collapse
could you give me more details?
Which version/firmware you're trying to flash via Odin?
Which version/firmware did phone have when it "died" ?
Did phone have USB Debugging enabled?