yashsingh1/xdaforums huggingface dataset:
[SuperSU] lion7718:
As far as I know, only SuperSU works with 4.3.
[SuperSU] RooFgr:
Tried to sideload and it failed

Verifying update package

E: Failed to verify whole-file signature

E: signature verification failed

Installaton aborted.
[SuperSU] polobunny:
Try to redownload, maybe a corrupt one.
[SuperSU] RooFgr:
nop.. same failure.
[SuperSU] dberthia:
So, I flashed this a few days ago to re-root 4.3 on my Nexus 10. If I see a SuperSU update available in the Play Store, should I install it?
[SuperSU] RooFgr:
in nexus 4 updating from the market leads to problem updating binary. I have uninstalled the update and it works, for now.
[SuperSU] fernandezhjr:
I have been updating thru the market and was able to update the binaries. At first the normal method failed. The other option thru recovery worked for me. The last SuperSU I flashed in recovery was 1.43. I have been updating thru the Play Store since.
[SuperSU] RooFgr:
Yeap. Im talking about stock recovery.
[SuperSU] zeppelinrox:
[MENTION=631273]Chainfire[/MENTION] Not sure if this matters or maybe you know about a certain quirk in 4.3 ROMS (actually, not sure if it's all but anyway...) where some basic commands are crippled.

This user http://xdaforums.com/showpost.php?p=44062505&postcount=21379 is using a 4.3 rooted factory image and it turns out the grep command is a text file with "toolbox" in it.

So when they run grep, the output is "Toolbox!"

Same thing with cp.

If you check the attachment in the link, all the 7 byte files in /system/bin are broken commands:

chcon

clear

cp

du

getenforce

getsebool

grep

load_policy

md5

restorecon

runcon

setenforce

setsebool

The output of any of those commands will be "Toolbox!"

Anyway, thought it would be of interest.
[SuperSU] fernandezhjr:
I see. I've never seen the point in keeping stock recovery if rooted. Stock recovery is pretty much useless for me when rooted. This is just a good example. Plus, when tinkering with my phone with root, I absolutely have the want to do nand backups.
[SuperSU] Pkt_Lnt:
I have seen posts in this thread about using fastboot to boot twrp or cwm to install a zip, leaving stock recovery in place. I have searched fastboot docs and tutorials with no luck. Is it possible?

Galaxy Nexus / JB 4.3 / Tapatalk 2
[SuperSU] jazzruby:
fastboot -h

usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable

fastboot boot recovery.img

-JR-
[SuperSU] p.chi:
Thanks for your response and sorry for the late reply. I wasn't able to wipe get into recovery at all. I was able to get into download mode and use Odin to reflash to get to the CWM recovery. Mounted to connect to the PC, then I backed up my data (even tho I know I had all my personal stuff it was a just in case moment). reinstalled my ROM.

I feel this could happen to many people, my confusion over my ROM being able to use either TWRP and CWM wasn't clear to me when given the popup option on SuperSU. I was supposed to choose normal. Hopefully my questioning of it will prevent others from making the mistake I made and my post will actually be helpful to them.

btw (for me) there was no clear warning, Here's the popup I received that I interpreted wrong: Maybe this could be worded differently ?
[SuperSU] osm0sis:
Ah okay, maybe it isn't signed correctly to allow for flashing in stock recovery then.

If you're really attached to stock recovery then I'd recommend getting into temp booting a custom recovery when you need it (as suggested above). For example:

fastboot boot recovery-clockwork-touch-6.0.3.5-mako.img

Then you can adb sideload or adb push and flash whatever zips you need, but when you reboot you still have stock recovery flashed. All you need is an unlocked bootloader.
[SuperSU] Pkt_Lnt:
Thanks, yes, read all that (and way more), the "boot <kernel>" part is what made me hesitant. Nowhere did I see the command you gave of "fastboot boot recovery.img".

Fastboot is not the place to experiment, I feel. Once I gave it more thought and remembered that recovery has its' own kernel to boot, then it it clear. Appreciate the thinker prod. :good:
[SuperSU] osm0sis:
boot is the safest part of fastboot since it doesn't touch your partition data, only boots whatever you supply. Pretty much the only way it's safe to experiment with fastboot. :)

As you later said you realized, recovery does include a kernel and will boot as such. Check efrant's guides if you want further verification; he includes this as a stock recovery method in his rooting posts and OTA threads. :good:
[SuperSU] RooFgr:
Ill try flashing temp recovery from nexus root toolkit.

Tnx.
[SuperSU] ultravox:
Nexus 10, sideload install via stock recovery

v 1.50 installed fine, but didn't seem to work

V 1.51 over 1.50. Same error as above.

CWM sideload worked just fine.
[SuperSU] steviewevie:
I am on the 4.3 stock ROM, with SuperSU 1.51.

I have been having problems uploading stuff from TitaniumBackup via Google Drive, but I've now figured out (from looking at logcat) that it's hitting a permissions problem on a file to be uploaded.

This seems weird because the permissions on the file are 644, but I can reproduce this in a shell, e.g. I get an error (permission denied) trying to do a simple cp of the file. It's not just one file, it seems to be lots of files created when I did a backup after upgrading to 4.3.

I know there have been problems with su on 4.3 because of security changes including SELinux and so forth. Is this part of a glitch related to this, does anyone know? e.g. now the chmod permissions are not showing the whole story?

Sent from my Nexus 4
[SuperSU] bbsnick:
same on my nexus 4.

flashed version v1.43 working BUT the update from market ( to v.1.51) leads to problem updating binary.

I have uninstalled the update and it works, for now
[SuperSU] bmdixon:
have you tried this?

In the 1.50 post on Google+ ChainFire mentioned that
[SuperSU] steviewevie:
Thank you, that worked perfectly!
[SuperSU] gruntyoldbag:
Is SuperSU supposed to survive a complete reset (via menu) + KIES installation?

I rooted my SGS4 last night using CF-Autoroot, and used Triangle away and then I reset the device and then I reinstalled STOCK ROM 2 times using KIES.

I still have SuperSU installed and I have root. :confused:

(I have not used Titanium Backup to restore anything)

Do I need to uninstall SuperSU (IF possible via Titanium Backup, because I can only un-install latest SuperSU _update_ via Play Store - not the complete app) and THEN use KIES afterwards - if I do not want to have a rooted device?

In other words - what is the proper method to get rid of SuperSU?

Not that I want to right now, but in the future I might...

Would a wipe in stock recovery fix it?
[SuperSU] osm0sis:
My sdcard Fix Permissions zip automates this too. :)

http://xdaforums.com/showthread.php?t=2239421
[SuperSU] layup23:
I have a question, maybe you guys can help me out.

I just updated SuperSu to the latest version and while installing I got a weird supersu request for something called 1034. After I open supersu I can see that the first app in the list has no name and when I click on it all the fields are empty. When I click on forget I get a force close from supersu.

Does anyone know what this is and why is it doing that? I'm afraid I might have granted superuser access to a virus or something.

Thanks!
[SuperSU] polobunny:
1034 could be pretty much any running process.

There's some reserved UIDs very well known such as 1013 being media/audio out, 1010 wifi etc etc

Screenshot?
[SuperSU] osm0sis:
In Terminal Emulator type: ps

It'll show you all the running processes.
[SuperSU] jazzruby:
Is it 1034 or 10034 if the latter then check your running process and look for u0_a34

-JR-
[SuperSU] layup23:
Here are some screenshots

As you can see there is no name of the app that has the su access as I told you guys before, if I hit forget I instantly get a FC.

I'm going to see if a reboot fixes it lol. If not I guess I have to see what the terminal emulator says.

I'm not sure exactly what was the exact name of the app that asked for SU access, either 1034 or 10034.
[SuperSU] Pkt_Lnt:
The "logs" tab will show it.
[SuperSU] andrew8806:
I have tried just about everything to get root and it will not work. Wiped everything and reinstalled stock rom on GNexus. Flashed SuperSU 1.51 and when it boots up and I go to open SuperSU it says binary is not installed.

su -v

1.51:SuperSU

shows the version as 1.51 installed.

any ideas?
[SuperSU] boyheadkick:
my screenshot of 1013
[SuperSU] :
v1.51 not work for me, on the rasbeanjelly r2.1, on Nexus 4. Already reinstalled million times, and I only get the message that the binary is not installed! :mad::(

I found the problem. Was the Kernel.
[SuperSU] andrew8806:
well, looks like mine got resolved by imoseyon. He added support for SuperSU to the kernel. Looks like this may be kernel related.
[SuperSU] :
The problem returned. From what I can gather, there's something wrong going on in some kernels build jss15j, which cause the root to stop working.
[SuperSU] uberto.costanzo:
hi after 1 day of usage supersu stop work, if i install app with supersu permission i have stop at boot of new app and wait for permission. any solution please? thanks for reply sorry for english (s3 4.2.2 leaked )
[SuperSU] RooFgr:
Is there an easy way to temp flash a custom recovery at nexus 4 so that i can flash the zip?
[SuperSU] yethz:
Fastboot boot recovery-name.img
[SuperSU] RooFgr:
I just saw wugfresh just released 1.6.6 of nrt with full 4.3 support. I hope that means it also flashes the latest supersu with root.

Is there a problem if i root again over my already rooted device?
[SuperSU] RooFgr:
Nexus Root Toolkit 1.6.6 solves the problem with supersu 1.51 not updating the binaries.
[SuperSU] CoolApps:
Too bad I forgot to do that, now I cannot restore the Android 4.3 recovery. :P
[SuperSU] ogre_x:
Doesn't work after upgrade to 4.3.

fastboot -c "lge.kcal=0|0|0|x" boot recovery-clockwork-6.0.3.5-mako.img

Works as a workaround. Only caveat is that the vol-up and vol-down buttons get reversed in clockworkmod.
[SuperSU] mrazster:
Just to clarify, is this http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip?retrieve_file=1 ...the full SuperSU or just an update and does it work in CWM with HTC One ?
[SuperSU] DJxSpeedy:
full yes

send via Samsung Galaxy Nexus with Tapatalk 4 Beta
[SuperSU] mrazster:
Worked like a charm on HTC One Stock GE 4.3.

Did the Pro/Donation thingy ....keep up the good work ! :D
[SuperSU] mnbrightblade:
Awesome! This fixed my Evernote issues!
[SuperSU] gaurav247star:
it is a zip that will root ur android device ..& after that u will find the super su app in app drawer.. which later u can upgrade to pro ...
[SuperSU] mrazster:
Yeah...thnx for taking the time. But as I said in my previous post I flashed and it works fine. I also bought the Pro version.
[SuperSU] androidfr33k:
I had everything working fine and ran the command suggested from the chainfire google+ blog. That the /data/media should be chown after installing busy box which I did but now I have lost connection with Android FIle Transfer for Mac.

As per blog I ran:

busybox chown -R 1023.1023 /data/media/*

I believe that broke connection to AFT.

Nexus 7 2013 FHD model running JB 4.3 and CM 10.2 8/3/13 nightly. I had it working after installing nightly so its not that. It stopped working after I ran Chown!!

Any ideas on how to fix this?
[SuperSU] osm0sis:
Flash my sdcard Fix Permissions zip. See if that fixes it.

It's in the Odds and Ends thread linked in my sig.
[SuperSU] androidfr33k:
Will get it running shortly. Where do I run the script? From Android terminal and which dir to run it in, or from TWRP install?

Thanks

EDITED:

Installed fine with TWRP recovery unfortunately AFT still won't launch. I will try maybe disabling USB debugging then re-enabling it an possible removing ADB and Apps root to just APPS root, then back again. Just different things in developers options.

EDITED:

None of those options I tried worked!! Something has broke AFT.

EDITED

I formated and started over and JB 4.3 rooted is not the problem its CM 10.2 is what had broke AFT.

EDITED:RESOLVED

Problem resolved. MTD got disabled with CM 10.2 kangs release.
[SuperSU] Morlok8k:
I attempted to flash 1.51 on my droid 2 global, using CWM recovery. no luck.

reverted back to 1.45.

playing the waiting game...
[SuperSU] gaurav247star:
LoL :victory: :)
[SuperSU] you5urf:
how could i protect supersu settings from being cleared by a wipe/factory reset? I have pro and pro and supersu are both stored in system. what next?
[SuperSU] schiznik:
Hey..

not knocking your work at all, but I would like to try Koush's Superuser beta (on my N4 running stock 4.3).

Whats the best way to remove SuperSu so that I can flash the Superuser beta?

Thanks :)
[SuperSU] ogre_x:
Do full unroot in SuperSU settings and flash The other zip.
[SuperSU] luckylui:
I want to say you have to click on the "Survival Mode" if not download in the playstore a apk called "OTARootkeeper" :)
[SuperSU] Casastr:
Temporary unroot

Tried to search the thread for this, but the search don't work today. :(

So, forced to ask the question here (again?).

Does anyone know how the temporary unroot works? In superuser there is a check box. In SuperSU I see nothing of the sort. How to enable it? How to use it? Did anyone try it? Want to temporary unroot in order to get OTA update -- tired of delaying it every 3 hours...

Thanks!

(SuperSU 1.51 Pro, SGS2, 4.1.2)
[SuperSU] efrant:
Why would you want to "unroot"? The OTA update will install regardless of whether you have root or not.
[SuperSU] Casastr:
It won't install... Always fails.
[SuperSU] efrant:
The reason it fails has nothing to do with whether you have root or not. It is something else.
[SuperSU] Casastr:
Did not know that. Thanks for the info!

Can it be because the original device ROM was branded, and I now have an unbranded Samsung ROM?

Or non-stock recovery? (CWM Recovery)
[SuperSU] -Maverick-:
Non stock recovery, install the original recovery that comes with your phone, the OTA update should then install and more than likely unroot your phone in the process. :good:
[SuperSU] Major-Hardon:
after udating SuperSu, i have been getting this weird app trying to install itself and when i press it, it opens suersu and starts downloading the app. it's some kind of korean game or something. it udated through googleplay, is anyone else getting this?
[SuperSU] Casastr:
That's the thing -- I want to keep the root. Allegedly, that's what the Temp unroot and Survival mode are supposed to be for in the SuperSU.

Anyway, the search is now working again, and here is the answer to one of my original questions:

http://xdaforums.com/showpost.php?p=42651667&postcount=2962
[SuperSU] CoolApps:
What is app called?, Did you install this app from an external source or the Play Store?
[SuperSU] Major-Hardon:
do not know what the app is called seeing it's in a different language, supersu was installed by default when i upgraded it with aocp.
[SuperSU] -Maverick-:
I understand now, when you posted "unroot" I thought you meant you wanted to completely remove root. You simply want to hide root.

I haven't tried SuperSU v1.51 option to hide itself from root checking apps, yet. I'll have to install it on 4.3 and check myself. I was planing on doing it anyway, but now I have an excuse.
[SuperSU] bsoplinger:
If you went through the trouble to find my post which answered your question you could have hit the thanks button ;)

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] isharra:
Works with the sole app I needed it for. Annoying that you loose root for all apps though.
[SuperSU] -Maverick-:
I just tried it on a stock 1st gen Nexus 7 running 4.3 and superuser wasn't even detected, root still on. I guess either the app was updated to not care about root anymore or something else is up. The app I tried, TWC TV, only bugged me about turning off usb debugging. Very happy with the results.
[SuperSU] Casastr:
I did, but it did not work -- I have scripts disabled in Firefox. Now fixed. ;)
[SuperSU] drbrainsol:
Can anyone reupload de zip somehow? Chainfire's link seems to be down. I tried to download it a few times, disabled ad blocking software and stuff...nothing :|
[SuperSU] Bill Gamble:
Here you go:

https://app.box.com/s/isy14bvfep62mg67l7t4
[SuperSU] drbrainsol:
Thank you very much :D
[SuperSU] -Maverick-:
Not sure how long the BOX account will hold, so I posted an attachment as a mirror.

edit: removed, hopefully no more mirrors needed.
[SuperSU] Hashbang173:
Can you post one that works on 4.3
[SuperSU] xolanir:
It does. Just flash in CWM or TWRP, and presto!

Sent from my Galaxy Nexus
[SuperSU] techieboy:
[2013.07.29] SuperSU v1.51

Confirmed that SuperSU 1.53 works with 4.3.
[SuperSU] Vaetheran2107:
Where to get 1.53?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[SuperSU] Pons:
Pretty sure that's a typo, and latest version is 1.51. At least, that's the latest in the OP, on Chainfire's site, and on the Play Store.
[SuperSU] Bait-Fish:
Sorry about this noob move, but search is failing me. Please do direct me to a FAQ if necessary. However...

I have an unlocked Verizon Developer Edition Samsung GS4. I need SU _without_ modifying recovery, boot, etc., which precludes me from the two known available root methods. This is necessary to get unmodified images off the device.

Can ODIN flash SuperSU? If no, can the SU binary be converted to do so?
[SuperSU] rta:
All my apps that need root work fine with SuperSU 1.51 except for one! GMD auto hide soft keys, for some reason this app will not acquire root access it says my phone is not rooted. It works on a fresh rom update but when you reboot once it loses root access and it wont ever get back until next rom update. Is there a solution for this?

My device - Nexus 4 Paranoid Android 3.95 (4.3)
[SuperSU] osm0sis:
Look up temp recovery, PhilZ made one for the S2 awhile back. It's a signed zip you flash in stock recovery. Gets you into CWM without modifying anything, only temp replaces them on the ramdisk. Then you'll have adb shell access and can root with ease.
[SuperSU] segv11:
For those wanting to hide root from snoopy apps, what if SuperSU patched the kernel to modify the syscall's for directory listing and file access so that when a zygote process that is NOT on the whitelist looks for /system/xbin/su it appears not to be present...

Sent from my stock 4.3 mako.
[SuperSU] CamoGeko:
1.51 flashed with CWM and works perfectly on 4.3.

Just say no if you get asked to reflash stock recovery.
[SuperSU] pietro1028:
temporary unroot

I am using PA 3.95 with franco kernel and supersu 1.51. However, I'm unable to use the temporary unroot on my phone.

Can anyone please help me ?
[SuperSU] osm0sis:
Actually it doesn't matter what you select because Chainfire chattr +i'd /system/etc/install-recovery.sh making it unable to be deleted by any method until it has -i applied. You can make that warning/question in CWM 6.0.3.5+ go away by creating an empty file at /system/etc/.installed_su_daemon :good:

Hopefully Chainfire adds that to his flashable zip/install in the future. I already have on my local copy.
[SuperSU] JuggaloDroid:
Tried this in 2 different root browsers and I keep getting "operation failed." When I get to /system/etc/ I hit new -->file & type .installed_su_daemon. I hit enter & get "operation failed." Any thoughts on what I may be doing wrong? Thanks in advance :good:
[SuperSU] jesssiii:
Did you change the system folder to read/write?

Osmosis, we should change the file permissions on that, right?

Galaxy Nexus Toro
[SuperSU] JuggaloDroid:
Yep. It's set to read, write, & execute. Thanks for the response :good:
[SuperSU] Pkt_Lnt:
Worked fine for me on Cataclysm ROM (JWR66V) with Root Explorer.

Galaxy Nexus / JB 4.3 / Tapatalk 2
[SuperSU] JuggaloDroid:
Finally worked. I had the permissions set to read, write & execute for owner but group & others did not have write permissions. Seems as though that's what the issue was. I rebooted into recovery and the notice/warning didn't show up so I hope it worked. Not sure if I have to flash something for it to give me that notice/warning before reboot but we'll see. Thanks for pointing me in the right direction jesssiii :victory:
[SuperSU] VIPOA:
Can I use this http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip with N-Cry toolkit for nexus 4?

this file is just the supersu zip right?
[SuperSU] yethz:
I dont know whats the process of that toolkit (not a fan of those kind of AIO tools, no offend)

But u can flash it via your recovery...
[SuperSU] VIPOA:
Thank you, I rooted my device now and I'm going to install PA Rom now :)
[SuperSU] ajaykumarmeher:
Hey, Please help me....

I have installed this App from play store. But when I open any application that needs root access, I do not get any prompt. But I get the root access for the app. Seems like I am automatically granted permission. This was working fine before. But today I reset the phone to factory mode and noticed this issue after I re-installed this app. I installed an app called links2Sd, is that the cause?
[SuperSU] samersh72:
are you sure you have root access?

anyway, in supersu app, go to setting>default access and change it to [prompt]

dont quote the whole op :good:
[SuperSU] My1xT:
he has root since it is auto granted. sounds like a binary of another su app is active right now... or that setting you mentioned. load the CWM package from OP and flash it via Recovery, maybe it helps...
[SuperSU] NZgeek:
Nothing should ever automatically grant you root without promoting, unless you've explicitly set SuperUser to do that. It's far more likely that you don't have at all.

Getting root access needs more than just installing an app from the Play Store. There are bits that need to be installed to the /system area, and this can only be done (a) from recovery, or (b) if you've already got a different SuperUser installed and working.

Use the package linked to in the first post to install SuperSU as this makes sure everything is installed properly. If that doesn't work, try going into the SuperSU settings and untick Respect CM root settings.
[SuperSU] Brute.Force:
I dont know why but supersu never works on my htc wildfire (buzz) whether it is included as system app in the rom or installed through playstore. After opening the app i get a outdated binary prompt and then the option to choose cwm or normal appear. I tried both options but on normal it says fail and in cwm it doesnt do anything. Also tried replacing su in system/xbin but no luck.

Sorry if the question is already answered (I dont have time to read 352 pages)
[SuperSU] fezzy102:
Has anybody tore apart the flashable and added it to there ROM ? If so what all did you add to your updater-script?