I might have accidentally bricked my SGS 2. I get a screen saying:
"firmware upgrade encountered an issue. Please select recovery mode in kies and try again"
with a mobile phone and a computer logo with a Yellow triangle in between.
I know abt Rooting and ROM flashing etc and has been doing it for the last couple or years.
I flashed Franklin's XXKG3 Kernels, and before I could flash Chainfire's XXKG3 kernel, the USB ports refused to recognize my handset. I can still go into download mode but the Odin or Samsung Kies etc. won't do nothing.
Keeps saying "USB Device not recognized"
Please help!!!!
leo13aug79 said:
I might have accidentally bricked my SGS 2. I get a screen saying:
"firmware upgrade encountered an issue. Please select recovery mode in kies and try again"
with a mobile phone and a computer logo with a Yellow triangle in between.
I know abt Rooting and ROM flashing etc and has been doing it for the last couple or years.
I flashed Franklin's XXKG3 Kernels, and before I could flash Chainfire's XXKG3 kernel, the USB ports refused to recognize my handset. I can still go into download mode but the Odin or Samsung Kies etc. won't do nothing.
Keeps saying "USB Device not recognized"
Please help!!!!
Click to expand...
Click to collapse
Might help to reinstall KIES or try another computer.
Keeps saying "USB Device not recognized"
USB drivers problem remove Kies totally and reinstall .
Connect in mass storage mode and let windows find drivers .
That fails its broken phone .
jje
you broke your phone.
buy another SGS II
You can always try using a USB JIG to put the phone in download mode.
leo13aug79 said:
Keeps saying "USB Device not recognized"
Click to expand...
Click to collapse
Uninstall the Samsung USB Driver from Control Panel
START/Control Panel/Programs and Features
Select "SAMSUNG USB Driver for Mobile Phones" and then uninstall
reboot your PC and then re-install the Samsung USB Driver from:-
C:\Program Files\Samsung\Kies\USB Driver
and run "SAMSUNG_USB_Driver_for_Mobile_Phones.exe"
Doing that will make sure there is no USB driver corruption.
"firmware upgrade encountered an issue. Please select recovery mode in kies and try again"
Click to expand...
Click to collapse
I had the same problem on my SGS4g after updating to a leaked 2.3.4 rom, which would not make phone calls. Tried to use heidmall to downgrade by loading a new rom. After installing the usb driver as described here http://forum.xda-developers.com/showpost.php?p=14798367&postcount=1 . After reboot I get the error screen <phone..!..Computer> "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I then took the following steps.
I came across this site: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Bricked_Screen Under the bricked section it mentions a couple things to try. I the reboot cycle with a couple of times and kept on getting the same screen. Still no go.
I took Odia's advice an did a complete removal of all usb drivers as mentioned and reinstalled kies. This was key in getting odin to recognize the phone again.
My solution:
I try Odin again to try to get it to recognize my phone. I open odin with the usb connected in this state and it is not recognized. I pull battery, it boots to error screen. I restart odin and then plug in the usb and it is recognized. I was then able to load my pit, pda, phone, csc back onto the phone with odin. The first time it tried to load the data it failed, the second time it worked!
Interestingly I never got the "Download Screen". I was still on the mentioned error screen, yet odin was able to still see the phone. The status bar still showed up on the error screen as the fresh rom was being loaded.
I thought I was totally bricked, but this method worked in my case. Hope something similar might work for you.
I still don't know I would get this error screen and have to go through this after loading the required usb driver for heimdall? Any ideas?
OMG! It's WORKING!
Thanks a lot to you all guys for the co-operation....
So, what did I do???? I uninstalled Kies and re-installed a couple of times but it won't access it. Tried Odin in all possible ways, No success. While playing and after ordering a "Jig" from some1 in USA,
I thought of something else and while the phone still being connected with the pc, I ran SuperOneClick, but it went on saying waiting for the device,.... I accidentally or in frustration hit the "HOME" button and it started doing something, USB drivers and Modem drivers installed on PC. Then I started Odin and the port went "Yellow". And I flashed it with the XXKG3.....
OMG! I'm so much relieved!!!!!!!! thanks God
thank you all too
Love your SGS2 and love God! Bless you all!
fvnktion said:
I had the same problem on my SGS4g after updating to a leaked 2.3.4 rom, which would not make phone calls. Tried to use heidmall to downgrade by loading a new rom. After installing the usb driver as described here http://forum.xda-developers.com/showpost.php?p=14798367&postcount=1 . After reboot I get the error screen <phone..!..Computer> "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I then took the following steps.
I came across this site: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Bricked_Screen Under the bricked section it mentions a couple things to try. I the reboot cycle with a couple of times and kept on getting the same screen. Still no go.
I took Odia's advice an did a complete removal of all usb drivers as mentioned and reinstalled kies. This was key in getting odin to recognize the phone again.
My solution:
I try Odin again to try to get it to recognize my phone. I open odin with the usb connected in this state and it is not recognized. I pull battery, it boots to error screen. I restart odin and then plug in the usb and it is recognized. I was then able to load my pit, pda, phone, csc back onto the phone with odin. The first time it tried to load the data it failed, the second time it worked!
Interestingly I never got the "Download Screen". I was still on the mentioned error screen, yet odin was able to still see the phone. The status bar still showed up on the error screen as the fresh rom was being loaded.
I thought I was totally bricked, but this method worked in my case. Hope something similar might work for you.
I still don't know I would get this error screen and have to go through this after loading the required usb driver for heimdall? Any ideas?
Click to expand...
Click to collapse
I love you man! You saved my phone and me!
So what have we learnt today? Don't go screaming "brick!" everytime you encounter a problem
I had a same issue yellow triangle between Phone and PC symbol...
followed this step .. http://forum.xda-developers.com/showthread.php?t=1274337
just did like this on very first step to get into odin mode hold vol down and power for longer then usual to get into odin mode and by pass that yellow triangle between Phone and PC screen and then follow rest of it same and easy as right clicking on desktop LOL!
From my experience, only true brick I encountered was when I messed with boot loaders. If the screen shows anything at all, Odin will recognize it. Glad to hear it's fixed
Sent from my GT-I9100 using XDA App
Odia said:
Uninstall the Samsung USB Driver from Control Panel
START/Control Panel/Programs and Features
Select "SAMSUNG USB Driver for Mobile Phones" and then uninstall
reboot your PC and then re-install the Samsung USB Driver from:-
C:\Program Files\Samsung\Kies\USB Driver
and run "SAMSUNG_USB_Driver_for_Mobile_Phones.exe"
Doing that will make sure there is no USB driver corruption.
Click to expand...
Click to collapse
I´d tried to upgrade my Infuse SGH-i997 (AT&T) but I did something wrong and now the cell phone no work.
When it turn on says:
"firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The computer recognize the cell phone but I don´t know what else I can do.
Any suggestion?
Can you get into download mode? If yes then reflash stock firmware using Odin
Sent from my GT-I9100 using Tapatalk
A bricked phone is a phone which will not respond. It maybe a soft brick or hard.
If you can get into download or recovery all you have to do is reflash. Wipe data & Cache. You will be up and running. If your phone is not recognised by your computer then reinstall kies.
Sent from my GT-I9100
Yep. Infuse Q&A (You're in the wrong section).
anjimgo said:
I´d tried to upgrade my Infuse SGH-i997 (AT&T) but I did something wrong and now the cell phone no work.
When it turn on says:
"firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The computer recognize the cell phone but I don´t know what else I can do.
Any suggestion?
Click to expand...
Click to collapse
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Well, I got this same Firmware upgrade error. I can't get the computer to see it at all. It's almost like the USB port doesn't work anymore. I can get into the download mode but then it ends there. I cannot get into the bootloader at all. If I try, it goes to the error screen and if I boot normally, it goes to the error screen.
Brittlespeed said:
Well, I got this same Firmware upgrade error. I can't get the computer to see it at all. It's almost like the USB port doesn't work anymore. I can get into the download mode but then it ends there. I cannot get into the bootloader at all. If I try, it goes to the error screen and if I boot normally, it goes to the error screen.
Click to expand...
Click to collapse
I can't tell if you're asking for help or just letting people know, but anyway, considering all your previous posts were in the Epic 4G Touch forums, you've probably trashed your device flashing something meant for the I9100.
See this thread for confirmation of your new shiny brick, if my above assumption was correct: http://forum.xda-developers.com/showthread.php?t=1492323
this solution worked for a Galaxy s3 mini
fvnktion said:
I had the same problem on my SGS4g after updating to a leaked 2.3.4 rom, which would not make phone calls. Tried to use heidmall to downgrade by loading a new rom. After installing the usb driver as described here http://forum.xda-developers.com/showpost.php?p=14798367&postcount=1 . After reboot I get the error screen <phone..!..Computer> "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I then took the following steps.
I came across this site: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Bricked_Screen Under the bricked section it mentions a couple things to try. I the reboot cycle with a couple of times and kept on getting the same screen. Still no go.
I took Odia's advice an did a complete removal of all usb drivers as mentioned and reinstalled kies. This was key in getting odin to recognize the phone again.
My solution:
I try Odin again to try to get it to recognize my phone. I open odin with the usb connected in this state and it is not recognized. I pull battery, it boots to error screen. I restart odin and then plug in the usb and it is recognized. I was then able to load my pit, pda, phone, csc back onto the phone with odin. The first time it tried to load the data it failed, the second time it worked!
Interestingly I never got the "Download Screen". I was still on the mentioned error screen, yet odin was able to still see the phone. The status bar still showed up on the error screen as the fresh rom was being loaded.
I thought I was totally bricked, but this method worked in my case. Hope something similar might work for you.
I still don't know I would get this error screen and have to go through this after loading the required usb driver for heimdall? Any ideas?
Click to expand...
Click to collapse
Thanks a lot. My teenage son thought he had bricked his S3 mini but I was able to fix it after reading this thread. Thanks.
i got the "verizon has detected unauthorized software" soft brick earlier today when trying to partition my sd card. i since have been trying and trying to flash stock in odin to no avail. now, instead of the "detected unauthorized software," i get "firmware upgrade encountered an issue, please select reecovery mode in kies & try again."
kies does nothing. odin fails every time. im getting fed up and i need to leave for work soon
im sorry for the stereotypical help me post but ive looked at MANY threads on here and none helps
If you looked at the stickies you would have had your answer in seconds. Also there are probably a dozen threads about this so you may want to brush up on your searching technique.
Use the alternate restore download.
Here's the thread from the stickies
http://forum.xda-developers.com/showthread.php?p=39299305
Sent from my SGH-T889 using xda app-developers app
souvasaurus said:
i got the "verizon has detected unauthorized software" soft brick earlier today when trying to partition my sd card. i since have been trying and trying to flash stock in odin to no avail. now, instead of the "detected unauthorized software," i get "firmware upgrade encountered an issue, please select reecovery mode in kies & try again."
kies does nothing. odin fails every time. im getting fed up and i need to leave for work soon
im sorry for the stereotypical help me post but ive looked at MANY threads on here and none helps
Click to expand...
Click to collapse
1) Make sure you are using the latest Odin 3.0.7.7(http://www.androidfilehost.com/?fid=23321874045862882) with 4.3 full stock firmware.
2) If not working you could use the full firmware and a PIT file( http://d-h.st/mKu)
or If Odin failed
3) Verizon Utility (Credit to ThePagel):
Download and unzip
SUA_ar.zip http://www.androidfilehost.com/?fid=23269279319199795
Open SUA_ar folder
Install SUABnRSetup as administrator (might take some time and may not be necessary)
Download kies from here http://downloadcenter.samsung.com/content/SW/201312/20131213110414156/KiesSetup.exe and install as administrator. make sure the [Unified Driver Installer] check box is checked at the end of the install (Might take some time)
Make sure Kies is closed then go into download mode and plug into your pc (hold here until drivers install)
Run SUA.exe as administrator
Click on [Repair Assistant] (on the left)
Click on run [Repair Assistant] (on the bottom)
After repair assistant recognizes your phone click [Repair Galaxy Note 2I] (on the right side)
It will say "Due to the condition of your phone/tablet, all data will need to be erased during the repair."
Click [continue]
From here on out its all automated it will download and install full stock firmware then restart (dont forget first boot takes time)
If you get stuck in a boot loop go into recovery and do a factory reset (probably should regardless)
Good luck!
buhohitr said:
1) Make sure you are using the latest Odin 3.0.7.7 with 4.3 full stock firmware.
2) If not working you could use the full firmware and a PIT file
or If Odin failed
3) Verizon Utility (Credit to ThePagel):
Download and unzip
SUA_ar.zip
Open SUA_ar folder
Install SUABnRSetup as administrator (might take some time and may not be necessary)
Download kies from here and install as administrator. make sure the [Unified Driver Installer] check box is checked at the end of the install (Might take some time)
Make sure Kies is closed then go into download mode and plug into your pc (hold here until drivers install)
Run SUA.exe as administrator
Click on [Repair Assistant] (on the left)
Click on run [Repair Assistant] (on the bottom)
After repair assistant recognizes your phone click [Repair Galaxy Note 2I] (on the right side)
It will say "Due to the condition of your phone/tablet, all data will need to be erased during the repair."
Click [continue]
From here on out its all automated it will download and install full stock firmware then restart (dont forget first boot takes time)
If you get stuck in a boot loop go into recovery and do a factory reset (probably should regardless)
Good luck!
Click to expand...
Click to collapse
This always fails at 83% for me. I've tried seven different USB cables including the original Samsung one, and still, no dice. Thanks for the info, though. I was out of options before I saw this.
VDubFanR said:
This always fails at 83% for me. I've tried seven different USB cables including the original Samsung one, and still, no dice. Thanks for the info, though. I was out of options before I saw this.
Click to expand...
Click to collapse
I have the exact problem when trying to repair, it sits at 83% and eventually says phone was disconnected. if I disconnect phone Windows makes the "disconnected device" sound. What is wrong??? Tried flashing stock PIT. No luck. Flashing stock 4.3 via odin fails as well.
I have a different issue where, while in Download Mode, the Verizon Repair Assistant won't let me click the Repair button. It's grayed out.
So I was helping my friend root his phone, and ran into a few unsuccessful trials. Tried to flash recoveries from 2-3 sources, it didnt work but atleast he was able to start his phone normally. Now it shows the screen which says firmware error, try recovery from Samsung Kies. Problem is Kies wont even detect the phone.
Will the instructions in this guide fix his issue?
http://forum.xda-developers.com/showthread.php?t=1414341
Yes I can still access the download mode. The part I can;t understand in this thread is : "Find a G2x USB and check if it puts in download mode while its off. If it doesn't" Once in the download mode screen, WHAT exactly indicate if it has been 'put in download mode' Is it the "Added" text in Odin?
I made a stupid mistake - just so see whether it works I brought my device into download mode, unaware, that there is no way of exiting it. I connected the player to my laptop, launched heimdall, but there was nothing like "reboot" or so available. So in heimdall, I pressed the undocumented button "Close PC screen", without knowing what it does.
Now, the devices shows a screen saying
"Firmware upgrade encountered
an issue. Please select
recovery mode in Kies & trie again"
Removing the battery does not change the situation.
I did not actually flash any firmware, so I would hope that the original firmware is stil intact and that there is just some stupid switch that needs to be triggered.
Can anyone advise what to do?
I also connected the device to a windows laptop with Kies on it, but to no avail... Windows detects it, but Kies ignores it.
I am trying to solve this now by re-installing the stock firmware, but heimdall, even though it detects the device says "ERROR: Protocol initiallisation failed!
[SOLVED] stuck in download mode
actually taking out the battery for a while and restarting made it work. Ignored the error message on the screen, flashed the stock firmware and I was done.
Hello All,
I've been reading posts from here for a long time but this is my first post.
I'm coming here as a last resort to save my Galaxy s2 (SGH-T989) which has a stock ROM.
Here's what happened.
I dropped my phone and then it got stuck in bootloop (it only boots until I see the "SAMSUNG" word animation and stops there).
At that point, ODIN 'sees' that there's a connected device; KIES keeps "connecting...." but can't actually connect; ADB does not show any connected device.
So, what I wanted to do was to factory "reset" the phone. The problem is I can't get the phone into Recovery mode. I believe it's because my volume down button was acting up when the phone was working. However, I can get to "Download Mode" using a USB Jig.
So, the next thing to do is to flash a new stock ROM. However, whenever I connect my phone when it's in "Download Mode", ODIN does not see it.
Yes, I've installed, re-installed, removed, re-installed all drivers and Kies and I've done that so many times you can't even believe it.
The problem is that the device driver "SAMSUNG Mobile USB CDC Composite Device" gives the following error "This device cannot start. (Code 10)", and I don't know why or how I can get rid of that. As mentioned above, I've tried all the device driver installation fixes but none has worked.
I mean, when the phone is not in Download Mode and I connect it to my PC, all device drivers are working fine with no error, but when it's in Download Mode, I get the error mentioned above "This Device cannot start.".
So, my questions:
1) Is there a way to get to Recovery Mode without using the button combinations? (The phone is in bootloop)
2) How can I fix the device driver error mentioned above to get ODIN to see my device?
3) Is there anything else I need to be doing?
This problem is really frustrating and I've been on it for more than 2 weeks and nothing has worked so far. Any help is greatly appreciated.
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. http://support.microsoft.com/kb/943104 try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
wulsic said:
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
Click to expand...
Click to collapse
Thanks for the quick reply, wulsic.
1. No, I did not flash any kernel on this phone, everything on it is stock and was working just fine before it was dropped. I meant that the volume down was not working properly, not that it was acting like up.
2. I tried that but did not work
3. The drivers are working fine when the phone is not in Download Mode, it's only when it's in Download Mode that I get the error and I've tried re-installing drivers and everything, I think the problem is with the device itself not a driver problem.