i know what most of you are thinking, i have already read through forum after forum for 4, going on 5, hours now. several people have similar situations to mine, but not similar enough to actually help me.
i rooted my s2 earlier today and it went perfectly. then i tried to use odin to flash jellybean to my phone, it was the stock rom. but since that little box wasn't yellow, it failed. my drivers were not properly installed. i forgot to install kies and get my drivers before i did this process. i thought i had already properly installed the drivers i needed, and i am still unsure of what the heck im supposed to have in order to make odin work. well i got this lovely little screen saying "firmware upgrade encountered an issue. please select recovery mode in kies & try again."
so i installed kies. immediately it said that no device was connected. so i unplugged and replugged my phone, said "connecting" but it never connected. not even twenty minutes later. so i rebooted my computer. nothing worked. i tried to boot my phone up to turn off "usb debugging" in case i had turned it on a few days ago without realizing it. the phone wont boot. its stuck on the screen that tells me "firmware upgrade encountered a problem".
however, i can get it to go back into downloading mode, but that doesnt really help me much since odin still cant flash my firmware correctly. it keeps bringing me back to that dreaded screen, im to the point of wanting to rip all my hair out. what else can i do?
someone must know how to deal with this situation. please please please help me! i dont want a $150 paperweight ):
thank you!
jennalking1992 said:
i know what most of you are thinking, i have already read through forum after forum for 4, going on 5, hours now. several people have similar situations to mine, but not similar enough to actually help me.
i rooted my s2 earlier today and it went perfectly. then i tried to use odin to flash jellybean to my phone, it was the stock rom. but since that little box wasn't yellow, it failed. my drivers were not properly installed. i forgot to install kies and get my drivers before i did this process. i thought i had already properly installed the drivers i needed, and i am still unsure of what the heck im supposed to have in order to make odin work. well i got this lovely little screen saying "firmware upgrade encountered an issue. please select recovery mode in kies & try again."
so i installed kies. immediately it said that no device was connected. so i unplugged and replugged my phone, said "connecting" but it never connected. not even twenty minutes later. so i rebooted my computer. nothing worked. i tried to boot my phone up to turn off "usb debugging" in case i had turned it on a few days ago without realizing it. the phone wont boot. its stuck on the screen that tells me "firmware upgrade encountered a problem".
however, i can get it to go back into downloading mode, but that doesnt really help me much since odin still cant flash my firmware correctly. it keeps bringing me back to that dreaded screen, im to the point of wanting to rip all my hair out. what else can i do?
someone must know how to deal with this situation. please please please help me! i dont want a $150 paperweight ):
thank you!
Click to expand...
Click to collapse
Disconnect the cable. Remove the battery and let it out for 10 minutes. Put it back in, go into download mode. Connect with odin and flash again. Hope this will work for you.
Verstuurd van mijn GT-I9100
Christiaan91 said:
Disconnect the cable. Remove the battery and let it out for 10 minutes. Put it back in, go into download mode. Connect with odin and flash again. Hope this will work for you.
Verstuurd van mijn GT-I9100
Click to expand...
Click to collapse
Also, remember to exit Kies using Task manager (and maybe disable Antivirus in ur PC) before connecting to Odin.
Sent from my SGS II
Related
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Remove Kies and reinstall see if it picks the phone up and installs the drivers .
jje
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
Yes it's an Epic touch 4g from sprint.
EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
OperationIvy85 said:
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
Click to expand...
Click to collapse
Try to reset your binary counter with a usb jig.
you could try and download the drivers again from here and see if it then connects
http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html
I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there that date is important
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
OperationIvy85 said:
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
Click to expand...
Click to collapse
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Who told you that the exclamation point means you voided your warranty?
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.
EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.
---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------
OperationIvy85 said:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
Click to expand...
Click to collapse
Well at least you got a phone now hope they didnt charge to much!!!!Good on ya mate
Update on my issue....
It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).
After using the right firmware, it worked.
OperationIvy85 said:
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
Click to expand...
Click to collapse
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
sfoksn said:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
Click to expand...
Click to collapse
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
aceofclubs said:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.
Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.
Is there anythign I could do to make the USB jig work without connecting it to the computer?
Can you get into download mode using the buttons?
Volume down+home+power
If so try and flash another Rom from intratechs thread to get back to stock.
If that works you can try again.
Sent from my GT-I9100 using XDA App
Okay, honestly, I didn't try doing anything out of the ordinary, I swear. I was trying to update my phone from Gingerbread to ICS.Using Samsung Kies, everything was going great, until halfway through the update Kies told me something along the line of "Phone cannot be recognized". Then it told me a bunch of steps which involved powering the phone off and reconnecting. I did just that.
Now my phone is stuck on a screen that reads Odin Mode and says: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. I can't get into download mode either. Everytime I try, my screen just goes black and my phone vibrates every 6 seconds or so.
I've tried recconecting to Kies, but it says "Device not responding. To resolve issue, reboot the device". I can't really reboot because it just goes back to the "Firmware encountered an issue" screen.
Yes, I've re installed Kies already. I do have "Odin" downloaded on my phone, but I don't know how to use it.
God, this is why I didn't dabble in custom roms or whatever. But I still get screwed over. >_>
Whoever helps me out, I thank you so much. Please, anyone. =/
(I have a Samsung Galaxy SII Skyrocket from AT&T)
MrPleh said:
Okay, honestly, I didn't try doing anything out of the ordinary, I swear. I was trying to update my phone from Gingerbread to ICS.Using Samsung Kies, everything was going great, until halfway through the update Kies told me something along the line of "Phone cannot be recognized". Then it told me a bunch of steps which involved powering the phone off and reconnecting. I did just that.
Now my phone is stuck on a screen that reads Odin Mode and says: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. I can't get into download mode either. Everytime I try, my screen just goes black and my phone vibrates every 6 seconds or so.
I've tried recconecting to Kies, but it says "Device not responding. To resolve issue, reboot the device". I can't really reboot because it just goes back to the "Firmware encountered an issue" screen.
Yes, I've re installed Kies already. I do have "Odin" downloaded on my phone, but I don't know how to use it.
God, this is why I didn't dabble in custom roms or whatever. But I still get screwed over. >_>
Whoever helps me out, I thank you so much. Please, anyone. =/
(I have a Samsung Galaxy SII Skyrocket from AT&T)
Click to expand...
Click to collapse
This is not the ****rocket forum. and all at&t releases suck. they bring problems to our device too. just flash a custom ROM.
From your section. this should get moved.
MrPleh said:
Okay, honestly, I didn't try doing anything out of the ordinary, I swear. I was trying to update my phone from Gingerbread to ICS.Using Samsung Kies, everything was going great, until halfway through the update Kies told me something along the line of "Phone cannot be recognized". Then it told me a bunch of steps which involved powering the phone off and reconnecting. I did just that.
Now my phone is stuck on a screen that reads Odin Mode and says: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. I can't get into download mode either. Everytime I try, my screen just goes black and my phone vibrates every 6 seconds or so.
I've tried recconecting to Kies, but it says "Device not responding. To resolve issue, reboot the device". I can't really reboot because it just goes back to the "Firmware encountered an issue" screen.
Yes, I've re installed Kies already. I do have "Odin" downloaded on my phone, but I don't know how to use it.
God, this is why I didn't dabble in custom roms or whatever. But I still get screwed over. >_>
Whoever helps me out, I thank you so much. Please, anyone. =/
(I have a Samsung Galaxy SII Skyrocket from AT&T)
Click to expand...
Click to collapse
Omg another slowrocket? Dude...just...no...if u don't even know your model number to ur phone don't bother doing anything else to it and read
Sent from my SGH-i777 using XDA
Sorry, but if you cannot be bothered to find the right board to post in, i won't be bothered to move it for you..
(This assumes your "sent from" line is correct. If your device actually is an i777, let me know)....
Hi guys im not quite new when it comes to android.
last night i was trying to upgrade and flash a CWM on my friends vibrant whe it stopped. i turned off the phone when tries to turn it back on.... the phone quite turns hot and not like my phone when im flashing it.
i got all the files download and read all of the instructions before starting ofcourse.
first the phone doesnt turn on, then i manage to enter the DOWNLOAD MODE again but somehow the Laptop doesnt detect and gives a yellow punctuation mark on the device. i tried to install and flash the rom but it doesnt continue. i tried putting or plugging it to a diff port but still no luck.
can someone help me and answer this question? is this thing hard bricked = im screwed
any help would be gladly appreciated. thanks again guys in advance
Try a different USB cable as well as a different USB port.
http://forum.xda-developers.com/showthread.php?p=30831184
Read that post, then, read the thread from page 1, just so I don't feel like I've had the same conversation twice in 1 day.
Shouldn't take long its only a few posts. See if this applies to your situation.
thanks boss but i tried the cable with my galaxy mini and it worked when i tried to flash and went back to stock rom. changed the port as well but still no luck....
the phone as well doesnt turn on like the way of a soft brick. a picture of a phone wanted to be connected to a pc, black screen it is though but the phone goes to DOWNLOAD MODE
Try reinstalling drivers from AIO toolbox. Open Odin as administrator. What does Odin say exactly? Is there a yellow box, if so what does it say in it?
i tried reinstalling the drivers i have downloaded but still no luck, odin detects the phone and when it doesnt i re-install the driver so the computer would detect the COM port of the phone. the odin doesnt push through and no BLUE bar on the phone it self. such as the indicator for the flashing. i tried as well running odin as the administrator but still no luck. so do you think that this could be a hard brick, i dont think so cause i can still enter the DOWNLOAD mode of it. the phone turns hot when im on the download mode. could this be a hardware problem.
No its probably not a brick. I think its a communication issue. I would still think its possible to fix it. As far as it getting hot, not sure but the fact that it gets to download mode is a beacon of hope.
I've got to go to bed, will be back tomorrow to check on this.
yeah i hope thesame way too man. thanks for the reply.... time for you to take some rest. thanks again. i'll post the reply if ever the phone gets fixed
thanks for everything man, the phone now is resurrected after JTAGGING. but i know that those technicians who charged me 1000php just did the flashing on ODIN. i know the thing i've done wrong why it didnt work the first time. now it is running up again. the firmware that was flashed was for TELUS. it now shows T959D. i'll follow the guide fully on flashing and upgrading this thing
I had the same problem as you this morning. I tried driver, after driver, after driver and nothing worked. Eventually I gave in and used my sister's laptop and that did the trick. Mabuti ayos na ang cp mo. Ingat.
It's my beloved I9100P. Last night it strangely failed. I realised in the morning when the alarm didn't go off. The phone was switched off.
When I tried to switch on, it got stuck in boot loop. The carrier animation and samsung logo will keep repeating. So I thought I will go into recover mode and do a factory reset. Phone went into factory mode the first time. I thought let me do a restart from there, just to see what happens. At this point, I noticed a lot of red errors on recovery mode screen, most of which saying something like "unable to mount /cache". I restarted it, but unfortunately the phone again went into boot loop.
Now when I tried, it refused to go even to recovery mode. I tried several times, but every time it got stuck on Samsung Galaxy logo.
It went into download mode fine, so I thought I will flash Orange UK carrier ROM. I downloaded the ROM and tried flashing with ODIN. ODIN recognised the device, but the flashing failed with error "Complete (Write) operation failed".
I don't know what to do now, have exhausted all option that I knew.
Any help in reviving my phone please?
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
wulsic said:
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
Click to expand...
Click to collapse
Interesting. After trying several things, I did unplugged it from the machine. It shows the upgrade failed warning message whenever I try to switch it on now, which was expected.
I can still go to download mode and restart the ODIN flashing original Orange firmware process, but it fails with the same error. The only difference is, the first time it failed on CACHE step. Now it is failing one step earlier, at NAND writing stage.
Is there any hope? I had kies disabled etc., but will give it another shot. My phone was accessible with kies and I could also upload my development APKs from Android studio. So I think drivers shouldn't be a problem.
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
wulsic said:
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
Click to expand...
Click to collapse
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
kaushal101 said:
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
Click to expand...
Click to collapse
Did you tryed another stock rom version?
Try other usb cable.
Sounds weird but try to leave the battery out of your phone for like a couple minutes
Try other usb port.
Try other computer:silly:
These are the things I can think of atm.
Have tried other USB port. Have tried a different firmware.
Am going to try a different PC today, will also give different cable a shot. But the cable I'm using is Samsung official one which came with the phone. And I've been uploading APKs using this cable fine, so am quite sure the cable is fine. But still, will give it a shot. Thanks for replying
So I have a S4 i9545 for Verizon. It was on 4.2.2 rooted and I upgraded using Fireflash with I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Everything seemed fine so I was using Titanium back up to remove the bloatware and then my battery died. When I charged it and booted up it got to the Verizon screen and hung there. I reset and tried several more times. I tried to use odin and flash a stock ROM SCH-I545_VZW_1_20140330160240_yni63xq6zh and I also tried one more. Odin gave a an error and failed. I then tried going into the boot loder and flash the I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Not sure if this was foolish or not. When I booted up I got to a black screen and there was a voice talking, maybe some sort of training, but I couldn't do anything.
If anyone can point me in the right direction on how to unbrick my S4 I would appreciate it. I know I screwed up.
Right now when I turn on the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I tried connected to my computer and opening kies but it doesn't find it.
Try disconnecting your phone, completely closing Kies, then re-launching it with your phone still disconnected. Then click Tools > Firmware Upgrade and Initialization then follow the prompts