yashsingh1/xdaforums huggingface dataset:
[SuperSU] Fif_:
I did further testing with SuperSU 2.65, but now on a Nexus 4 running 5.1.1 / LMY48M.

Experiment #1:

I started from SuperSU 2.46, with "mount namespace separation" initally enabled.

I proceeded with the upgrade to 2.65, I was asked to update the su binary and reboot.

Upon reboot, I launched terminal emulator:

u0_a79@XXXXX$ ls /sdcard /storage/emulated
/sdcard:
Android
DCIM

/storage/emulated:
0
legacy

u0_a79@XXXXX$ su -c 'ls /sdcard /storage/emulated'
/sdcard:

/storage/emulated:
0
legacy

u0_a79@XXXXX$ su -mm -c 'ls /sdcard /storage/emulated'
/sdcard:
Android
DCIM

/storage/emulated:
legacy

When running as a regular user, /sdcard and /storage/emulated are fine.

When running under su, /sdcard is busted while /storage/emulated is OK.

When running under su -mm, /sdcard is OK while /storage/emulated is busted.

Experiment #2:

I then toggled "mount namespace separation" off and rebooted.

u0_a79@XXXXX$ ls /sdcard /storage/emulated
/sdcard:
Android
DCIM

/storage/emulated:
0
legacy

u0_a79@XXXXX$ su -c 'ls /sdcard /storage/emulated'
/sdcard:
Android
DCIM

/storage/emulated:
legacy

u0_a79@XXXXX$ su -mm -c 'ls /sdcard /storage/emulated'
/sdcard:
Android
DCIM

/storage/emulated:
legacy

When running as a regular user, /sdcard and /storage/emulated are as expected.

When running as su, /sdcard is OK but /storage/emulated is borked.

Adding -mm to su has no effect as "namespace separation" is off.

Experiment #3:

I toggled "mount namespace separation" back on and rebooted.

u0_a79@XXXXX$ ls /sdcard /storage/emulated
/sdcard:
Android
DCIM

/storage/emulated:
0
legacy

u0_a79@XXXXX$ su -c 'ls /sdcard /storage/emulated'
/sdcard:

/storage/emulated:
0
legacy

u0_a79@XXXXX$ su -mm -c 'ls /sdcard /storage/emulated'
/sdcard:
Android
DCIM

/storage/emulated:
legacy

We are back to the same situation as #1.

So for me:

Toggling twice "enable mount namespace separation" has no effect (which is expected).

Using 2.65, neither "mount namespace separation" option gives me a working supersu as either /sdcard or /storage/emulated is busted in both modes.

I'm reverting back to 2.46 once more :)
[SuperSU] LoverBoy2415:
[MENTION=4860519]Tzfardaya[/MENTION] .. Was Facing Issues In Titanium Backup .. & SuperSU Mount Namespace Separation Was Already Marked ..So Unchecked & Rebooted As U Said ..Now TB is Working Fine Again :) .. Thank You :) ..
[SuperSU] ob1silvia:
What exactly did you do to get this to work . Did you toggle off the mount then reboot or did you toggle off then on them reboot
[SuperSU] LoverBoy2415:
I just toggled off The Mount Option In Supersu ..It Was Already Marked By Default ..So Toggled Off & Rebooted ..Now Everything Working Fine ..
[SuperSU] spainter:
This also works with the 2013 Moto X Dev Edition, but isn't necessary on the Nexus Devices I have. Out of 3 Tablets and 4 phones the only ones that seem to need this is the Moto X.

None are Samsung devices.
[SuperSU] ajmawhinn@gmail.com:
Not sure where to post this but SuperSu has been asking me to update it. I try to update it but it tells me the update failed and to reboot my device. I've rebooted 4 times and keep getting the same error. Just letting you know. Thanks for all your hard work. -Device--Nexus 6P
[SuperSU] egingell:
There's a link in the OP to where one posts issues with updating the binary.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] skulldreamz:
Flash this in recovery, you'll be good to go.

https://www.dropbox.com/s/viin6zfb3nxl52l/BETA-SuperSU-v2.67-20160121175247.zip?dl=0
[SuperSU] phaze3131:
so whats going on with this, there aren't any instructions on how to update. I'm on 2.46 and need to upgrade.

Flash in twrp?

uinstall then flash?

uninstall, do a hand stand, flash?

eat cheesecake, go into su settings switch superuser app, look at it till you get dizzy and more confused?
[SuperSU] ob1silvia:
Wow this worked i hope people having the same issue see this thread i was on another thread that specifically says all problems go to another thread i found solution here thanks
[SuperSU] su35:
moto g 2015, original rom and just unlock bootloader. I first flash 2.67, and get soft brick; then try the 2.46, and no help. could I flash the 2.65 or 2.62-3 to remove the bootloop?
[SuperSU] :
Follow this guide exactly. will work on moto g 2015 too.
[SuperSU] jwgallardo:
I been following your comments about Moto G. I have a Moto X-Force and I rooted using SU v2.62-3. At that moment it seems no other SuperSU version was working. Now I have the new v2.65 waiting in the playstore. In your experience, Do you think I can update from the playstore without any issues? Using normal update instead of TWRP to update binaries? My device has MM 6.0. Thanks!!!
[SuperSU] su35:
Hi gauravrai

Thank you very much, it works:good:. Could I update supersu in play store regularly?
[SuperSU] hongning:
Nexus 4 Did an autoupdate SuperSU and now doing bootloop Help

Good morning, I have a rooted Nexus 4, with stock Android 5 Rom with TWRP 3.0. I did an auto update when SuperSu requested and did the CW,TWRP selection. It gave me some kind of missing error and went directly to TWRP. It did some script and now is bootlooping.

Can I be given guide/instructions on how to restore, without reinstalling ROM/Reset? Unfortunately I don't have any NAND backups.
[SuperSU] hongning:
After Flashing SuperSU 2.65, Recovered from Bootloop but no SuperSU

Based on what I read here I flashed the SuperSU2.5 and I recovered from BootLoop, however I cant seem to find SuperSU app? It seems to still have root as non of my root programs are complaining. Should I flash SuperSU 2.65 again? Thanks for the help
[SuperSU] Ahkah:
su update prevented the device from booting

Yesterday SU told me it needs to update, told me to reboot the device (Nexus 7 tablet, 2012 version, Lollipop) to twrp, then something was installed, the device booted again, and now the boot animation never stops. I can still enter the boot loader and switch the device off, but Android does no longer work.

Is there a preferred way to regain control over the device?

PS: I just read that the previous writer had the same problem. I will try to find the mentioned version 2.5 and to find out how to flash it.
[SuperSU] stealth_nightshade:
im having problem with adb in my device, anyone here got the same experience? i dont know if its connected with SuperSU. I backup my TA partition and it went well while im having SuperSu 2.46 in my device which is available in Playstore for free. After that I bump into this section where it says that there is already an update of SuperSu to 2.65 and I decided to update it. After that, my backupTA is not working anymore when I tried to backup it again and also when doing a restore dry-run from my previous backup. I already planned to unlock my bootloader its just that sony took ages to reply with my unlock code and now Im facing this problem. SuperSu update is the last thing I did before my Backup TA is not working anymore. Anyone can help? Thank you very much
[SuperSU] avercros:
Where i can find the latest stable apk file? I tried apk mirror but i can only find betas.

I can't use playstore at the moment, thank you.
[SuperSU] LoverBoy2415:
Use the Stable 2.65 Zip in the thread itself & open It then Open Common folder you Will have The Stable 2.65 Apk..
[SuperSU] avercros:
Thank you for the idea.
[SuperSU] LoverBoy2415:
Yeah Its The Most Trusted One..As Its Uploaded by [MENTION=631273]Chainfire[/MENTION] Itself ..So Why We Need To Download The App From third Party sites ;) .
[SuperSU] MrTrip:
My HTC One M9 with Marshmallow can't install SuperSU 2.65... I flashed the Zip file and the app never shows up and I never get root.

No, I do not allow TWRP to install su or root for me, it never asks me if I want to anyway.

Running TWRP 3.0.0-1

I'm at a loss, I have no idea what is going on, I'm using this ROM that should have it all integrated http://xdaforums.com/verizon-one-m9/development/6-0-verizon-htc-one-m9-marshmallow-3-37-t3318605/

I'm the only one on the planet that seems to have this issue... I have tried flashing the firmware over and over and over again, did an RUU, everything, it still never writes the app to /data/app and never gives me root again..

Phone is S-OFF
[SuperSU] Manuel15:
After flashing the file, boot the system, go into the zip file and you'll find SuperSU apk in the "common" folder. Try to install it (you'll have to activate the "unknown source" setting if you didn't already)
[SuperSU] MrTrip:
First, I have NO Root. It is not installing root at all. It is spamming files all over the place. I have started a post on this here -> http://xdaforums.com/showpost.php?p=65559640&postcount=637

I have attached all log files. Something is seriously wrong and I need some help on this, I have two phones it is not working on now.
[SuperSU] arnab:
[MENTION=631273]Chainfire[/MENTION] Can you plzzz take a look in this problem.

My source code is http://github.com/kularny

I am trying to use this on DirtyUnicorns for i9100. For some reason it fails. Tried changing RD compression from gzip to lzma. Still doesn't work. Can you please provide me a solution. Thanks in advance.
[SuperSU] shoey63:
It's not the compression, it's the format. It can't be unpacked with standard mkbootimage tools. You need to force system root.
[SuperSU] arnab:
Any pointers on how i do that... I never played with SU b4...i get ur point that we need systemmode root... So can u help me how i do that.
[SuperSU] theankitkulkarni:
SuperSu v2.68 beta will work on Moto G 2015 marshmallow systemless?
[SuperSU] Lukest85:
Yes !! I upgraded from 2.67 systemless and everything is working fine here.

NB

If you flash the SU zip and are currently running a custom kernel;

Your kernel may need to be flashed again after SU

(if SU restores & patches the backup of your stock kernel during install - this occurred in my case)

Happy Flashing ;) pls post in the Beta thread next time.

Thanks [MENTION=631273]Chainfire[/MENTION] for the continued support and fantastic dev work !!

XT1550-Stock-MM-SU-xposed-RRO-Lspeed-v4a

Enforcing seLinux
[SuperSU] dirkdigles:
Just got the update to v2.65. Messed up my phone pretty good, at least the launcher.

I use Nova Launcher. My wallpaper is gone (black, no matter what I set), and it seems a lot of transparency in the UI is replaced by solid black. Can't use TB to restore because searching gives a black screen. Pressing menu in Nova Launcher gives a black box around the icons that are normally shown.

Uninstalled and back to 2.46. No idea what is going on
[SuperSU] Gaby4430:
Hey guys, since the last update, I cannot access to the app anymore. Supersu always refuse my pin code. How can I reset it?

(Ok, I found myself ! Just delete /system/.pin in TWRP :) )
[SuperSU] Manuel15:
How could SuperSU mess up the system graphic?
[SuperSU] dirkdigles:
No idea, but it did. Went back to normal after reverting to previous version.
[SuperSU] dunezoom:
I forgot my SuperSU pin. I've tried following the advice of removing /system/.pin, but no such file exists.

SuperSU is prompting for the PIN in order to update the binary.

SuperSU was version 2.65

To find out what version I was running when I set the PIN, I did Uninstall Updates to get back to the version that came with my ROM, so now SuperSU is version 2.46

SuperSU Pro is version 2.05
[SuperSU] Manuel15:
Actually, if you are using the systemless root, the .pin file is located in /su/etc
[SuperSU] Yamato-san:
The same for me. Go back to 2.46.
[SuperSU] Subrad5446@aol.com:
Same here. Tibu wouldn't work. I had.to unchecked Mount namespace seperation and reboot. Root explorer not working properly either. I'm getting random reboots, so I ran a catalog. Seems super su is the cause. Do u think these issues would be solved going back down to 2.46?
[SuperSU] infatality:
Change file storage in option.

Root Explorer working fine..
[SuperSU] stealth_nightshade:
ok, I will try it when i got into my device and will give you an update
[SuperSU] Dobsgw:
I had exactly the same issue with TitaniumBackup when I came to 2.65. Changing the mount space fixed TB, but then my internal storage went crazy/corrupted and I couldn't access most of my stuff. Nandroid is our bestfriend in times like that :P

If it happens I guess the best bet is to stay on the last working version and ignore the play updates (which is also annoying as I know I can't use it).
[SuperSU] Yamato-san:
For me yes, 100%. With 2.46 no one problem about six months.
[SuperSU] egingell:
I use Nova (Prime fwiw), TB, and SuperSU 2.65 and have no problems. It is not a SuperSU issue nor could it be. All SuperSU does is just sit there and wait for calls to its binary and the binary just grants access to commands and system binaries apps can't access otherwise... and Nova doesn't even use su, so there's not even a slight possibility that its problem is SuperSU related. At least not directly - if you have another su-using app that changes the wallpaper or messes with the graphics, I'd look into that.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] zelendel:
Not completely true. Nova does use SU. It was added a few versions ago to get around the android lag when pulling down the notification shade.

While I dont think it is the cause I just wanted to clear that up.

Its most likely the retarded Google search bar people like to use on their homescreens that had a bad update recently and people were told to revert.
[SuperSU] egingell:
I don't have a problem with the search bar, either, and I forgot about the alternate notification shade puller. I'm pretty sure it still doesn't have any impact on what I said, though.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] dirkdigles:
I'm using CF Lumen, also by Chainfire. He's been working on various issues from the newest set of updates. Definitely could be related, if not the culprit; however I assume most people who are using CF Lumen are also using SuperSU, so we'll see if others have issues.
[SuperSU] s-android:
i install the systemless version (2.68)

and not work on m8 dual sim with android 6

which version should i install?
[SuperSU] daniu:
Hi,

Hope this one does not end with people making fun of the S2 again ... Is this still the right thread for SuperSu for the S2? And: does anyone know something about the progress? Or is there a version already that works with CM13 for the S2?

regards
[SuperSU] fubo73:
I do not have any fresh info. I think still there is no supersu version working with CM13 on S2.

But currently, although I would prefer supersu, I can stay with superuser.
[SuperSU] FlyingHorseGA:
Installing the 2.65 binary screws up a variety of symlinks pointing to my internal SD card. I've tried both methods from within the app as well as installing the zip version via TWRP (Ver. 2.8.7.1). I'm running a Samsung Galaxy Note Pro 12.2" tablet (SM-P900) with Android 5.0.2 (CivZ P900 rev. 2.7).

Does anyone else have this issue?
[SuperSU] immelmann:
Is it possible to install SuperSU Pro (which I bought) on my gapps-free phone?

(If it was mentioned in one of 1000 pages then redirect me)
[SuperSU] djonx:
Hallo...

I've used SuperSU 2.46 before, very impressed with it, so stable and no bug I've found.

But after I updated to 2.65 stable version, my TitaniumBackup not working properly.

I can open the app with success root permission, but when I try to backup some app, error notification shown up said insufficient storage.

I check my One Storage, it said more than 10GB free space.

When I try rolling back to SuperSU 2.46, TitaniumBackup back working properly.

Did I miss something? Or is there something in SuperSU setting need to change...?

Thanks... [emoji4]

Sent from my 1+1
[SuperSU] LoverBoy2415:
Yeah..After Updating to 2.65 ..turn off the Mount namespace separation option Which is Already marked default in Supersu & Reboot once after its done ..Voilà now You Have Titaniuim backup..back on track ;) ..
[SuperSU] djonx:
[emoji3] [emoji4] Woooohooo...

Updated and Working Good Now...

Thanks [MENTION=6794596]LoverBoy2415[/MENTION]... Thanks for helping Me...

Sent from my 1+1
[SuperSU] LoverBoy2415:
Enjoy Man [MENTION=7313998]djonx[/MENTION] .. ;) ..You are welcome :) ...
[SuperSU] Strizay:
why can't this come with an already update binary? or an easier way to install it? I don't have a custom recovery and I need supersu to get one. it's like a stupid circle. what's an alternate way to update the binaries without having to flash it?
[SuperSU] erriperry:
If you already have root you can install SuperSu from Play Store and then install binaries from within the app (there should be a prompt when you open it).

Sent from my GT-S5360
[SuperSU] Strizay:
please tell me how from within the app
[SuperSU] brossovitch:
The post you quoted literally tells you how to do it.
[SuperSU] Strizay:
but when you try to automatically update it, it fails. Then what do you do if you can't flash it through a custom recovery? now you understand what I'm saying?
[SuperSU] brossovitch:
If the app doesn't work and recovery doesn't work you may need to use ADB.

Do you have busy box installed? I assume not. Perhaps flash a busybox zip from your custom recovery. And the app will work maybe?

Also, have you enabled ADB in developer options?
[SuperSU] Pkt_Lnt:
From post #1
[SuperSU] Strizay:
I can't flash anything my friend, I don't have a custom recovery. if I installed busy box from the play store, would that help me update the SuperSu binaries?
[SuperSU] Pkt_Lnt:
Read here what Chainfire says about busybox. It is more likely the cause of problems than the solution.

http://xdaforums.com/showpost.php?p=65273576&postcount=9972
[SuperSU] Strizay:
so the bottom line is that I will never be able to use SuperSu and install a custom recovery? that's how it seems now.
[SuperSU] Pkt_Lnt:
Look at Flashfire app by Chainfire.
[SuperSU] Strizay:
that's another circle, flashfire is what I'm trying to use, but it only uses supersu
[SuperSU] brossovitch:
You don't need SU to flash a custom recovery. Just a PC with ADB commands.
[SuperSU] Strizay:
all I'd like to do at this point is flash the updated supersu binaries
[SuperSU] Pkt_Lnt:
Go to the thread about binary update failures that I posted.

Or learn to use adb as suggested. You have been offered solutions, so posting that nothing works is not helping.
[SuperSU] Strizay:
I don't think it's worth it to file a complaint.
[SuperSU] Pkt_Lnt:
There is help there for update failures, it is not a complaint thread. OMFG
[SuperSU] makix13:
hi all,

First of all, sorry if it's an off-topic. I use supolicy from Master Chainfire in CM12.1 to be able to run v4a in enforcement mode and everything went great.

Now I move to CM13 and doing the same I've got an problem running supolicy.

I think it's something related to CM13, but any help will be appreciated.

Thanks Chainfire and all developers in Xda

Regards

S2 Cyanogenmod 6.0.1 [official nightly] - arnab isorec twrp - Xposed [official framework]
[SuperSU] Strizay:
is it possible that since I used kingroot to root my phone that's why I'm unable to update SuperSu binaries? I don't understand the adb method of pushing the binaries to my phone either. I can reboot my pone to stock recovery and adb is one of the options, I choose that and it asks to sideload a package. That's as far as my understanding goes with this. I hold shift and right click in the folder with adb.exe and open a command prompt and that's as far as I understand.
[SuperSU] egingell:
There are plenty of threads in which one can get hep with ADB. Search XDA for "adb". It's command prompt only. There are Windows apps that provide a front-end, but they're usually very basic and don't provide everything one needs.

There's also help with King Root in the SuperSU binary updates support thread, which is linked in the OP. Just search it for "kingroot" or "kingo".

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Strizay:
thank you for your help. would you mind point out the exact thread I need? I would appreciate it. I've tried supersu-me, several versions and they all fail. what most of them do is completely uninstall Kingroot and not install Supersu which is what the point of the app is.

If there was a way I could sideload supersu binaries that would be great. for some reason though, I don't think kingroot lets you auto update it over wifi.
[SuperSU] mfunction:
Is Google Store the only place to buy the SuperSU Pro key?

Is Google Store the only place to buy the SuperSU Pro key?
[SuperSU] jimbomodder:
Pretty sure yes.

Sent via S4 power!
[SuperSU] fubo73:
I bought from Amazon Apps.
[SuperSU] egingell:
It's no longer available on Amazon.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] fubo73:
Right. I checked the order, and the page is not available anymore.
[SuperSU] mfunction:
Wrong app.
[SuperSU] HenriHoen:
Warning after boot

After updating from 2.46 to 2.65 I experienced 2 problems. One (with Titanium Backup) I could resolve thanks to this forum, but I could not find a solution for the second problem.

After booting up my device (OnePlus One,stock ROM, TWRP 2.8.7.0.6) displays a message saying:

Android-system

There is a internal problem with your device. The device could be unstable until you will reset it to factory settings

Though evrything seems to work fine, I'm afraid that at some point I will get into (big) trouble. So I would appriciate a solution.
[SuperSU] jimbomodder:
Do a full backup then do a factory reset and restore the backup, worked for me

Sent via S4 power!
[SuperSU] HenriHoen:
Trouble!

I made a full backup, did a factory reset and tried to restore the backup. But restoring did not work. It says: Cannot restore System -- mounted read only.

What should I do?
[SuperSU] jimbomodder:
Backed up to removable storage? If yes remove the sd card and fully format the whole device then try a restore

Sent via S4 power!
[SuperSU] Cookie Ninja:
It's a One Plus One..... No micro SD card, only OTG memory......comes in 16 Gb and 64 Gb internal storages....

[MENTION=7207726]HenriHoen[/MENTION], It seems that you are using an outdated TWRP recovery......update your TWRP and then check if it's ok or not.
[SuperSU] jimbomodder:
Can u transfer via OTG to your pc?
[SuperSU] HenriHoen:
The backup is indeed stored on internal storage as the Oneplus One does not have the possibility for an external SD-card. And before I take any further action I want to copy the backup to my PC as soon as I get home from work in about 5 hours from now.
[SuperSU] jimbomodder:
OK 1 other thing you could try is format the system partition then reboot recovery and try restoring then.

Sent via S4 power!
[SuperSU] brossovitch:
Why does flashing this zip install systemless mode? But installing from the Play Store allows me to install to the system?

I'm using CM13 - Android 6.0.1
[SuperSU] bouchigo:
Go here if you want to install to system: http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] brossovitch:
I did install to the system. By installing from the Play Store. I was just wondering why the zip doesn't install into the system. Thank you, I have used every version of SuperSU before.

I enjoy version 2.65 installed in my system. ?

This definitely helped!
[SuperSU] Logan:
At the changelog beta 6.28 doesnt have "(systemless)" word that means it is not systemless?
[SuperSU] bouchigo:
The zip is setup that way. If you don't have the proper changes made to your boot.img it will install systemless every time. You can either flash the zip I linked to earlier that forces the install to /system, or modify your boot.img.
[SuperSU] brossovitch:
I downloaded from the link you gave.

Is it still chainfire SU? I assume someone just modified the zip but otherwise it's identical?

And I do have a custom kernel I'll have to speak with the dev about the mod for system mode..
[SuperSU] bouchigo:
Yes, correct :good:
[SuperSU] DroidJP:
I downloaded the zip and flashed. No issues. Feels more stable :)