Hi guys, last night i was trying to root my galaxy s2 and i realized while my phone was trying to flash recovery.tar i hadnt unzipped the file yet. so my galaxy s2 was in download mode forever until i decided to just pull the battery out and turn on my phone, now my phone goes to a screen that says:
odin mode
product name: t989
custom binary download: no
current binary: samsung official
(mobile)--!--(PC)
"Firmware upgrade ecountered an issue. please select recovery mode in Kies & try again."
is there any way i can restore my phone to normal? maybe a usb jig can help??
I would try what it says to do.
drivinfast247 said:
I would try what it says to do.
Click to expand...
Click to collapse
ive tried connecting my device, but even then it doesnt read . Any other suggestions?
some help would be great
Firmware update failure via Kies
Hello everyone!
I was trying to update my SGSII GT-I9100 (Gingerbread) to ICS 4.0.4 via Kies. Kies worked well during the downloading part and then it got stuck with nill progress while installing. I had no other option than to disconnect. And now when I switch on the phone it says:
(mobile)--!--(PC)
"Firmware upgrade ecountered an issue. please select recovery mode in Kies & try again."
I connected the phone again and my desktop is not recognizing it anymore.
What I get from all this is that there is no Stock firmware or something like that and the phone can go into download mode only.
Can anyone help?
shahrozeumar said:
Hello everyone!
I was trying to update my SGSII GT-I9100 (Gingerbread) to ICS 4.0.4 via Kies. Kies worked well during the downloading part and then it got stuck with nill progress while installing. I had no other option than to disconnect. And now when I switch on the phone it says:
(mobile)--!--(PC)
"Firmware upgrade ecountered an issue. please select recovery mode in Kies & try again."
I connected the phone again and my desktop is not recognizing it anymore.
What I get from all this is that there is no Stock firmware or something like that and the phone can go into download mode only.
Can anyone help?
Click to expand...
Click to collapse
Just so you know as this is your first post I would like to say welcome now moving forward this issue is quite rampid on the web and honestly if you did a little searching you would of found a crap load of things to try. First thing I would tell you is since you can get into download mode is download Odin and flash stock firmware back on your phone. In your forum there has to be a restore to stock thread and this is what I would look for first
Whoa GT-I9000?
Totally diffrent device, and wrong forum. Your on your way to HARD Bricking your phone if you don't find the correct forum. Believe me I know from past Experiences .
@MickeyCobra
Is your computer recognizing your phone? If not try this things:
Uninstall Drivers
Connect phone to computer with phone in download mode, and let Windows Auto-Search the Drivers
Recovered finally
playya said:
Just so you know as this is your first post I would like to say welcome now moving forward this issue is quite rampid on the web and honestly if you did a little searching you would of found a crap load of things to try. First thing I would tell you is since you can get into download mode is download Odin and flash stock firmware back on your phone. In your forum there has to be a restore to stock thread and this is what I would look for first
Click to expand...
Click to collapse
Yeah, I got it fixed via recovery mode in Kies. I would suggest never try Kies for upgrading firmware, as it gets disconnected in between !
Thanks
---------- Post added at 06:13 AM ---------- Previous post was at 06:08 AM ----------
DroidDonX said:
Whoa GT-I9000?
Totally diffrent device, and wrong forum. Your on your way to HARD Bricking your phone if you don't find the correct forum. Believe me I know from past Experiences .
@MickeyCobra
Is your computer recognizing your phone? If not try this things:
Uninstall Drivers
Connect phone to computer with phone in download mode, and let Windows Auto-Search the Drivers
Click to expand...
Click to collapse
Recovered finally. Now I am having ICS 4.0.4 on my phone.
I had a similar issue with my T989. When I was flashing back to a stock rom through Odin, the connection between my phone and computer got disrupted. I received the error and was told to upgrade the firmware through Kies. I tried to reinstall the stock rom through Odin, and kept getting a failed installation. So I tried again and again and finally it went through. I prefer to keep away from Kies.
i was trying to flash a new rom and read that i needed to flash EL26 kernal with the CWM and by accedent i flashed EL29 and it had no recovery and now i cant boot up to android in in constant bootloop i tried applying the EK02 update.zip but i get a fail and my computer (and 2 more with 3 different cables) dont pick up the phone i get unrecognized device so i cant odin. any ideas?
luigi311 said:
i was trying to flash a new rom and read that i needed to flash EL26 kernal with the CWM and by accedent i flashed EL29 and it had no recovery and now i cant boot up to android in in constant bootloop i tried applying the EK02 update.zip but i get a fail and my computer (and 2 more with 3 different cables) dont pick up the phone i get unrecognized device so i cant odin. any ideas?
Click to expand...
Click to collapse
i think some ppl might get on u for not posting in this q&a. nevertheless, i feel ur anxiety.
i was able to get out of a bootloop once by deleting my copy of ODIN and downloading a new one. for some reason my old program seemed to corrupted/not working.
other times i've had trouble getting device recognized errors were due to cables/sometimes it seemed like if i didn't enter recovery prior to plugging in the usb i would get the error and had to re-start into recovery over again if i messed up the order.
there's definitely more info out there if u dig around in Q&A this was just off the top of my head.
Download Samsung drivers again, and use sfhubs one click no data. Most of the time its the drivers, especially since you said it doesn't recognize.
Sent from my Blu Kuban powered Epic (4g lol) Touch
thanks for the help guys yea sorry about wrong placement. I already tried reinstalling the drivers i even tryied reinstalling kies and download the drivers 3 times to make sure. as far as cables i tried 2 samsung ones that come with the phone and i tried a HTC one that i got from my EVO LTE and still no dice
-edit: is there a way to acually manually point it to a certain driver by using the have disk feature and using a .inf?
Hi, I started out with a stock tmobile s3 and tried to root it for the first time today, I followed this video
http://www.youtube.com/watch?v=mndQZqom3Ac
which asked me to use this cf-root 6.4
http://forum.xda-developers.com/showthread.php?t=1695238
when I hit start on that .tar file under odin, it failed stating "complete (write)operation failed)
since then, my device would boot with error "firmware upgrade encountered an issue" nothing else would happen.
I tried to go into recovery mode again and this time when I tried to retry the odin tar install, it would give me a new fail of cannot open com3
When I tried to use kies, it would just forever try to connect and never connect. so I couldnt do anything there.
What can I do? I would preferably try to retain all my saved data.
I also suspect my usb port might be faulty, sometimes need to press it in firmly to make the usb mass storage to work properly.
Thanks in advance
What is your Current android version ?
Perseus71 said:
What is your Current android version ?
Click to expand...
Click to collapse
i really didnt note which version i have... noob mistake i kmow. i think it is 4.2...is there any way i can check?
Ok, I totally messed up when I first attempted this. The .tar I used was for an international s3 and I have a tmobile us version!. the OP of the thread says it may even brick my phone if I attempt this on a non international version.
competely my fault, but what should I do to fix this and save my phone?
I cannot connect to kies, reinstalled the drivers and it still wont connect. just gets stuck in "connecting"
The odin now doesnt load a tar because it says "cannot open com3 "
EDIT:
fixed it, odin was not working due to kies running in the background and I finally was able to flash the correct chainfire for my phone
Glad its sorted out. I assume no issues now ?
Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
gica69 said:
Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
Click to expand...
Click to collapse
I found out that the phone had 4.1.1 on it and the guy tried to flash 4.2.2 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
gica69 said:
I found out that the phone had 4.11 on it and the guy tried to flash 4.22 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
Click to expand...
Click to collapse
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3
PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
Larry2999 said:
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
Click to expand...
Click to collapse
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
gica69 said:
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
Click to expand...
Click to collapse
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
Larry2999 said:
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
Click to expand...
Click to collapse
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.
gica69 said:
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.
Click to expand...
Click to collapse
You didn't mention if you tried the Kies option. I had a similar problem once when upgrade to 4.1.1 via Kies failed during the process and that was how I was able to recover. However, since you bought this from the secondary market, there is no way of telling for certain what the previous owner did wrong which would have been useful for recovery options.
One of the nice things about Odin is that you usually know the results immediately. If it says Pass, therefore, that's likely what it means. So Odin did flash something. But what did it flash? The counter you saw in download mode shows how many custom system installations there have been and 6 does show there has been some previous heavy tinkering with the phone. As you are still able to get into download modes, I would suggest you try flashing custom recovery (TWRP or CWM) via Odin. If this works and you are able to get into recovery mode, you may then try doing a hard wipe/reset via recovery. You may also try flashing the other (rooted) 4.1.1 file via Odin. At this stage, you really have nothing to lose in trying all options. I guess if you can get into recovery mode, the problem is almost solved as this leaves plenty of options.
A jig wouldn't help as that only gets you to download mode which, for now, you don't have a problem with. JTag should always be a last resort option only. Let me know how far it goes and good luck!
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
audit13 said:
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
Click to expand...
Click to collapse
This damn phone is starting to annoy me. I can still get into download mode but my phone gets usb device not recognized now. I have access to another I747 phone so my question is if I have access to the pit file from that phone can anything be done with the Debrick utility and a SD card with only download mode access? Thanks in advance.
Go into download and let us know what is shown on the screen.
audit13 said:
Go into download and let us know what is shown on the screen.
Click to expand...
Click to collapse
Odin Mode
Product Name: SGH-I747
Custom Binary Downloads: Yes (6 Counts)
Current Binary: Samsung Official
System Status: Official
Qualcomm Secure Boot: Enable
Green Android Icon Downloading...
Do not turn off target!!!
OK I plugged the USB in and out a few times and it allows to write every few tries. Back to my question can I do something in download mode if I have another i747 that I can copy stuff from? I also tried the suggestion to uncheck auto-reset pull the usb cable then the battery and try to go to recovery but it doesn't.Any suggestions are welcomed.
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
audit13 said:
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
Click to expand...
Click to collapse
I will try it again I think I already did but when I put the battery back and click the Vol+ Home Power I get the blue writing and then black screen. Should I wait like 10 min on the black screen or it should be quick. Thanks
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
audit13 said:
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
Click to expand...
Click to collapse
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
If u can get it into download mode u are never ever hard bricked my friend...take it from a guy who had to dust off his old galaxy sll last weekend & still can't get into d/l mode on my s3 after a week & even with a jig lol
Sent from my SGH-T989 using xda app-developers app
gica69 said:
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
Click to expand...
Click to collapse
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
Larry2999 said:
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
Click to expand...
Click to collapse
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
gica69 said:
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
Click to expand...
Click to collapse
I couldn't find one either although you may be able to create yours using the command line posted in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
You may also try using a jig to get back into download mode. Have you, however, considered exercising any buyer protection options you have on the phone since, it would appear, the guy sold you a lemon?
So this happened about a month ago. The battery drained and when I left it charging I noticed that it was vibrating and showing the grey battery icon and this loops. I have the CMR Recovery v6.0.4.7 and can only access it when connected to the wall charger. I have left it a while on CMR while connected to the wall to see if it need charging but it just does the same thing when trying to boot. I have wiped cache, dalvik cache and selected the "Fix root" option before rebooting and nothing. I have not tried to flash a ROM in fear of bricking it. I made it as far as the "Upgrading Apps" window before fully booting but it turned off. I searched a bit and some people blame a faulty USB Port and/or power switch. I have no problem in buying and replacing the USB port and the power switch, though I don't have soldering tools for the power switch. But since I don't know what the issue is exactly I haven't rushed to buy the USB port replacement. So, the question is: is it a software or hardware problem and can it be fixed? I hope this is a software issue so it can be easier to solve.
I suggest putting the phone into download mode and see if Odin recognises the phone. If it does, I would flash the latest stock rom.
audit13 said:
I suggest putting the phone into download mode and see if Odin recognises the phone. If it does, I would flash the latest stock rom.
Click to expand...
Click to collapse
Odin does recognize the phone on Download Mode. So, what you are saying is to flash the latest non-rooted ROM (OFW), correct? Like the tar files found in sites like SamMobile? That won't remove my root nor custom recovery, right? Kinda of a newb question even though I kinda know the answer, but I just want to make sure.
Flashing a stock ROM will always remove root and twrp.
audit13 said:
Flashing a stock ROM will always remove root and twrp.
Click to expand...
Click to collapse
Hi. So, I flashed the latest stock ROM that is available on SamMobile and it fails in Odin. Now when I plug the phone without going to Download Mode its says something about recovery mode in Kies and and a firmware upgrade issue. What is happening? Thank for your responses, btw.
What I downloaded was a zip titled "SGH-M919-TMB-M919UVUAMDL-1366964131" and inside is and tar.md5 file called "M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar". There on the same folder as Odin.
What error message was displayed in the Odin log?
Post the entire Odin log if possible. This will help to determine the issue.
You confirmed that the phone is an sgh-m919 in download mode?
Even though you turn on the phone and see the message"...firmware upgrade encountered an error...", Odin can still be usedto flash a stock ROM as if the phone was in download mode.
The MDL firmware is too old. Try flashing the latest ROM.