Hi guys.
As i recently installed TwistedKat and charged my phone over night because the battery was empty i couldnt turn off the screen via power button anymore. Longpressing it still shows the menu but i cant turn off the screen at all. What was also quite amazing is that the bootscreen doesnt come up anymore, its just a black screen instead of the twistedkat logo.
Im on TwistedKat 2.6
Using the Icecode Kernel from the 28. march since i cannot download the latest version.
Any ideas what this could be?
(Wiping caches also doesnt help i tried that a few times)
Edit: the problem also happened while i was on another rom - vanir - i solved the problem by doing a fresh install but since its happening again i would love to know what causes this problem.
I have flashed a CM12 nightly using TWRP recovery. After that, during rebooting, phone switched off automatically after showing “google” logo. I went back to the TWRP and installed the backup which I have kept (stock lollipop 5.0.1). After that when I’m trying to turn on, it’s working with the charger plugged in. If I remove the charger after switching on, if I kept it idle, it will stay on till the battery is empty (I got around 24 hrs). But if I try to take mobile data or camera it will switch off for sure. Sometimes just moving across different home screens also will make it switch off. The battery status show is also not correct when switched on. In recovery mode it works well without battery and battery percentage is also correct.
What will be the reason?? Is it something related to the firmware or a Hardware issue?? Will changing the battery help??
Please Flash Stock Firmware. Once done, you can try another Nightly of CM. If it persists, please post in [Q&A] [Mako][Nexus 4][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v4.2 - 04/01/201
Oh Yes, Don't do any of this until the Battery is Fully Charged.
while charging and sometimes when my HTC ONE S is idle , it reboots.
why?
my boot info attached .
installed rom: CM 12.1 lataset nightlies.
completely wiped before first 12.1 nightly and then update via software updates of android.
thanks
Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!
Thread closed / Duplicate
Hi Guys,
Prelude : 2 months back, my pure stock Moto G experienced i guess a battery drain and refused to start the next time onwards. When it was powered on, it just got stuck on the M Logo of the bootup. After the help from @lost101 & others, i was able to flash the custom recovery & rom and got the phone to bootup atleast although faced the same issue which i'll be writing below now.
Since that event has happened, everytime I flash a custom rom, the installation happens without any glitch which includes the rom.zip & gapps_pico.zip. Now when the ROM bootups, the startup screen shows up after which it starts optimizing apps. That's where is the issue starts.
For eg. optimizing app x (single digit) of 101, it doesn't goes beyond that point even after waiting for 15-20 mins or so, and i've to manually reboot using the power button after which again the optimizing apps screen comes up and this time the figure is optimizing app xx of 16/17, and in this turn the phone successfully boots up to the setup screen and works as normal. But after a few moments when i'm done setting up all my apps and everything, random issues turn up for eg. the notification quick tiles won't drop down. And when i restart the handset, again it shows the optimizing apps screen, the phones boots up to home screen but random issues pertain.
I've tried ROM's like Stock Debloated (5.1.1) , CrDroid, CyanPOP, RessurectionRemix all based on 6.0.1.
Before installing any ROM, i do an advanced wipe and all format the data. Right now the handset is running CyanPOP but the main issue is i'm unable to access the notification dropdown. It doesn't goes beyond the header.
One more thing, I installed RR (xt1022 specfic) with same pico_gapps on my Moto E & the rom booted up in no time and working as smooth as butter till date with no issues whatsoever.
I'll be helpful if some one can diagnose the issue. Thanks
BBThumbHealer.
Did you try flash stock firmware and then flash a costum ROM ?
@Eurofighter_ty : when the issue first happened, what I remember is that I tried installing the debloated stock ROM of 5.1.1 and not the pure stock having all the unnecessary gapps. And similar issue was encountered. Same thing happened with other custom ROMs.
Today I've now reverted to a previous version of CrDroid 6.0.1 released in April and it at least runs fine when in use although a reboot causes the same issue. However, CrDroid June update and CyanPOP had the issue in which the quick tiles didn't drop down along with refusal of bootup.
Try to flash the stock ROM via fastboot with all files