• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[KERNEL] [6P] [8.x/7.1.x] [2018-02-14] Kernvatore v3.11

Should I remove SuperSU from the ramdisk so SuperSU/phh can patch like stock?

  • Yes. I like this idea.

    Votes: 1 100.0%
  • Nope. I only use SuperSU.

    Votes: 0 0.0%

  • Total voters
    1
  • Poll closed .
Search This thread

vt0r

Senior Member
Sep 22, 2013
465
1,002
New York
shellvatore.us
iJoKF6l.png


Code:
/*
 * kernvatore-angler.c
 * --------------------------
 * YOUR WARRANTY IS NOW VOID
 *
 * I am not responsible for bricked devices, dead SD cards,
 * sick/abused animals, thermonuclear war or you getting
 * fired because you missed your alarm.
 *
 * Do some research if you have any concerns about features
 * included in this kernel BEFORE flashing it!
 *
 * YOU ALONE are choosing to make these modifications,
 * and if you try to blame me for messing up your own
 * device, I will drink your tears.
 */

Introduction

Kernvatore is intended to be a super light and lean kernel, much like leanKernel or ElementalX. Kernvatore only exists because Imoseyon has not been able to update leanKernel in a while, and I miss his kernel very much. Though I would never claim my kernel compares to the great leanKernel, I do aim to make it as close to the original lk experience as possible. The only place where this kernel really deviates from lk is the included I/O schedulers. However, including additional ones does NOT make this kernel any less lean, so no need to worry. I know some people love to change settings, even if you recommend they don't, so I just want to provide ample choices in that department. I have no desire to add new CPU governors at this time, as most of them are highly unstable and have been ported many times between devices.

Features

  • Built from the latest Oreo sources
  • InteractiveX V4 governor is the default (replaced original interactive)
  • KCAL color control support from @savoca
  • Optimized for cortex-a57/a53 and built using UBERTC optimized 4.9.x toolchain
  • Performance/stability optimizations
  • Some unnecessary features were removed/disabled
  • No F2FS support currently (trying to find time to merge upstream f2fs again)
  • Full SDCARDFS support
  • Synced with upstream to the latest 3.10.x version (currently 3.10.105)
  • Disabled forceencrypt to widen adoption
  • No longer patched with any root solution as of v2.x, so you can choose your own root adventure
  • Removed dm-verity
  • Filter ro.boot.verifiedbootstate from /proc/cmdline (for SafetyNet checks - Android Pay/PoGo/whatever)
  • Some code pulled from CAF repo directly, likely more to come in the future
  • Enabled deadline and ROW I/O schedulers (both built-ins, but disabled by default)
  • Added FIOPS, SIO, SIO+, Zen I/O schedulers - FIOPS is the default.
  • Kexec support with hardboot
  • Config access via /proc/config.gz - mostly for us nerds
  • Disabled ZRAM and swap
  • Rudimentary support for init.d scripts in /system/init.d using run-parts (but neither the zip nor the kernel's ramdisk will EVER mount your system RW, so this does not enable support where it doesn't already exist).
  • Gesture sleep/wake support
  • FauxSound support
  • More features will be added as I see fit, as long as they don't add too much "heft" to the kernel.

Installation

  1. Download the zip
  2. Flash the zip in TWRP or using your preferred flashing app
  3. BEER





Downloads and Changelog

Pushbullet channel




XDA:DevDB Information
Kernvatore N6P, Kernel for the Huawei Nexus 6P

Contributors
vt0r, imoseyon, franciscofranco, googy_anas, flar2, ryanbg
Source Code: https://github.com/vt0r/kernvatore-angler

Kernel Special Features:

Version Information
Status: Stable
Current Stable Version: 3.11
Stable Release Date: 2018-02-14

Created 2016-09-29
Last Updated 2018-02-14
 
Last edited:

vt0r

Senior Member
Sep 22, 2013
465
1,002
New York
shellvatore.us
Frequently asked questions

Q: What's with the two zips for encrypted and unencrypted?
A: If your device is encrypted, and you want it to stay that way, use the "-encrypted" variant. This is an absolute must if you're using FBE with Oreo (and possibly Nougat as well).

If your device is not encrypted, either join the dark side and encrypt it, or avoid using the "-encrypted" zip.


Q: I run XXXXX ROM. Will it work?
A: Should no longer be an issue, as we're using AnyKernel2 by @osm0sis. IT SHOULD NOW BOOT ON ANY ROM. If you find one that isn't working, please provide all the logs you can possibly get (see log question below).

Q: I'm just getting a bootloop. What should I do?
A: Please provide logs if you have them, or at least provide full details about your setup and what steps lead you to the bootloop (also see log question below).

Q: How can I collect debug logs?
A: Download and flash my debug log collector zip file in TWRP. This zip will gather some common kernel/boot logs and create a tarball in /sdcard/debug_logs that you can upload to some file sharing site for me to review. Once you've flashed the zip, you can either pull the resulting archive using adb or reflash some kernel that previously worked, reboot back into the system and upload from your phone. Either PM or post the link where I can retrieve the log archive, and I'll review as soon as possible. This does not guarantee I'll be able to resolve the issue, but it should provide a great deal of debugging information either way.
 
Last edited:

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
5,536
11,438
30
Ambala
OnePlus 5
So what's the difference between normal interactive on other kernels and interactiveX in this? :fingers-crossed:

Created by kernel developer Imoseyon, the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery v/s performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
 
  • Like
Reactions: vt0r and Prattham

eqbirvin

Senior Member
Apr 6, 2012
579
472
Philly
I'm not going to ask you to disable force decryption, you're the author of this good work. But can i at least ask why you wont? You seem to have strong reasoning behind it
 

vt0r

Senior Member
Sep 22, 2013
465
1,002
New York
shellvatore.us
I'm not going to ask you to disable force decryption, you're the author of this good work. But can i at least ask why you wont? You seem to have strong reasoning behind it

Absolutely. I'm a paranoid fool, so the thought of intentionally disabling Android's full disk encryption (or file-backed encryption) just makes my stomach turn.

Also, unless things have changed drastically since the N6, unencrypted devices don't even offer that much of a performance boost, especially considering the encryption ops are all done on chip using the built-in AES-NI extensions, which are extremely fast. I just can't fathom someone voluntarily foregoing protection on a device that's so easy for some to lose, just for some perceived performance boost.

TL;DR - I don't want to be the one to make your device less secure, so just update the fstab in the ramdisk if you're one of those who wants to disable encryption, but please don't tell me about it, because I don't like to cry.
 
Last edited:

danmaman

Senior Member
Jan 15, 2012
1,376
891
@vt0r
hey mate
i wanted to try your kernel.zip but with no luck
i'm on stock N with systemless root and stock kernel....
flashed with flashfire but it says "no 6p device abborted"
But I have to say I've unticked the mount/system read write option in FlashFire .. Because I want a full OTA support
Just an example in screenshot
with elementalx i had not this ......maybe ex kernel doesn't touch the system partion?
hmmm weird
 

Attachments

  • Screenshot_20160930-175756.png
    Screenshot_20160930-175756.png
    201.2 KB · Views: 4,182
Last edited:

vt0r

Senior Member
Sep 22, 2013
465
1,002
New York
shellvatore.us
@vt0r
hey mate
i wanted to try your kernel.zip but with no luck
i'm on stock N with systemless root and stock kernel....
flashed with flashfire but it says "no 6p device abborted"
But I have to say I've unticked the mount/system read write option in FlashFire .. Because I want a full OTA support
Just an example in screenshot
with elementalx i had not this ......maybe ex kernel doesn't touch the system partion?
hmmm weird

Sorry, but I'm having trouble understanding what you mean. Can you provide the recovery.log, please?

Based on what I think you mean, it's not detecting either of the property values it checks to ensure your device is a 6P, so I'm expecting the log to confirm this.

Also, neither my zip nor ramdisk scripts will EVER try to mount system RW, so that option has nothing to do with the failure. My zip doesn't even mount system RO.
 
  • Like
Reactions: danmaman

danmaman

Senior Member
Jan 15, 2012
1,376
891
Sorry, but I'm having trouble understanding what you mean. Can you provide the recovery.log, please?

Based on what I think you mean, it's not detecting either of the property values it checks to ensure your device is a 6P, so I'm expecting the log to confirm this.

Also, neither my zip nor ramdisk scripts will EVER try to mount system RW, so that option has nothing to do with the failure. My zip doesn't even mount system RO.

all good now...
i flashed the 32mb boot.img not the zip.....and all ist good

thanks a lot
i'll test now
 

yung40oz84

Senior Member
Sep 23, 2014
3,090
1,027
sites.psu.edu
Considering this kernel is for N and TWRP cannot decrypt android N yet, I cannot flash because it does not disable force encryption. This is kind of a catch 21.

---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------

Absolutely. I'm a paranoid fool, so the thought of intentionally disabling Android's full disk encryption (or file-backed encryption) just makes my stomach turn.

Also, unless things have changed drastically since the N6, unencrypted devices don't even offer that much of a performance boost, especially considering the encryption ops are all done on chip using the built-in AES-NI extensions, which are extremely fast. I just can't understand someone voluntarily foregoing protection of a device that's so easy for some to lose, just for some perceived performance boost.

TL;DR - I don't want to be the one to make your device less secure, so just update the fstab in the ramdisk if you're one of those who wants to disable encryption, but please don't tell me about it, because I don't like to cry.

I do I update the fstab in the ramdisk as you speak of? I would be willing to do so if it is not such a hard process so I can try this kernel. Thanks in advance!
 

th3discodancer

Senior Member
Oct 20, 2011
779
236
Considering this kernel is for N and TWRP cannot decrypt android N yet, I cannot flash because it does not disable force encryption. This is kind of a catch 21.

---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------



I do I update the fstab in the ramdisk as you speak of? I would be willing to do so if it is not such a hard process so I can try this kernel. Thanks in advance!
TWRP 3.0.0-1 upwards support N. I'm encrypted and have been not facing any issues on any kernels I've tried so far.

@OP, really excited to try this. Gotta love leans. :)
 

atrus5

Senior Member
May 12, 2011
949
990
Saskatoon
OnePlus 7
After flashing this kernel and rebooting phone, I could not boot back into rom. After 15 minutes waiting I booted back into twrp and it asked me for a password which I have never set. Was only able to mount system as read only. After trying to read the sdcard, it says I have 0mb of space. After trying to flash factory images it says that it cannot write system.img as it does not have enough space. I have tried all options that I can think of. Any help would be appreciated.
 

vt0r

Senior Member
Sep 22, 2013
465
1,002
New York
shellvatore.us
...TWRP cannot decrypt android N yet.

This is not true. Visit http://dl.twrp.me/angler and grab the latest (3.0.2-2 I believe), which has no issue decrypting /data.

I do I update the fstab in the ramdisk as you speak of? I would be willing to do so if it is not such a hard process so I can try this kernel...

I wouldn't recommend it for beginners, but there are utilities to make the process simpler, like abootimg and similar. Check their man pages for usage info.

My current recommendation is to use some other kernel that disables forced encryption if you don't want your device to be encrypted.
 

rohitchouhan07

Senior Member
Nov 11, 2014
66
38
Indore
After flashing this kernel and rebooting phone, I could not boot back into rom. After 15 minutes waiting I booted back into twrp and it asked me for a password which I have never set. Was only able to mount system as read only. After trying to read the sdcard, it says I have 0mb of space. After trying to flash factory images it says that it cannot write system.img as it does not have enough space. I have tried all options that I can think of. Any help would be appreciated.

Try doing a full wipe in TWRP i.e. system,data and cache
 

vt0r

Senior Member
Sep 22, 2013
465
1,002
New York
shellvatore.us
After flashing this kernel and rebooting phone, I could not boot back into rom. After 15 minutes waiting I booted back into twrp and it asked me for a password which I have never set. Was only able to mount system as read only. After trying to read the sdcard, it says I have 0mb of space. After trying to flash factory images it says that it cannot write system.img as it does not have enough space. I have tried all options that I can think of. Any help would be appreciated.

Ok I'm going to need lots more info to help here.

First, which ROM were you trying to boot into?

Second, were you unencrypted?

Third, where is the error you're getting about not having enough space? TWRP? Fastboot? Something else?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    iJoKF6l.png


    Code:
    /*
     * kernvatore-angler.c
     * --------------------------
     * YOUR WARRANTY IS NOW VOID
     *
     * I am not responsible for bricked devices, dead SD cards,
     * sick/abused animals, thermonuclear war or you getting
     * fired because you missed your alarm.
     *
     * Do some research if you have any concerns about features
     * included in this kernel BEFORE flashing it!
     *
     * YOU ALONE are choosing to make these modifications,
     * and if you try to blame me for messing up your own
     * device, I will drink your tears.
     */

    Introduction

    Kernvatore is intended to be a super light and lean kernel, much like leanKernel or ElementalX. Kernvatore only exists because Imoseyon has not been able to update leanKernel in a while, and I miss his kernel very much. Though I would never claim my kernel compares to the great leanKernel, I do aim to make it as close to the original lk experience as possible. The only place where this kernel really deviates from lk is the included I/O schedulers. However, including additional ones does NOT make this kernel any less lean, so no need to worry. I know some people love to change settings, even if you recommend they don't, so I just want to provide ample choices in that department. I have no desire to add new CPU governors at this time, as most of them are highly unstable and have been ported many times between devices.

    Features

    • Built from the latest Oreo sources
    • InteractiveX V4 governor is the default (replaced original interactive)
    • KCAL color control support from @savoca
    • Optimized for cortex-a57/a53 and built using UBERTC optimized 4.9.x toolchain
    • Performance/stability optimizations
    • Some unnecessary features were removed/disabled
    • No F2FS support currently (trying to find time to merge upstream f2fs again)
    • Full SDCARDFS support
    • Synced with upstream to the latest 3.10.x version (currently 3.10.105)
    • Disabled forceencrypt to widen adoption
    • No longer patched with any root solution as of v2.x, so you can choose your own root adventure
    • Removed dm-verity
    • Filter ro.boot.verifiedbootstate from /proc/cmdline (for SafetyNet checks - Android Pay/PoGo/whatever)
    • Some code pulled from CAF repo directly, likely more to come in the future
    • Enabled deadline and ROW I/O schedulers (both built-ins, but disabled by default)
    • Added FIOPS, SIO, SIO+, Zen I/O schedulers - FIOPS is the default.
    • Kexec support with hardboot
    • Config access via /proc/config.gz - mostly for us nerds
    • Disabled ZRAM and swap
    • Rudimentary support for init.d scripts in /system/init.d using run-parts (but neither the zip nor the kernel's ramdisk will EVER mount your system RW, so this does not enable support where it doesn't already exist).
    • Gesture sleep/wake support
    • FauxSound support
    • More features will be added as I see fit, as long as they don't add too much "heft" to the kernel.

    Installation

    1. Download the zip
    2. Flash the zip in TWRP or using your preferred flashing app
    3. BEER





    Downloads and Changelog

    Pushbullet channel




    XDA:DevDB Information
    Kernvatore N6P, Kernel for the Huawei Nexus 6P

    Contributors
    vt0r, imoseyon, franciscofranco, googy_anas, flar2, ryanbg
    Source Code: https://github.com/vt0r/kernvatore-angler

    Kernel Special Features:

    Version Information
    Status: Stable
    Current Stable Version: 3.11
    Stable Release Date: 2018-02-14

    Created 2016-09-29
    Last Updated 2018-02-14
    16
    Kernvatore v3.8 is released!

    Changelog
    • Merge all upstream changes from oreo-r5(?) branch. Google wat r u doin with release versions? :confused: Patch level: October 2017


    DOWNLOAD HERE


    md5sum/sha256sum/b2sum:
    Code:
    d5c46d66e9dd3bcb0bbed5d149cee889  kernvatore-angler_3.8-anykernel2-encrypted.zip
    7e7615846a383cb645fd6ca3cc0e0ec70977efb1aa89cfa9ffca833898be3bf6  kernvatore-angler_3.8-anykernel2-encrypted.zip
    b11a26ec9d5207e8e9f743219b49bb1002ae39ad237aaa6935d6a79f21a4da9d7a2d40bf05c82b9f8dd586d347305f6b9153c2c533f3cfdc78543d378631d63b  kernvatore-angler_3.8-anykernel2-encrypted.zip
    
    b206d20f8a3a99ff116a6886cf44ed07  kernvatore-angler_3.8-anykernel2.zip
    1f8e04ec1d82c58f53014a0c1eed55b8c35f4002926ad152e28a02fecf5ca42f  kernvatore-angler_3.8-anykernel2.zip
    89076bf30d74f5048d48b881f958fb46bda450b67589baae839767bf5f693cdda83baa7fc0764bf3011fdf347a279df5c7e275478c2cc7b7278169956d70e333  kernvatore-angler_3.8-anykernel2.zip
    16
    Kernvatore v3.9 is released!

    Special Note
    I just wanted to let you guys know I'm finally upgrading my phone. I should have my new Pixel 2 XL (Panda) within about 2 weeks! However, I don't intend to get rid of my 6P any time in the near future, so I will keep the monthly (tested by me on my own device) security patched releases going. Should I decide to get rid of my phone later on, I will make it very clear in this thread before doing so. I don't like the idea of releasing untested stuff, and I'm sure you guys don't like the idea of running it, so I just wanted to make that bit known in advance before any questions come up.

    Changelog
    • Merge all upstream changes from oreo-r6(???) branch. Google really has no idea what they're doing when it comes to release management.
    • Patch level: November 5th, 2017


    DOWNLOAD HERE


    md5sum/sha256sum/b2sum:
    Code:
    0e3e158db6569b46bc41e5e8552c52d6  kernvatore-angler_3.9-anykernel2-encrypted.zip
    ac53698ece6e62df20fceff685137dfba9ebef7d38821847608c80652f69b03d  kernvatore-angler_3.9-anykernel2-encrypted.zip
    f210ac9aaadf2f0df8687587390ab77ccde041274469579bbd5a6a8ecdfe1c16278c710869304e70ab683e978701395854203237d6c78ffac5e0ba7eb6e230a1  kernvatore-angler_3.9-anykernel2-encrypted.zip
    
    5978418b3efb49ac33c839b65196f3d4  kernvatore-angler_3.9-anykernel2.zip
    4860d357ab139180f4e5de3b110ac5eda9a2d11f1537762956ab8f2d8e4c88ee  kernvatore-angler_3.9-anykernel2.zip
    75aa5f9d941f47097559e5ecfd097f272c95cbad3b34d906db38edc2815da680befc3a6caff1474d126a04a76ed686b952b9a6a1b2f1b4eac521c807bf61e5bc  kernvatore-angler_3.9-anykernel2.zip
    15
    Kernvatore v3.6 released!

    Changelog
    • Merge all upstream changes from September security release (official Oreo release branch for 8.0.0).

    Note: F2FS is likely still not working, and just like I said last time and the time before that, I'll try to get another release out as soon as possible for that. No promises or ETAs. See post #195 for more details.


    DOWNLOAD HERE


    md5sum/sha256sum/b2sum:
    Code:
    47a08d142e78d1013153e3f6a70ee4b6  kernvatore-angler_3.6-anykernel2.zip
    bcf3b793c3406b056f2577e6523d1901f657ddf8607156a1db4f1aff7ec5db85  kernvatore-angler_3.6-anykernel2.zip
    e12b59e77863915f2ea354c1b5a89d28883069172f8e246f4dabd7d87d9a7ff7bc697d8fe699fb976e05bb15e37c47557f717d68d52295f2b949eb60345715bc  kernvatore-angler_3.6-anykernel2.zip
    14
    Kernvatore v3.4 released!

    Changelog
    • Merge all upstream changes from July security release for 7.1.2 and also from O DP3 image for 8.0.0, as the sources finally dropped a few days ago. Here's hoping DP4's sources arrive sooner to its release.

    Note: F2FS is likely still not working, and I'll try to get another release out as soon as possible for that. No promises or ETAs, but hopefully very soon. See post #195 for more details.


    DOWNLOAD HERE


    md5sum/sha256sum/b2sum:
    Code:
    35d916edb084654aa1efb15ab203180e  kernvatore-angler_3.4-anykernel2.zip
    30c1aa8b442b7aa6d8bf54b042e69cf566aa3852c47a2594730121c4feb22805  kernvatore-angler_3.4-anykernel2.zip
    86087ddcd34222d68df54e55b160b152dbad9316b51bd9999e99e6df2d767ac01d6b6f778d821081d08908ac1c4352624b15bb52473c9ed26dcd16a696cf8673  kernvatore-angler_3.4-anykernel2.zip