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
Related
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.
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
I have a galaxy nexus, uses the Eclipse-2.1-toro-build4 rom (old I know, but it was smooth and worked for me, so I kept it).
Last night, after keeping it in my backpack during a bike ride, I went to go use it. The screen is black and I noticed a few solid color black lines running through the screen. Screen is likely dead, my guess.
I am able to boot up the phone fine. I see the L..E.D. notification light come on, and when I get new emails (I left it on wifi the last time I used it), I'll hear notifications...
But, when I try to connect my phone through usb and attempt to connect to it via adb, I'm getting a device not found. I've connected my phone dozens of times using this method without a problem.
Anytime I issue a command with adb from my computer (ubuntu 12.04), it gives me the device not found although the device is connected via usb. This happens even when the galaxy nexus is displayed in nautilus, so it's clearly connected to the computer.
Any idea how to access my sdcard with adb then or to troubleshoot why it's not being read?
Does your phone have a screen lock? Try pressing the power button to unlock it and see if you can find the unlock button (assuming the touch screen still works). If you have a pin, it might be quite hard to get it
I can't access adb whilst my phone is locked. I think it is a security measure.
Hi everyone,
first off, I've spend days now trying to find a fix. If I've missed anything, I'm sorry, it wasn't for lack of trying.
Here's the situation: I have acquired an HTC One X earlier this year which has worked quite flawlessly. I went ahead and unlocked the bootloader and installed a custom recovery. However, since I handed the phone off to my not-so-techy sister I did not use a custom ROM, and after the HTC update failed with the custom recovery I reversed that as well. The device should now be stock everything with unlocked bootloader.
After a few months my sister encountered heavy problems, though. She described them as battery related (wouldn't turn on correctly) and eventually she moved to a new phone. Now I have gotten the device back and I am trying to fix it. After charging it I managed to have it boot once. However, I but it to the side and wanted it to load some more. Ever since then the screen doesn't come on. The charging LED seems to work fine (eventually switched from red to green, too, indicating that the device is fully charged) and the button backlight still works, too. Most significantly though, the device is recognized as MTP device in Windows: I can access all the data in the storage without problems.
I have read that there is an issue with the HTC One X and the display connector so eventually I went ahead and took the device apart. It's lying in front of me now in pieces, but I still couldn't get the screen to come alive. The obvious conclusion would be to buy a new screen but the device doesn't feel like it's worth the investment. Besides, I would like to know for sure that it's the screen before I do anything.
So I turn to you guys and ask if you have any idea how I could access the phone via my computer. I tried to boot it up in bootloader mode but due to the strange standby methods HTC is using and not seeing anything on the screen I haven't been able to do that yet: Whenever I connect my USB cable it's recognized as MTP device, not ADB. Debugging seems to be deactivated so that doesn't seem to be an option. Does anyone have any idea how I could get the phone to talk to my computer (i.e. get into the bootloader or ADB screencast for sure)? With my Galaxy S I could simply plug in this dummy micro USB and would be sure to end up in download mode.
Any help is appreciated!
tl;dr: HTC One X screen is dead but LEDs work, is recognized as MTP device. How to make it talk to the computer?
Thanks,
rien
Alright, sometimes just posting stuff like this helps already. I was now finally able to get the phone into fastboot (apparently) and it's reacting to the fastboot commands. I suppose the next step is to load CWM and connect via adb. This way I can at least do a factory reset.
Does anyone have any ideas regarding the original issue with the screen? Especially since it does seem to work occasionally. And doesn't show any fragments...
Can I enable USB debug mode from within the recovery to work in the system?
I've had my Nexus 7 for a while, and I actually recently got a Nexus 10 and handed off the 7 to my fiance, who was using it to browse tumblr and read fanfiction, and that's about it as far as I can tell. I do have it rooted and unlocked and running Paranoid Android Beta 4.6 (and has been for a very long time), however since I haven't messed with it in so long I couldn't tell you anything else about it (kernel, etc.)
Since I know she wouldn't have tried to do anything like update or anything like that, my guess is that the problem is stemming from the fact that she just lets it die a lot, then charges it. She charged it all night and it would not turn on so she had me look at it. I tried everything I could think of, holding power for various amounts of time, both alone and in combination with either of the volume buttons to try to access fastboot or just anything. I should mention I even followed Google's troubleshooting steps, which involved strange charging times, having it plugged into the PC for a spell, then unplugging and replugging and trying to power on. But the battery icon does not even show up. The screen just stays black.
I plugged it into my computer to see if anything would happen, and it showed up in Device Manager as QHSUSB_DLOAD, so I googled this problem and it seems to be some sort of hardbrick where the bootloader is corrupted, and some people have found solutions for other devices, mainly HTC devices, but there doesn't seem to be anything that particularly pertains to this device. If I hold down the power button while plugged into the PC it will intermittently "disconnect" and "reconnect" (Windows plays the sounds) and disappear and reappear in Device Manager.
I'd like to try to fix it if I can, but I'm not gonna send it in for repairs/replacement or anything like that. I'd rather just buy a brand new device at that point, but if anyone somehow has a solution, I'd gladly welcome it.
Thanks so much!