Hello, today I updated my phone to the latest CM13 Nightly and it was going well. Then my AK Kernel Updater notified me to update the Kernel so I did. After rebooting my phone, it is stuck on the AK Kernel screen for a few minuted (2 - 5 minutes) then my screen turns black but my phone is still running in the background but I cannot view the screen (I can use the buttons and can press icons on the screen randomly) Any tips without wiping my phone from it's data?
ronaldonater said:
Hello, today I updated my phone to the latest CM13 Nightly and it was going well. Then my AK Kernel Updater notified me to update the Kernel so I did. After rebooting my phone, it is stuck on the AK Kernel screen for a few minuted (2 - 5 minutes) then my screen turns black but my phone is still running in the background but I cannot view the screen (I can use the buttons and can press icons on the screen randomly) Any tips without wiping my phone from it's data?
Click to expand...
Click to collapse
Wipe system and reflash ROM + gapps should be back on stock kernel then
Sent from my A0001 using Tapatalk
If you made a Nandroid backup before, just hold down the power button until the phone hard shuts down, boot into recovery, and restore your old backup
Just dirty flash over your ROM. It will change the kernel to it's stock state. This is what I do every time I'm running into a problem like this.
There is no ak kernel for CM13. Just check next time the thread.
Related
**** resolved *****
(left the battery out for 30 min then tried rebooting into recovery - worked. immediate face palm)
Coming from CM 10 to SlimKat 4.4 build 4 - clean install. Installed the .zips and when I rebooted, the touch screen was not responding. Hard buttons working fine, but can't unlock the screen (somehow a pattern unlock is now on my phone when I had that turned off previously...?!). Tried to reboot into recovery but it takes me to the splash screen and back to the unlock screen. I'm about ready to pull my hair out! Any other suggestions to at least get back to recovery? I was running the latest version of CWM.
Thanks in advance!
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.
Downloaded the Kernel from this website below:
http://rootzwiki.com/topic/25777-kernelaospv2updated-519-gt-p3113-kernel-ocucuvgpuoc-448mhz-etc/
Installed through CWM with zip
Now stuck on a bootloop (when I press the power button, it only reboots it self. doesn't turn off)
The bootloop doesn't go on to my ROM. Stuck on the Samsung GALAXY TAB 2 7.0 logo. My GTab is GT-P3113.
Thankfully, still can go to CWM with ease. (Power + Vol Up) Everything still accessible. Just how to boot to ROM. If going back to stock kernel fixes it, fine. Just give me the link and I'll give it a try(I feel bad for not backing up my kernel). Please help ASAP:crying:.
P.S. I'm on CM11 for P3110. Works fine, even the IR blaster. Just if anyone needs this information
Late Question: Does re-flashing CM11 on the tab restore the stock kernel? If so, is the appdata going to be saved if I re-flash the ROM?
Fixed: booted to ROM
Anyone facing the same problem, just re-flash your ROM (in my case CM11) and GApps if needed. To my surprise, it reboots back to the home screen. Now, I have the problem of android.process.acore crashing. Help?:crying:
That kernel and link are ancient, I wouldn't flash even if you paid me $809,786.00 dollars. There's plenty 0f roms around forum with proven track records. Update you recoveryand your odin try flashing again.
Pp.
Also this Kernel is from 2012 - CM 11 wasn't released
Send from OnePlus One using Tapatalk
Hi can anyone help me? I had flashed elementalx kernel in chroma rom, after some hours the screen has had some glitches. after an hour later I took the phone from mypocket and the screen is switched on , but remains black. I try with the various toolkit to reflesh stock rom , but the screen remain black
Hold the power button for 10 seconds or until your device force reboots , also what rom did you have and what kernel before you flash elementalx and how did you flashed it?
I recently replaced my nexus 5 display and frame, flashed the latest marshmallow stock images (through flash-all.sh from an early MM preview). From there I flashed TWRP hammerheadcaf and cm13 hammerheadcaf, and my power button would not power the device. I could get to bootloader with pwr+voldown, but the device wouldn't start from there (black screen).
Standard CM13 and AICP hammerhead builds boot and run great, hammerheadcaf builds just cause the device to stop powering. I even tried modifying a hammerheadcaf updater script to flash on the hammerhead TWRP, but the device still wouldn't power with the power button.
I remember hammerheadcaf (in cm12/12.1 days) as being light on battery and awesome in general. I'm open to any ideas or testing. Thank you in advance.
Bump
Same here
Same thing happened to me today:
My Nexus 5 was working well on cm 13 hammerheadcaf.
I changed my screen, and it was stuck on google logo when i tried to reboot it.
Tried to reinstall cm-13.0-20160129-UNOFFICIAL-hammerheadcaf (noticed that it is not longer officially supported btw..) but my phone wouldn't boot after the install (black screen, not responding to power button). I also tried an older hammerheadcaf one, without success.
When back to stock Android, it worked.
Tried cm-13.0-20160130-NIGHTLY-hammerhead, it worked too.
I suppose a problem with cm-13.0-20160129-UNOFFICIAL-hammerheadcaf bootloader, but couldn't find what..
I noticed that bootloader images are present in the cm-13.0-20160130-NIGHTLY-hammerhead zip file, while they are not in the hammerheadcaf one.
Running cm-13.0-20160130-NIGHTLY-hammerhead right now, awaiting for more informations about hammerheadcaf..
Numerinico said:
Same thing happened to me today:
My Nexus 5 was working well on cm 13 hammerheadcaf.
I changed my screen, and it was stuck on google logo when i tried to reboot it.
Tried to reinstall cm-13.0-20160129-UNOFFICIAL-hammerheadcaf (noticed that it is not longer officially supported btw..) but my phone wouldn't boot after the install (black screen, not responding to power button). I also tried an older hammerheadcaf one, without success.
When back to stock Android, it worked.
Tried cm-13.0-20160130-NIGHTLY-hammerhead, it worked too.
I suppose a problem with cm-13.0-20160129-UNOFFICIAL-hammerheadcaf bootloader, but couldn't find what..
I noticed that bootloader images are present in the cm-13.0-20160130-NIGHTLY-hammerhead zip file, while they are not in the hammerheadcaf one.
Running cm-13.0-20160130-NIGHTLY-hammerhead right now, awaiting for more informations about hammerheadcaf..
Click to expand...
Click to collapse
Please keep me updated Numerinico. I never ran cm13 hammerheadcaf on this device, only 12.1. But I do wonder if there's an issue with (potentially) non-OEM hardware that's supported by stock kernel but not hammerheadcaf kernel.
I decided to try a new build of hammerheadcaf with the new twrp 3 caf recovery. The recovery fails to start, and sits at a black screen (like when I try the ROM). The author notes that the build is based on the current caf branches.
bump
I did not tried anything else for the moment, I ll keep you in touch.
By the way, I did not noticed any big difference between CAF and not CAF after a month of usage.