So yesterday morning the Wifes 5X crashed and rebooted, then started looping on the "Google" splash screen. Having been unaware of the common bootloop issue i did some reading and realised what was going on.
So i stuck the phone in the freezer for an hour, then fired it up. This time it managed to get into the OS, and i switched on the "OEM Unlock" option as well as turning on ADB debugging, then shut the phone down.
So far so good, but then it all took a turn for the worse.
I booted into fastboot, and connected the PC. The PC reported that "Windows could not recognise the USB device" and it appeared in device manager as "device descriptor request failed".
I've tried 5 different cables, same error. I've tried three different PC's, same error. Thinking i was doing something wrong, this morning i booted my own 5X into fastboot, connected that to the PC, and it immediately was detected properly and shows up as it should. So it has to be an issue with the broken phone.
Any ideas? I've stuck it back in the freezer now, and will try it again straight out the freezer and see if that makes any difference.
Unfortunately, i bought it used from ebay, so i dont seem to have any warranty recourse.
Aragorn84 said:
So yesterday morning the Wifes 5X crashed and rebooted, then started looping on the "Google" splash screen. Having been unaware of the common bootloop issue i did some reading and realised what was going on.
So i stuck the phone in the freezer for an hour, then fired it up. This time it managed to get into the OS, and i switched on the "OEM Unlock" option as well as turning on ADB debugging, then shut the phone down.
So far so good, but then it all took a turn for the worse.
I booted into fastboot, and connected the PC. The PC reported that "Windows could not recognise the USB device" and it appeared in device manager as "device descriptor request failed".
I've tried 5 different cables, same error. I've tried three different PC's, same error. Thinking i was doing something wrong, this morning i booted my own 5X into fastboot, connected that to the PC, and it immediately was detected properly and shows up as it should. So it has to be an issue with the broken phone.
Any ideas? I've stuck it back in the freezer now, and will try it again straight out the freezer and see if that makes any difference.
Unfortunately, i bought it used from ebay, so i dont seem to have any warranty recourse.
Click to expand...
Click to collapse
I'd still go on LG website and give the imei number to a rep and see if it's under warranty. You'd be surprised. They didn't require me to show proof of purchase when I sent mine in a few weeks ago.
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.
Hi there, my Verizon Galaxy Nexus is giving me trouble.
Several weeks ago, a glass of water was spilled on it. I quickly removed the case and battery, wiped it off and set them somewhere dry. A week later, when I tried to turn it on, it almost booted right before turning back off. I tried the usual (battery pull, holding down volume buttons), it wouldn't turn on at all. Another week passes, and it boots. The camera app didn't work at first (force close upon opening), but a week or so later it started again, works fine and takes clear pictures.
My problem is that the USB port isn't detecting properly on my computer. I've replaced the USB port, and that didn't solve it. The old one also would not properly recognize when it became unplugged. Windows, however, does not show anything in My Computer or in Device Manager, no hardware detected sound or anything. My phone doesn't do anything either, nothing in the notification area (charges normally, however). ADB does not work while booted, only in recovery. Fastboot does work. How should I proceed? Thanks.
New phone.
Months ago I rooted and flashed a lollipop stock ROM. It's worked flawlessly ever since, so I doubt it's the cause of this problem.
Suddenly my (international) G3 has started doing a cycle of freezing, rebooting, staying awake for a few seconds and then freezing and rebooting again. This started happening this morning, while using the "reddit news" app. I don't think it's related to the issue. Now, after a few hours, it's stopping the boot cycle at the LG logo, and it doesn't seem to go anywhere from there.
Previously, when it did boot and stayed awake for like 10 seconds, it showed some strange behaviour. Wifi didn't turn on, the phone got pretty warm, and whatever mode of USB connection I chose, USB debugging never turned on despite being enabled in the developer options.
"adb devices" in windows cmd doesn't show anything in any part of the cycle, so I can't take a logcat. The phone isn't awake for long enough to do it on the phone either. How can I find out what's suddenly causing this? Has anyone else experienced it? Trying a hard reset via pwr + vol down just shows me the LG logo again.
Does it still go into download mode when you press volume up and plug in usb cable?
itsbighead said:
Does it still go into download mode when you press volume up and plug in usb cable?
Click to expand...
Click to collapse
I assume so. I've never used it before so I'm not sure what it looks like - but I do see a little box in the middle of the screen saying "Download Mode", with a little graphic underneath.
Hi!
I've got a Note 7 from Germany, I occasionally buy second hand phones from a shop. This one had a 0% battery so I've used a battery to turn the phone on.
I'm sure it has FRP, but that's a different problem.
My problem is that when I plug it in and the phone is turned on, it shows the Battery icon then the screen turns off. If I plug it in when the phone is turned on, then the don't use this device message is showed and that's it.
If I boot into download mode, my PC doesn't recognise the device, it says something like "Device descriptor request failed".
Any idea how to bring it back to life?
Thanks in advance!
Edit:
After reinstalling the drivers multiple times, I was able to make it work, now it’s time to remove the FRP
I am running the latest Android 13 QPR beta release. Ever since I updated, I've been having a connection issue in every app. Every 2 minutes or so, my phone "loses connection", regardless of Wi-Fi or data, regardless of signal strength, any app will struggle to connect for a few seconds. My phone doesn't actually lose connection, it's weird. Most apps will just reconnect and go on about it's business after about 10-15 seconds of connection issue, but some refuse to "reconnect", so I have to close the app and reopen. After weeks of this, I decided to reformat my phone and go back to the stable android 13 release, by opting out of the beta and receiving the OTA to go back to stable. I did this with the intention of installing a custom ROM.
However, the OTA took an abnormally long 2 hours to complete. Upon completion of the update, my phone gave the the installation successful message with a restart. Upon restarting, I was greeted with the bootloader and the message "No operating system installing. Cannot boot". After a few minutes of restarting and fumbling around to no avail, eventually it booted back into my beta build. I breathed a sigh of relief. This was, however, not the end.
At this point, I thought "that was frightening. Best off just to try to install the factory image through ADB". So I go on to plug in my USB cable, and I see the notification that USB was connected. I try to click the notification to switch to file transfer mode, and then it disappears, and Windows loses connection to my phone. I'm now no longer able to get my P6P to recognize that it is plugged into a computer, and my computer refuses to detect my phone. It does however charge off the PC connection though. I've tried updating drivers, switching cords (including the factory cable, the usb-c to a cable that I usually use with this phone with success), USB 2 ports, USB 3 ports, restarted my computer, factory reset my phone, quadruple checked USB debugging was enabled, and nothing seems to work.
I'm stuck on the beta build. Cannot do anything with ADB. Cannot do anything with recovery mode, as apply update from SD just returns an error. I'm hoping I'm just missing something simple. Are there any other suggestions or ways to get around needing a computer for anything?
Thanks for reading!
This can be closed. After hours of frustration, I tried a cord that doesn't seem like it should work. It's a "universal" cord (one with a micro-USB connection and an adapter for USB-C and lightning). Never give up, you never know ¯\_(ツ)_/¯
xChowderrrx said:
This can be closed. After hours of frustration, I tried a cord that doesn't seem like it should work. It's a "universal" cord (one with a micro-USB connection and an adapter for USB-C and lightning). Never give up, you never know ¯\_(ツ)_/¯
Click to expand...
Click to collapse
I always have mtp set as default. Better to be safe than sorry
I do, as well. Connection wasn't being detected on either side. I was also getting a pop-up on my computer saying something along the lines of "the last time this device was connected, it malfunctioned. Windows cannot recognize the device." That's why I initially thought drivers, and only tried a few cords. But I got desperate and reached deeper in the bin. Thanks for the pointer, though.