something i never noticed as i never turn phone off - Huawei Ascend Mate 2

im on cygon 13 nightly, and i notice sometimes if you turn phone off and plug it in charger it reboots into showing the battery level and then doesnt want to boot up, sometimes after a time or 2 boots up sometimes have to force it into twrp and then reboot from there and it boots does same with like 3 builds of cygon 13..wondering what the hell

Related

[Q] Endless Reboot with custom ROMs

I've been able to flash custom ROMs onto my HD2 without problems for a long time.
However since recently when I flash a ROM (e.g. radio) it goes into a constant reboot mode:
- Does not turn on without power cable anymore
- When I plug in power, it vibrates and the white screen comes up
- After a few seconds it goes black then comes the white screen again
- Goes on forever...
I was able to get the it to run again by first doing Task29, then installing the latest original ROM (1.66.405.2). However, as soon as I install another ROM (e.g. RADIO_2.07.50.27_2) I get into the endless reboot again.
Update: After another try to get a different ROM onto the device, I'm not even able to flash anything working (endless reboot).
Please help!
bent battery pins.
Thanks a lot that actually seemed to be it.
I noticed a pin was bent when I finished my flashing crusade but I didn't connect it to the issues I noticed.
i have the same problem today, but no bent pin. I cant even charge it, when plug into charger it charges for 5 seconds then boots up to HTC logo white screen without any info for 10 sec then reboots itself forever, I cant even charge it at the moment because once it boots up it goes to HTC logo screen and reboots the whole time rendenring the battery unchargeable. I assume the battery is faulty eventhough the phone is brand new.
any ideas?
relic said:
i have the same problem today, but no bent pin. I cant even charge it, when plug into charger it charges for 5 seconds then boots up to HTC logo white screen without any info for 10 sec then reboots itself forever, I cant even charge it at the moment because once it boots up it goes to HTC logo screen and reboots the whole time rendenring the battery unchargeable. I assume the battery is faulty eventhough the phone is brand new.
any ideas?
Click to expand...
Click to collapse
try this, it might work .
Remove battery for 10 minutes, plug in charger and wait 5 minutes, hold power for 10 seconds then release, insert battery normally, should charge fine now
kawazaki said:
try this, it might work .
Remove battery for 10 minutes, plug in charger and wait 5 minutes, hold power for 10 seconds then release, insert battery normally, should charge fine now
Click to expand...
Click to collapse
not working

Silver N Screen Bootloop

I'm running CM7 and I guess my tablet locked up in the middle of the night or something. I cut it on and sometimes it won't even get to the N and sometimes it gets to the N, stays there for a second, and then cuts back off. Is there any way to bring it out of this bootloop?
Edit: I got it to boot to the Cyanogenmod boot screen twice, but it keeps cutting off from there. Sometimes the Team-B screen comes up, sometimes it just cuts at the N screen. Other times the screen just flashes. I can't even seem to get it to boot into clockworkmod using the button press.
Edit2: It booted into CWM... I was doing some button presses and it shut off. It seems like the battery died and there's not enough power to turn it on, but yet I had it charging all night.
It happened to me before, luckily I had a spare iPad cable that used more volts lol
It seems like when this problem occurs, the Nook wants more energy from the AC, and yet, I have no fix for this problem. I went back to stock before this occurred.
I think you should hold the power button for 20 seconds.
LeonHikari said:
I'm running CM7 and I guess my tablet locked up in the middle of the night or something. I cut it on and sometimes it won't even get to the N and sometimes it gets to the N, stays there for a second, and then cuts back off. Is there any way to bring it out of this bootloop?
Edit: I got it to boot to the Cyanogenmod boot screen twice, but it keeps cutting off from there. Sometimes the Team-B screen comes up, sometimes it just cuts at the N screen. Other times the screen just flashes. I can't even seem to get it to boot into clockworkmod using the button press.
Edit2: It booted into CWM... I was doing some button presses and it shut off. It seems like the battery died and there's not enough power to turn it on, but yet I had it charging all night.
Click to expand...
Click to collapse
Yeah, be sure you're using the B&N factory cable and adapter. Also, don't use the a PC to charge your NT, always use the AC adapter.
It appears that the place I bought it from did not give me the correct charger and the strongest thing I have is 5 watts at 1 amp.

Possibly bricked phone.. Out of nowhere? Not even flashing

Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
crovax33 said:
Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
Click to expand...
Click to collapse
It could be a power button failure, it's actually quite common on the S4.
Google "Galaxy s4 power button problems"
Check out this link:
http://forum.xda-developers.com/showthread.php?t=1931310

[Q] Soft Bricked Verizon Galaxy Nexus (Toro)

My apologies if this is addressed elsewhere in the forum, but if it is I couldn't find it...at least, not exactly what I'm dealing with.
Phone: Verizon Samsung Galaxy Nexus (Toro)
I was running an unofficial Cyanogenmod of Android 5 on my phone for about 2 months with no problems. Last week the phone just shut off on it's own, and since then I've been stuck.
Here's what I can do (note, all these things can only be done if the phone is plugged in and has the battery in...no response at all if just on battery):
I can boot into the boot loader, and can toggle through the options (recover mode, start, etc), but every time I try to go int recovery the phone restarts, enters the google splash screen for a few seconds, then it flickers and shuts down, showing only the "battery charged" icon.
Same thing happens if I just try to start the phone normally...google splash screen, flicker, dead.
I've tried flashing a stable version of CM11 via the CM installer, but the phone just shuts down to the batter icon during the install.
My computer won't recognize the phone via usb (it keeps trying and failing, and trying and failing...again and again and again).
I tried accessing the phone via ODIN to flash the stock android 4.2.2 rom back onto it, but with no luck. Same problem as described above (i can also boot into ODIN Mode, but it stays on "downloading" and never gets past it - again, this is only when plugged in).
Before the crash the battery life was fine, and the "battery charged" icon shows it being fully charged whenever plugged in.
I've tried pulling the battery for long periods of time (overnight, all day, etc). Same result.
I feel like I hard bricked the thing...but if I did I wouldn't expect to be able to turn anything on...
Thanks, in advance for any suggestions!

Poco F1 on Pixel experience (PE11) stuck in bootloop

Hi Community,
Everything was working fine and couple of days back, my poco F1 on PE 11 started acting wierd. I had to boot it while plugged in or it got stuck in bootloop. But once I boot it, it will work without any problem (unplugged). But since this morning, it won't start or work without plugging it in. And when I stop charging it will work for a while(mostly well until i press power button to lock or unlock) but suddenly goes off and goes in bootloop.
charge percentage also acts weird. While switching on without plugging in, it sometimes shows 0% charge but when I plug it in and use for 10 minutes, battery goes Normally from 1 to 20% and then suddenly it shows 100%.
I opened twrp recovery (which works without plugging in) and kept the phone in recovery for 2 hours, i know it doesn't drain much battery but it just went from 100% to 97 %
Did anyone face similar problem? I am not technically sound in these things. I need help from you guys to get this monster working. Thanks in advance
The reason why I kept it in twrp recovery for couple of hours(unplugged) was to check if it goes off in recovery mode but it didn't.
Here's one similar thread i found but not sure mine is a battery issue since it suddenly started misbehaving.
https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/

Categories

Resources