[KERNEL] [January 29] ElementalX-N9 5.17 (Nougat) 7.03 (Oreo)

[mjc2251]

http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Use the modified boot.img from the chainfire thread and the new version of supersu. Booting up now...no device corrupted message...ill comment back on system read/write in a few.

EDIT: System is read/write, confirmed by installing Adaway and successfully applying hosts file. All is working perfectly with ElementalX 4.00!!!

 

[flar2]

I'm going to hold off on an official kernel update for tonight.

Chainfire's current root solution will likely change soon, as it's a work in progress. He says there is a possibility of a factory reset if your data partition is encrypted. I don't want people losing valuable data when they flash the kernel. At the very least, there could be bootloops.

For now, if you want system rw, flash this modified version of ElementalX-N7-4.00

https://www.androidfilehost.com/?fid=24052804347831454

The only change from yesterday's release is ro.secure=0 (incsecure boot.img)

 

[v12xke]

I'm going to hold off on an official kernel update for tonight.

Chainfire's current root solution will likely change soon, as it's a work in progress. He says there is a possibility of a factory reset if your data partition is encrypted. I don't want people losing valuable data when they flash the kernel. At the very least, there could be bootloops.

For now, if you want system rw, flash this modified version of ElementalX-N7-4.00

https://www.androidfilehost.com/?fid=24052804347831454

The only change from yesterday's release is ro.secure=0 (incsecure boot.img)

Confirming that with the modified kernel I now have write permissions to /system. I still get the red "corrupt" boot warning but I'm pretty sure how to get rid of that. Backup, reset and restore. Thanks!

 

[flar2]

Confirming that with the modified kernel I now have write permissions to /system. I still get the red "corrupt" boot warning but I'm pretty sure how to get rid of that. Backup, reset and restore. Thanks!

The warning is dm_verity. If you flash Chainfire's boot.img before flashing EX, you can get rid of it. But I will do something about that in the next release.

 

[STB2010]

adb sideloading this Kernel and r/w /system works fine. Adaway is working.
Now I'm also waiting for a fix for the corrupt boot message and a working TWRP.

Great work, flar2!

 

[v12xke]

Nexus 9 LTE unencrypted. Per @flar2, flashing su beta 2.50 first, then EX 4.0 (mod version) did get rid of the red "corrupt" boot warning. Did not reset or wipe anything. TiBu, Adaway, Root. Explorer all working. Full rwx access to /system. Super SU is definitely still a work in progress, but we're 90+ % there. Hang on and be patient. My N6 is next up.

 

[EMK2000]

Yesteday i had flash the factory image of Android marshmallow with full wipe... Today I have flash the latest twrp for flashing this custom kernel and root the device but when I boot into recovery twrp ask me the password... How can I fix that? Anyone can help me?

If you press "cancel", can you use it normally except perhaps you cannot mount /data?

If it is the case, do the following:
1. At the password screen, press "cancel"
2. Go to "Wipe" and then do a Factory Reset
3. Go to "Wipe" again and press "Format Data", type "yes"

After all, there should be no password and you can mount /data as normal.

Reference: http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049

Using these steps, I was able to solve the same problem on my Nexus 9.

 

[flar2]

Update

For Android 6.0 Marshmallow

I removed the permissive hack, this kernel is back to selinux enforcing

You NEED SuperSU-2.50 for this one!

I'm not pushing it to EX Kernel Manager quite yet, because many people may be unaware they need to update SuperSU

This will also get rid of the corruption warning on boot.

And system will be writable



Download:
ElementalX-N9-4.01 BETA


Changes:
-selinux enforcing
-sepolicy mod and dm_verity removal from Chainfire

 

[WhammyDroid]

Update

For Android 6.0 Marshmallow

I removed the permissive hack, this kernel is back to selinux enforcing

You NEED SuperSU-2.50 for this one!

I'm not pushing it to EX Kernel Manager quite yet, because many people may be unaware they need to update SuperSU

This will also get rid of the corruption warning on boot.

And system will be writable



Download:
ElementalX-N9-4.01 BETA


Changes:
-selinux enforcing
-sepolicy mod and dm_verity removal from Chainfire

Thank you!

Is a insecure boot image needed also?

 

[flar2]

Thank you!

Is a insecure boot image needed also?

No

 

[House.m.d]

Thanks for the update. Installing Beta Kernel and SuperSu 2.50 and Adaway make no Problems.

Sent from my Nexus 9 using XDA Free mobile app

 

[Holer Togni]

Thanks a lot for sticking to the N9!!

 

[Holer Togni]

My N9 won't accept the PIN to unlock the screen with 4.01 Beta and SELinux set to enforcing. However if I set SELinux to permissive (via adb while the screen is locked), the PIN is accepted.

I'm on the factory image (clean install) with SuperSU 2.50. Also flashed Chainfire's most recent boot image before ElX in order to remove the triangle warning message.

Obviously, if I flash back 4.00-sysrw the PIN is accepted and vice versa.

 

[topjohnwu]

@flar2 could you include SELinux permissive mode in aroma just like you did in M8? Some particular apps require it.
This is a really nice kernel, thanks a lot!!

 

[flar2]

@flar2 could you include SELinux permissive mode in aroma just like you did in M8? Some particular apps require it.
This is a really nice kernel, thanks a lot!!

Use the permissive zip, I think there is a link in the OP.

I guess it wasn't posted there. Here it is:
https://www.androidfilehost.com/?fid=23991606952602503

 

[EMK2000]

Using EX 4.01 with SuperSU 2.51 (not 2.50) works. In Root Explorer, it show that /system can be mounted R/W, however it failed to edit build.prop...so weird

 

[flar2]

Using EX 4.01 with SuperSU 2.51 (not 2.50) works. In Root Explorer, it show that /system can be mounted R/W, however it failed to edit build.prop...so weird

Some root apps may have to make changes. Also, SuperSU with selinux enforcing is still being worked on.

 

[PhilDX]

Using EX 4.01 with SuperSU 2.51 (not 2.50) works. In Root Explorer, it show that /system can be mounted R/W, however it failed to edit build.prop...so weird

I hit the thanks button by accident...

I noticed this with root explorer too but build prop editor in the play store by j rummy works fine

 

[frontalot]

How do I undervolt the CPU? Clicking the CPU voltage offset line in EXKM doesn't do anything? I can undervolt the GPU just fine, by the way.

 

[flar2]

How do I undervolt the CPU? Clicking the CPU voltage offset line in EXKM doesn't do anything? I can undervolt the GPU just fine, by the way.

Undervolting is deprecated on newer chips. Does more harm than good