My phone worked, then I biked 20 minutes to school, and my phone no longer worked. I tried turning it on. My phone got the hottest I've ever felt a phone, and it stayed that hot for about 40 minutes. It is not recognized by my computer when plugged in.
hopefully you've had progress by now, but if not, try using the motorola and xda guides on launching recovery mode and doing some wiping of the cache partition and possibly the device.
Related
my att g2 4.2 rooted stock rom worked normally last night, this morning I plugged it into the car charger and it displayed it was charging with 2% charge present. I pressed the power button the boot animation began I set it down and when I picked it back up a few minutes later to use it...well nothing...the charging indicator led wasn't lit and when I pressed the power button LG appeared for only a split second then went black. when I plug it in same thing, LG logo for a brief second then disappears. I haven't done anything recently except xposed modules, no flashing of anything. any ideas? thank you guys
It happened to me (on other devices) when I let them discharged too far. Just allow it to charge awhile then try to hold the power button
for 10-20secs ... The NookHD+ were the worst in this situation (it won't charge sometimes, I had to plug/unplug a few times to initiate a charge, I was almost about to RMA one of them).
something else that's odd
when I plugged my device into my laptop the laptop acted like I just plugged in 12 different things that all needed to have their disk formatted. what is going on? wierd
pollutedmuse said:
when I plugged my device into my laptop the laptop acted like I just plugged in 12 different things that all needed to have their disk formatted. what is going on? wierd
Click to expand...
Click to collapse
try charging the device in offline mode ( turn it off and let it charrge for a while) and then turn it on . mind wouldnt turn on because of very low charge yesterday. doing this helped
update
I let it charge for several hours, nothing...it appears to be in some kind of boot loop. I can't turn it off all the way, I hold the powwer button for tensec or so and the LG will appear for a second then disapear and then the back light stays on. oh ya, when I plugged it in a few hours ago it wouldn't turn on but the red LED was flashing. I'm not sure how long it stayed on, but it was off when i got back to it several hours later. thank you for your time fellas!
If you can get to recovery at all, leaving it on charge in there. Has saved me in a similar situation.
shriom_manerker said:
try charging the device in offline mode ( turn it off and let it charrge for a while) and then turn it on . mind wouldnt turn on because of very low charge yesterday. doing this helped
Click to expand...
Click to collapse
Could have been the power switch that makes the phone short circuit and goes off anytime.
Sent from my LG-D801 using xda app-developers app
Thank you sirs, unfortunately still no good
it sounds like you had the same thing as everyone else yesterday that had twrp installed and the carrier automatically updated the system.
I could not get my phone recognized by the laptop and had to use pdanet drivers, which finally worked, but I still had to dig for the device. then had to flash back to stock. There is a pretty good thread on this topic, already. Search for it in the developer section. Do not skip any steps, such as setting the date back to jan2012 and turning off the internet. go slow and methodically, or you will miss a step and get frustrated.
I was recently on vacation taking a "Photo Sphere" with my Nexus 4 and suddenly my phone just turned off. It didn't power down, it just suddenly was off. I felt the back of my phone and it was particularly hot right in the center of the phone. Since that event, my phone is highly unreliable when unplugged and will continue to immediately turn off when I either try to use the phone's camera, or sometimes: try to make a phone call, watch a video, and other random things. After the phone has powered off, it gets stuck in a reboot loop. The phone is bootable and works reliably when it is plugged in. When I am able to successfully reboot the phone, when plugged in, I can see that the battery has plenty of charge remaining. The phone will work for hours or minutes after it has been unplugged as long as I am doing very little with it.
Things I have tried so far have been rebooting into safe mode and formatting my phone with the stock Android 4.4.2 image. Both of these things have not worked out.
I'm trying to determine if I need a new phone if there is something else. Is there anything that would be indicated by a crash log and if so, how would I access that log.
Think it is a hardware issue
I can't help but think that this is a hardware issue. So, I just bought a new HTC One (M8). It is a fantastic phone. I am going to keep my glitchy Nexus 4 as a development/test device.
Hello.
I have a problem with my LG G2, it got bricked yesterday. I was playing some game and suddenly it turned off and keep restarting on LG logo. After couple tries with powering off and on it turned on, I wasn't at home so I could not do the backup. After an hour bootloop started again, today after >30 tries it turned on but unluckily I was at the gym at that moment, after 30 minutes bootlooping started all over. I tried over couple hundred times but to turn it on and do the backup but no luck.
I am able to get into download mode but I dont think it's the full one, when plugging into computer it maked couple hardrives saying they need formatting
LG is detected as qhsusb_bulk in device manager.
I am able to get into factory settings but I don't have CWM. My device is not rooted. Probably it doesn't have usb debugging on.
Oh and theres one strange thing, I cannot turn the phone off (during bootloop) when it's plugged into charger, if I hold power button a red led blinks 8 times.
Is there any chance I could backup my data or fix it without erasing? It's very important because there are over 3 thousand photos.
I will be really grateful for help.
TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
walter77d said:
TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
Click to expand...
Click to collapse
Try the apps such as Ampere which shows battery info.
I don't think so Non-Turbo charger can lead to affect the battery life but using a cheap charger does.
Long story short, I have an AmazonBasic bike phone mount, I had my PH-1 placed in it for weeks, but one day after a ride and taking a break, when I got back on the bike I noticed my phone was just bootlooping on and off, I noticed the power button was held in by the side grips of the mount... since that day (2 weeks now) the most progress I made was the phone doesn't bootloop, it just stays on the logo, I cannot power off the device, I can't get into recovery, I left the battery drain and off for 48 hours, left it sit on the logo for hours and hours, I even tried to fastboot but CMD doesn't pick the device up, Device Manager (Windows 10) does show PH-1 at the top, but I can't do anything... Bootloader screen shows Device State = Locked.
I'm at a loss here and just about to throw the phone in the garbage as I'm starting to feel this is borked completely... I'm hoping someone out there might have some sort of magical fix under their belt that I could try. From the research I could find, fastboot wiping the device seemed like the only option but I can't get the PC to find my device.
Omnipotus said:
Long story short, I have an AmazonBasic bike phone mount, I had my PH-1 placed in it for weeks, but one day after a ride and taking a break, when I got back on the bike I noticed my phone was just bootlooping on and off, I noticed the power button was held in by the side grips of the mount... since that day (2 weeks now) the most progress I made was the phone doesn't bootloop, it just stays on the logo, I cannot power off the device, I can't get into recovery, I left the battery drain and off for 48 hours, left it sit on the logo for hours and hours, I even tried to fastboot but CMD doesn't pick the device up, Device Manager (Windows 10) does show PH-1 at the top, but I can't do anything... Bootloader screen shows Device State = Locked.
I'm at a loss here and just about to throw the phone in the garbage as I'm starting to feel this is borked completely... I'm hoping someone out there might have some sort of magical fix under their belt that I could try. From the research I could find, fastboot wiping the device seemed like the only option but I can't get the PC to find my device.
Click to expand...
Click to collapse
If the power button doesn't work and you can't get into fastboot mode then you really can't do much
Sent from my Pixel 3a using Tapatalk
Did you try adb rather than fastboot? Or does the computer just not recognize the device is connected at all? In that case, try different cables, computer and make sure to use a USB-A to C cable, not C to C. Use a USB 2 port, not USB 3.
A last resort before it hits the trash can, open it and disconnect the battery for a bit.
Omnipotus said:
Long story short, I have an AmazonBasic bike phone mount, I had my PH-1 placed in it for weeks, but one day after a ride and taking a break, when I got back on the bike I noticed my phone was just bootlooping on and off, I noticed the power button was held in by the side grips of the mount... since that day (2 weeks now) the most progress I made was the phone doesn't bootloop, it just stays on the logo, I cannot power off the device, I can't get into recovery, I left the battery drain and off for 48 hours, left it sit on the logo for hours and hours, I even tried to fastboot but CMD doesn't pick the device up, Device Manager (Windows 10) does show PH-1 at the top, but I can't do anything... Bootloader screen shows Device State = Locked.
I'm at a loss here and just about to throw the phone in the garbage as I'm starting to feel this is borked completely... I'm hoping someone out there might have some sort of magical fix under their belt that I could try. From the research I could find, fastboot wiping the device seemed like the only option but I can't get the PC to find my device.
Click to expand...
Click to collapse
Done the same thing, luckily I noticed a minute or two after I put phone in mount & it rebooted normally, bring back the old Nokia power buttons on the top ?
Recharge your battery to make sure you have enough power to boot properly. Then try a forced reboot by holding both the power button + vol down buttons at the same time for 10s (think this does a simulated battery pull)
(Though obviously if you have a power button stuck on this won't help, some old Samsungs got this & people reported banging phone on hard surface sometimes fixed but with newer screens being so close to the edge & our ceramic body you run the risk of cracking screen/ceramic!)
I'm going to add to @IronRoo's advice by reminding that when plugged in, the device tries to boot. It's helps to unplug when doing button commands.