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.
v1.69 has just been released. The link below is for the latest flashable ZIP. Google Play will start updating in a few hours.
This update includes fixes for two exploits that have been found and may allow an attacker to gain root access without prompting. Disclosure of these will take place next Monday, so I advise everyone to update before then.
Just a heads up, there will likely be another update next week.
XBIN mode (some new roots need this)
Slightly adjusted binary installer
Backup script installation now available for all backuptool-capable ROMs
Fixed su-ing to a non-root user not working on some 4.3+ firmwares
Fixed BOOTCLASSPATH vulnerability (CVE-2013-6774)
- Fixed notification sanitization vulnerability (CVE-2013-6775)
Fixed possible closed special files vulnerability
Updated language files
Chain fire when u can I have a question for ya
after I upgrade via Play, do I need to do anything? I suppose supersu lives in the system partition and can Play write to it?
Hope you don't mind my dumb question.
+Alex Fung you will need to open the app in order for the su binary to be updated
Will the Nexus 4 auto-root image in your site be updated when the official ota arrives, or will the currently posted one still work in KitKat?
Thanks. Is there a new CF-Auto-Root (for Galaxy S4) to go with it? And is encryption of the internal store still broken with Android 4.3?
Phew ...I feel much safer now ;)
Thanks man, you should work for google to bring android to a new level of accuracy, smooth, unbugged, trusted operating system
Nicely done, thanks
If I flash this zip is it going to fix the failure to update problem I have had for almost a year. It works but I cant update it and so cant access to manually configure. Also I paid for the premium version wont that be lost if I flash the zip file?
+Clive Richards I flashed the zip and I also have the Pro version. No you never lose the Pro version. It's just an unlock for a couple premium features I think. If you open Super Su and go to settings, it will still show Pro version after you flash the update zip
+Thomas B from what I know its working perfectly on my 4.4 Rom without any trouble :)
Thanks, works on my Nexus 7 on 4.4
Does anyone know about this kingo an it's method of rooting verizon s4 4.3 ota ..I'm very skeptical on using it ..any ideas on it
OTA update to v4.4 failed for me on my Nexus 7 (2012):
ApplyParsedPerms: chown of /system/xbin/daemonsu to 0 failed: Operation not permitted
ApplyParsedPerms: chown of /system/bin/.ext/.su failed: Operation not permitted
When I got those two files deleted, the OTA went through without any issues. A problem with v1.69, which I was running?
Nevermind, was properly because "Survival mode" was on :)
Not playing nice on Nexus7 (2012). su binary seems to hang. Apps get no SuperUser dialog, and tying su from adb shell just hangs.
Flashed ZIP from recovery onto KitKat.
+Arthur Stingo I used it on sprint note 3 no broblem knox 0x0
+Mark Gillespie: I think I have the same problem on my Nexus10. No solution, though.
+mario segura okay but what did u do about replacing Chinese su
+Mark Gillespie On my N7 I unrooted in SuperSU, flashed the zip of the OTA in cwm recovery, then immediately flashed the SuperSU 1.6.9 zip.
But it's not taking. I've tried redownloading and flashing the zip several times. No luck. Is this the issue you're having?
Yes, and I did the same I unrooted before applying as having supersu installed on my 2013 n7 caused the ota to fail.
I read at xda to flash stock 4.3 recovery, boot, system then sideload the OTA and then install SuperSU 1.69. This should work. I will try it later...
+Arthur Stingo I left it at 1.95 because 1.69 was giving me problems it updated and lost root used kingo app to root all good at 1.65 Knox 0x0
I used this just now on my S4, however I am also running a custom ROM (CM 10.2 nightly builds) so I can not say yes or no for certain about stock recovery on an S4.
Unfortunately I'm getting regular crashes with a security exception "Unable to start receiver eu.chainfire.supersu.NativeAccessReceiver" due to ": Neither user 10051 nor current process has android.permission.WAKE_LOCK".
I should say that's on a stock recovery N4 running 4.4.
... aaaand I resolved this by uninstalling all updates then updating it again through the Play Store. Hurrah!
+Colin Whiteside: You don't happen to be user hyperspacey over at xda?
Hah! Indeed I am.
I installed via TWRP recovery on my AOSP Galaxy Nexus, but the app doesn't appear in the app list and my device has no root functionality. Any suggestions? I've reflashed several times to no avail.
Nice . . .i like it . . . .?
Where can i find CWM for s4??