Hello XDA,
i have an S3 international that i havent used since some time, and when i gave it to my brother he messed up with it until finally it gives "Firmware Upgrade Encountered an Issue Please select recovery mode in Kies & try again"
i have searched a lot and tried all possible solutions( note: i've forgot what android was used but its supposed to be 4.1 or 4.2)
i have tried all possible kies and smart switch, it reaches to the end of process and says upgrade failed due to an unexpected error (give a recovery code blank space that cant be written to it) and nothing happens as if it was canceled.
i have tried flashing using odin , android 4.3 repair firmware different regions with different .pit, i even tried flashing the pit alone but i get no pit partition and fails quickly
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
one flash of a .tar AP file gave this but failed:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
what am i supposed to do ? is it 100% damaged? no way to be fixed, how is it possible that there is no fix for such a thing.. i mean i want to format it completely i dont care for the data.. why havent samsung developed a tool that can fix this things? all tools developed like kies smart switch and others work for some times then they dont support the phone models after some time..
You're using the latest stock firmware from sammobile.com or updato.com with Odin?
Tried different USB cables and USB ports?
audit13 said:
You're using the latest stock firmware from sammobile.com or updato.com with Odin?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
yes i've tried different usb cables , i tried different ports.. samsung kies always reach at the end of upgrade and then say failed due to an unexpected error
tried download all sort of firmwares, different regions, also repair firmware containing (AP,CSC...) but always fail in odin.
most fail says no pit partition ( which i tried to download different pit files and none worked)
another fails at NAND write ( which i tried to rebuild the .tar file and it passed the nand write but then it fails again at cache.img)
There should be no need to flash the stock firmware separately. The firmware from sammobile.com is unzipped once to create a tar.md5 file for flashing in AP/PDA.
I often get the pit error when using a non-Samsung OEM USB cable.
audit13 said:
There should be no need to flash the stock firmware separately. The firmware from sammobile.com is unzipped once to create a tar.md5 file for flashing in AP/PDA.
I often get the pit error when using a non-Samsung OEM USB cable.
Click to expand...
Click to collapse
i've downloaded several firmwares 4.1.1 & 4.1.2 & 4.3 and tried different regions for each..
i am also getting this error in some of them
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
It's possible that the memory chip inside the phone is damaged. You may have to take it to a cell repair shop to see if they can force flash it via tag.
Related
Hi, after trying out some custom roms like CM9-10 and Omega my phone suddenly started rebooting. It lets me enter the PIN and starts up but after a qouple of seconds it reboots again.
The wierd part is that it autostarts after I insert the battery, but I can enter both CWM and Download mode.
I have tried enter CWM and do a wipe but phone reboots in the middle of the process, same goes when trying to flash CM9 or any other rom I have on the internal SD.
I have also tried following a Swedish guide to restore it to stock using Odin, but after adding the PDA and pressing start I get a Fail in Odin to, something about NAND write fails.
Does anyone have a solution for me? Should I tick re-partition or do something other in Odin?
I would suggest boot into recovery. Wipe Dalvik cache. Flash Rom. Wipe both caches. reboot.
Sent from my GT-I9300 using xda premium
Do you have international galaxy s3 (gt-i9300)?
jnr21 said:
Do you have international galaxy s3 (gt-i9300)?
Click to expand...
Click to collapse
Well I think so, it was sold in Sweden.
The problem is that it reboots doing most of the actions in CWM, I think I have managed to wipe Dalvik but as soon as I try to install a rom it just reboots.
I also tried rooting again using Odin 1.85 but it fails with that version too.
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
burton6666 said:
Well I think so, it was sold in Sweden.
The problem is that it reboots doing most of the actions in CWM, I think I have managed to wipe Dalvik but as soon as I try to install a rom it just reboots.
I also tried rooting again using Odin 1.85 but it fails with that version too.
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
If all else fails get yourself a S3 USB Jig. I bought one, funnily enough it arrived today from Hong Kong and it only cost something like 2,50€ delivered free. Then install a stock rom.
burton6666 said:
Hi, after trying out some custom roms like CM9-10 and Omega my phone suddenly started rebooting. It lets me enter the PIN and starts up but after a qouple of seconds it reboots again.
The wierd part is that it autostarts after I insert the battery, but I can enter both CWM and Download mode.
I have tried enter CWM and do a wipe but phone reboots in the middle of the process, same goes when trying to flash CM9 or any other rom I have on the internal SD.
I have also tried following a Swedish guide to restore it to stock using Odin, but after adding the PDA and pressing start I get a Fail in Odin to, something about NAND write fails.
Does anyone have a solution for me? Should I tick re-partition or do something other in Odin?
Click to expand...
Click to collapse
If your Nand is corrupt i dont think you can get out of it......99 percent of the time if you can get into download mode your good. but if you having Nand Write issues, i dont know if there is a coming back from that.
hope thats not the case and another member can shed some better light on the subject.
Nand. See posts regarding. PIT today.
jje
Sent from my GT-I9300 using xda premium
JJEgan said:
Nand. See posts regarding. PIT today.
jje
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Could you post a link to that thread? I found this one and have tried flashing some of the PIT-files but it does not work. Or should I flash some other files at the same time?
Ok, following one guide witch seams to fix my problem is that I need a 3-part firmware. Every Firmware I have downloaded contains:
boot, cache, hidden, modem, recovery, system -if I extract them one extra time. Is that right? Where should I load them in odin in that case? If not could anyone direct me to a download-page for 3-part firmwares? (I downloaded the last one from samfirmware.com)
It is very strange that the core functions kind of work as I can boot normaly into the system and even run an app if I am fast, then reboot.
Downloadmode works untill I try to flash something.
CWM works until I try to do a Wipe or flash a rom, I can wipe dalvik and some other stuff, but not cache, data and some other. I noticed that You could partition sdcard from CWM should I try that? and if so what should i select in the next screen about partition size?
Guys help..
I was trying to get my phone back to basic and I tried to install an official firmware by using odin 3, and it failed..
Now I am stucked???
My phone failed and know its saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again"
What to to??
what does the log say?
Glebun said:
what does the log say?
Click to expand...
Click to collapse
log???
yes, the Odin log.
Sivasli_ said:
Guys help..
I was trying to get my phone back to basic and I tried to install an official firmware by using odin 3, and it failed..
Now I am stucked???
My phone failed and know its saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again"
What to to??
Click to expand...
Click to collapse
Before flashing, make sure you have all necessary drivers installed and that you have more than 50% (30% is the absolute minimum) of battery left. Then download a ROM (I.e. from sammobile.com/firmware) and make sure that is is the right ROM for your device. If you download something that is for a different device, you may end up bricking it.
Then boot your phone into Odin mode (I think you know how to do that?) and connect the phone to your PC. Wait for the PC to recognize the device as a serial CDC (That's what Windows 7 and Vista usually show) and then wait for Odin to recognize the device. Then (If you have not already) load all the files into Odin (PDA - ROM and kernel, Modem - Phone, CSC - CSC) and hit "Start".
Then it should download fine. If you are still having trouble, feel free to PM me and I'll gladly help via TeamViewer
Lg
Sound to me like Kies was running in the background while you made the Odin flash.....you must disable Kies before using Odin
No Kies was not running in the backgorund..
Could it be, because I was going from 4.1.2 down to 4.0.1 for example? It is a old firmware..
I solved my problem with installing an Omega Rom v43, but I still want to back to original firmware..
what does the log say?
I dont now how to look at the log..
Can I just flash the original firmware even that I am on a Omega firmware?
Glebun said:
what does the log say?
Click to expand...
Click to collapse
Here is what the log says..
<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> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> sboot.bin
<ID:0/004> system.img
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
Sivasli_ said:
No Kies was not running in the backgorund..
Could it be, because I was going from 4.1.2 down to 4.0.1 for example? It is a old firmware..
I solved my problem with installing an Omega Rom v43, but I still want to back to original firmware..
Click to expand...
Click to collapse
The new 4.1.2 bootloader (I assume you have it, unless you specifically replaced it with the older one) will blacklist older bootloaders and prevent them from being installed. This might be part of the problem.
hello,,
i have a problem with my galaxy s3 GT-I9300
the problem is that i flashed MIUI and it worked perfectly .. after that restarted my device and it repeat restarting.
so i got to recovery mode and it failed to flash any zip file. and failed to wipe to factory reset and failed to wipe data.
i was on CWM touch 5.0.5 but someone here adviced me to flash Philez Touch and after that i couldn't access recovery anymore
i tried to flash from odin a stock rom
Code:
I9300XXELLB_I9300OJVELL3_I9300XXELLA_HOME.tar.md5
and here is the result
Code:
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Download screen says the following
Code:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: YES (5 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Downloading..
this is all i have .. please help me
thanks in advance
not SDS. probably some kinda loose connection of usb. happened to me many times! tried all the ports?
sent from GS3 running MOKEE CM10.1 NIGHTLY RC3
sriram231092 said:
not SDS. probably some kinda loose connection of usb. happened to me many times! tried all the ports?
sent from GS3 running MOKEE CM10.1 NIGHTLY RC3
Click to expand...
Click to collapse
tried all ports.
killed all samsung kies processes.
the problem is that i flashed a recovery file and it works but when flashing any rom it stuck !!!
Same answer nand damaged take to a service centre .
jje
JJEgan said:
Same answer nand damaged take to a service centre .
jje
Click to expand...
Click to collapse
flashing
Code:
recovery-cwmtouch-6.0.3.2-GTI9300.tar
result to successful
Code:
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
Have you tried flashing with separate files and pit file ? This should rewrite your partitions. Such "more parted" can be found here on XDA or sammobile.
Sent from my GT-I9300 using xda premium
JJEgan said:
Same answer nand damaged take to a service centre .
jje
Click to expand...
Click to collapse
ground-zero said:
Have you tried flashing with separate files and pit file ? This should rewrite your partitions. Such "more parted" can be found here on XDA or sammobile.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
can you please provide me the link
thanks
eng.helewa said:
can you please provide me the link
thanks
Click to expand...
Click to collapse
Follow the steps in this thread.
If boots, then good, if not, then try flashing an ICS firmware. Download from Sammobile.
eng.helewa said:
can you please provide me the link
thanks
Click to expand...
Click to collapse
hey guys
i have flashed a rom finally though odin .. but the device still restarting and can't reach recovery mode
The NAND stuck problem caused by improper pit file .. i changed my pit file and it worked.
but why it still restarting ?!
here is what i did: flashed
Code:
[B]The ROM:[/B] I9300XXELLB_I9300OJVELL3_I9300XXELLA_HOME.tar.md5
[B]The PIT FILE:[/B] M0_20120220.pit
Note that the rom wont flash without the pit file
I had a similar problem with my I9305, would die at 23% of system.img. Fixed by re-flashing using Heimdall - after that, Odin also works again. Apparently a bug in Odin.
(However, in my case, the problem was not caused by repartitioning, nor did I need a PIT file to fix it.)
Sent from my GT-I9305 using xda app-developers app
eng.helewa said:
hey guys
i have flashed a rom finally though odin .. but the device still restarting and can't reach recovery mode
The NAND stuck problem caused by improper pit file .. i changed my pit file and it worked.
but why it still restarting ?!
here is what i did: flashed
Code:
[B]The ROM:[/B] I9300XXELLB_I9300OJVELL3_I9300XXELLA_HOME.tar.md5
[B]The PIT FILE:[/B] M0_20120220.pit
Note that the rom wont flash without the pit file
Click to expand...
Click to collapse
Have you flashed a firmware with single CSC, modem, code files ? When you make a repartition this is necessary. And you can try an other Odin vetsion. I use permanently 1.84 or change to Heimdall.
Hope this works !
Sent from my GT-I9300 using xda premium
Hi all,
I need help to fix the S3 that i have here, model GT-I9300, I don't know what happened but I cant boot the phone it is stuck at Galaxy S3 screen, I can enter in recovery and Download mode but I am not being able to flash anything using Odin and KIES also does not work, what I have tried:
Flash stock room using Odin;
Flash TWRP Using Odin;
Update firmware using KIES, I do put the model and serial number but the KIES give a message that is not possible to start the process;
Odin fails in anything that I tried to flash:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1101)..
<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> recovery.img
<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)
If I enter in the recovery mode i saw a lot of red messages saying that is not possible to mount E: bla bla.
Any help Is appreciated.
Looks like a SDS
MGSGS said:
Looks like a SDS
Click to expand...
Click to collapse
I googled for it and seems that there is no fix for it... so, good bye
Tried different USB cables and ports?
audit13 said:
Tried different USB cables and ports?
Click to expand...
Click to collapse
Yes, also different computers, I think that it is a sds
Confirmed the model # in download mode? Using the latest stock ROM from sammobile.com?
audit13 said:
Confirmed the model # in download mode? Using the latest stock ROM from sammobile.com?
Click to expand...
Click to collapse
Yes, also tried to flash twrp, stock recovery, everything fails....
hey guys,
I don't have a recovery mode (getting white screen instead). only download mode.
I downloaded the correct firmware and tried install and it failed (in system.img) and requested a PIT file.
I downloaded the PIT file and it got failed again.. I tried to install this twrp thing and still not good.
This is what I get when I try to install pit + twrp (auto reboot, re-partition and f. reset time are checked):
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
Edit:
I've tried with the nand checked aswell and got this:
<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> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea?
Thank you guys!
Have you tried different cables, are you using a USB port on the motherboard?.
The drivers work because it sees the phone in odin.
Are you loading the stock firmware AND the pit file at the same time?.
If you can answer yes to all of those then it's a bin job.
I don't recommend trying to flash a pit and TWRP at the same time. I only recommend using a pit file, when necessary, with stock firmware.
shivadow said:
Have you tried different cables, are you using a USB port on the motherboard?.
The drivers work because it sees the phone in odin.
Are you loading the stock firmware AND the pit file at the same time?.
If you can answer yes to all of those then it's a bin job.
Click to expand...
Click to collapse
Yes, tried a different cable.
Yes, I used a USB port on the motherboard
Yes it's a stock, and tried separately and didn't work.
Damn
audit13 said:
I don't recommend trying to flash a pit and TWRP at the same time. I only recommend using a pit file, when necessary, with stock firmware.
Click to expand...
Click to collapse
I tried to use only the pit but all i get is that error. It didn't matter if I used a TWRP / stock firmware.
Don't flash using only the pit file.
Flash twrp or stock ROM without pit.
If flashing the stock firmware on its own fails or it says about a pit partition in odin then load both the pit file and the stock firmware at the same time. If it fails to flash them you can safely assume the phone has a corrupt nand and is dead.
You can also try flashing older versions of the recovery, twrp or cwmr. The last official cwmr was the most stable for me and helped me recover from a f*ked twrp that caused the e:failed to mount errors.
If it can take a flash of any type it might be recoverable. Just because it fails a flash doesn't mean its dead dead, just borked beyond the usual capability of the average Joe bloggs..
I would recommend, just for the fact it can't get any worse than what it already is, find the stock firmware in separate files along with the last official cwmr and flash them one by one and when you get the fail errors you'll know exactly what part of the nand is faulty. Basically just mess with it until you kill it. If it jumps into life in the meanwhile then you got lucky and should put a ticket on the lottery!.
Hope this helps inspire a bit of confidence!.
audit13 said:
Don't flash using only the pit file.
Flash twrp or stock ROM without pit.
Click to expand...
Click to collapse
I tried it, didn't manage to succeed.
shivadow said:
If flashing the stock firmware on its own fails or it says about a pit partition in odin then load both the pit file and the stock firmware at the same time. If it fails to flash them you can safely assume the phone has a corrupt nand and is dead.
You can also try flashing older versions of the recovery, twrp or cwmr. The last official cwmr was the most stable for me and helped me recover from a f*ked twrp that caused the e:failed to mount errors.
If it can take a flash of any type it might be recoverable. Just because it fails a flash doesn't mean its dead dead, just borked beyond the usual capability of the average Joe bloggs..
I would recommend, just for the fact it can't get any worse than what it already is, find the stock firmware in separate files along with the last official cwmr and flash them one by one and when you get the fail errors you'll know exactly what part of the nand is faulty. Basically just mess with it until you kill it. If it jumps into life in the meanwhile then you got lucky and should put a ticket on the lottery!.
Hope this helps inspire a bit of confidence!.
Click to expand...
Click to collapse
Hahaha thanks mate, I guess I'll just give up and deliver this phone the place it belongs - hell!
Thanks for the help tho, It will be easier to win the lottery as you wrote