yashsingh1/xdaforums huggingface dataset:
[SuperSU] HenriHoen:
I’m up and running again. This is how I did it.

I first wiped everything (except internal storage) en installed the stock ROM. This however replaced TWRP with stock recovery, so I then had to fastboot flash TWRP. Then I wiped everything again and restored the backup. And everything worked after that.

I even got the warning message, because SuperSu v2.65 was part of the backup. I removed this version and re-installed v2.46. And the warning is gone. Now I will first do some research (Google) before updating SuperSu.

Thank you all for your help.
[SuperSU] jimbomodder:
Glad you got it sorted :thumbup:

Sent from my SM-G903F
[SuperSU] Manuel15:
Every version since 2.56 is and will be systemless. The fact it doesn't have the "(systemless)" means there are not changes regarding systemless mode.
[SuperSU] grep_i:
Try to use scriptmanager from Google play store
[SuperSU] key Hole:
I have an HTC One M7 the update seems to have broken Titanium Backup and ROM manager any ideas

Sent from my One
[SuperSU] LoverBoy2415:
Insufficient storage issue in titanium backup ??..
[SuperSU] key Hole:
Yep..... and on Titanium Backup it cannot find the backup but it is there

---------- Post added at 07:38 PM ---------- Previous post was at 07:37 PM ----------

I'm sorry I meant on ROM manager could not find the backup

Sent from my One

---------- Post added at 07:47 PM ---------- Previous post was at 07:38 PM ----------

Uninstalling the update seems to have fixed the problem

Sent from my One
[SuperSU] LoverBoy2415:
After updating to 2.65 ..disable the Option Mount Namespace separation which is already enabled by default ..and reboot once.. It will fix titanium backup problem.. & I hope it will fix ROM Manager too ..
[SuperSU] iwearthebelt:
Good timing on this post , I'm having the same issue. Selecting (or deselecting) Namespace separation didn't fix it. I also tried the Beta 2.68 version but that didn't work either. Please share if you can't figure it out. Thanks!
[SuperSU] nareshnani142:
Hai all. Can anyone help me here. I have installed su 2.65 it all ways says the su binary needs to be updated! . I am on stock now when I use custom Rom like cm 12 it worked fine. Is supersu won't work with stock Rom. Plz help thanks in advance...
[SuperSU] stevenshea:
N preview at Nexus 6, SuperSU 2.68 not work, pks fix it, thanks.
[SuperSU] grep_i:
Did you flash the zip in custom recovery
[SuperSU] eggydrums:
Love super su thanks.for.this.

Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
[SuperSU] AndroidUzer:
Full unroot question for HBOOT 1.5, Unlocked, S-Off

Does the the "Full unroot" feature of SuperSU also relock the device if unlocked or do you still need to run fastboot oem writesecureflag 3?

And a follow up question will it switch a current state of S-OFF to S-ON?

Any input is appreciated!

Thanks
[SuperSU] avensakias:
Full unroot means that deletes the su.bin , busybox.bin ,symlinks for busybox & the supersu.apk.

It has nothing to do with s-on or s-off.

If i am wrong please correct me.

Sent from my HTC Desire S
[SuperSU] snandlal:
Big fan here.

Are there any plans to release your source code?
[SuperSU] Chainfire:
Full unroot only uninstalls SuperSU and all its components (including binaries and such).

If you have busybox installed, that will still be installed, that has nothing to do with root/unroot.

If you have CWM, that will still be there, that has nothing to do with root/unroot.

If you have OEM unlock, that will still be there, that has nothing to do with root/unroot.

etc.
[SuperSU] Chainfire:
SuperSU v0.93 released !

SuperSU has been updated to v0.93.

Important bugfix that may solve some freezing/hanging issues with some apps (more on that later) after initial permission allow.
[SuperSU] Prazaar:
Xda DL not working....
[SuperSU] Chainfire:
That's weird... contacting server admin !
[SuperSU] hpchiu:
can't download.:crying:
[SuperSU] Tungstwenty:
Hi Chainfire,

I didn't find any additional info about this use case, don't know if it's buried in the past posts somewhere.

Do you have any plans to address even partially this type of usage?

Just a while ago I was running one of the apps for which I want to be asked every time, and it bugs me a bit that I have to remember each time to click "ask me again" before allowing. Also the timer would be useful when some apps launch multiple su commands instead of a single one.

Sorry if has been responded in the past, but I didn't find it.
[SuperSU] sabbotage:
Is there any chance of getting a mirror for the zip until the XDA link is fixed? TIA!
[SuperSU] Chainfire:
Mirror added :)

CWM-SuperSU-v0.93.zip
[SuperSU] claytonjn:
+1

-Posted from my Verizon Galaxy Nexus
[SuperSU] Chainfire:
This is on my list to fix, but admittedly I have a lot of other stuff with higher priority.
[SuperSU] ironia.:
Best way TO install super su instead of su?

Tnx
[SuperSU] Pons:
Tried the Play Store? That way you get notified of updates.
[SuperSU] Pkt_Lnt:
Or as a last resort, read the OP. :D
[SuperSU] ironia.:
So now i have superuser i have boot TO uninstall it or just install super su from market?

Tnx
[SuperSU] mystical80:
How do you update supersu to .93, because I just rooted my phone and it came with .90, and doesn't give an option in playstore to update? Thanks anyone!!!
[SuperSU] Chainfire:
Inside SuperSU is the option to "clean for reinstall from market", use that button. The just install the version from market.
[SuperSU] LoverBoy2415:
I think that's the Only Fix for it so far regarding 2.65 And Titanium backup issue..Toggling Name separation worked perfectly for every users facing that issue including me.. [MENTION=4773434]iwearthebelt[/MENTION] ..

You flashed the zip or updated the binary with 2.65 apk ? .. I was using 2.56 zip & installed the apk of from 2.65 zip(Common Folder) & updated the 2.65 binary and rebooted ..after that titanium backup issue occurred ..then toggled it off(Namespace separation) ..& rebooted once ..and it worked like a charm after the reboot ..
[SuperSU] shoey63:
I personally don't use titanium backup. Twrp is just fine for me. But could users of the app PLEASE ask titanium app devs to fix the namespace separation issue? I'm sick of revisiting this thread, expecting something useful, only to find yet another question and reply about titanium backup issues.
[SuperSU] alandd86:
guys after flashing 2.65 on my note 4 n910 F twrp says ur device doesnt appear to be rooted !!whyy??
[SuperSU] nareshnani142:
Finally I have got successfully fix the problem. I have Google it an solved my problem..thanks for your REPLY..
[SuperSU] zzenyoo:
Ignore it. TWRP can't see new root type (systemless).
[SuperSU] newcryttle2015:
Dingbat here that don't understand root

Ok so I have a samsung t399 and the camera on it keeps saying ""unknown error occurred"" so im kinda doing research and it says to root, and clear cache on camera and media files, and to reboot to recovery.... all of it completely confusing the hell out of me and doing me no justice. So could anyone please explain how I can get my camera to work again.? Or is it a simple fix like ""dumbass download a new camera"" kind of thing. I am open for any suggestions just please respond back like your explaining this to a empty headed blonde. :eek:
[SuperSU] Mr. Poopybutthole:
Can't install Google Play Services

I am not able to install Google Play Services on my Samsung Wave GT-S8500. It was not installed after I flashed my device with MultiLoader V5.65, with the provided files for the GT-S8500. Is this the way it's supposed to be? I don't hope so, I would really like to use Google Photos on my Samsung Wave. I'm currently useing Amazon Underground to install apps, but I really don't think it is as good as Google Play Store. Do I have to re-flash my device or something? I have tried to install the .APK file of Google Services, but it won't install. However Google Play Store does install with the .APK-file, but I can't use it since Google Services is not installed. What do I do in this situation? Any suggestions?
[SuperSU] Manuel15:
I keep reading about the Titanium Backup issue over and over. AFAIK the Titanium Backup app has itself a screen (when you open it) which says "The mount namespace separation is activate in SuperSU settings, this could likely cause issues.. If you have issues try disabling it" Isn't the app showing the screen for some bug or aren't people reading it??
[SuperSU] grep_i:
You can try and install Google apps package from the following links.

http://opengapps.org/

OR

http://www.android.gs/download-install-and-flash-google-apps-for-android
[SuperSU] harshharry:
SOS

I recently installed new Marshmallow ROM for my Galaxy grand i9082 and after installing SuperSU, it is asking for binary file which I am not able to install.
[SuperSU] Pkt_Lnt:
http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] tolux1:
No prompt

I installed Supersu 2.65 on a huawei g7 with Android 4.4.4. I never get a prompt from Supersu. I can allow or deny request just fine. But when I try to use permission promting the requesting app just hangs. What could be the problem?

Tolux1
[SuperSU] grep_i:
Try Supersu 2.46
[SuperSU] tolux1:
Thanks for the quick answer. Unfortunately 2.46 also does not work.

---------- Post added at 11:33 PM ---------- Previous post was at 11:33 PM ----------

Is there a way to configure access without the prompt?
[SuperSU] egingell:
Yes, in the SuperSU app on the Apps tab, but your problem is likely because of tapjacking. Apps like Lux put up an overlay which SuperSU thinks is trying to jack your taps.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] tolux1:
I switched tapjacking protection off. No effect. l don't even get the prompt.

In the application tab I can't see any apps. When do they appear? After the first prompt?
[SuperSU] egingell:
They appear after the first prompt.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
Did you reboot phone after turning tapjacking protection off.
[SuperSU] Rix70:
With 2.6.8 greenify works much better, more fast.

Thank you as always.

M9/6.0. 1 (ViperOne)

Inviato dal mio HTC One M9 utilizzando Tapatalk
[SuperSU] nareshnani142:
I want to unroot my device HTC 816 a5 to update OTA 6.0 official(yesterday I got update msg) I have downloaded it and when I was trying to I install it reboots to (screenshot). I had Google it and it's to UNROOT your device and try it. Now the problem is I am confused to unroot it .. I also tried ROOT UNINSTALLER no use ..tried ROOT EXPLORER to delete system/bin/su not successful... I think here are more helping suggestions... Plz suggest me the best way...thanks in advance..
[SuperSU] nareshnani142:
Below error I had..
[SuperSU] tolux1:
Yes, I rebooted.

It's there any way to configure apps without them prompting first? It's there a file our a database which I can edit?

I could live without prompting butt I don't want to grant all apps root privileges.
[SuperSU] kakashi2k:
i have problem with root, on my nexus is not enable, why??
[SuperSU] harshharry:
Thank you, but I had visited this page before. It did not find any solution to my issue
[SuperSU] red john 07:
How to install the latest SuperSU from the zip file
[SuperSU] LoverBoy2415:
Flash the zip using recovery or u can install it as apk too & update the binaries ..open the zip using any file manager , & open common folder in that zip ..u will see the apk install it & after install & opening you will get a prompt to update the binaries ,update it reboot once ..that's it :).
[SuperSU] red john 07:
Thanks for quick reply one last question which way is better
[SuperSU] LoverBoy2415:
Lollipop or below or Marshmallow ??
[SuperSU] red john 07:
KitKat 4.4.2 I installed SuperSU from playstore last version I believe 2.65 need I to update it ? Thanks in advance
[SuperSU] LoverBoy2415:
Update it in apk method then :) ...
[SuperSU] red john 07:
Is there a forum that explain this two methods I mean why I use the apk method (sorry I asked you too many questions )

---------- Post added at 09:59 PM ---------- Previous post was at 09:56 PM ----------

I can't update su binary

---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------

Installation failed

Please reboot and try again
[SuperSU] LoverBoy2415:
Reboot & try again ..if it happens again like this flash it using recovery..
[SuperSU] red john 07:
I rooted my device with Kingroot and I replaced him with SuperSU ( I used I an app called SuperSUme ) he installed an old version of SuperSU then I updated him with playstore and su banaries updated successfully , can this help you to give me some help because I tried to update binaries with 2.67 version and didn't work also

---------- Post added at 10:23 PM ---------- Previous post was at 10:13 PM ----------

Help please
[SuperSU] LoverBoy2415:
Having custom recovery means flash the zip using recovery then ...or uninstall the update of supersu app in settings so you will have the older version apk now that is already installed as supersu as a system app by supersume ...now reboot and install 2.67 from the zip & update the binaries..
[SuperSU] red john 07:
SuperSU it's not a system app because I lost root when I uninstalled him
[SuperSU] LoverBoy2415:
Install the 2.67 apk & update the binaries now..
[SuperSU] red john 07:
I installed it but no update binaries prompt come to me , thats strange because because the update binaries prompt come to me when I overwrite 2.65 with 2.67

---------- Post added at 10:49 PM ---------- Previous post was at 10:41 PM ----------

Now I uninstalled 2.67 and installed 2.68 and I can't update binaries installation failed , what's this mess

---------- Post added at 10:55 PM ---------- Previous post was at 10:49 PM ----------

Give some help I m confused

---------- Post added at 11:02 PM ---------- Previous post was at 10:55 PM ----------

Now 2.67 working fine need I to update it to 2.68
[SuperSU] LoverBoy2415:
Binaries updated in 2.67 ? ..
[SuperSU] red john 07:
I don't no I think the first time I installed 2.67 I cancelled the binaries update and I installed playstore version again then I installed 2.67 and no update binaries prompt come to me ( I reinstalled 2.67 and no update prompt come) any way to update binaries manually
[SuperSU] grep_i:
Download the zip to your sdcard or downloads folder on your phone.

Boot into custom recovery and flash the zip file.
[SuperSU] red john 07:
Can't find the zip file from recovery where should I put the file
[SuperSU] LoverBoy2415:
Search in which folder its been downloaded when you done it..or move it to the root of the sdcard or internal storage ..
[SuperSU] grep_i:
Don't know for sure if you already download it from one of the following URLs.

If so find the download location which in most cases is the folder

'Download' or when on a SD card

'/sdcard/download'

TWRP / FlashFire installable ZIP:

Stable: http://download.chainfire.eu/supersu-stable

Beta: http://download.chainfire.eu/supersu-beta

Latest: http://download.chainfire.eu/supersu
[SuperSU] harsh.:
I have subscribed to threat long ago.but still not getting how to flash SuperSU without any trouble. I rooted device using kingroot then using flashify I flashed twrp n now using cm13 ..it has SuperSU.using which I give root access to apps.this is the only device that I have. Can anyone address me what to do!!!! :confused: (bootloader still locked) never unlocked it.
[SuperSU] Nimueh:
Sooo ... on a previous rom that didn't come with SuperSu built in (or so I thought) I flashed it and then let it install that backup script that's supposed to keep it alive through dirty flashes.

Now I'm back on a rom with it built-in, but I get update notifications in Playstore, so I'm guessing that script survived a clean flash too?

How do I go back to the proper built-in version without unrooting my phone? Or am I SOL and will just have to live with the update notification? I'm on 2.52 now and don't want any of those 2.6x ones ... too many people having issues with it plus I don't trust that systemless stuff :laugh:
[SuperSU] twobats1:
Hopeless
[SuperSU] red john 07:
I don't have custom recovery for my wiko sunset 2
[SuperSU] oraixearl:
Have a little issue. I can't flash anything newer than 2.52 thru recovery on my victara (moto x 2014). Updating the binaries via the app works fine and gets me to 2.65. My ROM is built with 2.68, but I loose su with every flash. Clean or dirty doesn't matter. Backup script doesn't help either. Tried with twrp 2.8.5 up thru 3.0, same result. Always get the message failure, aborting. Any help/advice.
[SuperSU] grep_i:
You do understand that writing in /system is more dangerous than not doing it, systemless.

So in terms of not trusting you should better not trust systemmode.

Systemmode had more potential to break the working of your device.

Maybe you confuse compatibility with trustworthiness.
[SuperSU] Nimueh:
I've been using the "normal" version for years without any problems, with systemless I see all kinds of users with all kinds of problems - I'd rather stick to what I KNOW works :)

So - is there a way to "undo" the backup script? Maybe a folder/file to delete or something?
[SuperSU] tolux1:
Configuring apps

Is there any other way to configure root-access for apps without a prompt (since supersu on my phone never prompts)?

Maybe via sql-editor or by editing a file?
[SuperSU] grep_i:
I use systemless from the first beta version without issues.

But if you want to stick to what you know you best install from Google playstore and disable auto update.
[SuperSU] Nimueh:
Not helping, see my previous post :laugh:
[SuperSU] grep_i:
Did not know that was even possible I thought you had to unlock bootloader to get root on your device working well.

Maybe you should try another super user app instead of Supersu.

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

So basically if I understand you correctly you don't want Google playstore to say that there is an update for Supersu.

Go to settings select "clean up for other supersu app download apk from apk mirror and install it and Google play won't prompt to update it anymore.

You could even install Supersu with aptoide.
[SuperSU] Nimueh:
My rom has SuperSu included already - so I'd do the cleanup and basically dirty flash the rom again to use the built-in version and get rid of the update notification at the same time? And that wouldn't unroot my phone?

I'm pretty sure the built-in SuperSU shouldn't have the update notification, it has to be a remnant of the backup script I let it install 2 (clean flashed) roms ago :laugh:

Edit:

OK, so I got my answer elsewhere: Under /system/addon.d/ delete everything to do with SuperSU (in my case 2 files) and that gets rid of the backup script that's not needed in custom roms with built-in SuperSU anyway.

That's all I really wanted to know :) :cool:
[SuperSU] DarkPhoenix19:
Hi, my rom has superuser built in, and I was wondering how to switch to supersu. Thanks.
[SuperSU] kamikaze702k:
Go into SuperSu settings, options are there to switch etc
[SuperSU] DarkPhoenix19:
Should I flash the zip or install from play store?
[SuperSU] Nepturion:
Chainfire, will the newer updates work on Xperia Z3 running 5.1.1?

There is no changelog saying this version is only for 6.0 etc..

I installed the 2.67 last time and my phone bootlooped...

I'm not going to update from my 2.66 unless I see some changelogs that makes me feel safe to install newer ones. :-/
[SuperSU] kamikaze702k:
What exactly do you want to do?? Switch the SuperSu app meaning what? Use another SuperSu app or do you want to update the existing SuperSu app? If it's built in your ROM and needs an update then do so from play store. Only need to flash the zip if you keep getting binary failure from the normal way....

---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------

Just stick to what works mate. The latest 2.69 is for Android N preview users!
[SuperSU] grep_i:
2.69 add support for Android N preview but also works on existing Android marshmallow I have it installed on my device yesterday and did not ran into any problems.
[SuperSU] iPAQ 6515a User:
There is a 2.70RC out there ..... but is it a real mccoy?
[SuperSU] goRt:
For me I lost the exposed framework (which was then reflashed ok), then had a single ui failure prior to unlock, then titanium had issues so I reverted.
[SuperSU] harsh.:
I just mount system to read/write n flashed 2.68.. N boom! M done! ????
[SuperSU] j1gga84:
No problems here with 2.70 RC.

TB has the same issues than with 2.68 so it is a TB issue.

TB is not optimised for MM in my opinion.

Regards

Sent from my SM-G900F using german Tapatalk 4
[SuperSU] Darke5tShad0w:
Yes but this is the thread for stable.

The beta thread is better suited for this, also checkout his g+ for info.
[SuperSU] grep_i:
So basically you got your answer the post before your initial question.

Great it works out for you.
[SuperSU] manbat:
Yep....Post link: http://xdaforums.com/showthread.php?p=65816783

Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
[SuperSU] _alexndr:
[MENTION=631273]Chainfire[/MENTION], I hope it is the proper place to ask you a question related to your SuperSU's update-binary shell script. Before I'll ask you - I'd like to thank for all your work!

My recent work (related to ROM development) also aims to moving all "magic" to update-binary (thanks again - for inspiration!), all is almost done, but after many days of work (incluging sleepless nights) I noticed, that my update-binary triggers "legacy property environment" in CWM based recoveries. Personally I don't prefer CWM based recoveries, but for some people who still prefer using it - such message could mean "stay away from this work as dev is at least NOT up to date!" (I mean reccomendations like "please upgrade to latest binary" ...)

Seems like you also had such problem (according to this old quote) but seems like you "solved" it already as your recent UPDATE-SuperSU-** installers does not trigger "legacy property environment" (at least it is not shown during install).

The question is - how did you do it? :)
[SuperSU] osm0sis:
I believe recoveries just updated so it's not an issue now. :good:

Hopefully you knew about my Complete Shell Script Flashable Zip EDIFY/update-binary Replacement + Zip Signing Documentation thread... definitely could save a few sleepless nights! :)
[SuperSU] MigoMujahid:
I believe it requires a modified boot.img to work on cm13, so would anyone link me to a modified boot.img for the s2 gt-i9100 or tell me how to make ONE??
[SuperSU] egingell:
Um... No, it doesn't.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] MigoMujahid:
But I realy tried it, the boot.img patcher faild to patch it in recovery, and after reboot no supersu installed.

Any help..:( ??!
[SuperSU] grep_i:
I want to try and help you but please don't let me search for your question.

Is it possible for you to describe with so many details as possible what kind of hardware and software you have.

What you're trying to do or what your goal is.

What you did and what the outcome was.

Maybe it is than possible to help you on your way.
[SuperSU] red john 07:
Hi guys I routed my device with kingroot and supersume and it worked fine I also updated SuperSU binaries to 2.65 play store version I checked the root and everything worked fine ( lucky patcher xposed ...) But i lost the root suddenly and SuperSU say there is no SuperSU binary installed I restart ed my phone and I get back my root (that's happened to me 3 times ) any help ?
[SuperSU] seraphyz:
anyone have a link to 2.27?
[SuperSU] Pank9j:
Which version works great with CM13 Snapshot.?
[SuperSU] LoverBoy2415:
Use this ... [MENTION=7085061]seraphyz[/MENTION] ..

http://download.chainfire.eu/630/SuperSU/BETA-SuperSU-v2.27.zip
[SuperSU] MigoMujahid:
I'm trying to install supersu on cm13, the recovery gave me some kind of ramdisk failure

I'm using gt-i9100

Running cm13 nightly
[SuperSU] fubo73:
You should know that supersu cannot be used on cm13 on i9100.
[SuperSU] j1gga84:
Are you sure?

I think you cannot use the systemless SuperSU, like in LP but up to SuperSU 2.52 it should also work under MM

regards