Please help, my phone sporadically broke after a period of not using it for about 8 hours. I don't know what happened, the battery charge was ~70%, the last time I checked. I tried to plug it into a wall socket (for a few hours), but the phone won't vibrate, and the LED won't turn on. I tried forcing a reboot, by holding power+volume+ for about 5 minutes, but still no luck. Lastly, I plug it into my PC (Windows), and something interesting happens. Windows starts to install this new device driver, and then when I check on devices and printers, it shows up as "Unknown USB Device (Device Descriptor Request Failed)" Then, when I right-click, and then choose troubleshoot, it returns "Unknown USB Device (Device Descriptor Request Failed) is not working properly." Then there's the warning sign, and "Detected"... I even tried adb devices and fastboot devices, but those returned nothing, too..... Please help!
Did you ever figure this out? My sister in laws phone just started the same thing.
Related
I installed the drivers for the phone (v3.0.0.007 & v3.0.0.017), rebooted PC since it wasn't working when I plugged the phone in, then plugged in phone which worked (couple devices showed up in device manager), fired up ADB which I already had installed for my OG Droid & Nook Color, "adb devices" returns nothing. Replug phone in, select HTC Sync for the method, verified USB Debugging was showing up, "adb devices" - still nothing. Now in Device Manager, I don't have any HTC Android devices like I saw a minute ago. Now I just have "Unknown device" and it won't accept the USB drivers from C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64. When I plug in the phone, it no longer prompts me what I want to do on the phone, it just connects USB Debugging and nothing else - no disk drive, no HTC Sync, no nothing. Rebooted PC & phone, same deal when I plug in the phone - it just has an "unknown device" and doesn't let me choose HTC Sync or anything. I made sure the check box is still checked for "ask me" under settings -> connect to PC.
I am reinstalling drivers now and am not going to install the full HTC Sync package. Maybe that'll work better. So far, it appears that the drivers and/or HTC Sync software are crap.
Unplugged phone
Uninstalled all 3 HTC pieces in appwiz.cpl
Installed v3.0.0.007 drivers
Plugged phone in
Got message about failing to install hardware
Device manager now shows: Other devices - Android Phone
It did this the first time I tried installing stuff and a reboot of the PC fixed it, so I'm rebooting...brb!
No luck still. Trying some more stuff. If anyone out there has any ideas, let me know. My phone still won't prompt me for action when I plug in the USB.
Uninstalled HTC USB drivers (v3.0.0.007)
Installed HTC Sync package, including HTC USB drivers v3.0.0.017 & USB BMP drivers
Plugged in phone - same problem
Running out of ideas. Might do factory reset on phone. Might try another PC.
OK I think I figured it out. You have to turn off USB Debugging. As soon as I did that, my PC found new hardware and the phone displayed the expected prompt. It mounted an E: drive and wanted to load TL-bootstrap.exe, which I didn't do.
When I go to the debugging options, it shows as already on even though I just disabled it. I uncheck it and recheck and it goes back to broken state - PC shows an unusable "Android Phone" under Other Devices.
Hmm...now what?
Had to go to a meeting, so I did a factory reset on my phone and set it to not sync, so it should be just like it was when I first got it from Verizon.
Without USB debugging turned on, the phone appears to connect to my PC properly, but HTC Sync says "no device connected" and the phone says "Unable to find HTC Sync on your PC. Please make sure that HTC Sync is installed and opened blah blah blah".
The only hardware that appears in device manager is a pair of "HTC Android Phone USB Device" in the Disk Drives section, as well as a 3rd one under DVD/CD-ROM Drives.
Since HTC Sync isn't working, I guess the drivers are completely failing. I hate crappy drivers. Might have to just mess with my phone from a different PC.
Now USB Debugging won't load at all. I toggle it on and off, disconnect and reconnect USB cable, toggle it again.....nothing happens. Seems to be going downhill quickly.
Uninstalled all HTC software again, including a WModem one that I didn't see before (could be leftover from rooting the wife's Incredible).
Plugged phone in to see what it does - pretty much the same as when all the HTC software is installed. That is, 3 drives mount when USB Debugging is turned off. Turning debugging on is working now, but there is no driver installed on my PC. However, it doesn't matter if I install drivers, it still won't use them.
Does anyone know if there is a special driver for Win7 64-bit?
I have Windows 7 x64 Pro at the office and home, and am using the drivers from HTCDriver3.0.0.007.exe just fine. Try doing a hard power cycle on the phone (power off, then on -- or yank the battery) and restart your computer. Use a USB port that is on the back of your motherboard or from a trustworthy powered USB hub (undervoltage will cause you all kinds of grief). Try another cable. Use charge-only mode, not HTC Sync.
Sorry for the spam earlier. Ya, it was just my laptop. My home PC is Win7 x64 as well and it works fine. Wireless tether is workin'. Loving the Rezound!
REPLY:ADB not seeing the device
yeahh i got so scared because ADB would not recognize my Rezound after Re-Flashing the Stock Rom because for some reason my phone suddenly kept re-booting over and over non stop.. so anyways.. i found a fix. well it worked for me at least. i re-installed the HTC drivers and then on the phone i turned "USB Debugging" On. then i plugged the phone to the computer, opened up CMD and when typing
"cd c:\android-sdk-windows\platform-tools\ ENTER"
"adb devices ENTER" it came back as
List of devices attached
HT19YS204824 device
Before it would say error. it worked for me. hopefully this is at least of some help
I made an error in the rooting process somewhere, though I don't know where. I was trying to use CWM Recovery to install Cyanogen
Somewhere along the line, while trying to unlock the bootloader and flash ROM, I made a grave mistake.
Now, my Motorola Photon 4G is bricked. It will show nothing on the screen.
When plugged into the computer via USB, the computer will see that a USB device is plugged in, but give the message "USB Device Not Recognized" - in "Device Manager" it shows up as a "USB Mass Storage Device" with a yellow triangle with exclamation.
When plugged in to USB, the LED light is white (which is a color I had never seen before when the phone was working). Then sometimes if I try to boot the phone with Power+VOLDOWN the phone will restart or something (indicated only by the Windows notification sounds of disconnecting device/ connecting device) and then the LED light is green, as it used to show when fully charged.
Every method of fixing a bricked Photon I've found seems to require that the computer can already recognize the phone in some way. I've tried RSD Lite and others.
I just seem to be very lost here, and maybe I'm missing something obvious. Is there anything that I can do to troubleshoot this issue further?
You may want to try to charge your battery using a different phone or some external charger.
Enviado desde mi MB855
mammolastan said:
I made an error in the rooting process somewhere, though I don't know where. I was trying to use CWM Recovery to install Cyanogen
Somewhere along the line, while trying to unlock the bootloader and flash ROM, I made a grave mistake.
Now, my Motorola Photon 4G is bricked. It will show nothing on the screen.
When plugged into the computer via USB, the computer will see that a USB device is plugged in, but give the message "USB Device Not Recognized" - in "Device Manager" it shows up as a "USB Mass Storage Device" with a yellow triangle with exclamation.
When plugged in to USB, the LED light is white (which is a color I had never seen before when the phone was working). Then sometimes if I try to boot the phone with Power+VOLDOWN the phone will restart or something (indicated only by the Windows notification sounds of disconnecting device/ connecting device) and then the LED light is green, as it used to show when fully charged.
Every method of fixing a bricked Photon I've found seems to require that the computer can already recognize the phone in some way. I've tried RSD Lite and others.
I just seem to be very lost here, and maybe I'm missing something obvious. Is there anything that I can do to troubleshoot this issue further?
Click to expand...
Click to collapse
not.a.troll is probably right...I'd try charging the battery with an external charger. It's a pain in the rear, but that's best shot, then try starting over. It seems to me that you may have started the process when you weren't fully charged.
No, not a troll, despite my poor typing.
Thank you for both of your suggestions about charging the battery in some other way.
I'll try that and see if it changes things.
sorry to bring old topic back, but can you tell me how`s your phone now? because i`m having the same problem here, My photon can`t boot, not even going to fastboot when i press power & vol+
really need some help here,.. anyone??
Thanks...
Hello everyone,
I'm writing in the hopes of receiving some guidance re: a small "challenge" a friend issued to me. As you can probably guess, the half of the story that involves my friend's actions on the tablet are word-of-mouth, seeing as the device was given to me in a totally bricked state. Hope you'll be able to assist me somehow!
After using his Galaxy Tab P7500R for some time, the battery stopped charging. He supposedly tried a complete wipe and system restore (for which he was unable to guarantee a successful conclusion), and then the machine ran out of whatever juice had been left behind during the last successful charging cycle, and turned off completely, showing no signs of life whatsoever.
This is where I come in - I was given the "expensive ornament", accompanied by the words "have fun, I've already bought another one".
Symptoms are the following:
1) Powering the device on doesn't work. While the device is connected to the house power grid, there are no indicators of the device doing anything.
2) Connecting the device to a USB port on my laptop, and holding the power button, after 15 seconds my PC signals a device being disconnected via sound, and that disconnection sound is almost immediately followed by a couple, rapid, "halved" 'device connected' sounds. On the other hand, while the device is connected to a USB port on the laptop, if I hold the power button together with volume+, all I hear every 15 or so seconds is the "Device disconnected" sound.
3) After using USBDeview to remove a driver named APX, and after reconnecting the device to the computer via USB (sometimes this requires holding the power button, sometimes all it takes is a reconnection), I will hear a full "device connected" sound; then, an "installing driver" window will open, for the APX driver, which, after looking for the appropriate driver via Windows Update, will give me an error message ("no driver found") on the "unable to install device drivers" window.
4) Opening the device (out of warranty for over a year), and utilizing some testing tools have shown that power does reach as far as the motherboard, and that the batteries are somewhat charged at the moment.
Any ideas?
Thanks in advance for your help!
Lightside
[UPDATE 1]: I successfully installed the NVIDIA USB Boot-Recovery drivers for mobile devices. The tablet is now detected as being connected to my laptop, sounds and everything.
Following some instructions I was able to find on these forums, I tried installing NVFlash, and running the --bl bootloader.bin --go, receiving a "Rcm version 0X4 - Command send failed (usb write failed)" message.
From what I gathered, this is evidence of a locked bootloader. I wasn't able to find any posts dealing specifically with a bricked device that is only recognized in APX mode, and how to unlock the bootloader in such cases. Is there a guide available by any chance?
Update 2 :
I've extracted the battery, but I seem to be unable to remove the residual charge, as the device shows up (APX) as connected, as soon as I plug in my USB cable.
Anyone? :/
Up?
Hi,
maybe one of the experts can help...
I have a LEMAX2 with X820_20S_ROW_CUOCO92 ROM.
Since half a year or so the USB-Connection to the PC does not work anymore. Tried several cables and several PCs, no change.
I can boot the phone in RECOVRY Mode, but it It shuts itself off immediately.
I can enter fastboot mode, but the phone is still not recognized by the PC.
When I connect the phone via MyPhoneExplorerClient, WLAN works, but MyPhoneExplorerClient says 'USB-Cabel 'Not conneced.'
When I unplug and re-plug the USB-Cable, for a short time MyPhoneExplorerClient says 'USB-Cabel 'conneced', but no setting option for USB configuration can be found and after a second or so MyPhoneExplorerClient shows 'USB-Cabel Not conneced' again.
I tried to find out how to change or repair the firmware but all howtos require a USB Connection.
Mayby I accidentaly removed some system software responsible for the USB Connection?
Any idea?
:crying:TWSMS
I seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.