Issue:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Solutions tried:
1. Downloaded 2 types of ROMs a) (I9300XXEMF6_I9300OLBEMF3_I9300DXEMB1_HOME.TAR); b) I9300XXEMF6_I9300ITVEMF1_I9300XXEMF6_HOME.tar.
Flashing through ODIN in DOWNLOAD MODE failed right after cache.img.
2. Changed USB cable, USB ports & computer.
3. Downloaded separate USB driver & KIES (killed its processes before flashing).
4. Could not get into recovery mode.
Please help, thank you!
Saladz said:
Issue:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Solutions tried:
1. Downloaded 2 types of ROMs a) (I9300XXEMF6_I9300OLBEMF3_I9300DXEMB1_HOME.TAR); b) I9300XXEMF6_I9300ITVEMF1_I9300XXEMF6_HOME.tar.
Flashing through ODIN in DOWNLOAD MODE failed right after cache.img.
2. Changed USB cable, USB ports & computer.
3. Downloaded separate USB driver & KIES (killed its processes before flashing).
4. Could not get into recovery mode.
Please help, thank you!
Click to expand...
Click to collapse
Failed? if there was an error, please post it.
rootSU said:
Failed? if there was an error, please post it.
Click to expand...
Click to collapse
Ops sorry, here you go:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF6_I9300OLBEMF3_I9300DXEMB1_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.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sounds like the internal memory is screwed. Probably needs to be sent for repair.
It might be worth trying a rescue rom & pit:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Make sure you follow all the instructions.
rootSU said:
Sounds like the internal memory is screwed. Probably needs to be sent for repair.
Click to expand...
Click to collapse
Just tried to flash 2 (Phone & CSC) files out of a 3 files package. It was able to write, the green bar in Odin and blue bar on my phone was moving till halfway but still failed. It shows:
<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> modem.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img
<ID:0/005> FAIL!
Click to expand...
Click to collapse
Also, the "No" in flash count became "1".
boomboomer said:
It might be worth trying a rescue rom & pit:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Make sure you follow all the instructions.
Click to expand...
Click to collapse
Hi, thanks for the link, i will keep it as my last resort =)
UPDATE***
Tried the pit file, killed my phone, not turning on now (black screen), looking for a usb jig now, but before that i have a question:
If somehow i could get the jig to work, what are the chances of me being able to fix the phone? Odin does not work earlier so i doubt using a jig would make much difference.
How about heimdall? I don't have a packaged heimdall file though >.>
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMC2_1042335_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMC2_1042335_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMC2_1042335_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300XXEMC2_KOR_FACTORY_1042335_REV00_user_low_ship.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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> tz.img
<ID:0/005> param.bin
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> tz.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Saladz said:
what are the chances of me being able to fix the phone?
Click to expand...
Click to collapse
Very slim, as rootsu said the memory sounds damaged. The pit rescue is a last resort, if that didn't work then new motherboard is probably required.
Usb recovery jig only boots to download mode nothing else .
At post one you had warranty now strictly speaking warranty is void .
jje
boomboomer said:
Very slim, as rootsu said the memory sounds damaged. The pit rescue is a last resort, if that didn't work then new motherboard is probably required.
Click to expand...
Click to collapse
Hmm, i don't understand, i left the phone charging overnight and it became like that, i did not even drop it so how could it fail itself (slim chance)?
JJEgan said:
Usb recovery jig only boots to download mode nothing else .
At post one you had warranty now strictly speaking warranty is void .
jje
Click to expand...
Click to collapse
Well warranty was over so i had to use such method lol
Phones dying when on charge all night is a weakness of these phones, not common but given the millions made quite a few have been reported.
Samsung warranty is 2 years, if your phone is now completely dead a service centre is worth a try.
Saladz said:
Hmm, i don't understand, i left the phone charging overnight and it became like that, i did not even drop it so how could it fail itself (slim chance)?
See the basic faqs and guides reference sudden death syndrome it would have been a free replacement of the motherboard under warranty .
Click to expand...
Click to collapse
boomboomer said:
Phones dying when on charge all night is a weakness of these phones, not common but given the millions made quite a few have been reported.
Samsung warranty is 2 years, if your phone is now completely dead a service centre is worth a try.
Click to expand...
Click to collapse
JJEgan said:
Saladz said:
Hmm, i don't understand, i left the phone charging overnight and it became like that, i did not even drop it so how could it fail itself (slim chance)?
See the basic faqs and guides reference sudden death syndrome it would have been a free replacement of the motherboard under warranty .
Click to expand...
Click to collapse
Well, the phone's warranty is already over before i tried any flashing.
A quick question:
Say if the usb jig works, will i be able to return the phone's condition to normal if odin worked? Or to the prior condition (firmware encountered issue..).
Or even if odin worked later it would be of no use due to the pit & bootloader flashing?
Thanks in advance!
Click to expand...
Click to collapse
Saladz said:
JJEgan said:
Well, the phone's warranty is already over before i tried any flashing.
A quick question:
Say if the usb jig works, will i be able to return the phone's condition to normal if odin worked? Or to the prior condition (firmware encountered issue..).
Or even if odin worked later it would be of no use due to the pit & bootloader flashing?
Thanks in advance!
Click to expand...
Click to collapse
Can you boot to download mode if so USB Jig is no use .
If three buttons boot to download mode fails recovery jig may boot into download mode and no more than that allowing you to flash via Odin .
But as your failure is posted via Odin jig is not going to do anything at all
Click to expand...
Click to collapse
Saladz said:
Issue:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Solutions tried:
1. Downloaded 2 types of ROMs a) (I9300XXEMF6_I9300OLBEMF3_I9300DXEMB1_HOME.TAR); b) I9300XXEMF6_I9300ITVEMF1_I9300XXEMF6_HOME.tar.
Flashing through ODIN in DOWNLOAD MODE failed right after cache.img.
2. Changed USB cable, USB ports & computer.
3. Downloaded separate USB driver & KIES (killed its processes before flashing).
4. Could not get into recovery mode.
Please help, thank you!
Click to expand...
Click to collapse
if you change the firmware name it wont work. if you download the firmware dont change the name just keep it the way you download it and set it on PDA.
it failed on me also because i change the original name ... so try that.
Related
Hello, together, up until now I was on Omega 4.0 (Yes very old rom^^) and due to many problems I wanted to set my Phone back to zero.
For that purpose I took the firmware with three parts and the 220 PIT for devices with 16gb, Now in the Odin log it shows for almost an hour now: "NAND Write Start!!"
The progressbar doesn´t move a bit and the phone itself isn´t showing any change either -.-'
Directupload.net - n79fcdue.jpg
Also the downloadmode looks different to my mind?...
So what should I do?!
To my knowledge the battery doesn´t load while flashing, so I can´t keep this up forever!
I have no clue what is going wrong and I am afraid I am bricking my 500€ phone!!! Please Help!
Here the complete Odin log:
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.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> sboot.bin
<ID:0/007> NAND Write Start!!
Ok first question is have you used PIT file .
The site you got the firmware from may give more information as XDA say never use PIT .
jje
Believe me, I will never use it again -.-
It just always worked fine on my old P1000 and gave me simply a Internal SD cleaned from all the garbage I loaded on there over time.
But on the S3 it seems to just **** everything up^^
I used the GT-I9300_mx_20120220.pit
Found it here: http://www.android-hilfe.de/origina...ersicht-firmware-listen-anleitungen-mods.html
(German forum)
https://hotfile.com/dl/156320160/eb4a939/I9300XXALE8_I9300OJVALE7_OJV.zip.html
The firmware I used.
http://www.multiupload.nl/RSGZTRC78Z
And a direct link to the PIT
Why have You used old pit? Mx.pit from May is that proper you should use to flash. You have no choice now, disconnect your phone and try to enter download mode.
I don't wont to scare You, but its look like flashing has stoped when bootloader was transfered and this is worst thing that may happend.
I hope You don't bricked your device. If its boot into download mode use this (Odin with proper pit file inside):
http://www.mediafire.com/?vc7jg5uz5tvcoi1
Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
SirKunon said:
Why have You used old pit? Mx.pit from May is that proper you should use to flash. You have no choince now, disconnect your phone and try to enter download mode.
I don't wont to scare You, but its look like flashing has stoped when bootloader was transfered and this is worst thing that may happend.
Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
Click to expand...
Click to collapse
DOwnload mode still working! Puh!
Now trying to flash without PIT, just in case the file system is wrecked: What is the right PIT?
The same **** happens without PIT and regardles of the firmware version!
Is there any way to fix this?
Hell yeah!
It works again!
Mx.pit did the job
phewwwwwwwwww the suspense killed me reading through this thread
glad it aint bricked
an awful situation
I was using the MIUI rom and I sold the phone. To deliver to the buyer I decided to go back to the stock rom but forgot to wipe and now I have the following situation:
- I can only get into download mode
- Odin recognizes the phone
- I tried to repartition the Odin reported successful operation (my model is 16gb)
- Tried to put other roms on the phone including those downloaded from the site sammobile, selecting only auto-reboot and f.reset.time
- With these steps could only get stuck in "nand write start ..."
- Tried installing kies but do not believe it can be something with the drivers because the odin recognizes the phone.
I read many posts but after two days decedi post to see if anyone would help me solve this issue
I'll be waiting for directions on how to proceed without worsening the scenario.
Odin log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_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> modem.bin
<ID:0/006> NAND Write Start!!
have you tried restarting your computer or using another computer? or even a different usb port or cable?
ages ago I had a similar problem - never moved beyond the start point - simple restart solved it for me...no idea if that's the same situation as you.
Just throwing out ideas here; otherwise I'm not sure.
Sent from my GT-I9300 using Tapatalk 2
Tried to do this, but still stucked at nand write start...
One thing I noticed is that the progress bar on the phone at the "downloading mode screen" runs quickly, and then it stops at nand write start.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBBLG2_I9300VILG1_I9300ZVVBLG1_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> modem.bin
<ID:0/005> NAND Write Start!!
At least I'm not alone
I have the exact same problem you have. Intl i9300, cannot enter recovery, only download mode. Flashing 16gb pit file works ok, however attempting to flash Stock rom gets stuck at Nand Write Start. Not sure what to do now, I guess I'll wait for responses here as well.
RePartition .
Fail Nand write .
Assuming you have read and are following the basics re an Odin flash ( if not go and read them ) .
This sounds in both cases like a damaged Nand >>> service centre job .
jje
I've not done much to my S3. Trouble started when I decided to install an OTA of Foxhound 1.8. Installation completed successfully but during the application upgrade (...you know the first boot message of 'Android is updating x of 365 apps). It froze and stuck there for like 15min so I decided to reboot it and all hell broke loose.
Started with 'Foxhound cannot mount recovery command..' etc. Which made me decide to flash my 16gb pit file, and since then all attempts to flash back to stock stall at 'Nand write start'.
I have backups of everything, even my efs. Problem is I can't even get to recovery to restore anything.
I'll keep trying I guess, worst case I'll just return it back to Samsung.
pull usb devices except s3 and be sure to have correct drivers then try again. you may even try it on another pc of course with installing drivers. if none of them works try flashing a kernel or recovery if it flashes then try to flash stock rom.if stucks again at nand write there may be a problem at emmc sect. but dont worry just do what i said if it fails there should be a solution
if you can enter the recovery mode u should be happy
to kamau can u send me the pit file you flashed thanks
zhjackss said:
to kamau can u send me the pit file you flashed thanks
Click to expand...
Click to collapse
There it is. I"m now working on resetting the flash counter from odin since I obviously can't install triangle away in preparation of returning it to samsung.
Hello everyone,
I am not sure whether this is the right place for my question but my Galaxy S II stopped working and I was wondering if anyone might help me?
I tried updating the FW from 2.3 to 4.0 (I'm guessing) through Kies and after about 45 minutes of seeing both screens (PC and Phone) unchanged, I ended up removing the phone. Next, Kies suggested an "Emergency Firmware thingy" (it said it in German so I wouldn't really know how to translate it). Tried again, after 45 minutes gave up once more.
Since then, I downloaded ODIN and tried to follow instructions I found online to flash it (first I tried with Ice-Cream, then with Gingerbread).
Ever since I removed it from Kies, it would only show a phone connected to a PC with a yellow warning triangle in the middle. Whenevery I use the Volume-Menu-Power button, the warning on changing the OS appears and then, when I press "volume up", it shows the green android in the middle and tells me it's downloading and not to turn off the device, though there is no downloading progress.
When I try with ODIN, ODIN recognizes the device on both USB ports - I found md5 files for Germany but every time I start it the Message window says:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_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
and doesn'tget any farther than "cache.img".
I am at a complete loss as to what to do or try. I have had this phone for a year now, this is the first time I tried to update with Kies - the phone had not been rooted or anything else. The phone has no simlock (I don't know if any other information is relevant).
Any ideas or has my phone thus become the infamous brick? *pleasenopleasenopleaseno*
Thanks in advance for your time and patience - in case I've overread a thread with this exact same problems, I apologize and would appreciate if someone could re-direct me. I've already spent so much time looking for solutions, my concentration may have suffered.
Best wishes,
Junivere
Before flashing with Odin, did you kill all Kies processes from Windows task manager? If not, do that and then start flash.
Edit: And since you can access download mode, its not bricked...so you can relax
Sent from my GT-N7100 using Tapatalk 2
I9100?
Flash JB.
And try an older ODIN version.
And check kies like the above poster suggested.
Other usb port/usb cable might do the work too.
Sent from the little guy
Thanks for the replies!!!
I stopped all the Kies processes over the task manager before (was that enough?) and tried from both USB ports of my laptop (006 and 007 I guess) with equal results.
I used Odin3 v1.85 - is that too old or too new? Which version should I try?
And I am sooooooooo relieved it's not a brick!!!
Thanks again!
kinda old, try 1.3 or 3.x
And flash siyah v5 just for kicks.
Sent from the little guy
I tried again and I'll try to explain step by step, ok? Maybe you notice something I did wrong?
I killed all the Kies processes in the task manager like before.
I downloaded Odin 3 v.07 and started it. I had "Auto reboot" and "F.Reset time" checked and clicked on "PDA" to add the *.md5 file with the firmware.
I started the phone in the download mode and connected it to the PC, Odin recognized it alright.
I started and the first time, with the USB port in front, it stopped at "cache.img" in the message window.
I tried a different FW file and the other USB port further back and for the first time the phone shows a tiny bit of blue in the progress underneath "Downloading..." but in Odin it is now stuck at "factoryfs.img" for the last ten minutes,
The entire message window says this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<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> factoryfs.img
Any ideas???
Best wishes and thanks again!!!
Flash siyah V5.
Sent from the little guy
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Junivere83 said:
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Click to expand...
Click to collapse
gokhanmoral.com
Siyah v5 for SII.
Put it on PDA, press start and flash away.
Sent from the little guy
Ok, so now I am starting to get slightly terrified:
When trying to flash Siyah 5 (Siyah-s2-v5.0.1), it stops there:
<ID:0/007> Added!!
<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> zImage
:crying:
Keep trying, you'll come around.
Another usb cable could help.
Another pc would as well.
Sent from the little guy
Ok, so the Sivyah v5 flash worked when I tried Odin3 v1.3 but I'm still battling with the actual firmware.
Thanks for your help so far, though - I'm really greatful and I'll keep trying.
My mission for today will be finding someone's cable and PC to borrow...
I'll keep you posted, though!
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Junivere83 said:
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Click to expand...
Click to collapse
Depends on what ROM you are flashing.
For instance, if you flash LS8 you'll get a 22 mb update to get you to LSD.
I would flash LSD straight up tho.
If you don't want a headache with odin no more, feel free to try Mobile Odin, it will perform all the flashing for you.
Sent from the little guy
Hello everybody!
First of all, I'm not sure about my english skills...please have mercy on me :fingers-crossed:
Here I go:
I got my S3 in August/Sept with a T-Mobile Branding. My first action was getting it rootet and flashed with an official Samsung Rom just to get rid of the branding.
Two days ago I woke up to my charging S3 only showing the "Samsung..." Bootlogo. Removed the battery, nothing changed. Tried the Volume up-HomeButton-PowerButton Combo and it only resulted in a blinking logo (the logo disappears for a few seconds). The only thing I have access to is the Download-Mode.
What I tried since then:
Flashing a new one-part-rom with Odin, this was the result:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.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> sboot.bin
<ID:0/003> NAND Write Start!!*
<ID:0/003>*
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Same with a three-part-rom.
Then I tried to downgrade the bootloader with ADB. But I don't get the drivers (Universal-Naked-Drivers) running. The S3 shows up as "unknown device" at the device manager but it doesn't want to be updated with the right drivers. PdaNet also refused to install USB-Drivers.
It's like they don't recognize the S3.. Perhaps I don't have USB-Debugging enabled? I'm not sure about this, because this brick just happened from one day to another.
I installed and uninstalled the "normal Samsung USB-Driver for mobile phones" often while trying to get the other drivers running. When installed, the S3 showed up in the device manager as one of the USB-Controllers.
Installed Kies for a factory reset but it didn't recognize the S3..
This shows up in Download-Mode:
ODIN*MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
I guess it's no sudden death because it shows the product name? Also I have no idea why it has three flash counts, I just flashed it once seven month ago.
Since I never updated to Jelly Bean the S3 was running on ICS 4.0.4
Edit:
Next steps I tried:
Flashing with an older version of Odin (v.1.85) But also failed at <ID:0/003> Complete(Write) operation failed
Flashing CF-Root v.6.4 to get the recovery mode back. Failed at <ID:0/003> Complete(Write) operation failed
Flashing Resurrection Odin CheckRom EvoHD v.4. Failed at <ID:0/003> Complete(Write) operation failed
Repartition with 20120329.pit and mx.pit. Failed at <ID:0/003> Complete(Write) operation failed
I'd still appreciate any kind of help or feedback!
It sounds like partial nand failure or simple partition corruption. Search here in q&a for solutions to repartition, but if that fails then your nand is probably toast.
try flashing a pit file
not sure if it will help but..
connect it to computer..when it fails to install drivers..Turn off and Pull battery out for few secs restart..
sometimes this helps to reinstall drivers..not sure in your case of a bootloop though?
Thanks for your answers!
I tried to repartition with a PIT-File but it didn't work.
At first I tried the GT-I9300_mx_20120329.pit with this 3-part-rom:
CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
But the same error appeared.. also the error appeared so fast I don't think there happened a repartition at all?
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Second try was 3-part-rom recommended with the mx.pit-File:
CODE_I9300XXALEF_611327_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLEF_REV02_REV04_CL1147871.tar.md5 is valid.
CSC_OXF_I9300OXFALEA_613742_REV00_user_low_ship.tar.md5 is valid.
With the same result...
It's always the same error, again and again...
Any further ideas?
you are done
Only two answers one wrong PIT or partition damaged .
Two Nand damaged see how much will a new motherboard cost .
jje
Thanks again!
With the GT-I9300_mx_20120220.pit-File I got my S3 responding for the first time since it died. It showed the blue loading-bar, but it didn't move at all and Odin stopped at <ID:0/004> NAND Write Start!!
Tried this rescue-version http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 with mx.pit but of course it didn't work..
you are done
Click to expand...
Click to collapse
seems like you're right, unfortunately..
But if you have ANY idea what I could try, please post it.
Are you sure it's a NAND damage or could it be a bootloader problem? I found this thread: http://forum.xda-developers.com/showthread.php?t=1916796 but I don't understand what they are talking about yet.
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Possible Solution
xylakant said:
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Click to expand...
Click to collapse
I had a similar problem, my phone just froze in the middle of a phone call, had to pull out battery, and when i tried to turn it on, it wouldn't pass the second "SAMSUNG" logo, just stayed there forever, with the blue light (Official JB 4.1.2 - not rooted)... Anyway, after 3 days of trying, downloaded bunch of firmwares, but all of them gave me the infamous "Complete(Write) operation failed". This is how I MANAGED to revive my i9300 16Gb Int:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
2. Click on the "Reset" button in Odin (or close and re-open it), in PDA select "recovery-cwm-touch-6.0.1.2-i9300.tar", make sure only "F.Reset Time" and "Auto Reboot" are checked, and flash it. If everything goes OK, you should now have CWM instead of Stock recovery.
3. Take any microSD card, any size, and put THIS file on the root of the microSD using a card reader or whatever you prefer - but be careful, copy the zip as it is - do not unzip it.
4. Insert the memory card in the phone, enter recovery*, and select "Install zip from External Storage" and choose the file you put on the root of the card (by the way, it's a 4.0.4 downgrade bootloader), it should flash in a second, the phone will restart, and that's it!
5. Download and flash 4.0.4 Stock FW using Odin (i used "I9300XXBLH1_OXEBLF1.zip"), everything should go OK, and the phone will be bootable again.
*(my phone didn't wanted to enter recovery the old fashioned way using 3-button combo, but i managed to enter recovery from charging mode, by connecting the charger on a switched off phone, and as soon it starts charging press Vol Up + Home + Power, and when the FIRST Logo (Galaxy S III GT-I9300) appears, let go of the power button, keep pressing the Vol Up + Home, and it enters recovery).
ATRAC3 said:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
Click to expand...
Click to collapse
Odin Stuck at "Set Partition" ^^
"<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..
Help ?
Did you give it the pit file? Pit is really a last resort AFTER you've ruled out sending for repair
Sent from my GT-I9300 using Tapatalk 4
I have the pit file and Checked the Box ^^
MrFraggii said:
I have the pit file and Checked the Box ^^
Click to expand...
Click to collapse
Correct PIT file ??? for your phone ??
Flashing PIT 99% kill the phone .
You require a service centre .
Warranty will depend upon their report .
jje
Have the right Pit file ^^ But odin Stuck at Set mapping
MrFraggii said:
Have the right Pit file ^^ But odin Stuck at Set mapping
Click to expand...
Click to collapse
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
JJEgan said:
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
Click to expand...
Click to collapse
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
tris16 said:
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
Click to expand...
Click to collapse
Your sense of entitlement is awe inspiring, if you searched and read you would find many people who flashed pit files to fix just a soft brick and then had to pay for a new motherboard.
So no, we won't help people wreck their phones.
Pit Files
tris16 said:
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
Click to expand...
Click to collapse
This is where i got mine.
http://forum.xda-developers.com/showthread.php?p=30547929
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Bump*
What makes this issue differ from others i've read on these forums, is this:
Akiiras said:
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Any theories?
As much as i hate bumping, i'm feeling kind of responsible to try and fix it. Hope someone got a clue on what might be wrong. Thanks
"I bet you 10 buck you'll get your answer here within a couple days" -a friend said, well, in norwegian though.
I guess a week later and no response means that i've at least earned 10 buck! ^^
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Akiiras said:
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Click to expand...
Click to collapse
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
LS.xD said:
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
Click to expand...
Click to collapse
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Akiiras said:
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Click to expand...
Click to collapse
BTW there are 4 different versions for nodric countries --> LINK
Odin3 v1.85 didn't work. Well, in the sense that it probably does a job well done and says everything went well, but the phone wont nudge past boot screen.
I'll see if i can learn how to do it manually and come back with the result.
Edit:
LS.xD said:
BTW there are 4 different versions for nodric countries --> LINK
Click to expand...
Click to collapse
Oh, thanks! I couldnt find it at sammobile myself, so i found it somewhere else. This could be it!
any developments?
I Have the Same Problem
I Have the same problem please anyone help me!!!!!
SOLUTION
Akiiras said:
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Click to expand...
Click to collapse
I have The solution For that remove your battery and charge battery by use of another working mobile or battery charger box
after charging you do the flashing using android 4.1.2
it successfully works on my mobile
the problem is battery is low so that at the time of flashing it turned off ....so fill the battery and use......