yashsingh1/xdaforums huggingface dataset:
[SuperSU] Frank Westlake:
OK. All this only supports what Chainfire already said -- that it looks like something is deleting it -- and there is only a slim chance after a tremendous attempt that you could find out how.

I think your best option is to start again with clean firmware and install root applications one at a time at least a day apart.

Frank
[SuperSU] JaCh0o:
I think it's not app fault but systems. There is another root Kingroot (not kingoroot) with special binaries which makes root app and binaries stays permanently. I can provide it also. It's just that I like SuperSU most and admire Chainfire work, would prefer SuperSU instead of Kingroot.

Wysłane z mojego Oppo Find 7 przy użyciu Taptalka
[SuperSU] kmcphee:
Youre Squared Away!
[SuperSU] zadigre:
thanks for you hard work!

as always, it installed fine, flashed with TWRP recovery, on my HLTE on CM 11 nightly.
[SuperSU] kmcphee:
No problems here Sprint Samsung Galaxy S5. Thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] robygt:
Working fine on Nexus 4/Lollipop.

Sent from the happy land of Mordor by my polite Nazgûl followers.
[SuperSU] Frank Westlake:
2.17 OK on:

- Note_ SGJ-I717 4.0.3

- Note3 SM-N900V 4.3 Permissive

- Note3 SM-N900T 4.3 Enforcing

Frank
[SuperSU] jcarreira:
OK on 1+1 too
[SuperSU] jesssiii:
Good on LG G2 Verizon and Liquid Smooth 4.4.4
[SuperSU] rcobourn:
Boot looping on my T-mobile Note 4.
[SuperSU] Mariner_1712:
All good on xdabbeb's 2.2.0. ROM for LG G2
[SuperSU] JaCh0o:
SuperSU 2.17 BETA still not working on Oppo Find 7 (x9076) with ColorOS 2.0.0i Build 1017 (KitKat 4.4.2). Still random root privillage rejection.
[SuperSU] Elaugaufein:
Am I understanding 2.62 right in that if I want to install busybox to /system/xbin without modifying /system then what I need to do is install it to /su/xbin_bind , which will result in apps that look for it in xbin finding it there ? (since xbin_bind gets mounted over system).

On the other hand it seems like system would have to be copied per boot in case an OTA modified it , wouldn't that result in Busybox getting cleared ?

Is there some way to do a semi-permanent install to xbin without modifying system ?

(I'm on a 6P for reference).
[SuperSU] mistermojorizin:
it's safe to flash 2.62 directly over 2.61?
[SuperSU] sidamos77:
Worked fine for me without workaround. And Autorun Manager and Kernel Adiutor can find it.
[SuperSU] egingell:
OTA runs in recovery where nothing non-stock is mounted or bound.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Elaugaufein:
Yeah, but I mean in order for this to work you'd have to synch system/xbin to su/xbin_bind after each boot in order to account for things like that and that would theoretically remove anything installed to xbin_bind wouldn't it ?
[SuperSU] Android-Desire:
Open ZIP, remove the system files you want to remove, then flash profit.
[SuperSU] GloriousGlory:
I'm still losing root every time I reboot. Am I doing something wrong?
[SuperSU] Ingenium13:
An OTA would rewrite boot anyway and set it back to default, wiping root. So you'd have to reinstall supersu from recovery no matter what. In which case I believe it'll recreate su/xbin_bind from the current set of files in system/xbin.

I'm also not sure if you can take the OTA without unrooting first. It depends if boot is a binary patch like system or if they include a full copy. If it's the former you have to unroot first.

Sent from my Nexus 6P
[SuperSU] Elaugaufein:
Ahh, yes that's the bit I was missing. You don't have to copy system dynamically because anything that would alter system would also require reinstalling SuperSU anyway, so there's no synching issues.
[SuperSU] aaaadrian:
GSam Battery Monitor with Root Companion is not working properly (without Root Companion it is OK, but with limited information) on Nexus 5.

I don't know if it is SuperSU_Beta 2.62 or Android 6.0.1. (worked before with 6.0.0. and system less root with changed boot.img and a prevoius SuperSU beta 2.52 or 2.56)
[SuperSU] scandiun:
Could the system partition size be increased repartitioning the device?
[SuperSU] anmg:
tested version 2.6 on Xperia M2 Aqua with Android 5.1.1 and Fkernel 1.1 - everything is OK
[SuperSU] Jacktheskipper:
Just wanted to report in:

- installed 6.0.1 MMB29K factory image on my Nexus 5 (removed -w from flash-all.bat)

- installed CWM Touch recovery (recovery-clockwork-touch-6.0.4.5-hammerhead.img)

- installed SuperSu 2.62 Beta from recovery

Up until now everything works perfectly fine and no unexpected behaviour.

Thanks so much for your hard work and dedication Chainfire!
[SuperSU] wiQbold:
I am a little confused about the warning from chainfire about /system.

did that mean I couldn't delete all the googlecrap in twrp if I don t want to get bootloops or maybe more worse!?
[SuperSU] Ingenium13:
I can't be completely sure this is related to the new bind mount of /system/xbin, but after flashing 2.62 today I lost the ability to grant apps run time permissions. They never requested the permission and were just silently denied, though I could manually go into app info and turn them on. I disabled the bind mount (deleted /su/xbin_bind) and rebooted and run time asking for permissions was back.

It could have just been a fluke, but it might be worth someone else checking out to see if they have the same issue, since I could see it being a security measure in Android. An easy way to test is to remove Keep's Location permission then try to add a note with a location based reminder. If it is greyed out then something is wrong, it should popup asking for permission to access location.
[SuperSU] kc2kzz:
It doesn't work for me either with systemless root. It worked fine for me on 6.0, but I wasn't rooted. I switched to Battery HD and that is working fine, although doesn't have as many features.
[SuperSU] thaidroid:
chainfire

"As always though, I strongly recommend against installing BusyBox and symlinking it. In my experience it is the largest reasons for unexpected behavior of root apps."

Are you saying no need for busy box, are there not certain apps that need it?
[SuperSU] bautrupp:
If for some reason you don't want to be rooted but unencrypted this might help.
[SuperSU] noobhero:
[MENTION=631273]Chainfire[/MENTION] sir, is there a need to delete the su files we manually created in bin and xbin after flashing 2.62 ?
[SuperSU] Aliston Pinto:
Its not ota survival using on moto g 2014 with cm 13
[SuperSU] Pkt_Lnt:
You have to look at what he quoted and read the whole thing carefully. You are taking one sentence totally out of context! Symlinking is the key word there. ;)
[SuperSU] xxxmadraxxx:
Can't Mount Errors Galore

[Apologies if this has been mentioned earlier in this thread but, 9000+ posts is a bit too many for anyone to read through!]

I just managed to root my Nexus 7 last night, after trying multiple times with both CWM and TWRP recoveries of various guises and vintages . The recoveries would install fine, but I could never get SuperSu [or anything else for that matter] to install or sideload from recovery. I'd just get loads of Unable to find.... and Unable to mount.... errors, similar to those in this piccie I shamelessly lifted from another post in another thread

The answer in that thread worked for me first go and I'm now rooted. I'm just throwing it into the mix here, in case anyone else has been banging their head against a brick wall on this. I must have followed a dozen fruitless leads when searching for a solution to this, only for the answer to be sneakily hiding on this very forum.

TL;DR:

Instead of the 'regular' CWM or TWRP recoveries, try the TWRP mulitROM one from here --->

https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view

[Posting the whole URL as I doubt my newbie post count will allow me to embed links]
[SuperSU] Chainfire:
Next ZIP update I updated the app replacement mechanism. Hopefully it will pick up this case.

Shouldn't be needed, no.

It has indeed been mentioned before. If you search this thread for "flo" (the name of your device), the first result is the answer. (or was... maybe this post will be the first result now)
[SuperSU] ayamgoreng:
using supersu 2.60 or 2.62 I can't install viper4android driver,

un root, then flash 2.52 I'm able to install the driver.

Tested with T705 + 5.02 lolipop + skyhigh kernel (selinux = permissive)
[SuperSU] Tanveerul:
Do we have root file for Android 6.0.1 (Build No - MMB29M ) ?

I have not rooted my Nexus 6P till now and I updated my android to 6.0.1, now I don't see root file for build - MMB29M

Can you please help me with this.

----Edit---

Basically, I need boot image for build MMB29M
[SuperSU] SamuriHL:
I'm not sure what's happening on the Samsung 5.1 kernel devices, either. But it happens on both my S4 GPE and my Note 10.1 2014. Once I flash back to stock boot img manually everything works as it should. One thing I noticed on my S4 GPE, and I'll check the Note 10.1 2014 shortly, is that there were multiple stock boot img backups in /data. Which is odd because it's the same Android version that I've been using with 2.6.0, 2.6.1, and 2.6.2. I deleted all but the latest on my S4 GPE and I'll check to see if my Note 10.1 2014 has more than one backup. Could that cause the restore functionality some confusion? My NX6 only has one stock boot img backup and it's been through the exact same upgrade process from 2.6.0->2.6.1->2.6.2 that I tried on the Samsung devices. So that must be the key. Question is, why more than one backup on those devices?

EDIT: Nope. Note 10.1 2014 only has the one. I really don't know then.

---------- Post added at 09:27 AM ---------- Previous post was at 09:27 AM ----------

http://xdaforums.com/showpost.php?p=64161125&postcount=3

Read...fully.
[SuperSU] Chainfire:
2.61 didn't clean up the old backups properly. Even if you used the same original stock boot image you can get multiple different backups because the entire boot partition is hashed, while a boot image may be smaller, so if you flash/reflash multiple images (stock or not) with different size, the contents of the entire boot partition may differ.

Having multiple of these backups isn't the issue. Try flashing the ZIP and if it fails, post /tmp/recovery.log
[SuperSU] ashyx:
Holy cheeses... Here we go again :banghead::banghead::banghead:
[SuperSU] zuberio:
SuperSU 2.62 Beta installed on 6.0.1 via TWRP working great!

Reporting in:

- manually re-flashed 6.0.0 MRA58N factory images of bootloader, boot, recovery, & system on my Nexus 5 (back to bone stock!)

- Installed MMB29K OTA Update to 6.0.1 (would have side-loaded the update but I got the OTA notice yesterday)

- flashed TWRP 2.8.7.1 recovery image

- installed SuperSU 2.62 Beta via TWRP (did NOT let TWRP install root)

Up until now everything works perfectly fine and no unexpected behavior. Checked root apps are StickMount Pro, WiFi Key Recovery, Wakelock Detector Free, ES File Explorer (4.0.2.3), Titanium Backup, Terminal Emulator, Rashr

Thank you so much for all your hard work and dedication Chainfire!
[SuperSU] Chainfire:
v2.62-2

I've just posted v2.62-2 in the WIP thread.

There are no changes to SuperSU itself. The only changes to the ZIP are:

- (systemless) ZIP: Fix calling wrong script name for custom patcher script

- (systemless) ZIP: Improve APK overwrite

There is no need to update unless you had one of these two specific issues. However, it can't hurt to flash and let me know if anything goes wrong :)
[SuperSU] dratsablive:
I tried using the modified boot.img file to do a systemless root but it apparently is blocking the camera from functioning on my Nexus 6p. I had flashed the stock images to 6.0.1 then the modified boot image file. After rebooting camera would not open, ie just black screen. Flashing the stock boot.img file cleared this issue up.
[SuperSU] SamuriHL:
I know what the issue is but it's nasty and ugly. The versions of TWRP I'm forced to use on those devices do not support decrypting the /data partition, so, it can't be read from. I've included a log though, just in case I'm wrong.
[SuperSU] Hi78sk:
Thank you very much
[SuperSU] sefrcoko:
Strange, backup and restore seems to be working fine for me on sammy 5.1.1 n910w8... no issues here with supersu 2.62 as far as I can tell.
[SuperSU] SamuriHL:
I'm guessing you're not running an encrypted data partition OR you have a version of TWRP that can be used to decrypt it.
[SuperSU] confanet:
Hi guys,

I usually follow this forum every day but I’m little bit confused how to get root with 2.62 on my N6 using a different kernel from stock. Just not sure about the order I should follow.

I just need to follow these steps (I'm starting from a clean unrooted phone with 6.0)

1.	Flash stock system and boot img from 6.0.1

2.	Flash TWRP (if not yet present)

3.	Boot in recovery

4.	Flash supersu 2.62 from TWRP

5.	Flash custom kernel from TWRP

Is it correct? In this way I should also have my phone unencrypted (anfter a wipe and if the custom kernel has no force-encrypt).

Another noob question. Do I really need to install BusyBox? Does it works with systemless root? Do I need a different or manual procedure to install it?

Thanks
[SuperSU] Chainfire:
Not being able to mount /data would indeed be a cause for this issue. While I've gone through some trouble to make sure the install will still succeed, the backup restore case might not, hmm.

You can skip (5) Flash custom kernel. Unencrypted is indeed possible. You don't need to install BusyBox unless you need it for some specific reason, which for most people means they don't.
[SuperSU] Chainfire:
v2.62-3

Make that v2.62-3

There are no changes to SuperSU itself. The only changes to the ZIP are:

- (systemless) ZIP: Fix calling wrong script name for custom patcher script

- (systemless) ZIP: Improve APK overwrite

- (systemless) ZIP: Do not move backups from /cache to /data, just copy them

There is no need to update unless you had one of these two specific issues. However, it can't hurt to flash and let me know if anything goes wrong :)

[MENTION=2812087]SamuriHL[/MENTION] Please flash back stock boot img, then flash the 2.62-3 ZIP, then boot into Android, then flash that same ZIP again to see if the restore works now.
[SuperSU] GiGiSSiMo:
Link seems to be broken...

EDIT: Because there's V3 :D

Just a question, does it work also on Android L?
[SuperSU] SamuriHL:
Will do. My S4 GPE is one of the devices that has the stupid Android is updating issues after flashing SuperSU zip, so, it's still optimizing 151 apps from the last attempt. This will take a bit of time but I'll let you know if it works. Thanks!!
[SuperSU] Alxoom33:
Is this something that will be addressed by @Chainfire.eu in 2.6.x?or is this a user issue?
[SuperSU] Pkt_Lnt:
Change log for versions in in post # 3 or 4 or so in this thread. That will answer your question.
[SuperSU] SamuriHL:
Ok, so this worked. I'm guessing any wiping of cache between flashing of SuperSU builds would negate this fix, yes? :)
[SuperSU] tsadev:
Try flashing the kernel before you flash SuperSu
[SuperSU] Chainfire:
The way I have understood it, you guys have reasoned your way into an issue without checking how it actually works. As far as I'm aware, the issue doesn't actually exist, and as such, doesn't need any fixing.

You are correct.

Of course, "wiping cache" may go in the same bin as "installing busybox" and "fixing permissions". The times where they actually fix anything of relevance are rare indeed. At least wiping cache rarely results in actually breaking things, unlike the other two :)
[SuperSU] SamuriHL:
Yea, the move to ART certainly has changed things in that department. But the upshot is even if I did want to wipe the cache, for whatever stupid reason, I could just copy off the backups, wipe the cache, and then put them back when I was done. That's at least a useful workaround. There's a 99.9% chance I'll never wipe the cache anyway, so, I think this solution works great. Thanks for fixing it!
[SuperSU] bill_kevin:
i have installed v.2.62 12/11/205 but the app does not disable knox, any help?
[SuperSU] dratsablive:
I flashed the new system images for my Nexus 6P. Then installed TWRP, flashed the SuperSU-v2.56-20151030013730.zip file for systemless root. The application is available but reports that the binary is not available.
[SuperSU] chikimonke:
Why didn't you flash the latest 2.62?
[SuperSU] dratsablive:
Because I was trying to flash the Systemless root that was mentioned in the thread.
[SuperSU] chikimonke:
2.62v3 is the latest systemless
[SuperSU] Alxoom33:
Thanks for responding to my post. First, just wanted to say that 2.6.2 and versions-1 and-2 have all been working flawlessly for me on my NX6 running 6.0.1 with EX3.0.7 kernel and CATCLYSM mod. My inquiry was not to report a bug, but to find out if this was an actual issue for systemless root, which you may be planning to address. Based upon your response, it seems that the busybox matter is a non issue.

Second, I have seen statements by experienced contributors that tell users to root with 2.5.2 because 2.6.x is too untested or unstable. Would you provide me with a quote, to respond to such posts. Thank you!
[SuperSU] dratsablive:
Do you have a link for that, can only find 2.52.
[SuperSU] Captain_Throwback:
It's in the same place you got 2.56.
[SuperSU] jokerclown:
Always look for newest SuperSU there Link
[SuperSU] dratsablive:
That was what I needed. Thanks!
[SuperSU] SketchyStunts:
your KNOX is tripped as soon as you flash a recovery. No way around that. lol
[SuperSU] bill_kevin:
I know that hehe lol, I never said how to disable tripped knox, I mean I have warning knox security (screenshot)
[SuperSU] Zer3s:
Hammerhead; 6.0; Supersu2.62-3: Tried the OTA 6.0.1, but after some progress in recovery it stops and just says error? Shouldnt this work now with systemless root?
[SuperSU] boxcar8028:
Just flash SU-2.62-3 over SU-2.56 on my stock 6p running MM6.0.1 and all booted up just find. Great job Chainfire, super smooth and easy, just like old times. THANKS MAN!
[SuperSU] Ingenium13:
You need to make sure you're on stock recovery. And if the OTA patches boot instead of including a full copy (which I'm guessing is likely), then you need to unroot from the SuperSU app or the patch will fail.

Sent from my Nexus 6P
[SuperSU] Aggiefury101:
Hey guys I'm trying to root my note edge n915a. I've never rooted this phone before.I get to install twrp and can't seem to figure it out. Help!
[SuperSU] Faixa-Preta:
Downgrade from 2.62-3

How should I go about going from 2.62-3 to 2.61 can I use UNSU script to remove all traces or is there a better method?
[SuperSU] santadomingo:
Why you do this question!! Please read the thread!! And happiness ?! With the unSu you uninstalled all supersu! So you can flash
[SuperSU] Faixa-Preta:
I see nothing in the thread about going back down from 2.62-3, that's why I asked.
[SuperSU] santadomingo:
The way you have is Wright, is the simple way!! To install all a out 2.60 over!! Sorry my fault!!

---------- Post added at 10:30 PM ---------- Previous post was at 10:26 PM ----------

If you flash the unSu you can flash every supersu!!! Because you have no supersu !!
[SuperSU] ashyx:
Remove/disable security log agent.
[SuperSU] maluus:
I tried 2.61 and 2.62 (v3) but both causes boot loop on my nexus 5 with 6.0.1. After that reflashing the boot.img and system.img doesn't solve the problem. It may be recovered only with data wipe. I tried 2.61 few times but it causes bootloop from the beginning. But when I flashed 2.62, it booted normal for the first time and the root was working, everything seemed normal. But when I rebooted it bootlooped again. Btw what I mean with boot loop is that it stucks at four animated circles, screen brightening and dimming constantly without reaching to the android text. Is this a known problem?
[SuperSU] santadomingo:
Please use the unSu.zip for the first, go in your recovery flash the zip, after than flash the 2.62.3 zip! Try this way!! I hope I can help with this way
[SuperSU] weedy2887:
Mine flashes but doesn't boot.

04-14 04:19:03.123 148 148 I auditd : type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
04-14 04:19:03.123 148 148 W auditd : type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
04-14 04:19:10.093 1 1 W init : type=1400 audit(0.0:4): avc: denied { relabelfrom } for name="hosts" dev="mmcblk0p28" ino=24580 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
04-14 04:19:10.583 204 204 W init : type=1400 audit(0.0:5): avc: denied { execute_no_trans } for path="/system/etc/install-recovery.sh" dev="mmcblk0p25" ino=40961 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
04-14 04:19:10.813 214 214 W init : type=1400 audit(0.0:6): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p25" ino=32770 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

Flashed hammerhead-mmb29k with fastboot.
[SuperSU] edrickmph:
Where is the download link of unsu.zip?
[SuperSU] swallowingled:
http://xdaforums.com/showpost.php?p=63615067&postcount=2459
[SuperSU] sidamos77:
Disable the app SecurityLogAgent.
[SuperSU] santadomingo:
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067#post63615067

---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------

It's works
[SuperSU] Clark Joseph Kent:
Thread Cleaned of trash/spam....carry on please.....
[SuperSU] Alxoom33:
I appreciate the explanation. I just didn't like the "you should read before posting" part. However, thank you for your response. We're good!
[SuperSU] castrwilliam:
Would removing root's reserved blocks (i.e.

tune2fs -m 0 $insert_system_partition_here

when it's not mounted) be a solution to this?
[SuperSU] Aggiefury101:
Been at this all day please help

Im on Note Edge N915A. I can't seem to flash twrp because of a secure check fail recovery error. I've already disabled R/L. Thus I can't try this awesome piece of work. Can anyone point me in the right direction?
[SuperSU] EvanVanVan:
With the Systemless root #2, it says to tell "TWRP keep it read only if it offers."

Is there any problem with allowing it to make modifications? Or does it just negate some of the benefits of the "root without modifying /system"?
[SuperSU] mjohnson4580:
Can the latest su be installed to /system if your not worried about system less root?
[SuperSU] Alxoom33:
Use 2.52 if you want to root to System.
[SuperSU] :
I did the reading and chainfire mentions it in post #3665, but i still don't understand... For the nexus 6p (stock, 6.0.1, 2.62.3), is system space an issue? I use Layers, adaway, busybox, and a bunch of xposed mods...

Should i follow these instructions :

So is system space a problem for n6p and if the above quote is for something else, should i do the command anyway? I'll flash 2.62.3
[SuperSU] hassann98:
galaxy s6 edge g925f

bootloop!

2.62!

rom : G925FXXS3COK5
[SuperSU] FPSUsername:
My rom came with v2.52 pre installed using xbin directory. How can I update to v2.62-3? Do I have to unroot (and how do I do that on xbin version) it first or can I upgrade directly?
[SuperSU] anakdayak:
Hi an i flash this 2.52 on top of 2.46?Currently ion on xperia z1 lollipop.
[SuperSU] shaggyskunk:
Yup - I haven't had any issues with 2.52 on any LP or MM Roms.

Sent From My SM-N910W8 Running SlimRemix V5.3
[SuperSU] dmantilal:
2.52 is the standard SuperSU, beta, that requires a custom boot.img to allow SELinux to run in Enforcing mode and modifies /system.

2.62 is an experimental beta that only modiufies the boot.img and tricks the OS to think files are on /system which actually are not, using overlays. Referred to as "systemless"

They are two separate projects. 2.62 is not tevhnically an upgrade to 2.52. There are loits of great Chainfire posts and FAQ threads in this sub-forum that you should read. Try not to brick your device... stay with 2.52 unless you are fully aware of 2.62's differences.

Read http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125#post64161125 and the complete thread.