Shared publicly  - 
 
Superuser Installation Zip for Android 4.3  - Beta 2
(and older versions too)

Installation instructions:

1. Download zip: http://download.clockworkmod.com/test/superuser-4.3-beta2.zip

2. Install zip via recovery.

3. CLICK NO TO THE FOLLOWING: if you are on an older version of ClockworkMod recovery, and you are warned about "ROM may flash stock recovery on boot. Fix?", do not fix it. Click no. [1]

This is a beta. Please test on all versions of Android and leave issues in comments.

[1] There are updates to +ClockworkMod recovery being rolled out right now to fix this issue. It will take a while, as I need to rebuild 90+ devices.
206
25
Lauren Weinstein's profile photoBrian Hermon's profile photoKeyan Mobli's profile photoDavid Dzado's profile photo
147 comments
 
Wait if I did the opposite on step 3 in the past, What would happen? And also, would it be possible to add the feature to be able to change a rule on an application? For example, if you accidentally denied root rights to an app, I want to be able to change that to allow. +Koushik Dutta thanks!
 
+Ani Ravi To change the allow/disallow, just delete the policy/rule and you'll get reprompted.
 
Thanks! +Koushik Dutta oh I didn't notice that the rule could be deleted. Must have been blind at the moment or something xD
 
+Koushik Dutta I gave it a go on my Google Edition GS4 (running the JWR66V 4.3 leak). I'm using +Dees Troy's TWRP, which I think is the only recovery available for the GPe GS4 thus far. Works great with GooManager thus far. Thank you!
Amon RA
+
4
5
4
 
Nexus 4 running stock 4.3 : No issues so far. 
 
I tried on Galaxy Nexus with stock ROM and custom kernel.

Received a pop up saying, "The Superuser binary (su) must be updated". However it failed to update.
 
Yes I was. I was using ChainFire's previously.
 
Grabbing that zip but I prefer supersu. 

Thanks for all you do for the community. 
 
Got the same deal as +Rashidi Zin . Can't seem to get root now. Had it before flashing the zip. On a custom Rom. N4 
 
+Koushik Dutta After updating to CWM 6.0.3.5 then flashing the superuser beta I get

"The Superuser binary (su) must be updated..."
 
This is what I get with "su -v" 10 com.koushikdutta.superuser
 
Tried with Beta 2. Still didn't work.
 
+Koushik Dutta Will CWM recovery for Nexus 7 work on the new Nexus 7 as well? No offense to Team Win, but I prefer CWM.
 
oh that way thanks. Sorry it is late here. EST
 
Beta 2 does not help here too... Still getting the message "There was an error installing Superuser. Please send a log of the error to the developer"
 
Thanks +Koushik Dutta ... I figured as much, but doesn't hurt to ask just the same. I may just wind up wiping it again when your release it. I'm hearing of permission issues with root apps trying to access data.

I figure its best to start with a fresh recovery, superuser, and data.
Amon RA
 
After granting root explorer su privileges battery life dropped to 1 hour :-\ 
Translate
 
+Amon RA What's eating the battery? Can you pastebin your process list?
 
+Rashidi Zin looks like your su daemon did not start. you're on stock galaxy nexus you said? i have one of those, I'll try doing an install.
 
Yes I am. Stock galaxy nexus but with custom kernel.
 
+Koushik Dutta is this doing the hacky method? I'm assuming something is touching recovery :)

(Unless I missed your how this works post"
 
Beta 1 didn't work for me on my Nexus 7 with stock 4.3 and CWM 6.0.3.4, however flashing Beta 2 worked perfectly.
 
+Koushik Dutta I'm running the N4 stock rooted 4.3 coming from chain fires SU. I uninstalled his version installed yours via recovery and said No. I get the error about unable to update. Doing su -v I get the same error as +Rashidi Zin was getting.
 
+Keyan Mobli If you're running stock, this uses the hacky method. CM uses a non-hacky daemon that is invoked from init.local.rc.
 
+Koushik Dutta Cool thanks. I think I'm gonna run rootless for now. Can't think of anything I do that needs it nowadays.
 
+Rashidi Zin That kernel doesn't seem to extract properly, so I can't investigate the scripts it uses. Hrm. Will look into it more tomorrow. My Galaxy nexus is at the office.
 
+Koushik Dutta I am running stock kernel however. I have tried to reflash the 4.3 factory image and now trying to root with Beta 2, let's hope it works. Will post an update
 
Ok...Beta 2 works after fresh install of 4.3. Hope that helps.
 
+Amon RA Looks like a bunch of log workers are stuck. That may be why. Thanks for that log, I'll work on fixing it.
 
+Wolf Irotisha Link to franco kernel? I gotta go to sleep in a bit, so I'll investigate these issues in the morning.
 
+Koushik Dutta I hope I set it up properly so you can download and view the files. If not let me know and I'll upload to DB
 
Ugh. I'm still waiting on a 3.4 kernel for my Droid RAZR Maxx HD. Maybe you could help out +Hash Code there +Koushik Dutta! J/k
 
+Koushik Dutta  TitaniumBackup fails due to mount problems /storage/emulated/0/TitaniumBackup is not writable. SuperSU had that problem too at first. Should Titanium update their default path or should /storage/emulated/0 work?

Setting backup path to /storage/sdcard0/TitaniumBackup seems to work for now.
 
Working with all my apps but rom manager still won't fix permissions, just shows 2 lines and says it's done, any idea when this might work?

The option seems to be missing from CWM too in recent builds?
 
I make the kernel rashidi zin is referring. install-recovery.sh is enabled in the version he's using. supersu from chainfire works. I guess it is more probable that the daemon somehow gets killed by PaX or GRsec. Chainsdd root app was also having this issue.
 
+Fredrik Duprez :

"TitaniumBackup fails due to mount problems /storage/emulated/0/TitaniumBackup is not writable. SuperSU had that problem too at first. Should Titanium update their default path or should /storage/emulated/0 work?

Setting backup path to /storage/sdcard0/TitaniumBackup seems to fork for now."

You mention that +Chainfire 's SuperSU had that problem at first. Do you mean therefore that v1.50 fixed it? (and presumably you would have been on a version of Titanium Backup prior to v6.1.0 at that point?)

If v1.50 did indeed fix it, did you therefore switch from SuperSU to +Koushik Dutta 's Superuser because you prefer the usability of the latter?

Sorry for all the questions, +Fredrik Duprez - I'm just looking to give my non-techy friend with an Xperia Z a pain-free method to move from the stock Sony ROM to vanilla Android 4.3!
 
I would wait for the moment to be honest, it's not totally "pain free" yet, there's a few good apps that need updating. I'd give it another week or so.
 
+Nicholas Polydor Yes SuperSU 1.50 fixed that mount problem. I prefer Superuser due to it's more elegant installer and open source code. So I'd really like to get a working Superuser. If your friend is impatient, SuperSU is the way to go right now, but I'm confident that when Superuser irons out the rough edges it will work just as well.
 
How can i switch from supersu to this one?
 
works great; VZW GNex, Shiny ROM, CWM Recovery 6.0.3.3
 
+Koushik Dutta this little hack rush you have going on here is inspiring. You are truly a "for the people" dev and it shows. EFF donation made in your honor. 
 
Installed recovery 6.0.3.5 cleared cache, dalvik. It will not install binaries on my mako.
 
So previous to 6.0.3.5 we were supposed to select "no" when prompted to keep root. On 6.0.3.5 are we now supposed to click "yes" and it will keep CWM Recovery and root?
Amon RA
 
+Brian Hermon
It depends if you are using stock 4.3 or not.

No = run the stock recovery install script on boot.
Yes = don't run the stock recovery install script on boot.

As of 4.3 you'll need to select no, because the recovery install script is now used to start the su daemon.
 
Finally! I will be able to change back from superSU to my favorite su app again. Thx! 
 
I'm on Shiny ROM 4.3, as close to stock as you can get. That's weird because I read on rootzwiki it was the exact opposite of what you said. Up to this point I've been selecting "no" and maintaining root.

Are you saying 6.0.3.5 changes that and now requires selecting "yes"? 
 
Clockworkmod Recovery couldnt' mount my storage (Nexus 10), but I could sideload the superuser app - and it works fine for the N10.
Amon RA
 
+Brian Hermon Made a stupid mistake, and updated my comment above. Yes and No are not changed, but as of 4.3 the stock recovery installer is hijacked to start the su daemon. Selecting yes or no will not change the fact that you keep root or not, it is used to run the stock recovery installer or not... 
 
I am getting "superuser binaries are out of date" after i flash. When i try to update it I get the option of cancel or recovery install.  I choose recovery install and i get the message "There was an error installing Superuser. Please send a log of the error to the developer"  and then i still do not have root.  I check the logs and there are no logs.  I just want to use Helium :)
This is on CM 10.2
 
2012 Nexus 7 w/ 4.3. Had problems with this until recovery re-flashed 4.3 and beta2 zips. Oh BTW not sure if this is a beta2 issue, but Titanium Backup (latest) doesn't work, can't restore and backup.... 
 
Hoping +Koushik Dutta will comeback and update us on this. I experienced the same as many others. Im using a CWM style recovery by phil3579 on xda. 
 
Just installed it on my Stock Nexus 7 (2012) with 4.3 and it works well. Tried using Helium with it. Will see how battery life is.
 
Koush thanks bro! Finally got root back on 4.3 all I had to do was flash this zip! Thank you very much!
Edit: for those interested I'm running stock custom ROM on nexus 4! and this worked for me! Thanks again Koush! Your the man!
 
If you are coming from supersu and are already rooted go into supersu settings and select full unroot, then flash this. +Ricardo Varela 
 
Want to add I just did a full unroot within supersu and installed cwm 6.0.3.5 and superuser is working properly. I thought I did a full unroot before but it was 2am and I might have selected the wrong option. 
 
+Chris Flinn +Callum Stewart that resolved my issue!  I do not know why from a fresh CM 10.2 install that Superuser did not work but now that I did what you said above it works perfect!  
 
Worked like a dream. Now rooted on 4.3
 
When I tried earlier I switched from SuperSU and chose the option Switch Superuser app in SuperSU before flashing the zip file. When choosing Full unroot instead it all worked just fine. Thanks +Callum Stewart. +Koushik Dutta 
 
N4 with a freshly flashed JWR66V from the android developer page (clean wipe of all local data).  I flashed CWM touch 6.0.3.5 and used it to install the original post's zip.

The first zip installed and let me run `su` from w/in an adb shell.  `su -v` produced this output: 9 com.koushikdutta.superuser

There were two issues I noticed, however:
1.  su from an adb shell resulted in root being granted; but no permit/deny dialogue launched
2.  no apps seemed to work: Helium didn't recognize su was installed and ROM Manager saw it existed but attempts to use it didn't generate a permit/deny dialogue and didn't produce the desired action ).  

-beta2 corrected problem 2 but not problem 1; although, given the fact that the "Superuser access" setting has options that explicitly deny calling su from adb, this may actually be the intended behaviour.
 
Nexus 7 same issue as other wants to update binarys after work then fail. Tried new recovery, tried manually deleting old su reminents still no go. Thanks +Koushik Dutta 
 
+Koushik Dutta I got it working. I did the FULL unroot option in SuperSU and installed your zip and everything works. Even getting 10 when doing su -v
 
Anyone having issues using mount to remount the system via ADB? It works using terminal emulator but not through ADB, I just get "operation not permitted." Superuser does show an Allow for Shell in the log after I su.

edit: After using the app "adb insecure" to switch adbd to insecure I was able to get it to work. I don't remember if I had to do this on 4.2.2.
 
Quick suggestion: SuperSU installs its `/system/etc/install-recovery.sh` with `chattr +i`; it didn't work for me so I was trying your superuser.  Unfortunately, the install failed because when the superuser install script came to copy install-recovery.sh it silently failed and left the SuperSU version.

My suggestion is that you need to add a `chattr -i` to your install script.
 
+Andy Parkins I was just about to point that out. Also should remove /system/xbin/daemonsu
 
Hi! Thanks for your great work. Everything is working great for me, except for the OpenVPN Installer App. It fails on mounting /system rw. Also trying to remount (mount -o remount rw /system) in adb shell gives operation not permitted. +Koushik Dutta any ideas?
 
+Koushik Dutta - sorry, I think my post was unclear, that output was from the beta1 version of your zip.  The output after applying the -beta2 was correct.

Also, I'm experiencing the zombie log workers that +Amon RA described earlier.  I disabled logging and rebooted the phone, but the workers still kick off and still go into uninterruptable sleep.  If you need any details to tackle that issue, let me know. 
 
+Koushik Dutta Has the included app in CM been updated to reflect this? I'm unable to to gain root on CM-10.2 however it works fine after installing the beta-2zip+app. However this causes the app to take over and the superuser in Settings doesn't log anything.

edit: found the fix for cm-10.2 already stated in Cody's 10.2 unofficial nightly thread.
 
Coming from SuperSu (Nexus 4, Android 4.3), I had the same problem the others had regarding the message stating to update the su binary. The solution to do a "Full Unroot" inside of SuperSu and then flashing your beta 2 of Superuser worked perfectly.

+Koushik Dutta You should probably edit your post/make a new one to make a note of this process to avoid confusion as the thread gets longer. :P
 
Really appreciate all your work, sir!
 
Just receive the ota on my Nexus7.
I flash it with CWM recovery and flash superuser beta 2 before reboot.
Su/root works fine (test with Titanium Backup and local shell).
Thanks for your work.

 
SuperSU sets immutable bit on it's files when choosing 'OTA survival'
It's updater-script provisions for this:
Disabling OTA survival
chattr -i /system/xbin/su
chattr -i /system/bin/.ext/.su
chattr -i /system/xbin/daemonsu
chattr -i /system/etc/install-recovery.sh

If coming from SuperSU, you must handle accordingly...
 
Updated to 6.0.3.5 on my N4, then installed beta2 Superuser in Recovery (no warnings), then applied 4.3 update normally. => Boy, "Patching remaining system files..." is taking forEVER, how long should it take? 
 
Ha! then the 30 mins I gave it should be enough. :D Rebooted into recovery (6.0.3.5), re-installed Superuser4.3-beta2 (ok), restarted, apps optimized as usual, and ... Superuser-beta2 seems to be working fine with Helium, Total Commander, ES File Explorer, and Cerberus (rebooted from console, a root-only function). Hurray for +Koushik Dutta !  

I have 4.0.3 on an HTC Amaze at home, after updating my N7, I can try it on that....
 
2012 N7, 4.3 upgrade good, superuser install from this thread good, so far root ops good except (as noted by others) cannot remount /system rw, even via adb.
 
Update: Was able to mount /system rw via an internal app rather than adb. Interesting. All's well that ends well. Thanks!
 
+Lauren Weinstein Yeah, zygote is in its own mount namespace. mount changes in adb won't be visible to zygote spawned/forked processes.
 
Not working on i9300 cm10.2. I have the latest cwm touch recovery. Once the phone boot, superuser request su binary update, but it failed (only show recovery based update option).
 
I added it in ROM 4.3, and I'm always receiving a message to update su. But the su cannot be installed.
 
Same success with N7'12 (grouper). Installed beta2 on HTC Amaze (ruby), 4.0.3, seems to work fine. 
 
+Koushik Dutta I believe I found a nasty bug with Superuser today. It must have been triggered by an update to either Spotify, Dashlane or Digipost because it happened on both my Nexus 4 and 7 after updating those apps. What I got was en "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable" error. It became impossible to backup or restore apps with Titanium Backup and installing apks. Flashing SuperSU 1.51 fixed the problem on my Nexus 7. I don't know about the N4 because I had alrfeady factory reset it (luckily I had a complete backup from just a couple of days ago).
 
By the way, the problem wasn't entirely fixed on the N7 by just flashing SuperSU in CWM. I still get the error message and I can't restore the three apps I mentioned earlier with Titanium Backup. I can install apk's and uninstall and restore other apps though. My best guess is that there is something with the newest version of Spotify, Dashlane or Digipost that screwed up Superuser since this happened on both my devices right after installing those updates. 
 
+Koushik Dutta I can get root access in apps (e.g. Titanium), but shell still doesn't work for me.

I don't see the restore recovery script, but I didn't get the prompt to keep/delete it. 

Possibly the su daemon isn't running? How do I confirm/enable it?

Recovery: CWM-6.0.3.5
FW: OCCAM-JWR66V

copolii@PERSPOLIS:~$ adb shell
shell@mako:/$ su -v
10 com.koushikdutta.superuser
shell@mako:/$ su
shell@mako:/# ls /data/data
opendir failed, Permission denied
1|shell@mako:/# 

Thanks.
Reg P
+
1
2
1
 
Just flashed the GPE 4.3 to my One and am getting the same issue as +Rashidi Zin . Flashed the superuser beta2 zip on TWRP, supersu asked to update binaries then fails every time. :(
 
Beta is successfully use full
 
This zip installation could work for tablet with android 4.2.2 ?
 
+Koushik Dutta I am sure that it is WAY late, but I just flashed this version on my Nexus 7 and it worked MUCH better than the version that i had previously.  The previous version would not do that auto-update. 

Thanks!
Add a comment...