Hey people, i recently bought a new nexus 4 and im LOVING it.
I seem to have a problem with custom kernels, i cant seem to boot up once i install one. Ive tried 3 different kernels ( Purity, Matr1x and Franco ) with the same results. here's what i do and what happens:
1) install a new rom after wiping everything in CWM recovery
2) Install Gapps
3) Install the kernel
4) Reboot
Everything installs successfully but when i boot up, after the 'Google' image when the boot animation is supposed to play out, i get a black screen with nothing on it. And the phone doesnt boot.
If i dont install the rom without the kernel, it boots up. ive also tried installing the rom, gapps and booting it and setting it up ( google account, etc ) and then go to recovery and installing the kernel, still the same results. And ive also tried using different roms and i still get the black screen
Hope ive explained everything
I have an idea that maybe i can change the default kernel that comes with the rom by copying the stuff from a kernel zip and pasting it somewhere in the rom zip. Can it be done? If yes, what exactly do i copy?
THANKS!
adil1508 said:
Hey people, i recently bought a new nexus 4 and im LOVING it.
I seem to have a problem with custom kernels, i cant seem to boot up once i install one. Ive tried 3 different kernels ( Purity, Matr1x and Franco ) with the same results. here's what i do and what happens:
1) install a new rom after wiping everything in CWM recovery
2) Install Gapps
3) Install the kernel
4) Reboot
Everything installs successfully but when i boot up, after the 'Google' image when the boot animation is supposed to play out, i get a black screen with nothing on it. And the phone doesnt boot.
If i dont install the rom without the kernel, it boots up. ive also tried installing the rom, gapps and booting it and setting it up ( google account, etc ) and then go to recovery and installing the kernel, still the same results. And ive also tried using different roms and i still get the black screen
Hope ive explained everything
I have an idea that maybe i can change the default kernel that comes with the rom by copying the stuff from a kernel zip and pasting it somewhere in the rom zip. Can it be done? If yes, what exactly do i copy?
THANKS!
Click to expand...
Click to collapse
very importantly, what rom are you using? not all roms are the same. and no, you cant update a kernel that way.
simms22 said:
very importantly, what rom are you using? not all roms are the same. and no, you cant update a kernel that way.
Click to expand...
Click to collapse
cant beleive i forgot to mention that. Im using the LiquidSmooth rom but i tried ALOT of roms when i wanted to install the kernel. Carbon, Purity, XenonHD, Xylon and the official CM10.1
adil1508 said:
cant beleive i forgot to mention that. Im using the LiquidSmooth rom but i tried ALOT of roms when i wanted to install the kernel. Carbon, Purity, XenonHD, Xylon and the official CM10.1
Click to expand...
Click to collapse
are you on android 4.2.2 or android 4.3?
simms22 said:
are you on android 4.2.2 or android 4.3?
Click to expand...
Click to collapse
4.2.2
adil1508 said:
4.2.2
Click to expand...
Click to collapse
ok reflash your rom and other stuff(without a custom kernel), boot up/set up, then go back and flash this trinity kernel, tf152 http://goo.gl/CDAGV7
did it boot?
simms22 said:
no, you cant update a kernel that way.
Click to expand...
Click to collapse
Yes you can, but it depends on how the kernel is structured inside the flashable zip. If it's just a boot.img file inside, you can definitely just drag & drop it into the flashable rom zip and replace the original one. Some kernels will work, others will not. If you're going from a rom that uses franco to one that uses an original ramdisk, for example, you may run into issues, but in most cases this won't be an issue.
simms22 said:
ok reflash your rom and other stuff(without a custom kernel), boot up/set up, then go back and flash this trinity kernel, tf152 http://goo.gl/CDAGV7
did it boot?
Click to expand...
Click to collapse
OK, ill make a backup and let you know how it goes
adil1508 said:
OK, ill make a backup and let you know how it goes
Click to expand...
Click to collapse
please..
---------- Post added at 03:05 PM ---------- Previous post was at 02:57 PM ----------
adil1508 said:
cant beleive i forgot to mention that. Im using the LiquidSmooth rom but i tried ALOT of roms when i wanted to install the kernel. Carbon, Purity, XenonHD, Xylon and the official CM10.1
Click to expand...
Click to collapse
whats the default kernel in that liquidsmooth that youre running?
simms22 said:
please..
---------- Post added at 03:05 PM ---------- Previous post was at 02:57 PM ----------
whats the default kernel in that liquidsmooth that youre running?
Click to expand...
Click to collapse
It did boot up with the trinity kernel although the app drawer didnt seem as smooth and fast and there was a problem with the widgets
And its the Liquid kernel, do u want me to type whatever is under the "kernel version"?
adil1508 said:
It did boot up with the trinity kernel although the app drawer didnt seem as smooth and fast and there was a problem with the widgets
And its the Liquid kernel, do u want me to type whatever is under the "kernel version"?
Click to expand...
Click to collapse
yes please.
earlier for the franco kernel, other kernels flashed over it wouldnt boot, only flashing the other kernels with the rom would let them boot. franco kernel has modified ramdisk, framcisco had to adjust it so other kernels would boot up after. i have a feeling that something similar is whats going on with their kernel. especially since you say trinity booted but the app drawer is laggy. i bet they also have modified ramdisk(or something messed up by accident).
Kernel Version: 3.4.0-perf-g3ac0f9c [email protected] #1
adil1508 said:
Kernel Version: 3.4.0-perf-g3ac0f9c [email protected] #1
Click to expand...
Click to collapse
its probably a modified stock kernel. did you ask in their thread if this is the normal behavior with custom kernels?
No actually, i didnt. I see your point but what happens with the other roms. XenonHD or Xylon, they have the same problem.
maybe its important but i coudnt get into the stock recovery before i rooted my phone. When i got into fastboot and selected recovery, i would get an android with a red triangle saying ' no command' and i had to press Volume up and power buttons to see the menu
adil1508 said:
No actually, i didnt. I see your point but what happens with the other roms. XenonHD or Xylon, they have the same problem.
maybe its important but i coudnt get into the stock recovery before i rooted my phone. When i got into fastboot and selected recovery, i would get an android with a red triangle saying ' no command' and i had to press Volume up and power buttons to see the menu
Click to expand...
Click to collapse
that android with a red triangle is the stock recovery
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
adil1508 said:
No actually, i didnt. I see your point but what happens with the other roms. XenonHD or Xylon, they have the same problem.
Click to expand...
Click to collapse
lots of roms here are related to one another, some very related, so more distant. liquidsmooth doesnt do much of their own coding, they pick up stuff from other roms/sources. these roms might be very similar.
but honestly, i dont know. it is a weird issue though.
Related
when installing CM9 to your defy is it the same process for flashing CM7 or is there a slight variation or something?
Now why would you open a new thread for this question?
i realised that i could've directly asked on the actual CM9 thread, only after i'd just posted this thread, sorry.
another weird thread
nyambayo97 said:
when installing CM9 to your defy is it the same process for flashing CM7 or is there a slight variation or something?
Click to expand...
Click to collapse
Why a separate thread
but pls refer this
dlcookie said:
Why a separate thread
but pls refer this
Click to expand...
Click to collapse
No offence but this video is pretty useless. Good to see what can be done. but can't see what the dude is actually doing :|
boswald said:
No offence but this video is pretty useless. Good to see what can be done. but can't see what the dude is actually doing :|
Click to expand...
Click to collapse
is there anything u want to see in this video that i missed explaining >?
The original thread was Dev based, about the ROM being released and how stable it is as released. This thread was noob based about how to flash said ROM and if it is different from another, very similar ROM.
Why clutter one thread when you can have two?
Anyway, to answer the question instead of of questioning the question, Yes the basic principle is the same. Once you have the System Recovery installed, it's a case of copying the CM9 zip file to your SD card and flashing the same as CM7, although the way I've personally done it is using Multiboot, so that I can normally use CM7 for "production" but can have a go and see how CM9 is progressing for a few minutes or so.
The Multiboot thread is http://forum.xda-developers.com/showthread.php?t=1364659
Have fun.
Percz said:
The original thread was Dev based, about the ROM being released and how stable it is as released. This thread was noob based about how to flash said ROM and if it is different from another, very similar ROM.
Why clutter one thread when you can have two?
Anyway, to answer the question instead of of questioning the question, Yes the basic principle is the same. Once you have the System Recovery installed, it's a case of copying the CM9 zip file to your SD card and flashing the same as CM7, although the way I've personally done it is using Multiboot, so that I can normally use CM7 for "production" but can have a go and see how CM9 is progressing for a few minutes or so.
The Multiboot thread is http://forum.xda-developers.com/showthread.php?t=1364659
Have fun.
Click to expand...
Click to collapse
And to get back to CM7 from CM9, you only have to flash the CM7 zip?
Percz said:
The original thread was Dev based, about the ROM being released and how stable it is as released. This thread was noob based about how to flash said ROM and if it is different from another, very similar ROM.
Why clutter one thread when you can have two?
Anyway, to answer the question instead of of questioning the question, Yes the basic principle is the same. Once you have the System Recovery installed, it's a case of copying the CM9 zip file to your SD card and flashing the same as CM7, although the way I've personally done it is using Multiboot, so that I can normally use CM7 for "production" but can have a go and see how CM9 is progressing for a few minutes or so.
The Multiboot thread is http://forum.xda-developers.com/showthread.php?t=1364659
Have fun.
Click to expand...
Click to collapse
Thanks. I hope it is easy to boot into recovery and go back to nandroid backup of CM7. I want to try ICS over the weekend.
Install CWM.
Apply Bootmenu 1.0.4.zip
Reboot
Wipe Cache/Data
Apply CM9.zip
Reboot
be happy.
oh okay thanks
sent from Motorola Defy @1.3gz running 2.3.7!
Have a look at this guide on flashing CM9 as a second ROM, using multiboot
[Guide] Install double boot CM7 + CM9:
http://forum.xda-developers.com/showthread.php?t=1375156
i am currently running cm7, but have no idea which version of bootmenu or CWM is running on my handset...how do i check??and if its a different version from the 1 being recommended here, do i needa change it somehow??
abysstheking said:
i am currently running cm7, but have no idea which version of bootmenu or CWM is running on my handset...how do i check??and if its a different version from the 1 being recommended here, do i needa change it somehow??
Click to expand...
Click to collapse
Reboot and press vol- when you seen blue light. You'll be taken to the bootmenu. It's stated in there version of your current bootmenu.
And yes you need to change it speaking of compatibility..
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.4 - XDA Premium
farsight73 said:
Reboot and press vol- when you seen blue light. You'll be taken to the bootmenu. It's stated in there version of your current bootmenu.
And yes you need to change it speaking of compatibility..
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.4 - XDA Premium
Click to expand...
Click to collapse
Absolutely not. You don't need to mess around with bootmenu versions and other stuff. Just read the thread i pointed to above, it works, proven by people following it with succes, and no need to change bootmenus
Sent from my 1Ghz CM7 Defy
Noob GUide
Hi Guys!
I just saw the latest nightly but I'm afraid to flash since kernel will be change and I might not be able to downgrade to stock 2.2.2. May I know if there is a way to flash the latest nightly but also being able to downgrade to stock 2.2.2? I'm currently using CM7 stable ROM
Thanks!
Yes you can downgrade it using your stock 2.2 sbf.
---------- Post added at 06:17 PM ---------- Previous post was at 06:13 PM ----------
martt said:
Install CWM.
Apply Bootmenu 1.0.4.zip
Reboot
Wipe Cache/Data
Apply CM9.zip
Reboot
be happy.
Click to expand...
Click to collapse
I flashed stock full sbf 2.2.2
Rooted using superoneclick
Installed scndInitvs2.0 which gave an option of installing either 0.6.5 or 1.0.7 bootmenu. So chose 1.0.7
Rebooted a couple of times.
Did factory reset , cleared cache and cleared dalvik cache in that order.
applied 12-07 CM9 zip
and rebooted
but my phone is stuck on the M logo!
Thanks! As I want to try the Dec. 7 nightly just for testing purposes. Thanks again!
This is a kernal issue mine is the same im trying to find the best way to update the kernal if anyone knows please let me know
Sent from my MB525 using xda premium
Kind of burned out of flashing all these different roms. Dont get me wrong, I appreciate all the hard work everyone is providing for us. But I am burned out and wasting hours of my day flashing rom after rom etc.
So I went back to stock and rooted. But I did want to see if there was any advice on any kernel out there that I should be running with the latest stock build?
Thank you,
Whiteice
+1
Sent from my Nexus 7 using xda app-developers app
Just wanted to try again and see if I can't get any suggestions on this please?
Thank you,
Whiteice
I did the same. I'm running this at the moment. http://forum.xda-developers.com/showthread.php?t=1831780 with my min at 475 max at 1600, interactive. Had no problems so far. Gets a little warm but nothing crazy. Gonna bump to 1800 soon and see if it can handle it.
Sent from my Nexus 7 using XDA Premium HD app
Der Kernel - Trinity. Comes in high OC version a96 to lower of but slightly irregularities a110 and many more. YMMV but this is a solid, customizable kernel.
Is there a secret to flashing the trinity kernel?
I reboot into TWRP, wipe cache and /dalvik 2x (old habit) flash Trinity, reboot but still shows previous kernel under settings?
Whiteice
WhiteiceDMSTech said:
Is there a secret to flashing the trinity kernel?
I reboot into TWRP, wipe cache and /dalvik 2x (old habit) flash Trinity, reboot but still shows previous kernel under settings?
Whiteice
Click to expand...
Click to collapse
whats your previous kernel and whats in say in kernel version? btw, you dont need to wipe anything when flashing a kernel. anyways, only if you are coming from franco kernel you have to reflash your rom with trinity kernel(flash rom, trinity, reboot). this is because franco kernel uses its own ramdisk(frano kernel tweaks are in there). trinity and just about every other kernel use anykernel which grabs the roms ramdisk usually(unless you had frano kernel). so you want to flash your rom, then trinity, then bootup to resolve the issue. after that you can just flash the kernel. remember, no need to wipe a thing when flashing kernels.
simms22 said:
whats your previous kernel and whats in say in kernel version? btw, you dont need to wipe anything when flashing a kernel. anyways, only if you are coming from franco kernel you have to reflash your rom with trinity kernel(flash rom, trinity, reboot). this is because franco kernel uses its own ramdisk(frano kernel tweaks are in there). trinity and just about every other kernel use anykernel which grabs the roms ramdisk usually(unless you had frano kernel). so you want to flash your rom, then trinity, then bootup to resolve the issue. after that you can just flash the kernel. remember, no need to wipe a thing when flashing kernels.
Click to expand...
Click to collapse
I am coming from the motley kernel.
WhiteiceDMSTech said:
I am coming from the motley kernel.
Click to expand...
Click to collapse
redownload the trinity kernel, flash it, itll say "boom.." you cant miss it. boot up, give your device 3 minutes to set up itself, then check your about phone. if its still motley, post a screen shot please
simms22 said:
redownload the trinity kernel, flash it, itll say "boom.." you cant miss it. boot up, give your device 3 minutes to set up itself, then check your about phone. if its still motley, post a screen shot please
Click to expand...
Click to collapse
Thank for your help.
Each time I flash in TWRP I see the "boom" in caps. Reboot and it says Motley+3.1.10 [email protected]#106 SMP PREEMPT Aug 23rd (date and time of it here.)
WhiteiceDMSTech said:
Thank for your help.
Each time I flash in TWRP I see the "boom" in caps. Reboot and it says Motley Aug 23rd #106
Click to expand...
Click to collapse
will you post or pm me a last_kmsg? run this on a terminal emulator app from your device. there will be a file called last_kmsg.txt in your sd storage. if you can post it please, or send it to me via pm..
su(press enter)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt(press enter)
simms22 said:
will you post or pm me a last_kmsg? run this on a terminal emulator app from your device. there will be a file called last_kmsg.txt in your sd storage. if you can post it please, or send it to me via pm..
su(press enter)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt(press enter)
Click to expand...
Click to collapse
OMG this is so frustrating, I did what you said and try to send it to you, or copy/paste in this thread and it says there are to many characters etc. Working on it.
Hoping this works.
Thank you for your help,
Whiteice
Hallo,
i just tried to flash Franco Kernel v191 to enable USB-OTG on my Nexus 4.
But now i can only boot into CWM Recovery.
When i boot normally, the Screen of my Phone stays black after i see the Google-Logo.
I'm not sure if i flashed the right Version (Do i need JWR or JSS?).
I also flashed only the *.img-File, not the .zip, which was obviously wrong.
How can i flash the right Kernel (or maybe the stock one first) ?
Im using the Nexus Toolkit.
Help me please.
suxx0r said:
Hallo,
i just tried to flash Franco Kernel v191 to enable USB-OTG on my Nexus 4.
But now i can only boot into CWM Recovery.
When i boot normally, the Screen of my Phone stays black after i see the Google-Logo.
I'm not sure if i flashed the right Version (Do i need JWR or JSS?).
I also flashed only the *.img-File, not the .zip, which was obviously wrong.
How can i flash the right Kernel (or maybe the stock one first) ?
Im using the Nexus Toolkit.
Help me please.
Click to expand...
Click to collapse
stop using the nexus toolkits. flash via recovery if a zip, or via fastboot if an img file.
I did flash the Kernel directly via Clockwork Recovery.
Which Version do i have to flash?
I manged to reinstall Cyanogenmod now.
But the ADB-Bridge to the PC doesnt seem to work anymore :/
I enabled USB-Debugging and PTP, but the pc doesnt recognize my phone.
Any Ideas how i can fix that?
suxx0r said:
I did flash the Kernel directly via Clockwork Recovery.
Which Version do i have to flash?
I manged to reinstall Cyanogenmod now.
But the ADB-Bridge to the PC doesnt seem to work anymore :/
I enabled USB-Debugging and PTP, but the pc doesnt recognize my phone.
Any Ideas how i can fix that?
Click to expand...
Click to collapse
oh, youre running cm, thats why. cm changed its source from aosp to qualcomm, so custom kernels are now a no go since the custom kernels are aosp based. the kernels that do boot up on cm, mess up the colors, and franco kernel has issues booting cm. its actually not franco kernels fault, its cm that messed it up for our community(unless you are using cm based kernels).
simms22 said:
oh, youre running cm, thats why. cm changed its source from aosp to qualcomm, so custom kernels are now a no go since the custom kernels are aosp based. the kernels that do boot up on cm, mess up the colors, and franco kernel has issues booting cm. its actually not franco kernels fault, its cm that messed it up for our community(unless you are using cm based kernels).
Click to expand...
Click to collapse
You can get your colors working properly again just copy and paste system/lib/liboverlay.so from non CAF ROM to CM
== Sent from my CarbonMako ?? ==
MaxFTW said:
You can get your colors working properly again just copy and paste system/lib/liboverlay.so from non CAF ROM to CM
== Sent from my CarbonMako ?? ==
Click to expand...
Click to collapse
yes, for now. but that doesn't help the issue here of franco not booting on the newer cm.
simms22 said:
yes, for now. but that doesn't help the issue here of franco not booting on the newer cm.
Click to expand...
Click to collapse
Ok, havent used CM for long since they decided to go full retard and use bloat CAF stuff
== Sent from my CarbonMako ?? ==
MaxFTW said:
Ok, havent used CM for long since they decided to go full retard and use bloat CAF stuff
== Sent from my CarbonMako ?? ==
Click to expand...
Click to collapse
i used to be the biggest cm fanboy back in the day(cm3.1-cm7). many even thoughti was part of cm for a bit(including people who were part of cm). but they had an incident with supercurio(creator of voodoo) that began cm's decline to now, so its been 2+ years since i last ran cm.
simms22 said:
i used to be the biggest cm fanboy back in the day(cm3.1-cm7). many even thoughti was part of cm for a bit(including people who were part of cm). but they had an incident with supercurio(creator of voodoo) that began cm's decline to now, so its been 2+ years since i last ran cm.
Click to expand...
Click to collapse
Same here, I remember this moment when booted CM7 on my Galaxy Mini first time ever Than Desire Z and so on It's been a realy good rom for long long time and I am still using CM10.2 on my Galaxy Tab 2 as it is the only reasonable choice for that device
== Sent from my CarbonMako ?? ==
Q&A for [Kernel + MOD] Hells Doctor #3 R6 / T.A.R.D.I.S. MOD 4.09.18
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bootloop on DirtyUnicorn
Hi , nice work. I've been using HellsDoctor and the battery life is just amazing... but, when I try to flash TARDIS I got bootloop.
Running DirtyUnicorns[Du_mako_4.4.4_20140823.v.7.9-OFFICIAL] and 3.4.104-hells-Doctor-R6.
I am sure I've followed the steps and also I tried some combinations by myself but still isn't working.
Thx in advance.
Which kernel version
I'm using "fiui ROM" -http://forum.xda-developers.com/nexus-4/development/rom-fiui-nexus-01-10-2014-t2892753
Please suggest what version of your kernel will run on it. I tried the latest versions and i'm getting bootloops.
aksh_ad14 said:
I'm using "fiui ROM" -http://forum.xda-developers.com/nexus-4/development/rom-fiui-nexus-01-10-2014-t2892753
Please suggest what version of your kernel will run on it. I tried the latest versions and i'm getting bootloops.
Click to expand...
Click to collapse
CM version
Hello, and thanks for this awesome kernel!
I was trying to flash Dirty Unicorns and Hell's Doctor today, but all kinds of strange behavior ensued. (namely: I lost my display, while ADB could see the device normally).
I flashed the CM version, so am I correct to believe that I should flash the AOSP one?
sgiannouris said:
Hello, and thanks for this awesome kernel!
I was trying to flash Dirty Unicorns and Hell's Doctor today, but all kinds of strange behavior ensued. (namely: I lost my display, while ADB could see the device normally).
I flashed the CM version, so am I correct to believe that I should flash the AOSP one?
Click to expand...
Click to collapse
I will answer my own question here, based on the search in DU's thread:
We need:
- AOSP kernel version
- Revert_4.4.3_Wifi_Fix.zip from http://bit.ly/makostuff (thanks @gorilla p )
and If you want to flash TARDIS, chose CAF dalvik libs.
Tested with HD3_R6 on DU 8.1 & 8.2 and all is well.
Hello,I just wanna ask is this kernel working on aosp lollipop? Which version should I use?
I would also recommend checking out Unleashed kernel along with the latest UKM 3.5 for Synapse.
What does this mean. Every time I open synapse it pops up.LRX21M with hells Dr3-R6.
Sent from my Nexus 4 using XDA Free mobile app
I have clean flashed Lollipop on my N4. Can I simply download the kernel, tardis, and UKM and flash them as per usual, like on KitKat?
I've read through the original thread and it appears some people are talking about a "permissive" boot image? What for? Do I need it or not?
How do I flash this on a clean Lollipop install? It's not clear.
Thanks for the help
I'm having problems with the battery like someone reported before.
The Wi-Fi seems to appear active even if I shutdown.
Some search boxes when are suggesting options the image appears strange.
As I am a new user I can't post images.
Can you include volume rocker wake phone, please?
@AnaguaMateus The volume rocker is included in the N5X-ROM
I'm using this ROM and it has very cool features, I recommand it A new build is going to be release in few hours
Also a FULL WIPE is recommended if you have those bugs
---------- Post added at 10:12 PM ---------- Previous post was at 10:07 PM ----------
ansontyl96 said:
Hello,I just wanna ask is this kernel working on aosp lollipop? Which version should I use?
Click to expand...
Click to collapse
YES it is working on AOSP Lollipop Also you should use the latest L version (L11 for the moment) in combination with the TARDIS-L-Aroma
---------- Post added at 10:20 PM ---------- Previous post was at 10:12 PM ----------
WelfareBaby said:
What does this mean. Every time I open synapse it pops up.LRX21M with hells Dr3-R6.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
It means that your N4 didn't shut down properly last time so Synapse isn't applying the parameters you've set in the last session/boot
---------- Post added at 10:30 PM ---------- Previous post was at 10:20 PM ----------
SeanInToronto said:
I have clean flashed Lollipop on my N4. Can I simply download the kernel, tardis, and UKM and flash them as per usual, like on KitKat?
I've read through the original thread and it appears some people are talking about a "permissive" boot image? What for? Do I need it or not?
How do I flash this on a clean Lollipop install? It's not clear.
Thanks for the help
Click to expand...
Click to collapse
I think the easiest way for you is to install HellsCore Kernel Manager intead of Synapse, the most important parameters are configurables and you don't need to deal with those permissive boot images, UKM, and flash things ;P
Unable to download
Hi,
The download link it now working for me. Can you give me an alternate link?
undo tardis mods
How do i undo tardis mods?
Hello, will it support PA rom for sensation? (KK 4.4)
Sent from my Sensation using xda premium
Cm version
Hi barome, congratulations on this awesome kernel.
Are there plans for releasing L kernel CM based, so we can use it with liquidsmooth?
Thanks
Cpu min set to 1.5ghz
I have a problem with the latest L12 kernel. When using tricksterMOD or any other kernel tweaker app, the minimum cpu frequency is set to 1.5ghz. And I can't seem to make it lower because it jumps back to 1.5ghz immediately. What shall I do?
Stuck on logo of Hells Doctor
I flashed the kernal ad TARDIS mod on my nexus 4. but now I am stuck on logo screen of HD by Barome. Help me
Boot into recovery (hold power for 10 seconds to reboot, then volume down to go into fastboot mode) and then flash your ROM again.
Reboot to see if it boots ok, then flash HD, without TARDIS. If this boots successfully, flash TARDIS, with extra care to choose the correct dalvik (if applicable)
What I'm trying to do is to uninstall the kernel (if that's even possible) and reinstall it or reinstall it and now I want to know if it's even possible
Second question is if it's even healthy to install a kernel on another kernel? could that the reason why "Kernel (Android OS)" is taking up so much battery power?
(I've been playing around with ElementalX and Loony and Frostbitten)
Custom kernels instructions definitely say to be installed ONLY over the stock kernel.
SoNic67 said:
Custom kernels instructions definitely say to be installed ONLY over the stock kernel.
Click to expand...
Click to collapse
Do you know by any chances where to get the stock kernel?
I usually reinstall the stock without wiping the data.
pissgoat said:
What I'm trying to do is to uninstall the kernel (if that's even possible) and reinstall it or reinstall it and now I want to know if it's even possible
Click to expand...
Click to collapse
Kernel is basic requirement for OS to run, it controls (processor and) more than that you can see in any kernel manager.
Without kernel, your device will never boot.
Also can you explain, why you want to uninstall and reinstall ?
Second question is if it's even healthy to install a kernel on another kernel?
Click to expand...
Click to collapse
Stock kernel with many ROM comes with less tweaks allowed, but custom kernel gives you more features/tweaks and wakelocks, so it may increase performance of device and battery too..
could that the reason why "Kernel (Android OS)" is taking up so much battery power?
Click to expand...
Click to collapse
About battery usage, to monitor it correctly get 'batter battery stats' [ https://forum.xda-developers.com/showthread.php?t=1179809 ]
Monitor from this app..
---------- Post added at 07:06 AM ---------- Previous post was at 07:01 AM ----------
pissgoat said:
Do you know by any chances where to get the stock kernel?
Click to expand...
Click to collapse
In custom kernel thread,
Stock kernel means, the kernel which comes preloaded with any ROM that you installed.
Boot.img in ROM zip is stock kernel for that ROM.
You don't need to flash another kernel.