Related
I am hoping somebody can assist me with my Galaxy SII phone. I attempted to root it this morning and was able to connect it to Odin3Excution V1.81. The main title shows "E4GT FI27 Stock No Data". Once I connected the cell phone it generated a 0:[COM4] message. It went through all the steps but got stuck on the very last one (I believe it is the very last one) <ID:0/004> modem.bin. After waiting approximately 30 minutes, I disconnected the phone and turned it off. Once it turned in, it gave the following message "Firmware update encountered an issue. Please select recovery mode in Kies & try again".
I attempted to get into recovery mode by using all possible button combinations (volume down and power), (volume up/down and power) but I still get the same message. I started Odin again and connected the phone and it went through the same load steps but it is once again stuck on <ID:0/004> modem.bin. So at this point of time I am not sure if it is a matter of just waiting for this step to clear (however I have been 45 minutes patient and it never gets past it).
Can someone lend me a helping hand to get this issue resolved? Thanks in advance and I appreciate any assistance that can be provided. I have included an image of where I am currently stuck.
Hello guys,
I own an unlocked, unbranded SGS3 I9300 on the O2 UK network. Samsung Kies happily advised me of a new update for my phone so I went ahead and started to update. This is my first smartphone where I haven't rooted it or flashed an unofficial ROM, every ROM I have used has been downloaded and updated through Samsung Kies.
This time it failed...
It gave me a generic SGS3-I9300 error code. I turned my phone off and back on again, and it displayed the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." error. Plugged my phone back in, ran Kies, started the emergency recovery... it was taking a long time. It reached 19%. I left it for about 45 minutes and it shot up to 47%. A while later, 53% and I went to bed, leaving it on. Woke up in the morning to find that the emergency recovery had failed at 59%. So this morning I have attempted to start the recovery process again... and it has been stuck at 0% (after confirming that I wish to recover) for over 30 minutes now.
As far as I understand it my next step is to install Kies on another computer and attempt emergency recovery from there. Is that correct? If that fails or is not the next course of action, what is?
2013 has not been a great year for technology for me so far and heck, I've flashed custom ROMs, rooted and HSPL'ed all of my previous phones and cannot recall having a problem but I decide to use the official program and the official updates and this happens? Luck of the draw.
Next course of action is to install a custom recovery, and then flash a custom rom.
Seriously.
If you prefer stock though, I think there are stock roms out there which can be flashed via CWM or Odin. Should be there in the dev forums.
Try a different computer. If it doesn't work, download a stock rom and flash with Odin.
Sent from my GT-I9300 using xda app-developers app
Thanks for the help guys.
Do I need to root my SGS3 before using Odin to flash a stock rom?
So far, Odin is throwing up this error for me.
<ID:0/006> __Xmit Write fail
<ID:0/006> XmitData Fail..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've closed down anything and everything I can find relating to Kies as well as downloaded a UK language stock rom.
Elcs said:
Thanks for the help guys.
Do I need to root my SGS3 before using Odin to flash a stock rom?
So far, Odin is throwing up this error for me.
<ID:0/006> __Xmit Write fail
<ID:0/006> XmitData Fail..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've closed down anything and everything I can find relating to Kies as well as downloaded a UK language stock rom.
Click to expand...
Click to collapse
You don't need to be rooted. Can you enter recovery mode (vol up + home + power, then release power after logo comes up), then do a wipe.
Try flashing with a different pc, also run odin as an administrator.
Sent from my GT-I9300 using xda app-developers app
kofiaa said:
You don't need to be rooted. Can you enter recovery mode (vol up + home + power, then release power after logo comes up), then do a wipe.
Try flashing with a different pc, also run odin as an administrator.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Tried recovery mode but it still gives me the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" message, same as if I tried to turn it on normally.
Odin is being run as administrator. Will use a different PC.
Thanks for the help
Thanks given all-round.
Installed Odin on my dad's laptop and the USB drivers. Flash failed the first time around but swapped USB ports and it sailed through second time.
Phone seemed dead but it appears as though the battery has been wiped down to 0%. Charging for about 10 minutes, the phone booted, installed, updated, optimised and did stuff and finally got into the Android OS as I remember it pre-flash.
Not holding my breath just yet but it appears as if my phone is back in business on a Stock ROM
Elcs said:
Thanks given all-round.
Installed Odin on my dad's laptop and the USB drivers. Flash failed the first time around but swapped USB ports and it sailed through second time.
Phone seemed dead but it appears as though the battery has been wiped down to 0%. Charging for about 10 minutes, the phone booted, installed, updated, optimised and did stuff and finally got into the Android OS as I remember it pre-flash.
Not holding my breath just yet but it appears as if my phone is back in business on a Stock ROM
Click to expand...
Click to collapse
Good stuff :thumbup:
Sent from my GT-I9300 using xda app-developers app
Long story short, i wanted to install a new rom that required twrp to work correctly. i read that i could flash back and forth from twrp to cwm and vice verse just by using their respective file from each other. i downloaded the twrp zip and flashed it from cwm recovery, rebooted and phone booted. i then for some dumb reason used ClockWorkMod app and chose to reboot into recovery even though i have never had any lock using the app. ( always do my flashes manually) Now i am stuck in a loop. phone turns on, vibrates, shows samsung logo then reboots. doesn't matter how i try to turn on. ( odin download, recovery, or regular boot)
Any suggestions??
whitebrw said:
Long story short, i wanted to install a new rom that required twrp to work correctly. i read that i could flash back and forth from twrp to cwm and vice verse just by using their respective file from each other. i downloaded the twrp zip and flashed it from cwm recovery, rebooted and phone booted. i then for some dumb reason used ClockWorkMod app and chose to reboot into recovery even though i have never had any lock using the app. ( always do my flashes manually) Now i am stuck in a loop. phone turns on, vibrates, shows samsung logo then reboots. doesn't matter how i try to turn on. ( odin download, recovery, or regular boot)
Any suggestions??
Click to expand...
Click to collapse
Can you get back into twrp at all?
nope
Sounds like a stuck power button issue. Vibrates .... Samsung logo ... Black screen ... Vibrates.....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
ok so i was able to get it into odin download, but when i try to flash twrp or cwm it gets to
<ID:0/014> recovery.img
and just sits there. any thoughts?
So i left it sit all day while at work and it finally finished but failed. Below is a paste of the log. I'm gonne try to odin the stock recovery and if that doesn't work, if i can get it to dload Da_G's stock ROM. ??? Any thoughts anyone?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.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> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Repeat the process again.....
If it fails 3 consecutive times, I suggest moving to Kies for an emergency restore of the device.....g
Before you go any further, I would suggest as Bubba said, to check the power button. Sounds like it's stuck.
Edit: I also see that the latest twrp has been causing issues as well. Either way. Good luck!
I read about the latest twrp issues and im thinking that is whats causing the problems, but i have read that others have been able to fix by just flashing or odin downloading and starting over again.
I don't think the power button is stuck. When i push it, it feels normal, bounces back and everything. If it was stuck would it still mechanically operate normally? Plus i am able to get into odin download mode. Is my thinking wrong here.
I also tried the stock recovery and stock rom from Da_G and both just sat there forever and then failed but it restarted the phone so it must be communicating right?
I really miss my phone, should i be asking somewhere else?
Well...it's most likely not the power button unless that was fixed and you have a new problem. When the power button is stuck, the phone will continue to vibrate and attempt to boot.
Froid said:
Well...it's most likely not the power button unless that was fixed and you have a new problem. When the power button is stuck, the phone will continue to vibrate and attempt to boot.
Click to expand...
Click to collapse
Froid
when i try to boot normal --- vibrate, Samsung splash screen, black screen, repeat
when i try to boot into recovery --- vibrate, Samsung splash screen, black screen, repeat
when i try to boot into odin ---- vibrate, Yellow triangle screen
--- volume up --- Odin
--- volume down --- vibrate, Samsung splash screen, black screen, repeat
Stuck power button or ...?
gregsarg said:
Repeat the process again.....
If it fails 3 consecutive times, I suggest moving to Kies for an emergency restore of the device.....g
Click to expand...
Click to collapse
gregsarg
i can't use kies cause i can't boot the phone right? or am i miss understanding how kies works.
You can use Kies in download mode and do a firmware upgrade. It sounds like you wiped your OS. You should be able to use the stock Odin tar to recover. I would grab a fresh download and try again. If all else fails, use Kies in download mode and do an emergency firmware flash(or whatever it's called)
kies won't connect to my phone in download mode either. i tried re installing drivers, i went through the kies connection error troubleshooting stuff. i hate to think it is something to do with my pc because i know i have connect to it before when i first got the phone and rooted it. maybe I'll try using the laptop tomorrow. any other ideas please keep them coming. I'll make a nice donation to the one who comes up with something that works.
It won't connect while in download mode like it does when booted normally. It will just continue trying to connect from what I remember. Make sure you grab the phone info behind the battery. I think it needs the model and S/N. Then do an emergency recovery. Been a while but I think it needs to be all caps as well when you enter the info.
Froid said:
It won't connect while in download mode like it does when booted normally. It will just continue trying to connect from what I remember. Make sure you grab the phone info behind the battery. I think it needs the model and S/N. Then do an emergency recovery. Been a while but I think it needs to be all caps as well when you enter the info.
Click to expand...
Click to collapse
Agreed.....this is the logical next step....g
whitebrw said:
kies won't connect to my phone in download mode either. i tried re installing drivers, i went through the kies connection error troubleshooting stuff. i hate to think it is something to do with my pc because i know i have connect to it before when i first got the phone and rooted it. maybe I'll try using the laptop tomorrow. any other ideas please keep them coming. I'll make a nice donation to the one who comes up with something that works.
Click to expand...
Click to collapse
Had something similar happen about a week ago or so. Only difference is mine completed the process after reconnecting to odin and re-did the CWM, was all good afterwards. I know it's probably been mentioned but just trying to help. If you can get into factory recovery or download mode, do it, connect to Odin, follow the steps exactly as when you first rooted your phone, no need to install the super user if it's something you already installed previously, do it up until it says passed and unplug from the computer, your device should re-boot, fingers crossed. You more than likely already know what to have checked in odin and what not to have checked. Delete/Un-Install the TWRP newest update and go with I think it is 2.3. something. It helped me, maybe you, I'll keep my fingers crossed for you as well.
Thanks Everyone!
Thanks for all your help and suggestions. I have been trying kies for the last couple days to no avail. (which i wouldn't have even got started if it wasn't for Froid's all caps hint, small donation sent your way for that). But in the end it was my PC, i hooked up to the laptop and bam, first try. Grrr damn windows drivers, i keep threatening to kick windows to the curb, but then again i have paid a dime for any version since 3.1. LOL
Thanks again!
Thank you for the donation. I'm glad you got it all worked out. We're all happy to help(for free) ...Thanks again man...much appreciated.
Froid said:
Thank you for the donation. I'm glad you got it all worked out. We're all happy to help(for free) ...Thanks again man...much appreciated.
Click to expand...
Click to collapse
Gun to the head *Gimme the cash*
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Okay, so this is my story. I had cm11 m8. Everything was fine until, two days ago, he turned off. I tried powering on but nothing - bootloop. I entered cwm to make backup and reinstall it. When I tried, it showed error: can't backup /data or something like that. But that is the point where it would stop. Then I tried flashing CWM through Odin but that failed. It started processing zImage, wrote NAND write start and after some time it reported error: Complete(Write) Operation failed. All threads completed (succeed 0 / failed 1). I disconnected my phone and pressed the power button to try and go to CWM and reinstall ROM. But this time, CWM was gone. So I was stuck with only download mod available. I tried again in Odin, this time to flash stock rom but again, the same error appeared. I tried several times but nothing. But Samsung logo was lost and "firmware upgrade encountered an issue.." screen appeared. I tried to intall Kies but it won't start. At startup it displays an fatal error. Tried flashing the .pit file again, same error poped up. Then I tried downloading GB rom with .csc, .pit, kernel and rom files to flash them all together. But, once again, it showed the same error. But I got the Samsung logo screen back, only this time without roor.
Please, but please can someone help me with this?
Hello, i have a Samsung Galaxy S2 phone, got it from guy for 5$, cause it's not turning on.
Bringed it back home, plugged in into A/C and saw, that it only boots in Recovery mode. Tried to install custom .zips, doesn't work, shows errors. Tried to connect it to PC in Download mode, got many problems, drivers, Kies.... Finally i've managed Odin to find my phone only in that method: put battery out of phone, killed Kies.exe process, put the cable into phone, battery in with Volume Down button pressed, and vuola, Odin found it, but.....
When i tried to install 2 stock firmwares, there's what Odin shows:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And it fails.. I've tried two different computers, two different cables (one is original, one is different), changed USB ports, did everything.. So i'm asking for help, thanks for reading.
Lukitauskas said:
Hello, i have a Samsung Galaxy S2 phone, got it from guy for 5$, cause it's not turning on.
Bringed it back home, plugged in into A/C and saw, that it only boots in Recovery mode. Tried to install custom .zips, doesn't work, shows errors. Tried to connect it to PC in Download mode, got many problems, drivers, Kies.... Finally i've managed Odin to find my phone only in that method: put battery out of phone, killed Kies.exe process, put the cable into phone, battery in with Volume Down button pressed, and vuola, Odin found it, but.....
When i tried to install 2 stock firmwares, there's what Odin shows:
And it fails.. I've tried two different computers, two different cables (one is original, one is different), changed USB ports, did everything.. So i'm asking for help, thanks for reading.
Click to expand...
Click to collapse
Is the stock rom you've downloaded corrupted? There might be a problem with the nand chip on your phone.
gsstudios said:
Is the stock rom you've downloaded corrupted? There might be a problem with the nand chip on your phone.
Click to expand...
Click to collapse
I don't think it's corrupted, i've tried few different roms. What is NAND CHIP? It is repairable thing, or should i put that phone in recycle bin? :crying: