yashsingh1/xdaforums huggingface dataset:
[SuperSU] wilflare:
thanks! that makes much more sense now.

(1) When you say "reflash SuperSU to get the patched kernel", you mean after I take and install OTA on my Nexus 6P, I'll most likely lose root so I'll need to re-flash SuperSU? (what patched kernel? sorry)

(2) I'm using Stock ROM so I guess it's still systemless - I'm under the impression that systemless is "better" (with the ability to take OTA and all that)

(3) What's the point of making TWRP keep /system as read-only (as stated in the OP post #2)? (won't that cause TWRP to be replaced by stock recovery)?

(4) any idea what's the case for stock Samsung Galaxy Note3 (would it be systemless? and if I do a factory reset on my Note3 after rooting, I'll lose the root as well right? or is it different from Samsung devices)?
[SuperSU] nathanchance:
1. SuperSU 2.60+ makes modifications to the ramdisk that allows you to have root without modifying system. When you take an OTA, those modifications get written over so you need to reflash SuperSU to make those modifications (or patch the kernel) again.

2. Rooting stock on a Nexus 6P requires systemless root at the moment and yes, it is better for OTA.

3. I am not sure.

4. No idea. If it is systemless, yes factory reset causes you to lose root.
[SuperSU] osm0sis:
Stericson's Busybox Installer hasn't uninstalled things correctly for ages (circa Lollipop), and the new systemless "support" and fixes he added still don't allow a custom directory to be set at all on my N7 2013...

At the very least the following will manually remove all busybox links and the binary from a target directory.

(from my smart busybox installer):

target=/su/bin;
cd $target;
for i in $(ls -al `find -type l` | awk '{ print $(NF-2) ":" $NF }'); do
case $(echo $i | cut -d: -f2) in
*busybox) rm -f $(echo $i | cut -d: -f1);;
esac;
done;
rm -f busybox;

You may need to "mount -o rw,remount /su;" first. The target in the first line can also be altered to clean up /system/xbin if needed.

Then hope his installer accepts a custom path on your device. I'll be updating my busybox installer to look for /su/xbin and perform a complete install (and smart install to /su/bin if not, for legacy support) probably tonight.
[SuperSU] ericcostes:
Is there a way to update my superSU v2.41 to the SuperSU v2.52

Please Help

I am android 6.0 and started to gain my root access

I made an error when selecting the superSU version because I choose a SU.Zip containing an old version ..

I flashed this superSU 2.41 on my 6.0 android, using fastboot flash command.

BUT I stopped here : my phone is not rooted . I realize my error !

and now surper SU claim his bin to finish the root process .

is there a way to update SuperSU , so that I can continue to root

thanks for help or advice

regards

Eric :cowboy:
[SuperSU] tetakpatak:
fastboot flash supersu? ?

Android devices are really tough, many other would simply explode after such command ?

tetakpatalked from Nexus 7 flo
[SuperSU] sirxdroid:
Anything to be aware of if going from 2.64 to 2.65 on a Nexus 6P? Just flash it in TWRP or do I need to flash factory system and/or boot first?
[SuperSU] luigidk:
deleted..
[SuperSU] chazall1:
Well I got updated finily. I had to Install Cata Stable 12.08 then 12.21, Ex kernel and the new SuperSU 2.65 and all is working as expected.

Thanke for the Assistance. The Seamless root install method is great but you must follow the proper sequence.

Thanks
[SuperSU] luigidk:
Want to Clarify... I am using 2.61 - so to move to 2.65 do I need to:

- remove 2.61 first? If so - how?

- do I perform the command "echo SYSTEMLESS=true>>/data/.supersu" BEFORE flashing 2.65 or AFTER ? (assuming the command still needs to be run from TWRP>Advanced>Terminal... for 2.65 (as it does for 2.64)

EDIT: I went ahead and entered the command "echo SYSTEMLESS... "

Then I flashed 2.65 over 2.61

And installed busybox into su/xbin

So far - so good...
[SuperSU] azsl1326:
Any idea why I would get an error that the zip, 2.65, is corrupt every time I try and flash it? I have d/I it several times each time with the same result.
[SuperSU] greeneyez15o:
Tried flashing 2.65 over my secondary roms, it killed'em :(
[SuperSU] lpasq:
Reporting no issues from 2.64 to 2.65 zip flash:
[SuperSU] MechaStark:
Hi guys! Just a noob question.

My N6 is Systemless rooted, and I would like to use Xposed and Viper4android, but those 2 modifies /system, but I don't want that because I would like to install OTAs on my phone without any problem.

My question is: If I make a nandroid backup of /system on TWRP before I install Xposed, v4a or any other mod/APK that modifies /system, and then I restore it before installing an OTA, could my phone install the OTA?

I'm sorry for that question, and thanks in advance.
[SuperSU] nEUTRon666:
Regarding 2.64+ and detecting if the Phone can be rooted via /system, does this mean as for example a Nexus device will ALWAYS be rooted via /system and NOT systemless? Do i need to force systemless root every time ?
[SuperSU] demlv:
Remembering and manually typing terminal commands in recovery is not a strong suit for me. But perhaps I am not fully understanding the new procedure. Is there another, ideally simpler and/or more permanent way to force systemless installs going forward?
[SuperSU] nathanchance:
As far as I am aware, once that line is typed in, SuperSU will remember that for further installs. Anyone is free to correct me though.
[SuperSU] osm0sis:
Nobody ever said it had to be done in recovery, and it definitely only needs to be done once. Copy/paste it to Terminal Emulator while booted, or if that's still too difficult, all it does is echo that string out to a file in /data/ so you can just as easily create that file yourself in a file explorer and edit it then type it in, but honestly that sounds more complicated than terminal to me. ;)
[SuperSU] Taomyn:
Where can we find your installer, perhaps I should give it a shot? Stericson's seems to behave differently between my N6 and N9, and hasn't really been properly fixed for custom location as you state (still says it will install to /su/bin instead of /su/xbin that I enter, and N9 installed to /su/bin regardless so I had to move the files manually).
[SuperSU] osm0sis:
Over in my Odds and Ends thread.

I just posted the updated version with /su/xbin support. :)
[SuperSU] demlv:
I honestly did not know what the echo command did. Thanks for the info.
[SuperSU] Neverendingxsin:
Will your installer also remove all of stericsons stuff in system/xbin? This RoM can with it preinstalled in there and his app won't properly remove it.
[SuperSU] burduli:
Is it safe to flash? Because last time when I flashed 2.64, I got into bootloop.
[SuperSU] kukubau:
[MENTION=631273]Chainfire[/MENTION]

I've rooted my HTC M8 Marshmallow using m8-mmgpe-su-boot-systemless.zip and BETA-SuperSU-v2.65-20151226141550.zip and everything ran smooth. :)

I've installed SuperSU app from the store as it wasn't installed by default. Why does SuperSU nag about needing been updated. SuperSU also displays 2.46 version. Do I really need SuperSU app?

Ty
[SuperSU] antila:
For some reason my Samsung Note 4 loosing root. After I'm trying to flash this Beta trough TWRP, I'm getting the error message not correct zip file.
[SuperSU] vjtigas:
How can I root using v2.65 by system mode on a clean flashed CM13? It always roots using the systemless method.
[SuperSU] aosp:
https://play.google.com/store/apps/details?id=ru.meefik.busybox

https://github.com/meefik/busybox/releases
[SuperSU] Chainfire:
If I need to scroll several times the height of my screen to get through a screenshot, you may be doing something wrong.
[SuperSU] osm0sis:
Nope, but change the target in the script chunk I posted a few pages back to /system/xbin and that'll do it (also linked in the latest post in my Odds and Ends thread).

Nice simplistic app. My zip installer has x64 builds though. Anyway, with /su/xbin added to SuperSU, all busybox issues should be resolved, so let's all stop talking about it here. Questions pertaining to my installer can continue in my Odds and Ends thread. :good:
[SuperSU] ~SonkuB~:
My Nexus 5X can't use all camera app when I flash boot (both bullhead-mdb08i-boot.img, bullhead-mdb08i-boot-systemless.img)

If I flash stock boot, camera is ok.

Nexus 5X 6.0.1
[SuperSU] The-Droidster:
N5 2013. Systemless SuperSU 2.62-3 currently. How do I update to 2.65…? I have tried reading through but its really confusing ATM..sorry for my noobness.:o
[SuperSU] Ja_som:
Flash 2.65 over it...
[SuperSU] WNSTNSNRS:
Been out for a long time time, and it seems like there's already systemless and system mode. How to know if im rooted with systemless?

What's the difference between the two? Sorry for my noobness.
[SuperSU] Ch3vr0n:
That's because you didn't follow instructions. You need STOCK boot and system. Flashing a modified boot isn't STOCK.

Flash STOCK images and nothing else, then flash latest beta. It's been at least 3 or 4 beta's now that the zip installer does the work itself. Modified boot images are obsolete.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] nathanchance:
Go into SuperSU > Settings > Install SuperSU into /system. That will tell you if you have system or systemless root.
[SuperSU] Alxoom33:
Tried to dl and flash 2.65 several times, each time TWRP says file is corrupt.
[SuperSU] WNSTNSNRS:
I'm currently on v2.65 and it says that SuperSU is already in /system. So I bet this is System Mode right?

How can I switch to systemless? And what's good on systemless?

Thanks man.
[SuperSU] jah2110:
Hi master, I want to now if this method with stock kernel works in my 928g Edge plus? Thanks a lot.

http://xdaforums.com/galaxy-s6/general/root-universal-root-method-s6-s6-edge-t3267486/page2
[SuperSU] IronTechmonkey:
This seems to occur more with material downloaded over mobile data connections. Try downloading file on different device and or different network connection and copy it over to your installation location.
[SuperSU] Alxoom33:
Lol! It worked, 5th time's a charm![emoji108]

2.65 flashed over 2.64 on Nexus 6, 6.01 Cataclysm Rom. Stays Systemless without needing further ADB command[emoji106] [emoji106] [emoji106]
[SuperSU] zfrnz:
Just a quick noob question about systemless... I am am rooted with systemless root 2.60 on Nexus 6 stock android 6.0.1 and I want to install a ROM. Do I do anything differently when I flash a ROM with systemless versus normal root? Thanks in advance.
[SuperSU] Andehrson:
Doesn't work on CM13. Need to binary att but i can't do it.
[SuperSU] Ch3vr0n:
Wrong place to ask. This is about SuperSU, not the galaxy s6. Ask your device forum how to root.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] boxcar8028:
Just wanted to report that su-v2.65 flashed over v2.64 without out any issues. Booted up just fine and smooth. N6p stock 6.0.1 Great job CF. Thanks man.
[SuperSU] jah2110:
This is the correct place I'm talking about supersU...
[SuperSU] Riccardomille964:
V. 2.65

v2.65 works great on my LG G4, but I noticed that video outgoing in Skype communication doesn't run.
[SuperSU] H4X0R46:
Using a Nexus 6 and this works, but there is one annoying bug that's significant. My device is running stock rooted and with elementalx kernel, multirom installed as well! When I boot the device normally, I have to leave it alone with the screen on for a minute or two and wait for supersu to grant access to my usual root apps, I have to wait for the toast to come up and then I can shut off the screen on my device. If I shut off the screen before it gets a chance to grant permissions, the device freezes solid with a black screen making me have to force power it off with the power button. Could this be a supersu bug? The elementalx kernel not playing nice with my setup? Anyways, thought I'd report this bug! Cheers!
[SuperSU] pdcclf:
I tried to flash 2.62+ to Sultan CM13, but never succeed. According to the log, the flash seemed to me OK, but abort when update bootimg . any help?

I am using sultan cm13 as secondary with multirom 32l + customized twrp 2.8.7.
[SuperSU] antila:
I do not know what to do. For some reason all files with SuperSu, when I'm flashing it says "file is corrupted". Tried downloaded few times with same result. TWRP says "file is corrupted".

Any idea?
[SuperSU] WettbackMartyr:
[MENTION=341864]antila[/MENTION] someone experienced same problem as you one page back.....well I guess now two pages back since mine is the first post on a new page.
[SuperSU] swallowingled:
I had a corrupt file download too but then tried a second time using Chrome on my 6P and that download worked.
[SuperSU] BenPope:
I've tried to install 2.65 on my M9 running Marshmallow 3..35.617.12, but the app says "No SU binary installed".

Here's some logcat that might be relevant:

12-28 10:13:30.084 607 607 E installd: eof
12-28 10:13:30.084 607 607 E installd: failed to read size
12-28 10:13:46.310 1197 1197 D BOOT_LOCK: DexOptimizer: Dexopt: path = /data/app/eu.chainfire.supersu.pro-1/base.apk dexoptNeeded = 1
12-28 10:13:46.310 1197 1197 D BOOT_LOCK: DexOptimizer: mIsFromOnVolumeChange = false
12-28 10:13:46.312 607 607 E cutils : Failed to mkdir(/data/app/eu.chainfire.supersu.pro-1/oat): Permission denied
12-28 10:13:46.312 1197 1197 I PackageManager.DexOptimizer: Running dexopt (dex2oat) on: /data/app/eu.chainfire.supersu.pro-1/base.apk pkg=eu.chainfire.supersu isa=arm64 vmSafeMode=false debuggable=false oatDir = /data/app/eu.chainfire.supersu.pro-1/oat
12-28 10:13:46.297 607 607 W installd: type=1400 audit(0.0:231): avc: denied { write } for name="eu.chainfire.supersu.pro-1" dev="mmcblk0p67" ino=1196106 scontext=u:r:installd:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=0
12-28 10:13:46.313 607 607 E installd: installd cannot open '/data/app/eu.chainfire.supersu.pro-1/oat/arm64/base.odex' for output during dexopt
12-28 10:13:46.315 1197 1197 I BOOT_LOCK: WindowManager: mSystemBooted = false PMs.isNeedShowBootMessage = false
12-28 10:13:46.315 1197 1197 I SystemServer: LockSettingsService
12-28 10:13:46.325 1197 1197 I SystemServiceManager: Starting com.android.server.PersistentDataBlockService
[SuperSU] Nydalxy:
I can't find any information since supersu 2.65 was released. I have a nexus 6p with Android 6.0.1 and today I unlocked my bootloader, flashed twrp 2.8.7.2 and then supersu 2.65, now my camera isn't working. Any idea on what will fix it? It force closes as soon as I click it.
[SuperSU] Pkt_Lnt:
Reported earlier but no one has posted a logcat so it can be analyzed and maybe fixed.
[SuperSU] Nydalxy:
Let me know if this is enough.
[SuperSU] Taomyn:
Noob question as Linux is not my strong suit, but if I have a mount bind for /etc/hosts in /su/etc and then I create /su/etc/hosts as a symlink to /data/data/hosts, when I look in /etc should I not see the same symlink to hosts? I see a file instead.

Just trying to figure out a way to get AdAway to work on my Nexus 6 without complaining that it can't write the new hosts file or repeatedly trying to create a symlink.
[SuperSU] Alxoom33:
Try dl with a different browser. Firefox worked for me.
[SuperSU] namlas:
After doing a recovery install on CM13 on klte, I'm getting stuck in a bootloop -- logcat output is pasted below. Has anyone come across this in CM13 on klte (latest nightly)?

---------- Post added at 01:30 AM ---------- Previous post was at 01:15 AM ----------

And, I get the following error when trying to update the binary through the app:
[SuperSU] osm0sis:
It's been posted many times here and in (the correct thread,) the AdAway thread. Please search and read. You need both the bind mounted hosts file and AdAway set to the default location. If you have any further questions you should direct them to the AdAway thread.
[SuperSU] Taomyn:
Firstly, you've obviously never tried searching a thread with Tapatalk, secondly if you had also read both threads yourself would have also seen I have already done this for both my devices (I posted numerous times on the matter). Reading/searching a thread goes both ways.

I asked a very specific question about a specific use case, that asks something related to the way SuperSU works, which may or may not help me with AdAway.

If you can only respond with an irrelevant answer, kindly keep it to yourself.
[SuperSU] osm0sis:
Tapatalk is no excuse, use a web browser if you care about finding the answer. You basically just refused to try. And, despite telling you to read more I also directly provided you with an answer/solution to your issue. Once again, read, and if you want further help I'll help you in the AdAway thread. ;)
[SuperSU] Taomyn:
No you didn't, so you still haven't read either. I asked if I have a mount bind for /etc/hosts in /su/etc and then I create /su/etc/hosts as a symlink to /data/data/hosts, when I look in /etc should I not see the same symlink to hosts? I see a file instead.

Where exactly was your answer to that? I believe that part of my post was the only part with a question so wasn't difficult to spot.
[SuperSU] osm0sis:
Stop. Read the AdAway thread, where I have answered you in the depth you require.
[SuperSU] Taomyn:
Sorry, still doesn't answer me - and I replied there too.

Maybe someone else that does know the actual answer to my question will respond soon. I'm happy to wait.
[SuperSU] WNSTNSNRS:
I can confirm i'm on system mode. What's the benefit of using systemless? And how can I switch to it? Thanks
[SuperSU] :
I can't seem to be able to write to my /vendor directory anymore. I can't delete files from /vendor/overlay and I can't wirte to it either. Any idea why? Using 2.65

Edit: fixed, was related to busybox, not supersu
[SuperSU] antila:
For download I was not using browsers from computer. I downloaded directly to Note 4 and used ES Downloader from ES file manager. Actually I've tried many times many utills. Everything downloading without errors just SuperSu with this message. I'm trying to understand why? The problem appeared few days ago, when suddenly my device lost root. Supersu says "no binary". Then when I rebooted device I got loop and booted normally only after wiping Cash and Delvic Cash and also, restored the data from Nandroid. But then, again, "no binary" and everything the same after the reboot, loop, wipe cash and dalvik cash, restore data and so on. I couldn't install root, because all SuperSu says file corrupted. Tried versions 2.52, 2.46. and 2.64, 2.65.

Do not understand what is going on. I do not think that the problem SuperSu. But I do not understand where is the problem?

That is why I've asked for help.
[SuperSU] BlazeGhost:
Is it working on lenovo a6000 plus
[SuperSU] ktmom:
If you can, try downloading with a computer. I've had this problem (and others also) using mobile data.
[SuperSU] tamaraxxx:
Try downloading the file with stock browser. That did the trick for me. And dont let es downloader get those files.
[SuperSU] belek1979:
If 2.64/2.65 does not modify boot, then I'll loose no encryption - am I right?

As far as 2.62.3 modifies boot, my Nexus 6 stays unencrypted.

So when I flash system.img on Nexus 6 and then root with 2.65 and restart the phone, then it encrypt?
[SuperSU] TMFGO45:
Is there any way I can check to see if I'm actually using systemless root? I updated my Nexus 6P to the newest OTA and flashed SU 2.62 in TWRP. Can I check to see if it's truly systemless? Also, if this means we can take OTAs, does Xposed actually prevent OTAs or does that not modify /system either due to how it works?
[SuperSU] sansnil:
Check if your device has the su folder at the top level of your file hierarchy or if it's located on your system partition. If the former, you're systemless.

If you run Xposed, OTA's won't apply successfully because the system integrity check will fail. But it's super easy to reflash a stock system image and then apply the OTA. Although easier at that point to just apply the new system image directly imho. You won't lose your custom files/settings either way.
[SuperSU] CCJ22:
I want to know as well. What's the benefit of one over the other.
[SuperSU] vuurvlinder:
Working on sm-p600

2.65 works on samsung 10.1 2014 sm-p600.
[SuperSU] TMFGO45:
Thanks. SU is outside the system folder. But due to Xposed, you are probably right. Just flashing a new system image is surely faster and easier.
[SuperSU] dahawthorne:
I hope this isn't a particularly stupid question, but I see mention of installing Busybox in system/xbin. This would count as a system modification and therefore prevent OTAs...?

I installed it to try to prevent the incessant nagging of AutomateIt Pro to reboot, and it made no difference anyway, so I could easily uninstall it again - I've never really understood the benefit of Busybox, since I've been running on Marshmallow for months happily without it. If I uninstall it, has the system image now been marked irreparably as changed?
[SuperSU] TR2N:
Hi guys, I need help in understanding. I am using systemless root 2.65 Beta without Busybox. But I resized the system partition with TWRP, did a mod of the build.prop with the editor app and use layers. If I understood correctly, as soon as the system drive is mounted to make this kind of mods, OTA will fail? Even if I would undo this mods?
[SuperSU] KonoeKyon:
Correct, it will still fail without flashing system again.
[SuperSU] TR2N:
Thank you for explaining! So I will dirty flash the system.img over it to update with the factory images the next time.

Would be nice to do the idea with the overlay fs to allow this mods.
[SuperSU] ddfault:
I through I would post for others. I have the Moto X Pure 2015 XT1575. I've flashed stock CLARK_RETUS_5.1.1_LPH23.116-18 to CLARK_RETUS_6.0_MPH24.49-18 The Marshmallow Update. I tried the BETA-SuperSU-v2.65-20151226141550.zip and does not boot. I tried BETA-SuperSU-v2.64-20151220185127.zip and it boots, but basically all the settings, UI, and applications crash. BETA-SuperSU-v2.62-3-20151211162651.zip works! It boots and settings doesn't crash. I'm still in the process of getting it all setup. If things still aren't working I'll post again.
[SuperSU] Chahk:
Does the installation log for SuperSU say it uses system or systemless method? On my wife's Moto X Play (XT1563) running 6.0, the 2.64 and 2.65 versions keep using the system method which is causing the errors you describe. The 2.62-3 version installs via systemless method, and everything works great.
[SuperSU] ddfault:
I suspect we have the same experience. With 2.62-3 it goes through a whole process of backing up boot, dumping a portion, patching it, and putting it all back together. 2.64 and 2.65 do not do this.
[SuperSU] mlevin:
Which versions to use for Nexus 6

Hi,

Two quick questions before doing the systemless root as described in http://xdaforums.com/showpost.php?p=63197935&postcount=2 on my Nexus 6:

The post has a link to SuperSU 2.56, but I see that the latest is actually 2.65. Which one should I use, the one from the post or the latest?

Also attached to that post is a link to shamu-mra58r-boot-systemless.zip, but I am now on 6.0.1 MMB29K. Is there a newer ZIP or is it safe to use the one from MRA58K?

Thanks!
[SuperSU] nathanchance:
Look in the third post, systemless root is automated now instead of flashing boot image then SuperSU. Just follow the instructions in that post to get it set up.
[SuperSU] pnr2020:
need help please i used cf auto root all installed fine installed adaway. But i cant delete any files was working fine on other version but on 2.65 i cant delete anything with any root app my phone is gs6 920f
[SuperSU] mlevin:
Awesome, thanks. Next time I'll read further before asking :angel:
[SuperSU] fdc77:
i have also same problem on moto x style xt1572, su 2.65 keep using the system method and is causing issue, only su2.62-3 works properly