yashsingh1/xdaforums huggingface dataset:
[SuperSU] SpasilliumNexus:
I was just wondering how would one set up a ROM's updater-script to drop scripts into /su/su.d on a clean install? In TWRP, I do not see that directory until I reboot into Android.

Would it be possible to set up an "installer" script in /system/su.d which moves the script(s) to /su/su.d after booting, followed by deleting the /system/su.d directory? If this is possible, would anyone know how to set it up?

EDIT 1: Doing some Googl'ing, would this work?

updater-script

set_metadata_recursive("/system/su.d", "uid", 0, "gid", 0, "dmode", 0700, "fmode", 0700, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");

/system/su.d/postinstall.sh

#! /system/bin/sh
su
mount -o rw,remount /system
cp -r /system/postinstall/* /su/su.d
chmod -R 700 /su/su.d
rm -rf /system/postinstall/
rm -rf /system/su.d/
mount -o ro,remount /system

EDIT 2: This seems to work, only if I do the commands manually via terminal.

EDIT 3: Got it to work. Had to add "su" to the script and fix the permissions.
[SuperSU] CVAngelo:
How come the cat doesn't have a name?
[SuperSU] Upstreammiami:
I'm using temasek and it comes with superuser .

Why do I need to do to get supersu
[SuperSU] JochenP:
To have control su by app
[SuperSU] Naudiz:
It's really interesting. There seems to be some kind of bug with the display of logs inside the log-tab, which affects different users differently. Logging itself works, as can be seen by the dozens of text files inside the app's folder...

I guess I'll just wait and see for future updates :)
[SuperSU] dadykhoff:
Updated to the January security patch (MMB29P) on my 6P today - reflashed SU 2.66 and all is well. Great work, thanks again!
[SuperSU] kmandel:
On the other hand I'm having no success with the January security patch on the older Nexus 6 (Tmobil). I'm running stock MMB29K rooted with BETA-SuperSU-v2.66. The OTA for MMB29S fails after a few seconds when it boots into the tilted android mascot. The progress bar advances for a second or two before a red "err" comes up.

If I power down and back up, it comes back up normally in MMB29K. After a day or two I get another notification that it has downloaded the OTA again, and allowing the install does the same thing.

I know I can flash the updated firmware from the factory image site, which is how I did MMB29K back in December. However, I was hoping to be able to go with OTA's once a month.

Any suggestions?
[SuperSU] Djablos:
After installing Ressurection Remix and GApps and doing the basic configuration of the phone I went back to PhilZ Touch 6 Recovery and installed BETA-SuperSU-v2.66-20160103015024.zip over slideload. Now everything what I see is just "Ressurection Remix" booting screen promising the phone to boot but it doesn't boot. It just hangs in that boot screen. What could I possibly have done wrong and how to fix it?
[SuperSU] 10cheesecakes:
is it possible to add a "hide root" option that you can turn on and off at will? most of the apps that were built to do this just dont seem to work too well.
[SuperSU] agremlins:
Same question here :confused:

I think there is a correction of boot.img in the OTA or something like that doesn't work with the modifications made by SuperSU2.66.
[SuperSU] NPOA556:
Did you unroot before doing this? You must unroot from within the SuperSU app, which will replace the boot image it modified at installation with the stock boot image it stashed away for just this reason.

"If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image. A backup is made (/data/stock_boot_<sha>.img.gz) of the original boot image before patching it."

Above quote taken from here: http://xdaforums.com/showpost.php?p=64161125&postcount=3
[SuperSU] arteaga323:
I had unrooted from within SuperSU and also flashed UnSU, however no luck for me. I was still getting the Android logo with error What I ended up doing was going over to the official google page for factory images, downloaded the Jan update and flashed all but userdata. I now have the latest update with all my stuff here. You have to make sure you don't flash the recovery.img if you wanna keep yours (trwp or cmd) and in my case I didn't flash the boot.img because I wanted to keep mine, if you want a clean install then like I said, flash ALL BUT USERDATA. Hope this helps!
[SuperSU] #000000:
I'm in the same situation with my nexus 7 tilapia running omni.

Idk how to fix it:\ maybe i can root it with lower version pkg?

Im also on the last sec fixes
[SuperSU] reas0n:
[MENTION=631273]Chainfire[/MENTION] Do You use ChainsDD su binary or do You have Your own? I wanted to make a small change to it, but it doesn't work, but used koush's sources.
[SuperSU] arteaga323:
If you're in any other than stock rom, you wouldn't be able to apply the OTA because they have their own version of boot.img recoveries etc etc. You would have to flash stock.

I'm not sure I quite understood, could you please elaborate.
[SuperSU] agremlins:
no, I haven't this information.

I've tried but I also need to restore the stock recovery. This is again a lot of step compare to the flash of the full version.
[SuperSU] #000000:
My nexus 7 is 2012 version, so only custom roms can bring marshmallow to it. Omni rom comes without root, so I tried to flash 2.66 ver. But nothing more than just infinite boot. Without su it runs normally.
[SuperSU] arteaga323:
Type on Google "Google factory images" go on the result from Google and download the file that corresponds to your device, unzip the .tgz file and once that's done, unzip the .zip file inside. There's gonna be a recovery.img file, take that file and place it in the folder where your adb and fastboot files are (I assume you already have learned how to use adb and fastboot). Boot your phone to bootloader, open cmd, run fastboot, send command "fastboot erase recovery" without the quotes and then send "fastboot flash recovery recovery.img" wait for it to be done and then send "fastboot reboot bootloader" wait for it to be done and now you can just send "fastboot reboot" to reboot your phone normally. You should now have the stock recovery.

---------- Post added at 15:21 ---------- Previous post was at 15:13 ----------

Did you try 2.52? 2.66 is for systemless only, typically 6.0.1 unless that's what you have, if its a 6.0 variant then you need 2.52
[SuperSU] agremlins:
Thx, I know how to do it :)

My 1st idea was to be able to flash the OTA without having to download a factory image (for which I have an automated process).
[SuperSU] Tzfardaya:
Depending what other apps make changes, you may need to flash the system partition anyways.... I know that I need to...
[SuperSU] arteaga323:
Yeah that's what I was saying, if you reflashing system then it'll be clean/unrooted, OTAs should be fine but other than that, you would need to manually flash
[SuperSU] #000000:
I've 6.0.1 so I need systemless. And idk what to do. Cos On my s3 I've cm13 and no trouble.
[SuperSU] belek1979:
I'm unencrypted (Nexus 6)

Can I flash system.img (MMB29S), then flash SuperSU 2.66 thru TWRP and STAY unencrypted???

It works for MMB29K and SuperSU 2.62-3 but there are a lot of changes and issues with 2.66...
[SuperSU] nathanchance:
Yes, you can flash the system.img and boot.img with fastboot then go into recovery and flash SuperSU 2.66, which removes force encryption from the boot.img so you stay decrypted.
[SuperSU] asj0422:
-i'm on a nexus 6p, so everything's been pretty smoot boot.img wise and all that.

-there is a stable version for non mm roms?

-so besides just checking the page often, there's no way to get notified of updates to the app?
[SuperSU] belek1979:
So the changes in SuperSU since 2.62-3 with the installation (installer automatically chooses systemless or not, method) don't refere with removing encryption?

Thats gr8.

Is there a risk that Chainfire change that? ;)
[SuperSU] pkelly517:
I'm not sure if you want to remain encrypted or decrypted.

Flashing a no-enforce kernel does not immediately decrypt a partition. It only allows you to decrypt a partition. You can still run with encryption with a no-enforce kernel.

And there are always risks.
[SuperSU] holeindalip:
http://xdaforums.com/showthread.php?t=3219344

You can go here to see if any updates
[SuperSU] deathbytalkshow:
Hi. Whenever I run into this problem I have a solution that works for me and hopefully it works for you and anyone else who finds themselves in a similar situation.

I don't require a full stock TOT or KDZ, all I do is try to get back into TWRP using the volume down + power button, wipe everything (Dalvik, cache, system, data), go to Advanced > Terminal Command > start at "/" then type this in exactly:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc

Execute each line separately. Then I reboot to recovery (just for peace of mind), reflash the rom you want, your bootstack, your Gapps, and that's it. Don't re-flash SuperSU again :silly:

Hope it helps you next time (hopefully there's not a next time) :fingers-crossed:
[SuperSU] vel_tins:
Does the 5.1.1 (non systemless) rooting method still work on 6.0.1?

I've rooted Android-X86 5.1.1 successfully with a script and , which copies the needed files into a mounted "system.img"

Tried this script (and supersu 2.6.2) with MM 6.0.1, but after that, Android won't boot.

Is the 5.1.1 method no more valid?

If yes, what has changed?
[SuperSU] Wyneg:
Deleted
[SuperSU] greatheights:
I appreciate the quick response.

What is /su/xbin_bind? Any downside to deleting it if AP isn't a high priority for me?

Also, I take it that means I did, in fact, install systemless like I intended?
[SuperSU] Alxoom33:
If you are not comfortable with deleting the file and you still want to use AP, then rename it by adding .bak to the end of he file name and reeboot. The file can be easily reactivated if you need it.
[SuperSU] drewski_1:
The Material installer kang will inform you of new versions

Sent from my Moto X
[SuperSU] Alxoom33:
I take it Xposed still fails the AP Safety Net check ?
[SuperSU] bunklung:
You can also do:

echo BINDSYSTEMXBIN=false>>/data/.supersu

...prior to flashing SuperSU. It has the same effect as deleting /su/xbin_bind, but you don't have to boot into Android, delete/rename, then reboot.
[SuperSU] egingell:
The place to ask is the Xposed forum.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] JimSmith94:
It does for me and everyone else I've seen post about it.
[SuperSU] dron39:
What version you can recommend me to install on Sony 5.1.1 Xperia Z2?

Will SuperSU 2.66 be working or latest for 5.1.1 is SuperSU 2.52?
[SuperSU] shoey63:
For stable, use 2.46. For beta, use 2.66.
[SuperSU] payne_307:
Is there a way that the patching done by BETA-SuperSU removes the inbuilt root in CyanogenMod nightlies? I'm talking about CM13 specifically? I tried v64 and it didn't remove su from /system/xbin rather just created a symlink in /system/xbin ? I'm trying to use an app without having to use Xposed mods to run on the CM build which checks for root (su) in /system/ partition. Thanks
[SuperSU] BenPope:
You're probably better off asking in a thread related to the specific distribution of CM13 you're referring to, or perhaps the app.

I suspect that yes, there may be a way that installing SU interferes with an existing installation of SU, but I doubt that it would be a supported scenario. Support here probably ends at a non modified ROM.
[SuperSU] ksfno1:
Since my Nexus 7 (2013) was updated to 6.0.1, I have never been able to grant root access for the app Clean Master, whose developers suggested installing SuperSU Beta 2.49, which didn't help at all. Where does this issue stem from? From Android itself? From Clean Master? Or from SuperSU?
[SuperSU] drewski_1:
have you tried the latest 2.66?
[SuperSU] ksfno1:
Yeap! It was also no use :(
[SuperSU] thaidroid:
Well if everything but a particular app dont get superusers then you can be sure it's the app that has a problem......
[SuperSU] fink.nottle:
I'm on the latest image for nexus 5x, and I lose tmobile wifi calling as soon as i flash supersu (2.66 right now, but older ones too). Anyone else face this issue ?
[SuperSU] MaFiBoSS:
Its possible making the root on Note 4 (5.1.1) using the version 2.46 (no systemless)?

Thanks.
[SuperSU] MaFiBoSS:
But if I choose the "normal" update, I don't lose the Custom Recovery?

Thanks
[SuperSU] egingell:
?

"Normal" means while the phone is in normal operating mode.

"Recovery" means via recovery.

SuperSU doesn't flash any recovery, so you're not going to "lose" it.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] shoey63:
Samsung 5.11 requires 2.66. It will install systemless automatically, but so what? The installer will make it appear to be a "system" root to apps looking for /system/xbin/su.

Just do a full unroot beforehand if using a previously installed supersu. Or better still, reflash stock system and boot, and flash 2.66 in a custom recovery
[SuperSU] Dovidhalevi:
Does this work on an unrooted 4.4.4 LG L70?

Would need to use the apk since no flashing would be yet available.
[SuperSU] jcsww:
I have rooted with 2.66 and still have WiFi Calling on my Nexus 6P.
[SuperSU] RandomPooka:
Ok, maybe I'm just missing it, but are there links to the most recent versions somewhere near the OP, or do I need to dig through the last dozen pages of the thread to find them?
[SuperSU] PhilipTD:
You lookin' for this?
[SuperSU] RandomPooka:
Yes, thank you. I'd forgotten that they were posted in a separate thread. I have that thread bookmarked too.

I just haven't used systemless, because I'm running PureNexus on Shamu, which is already pre-rooted with the last version that's a "system" root. I don't actually need it to be systemless, but I was going to mess around with it for learning purposes
[SuperSU] PhilipTD:
No problem.

Yeah, I don't need systemless either. I wouldn't mind having Pay, but I could never live without Xposed.

I was thinking about giving pure a try...
[SuperSU] greatheights:
Can't delete system files

So, even with systemless root, I should be able to delete files in /system myself right?

I recently did a clean wipe of my phone (Nexus 6, stock) to install the latest google security patch, and used SuperSU v 2.66 to root. My previous install was one of the versions where you still had to flash the modified boot image, but I'm not sure which one. Anyway, it was working flawlessly and I had Xposed installed and running fine.

I'm trying to delete a few foreign language keyboards to make room for Xposed, but neither ES File Explorer (w/ root explorer turned on) or Solid Explorer will delete them. I even tried using the Mount /system RO/RW app to mount my system RW, and I still can't delete these files. I had no trouble doing this on my previous install.

Can anyone explain why I'm having this trouble? Since I'm going to modify /system anyway, I don't have a problem not using the systemless root, but like I said, I had it working before.

I used the option to install it to su/bin, whereas I'm not sure that option was available yet on my last install, so busybox had probably already modified /system. Could this have anything to do with it?
[SuperSU] KonoeKyon:
Read the WIP thread, it has information on how to get it to mount R/W, see if that allows it to work. I've got r/w access on my nexus 6 using stock ROM. I would also suggest having busybox installed in /su/xbin/ instead of /su/bin/.
[SuperSU] greatheights:
Sorry, WIP thread?
[SuperSU] force70:
Search button works great...

http://xdaforums.com/showthread.php?p=63168310

sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
[SuperSU] greatheights:
Point taken. Still, because I'm curious, what does WIP stand for?
[SuperSU] shaggyskunk:
Work In Progress ?

Why i Phone - lol

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] galakanokis:
Work In Progress.
[SuperSU] milojoseph:
Offtopic guys but [MENTION=2719389]z31s1g[/MENTION] has created a theme to override twrps supersu method [MENTION=631273]Chainfire[/MENTION] those not want us to use which may cause problem for systemless root. http://xdaforums.com/showpost.php?p=64853510&postcount=2641
[SuperSU] Manuel15:
Is there a 480 x 800 version?
[SuperSU] Ch3vr0n:
How about you ask that in the twrp thread, this is about superSU.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Arsinn:
Hi guys.can I root my m8 (marshmallow sense 7) with this superSU v2.52 + twrp recovery?
[SuperSU] Chainfire:
Pfee, been playing with adding support for bzip2/lz4/lzo/lzma/lzma2 compressed ramdisks, but shees, it's going to add whole megabytes to the ZIP it seems. Not happy with that.
[SuperSU] fhem:
Flash osmOsis' busybox after installing 2.66 and you should be good to go. Read this.
[SuperSU] giorgis91:
What if I would to switch from systemless root to normal?

I'm on cataclysm + EXkernel
[SuperSU] Smoosh1:
Follow the tutorial of [MENTION=6842057]nathanchance[/MENTION]
[SuperSU] deprofeet:
Brilliant script, thanks a lot!!!

I did notice that your script left the following two (SuperSU?) files in place:

/system/lib/libsupol.so

/system/bin/app_process_init

Is this an oversight or is there a reason for them to remain untouched?
[SuperSU] MaFiBoSS:
OK, but what the difference? Only the "state of phone" (Via Normal or Via Recovery) for install the binaries?

Thanks.

---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------

With v2.66 (systemless) I have problem with some apps and drain battery. So I prefer the root with system mounted. I tested the v2.52 + Custom Kernel + Stock Rom + Custom Recovery.

Thanks.
[SuperSU] asj0422:
Why does our root have to be systemless again? I remember it was something to do with boot verity and that not allowing the system to boot with a modified system partition, but i've installed xposed and mucked around in some system folders on my phone and I don't seem to be having any problems with booting/rooting/etc.
[SuperSU] Rakeesh_j:
Will there ever be a way to seamlessly accept OTA with systemless if we have the pro version? Just curious, not demanding it.
[SuperSU] Calnyx:
So root vanished again, strangely. More accurately, apps couldn't obtain root when they had perfectly just the day before. Reboot once again fixed it. Does anyone know why it seems to randomly vanish every 2-4 days?

2.66 systemless, G920T. DOJC firmware.
[SuperSU] bill_kevin:
I lose root every reeboot, I can't stay rooted,I'm in 2.66

my phone is g800h 5.1.1, I need to reinstallig and work for a while then I lose root.
[SuperSU] toster88:
Hi, which beta version should I get for moto g xt1039 aokp 6.01 ? I would really like to avoid bootloop :)
[SuperSU] Ch3vr0n:
Simple, running M = latest beta, always

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] TewFast:
Nexus 5 updated to 6.0.1 MMB29S today and installed SuperSU 2.66. Absolutely smooth. No issues.
[SuperSU] milojoseph:
It happens rarely but just reflash the zip

Sent from my SM-G900T powered by AllianceROM

and boosted by speedy kernel

Lollipop ?
[SuperSU] HudShow007:
Hey guys, I'm having some troubles here on Super SU. I flashed supersu v2.66. But its not working here on my rom. Here's the log that I took of supersu
[SuperSU] Manuel15:
I'm not an expert but I read the log and found this

- Decompressing ramdisk sukernel v2.66 (ndk:armeabi-v7a) - Copyright (C) 2014-2015 - Chainfire Loading from [/sutmp/ramdisk.packed] ... Decompressing [625958] --> ungzip: inflate: -3 failed --- Failure, aborting

It seem related to a ramdisk issue [MENTION=631273]Chainfire[/MENTION] writed a few pages back
[SuperSU] PocehNeheb:
is it possible to do a systemless install on an old device running lollipop? adding the two parameters to /data/.supersu didn't work.
[SuperSU] Pig Vomit:
It was late and I was rushed when I posted. I deleted xbin_bind, not xbin.
[SuperSU] shoey63:
It seems TWRP will no longer offer to root MM on future builds https://gerrit.omnirom.org/#/c/16438/

It's going to save a lot of confusion:good:
[SuperSU] bunklung:
I would reflash BOTH stock "system" and "boot" from fastboot.

Before you flash 2.66 do this in adb Shell via TWRP:

echo BINDSYSTEMXBIN=false>>/data/.supersu

Run https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground after Android boots up and see if it passes.

Try AP again.
[SuperSU] gufoman88:
I'm on nexus 5 with systemless root. I have to update kernel. When i flash the kernel i have to flash also the supersu zip with the terminal command "echo ......"? The kernel is blu_spark

Inviato dal mio Nexus 5 utilizzando Tapatalk
[SuperSU] nathanchance:
Technically eng.stk should be the one to answer this. However, blu_spark is in an AnyKernel format so you do NOT want to flash SuperSU afterwards. Otherwise, SuperSU will replace the kernel with an unpatched one and patch it. Just flash the kernel and reboot.
[SuperSU] FunkeeC:
Strangely enough, I cannot seem to use AP since the new update. I have the previous version backed up via Titanium and THAT version works fine. Just went to lunch and attempted to use AP at one store and got the can't verify error. Reverted to back up and hit up walgreens and was able to use AP without issue. Ill update when i have a moment and use this app to see if it passes not sure what would be the issue if others are using newest update to AP.
[SuperSU] bdorr1105:
Ok, so in other words, remover supersu from installing with the ROM, the kitchen packs it as part of system. Flash ROM first, then flash SuperSU 2.66? Thanks
[SuperSU] Manuel15:
Sorry my auto-corrector changed my words. I mean if you install SuperSU in normal MODE it will modify the system partition. If you install SuperSU in systemless MODE it will modify the boot partition

---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------

So if you flash SU it will be custom
[SuperSU] bdorr1105:
No problem, so I guess I do not understand, how do you choose what mode it installs? I do not see an option for that?
[SuperSU] Manuel15:
I know there is a command to run before flashing SU (if I'm not wrong) to switch to system mode. Otherwise it will install the systemless mode by itself.
[SuperSU] nathanchance:
After you do a full unroot of your current SuperSU in its settings (or you can flash UnSU from osm0sis if you are on SuperSU 2.52 or earlier in TWRP before the commands), go into TWRP. Select Advanced, then Terminal Command. Select the current folder (should be / by default) in the right hand corner. In the text box, type echo SYSTEMLESS=true>>/data/.supersu and hit enter. Then echo BINDSYSTEMXBIN=false>>/data/.supersu and hit enter. The first line forces a systemless install. The second removes /su/xbin_bind, which has to be done for AP to work. Then flash SuperSU 2.66.
[SuperSU] Chainfire:
I have created a new thread, for all your questions/complaining/whining/whatever about SafetyNet and Android Pay. All further conversation regarding these things should go there. I will start moving existing posts to that thread soon.

Android Pay and SafetyNet will now be treated as off-topic for this thread.

http://xdaforums.com/apps/supersu/supersu-safetynet-android-pay-t3298115
[SuperSU] PhilipTD:
I don't care what they say about you, Chainfire, you're awesome.
[SuperSU] shoey63:
Has anyone else found that installing systemless through twrp causes the device to heat up to the point where thermal throttling kicks in, and the process takes ages? (80 degrees on z3)
[SuperSU] skulldreamz:
Edited a few posts below... ?
[SuperSU] alex00006:
Hi

my phone G920I and android 5.1.1

I'm use su 2.66 root sucerfull

after

unistall apk 2.66 and reebot phone to recover mod and install su 2.56 now root again sucerfull

tnx for chinfire ???

next

install application deep sleep fix (tnx for dr ketan)

Now

My phone root with deep sleep good
[SuperSU] gannjunior:
So what i have to do? Thanks for your help
[SuperSU] Giumba:
Everything is fine but Titanium Backup

Just patched my N5 with SuperSu 2.20. Everything is fine but Titanium Backup (v.6.1.5.6) that still sees the phone as unrooted.

Any clue ?

I fear it's Titanium fault. Newest update (6.1.5.6) is 6 month old...