Oh dear - I bought a One Mini from eBay just before Christmas, was brand new (still sealed). Was really enjoying the phone until today when it just turned off in the middle of me browsing the net on it. It was on full charge!
I've spent ages trawling around online...tried all the hard and soft reset key combinations, none of these work. Have tried charging it - the LED lights don't come on, nor does the screen. I've tried plugging it into a laptop but it fails to install a driver, it just stays as 'QHSUSB_DLOAD' in device manager. Tried installing the HTCOneToolkit and using that driver button, but it seems to just launch the first pop-up then does nothing, tried doing an install driver and browse to the HTC directory but that doesn't find the driver. Tried different USB ports, resetting the laptop, tried HTC sync manager, tried standing on one leg and screaming, but no.
Madness, all I was doing was browsing an ebay shop on the Chrome app, how has that bricked it?!! Any ideas how to fix?
Have contacted the seller to see if they have a receipt failing that, going to try HTC direct. What a faff.
Related
This happened a couple of weeks ago, but I decided to post it because I want to help others and I am always open to some explanation as to why this happened. By way of background, I have had 2 HTC MDAs, a G1, and a Dash, amongst over phones. I've been flashing ROMs for probably 5 years or so, and I'd specifically flashed the Dash at least a dozen times. About two months ago I finally got off Windows as my primary OS. I am running Ubuntu 9.04 and Sun's Virtualbox on all my systems with Windows VMs. It has worked brilliantly, and by using this setup I still have access to all my apps that will only play nice with Windows including Outlook and Activesync. I've even flashed a ROM to the Dash from within Activesync before.
HOWEVER, in early July I tried to flash the 3VO 7.01 ROM to the phone using the same cable and same laptop I've used before. Battery was fully charged. I got some error about communications being interrupted or something and it walked me through recovery and restarted the flash. I got some other error and had to take out the battery and after I booted the phone again I restarted the flash and I got a similar error. When I looked at the phone, it was COMPLETELY DEAD. It would not turn on at all, even holding the center button, two soft buttons, etc. I took it to the Tmo store the next day and they plugged in a new battery and nothing. Nada.
If anyone has used Virtualbox for this, when the flash script is run and it goes through the steps and switches modes it will change the recognized USB device type at some point. To complete it in the past I had to re-enable that USB device for the VM to actually start the flash from the tricolor screen. This time when it switched modes was when it died. I didn't realize it could brick this way, but apparently it can and I have made a note to self not to flash from a VM Windows box ever again.
Just thought I'd pass it along as a warning to others.
Can u reach the bootloader by holding the camera button while powering on?
A red-blue-green screen should appear..
No, in fact it shows no sign of life at all, though it worked fine before this event. It won't even show a charge light when plugged in.
Hmm this is something that should be posted as a warning on the wiki for everyone to remember when updating their phones. I have never used a virtual machine for any type of flashing of any thing.
Yup, and I bet we all expect it is going to become a more common occurrence, even if it isn't a mainstream situation...
Here is what happened on my month new Galaxy Nexus.
1. Listening to mp3 via Bluetooth headset
2. Playing a game
3. Standing up
4. On a train
Sound stopped working across everything, in the game and on the mp3. Tried killing the applications and reloading, the mp3 player refused to even start the mp3.
Rebooted the phone, well, I turned it off. It has never turned back on. Tried removing the battery, all that, nothing.
Got home, tried plugging in the USB into a PC. Nothing. Tried booting into recovery mode, nothing, other than the PC claiming to have found a new device.
I haven't plugged it into a PC in recovery mode before. I haven't even seen recovery mode on the Galaxy Nexus.
I was running OTA Vodafone UK 4.0.2 I hadn't even considered rooting it or anything.
Anyone know if this is salvageable or had the same happen to them?
Hi. If popping the battery does no good I'd get it replaced without any further investigation. Sounds like hardware fail, so long as you are sure you have not got it wet or caused any damage to it.
Sent from my Galaxy Nexus using XDA App
If you cant bring it back on after a battery pull then its a dead phone for sure
I had the same problem last month. An usb jig solved the problem.
USB Jig?
Any more details? Something you can point me at?
Cheers
Found this:
http://forum.xda-developers.com/showthread.php?p=20504509
Appropriate?
So does the phone show anything at all? Does the screen come up for any amount of time? Can you get into bootloader?
So for completeness I have exactly this issue:
http://forum.xda-developers.com/showthread.php?t=1384415
Basically this paragraph:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Click to expand...
Click to collapse
Sounds like a USB Jig might do it. But in this case its back to vodafone and jumping through those hoops.
For the record I hadn't done anything at all to the phone than a normal consumer would. i.e. no rooting, hacking, booting, fruiting or cheesing.
It just died.
Hi Recently I wanted to run after installing a new rom the phone and instead of the expected effect of the phone vibrated 5-6 times, turn on the green light, the screen is black and nothing. After connecting to the PC starts to look for Qualcomm CDMA Technologies driver MSM but to no avail. POWER + VOL-does not work. Does anyone have any ideas? I would add that I took out the batteries for 10 minutes and put it back in and start up normally, I walked into 4ext and rom threw again, but the next day the problem returned. Removing the battery is no longer helps. Someone knows the solution?
Luniopl said:
Hi Recently I wanted to run after installing a new rom the phone and instead of the expected effect of the phone vibrated 5-6 times, turn on the green light, the screen is black and nothing. After connecting to the PC starts to look for Qualcomm CDMA Technologies driver MSM but to no avail. POWER + VOL-does not work. Does anyone have any ideas? I would add that I took out the batteries for 10 minutes and put it back in and start up normally, I walked into 4ext and rom threw again, but the next day the problem returned. Removing the battery is no longer helps. Someone knows the solution?
Click to expand...
Click to collapse
Post in the link in my Signature (Ace Think Tank). I've seen this problem before but I've never really learnt the solution. An awesome guy called Glevitan will probably help you
I tried to install a new battery, screwed the phone up in the process and smashed it out of frustration.
The good thing is that the battery works and apparently very well, just can't use it or the phone!
When I connect via usb to my laptop, it shows in device manager and at one point it also showed a storage drive (in device manager, nowhere else).
When i switch it on, it seems stuck in a boot loop (vibrates, connects via usb, wait...disconnects, vibrates and so on).
The little button bits on the volume piece have fallen off and without a microscope, i doubt i'll be able to find them, however, is there any way or point in getting into fastboot?
XL ? Wrong forum, you have to be in the at&t HTC one xl forum
My wife's google nexus was dropped & then ran over quite badly on the street, screen smashed and won't turn on, except for making a vibrating gesture (I assume power to the vital hardware is still there).
I hooked the phone to the laptop and drivers tried to instal OMAP4440.
After searching online for this, I am to believe this is the black screen of death!
I am in need of pulling all video & photos off the phone, I assume this is do-able as the laptop picks up the OMAP4440 driver instal command even though I currently do not have the driver installed.
Should I instal the OMAP4440 driver, will it give me the ability to gain what I need, or is there an alternative method to get the files?
Serious help & advice needed.
---
smash'n