[Q] Help! Still Soft Bricked, I'm frantic. - AT&T HTC One (M7)

I am still soft bricked with my One. I can still access bootloader and recovery.
The problem I am having is that my computer is not recognizing the device. Whenever I try to do anything, it says "Device not found"
This includes running the ATT RUU. The really weird thing is that I can flash a recovery using the All in One toolkit...
I tried a different computer and USB cable but no change.
What am I doing wrong?

Related

HELP!

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.

Did I brick the unbrickable phone?

I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
pscpa said:
I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
Click to expand...
Click to collapse
Control Panel/ User Account/ User Account Control settings- set to- Never notify- restart computer.
Should recognize phone. Reset to default when done and restart. Windows crap!
Thanks but this setting has always been set to "Never Notify"......any other ideas...please
I don't know nothing about it but the guy said " reset to default and restart (again)??
Sent from my SCH-I500 using xda premium
Followed the directions exactly. I think the OP wanted me to reset to default after I was done flashing. This is so strange....I figure if the people on XDA can't figure this out the phone is doomed.
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
schu9120 said:
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I had to use a laptop to access my Fascinate because my desktop wouldnt even show it as unrecognized hardware, it was like it didnt even exist... I went in device manager and uninstalled all my usb devices, rebooted with everything but mouse/kb unplugged, installed SDK drivers for Nexus S, rebooted again (probably not needed but better safe than sorry) and I can now Odin into my phone... Hope this helps ya man... sucks bricking a phone
The Heimdall drivers won't work. Kies won't recognize it if it won't boot. There should be an option in Kies to install the driver. Drop down box in the top left corner. Did you try to install your driver that way?
have you installed the driver yet? samsung driver?

S-off fail and phone not recognized by computer HELP

So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
DeviceSettings said:
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
Click to expand...
Click to collapse
I'm not sure what's happening with your computer not seeing the phone, but if you have a microsd adaptor you could get a stock RUU onto your card and flash back to stock.
Edit: or just your boot.img. If you can get into hboot you're not bricked.
Part fix
As previous poster said, put a PH...IMG with boot on it and you'll be able to boot up again. Yours is third phone reported here with USB problem after failed S-0ff.
I can boot my rom, but no radio or wifi, No charging, and no computer can see it for fastboot. Hoping for cure soon.
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Same thing happened to me. I just finished uninstalling HTC Sync and Android SDk, then reinstalled both. Now the drivers are working properly, and computer sees my phone again. This should help.
***edit: this process helped with my computer finding software drivers to connect phone to computer. Before- "Windows could not find drivers for Android device" (device manager in windows)
I could never get it to work in the first place. Cleanflash finds and flashes to it just fine but the s off just can't see my phone once it reboots.
Sent from my ADR6425LVW using XDA
DeviceSettings said:
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Click to expand...
Click to collapse
If the phone is rebooting to the screen with the arrow when you press power to enter fastboot then try going to recovery, your regular recovery will probably not show up but another stock hboot menu will. Then try selecting fastboot there and see if you can run fastboot commands without rebooting to arrow screen.
Sent from my HTC Vigor
Success getting it to reboot with the boot.img from the rom I was running....But unfortunately the usb is fried. Can not charge the phone or connect to a computer. So I guess that is another potential risk with using this method.
Ouuuuch :/
Sent from my ADR6425LVW using xda premium
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
DeviceSettings said:
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
Click to expand...
Click to collapse
Warranty!
(edit: kidding, no need for a ****storm)

[Q] Softbricked, can't get into recovery,HELP with $$!! NYC

Hey guys,
Long story short.
Flashed Kitkat with S-on (really stupid)
phone rooted
bootloader unlocked
S-On
Now softbricked, can't get into recovery, is able to get in bootloader, phone keeps rebooting.
Tried factory reset, no success
tried adb/fastboot, my pc wasn't able to detect the phone, no device listed
tried all in one flash tool, trying to reflash recovery, no success either cuz phone not found
when usb was plugged in, 'fastboot usb' shows up on phone's screen, but no real communication established. Windows' notification bar shows htc phone unplugged even though it's plugged in.
I guess usb debugging is off, but i don't know how to enable it
anyone had similar problem, any help will be appreciated
any NYC member here, i'm willing to pay 50 bucks for fixing this, sorry i'm poor, that's all i can afford T_T
Thanks in advance!!
Does it connect via Fastboot? The command is "fastboot devices" to check. You could try to flash a ROM through Fastboot, but I've never had any luck with that. Have you tried the RUU method?
Sent from my HTCONE using Tapatalk

[Q] AT&T Galaxy S4 i337 doesn't connect to PC

I tried flashing CWM recovery onto my AT&T Galaxy S4 and because my phone does not connect to my computer via USB for some reason (the phone charges and my computer recognizes that there's a device in, but I cannot actually do anything with it) I flashed it with Flashify. I rebooted into recovery mode, and I got slapped with the "Unauthorized software has been detected on your phone!" message. So I tried rebooting, and I got stuck in a recovery mode bootloop with the same message. Eventually, I realized if I just go into download mode and reboot by pressing the volume down key, it doesn't try to go into recovery mode. I have already endlessly researched my USB problem, and yes, I DO have USB debugging on. ODIN recognizes that I have an external device in as well, but I haven't tried flashing anything onto my phone with it because I don't want to brick my phone because the connection to my PC is faulty. I'm using the charger that came with the device as my USB drive, so that's not faulty either. I know rooting my phone did this, and I'm pretty sure it's because I missed a step. I used this tutorial to root my phone:
[droid views dot com] /root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/ (I'm not allowed to post links yet, so fix the URL if you're gonna have a look)
When I flashed the I337_NC1_Stock_Kernel, my phone refused to go into download mode and I couldn't flash the I337_NJ4_Stock_Kernel as a result. I'm pretty sure that's what caused it, but I have no idea how to fix it. I'm not an expert with my phone and, despite almost soft-bricking my phone via a corrupt CWM .zip, I'm not a newbie at this either. If I could figure out how to fix this problem, I wouldn't have to worry about throwing myself into a bootloop because I can just use ODIN. I was a sitting duck before download mode rescued me, so I'd like some help as to how I can accomplish this. Any and all help is appreciated. I am 100% certain my device is the right version for that tutorial, I wouldn't try to root my phone without checking all of the simple things first.

Categories

Resources