SuperSU updated to v1.60
Posted on 2013-09-05, 27 comments, 320 +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.

KNOX KNOX! Who's there? Super! Super who? SuperSU!

There's three seconds of your life you won't get back. This version of SuperSU works on the newer SGS4 firmwares that appear to have KNOX built-in, or if not that, at least SELinux set to Enforcing. (for more details on that, see this post: - also for instructions on how to remove that annoying popup that your device has been compromised). You will need to re-root on these firmwares, just updating through Play will not work.

There's been some other fixes as well, most notably a problem with the OTA survival in Android 4.3 has been corrected.

New binaries are included, but installation is not forced if you are running the previous binary, as you only absolutely need this binary upgrade if you are running SELinux in Enforcing mode, in which case you have to re-root anyway, and you would automagically already have the correct binaries. So don't worry if it doesn't ask you to update binaries.

All the CF-Auto-Root's have been updated as well at , and you can get the latest flashable ZIP here:

Let me know if there are any new issues. But please do keep in mind that problems with the new KNOX firmware may not be my problem. SuperSU is only the window to the internals of the firmware and device - if those internals change (not the window), your root-using apps may need to be updated to work with the changed internals.

As a reminder to those KNOX-firmware users: do not use Mobile ODIN or Triangle Away until they've been updated or your phone will explode.


  • Added SELinux+Enforcing compatibility (for new SGS4 ROMs)

  • Fixed (newest) CWM versions asking you question that break root if answered wrongly

  • Fixed issue with the TWRP/CWM binary installer 

  • Fixed 4.3 OTA survival looping

Krishean Draconis commented on 2013-09-05 at 13:31:

Already updated from the play store :-)

Joel Fernandes commented on 2013-09-05 at 13:32:


Gary Weldon commented on 2013-09-05 at 13:33:

Hmm, don't give up the day job.

Carlos Rodríguez commented on 2013-09-05 at 13:39:

Hey +Chainfire I don't know if you're aware of this, but with the new bootloader for 4.3 on the Nexus 4, it's not possible to boot to a .img (recovery or kernel) without applying some arguments to the fastboot command, specifically -c "lge.kcal=0|0|0x". By looking at the CF-Auto-Root for the Nexus 4. The .bat (or .sh) doesn't have those arguments. Have you tested on this device and works fine?? I always put that argument to boot to CWM and flash SuperSU (I want to root the old-school way). In my case I have to input:

fastboot  -c "lge.kcal=0|0|0x" boot nameofcwm.img

Without that, I only get a blank screen.

What are your thoughts?


Aitor González commented on 2013-09-05 at 13:42:

Thank you

Gustavo Sanabria commented on 2013-09-05 at 13:44:

Automagically updated from Play Store. Thanks for your great apps +Chainfire

Chainfire commented on 2013-09-05 at 13:58:

+Carlos Rodríguez I've not had that report from anybody else, also I don't own an N4. Please report this to the N4 CF-Auto-Root thread on XDA

Carlos Rodríguez commented on 2013-09-05 at 14:04:

I will. Another question: issuing fastboot oem unlock on an already unlocked device doesn't wipe data, right? +Chainfire

Enric UR commented on 2013-09-05 at 14:05:

Thanks so much!

Cembo Hurricane commented on 2013-09-05 at 14:12:

Thank youuuuu ;)

Larry Berg commented on 2013-09-05 at 14:12:

Thank you!

Giuliano Peretti commented on 2013-09-05 at 14:14:


mohammed shamsideen commented on 2013-09-05 at 15:41:


Roberto Villarreal commented on 2013-09-05 at 15:46:


mohammed shamsideen commented on 2013-09-05 at 15:53:


Mohd Shukri commented on 2013-09-05 at 16:50:

+1 update from playstore....tq

Michael Y commented on 2013-09-05 at 17:17:

Samsung KNOX?

Rafik Fares commented on 2013-09-05 at 18:10:

Are you planing one day to update chainfire 3D?

Paolo Di Sciorio commented on 2013-09-05 at 18:14:

Great Chainfire

Brandon Williamson commented on 2013-09-05 at 23:40:

thank you!

Piotr Budny commented on 2013-09-06 at 19:05:

+Carlos Rodríguez Agh, now I know, why I had to flash TWRP instead just booting it with stock. Thanks

Carlos Rodríguez commented on 2013-09-06 at 19:25:

+Piotr Budny you're welcome. I'd still like to now what happens if I do the oem unlock command on an already unlocked phone.

Jedidiah Pakula commented on 2013-09-06 at 21:10:


Job Fees commented on 2013-09-07 at 10:28:

It's ebb Oxygen

TheGrooveChannel 2017 commented on 2013-09-09 at 13:39:

Need the reset flash counter and the new samsung firmware bootloader to be reset to 0 and back to official asap thanks +Chainfire

TheGrooveChannel 2017 commented on 2013-09-10 at 11:16:

Gave you tried the htc one toolkit

Gilles LE GUILLOU commented on 2014-03-11 at 17:31:

Hi, thx for your work! no way without it!

Just a question, i used autoroot, disabled knox, reinstalled supersu from apk, cleared dalvik cache but i still encounter "supersu has stopped" and no more access to the sudo authorizations management.

For a complete misfit i don't have update option and reinstall just goes in an infinite loop.

I would like to be sure that only authorized apps will gain su rights, can I?

Are this clues of any help? How can i log more information?

A little more help would be greatly appreciated.

Thanks in advance,


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