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.
Related
Big problem...
After flashing 9.3 on SGS2 without wiping i rebooted in cwm and flashed siyah 2.6.2.
After that the phone stuck on the omega logo and did not boot.
I rebooted into CWM wiped cache/davlic etc and i tryed to reflash the 9.3 and the siyah.
After that i tryed to flash the kernel but the phone restarted itself and since then it doesnt boot at all neither in CWM or into android.
Only in download mode and it's not recognized by ODIN or kies.
ODIN:
ID:0/003> Added!!
<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> zImage
<ID:0/003> NAND Write Start!
Kies: The device is not responding.
BUT windows is recognizing the phone in devices.
What should i do?
IF i try to turn it on it appears a phone-triangle-pc logo and nothing happens after that.
angelossssss said:
Big problem...
After flashing 9.3 on SGS2 without wiping i rebooted in cwm and flashed siyah 2.6.2.
After that the phone stuck on the omega logo and did not boot.
I rebooted into CWM wiped cache/davlic etc and i tryed to reflash the 9.3 and the siyah.
After that i tryed to flash the kernel but the phone restarted itself and since then it doesnt boot at all neither in CWM or into android.
Only in download mode and it's not recognized by ODIN or kies.
ODIN:
ID:0/003> Added!!
<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> zImage
<ID:0/003> NAND Write Start!
Kies: The device is not responding.
BUT windows is recognizing the phone in devices.
What should i do?
IF i try to turn it on it appears a phone-triangle-pc logo and nothing happens after that.
Click to expand...
Click to collapse
1) Get the right CF Kernel from the Chainfire kernel thread in the Android Original Development Thread. Extract the zip to get a TAR and extract the TAR to get a z-image file. Also download the corresponding original stock kernel from the Intratech thread in the same section.
2) Flash the TAR in PDA using Odin. Do not click repartition. This lets you boot with with functional Root and CWM.
3) If you want to get rid of the yellow triangle, then load the z-image file into /sdcard. Reboot into download mode and use Odin to flash the stock kernel (again in the PDA without repartition). After that, go to the CWM app, choose flash kernel and locate the zimage and proceed.
NB: You can read Chainfire and Intratechs threads in case I was vague somewhere.
Thanks mate but i already know and did all these.
The thing is what i do in order to bring my phone back to life.
What is 9.3 you flashed ???
Kies: The device is not responding.
Why are you using KIES to flash a rom is it open and preventing Odin from working .
jje
Are you saying Odin does it doesn't recognise your phone?
In the past Odin flashing has gone wrong and can usually be fixed by a PC reboot or rebooting into download mode again.
Sent from my GT-I9100
9.3 = Omega 9.3 rom.
No i'm not.
I installed kies to see if the phone is recognized. After i realized that it's not i uninstalled the kies.
The thing is that odin sees my phone but stacks at <ID:0/003> NAND Write Start!
With 115 posts no reason for you not to ask in the rom thread as its possible its rom specific .
Dont think it is but worth a try .
Choices try Odin on another PC .
Take phone to service centre and hope it is not an expensive repair .
Buy a JTag machine .
jje
Just tryed odin on another pc and i got the same result...
i had the same problem and tried flashing the PIT thinking it might do something, but ended up fully bricked. couldnt power on anymore. only way is to JTAG it now, if odin cant flash it.
read this thread maybe it can help
http://forum.xda-developers.com/showthread.php?t=1382838&highlight=unbrick
angelossssss said:
9.3 = Omega 9.3 rom.
No i'm not.
I installed kies to see if the phone is recognized. After i realized that it's not i uninstalled the kies.
The thing is that odin sees my phone but stacks at <ID:0/003> NAND Write Start!
Click to expand...
Click to collapse
Were you flashing using Odin without Kies installed? As far as i'm aware Kies must be installed but not running to flash with Odin.
Nothing worked
The phone is off to Samsung service.
Thanks for your help people.
Dear friends,
I think i soft bricked my phone and i do not know what to do.
First i was on 2.3.6 (GB) Sensation N ROM (2.0). Then i desided to go for a stock ICS (4.0.4) and downloded I9100XWLPM (4.0.4) and flashed it with Odin (only PDA file). The flash was sucessfull but i didnt like to experiance of 4.0.4 (i was unable to reach my contacts through the numpad - phone.apk force closes) and i decided to go back to Offical GB (2.3.6) firmware. I flashed with Odin
GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2 firmware and the flash was suceful. But after restart it gives me force closes on the first boot screen (Google Services framework, Softaware update aplocation) and self restarts and then the same again.
Then i flashed with Odin the "new" GB Bootloader GT-I9100 and the same file again but the result was the same. And then something hapened and i did not manage to flash any more with Odin (flash unsucessful ).
So then i flashed again with the follwing PIT file (i9100_u1_02_20110310_emmc_EXT4-stock.pit) and the
PDA (GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2.tar.md5) and the flash was sucesfull but i have the same problems with the force closes on the first boot screen.
I am out of ideas and do not know how to proceed.
Any help will be apreciated!
hristo2000 said:
Dear friends,
I think i soft bricked my phone and i do not know what to do.
First i was on 2.3.6 (GB) Sensation N ROM (2.0). Then i desided to go for a stock ICS (4.0.4) and downloded I9100XWLPM (4.0.4) and flashed it with Odin (only PDA file). The flash was sucessfull but i didnt like to experiance of 4.0.4 (i was unable to reach my contacts through the numpad - phone.apk force closes) and i decided to go back to Offical GB (2.3.6) firmware. I flashed with Odin
GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2 firmware and the flash was suceful. But after restart it gives me force closes on the first boot screen (Google Services framework, Softaware update aplocation) and self restarts and then the same again.
Then i flashed with Odin the "new" GB Bootloader GT-I9100 and the same file again but the result was the same. And then something hapened and i did not manage to flash any more with Odin (flash unsucessful ).
So then i flashed again with the follwing PIT file (i9100_u1_02_20110310_emmc_EXT4-stock.pit) and the
PDA (GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2.tar.md5) and the flash was sucesfull but i have the same problems with the force closes on the first boot screen.
I am out of ideas and do not know how to proceed.
Any help will be apreciated!
Click to expand...
Click to collapse
install a custom kernel like siyah through download mode.....go to recovery and do a full wipe .....clear dalvik-cache and reboot
you should of posted it in the QA thread, its not bricked, just needs a proper format
http://forum.xda-developers.com/forumdisplay.php?f=1148
mysterio619 said:
install a custom kernel like siyah through download mode.....go to recovery and do a full wipe .....clear dalvik-cache and reboot
Click to expand...
Click to collapse
Ok, i flashed Siyah-v3.3.3d.tar (i load it as PDA in Odin) but the flash was unsucessful:
Here is the log:
<ID:0/009> Added!!
<ID:0/009> Removed!!
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What shoud i do?
do u having kies installed by chance? update the Samsung driver again.. if u using win 7 then run running Odin as admin..try every possible way
Prashanthme said:
do u having kies installed by chance? update the Samsung driver again.. if u using win 7 then run running Odin as admin..try every possible way
Click to expand...
Click to collapse
Hi,
I did everything. I uninstalled KIES. I installed again the USB drivers. I restarted the PC. I ran Orin (v1.85) as administrator and flashed. Flash froze at SetupConnection..(1 hour) Here is the log:
.<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I give up. I will call my provider to fix the phone.
I will keep all of you posted for what hapened!
hristo2000 said:
Hi,
I did everything. I uninstalled KIES. I installed again the USB drivers. I restarted the PC. I ran Orin (v1.85) as administrator and flashed. Flash froze at SetupConnection..(1 hour) Here is the log:
.<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I give up. I will call my provider to fix the phone.
I will keep all of you posted for what hapened!
Click to expand...
Click to collapse
offfff....i did it......i removed the battery and then went again in download mode and managed to flash the kernel........:laugh:
...it looks like that the download mode was struck...
thank a lot!
Hello,
I've pretty much exhausted all my brainpower trying to figure this one out. I have an I9305 S3 which I am trying to root, I have all the correct drivers installed and Odin v3 shows blue COM4 ID box. When flashing anything, I get this:
<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
Click to expand...
Click to collapse
Then it gets stuck and does nothing. I tried to flash CWM recovery first, and it would say this:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
Click to expand...
Click to collapse
So it appears it tries to flash boot.img or recovery.img but gets stuck. Unplugging the phone and rebooting shows everything to be working and still stock, in other words nothing really happens.
Tried several methods, both using Odin3 v1.87 and v3.07 directly, and via the Galaxy S3 Toolkit, also tried flashing various packages in the S3 Toolkit as well as pre-rooted firmware, all with the same result. Tried uninstalling all Samsung drivers and then installing via the Toolkit. Never installed Kies before but I tried installing Kies and letting it install drivers, then using Odin, still same result. Can anyone help?
DkNINJA said:
Hello,
I've pretty much exhausted all my brainpower trying to figure this one out. I have an I9305 S3 which I am trying to root, I have all the correct drivers installed and Odin v3 shows blue COM4 ID box. When flashing anything, I get this:
Then it gets stuck and does nothing. I tried to flash CWM recovery first, and it would say this:
So it appears it tries to flash boot.img or recovery.img but gets stuck. Unplugging the phone and rebooting shows everything to be working and still stock, in other words nothing really happens.
Tried several methods, both using Odin3 v1.87 and v3.07 directly, and via the Galaxy S3 Toolkit, also tried flashing various packages in the S3 Toolkit as well as pre-rooted firmware, all with the same result. Tried uninstalling all Samsung drivers and then installing via the Toolkit. Never installed Kies before but I tried installing Kies and letting it install drivers, then using Odin, still same result. Can anyone help?
Click to expand...
Click to collapse
try to flash use mobile odin by chainfire
this more safety way
hrcell said:
try to flash use mobile odin by chainfire
this more safety way
Click to expand...
Click to collapse
I can't since I can't get root on my phone.
Just fixed it. After all this time it appears to be a USB port / driver issue. I had a Galaxy S3 I9300 previously and I think there were some conflicts, I switched to a new USB port and everything finished without an issue. Interesting side note, I suspected the problem because when I plugged in the I9305 and tried to copy files to the phone, it gets stuck for any files over a couple of MB in size. I plugged in my old S3 (I9300) and there were no problems. Changing the I9305 to a new port fixed everything.
Hi guys, forgive me about my bad english but i'm not english....ok, let's start with my problem.
Today i want to clean my gs3 because i want to make it return to standard condition (i had a 4.2.2 rom). So i follow a guide of an italian android forum (yes i'm italian) to make a deep clean. The problem is now, when i try to flash a stock rom with odin. I put the phone in download mode (in the counter i have only 2), odin recognize it and i press start, but the process stop and says this
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
the nand write fail, i think. I've tried a lot of thing, such as change pc or change cable, but always the same error. At least i try with the pit procedure, but always the same error. I can only enter in download mode rigght now, and when i swich on the phone normally it says "firmware upgrade encoutered an issue, Plese select recovery mode in Kies and try again.
I try the way by kies, but it didn't recognise the phone.
Plese, help me, i'm desperate....
what phone model? what file
Glebun said:
what phone model? what file
Click to expand...
Click to collapse
i have the gt-i9300 no brand and for the stock rom i use this I9300XXALE8_I9300OJVALE7_OJV
trasposone said:
i have the gt-i9300 no brand and for the stock rom i use this I9300XXALE8_I9300OJVALE7_OJV
Click to expand...
Click to collapse
nobody can help me? this is a very big problem, i need my s3,please i'm desperate
you can't bump your thread more than once every 24 hours, it's against the rules.
if you flashed a pit file, you need to send it to ser
trasposone said:
nobody can help me? this is a very big problem, i need my s3,please i'm desperate
Click to expand...
Click to collapse
Seeing as your firmware is pre-sds fix, you may have a damaged nand, ....try both these.
Can you boot into stock recovery?
Can you boot into download mode?
slaphead20 said:
Seeing as your firmware is pre-sds fix, you may have a damaged nand, ....try both these.
Can you boot into stock recovery?
Can you boot into download mode?
Click to expand...
Click to collapse
As well as slappy's suggestion, also post what it says for 'product name' when in download mode (if you can boot into download mode)..
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.