Related
On Thursday the 29th my phone decided to take a dump on itself. Since then it has not been able to:
-Read any micro SD cards
-Connecting to computer doesn't fully allow USB connections, it detects something plugged in, but nothing else. No ADB, no RUU update, no Sync, etc.
-Cannot charge unless off
All of the above happened while trying to get onto the leaked Froyo. I cleared the cache and wiped the data then this happened.
I already ordered a replacement from Sprint (which I have yet to hear about), but I think I can fix this one by updating the OS.
Problem is that it downgraded me to a version earlier than the one that was on the phone when I first got it. Being on this version is causing a problem by not allowing HTC Update to even see any updates.
So basically I need to update without the use of USB or SD card.
Any help?
Have you tried this http://forum.xda-developers.com/showthread.php?t=695243
063_XOBX said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
Thanks for the quick response.
That seems like it will be of a lot of help, but unfortunately adb cannot detect the phone.
EDIT:
It's also mildly amusing the way anytime someone also had this problem in that thread (the < waiting for device > in adb due to it not detecting the phone) people would just ignore it and continue on.
I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.
kbone213 said:
I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.
Click to expand...
Click to collapse
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.
t3project said:
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.
Click to expand...
Click to collapse
No, it only is able to recognize some things while in HBOOT. Example would be PDANet, which I used to be able to read the phone in the first place on Windows 7 x64, can see that the phone is connected. Adb still reads no devices though.
I'm pretty sure this happened when trying to wipe the phone to do a clean install. My assumption is that it wiped a file that was otherwise necessary to keep the SD card reader and USB port operational.
Is there any way that I can execute the "fastboot oem enableqxdm 0" somewhere on the phone without using adb?
Did another reset on it. Battery was low and turned the phone off without my knowledge. I turned it on to check if I had any messages or whatnot and got a message saying that the battery is low and that the current being given from the USB is not strong enough to charge it and to switch the cable.
What in the software would cause the current to be low?
For some odd reason, I lost adb functionality (i.e. any adb command issued receives "error: device not found"). I looked in Device Manager and noticed that MyHTC was gone! I looked at my phone and USB debugging was enabled and in charge only. I could put it in USB Drive mode and the PC would recognize it as a USB Mass Storage Device so that I could exchange and view files but no adb.
I searched and searched on this issue for hours and installed over a half a dozen "androidusb.inf" driver files several times over. Every install generated the Code 10 error where Device Manager was lacking some information from the driver file and could not start the device. I reinstalled HTC Sync and gave that a try...nothing. Downloaded USBDeview and uninstalled all HTC drivers including the HTC Android USB Device and tried again to no avail. WTF?! What else am I supposed to do?
Well, in a "what the hell, let's give it a try" kind of moment, I decided to toggle the USB debugging off and then back on (and yes, it was checked and on the whole time). WORKS!!! WHAT THE CRAP?!! MyHTC is back in Device Manager and everything is back to normal. I'm glad but irritated!
I share this story in hopes that if someone else stumbles on this problem, they will not have to go through the same headache as I did. Just thought this was odd considering how many times I have plugged and unplugged and never had any problems with adb.
Toggle USB Debugging....so simple. *rolleyes*
Same Issue
I've got the same issue on my EVO 4G. Just installed the latest CM7 and now it tell me device not recognized. If I manually install the drivers it gives me the same code 10. I can't bring up the phone as a storage device and toggling the debugging is not working. Any ideas?
SillyJay said:
I've got the same issue on my EVO 4G. Just installed the latest CM7 and now it tell me device not recognized. If I manually install the drivers it gives me the same code 10. I can't bring up the phone as a storage device and toggling the debugging is not working. Any ideas?
Click to expand...
Click to collapse
You installed the hboot drivers correctly?
Boot into recovery, with usb debugging enabled, connect to pc, it should install the drivers.
Still the same
Even when I reboot into recovery it still gives me "USB Device not recognized." I previously had MikFroyo on my phone with no problems. I'm at a loss.
SillyJay said:
Even when I reboot into recovery it still gives me "USB Device not recognized." I previously had MikFroyo on my phone with no problems. I'm at a loss.
Click to expand...
Click to collapse
You most likely have a bad cable, do you have another one you can try?
Possibility
Not at the moment but that may explain it. Still seems weird for it to just go out right as I change to CM7, but still a possibility. I am going to run and grab my other cable. Thanks for the advice.
No Luck
The new USB cable didn't fix the problem. Also, in device manager, even with the driver installed its labeled as "unknown device."
If I boot into hboot the computer recognizes it.
**update: After rebooting from the hboot, my phone is recognized by the computer however, a disk drive is not coming up in "my computer." I have USB storage turned on but Im not getting anything.**
Any help would be much appreciated!
Sad Day
Apparently the Micro USB port on the bottom of my phone is going bad... I talked with some other people who've had the same problem. HTC knows that the ports aren't very sturdy as well. Well... sad day for me.
Also if you're getting the notice from windows saying that you your device will run faster in a 2.0 usb port and you know the port is 2.0 ... chances are your port is going bad as well.
*****UPDATE*****
Flashed to MikFroyo and none of the above stated problems. I would venture that it was CM7 but apparently everyone else is able to use it so who knows.
Alright to start I had some previous issues with this phone unable to charge. Which I am hoping the case isn't I destroyed USB input. But for starters I have a EVO Revolutionary Supersonic S-Off. Recently rooted very fresh noob. And I installed my first ROM MIUI with an iPhone theme I was unable to connect to my computer I quickly realized. I restored my phone and tried to connect as such but no good. I even went into recovery and mounted my USB storage under my Clockwork Mod Recovery. Still no change. Before I rooted my phone I had some minor difficulties with mount my phone via USB just to even charge, But as I plugged my phone in today I am not able to mount storage however I am able to charge my phone with no problems whatsoever. I am current installing CyanogenMod I believe 7.2.0 to see a if there is a change. So am I able to install a missing driver or anything of that sort on my phone or am I facing a physical issue?
Try using a different USB Cable. Alos try to make sure it's a real HTC USB Cable. The knock-offs sometimes cause issues like this. The other thing you should do is Update your HTC Sync Drivers. You can download them HERE. Make sure you read before you download, so that you do not download the wrong thing . Also go into Menu - Settings - Applications - Development. Make sure USB debugging is checked.
I used 2 USB cables that I had laying around. One is a cable that originally came with the phone the other is Samsung. And I'd have to revert back to stock in order to get those updates? And if I do would I be able to go back to my Cyanogen Mod 7.1 I installed 7.2 and it had major flaws in its ability to access the playstore.
just as a side note the usb port is known to break on the evo. it did on mine
Ive also had a broken USB port on my Samsung intercept I believe it was.
So I bricked my FireTV last night during an upgrade to rbox's latest fw...
Short story is, it got to the Amazon app optimization after the flash fine so I went back to the computer to start working on the second box while it did it's thing. I mistakenly sent the reboot recovery command to the box that was optimizing itself. I didn't notice I was sending the command to the wrong box until I saw that my second unit was not rebooting to recovery.
Needless to say, it now no longer boots to any logos, and does not turn on at all (no light when plugged in, not even for a split second).
What are my options to unbrick? I'm taking a guess that the SD reader/eMMC method is the only one. If so, is it possible to retain an unlocked bootloader/etc with this method? I've read you'd lose it, but I'm not familiar.
If someone could point me in the right direction that'd be awesome. I tried google but it's filled with loads of outdated or unrelated information (mostly debricking if the amazon logo appears) or info from when the initial hardware root method came out.
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
sparkd said:
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
Click to expand...
Click to collapse
At least you can connect with USB! I get no connection at all to the pc with a A-A cable.
I would suggest for you trying to get the timing right and initiate the fastboot commands right when the device is recognized.
You people need to reflash your partitions, this happened to me months ago. Can't search for the thread now, I think the steps were in the FireTV1 5.0.5.1 thread...
my device bootloader is not unlocked. I was following the steps to downgrade firmware in an attempt to unlock the bootloader.
in Win7 Control Panel > System > Device Manager the FireTV1 appears as QHSUSB_DLOAD - i think I am also going to try this ... http://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
thanks for the advice ldeveraux, ill take a look.
Ordered the eMMC adapter from exploiteers. This is likely the only way I'll be able to fix this as the USB A-A cable is not detecting my FTV
Well I managed to get my device talking with an A-A USB cable while waiting for my eMMC adapter. So now to flash
Is there a way to recover with this method without losing the ability to unlock the bootloader? Bootloader was unlocked prior to the brick.
UPDATE: annnddd it didn't work for me. Was getting I/O errors while writing and now the device no longer gives me partitions in /dev/. The usb device still shows up however.
how did you get the /dev/ partition to appear ?
which linux distro did you download / install as I cannot see any partitions on my device
did you use the linux in a VM ? & did you have the windows drivers installed beforehand ?
thanks
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.
Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯
I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.
have we even seen a bricked device yet?
twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.