[Q] Phone on boot loop - G 2014 Q&A, Help & Troubleshooting

So I tried to flash a rom today. Well, I tried to update it. I know I shouldn't have, but I aborted the process because it got hung up on the same thing for 10 minutes. Surprise, everything's screwed up. But don't worry, I fixed it. I literally re-constructed the system image through adb (the system folder was just deleted for some reason) and got the phone to boot again. But then the network wasn't working anymore, so I flashed the rom again and nope still not working. So then I flashed it AGAIN and my phone was low on battery and I was in class and it flashed fine, but then it shut off during boot. And now it's constantly turning on and booting over and over, and the battery is super low, and I can't access recovery. Or the bootloader. No combinations work, nothing. So here I am, completely at my own fault and stupidity. Ideas?
Here's the symptoms:
I plugged it in after class, 0% charge. Oops. Not supposed to do that.
Waited. Waited. Got to bootloader, tried to enter recovery. Not enough battery, waited.
Got to recovery, tried to boot normally, and now it gets the the "powered by android" screen for a couple of seconds, shuts down, and restarts the process.
My theory:
The phone is so low on battery it can't continue booting, so it shuts off. It uses what little battery it has to put the screen brightness on full and boot, repeat.
PDATE:
It's been a good hour or so, and the phone still shows 0% charge and wont boot. It's really hot.

Related

Need help! Possible brick

Hello,
I have a really strange experience with my G1. Last July when I was trying the latest Hero ROM /I do not remember exactly which/, my phone started to act strangely. When I was playing music through the music player, the phone suddenly shut down itself /without any reason/. I turned it on, the phone booted properly, worked for around 5 minutes and died again. This time it refused to power on /nothing happened when I pushed the power button/. From this moment I told myself that my phone is a complete brick, because I tried everything CAMERA+POWER; HOME+POWER, putted on the charger;USB, there was no reaction at all.
Today I have putted the USB cable /without any reason, hope dies last / and my phone suddenly showed a red LED. I pushed the POWER button and the led turned off, blinked and turned off again, when I released the button the RED LED turned itself on again. I tried HOME+POWER without any result, then CAMERA+POWER and it entered bootloader. Then I downloaded RC29 in order to downgrade it. The phone found the image file properly but it displayed the following error: Battery voltage too low, please change battery, I tried it several times, ending with the same error. I rebooted the phone it showed T-MOBILE G1 screen for about 10 seconds and it died again without showing any signs of life.
What should I do? Can this really be caused from the battery? Or is it something else?
The phone was running DANGER-SPL with the latest radio. I have flashed many roms after the installation of DANGER-SPL. The rom previously installed on the device was CYANOGEN MOD experimental /I do not remember the version/.
Thanks!
I don't mean to be rude, but it says low voltage charge battery. Why not do that, or buy a new battery.
Seems the phone doesn't recognize the full battery, I'm having the same problem - my thread here: http://forum.xda-developers.com/showthread.php?p=5307393
The battery I think must be full when flashing otherwise something goes wrong, but it's not bricked. I'm trying a few things...

Alert and FYI!

My phone (which is currently running Incubus26Jc's Android 2.2 FroYo RLS10 NAND) rebooted at around 12:30 AM. I noticed that it reboots, randomly, about twice a day. Not sure of the cause, haven't looked in to it, but normally it comes back to the desktop, like a fresh boot of the phone. So I thought nothing of it.
Last night, however, during the reboot, SOMETHING happened, and it seemed to have gotten stuck in an infinite loop. It would show the boot animation for a while, then lose power... then it would notice the power cable was plugged in, and try to automatically boot up.
If you notice, plugging the power cable in forces the phone to boot all the way into the Android OS. There seems to be no "charge while off" feature, at least for me.
Anyway, this endless loop caused the phone to reboot over and over and over, until the point where the battery was so far drained, that this "hand off" between the boot screen and the actual OS (somewhere during the boot animation) where the phone had to run on battery for a split second, was long enough to cause the phone to power off completely.
I couldn't flash back to Windows (I thought) because the phone didn't have enough of a charge to stay in bootloader mode while flashing the phone. Which was mostly true.
FYI (how I fixed my problem): should something similar happen to you, put the phone in true BOOTLOADER mode (hold the camera button when you press the power button, see the colored bars across the screen), even though the indicator doesn't light up, the phone DOES charge when in this mode and plugged in to a wall charger (and probably while plugged in to USB).
As far as I know, you are required to maintain a certain level of charge to run the RUU because the USB cable cannot charge the phone WHILE FLASHING, but while waiting in bootloader mode, the battery will charge. I was able to let the phone sit at the bootloader for about an hour then started up my phone and had over 70% charge according to Android. Working again!
thank for the 411. i had a similar issue with rls10. went to 10.5 and rls11 and flashed a new kernel, no further issue since

[Resolved]Bricked phone or battery problems?

Hello, I'll start with writing all the things i did:
I flashed JenaMIUI v1.29 succesfully then i waited about 30 minutes at the boot image, then I got the battery out, tried again another 10 minutes stuck at the boot image. After that I reflashed JenaMIUI v1.29 wiped data etc...same thing, stuck at boot image, I got the battery out and back in, one time just after turning on the phone ( before the boot image appear). Then I could'nt start the phone in recovery or normal or download mode. After some tries and leaving the phone for a few minutes i managed to start it normally( but still stuck at boot image) , so I wasn't able to get to recovery, one time I managed to power it up with the charger on, it showed a circle 1/4 full and then went to boot image. Now I'm not able to power up the phone at all, I tried getting the battery out and back in several times. When I connect the charger to the phone with no battery in it, it shows a black screen for a second then nothing. I am not able to start it in recovery or any other way. Is this a battery problem or sth like the mother board ? The bin counter is set to 0 (using triange away), can I take it to service ?
One more thing, when i managed to start it normally and was stuck at boot image i pressed all keys(vol up,down,home,power) and went into a black screen saying something with ARM ..idk.
Is this a battery problem or a brick ? What can I do ?
EDIT: I think the problem was caused by pulling out the battery right after powering on the phone, solution...disconnect battery from phone leave it for 10 minutes, hold power button for 30seconds then turn on the phone in download mode and flash stock...that worked for me
Are you stuck on Miui bootanimation?
Now i can't get it to turn on...i tried replacing the battery , but when i press power nothing happens
Edit: I'm pretty sure is battery problems because I pulled out and put in the battery very fast ...
no, never pull out battery while the device is on splash screen. Wait till boot animation at least. In that moment the kernel is being loaded. This is also causing the recovery bug. People get boot-loop and reset their phone by pulling out the battery. It's actually true, it's the same as if you turn off your PC by unplugging it from power cord.
So if the kernel has some problems because i pulled the battery out while it was loading...can I take it to service ? Can they see what ROM I have installed regardless of my 0 bin counter ? Will they give me a new phone or sth ? Will a lie like...I tried to change the grey case with the orange case and the battery fell out while I reseted the phone work ?
EDIT: I managed to "repair" my phone ! I used a method I found on the internet. I hold the power button for 30 seconds ( while the battery was disconnected) and then put the battery in and I managed to get it in download mode and flash stock rom, now everything works great)
Sorry for the inconvenience, i wrongly packed the rom
RageFoxtrot said:
Sorry for the inconvenience, i wrongly packed the rom
Click to expand...
Click to collapse
No problem...i knew the risks I was taking...and as long as everything turned out fine, It's all good.

Weird battery issue, has anyone else had this happen?

I noticed today that my phone has maintained a 100% charge, even hours after being unplugged. I tried rebooting, but that didn't fix it. I tried to boot into recovery (I have TWRP) to see if I can wipe battery stats, but once I selected recovery, an empty battery icon appeared and the phone shut off. I tried to boot up normally again, and the phone crashed outright during the boot animation and shut off.
After a minute the phone started up by itself, and went through optimizing apps (I plugged it into a charger out of curiosity). Now that the phone was able to boot, the battery is at 5% and finally charging again.
Has anyone else had this happen with their N6, or have any idea as to what might cause this? For reference, I'm running the latest stock image (LMY48I), just unlocked, rooted, and with custom recovery.
Only thing I have seen is apparently wireless charging screws it up. Go into bootloader>bootloader logs and reboot from there. May reset it.

Moto X 2 (2014) Bootloops and restarts on recovery menu

Hello!
I have a XT1097 (that has some battery issues - shutting down at 15%). When I started it while charging it would sometimes enter in bootloop.
Recently I was using it (the battery was low, almost 15%) when it shut down. It entered in bootloop and I couldn't access recovery mode. After the TWRP logo screen it restarts.
After some attempts and after full charges and discharges, I was able to access the TWRP menu. Everything works fine from there.
Yesterday this happened again. I tried a full charge and discharge but nothing happens: still bootloop and I couldn't acccess the TWRP menu.
Have you ever seen anything like that? I wonder if there's any other form of accessing the TWRP menu (via PC or something).
I'm using Lineage OS rom and I didn't notice anything different or strange before this happened.
I've had this happen for over a year now. It's not every time my phone dies, maybe 1 in 100. I've learned how to extract my texts messages then factory reset and start over.
Are you saying if you get to twrp, and click restart from there it'll start properly?!?
You can get out of the bootloop and into bootloader by pressing vol down and power for 20 seconds ish. Sometimes you need to do it multiple times.

Categories

Resources