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
Related
Okay I noticed this from very early development of any Jellybean Rom, like Paranoid Android, then CM10 kangs, then CNA up till 3.4.1 ( thought it would have cleared up by now). Every time I unlock the device it flashes red. I'm not sure how to explain this without sounding insane but here it goes. I unlock the device and it flashes red for a split second then the lockscreen comes up just fine. Doesn't happen every time but I notice the more I stay on one Rom the more frequently it happens to the point that by the second day it always happens. The flash happens only on about 2/3 of the screen diagonally. Happens way to quick for a screenshot but it's defiantly noticeable and annoying. Thanks for any help.
fyi...
I wiped
CNA 3.4.1
Franco.Kernel r246.
I have not noticed that when flashing to Cyanogens CM10.
Sent from my Samsung Captivate on Cyanogens CM10 Jellybean ROM with Devil Kernel.
That's what happens when you use custom colors in a kernel. That's the color profile being applied.
Don't use custom (Trinity, etc) colors and you won't get the flash.
I have seen a red flash once or twice but don't know which ROM it was in or whether it was a Roms stock kernel or the only other kernel I have ever used which is trinity.
I have tried out several Roms including...
Androidme
liquid
CNA
Rasbean
Erick Silver said:
I have not noticed that when flashing to Cyanogens CM10.
Sent from my Samsung Captivate on Cyanogens CM10 Jellybean ROM with Devil Kernel.
Click to expand...
Click to collapse
SirBindy said:
That's what happens when you use custom colors in a kernel. That's the color profile being applied.
Don't use custom (Trinity, etc) colors and you won't get the flash.
Click to expand...
Click to collapse
Slacker said:
I have seen a red flash once or twice but don't know which ROM it was in or whether it was a Roms stock kernel or the only other kernel I have ever used which is trinity.
I have tried out several Roms including...
Androidme
liquid
CNA
Rasbean
Click to expand...
Click to collapse
I want to thank all of you for your replies. i am running franco.kernel r246 w/ 384gpu, i will try with the stock kernel just to make sure it's not the kernel as i've never had problems w/ farnco's kernel. i will try new cm10 builds & i will do some tests to further investigate what could be causing the red flash. i believe it's related to the lockscreen shortcuts but am not sure completely. thanks.
edit: nvm delete thread.
JellyBean isn't fully stable on our DHD/I4G just yet. There are always going to be some issues because HTC didn't give us a full 3.0 kernel for ICS. That could be the reason you are experiencing some lag. Kernels could also help you, try the KangBang performance kernel, although the kernel is leaning towards performance, so it could cause instability
I bought the xda app. Problem?
...
I can't link to the kernel (cause I'm lazy and on the xda app). But when you install a kernel wipe your cache and Dalvik Cache and then flash. That's the proper way of flashing a kernel
I bought the xda app. Problem?
...
sullyy94 said:
Hey thanks for the reply, yeah i successfully installed the stable and performance kernel from this thread : http://forum.xda-developers.com/showthread.php?t=1931386
But the gaming performance still lags compared to 2.3.5. I guess its due to not being fully stable yet.
I had an idea, what if i flash the stock 2.3.5 kernel? Would i get stock performance back or not?
Click to expand...
Click to collapse
You'll ruin your phone. A 2.3.X kernel I'd meant for that specific version of Android. If you mix versions (e.g. a Gingerbread kernel with a Jelly Bean ROM) you'll most likely get bootloops and your phone. At worst you'll brick your phone. Don't ever mix kernel versions. Also don't flash a Sense kernel on a AOSP/AOKP/CyanogenMod based ROM (or vice versa), you'll also have a phone that won't boot.
I bought the xda app. Problem?
...
sullyy94 said:
Hey, thanks for the reply. Yeah I was guessing it had something to do with the kernel. I tried a kernel yesterday not sure which one it was from memory, but when I put the kernel zip onto the phone and installed it through recovery it said install complete. But when I rebooted the phone it gets stuck on a black screen. I can't do anything else unless I take the battery out. I was wondering if anyone can give me a link to the kangbang kernel and instructions in how to install properly if the recovery mode isn't the right way, even though it said kernel updated successfuly. Thanks!
Click to expand...
Click to collapse
The only compatible alternative kernel for JB is the KangBang (at least that i know of). If you flashed another one, that might be why it booted to a black screen.
...
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.
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
Hey guys, posting to get some help with some forced reboots.
I migrated from d2att CM 10.1.3 to SlimBean 4.3 stable build1-876 with no issues, running rock solid and looks and feels great.
I've tried "updating" to the SlimBean 4.3 stable build2, CarbonRom nightlies, and the new DanKang's stable slim + optimizations with success...but I get random reboots on all of them. I'm wondering if it has something to do with going back to the CM kernel with the other roms? The DanKang kernel uses LeanKernel, I also tried independently flashing LeanKernel on top of these other builds to no success.
Currently here's what we're looking at:
SGH-I747
Baseband: i747UCDMG2
3.2.60 slimbuild kernel from Sept 14 that shipped with build.1official-876
Have tried dirty flashes and clean flashes and open to suggestions. Currently have a Dandroid of Slim that I've been going back to between trying these different roms out.
I may just have to be happy with build 1 but I would like the bluetooth fixes and the SlimCenter keeps telling me to update lol, I'm trying!
Which bootloader and modem are you running? Have you tried a odin back to stock, reroot and install custom recovery to try again? This usually resolves these kinds of issues
in fact I'm about to it myself
I believe I'm on the "new" boot_CWM_I747UCDMG2 version and
modem_CWM_I747UCDMG2 flashed from dstruct2k's bootloader and modem threads.
I have been having the same issue on SlimBean 4.3 build 2. I have TWRP 2.6.3 and the newest official modem and bootloader. I don't have any reboot issues on build 1 either. I can try to grab a bug report next time if that will help.