O.o

You sir are a genius and a pioneer! Thanks for your quick and awesome work!

We already have a custom kernel that is working with root do we need to flash this instead? Or they are the same?

+Nihar Gajare

Great .

Thanks +Chainfire your that BEST!!!!???

+Mark Stronge  

+Johnny Kat From the post: These do not switch your entire system to SELinux permissive mode like some other posted images do. Food for discussions, but I personally prefer it this way.

+Rehan Kodekar I didn't change anything of selinux options that's why I asked...

+Merk Mernerlerter 

Thanx man, really appreciated!! ?

It is a fail for me in both devices flashing the kernel. Am I missing something here? Please help.

+Rehan Kodekar thx I flash it anyway chainfire word is law..

+Rehan Kodekar some of the things you typed are either conflicting or unclear

Right now I don't have the tools to unpack the initramfs on my system, so I eagerly await the technical explanation.

There's one thing that deeply disturbs me, though: this is starting to look like an arms race between root-enabling apps and upstream AOSP/OEMs. This is not looking good for those who want to keep using the factory firmware and apps that need root privileges (eg. ClockSync - clock drift on some Nexus devices is terrible and the Italian GSM networks don't bother providing network time to their subscribers).

Failed to flash new kernel...i had to extract and fastboot flash... anyway thank you so much!

Nice

+Matteo Panella   Saved you a click: 

diff -uwb initrd/init.rc stock/initrd/init.rc

--- initrd/init.rc 2014-10-19 00:02:38.000000000 +0900

+++ stock/initrd/init.rc 2014-10-19 00:20:54.000000000 +0900

@@-596,7 +596,7 @@

service flash_recovery /system/bin/install-recovery.sh

class main

• #seclabel u:r:install_recovery:s0

• seclabel u:r:install_recovery:s0

oneshot

+Nikolay Elenkov: thanks. So it's as I thought, they're sealing off access to privileged contexts that could be used to write on /system.

This is bad.

+Matteo Panella No, it is actually good :) You have no business writing to  /system. Once dm-verity is deployed, it will result in an error anyway (of course you can disable if you can flash things). 

Dude, that was insanely fast... Great job!

You are awesome ! Thank you?

+Nikolay Elenkov: I have to rephrase my last sentence: I agree that /system should never be touched under normal circumstances (exception: updates to su, but as of late we need to reboot the device anyway to restart the daemon) and it's a good thing that upstream is enforcing such restrictions.

What I really don't like is the kind of escalation they're pulling: the more people try to root their device, the more upstream tries to block them. And yes, I know that sooner or later block-based OTAs and dm-verity are going to land on production systems. I just wish that by then Android gains proper SNTP support (the only reason I need root on my phone) :-)

Failed to flash kernel with the CWM recovery. Any ideas?

+Chainfire.. Awesome bro! Thanks for your hard work! ?

+Matteo Panella I don't think anyone really cares about how many people root. It's about making the platform more secure.

+Chainfire Magic

Omg extract the file and flash with fastboot. Check out the zip files before you try anything.

+Daves Williams yeah a lot of people that flashed it said it fail

+Karan Rajpal I already rooted it before.

I made a Flashable zip for nexus 5 download it here https://docs.google.com/file/d/0Bwu7SoZnJhgNUW1PYTNpNEtmdTQ/edit?usp=docslist_api

+Gary D

+Johnny Kat can you link that kernel?

+Larry Harris it's on xda but yeah I can post the link

Btw this is an updated boot take a look http://forum.xda-developers.com/showthread.php?p=56100828

up

Thanks you da man

Did not work for me. :(

Any idea on how to install it on encrypted device? Lollipop changed password derivation algo and TWRP doesn't decode partitions ("bad password") -> cant write to /system. CWM doesn't even notice, that device is encrypted.

I flashed the boot.img but still cannot gain root. SuperSU is installed.

solved: Flash the latest SuperSU

if nexus7 2012 can use it?

+Aayush Kumar

+ishan verma ??

Hmm everything is asking me for root now.

Yes. Great work, +Chainfire 

awesome! thank you!

You are awesome thnx mate :)

After fastboot flashing this new kernel on my N7 2013 and then flashing SuperSU v2.14 I still do not appear to have root access. I tried with Titanium Backup and Helium, but neither seem to work. I realize this could be an issue these apps needing to be updated to be compatible with this latest preview, but has anyone else gotten them to work? I get the SU prompt on Titanium, but even after granting access the app says that it cannot acquire root access.

+Tadej Rudec Thanks, however I'm running into a different issue. It seems that I can't access my internal storage. I've tried using several file managers on Android, and I can't mount it on my computer unless I'm in TWRP. I also cannot download anything from the browser, whether it's a picture or an APK. 

I'm on android l and lost my rocovey all I get is a dead android when I try to go to recovery. How do I fix this!!

+Juli TJ Yup, flashed with Google's factory images. I've also tried factory resetting.

I'm sorry, but how do you flash this? Flash recovery, flash kernel, flash SuperSU , right?

+Juli TJ I just flashed the image again, we'll see if that fixes it.

+Jose Morales Just reflash your recovery image via fastboot.

Flashed it is crashed

Eventually worked it out... Zip doesn't work but flashing boot.img using 'fastboot flash boot boot.img' and booting to recovery before installing latest SuperSU then rooting works. The key thing is to ensure you input 'flash boot' as part of the fastboot thing. Yay! :-) 

thanks sir +Chainfire for your quick response, works great!

+Chainfire You are the man. I use all of the software that you make because the competition simply cannot compete with you.

I'm going to be the newbie and ask "How do I flash a kernel?". Here goes;

How do I flash a kernel? I can get it to  boot (./fastboot boot /home/robin/Downloads/boot.img), but when I replace boot with flash I get the following;

sending 'kernel' (7150 KB)...

OKAY [  0.240s]

writing 'kernel'...

FAILED (remote: partition table doesn't exist)

finished. total time: 0.244s

+DroidModderX ROOT Mastersomething to consider adding in when you make the install video for the Nexus 7

Thanks!

+Robin Jacobs you just have reboot to bootloader and run the command: fastboot flash boot boot.img (replace boot.img with your final location), then reboot to recovery and flash SuperSU 2.14. Thanks to +Chainfire!

+Antonio Saco Cheers!

thanks for your work

+Pawel Kraszewski Try flashing the kernel using fastboot. /system is not encrypted because the vold utility which handles mounting and encryption, resides on that partition. Something else is probably causing the error in TWRP.

+Chainfire.. Working perfectly here. Nexus 5, Pro Key recognized as well

+Raed Al-Mohammadi What did you do? I got the same problem and i wasn't abel to solve it. Anyone +Chainfire?

Edit: Okay my boot image was corrupt so it didn't install super SU correctly. Once correctly flashed correct file it worked perfectly cheers +Chainfire.

Any help? I fastboot flash boot boot.IMG. but nexus 5 still not rooted.

+Robin Jacobs not sure mine fastboot but no root

+Devin Shoemaker Did you solve your problem? my /sdcard is still inaccessible. At least accessing with a file explorer app and on Windows 8, the folder is empty.

Can't download anything too. Exactly the issue you mentioned.

+Eric Liou I updated my platform-tools in the Android SDK and that solved the problem initially, however it came back for a reason I'm not sure of. I was very impressed with that preview, but I'm back on CM now. I'd say just make sure your Android SDK is up to date and see how that works!

Titanium Backup & Solid Explorer & Fqrouter 2 can not get the root permission.

I think it is because /system/xbin/su can not be accessed in Android L. 

I can't flash anything if I don't have root

Good job !!!

Wait a minute, so its imperative that use TWRP as my recovery instead of CWM?? I've been flashing v2.14 all day & can't get root..

This guy is fucking awesome. Keep up the bloody hard work.

+Rounak Gandhi Thanks :)

Waw

thank you so much 

Do you have a root for the Sharp Aquos crystal

No

Its nice too be here

Flashed above bootimg, flashed TWRP 2.8.0.1, flashed SuperSu 2.14. Still get "There is no SU binary installed". Anyone has any idea for me to try?

+Raiterio Patterson it worked for me with CWM recovery, no issues there

+Fanmake Tan Use the beta test version, latest is 6.2.0-test5 if you need Titanium working on rooted Android L

I'm on android l and lost my rocovey all I get is a dead android when I try to go to recovery. How do I fix this!!

+Alex Buell "fastboot erase cache" then flash recovery again

Already exist

That's easy

Nexus 7 2013 WIFI. Strange, for me SuperSu says  that "there is no SU binary installed" and i followed the steps correctly. Can anyone confirm it's working ok ?

EDITED: no init.d folder in etc.And cannot create manually.

Thank you!!

works like a charm... thank you

+Alex Buell where i can find it?

Awesome, works just fine on my tablet, thanks!

Suport all android devices..thanks...1 hours...finish..root.repartition,rom,upgrade..easy

Without pc

+Fabio Cannas Find what?

+Alex Buell the titanium backup test version! 

Is Greenify working for you guys?

+Fabio Cannas google for titanium 6.2.0 for the download link off their twitter feed

Ha ap

pp

+Alex Buell thanks!!!

Uu-7-7tigyhbvv

GKl 7lgNNym7L(

kgg

This kernel fucks me up my SD partition!

I got it to work after 2 tries... Didn't follow the docs the first time.... 

+Ionut Tudorel The same to you. Nexus 5 D821. 

App hider seems not to work with this ernel, but works with the other found on XDA, could this be because of selinux?

Another issue: TWRP backups are marked as 0 bytes in file explorers...

im rooted now but TB is not working

Just used this method, worked great. Thanks

Thanks +Rounak Gandhi

Any reason why twrp recovery won't flash with fadtboot flash recovery recovery.IMG ?

+naji hakimian I downloaded a TB 6.2 beta 5 version from its twitter, and works well. 

Siete i N.1

I can't open the zip to get the boot IMG.

Will u be making a fix for the nexus 4 here is the rom I'm running http://forum.xda-developers.com/showpost.php?p=56145658&postcount=17973 it is a LPX13D port

I have flashed it a few times and still not bale to get root.

+Korban Hadley install new ROM flash twrp IMG then kernel boot.IMG. if you have done it more than once it fails. Need clean lpx13d install

"These are zipped fastboot images, not CWM/TWRP flashable ZIPs!"...

So that is what I was doing wrong

Is there a snowball's chance of getting an unmodified LPW39 boot.img for the ADT-1?

+Adrian M M what do you need it for ?

GREAT !! thanks, finally my nexus 5 running the latest build of android L preview is rooted.. Good work!

+martin thomas try use 7-zip, its free and easy to extract files..

If someone needs help, I did this process:

At Nexus 5, enter in fastboot mode (VOL- and Power)

1- Extract this (http://developer.android.com/preview/index.html#download) Android Preview, this (http://download.chainfire.eu/580/SuperSU/nexus5-hammerhead-lpx13d-kernel.zip) kernel, this (http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img) TWRP and this (http://download.chainfire.eu/supersu) root, with 7-zip (7zip.org).

First you'll extract the extension ".tgz", after, the ".tar". Put the files at the same directory that you have the fastboot.exe and adb.exe.

2- Execute these commands on Operational System:

fastboot flash bootloader bootloader-hammerhead-hhz12d.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot update image-hammerhead-lpx13d.zip

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash boot boot.img

fastboot reboot-bootloader

fastboot flash recovery openrecovery-twrp-2.8.0.1-hammerhead.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

Nexus 5:

Enter at Recovery Mode.

Go to "Advanced", then "ADB Sideload"

OS:

adb sideload UPDATE-SuperSU-v2.14.zip

Reboot the cellphone and be happy =)

+Devin Shoemaker I'm having the same issue with not being able to view internal storage, were you able to fix it?

+Nick Letsom I had the same problem, fixed it with formating data partition in twrp. Remember that you lose all of your data by doing so.

+Jesse Salmi  That's rough, but I guess you gotta pay to play... I was running Sykopompos' kernel before Chainfire's and didn't have any issues. Just flashed back to it and I can access my internal storage just fine with it. Guess I'll just stick with this for now, I don't really feel like messing with the fallout from wiping /data at the moment ;)

+Nick Letsom I'm not sure if these things are even related, or what may be the cause, but internal storage is working fine for me. I did set the USB options to PTP though.

+Chainfire I just want to say thank you for all you have done for the android community :)

Your the man????$$$$

The boot image doesn't boot for me, dunno why :/ 

try to unzip the boot.img and flash it via cmd

Got to work now :D 

works with nexus 7 2012?

Can we please get this for Nexus 7(2012)?

I don't know, you can try, and if it's fall may be you will be able too reflash the original boot.img ? no ?

this working on Release??

What are these other bootimgs that entirely switch selinux to permissive

Well, verified that it does work on release

Succesful on Nexus 5. But I have a question: am I supposed to have changed the kernel for a custom one modified by you, isn't it? So, why my kernel ID is 3.4.0-g323bbd9 android-build@vpbs1.mtv.corp.google.com#1 Thu Oct 9 05:57:15 UTC 2014? Isn't it the official Google one?

I think he actually changed the settings for the security on the boot partition, not the kernel itself.. but I could be misunderstood

Makes sense... I'm a big enthusiast of these things and I want to know, haha

SElinux is the only thing I think he changed.. and only modified it slightly.. that's what I'm taking away from his

"These do not switch your entire system to SELinux permissive mode like some other posted images do."  I'd love to get more info on it.. but I don't think I'd understand it even if CF did attempt to explain it to me with very small words lol

+Raed Al-Mohammadi How did you fix that problem?

For the "there is no su binary installed and super su cannot install it this is a problem!" error

Thanks!

N7 2013, working on release.

Question re CF autoroot, if I have a Moto X XT-1060, unrooted but not stock, if I flash to stock 4.4.4 will the XT-1060 designation change?  I ask because your utility does not list XT-1060 as having any root option.

Oh, and if the autoroot is coming for XT-1060, about when (if you know)!

Hi, what about N7 nakasi?. Best regards

Flashed the file using fastboot and reinstalled SuperSU (2.1.8) in TWRP (2.8.1.0), root access fully restored :)

Happy newyer

Anyone have a root that will work on my boostmobile kyocera icon 4.4.2 kitkat ive tried with pc and w/o nothing seems to work?????

Is it okay to flash this kernel on my nexus 7 2013 running lollipop 5.0.1?

how to root MOTO X2 Lollipop

Desperately need to root my Verizon Galaxys5

THANK YOU LYSM

Hi

For lenovo vibe x2 ap?

,, Cm Flare s4 . how can I root

My device is Obi sf1

I can't install SuperSu.apk

I can't find bootloader method on google about my device

for marsmalow?

+Ariel Arnesto for lollipop

Video Hanna Anissa full

https://youtu.be/aVBydIL2FvA

Please refund my amount you're app sis fuckedup