blue/turquoise screen after installing custom kernels - Nexus 7 (2013) Q&A

Ive been using the dark flo version if cm10.2 since I got my nexus 7, however when ive tried to install a custom kernel, I get a blue/turquoise screen upon reboot. Ive tried both CAF and normal versions of various kernels, but all with the same results. I tried using the AOSP kernel setting in the aroma installer, then installed some AOSP kernels, which do boot but it has the worst lag ive ever seen since my iPhone! Anyone else experienced this and know a solution? Ive searched the forum but couldn't find anything relevant

Same here: installed CM10.2 unofficial, GApps, rebooted and everything´s fine.
After installing any of the Faux-Kernels (es/m/u) and wiping Dalvik etc., I have the same screen problems and lags, which make the device unusable.
I´m searching for an overclock kernel, btw.
Thanks for your input!

im after the same thing, just an oc kernel. I even tried one with no mods, just the cpu speeds increased and had no luck
UPDATE - I read somewhere that some kernels wont work with CM versions released after oct 2nd. I tried installing a copy of dark flo from the end of September, then tried faux123's latest mainline kernel abd it booted fine! Im assuming its an incompatibility with the latest CM, so I hope the kernels get updated soon!

Thank you for the info!:good:
It´s waiting time again...

how did you get out of the turquoise screen?

Easy fix:
Uninstall CM
Install AOSP based rom
Profit
Seriously, CM has gone to crap since they moved away from aosp and started with CAF. Kernel devs shouldn't have to do extra work just for one rom, especially when said rom is going from bad to worse
Nexus 7 LTE
Stock rooted KRT16S
Faux Kernel

Related

Kernal ??

Is it necessary to flash a Kernal after flashing a custom rom ?
I am thinking of flashing CM 9 or Liquid Rom. Which is the best kernal to flash with them.
-The correct spelling is kernel.
-It is not necessary to flash a new kernel with a rom. In general roms will package the stock kernel unless they note otherwise.
-I am personally a fan of leankernel because of the mission statement behind its development and the accessibility and speed of its update cycle.
Nope. Custom roms have kernels included, so you are not required to download a separate kernel. However, some kernels run better (ie, more fluid, less heat, reboots, etc) than others on the same device. It all depends on the silicon in your phone. If you plan to run cm9, I recommend sticking with the default kernel. If you're going with Liquid, use imoseyon's leankernel (the default) or franco kernels.
Edit: BTW, I highly recommend franco's kernel app, especially if you are new to the scene. It can download & install either franco or imoseyon kernels, making kernel flashing stupid easy. It also lets you overclock & undervolt, change governors and tweak color settings. And it is the easiest way to keep up with nightly/experimental builds. Not to mention it shows your support and encourages more development.
Sent from my Galaxy Nexus using Tapatalk 2
i say try them all, but for cm9 i recommend fugumod.
Sent from my TF201
Thanks you all for your suggestions ...
finally going to try Liquid Smooth 1.25 (http://forum.xda-developers.com/showthread.php?t=1555667)
along with Franco.Kernel (http://forum.xda-developers.com/showthread.php?t=1367341)
...... One last question Which Franco Kernel to flash there are Milestone 2, Milestone 1, Nightly ??? Whats the difference between them ?
Also when installing extras for liquid smooth do i need to wipe everything again .. I am new to this flashing stuff
and does Liquid Smooth comes with a kernel if so which one ?
Latest milestone is the most stable. Nightlies are experimental. And no need to wipe.
Sent from my Galaxy Nexus using XDA
@cldwar
Liquid + franco is a great choice. Liquid is an extremely polished rom. Very, very smooth with absolutely ZERO lag (it is called Liquid Smooth for a reason) and lots of customization & tweaking options. franco kernel pushes the smoothness to another level. Liquid & franco are both awesome devs who have been tinkering with android for a long time, and they both know their stuff.
Liquid comes with imoseyon's leankernel, which is a solid kernel (obviously, or Liquid wouldn't have included it in the rom). imoseyon is another well-known & respected dev that churns kernels at a dizzying rate. He must develop in his sleep. A lot of people prefer his leankernel, and you really can't go wrong with it. But like I said before, it really depends on your device. Your phone picks the kernel, not you. Milestones are the most stable versions. Nightlies are bleeding edge experimentals with the latest patches & tweaks that may or may not improve battery or performance. Since you are new to flashing, you might want to go with milestone 2 for a few days and see how it feels. On the other hand, you could jump in balls deep and go with the latest nightly/experimental
And you don't need to wipe anything before flashing the extras package.
sublimaze said:
@cldwar
Liquid + franco is a great choice. Liquid is an extremely polished rom. Very, very smooth with absolutely ZERO lag (it is called Liquid Smooth for a reason) and lots of customization & tweaking options. franco kernel pushes the smoothness to another level. Liquid & franco are both awesome devs who have been tinkering with android for a long time, and they both know their stuff.
Liquid comes with imoseyon's leankernel, which is a solid kernel (obviously, or Liquid wouldn't have included it in the rom). imoseyon is another well-known & respected dev that churns kernels at a dizzying rate. He must develop in his sleep. A lot of people prefer his leankernel, and you really can't go wrong with it. But like I said before, it really depends on your device. Your phone picks the kernel, not you. Milestones are the most stable versions. Nightlies are bleeding edge experimentals with the latest patches & tweaks that may or may not improve battery or performance. Since you are new to flashing, you might want to go with milestone 2 for a few days and see how it feels. On the other hand, you could jump in balls deep and go with the latest nightly/experimental
And you don't need to wipe anything before flashing the extras package.
Click to expand...
Click to collapse
thanks .... extremely useful info
Just flashed Liquid with Franco kernel ... Wifi Sucks otherwise cool rom. Is there a way to flash stock 4.0.4 Rom ??
I cant find stock 4.0.4 to flash
cldwar said:
Just flashed Liquid with Franco kernel ... Wifi Sucks otherwise cool rom. Is there a way to flash stock 4.0.4 Rom ??
I cant find stock 4.0.4 to flash
Click to expand...
Click to collapse
If you have fastboot set up, grab official images from google and flash them.
bk201doesntexist said:
If you have fastboot set up, grab official images from google and flash them.
Click to expand...
Click to collapse
those images are for Yakju ..... mine is Yakjujp ... I think i cant flash them .. any other solution ??
cldwar said:
those images are for Yakju ..... mine is Yakjujp ... I think i cant flash them .. any other solution ??
Click to expand...
Click to collapse
doesn't matter,
infact if you flash yakju then you will get OTA as well. if you are in japan you can flash a japan radio on top of the rom.
Rcommander said:
doesn't matter,
infact if you flash yakju then you will get OTA as well. if you are in japan you can flash a japan radio on top of the rom.
Click to expand...
Click to collapse
Don't I need to get the boot loader etc back to orignal in order to receive the updates ... ? If so how ?
Sent from my Galaxy Nexus using XDA
Kernal?
I have been researching the many different kernels out there all day. I have been running GummyNex ROM's since I rooted my GNex. I really do like the options he has. I forget which version, but the battery life was amazing (which included the baked in kernel). I flashed to .0.9 and recently 4.0.4 1.0.1 and the battery life is like a V-12 Lamborghini. I just flashed a Franco Kernal and am hoping this fixes my battery drain issues.
Something has to give......
falconfan said:
I have been researching the many different kernels out there all day. I have been running GummyNex ROM's since I rooted my GNex. I really do like the options he has. I forget which version, but the battery life was amazing (which included the baked in kernel). I flashed to .0.9 and recently 4.0.4 1.0.1 and the battery life is like a V-12 Lamborghini. I just flashed a Franco Kernal and am hoping this fixes my battery drain issues.
Something has to give......
Click to expand...
Click to collapse
Use liquid rom with Franco milestone built ... gave me a 4+ hour screen time. Don't know why but the nightly version reduces battery life
Sent from my Galaxy Nexus using XDA
I'm running Liquid 1.3 and am using Franco nightly #143 and, so far, my battery life is really great. I was at 89% after 2 hours. I also want to try Milestone 3, that just came out yesterday and see how it performs.

Kernel flashing results in black screen on boot

Hey guys,
I've noticed recently that when i flash any kernel that is compatible with my rom, it results in black screen on reboot. But its as if the phone is active in the sense that i can hear the phone make the unlock sound when i pretend to unlock it. so its all there but the screen is black.
Rom i am on currently: Carbon 4.2.2 stable release
Kernels Ive tried: BMS, KT both of which are 3.4 version needed for the rom i use.
I've cleared cache, fixed permissions, factory reset and started from scratch with installling the rom and then flashing the kernel with the same issue.
Ended up doing a restore of nandroid for phone to work. But still cant flash any kernels that I know for sure are compatible with any rom. This doesnt seem to be a rom or kernel specific issue because i've tried different combinations. Like for example i tried the aokp tasker with KT with same symptoms pr for example liquid smooth with BMS etc.
Any suggestions?
Thank you in advance.
What's the release date of your rom? Try using a kernel release of that date or earlier.
xBeerdroiDx said:
What's the release date of your rom? Try using a kernel release of that date or earlier.
Click to expand...
Click to collapse
the latest version of carbon rom 1.61 is what is I use regularly. I've tried older versions of this and other roms but the issue persists.
gutlessmerc said:
the latest version of carbon rom 1.61 is what is I use regularly. I've tried older versions of this and other roms but the issue persists.
Click to expand...
Click to collapse
the release date of that rom is 3/29. i would try a 3.4 kernel with a release date of 3/29 or earlier to see if this corrects the issue.
gutlessmerc said:
the latest version of carbon rom 1.61 is what is I use regularly. I've tried older versions of this and other roms but the issue persists.
Click to expand...
Click to collapse
You need to use an older version of a kernel. Either 4/15 for BMS or 4/11 for KT747. The most recent builds have display commits that are required on the ROM for the display to work.
ktoonsez 4/11 release: http://forum.xda-developers.com/attachment.php?attachmentid=1916103&d=1367068269
Thanks for the response guys. I've tried flashing the older version of KT kernel as suggested. Thanks for the link man. Unfortunately, the same issue again: On boot, it goes all black. The difference though is that this time while the screen is black, there is no sound response by tapping on the screen. I tried increasing the volume to see if there was any difference but still nothing.
I guess i'll be fine. The only reason i tried flashing a different kernel was so i could enable fast charge.
Thanks for the help guys.
Cheers
flash tasks 4/23 build. its stable, bug free (for me) and has the fast charge feature in addition to amazinf battery life. cheers

[Q] CM10.1/Carbon/AOKP Recent Nightlies Causing Reboots

Hello! I've searched quite a bit but have been unable to find anything to address the frustration I'm having. Recently I have been having an issue where my phone will restart itself at random intervals. The best way to recreate the issue is to use a streaming media app like Spotify/YouTube/Google Play Music/etc but it does happen at other times as well. This will occur on all ROMs I've tried including AOKP, CM10.1, Carbon, etc.
I believe I have narrowed the issue down to the 3.4 kernel as all the ROMs I've flashed in recent weeks have been using 3.4. If I use an older ROM (such as the stable release of CM10 with the 3.0 kernel) I do not have the issue.
It gets even stranger...I have found that LeanKernel is the only 3.4 kernel to work and has been stable for about 3 days on my device. So apparently I am stuck with reflashing LeanKernel after each ROM update if I want to run the latest and greatest.
My question is two-fold....
Is this a known issue for the AT&T GS3?
Any suggestions to fix this problem?
For the record, I have reverted to the stock, unrooted ROM and do not have the issues there.
Thanks in advance for any guidance!
Issues and bugs with 3.4 kernels are known. This is not specific to you.
I am running tasks 4/23 with the packaged kernel. No issues. Full wipe is key
xBeerdroiDx said:
Issues and bugs with 3.4 kernels are known. This is not specific to you.
I am running tasks 4/23 with the packaged kernel. No issues. Full wipe is key
Click to expand...
Click to collapse
Thanks for the feedback. I may look at Task's ROM in the future.

Weirdness flashing kernels.

Thus far I have used stock rooted and Pro Bam with my N7. The ROMS all work fine with their included kernels. However, whenever I try to use another kernel like glitch of Elemental X I get weird colors while the ROM is booting (Kind of like static). Then the colors are all tweaked when it finishes booting. I have tried overclocking, underclocking, and stock settings. But the issue persists until I reflash the original kernel that came with the ROM.
I am fairly baffled by this one. Any ideas?
Sent from my Nexus 7 using Tapatalk
rastaguy said:
Thus far I have used stock rooted and Pro Bam with my N7. The ROMS all work fine with their included kernels. However, whenever I try to use another kernel like glitch of Elemental X I get weird colors while the ROM is booting (Kind of like static). Then the colors are all tweaked when it finishes booting. I have tried overclocking, underclocking, and stock settings. But the issue persists until I reflash the original kernel that came with the ROM.
I am fairly baffled by this one. Any ideas?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i dont know if Pro Bam is stock based but check if kernel is CAF or non-CAF if you are on stock install non caf kernel like aosp based in glitch

[Q] please help

Hello all. First I want to thank everyone for still being around to help, especially on such an old device.
Anyway, I recently bought one of these and got it rooted via odin. Currently that's all I've done to her. I have been looking over this forum, android forums, and Google in general prior to posting, I want to solve problems on my own, but when I can't, I'm not scared to ask for help. And I need help with a few issues. I will seperate them, to make answering them easier.
1) is twrp not available for this model?
2) if not, the only other recoverys I can find is Phils TouchWiz, and ClockworkMod recovery touch 5.8.1.5. I wouldn't think these are the same, which is suggested? Also Phils Touchwiz was last updated (that I can find) to 4.1.2 which is where I currently am, am I want to go to 4.4
3) I only see 2 ROMs listed on here, and 1 is one of the ones I was thinking of using in Dirty Unicorns. The other I was thinking about was CyanogenMod. Which of these two is suggested?
4) I have no service on this phone, as its my tinkering device. The only thing I need to work is WiFi. That being said, do I need to flash a new modem?
Do I need to flash a new kernel?
Thanks for any help you can throw me. I know there are lots of tuts for all these questions, but frankly they are all very old, and this stuff changes by the day...
1. Yes but this device has recovery and kernel built in together, this recovery is only for flashing / wiping, other than that, it is not usable with other custom roms unless the devs build it to use that
recovery along with the kernel.
2. It's the same as question 1, For Touchwiz Jellybean, you'll need a recovery kernel that supports the android version and firmware, otherwise it wouldn't work or boot up, Agat's Source GB27 for GB27 Touchwiz ROMs. Or specific AOSP Kernels for certain kernel build updates ( versions are compatible with the build date of the ROM's Original Kernel, meaning it only works on certain ROMs that are updated with the same kernel build, for example, A custom 0.0.25 will not work with stock 0.0.26 because there was a major update change in the kernel that'll make 0.0.25 not usable on it. If you use a kernel based on a specific date on an AOSP ROM that frequently updates the kernel, it may not boot up. )
3. The AOSP ROMs that are being updated at the moment are the Teams that do Nightlies. So Cyanogenmod is the only AOSP ROM that's being updated weekly for this device, I have not checked on the other ones.
4. No need to flash a modem if you don't have data service, however it may help either way when using WiFi due to dropped connections, stability etc. For AOSP, use any ICS modem, for Touchwiz, use the same android firmware modem.
Flashing a new kernel is not needed unless you don't like how the stock kernel performs whether if it's power saving or performance. AOSP kernels are kind of limited as the ones out now work with different build dates of the ROMs, Touchwiz has a couple, but Agat63's Source Kernel is recommended by everyone for GB27.

Categories

Resources