Related
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 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.
Hello everyone,
I really need help. A friend asked me to fix his tablet because it had malwares, so I rooted the device, and deleted the bad files, but then i got error messages, and at the end it went off. Now when i turn it on, it's stuck on the ACER logo, MT65xx goes on and off, I install all the drives but still goes on and off. I sent through adb sideload the stock firmware Acer_AV0K0_A3-A20_1.018.00_WW_GEN1_DCC thinking that i was going to unbrick the device but it didn't work. I tried smart phone flash with the 1.018.00 firmware but I keep getting BROM ERROR (2004). I checked the list of errors, and I changed the compatibility, and ran sp with administrator, but still error 2004. What can I do to unbrick it? By the way, I am following this xda thread to fix it, but I can't (http://forum.xda-developers.com/showpost.php?p=59693904&postcount=480) Thank you everyone!
acer iconia a3 a20 error sp flash fix
fmarino09 said:
Hello everyone,
I really need help. A friend asked me to fix his tablet because it had malwares, so I rooted the device, and deleted the bad files, but then i got error messages, and at the end it went off. Now when i turn it on, it's stuck on the ACER logo, MT65xx goes on and off, I install all the drives but still goes on and off. I sent through adb sideload the stock firmware Acer_AV0K0_A3-A20_1.018.00_WW_GEN1_DCC thinking that i was going to unbrick the device but it didn't work. I tried smart phone flash with the 1.018.00 firmware but I keep getting BROM ERROR (2004). I checked the list of errors, and I changed the compatibility, and ran sp with administrator, but still error 2004. What can I do to unbrick it? By the way, I am following this xda thread to fix it, but I can't (http://forum.xda-developers.com/showpost.php?p=59693904&postcount=480) Thank you everyone!
Click to expand...
Click to collapse
---------- Post added at 11:26 AM ---------- Previous post was at 11:21 AM ----------
fmarino09 said:
Hello everyone,
I really need help. A friend asked me to fix his tablet because it had malwares, so I rooted the device, and deleted the bad files, but then i got error messages, and at the end it went off. Now when i turn it on, it's stuck on the ACER logo, MT65xx goes on and off, I install all the drives but still goes on and off. I sent through adb sideload the stock firmware Acer_AV0K0_A3-A20_1.018.00_WW_GEN1_DCC thinking that i was going to unbrick the device but it didn't work. I tried smart phone flash with the 1.018.00 firmware but I keep getting BROM ERROR (2004). I checked the list of errors, and I changed the compatibility, and ran sp with administrator, but still error 2004. What can I do to unbrick it? By the way, I am following this xda thread to fix it, but I can't (http://forum.xda-developers.com/showpost.php?p=59693904&postcount=480) Thank you everyone!
Click to expand...
Click to collapse
hy friend use this sp flash tools v5.1515.00
this link download https://doc-0c-bc-docs.googleuserco...046/*/0B7XGoy6u4PgeX3ByYUNyWlpjZmc?e=download
go in sp flash tools then select scatter file where you download the rom on directory then check all,pres download ,now pres vol down and connect the usb to computer and tablet still press vol down,see the mtk usb on bar sp flash tools ,relese vol down and wait ,red bar,purple bar,yellow bar, ok circle , done ,now disconect the tablet and press power ,or check if have logo charger reput usb to computer.100 % tets by me work
I have a similar problem, but no error message...it just seems the computer can't see the tablet. I tried my Windows 10 machine and an old Windows XP machine I have lying around. I've installed several versions of drivers, and nothing. I'm so frustrated right now. @paulktm I tried your file, but there's nothing there. I don't get any kind of error message, the Win10 machine just acts like it sees the tablet for a second, then doesn't anymore. The XP machine sees it, but fails to install any drivers for it...even when I manually install them, they don't seem to do any good.
I'm so frustrated right now!!!
This is an old thread but maybe some poor soul finds it like I did and manages to get his device back as well.
I've had a lot of trouble with an Acer Iconia A3 A20 FHD that was stuck at the first logo screen. Powered off and connected to the charger it only showed the battery logo with the flash but no animation any more. Booting into recovery (Pwr+VolDn) worked but mounting the system partition didn't work.
SP Flash always aborted with the dreaded "BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL (0x7D4)" / "BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL (2004)" although cabling and drivers were perfectly all right. Obviously Acer patched the preloader in order to lock out SP Flash's download agent - that's customer support - thank you [email protected]#%&!!!
Solution: Power off, start SP Flash download/readback/whatever, press VolUp *and* VolDn simultaneously and plug in the usb cable. This way the download agent should be able to do it's job. I also plugged out the battery all the time and this seems to be necessary.
Flashing worked as it should and the tablet booted nicely and I didn't even loose my apps and data since I excluded the USRDATA partition from flashing.
Good luck!
Hi
same problem, tablet bricked after installing custom recovery and on boot loop
tried to unbrik with but SPF tools, com port is working but the firmware won't upload...
I waited for ages.. nothing...
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
You haven’t said much about as to what you had done with this phone prior to your issue, whether you have left your P9000 as standard with OTA updates or perhaps you have rooted, flashed a different Rom or changed its Kernel ?
It’s hard for anyone to give help easily without some background from you.
You're right, I bought it two weeks ago as a used part. To my knowledge it was left as standard (previous owner didn't seem to be skilled too much since some of his folders remained on the phone) and as far as I remember the installed ROM was 20160810, although I'm not 100% sure since I'm also new to android / not experienced with ROM versions and didn't write it down. At the end I believe the phone had never been rooted or changed kernel.
Maybe worth mentioning: The last two days before failure I noticed that the phone restarted one or two times per day.
@brager
There are two possibilities (or more)
1. It's hard bricked, so Google for a mtk hard unbrick guide
2. It's a battery related problem
Keep it two days plugged, or replace it
Keep in mind that the newest mtk software has to be installed on your computer
And try another cable first of all
1. It's hard bricked, so Google for a mtk hard unbrick guide
Click to expand...
Click to collapse
I've already performed all the steps in these mtk hard unbrick guides. I'm able to enter META mode but when I try to flash the preloader I get the error described above [BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)]
2. It's a battery related problem
Keep it two days plugged, or replace it
Click to expand...
Click to collapse
As far as I understand it flashing can/should be done without battery.
Keep in mind that the newest mtk software has to be installed on your computer
Click to expand...
Click to collapse
I was using SPFT 5.1524.00, now updated to SPFT 5.1628 and get nearly the same error: BROM ERROR: STATUS_DA_HASH_MISMATCH (0xC0070004)
And try another cable first of all
Click to expand...
Click to collapse
...didn't change anything.
I think the phone has a hardware problem and went to heaven.
Brom error: Status_da_hash_mismatch
brager said:
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
Click to expand...
Click to collapse
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Help,I have the same problem
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
It has been 2 days that i try to fix this problem,because i thought it was a driver problem i formatted my windows 7 and reinstalled everything.
This issue still persists and my phone is brand new.