SuperSU updated to v2.13
Posted on 2014-10-10, 117 comments, 700 +1's, imported from Google+/Chainfire

NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.

Holy wall of text, Batman!

Time for a 'stable' SuperSU update! There have been quite a few beta releases the past few months, with lots of under-the-hood changes, lots of bug fixes, lots of compatibility additions, etc.


Again, a fair amount of work has been done to keep SuperSU operational on the latest AOSP builds, as security-related changes to AOSP are likely to end up in retail L. The changes are quite extensive and a departure from previous strategies to keep SuperSU operational on AOSP. As a side-effect of this, it may ultimately actually increase compatibility for root apps between different Android versions (and be less work for root app devs to support), as if it ends up working well on L, I will back-port these changes down to 4.2. It should be noticed that these patches are already in-use and tested against 4.4.

Cryptic and unspecific, I know. I will write about these things in detail once L is released (any day now?), if I don't have to revert them.

So what are the chances of this working on L at release? If we're lucky, the CF-Auto-Root's for  the Nexus devices will work out-of-the-box, but there's no way of knowing yet. There are dozens of things that could still go wrong, in fact, I have some concerns that ultimately we may need to have modified boot.img's to have root at all. We'll see when we'll see!

One thing I can tell you is that OTA survival mode will be very unlikely to work between 4.4 and L, at least initially.

Architecture specific binaries

SuperSU now comes with architecture specific binaries for: arm (v5), arm-v7a, arm64 (v8a), x86, x64, mips and mips64. The 64-bit variants are officially supported from L onward, so obviously they have not been tested on production devices yet.

CF-Auto-Root currently still always installs the arm (v5) binaries. "su -h" will display the specific version you are using.


Amazon now distributes SuperSU as well, but their vetting process is more extensive and much slower than Play, so expect Amazon releases to generally lag behind Play releases.

Android TV

Aside from adding the CF-Auto-Root for it to my extensive list, this version of SuperSU brings some minor but much-needed improvements that just make it behave significantly better.


SuperSU now cleans up leftover packages from the root list at boot (if re-authentication is enabled). While this really is a minor thing, I want to point it out explicitly because on some devices and Android versions, if you move root apps to the SD card, this cleanup will be performed before Android has scanned the SD card for the apps. So from the perspective of SuperSU, these apps do not exist, get removed from the root list, and well re-request root access when run. 

A proper solution is still under investigation, and it does not happen for me on any of my 4.4 devices. Either way, if you find apps are losing root access on reboot, a work-around for now is turning off the 're-authentication' feature. Please do report this and your device and firmware details to the SuperSU threads on XDA if it happens to you.


The latest (stable) flashable ZIP is available from as always. All CF-Auto-Roots have already been updated.

I will update Play tomorrow, assuming no showstoppers are found by those flashing the ZIPs, which will probably be a staged rollout. So best-case scenario, everyone should be updated come Monday.


The main thread is here:

The thread for beta releases can be found here:

Special thanks to all the beta testers

Flashable ZIP

For the modders and exploiters amongst you, I have added some documentation to the update-binary script. It's not complete yet, and there are a number of changes and improvements I still want to make, but I'm sure it's more helpful now than it was before.


There have been a few changes to the CF-Auto-Root installer as well. One noteworthy one is that in preparation for L having encryption enabled by default, it no longer touches /data. This is both good and bad.

The good is that it doesn't need to know your decryption key, the process remains automatic, and encrypted phones are no longer wiped on usage of CF-Auto-Root.

The bad is that this means some /data cleanup code is run on first boot after rooting, which may trigger a (one) reboot in the process. I do not expect bootloops because of this, it works fine on all the devices I have tested it on, but you never know.

Additionally, because CF-Auto-Root cannot distinguish between a garbage and an encrypted partition, it no longer fixes OEM unlock issues. On several fastboot based devices, the OEM unlock command, instead of formatting /data and /cache, wipes them. Android will not automatically re-format them anymore (used to in 2.x days), which means that your device will forever bootloop until you manually format /data and /cache (which CF-Auto-Root did for you automatically in the past).

Last but not least, some changes have been made to allow the progress to be visible on some new Qualcomm based devices. While I would normally not waste words on something as trivial as this, I would like to point out that these devices no longer support fbdev to put content on screen, but instead use something called Qualcomm overlay. Nothing basically wrong with that either, aside from the absolutely horrid fact that the interface to this changes between different kernels in a completely incompatible way, pretty much requiring a userspace program to use the exact right version of kernel headers to do something as basic as putting anything onscreen. Making a non-kernel specific binary that support a wide range of devices is thus now nigh impossible unless some very ugly code and errorprone methods are employed. As such, I expect that ultimately there will be no visual progress for CF-Auto-Root anymore on Qualcomm based devices, as I certainly can't be bothered keeping track of these shenanigans.


  • Improved support for Android TV (adjusted icon, disable some features, use device default theme by default, etc)

  • Parse UID names to numbers manually if the system fails to do it

  • Fix system user not gaining root even if "trust system user" enabled

  • Transition to init context if started in init_shell context (if possible)

  • Adjust boot sequence for encrypted devices

  • Support MCS for -cn/--context switch

  • Silence a larger number of audits on latest AOSP/L

  • Many small changes to fix support for latest AOSP/L

  • Secondary users are no longer able to change trust system or respect CM settings

  • Added experimental supolicy binary

  • Check for removed apps at boot, and forget their settings if re-authentication is enabled

  • Amazon Appstore support

  • Remove APK restriction to install to ARM and X86 only (issue for MIPS)

  • Notify interested apps (with root granted) when overlays need to be hidden

  • Transition to init context if started in kernel context

  • Experimental builds for armeabi-v7a, arm64-v8a, x86-64, mips, mips64

  • Fixed erroneous fd close that could cause su session freezes

  • Fixed occasional freezes and wrong exit code in sugote

  • Remove busybox dependency in TWRP/CWM binary updater

  • Fixed missing sugote-mksh in backupscript

  • Fixed install script wiping out SuperSU Pro

  • Added option to disable mount namespace separation

  • Fix bug where grant as default access still showed a prompt 

  • Added reboot button in dialog after binary update

  • Added tapjacking protection - may cause issues with screen dimming apps!

  • Added removing Team Venom SU

  • Added new dalvik-cache paths to clear on package maintenance

  • Fix exitcode sometimes being wrong when full content logging is enabled

  • Fix automatic OTA survival

  • Updated language files

SuperSU Download

King sky commented on 2014-10-10 at 13:18:


Bernd Höhne commented on 2014-10-10 at 13:20:

if you can't be yourself, be batman!

Lionel Kaiser commented on 2014-10-10 at 13:27:


Manuele Polverini commented on 2014-10-10 at 13:30:

When will you update play store app?


Jamal Bellabrouj commented on 2014-10-10 at 13:35:

+Manuele Polverini

Did you even read the post?

Rich Cataldo commented on 2014-10-10 at 13:39:


Manuele Polverini commented on 2014-10-10 at 13:41:

Ah, ok..

"I will update Play tomorrow, assuming no showstoppers are found by those flashing the ZIPs, which will probably be a staged rollout. So best-case scenario, everyone should be updated come Monday."

Excuse me, i skipped this xD

Chirayu Desai commented on 2014-10-10 at 13:49:

+Chainfire, you could probably use setup_fs (system/extras/ext4_utils/setup_fs.c) to fix at least some of the OEM unlock issues, if not all.

This was last used by Google for Galaxy Nexus, and does work on Sony devices too (we're using it on all 2012+ devices supported by CM currently, which is all devices including and after Xperia T).

Chainfire commented on 2014-10-10 at 13:52:

+Chirayu Desai thanks, nice find. It's only a handful of devices suffering from this though, not exactly a priority.

Neil Tong commented on 2014-10-10 at 13:54:

Joshua Aniobi commented on 2014-10-10 at 14:06:

+Chainfire.. Keep up the epic work, man! Thanks again for all you do

[ 10tacleBoy ] commented on 2014-10-10 at 14:07:


Joe Repasy commented on 2014-10-10 at 14:09:

Thanks for your hard work!

Wug Fresh commented on 2014-10-10 at 14:30:

Thank you for all the work, updates and detailed info!

Gevo Lebron commented on 2014-10-10 at 14:48:


Антон Кузнецов commented on 2014-10-10 at 15:00:


Per Erik Skille commented on 2014-10-10 at 15:24:

Thanks ?

P. Murali Krishna commented on 2014-10-10 at 16:40:


Mark Onyx Taggueg commented on 2014-10-10 at 17:17:


Anthony TSE commented on 2014-10-10 at 18:25:

thx a lot

Michal Horna commented on 2014-10-10 at 18:46:

a big thank you, my friend

Angad Deep Singh Sehdeva commented on 2014-10-10 at 20:05:

Chainfire is GOD!!!

Julio Novoa commented on 2014-10-10 at 22:08:


Ruaraidh Mackay commented on 2014-10-10 at 23:29:
刘春 commented on 2014-10-10 at 23:41:


Nguyễn Lâm commented on 2014-10-11 at 02:57:

Thanks . i have rom note4 N910P need suport CR-root


Thomas Reintjes commented on 2014-10-11 at 07:15:


Aragaki Yui commented on 2014-10-11 at 08:37:


David Castle commented on 2014-10-11 at 20:46:

Can Super SU cause the os update to fail? I have a Samsung siii that I got from Craigslist that has Super SU on it and I have tried 4 times to os update with failure. I turned it off in settings but same thing. I reset cell to factory but Super SU is still there. Any suggestions?

Omair Zeeshan commented on 2014-10-11 at 21:47:

thank you so much

Jason Fleisher commented on 2014-10-11 at 23:08:

I just bought the Pro code from Amazon for my Google Play app version. Seems to work fine so far. Perfect combination! Amazon coins and Play Store updating.

Ahmer Jamil Khan commented on 2014-10-12 at 04:39:

Instead of a flashable zip, can we simply update with an APK file?

Derek Logan commented on 2014-10-12 at 09:14:

Hey can you help with la-912t generic quad core m8382 4.2.2

Zenik StFu commented on 2014-10-12 at 09:18:

Thanks A Lot man

Djcarwyn Harris commented on 2014-10-12 at 09:40:

How do I update from v2.01 please?

ahmed mohammed commented on 2014-10-12 at 11:43:


Andrea Florio commented on 2014-10-12 at 18:06:

on google play , the latest release is still 2.01 .. any plan to update it there too ? 

(using galaxy S4 here) 

Chainfire commented on 2014-10-12 at 18:25:

10% Play rollout is complete, reviewing found issues first before rolling out the other 90%

Ekansh verma commented on 2014-10-12 at 18:59:

Can you +Chainfire please Share the apk will be eaiser to install...

Jason Pasch commented on 2014-10-13 at 02:29:

thank you +Chainfire I am a very happy user and supporter of your work.

STEPHEN DOKU commented on 2014-10-13 at 05:35:

+Ekansh verma you can extract the compressed file, the apk is in the common folder. That's what I use to update.

STEPHEN DOKU commented on 2014-10-13 at 05:36:

Good job buddy

Chris Wells commented on 2014-10-13 at 07:14:

+Chainfire  - 2.13 had issues on Galaxy S4. No luck even stopping the app, clearing the cache and restarting. Rolling back to 2.0 fixed the issue (App  and Log forever spinning). But rolling forward again (auto update in play) brought the problem in again.

Chainfire commented on 2014-10-13 at 09:37:

+Chris Wells to help find and fix this issue, report to the XDA thread. G+ is not a support environment

Robert Louis commented on 2014-10-13 at 12:10:


Saleh commented on 2014-10-13 at 14:14:

Good job !!

Hilton Bowman commented on 2014-10-13 at 21:51:

Updated thanks

Stawek Putans commented on 2014-10-14 at 06:36:


Jan Gehrig commented on 2014-10-14 at 08:48:

You're still great! Thank you so much Grandmaster!

Htet Halaung commented on 2014-10-15 at 09:53:

Hi help oppo x9006

Róbert Vasinka commented on 2014-10-15 at 14:16:


Miguel Noa commented on 2014-10-15 at 14:35:

Thanks for you work

Darios Gregorio commented on 2014-10-16 at 01:13:

Men thanks your

Super u dude

Dean Farina commented on 2014-10-16 at 15:18:

How can i autohorize the xmod games for coc mod please answer

Bret Hicks commented on 2014-10-16 at 21:44:

So I have SuperSU on my Nexus5 but it is version 2.02. Play Store doesn't show an update and the version of what I see on the Play Store is 2.01. This is really confusing me. Should the Play Store have 2.14 by now?

Musio Musio commented on 2014-10-16 at 23:10:


Musio Musio commented on 2014-10-16 at 23:11:


杨小鹏 commented on 2014-10-17 at 06:24:


Olley pang commented on 2014-10-17 at 10:47:

I root my phone because i want to use xmode but it stuck when i open and restart my phone can anyone help me

apachegroup commented on 2014-10-17 at 14:16:

A fault in update-binary in '' :


if [ "$API" -eq "$API" ]; then

if [ "$API" -ge "17" ]; then




It should be:

if [ "$API" -ge "18" ]; then

I think, Since Android 4.2 needs setuid/setgid flags to be set on su binary.

Lars Stokholm commented on 2014-10-17 at 17:08:

+Chainfire I can't get SuperSU 2.14 to work in the new developer preview on the Nexus 5. Flashed via TWRP, but on startup of SuperSU it says binary isn't available and it can't be installed. Just a heads up. :-)

Алексей Сычев commented on 2014-10-17 at 17:16:

+Lars Stokholm same for me, nexus7 2013

Kyle Null commented on 2014-10-17 at 18:15:

Nexus 5 - new lollipop preview, no SU binary installed.

Bret Hicks commented on 2014-10-17 at 18:19:

Give the man at least a day guys, jesus.....

Kyle Null commented on 2014-10-17 at 18:23:

+Bret Hicks

Of course.  We're just letting other people know that they can stop trying until it gets fixed.  Would've saved me 45 minutes to know that sooner.

Jonathan Yee commented on 2014-10-17 at 18:26:

I rooted my Galaxy S5 back in May using Chainfire AutoRoot for the T-Mobile version, SM-g900t. Haven't flashed anything since; just wanted to have root access for a couple apps.

When Android 5.0 Lolipop rolls out to the Galaxy S5, how can I update my phone to that? Would I have to unroot, update to Lolipop OTA, and root again? (if so, would I have to find a different method of rooting or can I use the same Chainfire AutoRoot?)

Or is there a way to update to Lolipop without losing my root?

Rafael Mendoza commented on 2014-10-17 at 20:59:

Confirmed... Doesn't work with LPX13D 

Spiridon C. Dalietos commented on 2014-10-17 at 21:00:

+Jonathan Yee best way is to do clean install. Download your image from samfirmware, backup your data and update via Odin... Then root back again.

Jonathan Yee commented on 2014-10-17 at 21:05:

+Spiridon C. Dalietos If I have to root again, what method would I have to use? Assuming the firmware version is Android 5.0, would I have to find a root method that specifically works based on 5.0?

Spiridon C. Dalietos commented on 2014-10-17 at 21:09:

+Jonathan Yee the same way you rooted, via cwm or twrp, and yes, you will need root for 5.0

Jonathan Yee commented on 2014-10-17 at 21:11:

+Spiridon C. Dalietos Would a better method be for me to flash the 5.0 ROM (when it is released) using Mobile Odin? That way I can keep root?

Spiridon C. Dalietos commented on 2014-10-17 at 21:18:

Nexus 5 updated to lpx13d Lollilop just few hours before. I have tried su 2.0 for L, 2.01, 2.02 up to 2.14 with no luck at all... Keep getting binaries errors or installation errors via flash from twrp...

Jonathan Yee commented on 2014-10-17 at 21:26:

+Spiridon C. Dalietos What is that supposed to mean?

Val Ozuna commented on 2014-10-17 at 22:15:

+Spiridon C. Dalietos getting the same thing with new su from op. Using cwm running 5.0. Not complaining just letting you know.

Rob M commented on 2014-10-17 at 22:22:

any update coming to SuperSU to support the newest developer preview LPX13D (Nexus 5)? It's currently un-rootable. 2.15?

Val Ozuna commented on 2014-10-17 at 22:28:

+Robert Matear I'm sure he's working on it bro. Patience!

Josh Barker commented on 2014-10-17 at 22:44:

Nice app

Ben Sullivan commented on 2014-10-17 at 22:51:

+1 for wanting LPX13D support :) Awesome work Chainfire!

Rob M commented on 2014-10-17 at 22:53:

+Val Ozuna cool, can't wait to have root for this

Rob M commented on 2014-10-18 at 01:24:

Actually there has been a work-around, the latest dev preview is fully rootable with 2.14

Val Ozuna commented on 2014-10-18 at 03:20:

Meh! I'll wait till chainfire fixes su.

Rafael Mendoza commented on 2014-10-18 at 03:24:

A few questions +Brad Hoschar

Link for boot.img

Only works with TWRP?

Can i flash that boot.img thru fastboot flash boot boot.img and then flash thru CWM?

Thx in advance

Angel Vega commented on 2014-10-18 at 06:25:

Chainfire I know you'll fix it

Spiridon C. Dalietos commented on 2014-10-18 at 07:37:

+Brad Hoschar

Confirming working, Android 5.0 Lollipop Rooted. The Rootable Boot Image: thanks to +sykopompos. Follow Brad's instructions above. Huge thanks +Chainfire for the Root and SU...

Андрій Бакай commented on 2014-10-18 at 08:59:

+Spiridon C. Dalietos Thank you very-very much!!!

Jemy Zhang commented on 2014-10-18 at 09:23:

I am trying the newest android L preview. But after I flash the under the recovery[recovery-clockwork-touch-], SuperSU remind me that "there is no SU binary installed, and SuperSU cannot install it.", what should I do?

Jemy Zhang commented on 2014-10-18 at 09:29:

+Spiridon C. Dalietos have you got a rootable boot image for nexus 7 2013 wifi only?

Spiridon C. Dalietos commented on 2014-10-18 at 10:00:

+Jemy Zhang

nope, but if want to experiment you can check this thread out rootable image That boot image might work...

Jemy Zhang commented on 2014-10-18 at 10:11:

+Spiridon C. Dalietos  I review the file date of  supersu package, it is not for the lastest preview, right? so I have to keep an eye on the thread.

Spiridon C. Dalietos commented on 2014-10-18 at 10:20:

+Jemy Zhang

Download rootable image as I have posted above, then download SU 2.14 and flash via custom recovery according to Brad's how to... Get a backup before cause you might brick your 7...

Jemy Zhang commented on 2014-10-18 at 11:14:

+Spiridon C. Dalietos ok, I got it, I will try it later this night. Thank u!

Jemy Zhang commented on 2014-10-18 at 11:48:

+Spiridon C. Dalietos oops~ N7 can not boot up with the rootable boot image you post above.

Spiridon C. Dalietos commented on 2014-10-18 at 11:55:

+Jemy Zhang

Restore via backup otherwise adb push or sideload original boot image via custom recovery and wait / google for a working rootable Lollipop boot image for Nexus 7

Jemy Zhang commented on 2014-10-18 at 12:04:

+Spiridon C. Dalietos Thanks for your instructions, I have already flash back the original boot image with fastboot.

Randy M commented on 2014-10-18 at 13:05:

Some know how to root nexus 5 android 5.0?????

Angel Vega commented on 2014-10-18 at 14:01:

+Randy M read above

Jemy Zhang commented on 2014-10-18 at 16:49:

+Brad Hoschar I tried the boot.img, the SuperSU seems to be no warning out, but it is not working at all. Titaniumbackup and shadowsocks can not work at all. What is the meaning of "not switch your entire system to SELinux permissive mode"? Is that the reason why titaniumbackup and shadowsocks can not be worked correctly?

John Kavanaugh commented on 2014-10-19 at 07:07:

Chainfire, I'm using on my Samsung Galaxy Note 3 Verizon variant v214, supersu, and safestrap 3.75 with stickmount and it works great no problems at all keep up the good work, I got my first nandroid backup restored to a ROM slot and I haven't got a ROM yet but the phone is stable starting to think about xposed modules and can't figure out what rom I want any suggestions would be accepted used towelroot to root my phone and there was no computer use at anytime any suggestions on Roms , contact me at my gmail which is, On my samsung galaxy note 3, Kit Kat 4.4.2,SM-N900V)(NC4) thanks to Chainfire everything has been working great keep up the good work.

John Kavanaugh commented on 2014-10-19 at 07:17:

Well that's the kind of backup I need right now and I'm going to do it should have done it already thanks for reminding me if this was directed towards the randelflag, regardless of the conversation you remind me of something I needed to do and that was titanium Thanks

dante 2p commented on 2014-10-19 at 11:49:

100000xxxx, but v2.1 4 it's ready !! 

In PS too ?!!

Bryce Gerhardt commented on 2014-10-20 at 03:53:

.[100000xxxx, but v2.1 4 }]it's ready !! 

Bryce Gerhardt commented on 2014-10-20 at 03:54:


Sergio De Leon commented on 2014-10-20 at 20:47:


John Kavanaugh commented on 2014-10-20 at 21:08:

2.14 supersu works great on my samsung galaxy note 3 from Verizon SM-N900V/NC4 the update came in the Google Market I took it it works great please respond Chainfire. Thanks the update works on mine. Any suggestions please direct them to

Mohamed Ayman commented on 2014-10-21 at 22:49:

I want to root my device But This App For Android 4.4.3 Only And My Android is 4.4.2 Help Me Please

Sana Ayoob commented on 2014-10-22 at 11:58:

ماعرف كيف يسونsupersu

Mohamed Ayman commented on 2014-10-22 at 19:27:


Keek 123 commented on 2014-10-23 at 08:09:


Abdelkader guellati commented on 2014-10-24 at 15:14:

That's ont grue I'm Turing to update supersu from morts ago ni resault

Mohamed Ayman commented on 2014-10-24 at 19:26:


Aik Knoxville commented on 2014-10-25 at 03:32:


Violet McKinley commented on 2014-11-06 at 06:32:

Hey Batman she is married back off or else and I mean in

Keek 123 commented on 2014-11-06 at 07:23:

Good morning

Анастасия Кувшинова commented on 2014-11-11 at 15:37:


Alicia Reyes commented on 2015-01-10 at 17:37:


Pablo Javier Moreno commented on 2015-02-17 at 22:27:

Thank you my friend!!! ¡ love your work, it is very usefull for me !!! My best for you!!! Thanks again!!!!!

Ryan Choudhury commented on 2015-08-21 at 21:04:


This post is over a month old, commenting has been disabled.