yashsingh1/xdaforums huggingface dataset:
[SuperSU] jaxbierley:
Sort of going off what ramjet says above, I have a brief question.

I fastboot flashed the factory images yesterday and on order to gain root, used the permissive boot.img that was given to gain root when the first developer preview came out. Everything works fine, I have root and have flashed a custom kernel since. That being said, does using the permissive kernel first change how things are going to be affected. Such as (forgive me if this is stupid) battery life, or general performance? TYIA.
[SuperSU] VivaErBetis:
Tested and working. Thank you very much Chainfire :)
[SuperSU] TWEAKiMP:
I am not on android 5.0 if you meant that. i on xkat 4.0, based on android 4.4.2
[SuperSU] rajendra82:
My mistake. I thought you were talking about issues after upgrading to Lollipop.
[SuperSU] ELutts:
UPDATE-2.16 works with no issues on my devices

I just updated SuperSU earlier on my phone and my tablet and they have been running near perfect since. I'm running ART based Velocity ROM 4.4.4 for Mako (Nexus 4), and my tablet is the big surprise. Ive got the WiFi version on the Galaxy Tab 3 (SM-T210R) with 4.2.2 Neon V4 Beta 2 and the 3.4.5-blackhawk+Ubuntu kernel. I've had terrible times with that tab agreeing with anything i flash initially, but this was no problem. Used Flashify and copied to download folder, rebooted into TWRP 2.8.0.0 recovery. Everything is in perfect order. Great job Chainfire. You never cease to amaze.
[SuperSU] Badgie:
Problem with "Grant" dialog on KK 4.4.4

Hi. I'm running stock 4.4.4 unlocked and rooted on a Nexus 4. I have been using supersu since I loaded 4.4.4 (and in previous versions). In fact it was baked in when I installed the ROM. Up until now it has been fine.

This morning Greenify wanted su permission (update, presumably) and the supersu dialog came up. However none of the buttons on the dialog would respond so permission wasn't granted and it kept asking and timing out.

I tried reloading Greenify - no change - so I tried uninstalling and reinstalling the updates to supersu. I managed to grant su to a couple of apps (Ti Backup and WakeOnLan) but now the dialog is failing to respond on all the others.

Any thoughts?
[SuperSU] shinra00:
Go to setting in SuperSU and disable Tapjacking protection
[SuperSU] zadigre:
This question had been asked multiple times.

You probably have an app like Lux that is interfering with Supersu. Either disable this app, whitlelist Supersu in this app or disable tapjacking protection in Supersu

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[SuperSU] tobitege:
Running 2.19 beta (SuperSu Pro) on LG G3 (D855), ROM is AndroidNow 3.2 - Lollipop (V20A; rooted).

Occasionally I see 3 processes named like "daemonso:sugote" with each 25% CPU usage "hanging around". I can kill those within 3C Toolbox' task manager and nothing further happens. At the same time, all apps that require root already had root permissions granted prior.

Unfortunately, LogCat (and other derivates I tried) currently do not work for me (working on it).

May I kindly ask how I can "resolve" those processes (huge battery drain) or assist (as soon as I get logs back)?

Thanks in advance!
[SuperSU] Badgie:
Thanks
[SuperSU] Taomyn:
Just to add to the knowledge base, I sideloaded the Lollipop OTA to my Nexus 5, I first made sure the boot loader was unlocked and that SuperSU's OTA recovery was enabled (was running SuperSU v2.16 I think).

Did the upgrade with only one issue, had to recover debuggerd from an original KK image and that allowed the upgrade to work.

Result: SuperSU said I had lost root and could not fix it. Used CF-AutoRoot which successfully rooted then installed SuperSU v2.20

Everything seems fine so far, boot loader still unlocked and waiting for the "BootUnlocker" app to be upgraded for LL so I can hopefully use that again.
[SuperSU] Chainfire:
You need to figure out which process is causing it.

If you see "daemonsu:sugote:x:y" (where both x and y are numbers), then y is the process ID of the caller.

"ps | grep y" will then show you all processes associated with that, you can trace that all up the process tree, as the number following the process ID, is the parent's process ID.

For example:

# ps | grep sugote
root 6728 6727 24664 1284 c0197118 b6eb2e0c S daemonsu:sugote:0:6724

# ps | grep 6724
root 6724 6621 3160 588 c02770f4 b6f54ce8 S su

# ps | grep 6621
root 6621 6619 3200 748 c01a84e4 b6ed1520 S tmp-mksh

# ps | grep 6619
root 6619 5974 22616 1272 c02770f4 b6eb2ce8 S daemonsu:0:6616
(we got another su instance here, which is connected to PID 6616, so we use 6616 instead of 5974)

# ps | grep 6616
shell 6616 6611 3160 388 c02770f4 b6ef0ce8 S su

# ps | grep 6611
shell 6611 8421 3200 672 c01a84e4 b6efa520 S /system/bin/sh

# ps | grep 8421
shell 8421 1 10808 256 ffffffff 00021870 S /sbin/adbd

Walking the process tree ends at adbd in my case, but you'll usually see a package name like "eu.chainfire.supersu" (which would mean SuperSU is the issue) or "jackpal.androidterm" (Android Terminal Emulator). Figuring out which package is causing the issue is the first step into resolving it.
[SuperSU] nachtschicht:
Thank you for this great explanation! I also encountered this phenomenon and everything is now pointing to Titanium Backup (like I initially thought because it's often happening after I restore some app). So time to contact the dev of TB [emoji6]
[SuperSU] Chainfire:
Take note that just because its pointing at TiBu , doesn't necessarily mean it is an issue in TiBu. Could still be an issue in sugote itself. Exact reproducable steps are important both for them as for me.
[SuperSU] nachtschicht:
So sugote is a part of your project? I don't know supersu that well, I have to confess...

I reproduced it now 3 times in a row, it's always happening for me when I restore an app with another Google account (it's the only app I bought with this account), then after the restore is complete I can see this process consuming CPU time.

If you want more information just let me know, I will try to provide it.
[SuperSU] tobitege:
[MENTION=631273]Chainfire[/MENTION] Thanks, your explanation is great. Strange that those always come in three in my case. Will use ps to find out the processes.

---------- Post added at 18:46 ---------- Previous post was at 18:28 ----------

Those daemonsu:sugote processes were spawned by daemonsu:master (<- daemonsu:mount:master <- 1). I don't see one of my apps involved like TB right now. :confused:
[SuperSU] tobitege:
Installed today's official TB update of v6.2, but the daemonsu process occurr, still.
[SuperSU] CalicoZac:
The PlayStore only has up to 2.0.1, how can I update to the most recent stable version?

--------

Galaxy S4 Verizon - 4.3 MK2
[SuperSU] zadigre:
this has been asked multiple times...

you donwload the zip and flash the zip in recovery.

or you download de zip, extract the APK and proceed with the installation of this apk onto your device. First time you run SuperSU after installing the APK, it will ask you to update the binaries.
[SuperSU] CalicoZac:
Should I uninstall version 2.0.1 before I install 2.1.6?
[SuperSU] zadigre:
No
[SuperSU] VivaErBetis:
[MENTION=631273]Chainfire[/MENTION]

Sir, Google just published lollipop factory image for Nexus 4 ;)

Thank you very much!
[SuperSU] Chainfire:
I'm out, but the current Nexus 4 CF-Auto-Root should work, I updated that earlier today. Please try and let me know.
[SuperSU] VivaErBetis:
Uau!!! That was real quick!!!

Yes, CF Root for Nexus 4 works like a charm!!!! :good:

Thanks and best regards.
[SuperSU] chavocarlos:
Despite Android version reference, that says based on KitKat?
[SuperSU] VivaErBetis:
Yes. It works.
[SuperSU] chavocarlos:
Don't work using TWPR, are you using CWM?
[SuperSU] VivaErBetis:
That CF autoroot zip isn't a zip to be flashed from recovery. Just unzip its contents in your PC and follow the instructions of the download page and the batch file.
[SuperSU] 21plays:
Anyway to Flash through fastboot without custom recovery?
[SuperSU] Himeko7:
Same here... I'm on Nexus4 and just upgraded to lollypop, now TWRP won't mount partitions saying encryption password is wrong, so I can't install the binary.
[SuperSU] chavocarlos:
My fault, thanks.
[SuperSU] Chainfire:
Restore what? How? Play? TiBu? You may think you have described when it happens, but I still have no clue what you are doing what causes this. Details.
[SuperSU] Chainfire:
If you come across another daemonsu process, be sure to switch to the pid the name it says its connected to, instead of following its normal parent pid, or you will always end up at 1 (init). Quoting myself:

# ps | grep 6619
root 6619 5974 22616 1272 c02770f4 b6eb2ce8 S daemonsu:0:6616
(we got another su instance here, which is connected to PID 6616, so we use 6616 instead of 5974)
[SuperSU] Murad Ali:
Thanks
[SuperSU] twinkyz1979:
I am using your auto-root for the nexus 7 2012 wifi model. Wondering if you know why when i flash TWRP recovery I lose root? Also flashing your root through TWRP recovery does not work either.

Running the released version of Lollipop.
[SuperSU] tobitege:
[MENTION=631273]Chainfire[/MENTION]: thanks, I missed the one "branching" in your earlier post, sorry for that.

Now after unfreezing a single app in current Titanium Backup I found only one sugote process lingering around (literally, all operations finished minutes ago):

ps | grep sugote
root 22081 8135 28816 1220 ffffffff b6ed4e04 S daemonsu:sugote:10125:22076
root@g3:/ # ps | grep 22076
ps | grep 22076
u0_a125 22076 19392 3216 616 c0268618 b6f8ea00 S /system/xbin/su
root 22081 8135 28816 1220 ffffffff b6ed4e04 S daemonsu:sugote:10125:22076
root@g3:/ # ps | grep 19392
ps | grep 19392
u0_a125 19392 352 1642000 80780 ffffffff b6eabc70 S com.keramidas.TitaniumBackup
u0_a125 21626 19392 3216 504 c0268618 b6ec3a00 S /system/xbin/su
u0_a125 22076 19392 3216 616 c0268618 b6f8ea00 S /system/xbin/su

But after closing TB (by manually killing it), the above sugote process goes up the wall in CPU% (100% on a single core).

Also recorded adb logcat in separate terminal during same time, but it's several megs. Anything specific I could look for in there?

Thank you for your time and patience!

P.S.: I can reproduce the above also by freezing the same app again in TB and the corresponding sugote process jumps to 100% CPU when TB is gone.
[SuperSU] Krunk83:
How can I force an app to ask for root permissions? Nova launcher won't pop up.

OnePlus One
[SuperSU] zadigre:
If the app doesn't ask for root, it doesn't need root.

There's no way to force that unless the app has an option to enable root features.
[SuperSU] Krunk83:
It's nova launcher and it needs root for some settings. Not asking on 5.0 lollipop.

OnePlus One
[SuperSU] pjadec:
Nova Launcher doesn't need root permissions
[SuperSU] Krunk83:
You're wrong. Simply put.

OnePlus One
[SuperSU] bombadier:
I have just updated my nexus 4 to stock lollipop and nova launcher doesnt have the hide clock option, its missing compared to my 4.4.4 rom
[SuperSU] pjadec:
My rooted G2 and I use Nova Launcher and it doesn't ask any root permissions.

Sorry my mistake. You have choose hide clock in settings then supersu ask root permission

Maybe that option doesn't work with LP. Until Nova Launcher will be updated or something has been updated.
[SuperSU] Krunk83:
Yup thats what im missing.

Yeah that's what needs root.

OnePlus One
[SuperSU] pkelly517:
Wow. That's the way to get help.
[SuperSU] dante2p:
SuperSU 2.16 work fine in CyanogenMod 12 unnoficial- Lollipop, Xperia L.
[SuperSU] AkiraProject:
Just flashed the zip through recovery. Works amazing)
[SuperSU] Krunk83:
How else should I have put it? I don't have time for XDA thread drama.

OnePlus One
[SuperSU] matrixzone:
[MENTION=631273]Chainfire[/MENTION] need your help

I have updated my AT&T Samsung Galaxy S3 today. This was small incremental Android 4.4.2 update. Now after the update, I am not able to install the TWRP through ODIN.

The whole ODIN process works but on reboot I see only the stock recovery.

Please help me installing my favorite App -> SuperSU
[SuperSU] pkelly517:
Or manners, apparently.

You might have mentioned that Nova asks for root when trying to use the center clock. You could have taken the opportunity to teach a little bit. Instead, you went with condescension.

Best of luck to you.
[SuperSU] :
Hi there, flash the latest version from here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar and flash via Odin...

Anyway post this query in your appropriate device forum next time...

This thread should only be about SuperSU.... :good:

---------- Post added at 05:44 PM ---------- Previous post was at 05:39 PM ----------

Don't, he doesn't need it.. :p

---------- Post added at 05:47 PM ---------- Previous post was at 05:44 PM ----------

Try CF Auto Root... :good:
[SuperSU] Chainfire:
v2.22 beta released - kindly test as I want to upgrade this to a stable release available from all the stores over the next few days
[SuperSU] Savok:
Correct, and worth buying if only to support the dev IMO.
[SuperSU] sdeft:
Hi Chainfire

Would it be possible to make a version with grant as default without asking ?
[SuperSU] Pons:
Let's preface this with that is incredibly insecure and not very bright. One rogue app and you're done.

Now that that's out of the way, go to settings and change default access from prompt to grant and see what that does.
[SuperSU] theone10:
I don't agree with that . You can made it your default for your phone
[SuperSU] Reviewers:
Worked like a charm Chainfire.
[SuperSU] mermaidkiller:
When I run 'su' from a terminal app, the command changes the terminal settings, i.e. no prompt (e.g. '#') is shown and when e.g. pressing Ctrl+X a '^X' is echoed. This is not the case in the same app before issuing 'su'.

Does 'su' change the terminal settings ?
[SuperSU] SmasherDK:
Works very nice :D
[SuperSU] b3er:
Hi! Where can i find a link to the source code or public repository of SuperSU?
[SuperSU] DarkhShadow:
I don't believe SuperSU is open source, or if it is it might be on his github if he has one
[SuperSU] segv11:
Set the logging for Terminal to "access only". The "full" logging is confusing the shell so that it thinks it its non-interactive.
[SuperSU] b3er:
I'm just wondering, how is it - a potentially dangerous application, focused on security, has a closed source code.
[SuperSU] shaggyskunk:
It's potentially dangerous because Rooted phones have more exposure... Which is one of the reasons that CM is developing it's new roms without root.

Superuser privileges given to every app on your phone, is nuts... In my humble opinion.

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] b3er:
First of all, sry for my english.

I think chainfire is a great and productive developer, but the advantage of open source is the community, which can test it for bugs and exploits. Now we have a obfuscated code supported by one man. Devs make mistakes, always :). And the closed source prevents other devs to eliminate and find vulnerability in application. Security by obscurity is useless.
[SuperSU] jna9000:
I don't think we should discuss open vs. closed source in this thread.

Gesendet von meinem GT-I9000 mit Tapatalk
[SuperSU] shaggyskunk:
I agree. This thread is about an application that has been developed for our phones... It is NOT about the philosophical questions of the approach to Development.

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] b3er:
Ok. I've researched the app(ver 0.88) by one day using decompiled obfuscated code to find vulnerable code, and i found it(already posted to chainfire), executing this code can give SU rights to any app on the device without any user interaction(and it doesn't need any permissions). Due to closed source, we all are in dangerous situation. We can't analyse completely the code flow, so we can't say the app is safe at 100%.

So SuperSU is insecure at the moment. I'm just warn you...
[SuperSU] vlt96:
It is up to chainfire

Seek the signature below the line;)
[SuperSU] mermaidkiller:
Thanks, this works !
[SuperSU] crachel:
Stop being so alarming with your language. There are always inherent risks with root access. The precursor here would be you had to side-load or otherwise download a dodgy app that intended to do something malicious. That's your fault.
[SuperSU] dimebagdan65:
To clarify:The Android OS is open source. Apps are the IP of their creator and hence, they are free to disclose or keep their source private at their own discretion.

This is fact.
[SuperSU] Alexander1988:
After searching extensively I couldn't find the link for 2.22. Tried Google+, chainfire.eu, so...
[SuperSU] Giobio:
Go to the supersu beta version:

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

First post has the link you are searching for.
[SuperSU] defim:
[MENTION=631273]Chainfire[/MENTION]

I just noticed this in logcat with CM Android 4.4.4:

E/SuperSU(1675): SU BINARY IS NOT RUNNING AS "u:r:init:s0" - THIS WILL CAUSE ISSUES

Any advice? Which issues whould i have?
[SuperSU] Chainfire:
Depends. If CM is running permissive, nothing. If enforcing, all sorts of **** may happen.

Post the outputs of:

ps -Z | grep daemonsu
su --self-test
[SuperSU] defim:
SELinux-Status shows "Disabled".

I haven't noticed any rot related problems, so adb works with su, ssh & ftp apps, Xposed, file explorer.

CM is exactly 11-2014-1028 (by Quarx for Defy)

I'ts the latest SuperSU (pro) from Play Store

adb shell "ps -Z | grep daemonsu"

- root 1181 1 daemonsu:mount:master
- root 1192 1181 daemonsu:master
- root 3090 1192 daemonsu:10064
- root 3568 1192 daemonsu:10055
- root 4561 1192 daemonsu:0

adb shell "su --self-test"

version_code: 200
version_name: 2.00:SUPERSU
sdk: 19
daemon_sdk: 1
multiuser_sdk: 1
multiuser_userid: 0
multiuser_username: (null)
selinux_present: 0
context[base]: FAIL
context[u:r:shell:s0]: FAIL
context[u:r:shell:s0-->u:r:system:s0]: FAIL
context[u:r:shell:s0-->u:r:system_server:s0]: FAIL
context[u:r:shell:s0-->u:r:system_app:s0]: FAIL
context[u:r:shell:s0-->u:r:platform_app:s0]: FAIL
context[u:r:shell:s0-->u:r:untrusted_app:s0]: FAIL
context[u:r:shell:s0-->u:r:recovery:s0]: FAIL
context[u:r:system:s0]: FAIL
context[u:r:system:s0-->u:r:shell:s0]: FAIL
context[u:r:system:s0-->u:r:system_server:s0]: FAIL
context[u:r:system:s0-->u:r:system_app:s0]: FAIL
context[u:r:system:s0-->u:r:platform_app:s0]: FAIL
context[u:r:system:s0-->u:r:untrusted_app:s0]: FAIL
context[u:r:system:s0-->u:r:recovery:s0]: FAIL
context[u:r:system_server:s0]: FAIL
context[u:r:system_server:s0-->u:r:shell:s0]: FAIL
context[u:r:system_server:s0-->u:r:system:s0]: FAIL
context[u:r:system_server:s0-->u:r:system_app:s0]: FAIL
context[u:r:system_server:s0-->u:r:platform_app:s0]: FAIL
context[u:r:system_server:s0-->u:r:untrusted_app:s0]: FAIL
context[u:r:system_server:s0-->u:r:recovery:s0]: FAIL
context[u:r:system_app:s0]: FAIL
context[u:r:system_app:s0-->u:r:shell:s0]: FAIL
context[u:r:system_app:s0-->u:r:system:s0]: FAIL
context[u:r:system_app:s0-->u:r:system_server:s0]: FAIL
context[u:r:system_app:s0-->u:r:platform_app:s0]: FAIL
context[u:r:system_app:s0-->u:r:untrusted_app:s0]: FAIL
context[u:r:system_app:s0-->u:r:recovery:s0]: FAIL
context[u:r:platform_app:s0]: FAIL
context[u:r:platform_app:s0-->u:r:shell:s0]: FAIL
context[u:r:platform_app:s0-->u:r:system:s0]: FAIL
context[u:r:platform_app:s0-->u:r:system_server:s0]: FAIL
context[u:r:platform_app:s0-->u:r:system_app:s0]: FAIL
context[u:r:platform_app:s0-->u:r:untrusted_app:s0]: FAIL
context[u:r:platform_app:s0-->u:r:recovery:s0]: FAIL
context[u:r:untrusted_app:s0]: FAIL
context[u:r:untrusted_app:s0-->u:r:shell:s0]: FAIL
context[u:r:untrusted_app:s0-->u:r:system:s0]: FAIL
context[u:r:untrusted_app:s0-->u:r:system_server:s0]: FAIL
context[u:r:untrusted_app:s0-->u:r:system_app:s0]: FAIL
context[u:r:untrusted_app:s0-->u:r:platform_app:s0]: FAIL
context[u:r:untrusted_app:s0-->u:r:recovery:s0]: FAIL
context[u:r:recovery:s0]: FAIL
context[u:r:recovery:s0-->u:r:shell:s0]: FAIL
context[u:r:recovery:s0-->u:r:system:s0]: FAIL
context[u:r:recovery:s0-->u:r:system_server:s0]: FAIL
context[u:r:recovery:s0-->u:r:system_app:s0]: FAIL
context[u:r:recovery:s0-->u:r:platform_app:s0]: FAIL
context[u:r:recovery:s0-->u:r:untrusted_app:s0]: FAIL
[SuperSU] MrKaon:
So guys for rooting lollipop on Nexus 5 stock all I need is flashing latest zip with TWRP?

No more need to flash modified kernel?
[SuperSU] Chainfire:
SELinux is disabled, don't worry about SELinux things then :)

Initial root requires using CFAR. You can update using TWRP afterwards.
[SuperSU] defim:
Ah, thanks. Was worried, because there was nothing about SE, only that it "it will cause issues"
[SuperSU] Himeko7:
That won't work with encrypted phone, current twrp can't decrypt storage on Lollipop.
[SuperSU] rxxt:
I also just figured that out, by trying.

Does anyone know if there is another solution, where you not need to wipe your device? :)

(I have a Nexus 5 with Lollipop.)
[SuperSU] Chainfire:
SuperSU BETA v2.23 available for immediate testing - https://plus.google.com/113517319477420052449/posts/jGoDoPPZUdT
[SuperSU] pan.droid:
What's the MD5 for 2.16? Why are there never MD5s?
[SuperSU] Cile90:
Nexus 4 L 5.0

TWRP 2.8.1.0

I have flashed the 2.16 to same msg and 2.23

Is it twrp issue or
[SuperSU] CyberpodS2:
V2.23 running on Verizon S5 4.4.4 with SafeStrap. TB, greenify, many other root apps and a ton of xposed modules. All is running as it should.
[SuperSU] :
Run CF auto root to root your device... Here you go.. http://autoroot.chainfire.eu/

As simple as that... :good:

TWRP doesn't support encrypted phones(L is encrypted)...

Hence go forward with CF Auto Root...http://autoroot.chainfire.eu/

It's as simple as that... :good:

---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------

Dude, first you've got to root with CF Auto Root... http://autoroot.chainfire.eu/ :good:

---------- Post added at 03:35 PM ---------- Previous post was at 03:32 PM ----------

There's no MD5.... Generally there has never been the need for one because SuperSU file size is so small, there's a negligible chance of failed downloads...

In case your flashing doesn't go correctly due to corrupt download, you can download again and reflash in a matter of seconds... :)

Still if you go paranoid about MD5s, I suggest CF auto root for you... :good:
[SuperSU] Ja_som:
Is it? Because in settings - security I found option to encrypt my tablet. So now I'm not sure if is encrypted, or is not, or what...

EDIT:

I found some info here:

http://www.cnet.com/how-to/how-to-encrypt-an-android-5-0-lollipop-device/

So is not encrypted after update...

[MENTION=631273]Chainfire[/MENTION] also I have question to you...

If I encrypt my device, will I lose root which I did with your great auto root?

Thank you.
[SuperSU] :
AFAIK, encrypted by default...

AFAIK, you can't...

Check this post for details... http://xdaforums.com/showpost.php?p=55656370&postcount=2
[SuperSU] Ja_som:
I edited my post, it looks like is not encrypted after update, encrypted are only new devices, like N9 and N6 (I think)

OK, thank you for this...

Don't worry, I click Thanks every time when someone help me ;)
[SuperSU] aavvaallooss:
Is only encrypted by default in Nexus 6
[SuperSU] Ja_som:
So, N9 is not by default? For that reason is maybe auto-root available for N9 on chainfires page.
[SuperSU] kingvortex:
As far as I know, only the /data partition is encrypted when enabling device encryption. This means that root etc remains unaffected and custom recoveries and other methods can access /system and other unencrypted partitions.

Also, both new Nexus devices are encrypted by default. See this support entry by Google.

Sent from my C6603
[SuperSU] bombadier:
Yeah twrp will need an update to deal with the new encryption methods with android 5,dees_troy posted something about it on g+

Tapatyping fae the Nexus 4
[SuperSU] rxxt:
Yes, but I was looking for a solution where it is not wipe the device.

From http://autoroot.chainfire.eu/

ENCRYPTION
Warning: If your device storage is encrypted, using CF-Auto-Root will wipe your data !
[SuperSU] :
Backup everything with your Google Account and Helium app....

Then root with CF Auto Root.. :good:
[SuperSU] aavvaallooss:
I don't know about N9, sorry