yashsingh1/xdaforums huggingface dataset:
[SuperSU] Fallen Spartan:
Care to elaborate?

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[SuperSU] nkojic:
Supersu stop working after last update. I told that already and i i can not find the problem so i post log in post above
[SuperSU] Fallen Spartan:
Don't you have backup of previous version on titanium backup? If so, revert to previous version and then update again. See if that works

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[SuperSU] nkojic:
No that doesnt work. I try reinstalling the whole rom with super wipe. And everything is ok with Mikes original supersu, but if i update it then this aplication doesnt work
[SuperSU] Fallen Spartan:
Strange, I have no such issues, even with uninstalling it. Have you tried fixing permissions? What happens when you install latest SuperSU on to a fresh flashed rom

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[SuperSU] nkojic:
Aplication stop working
[SuperSU] kylon:
i can t use gamecih with super su,it doesn t work

is it the app itself that has problems with sense 4 or it need a special permission?
[SuperSU] ghard1977:
Also have fc after updating v087 to v092, flash back to v087 seem to fix, but no update till cf fix this bug
[SuperSU] bluntman420:
CHAINFIRE, do you plan on updating chainfire 3d to be fully compatible with ICS? Night mode doesn't work and if i install the egl driver none of my games work correctly.( I get screen flicker,NOVA 3 is just a gray screen with no visuals). I did pay for it through the appstore and i know myself and alot of others are hoping/waiting for full ICS support.
[SuperSU] waltnich:
Moved by waltnich to another thread ...
[SuperSU] nkojic:
I solved my problem but i didnt update the supersu to the latest. Its what it was in Mikes 6.6.7 xe rom. I am waiting next update of supersu to solve problem with "stop working aplication".
[SuperSU] blowtorch:
When using Jelly Bean it SuperSu crashes the whole system when granting access to 2 applications (that I've found so far) which are LBE Privacy Guard and PGM2 (slide2wake). Is this SuperSu or the app or Jelly Bean ... any help is appreciated
[SuperSU] pdppdp:
PGM2 posted in Play Store that it's not compatible with Jelly Bean (will be soon). Maybe that's the reason.
[SuperSU] blowtorch:
yes i'm sure it is ... probabily the same thing with lbe privacy guard ... i just though i would mention it here
[SuperSU] peeyourownpants:
i installed supersu from play on my toro running aokp40 and couldn't get rid of superuser until i flashed the zip in op. everything's working fine now. thanks chainfire!
[SuperSU] Arie-:
Just to cite myself: is there a way around this "problem", or should I just accept the fact that I have to change right occasionally using the SuperSU app.
[SuperSU] JimSmith94:
Page numbers as reference are useless! I have my settings to show 50 posts per page, so this is page 200 for me.
[SuperSU] bodomfan:
Does super su not work when device is rooted with kingroot
[SuperSU] hgmichna:
10,000 posts

Ah, OK. But anyway, congrats for 10,000 posts!
[SuperSU] Follow_and_Feel:
Hey guys. I flashed v2.52.zip for none-systemless-root in order for Cyanogen nightlies to survive updates. Now it says "back-up script is not available in xbin-mode". What's xbin-mode and how do I get rid of it? :D
[SuperSU] liayanaa:
peranti

(Galaxy s4

Nombor

model

GT-19500

Versi

Android

4.4.2

Versi

jalur asas

19500DXUFNB2

Versi

inti

3.4.5-699287

dpi@SWDD5723 #1

Wed May 28 23:18:46 KST 2014 9

---------- Post added at 02:28 AM ---------- Previous post was at 02:24 AM ----------

Jxjxjjxj
[SuperSU] Johnnady:
Can't replace kingroot 4.8.0
[SuperSU] Iku123:
Hi binary is not updating anyone plz help thanks
[SuperSU] Giobio:
Bad reply, sorry...
[SuperSU] kostassfirakis:
Is it possible to upgrade from su 2.46 to super su latest version (2.67) using terminal emulator to flash the zip? [MENTION=631273]Chainfire[/MENTION]
[SuperSU] Pkt_Lnt:
Try this thread.

http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] loparaan:
Me too with Galaxy S2, I can not install it from the recovery. Give a mounting error in the ramdisk
[SuperSU] nohmaan:
I have a HTC One M8 running 6.0 Marshmallow with TWRP and unlocked bootloader, would I just need to flash the SuperSU STABLE v6.65 with TWRP to have it rooted?
[SuperSU] Doug Shuuyo:
When the SuperSU v2.65 will be available to download in play store? The version 2.46 still there
[SuperSU] shaggyskunk:
Personally - I never install SuperSU from the Store - Flashing the zip is by far the best method - imho

None of the "updating binaries" stuff.

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] manbat:
http://xdaforums.com/showthread.php?p=65113356

Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION] I have rooted my phone i.e. motorola MotoG 2014 running marshmallow using supersu 2.52 beta. For rooting I had to use a modified kernel/boot.img to achieve successful rooting process. Now I got to know that 2.65 is a stable version. Can I flash 2.65 flashable zip over supersu 2.52? Is supersu 2.65 is still modified boot.img dependent for marshmallow or can be flashed over stock unmodified kernal/boot.IMG? I need a expert advise.
[SuperSU] Aakash Kaushal:
Firstly uninstall the supersu fron the supssuapp settings then flash the lastest stable supesu 2.65 in recovery..thatz it,also makesure that u should take nandroid backup first so that if anything happens wrong then u willnot loose your data.
[SuperSU] egingell:
And Andi, since everything needs to be repeated, don't let TWRP install Superuser.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] :
My one query still remain unanswered..whether it is required modified boot.img or stock img.
[SuperSU] Aakash Kaushal:
I don't think it requires any boot.img bcz ur phone is already rooted and you are just updating the supersu by uninsatlling the previous one..just give it a shot, it will work:thumbup:
[SuperSU] :
This is not the case. Yes previously I have rooted my device with supersu 2.52 beta using modified boot.img but when I heard about this stable 2.65 supersu I restore back stock boot and when I rooting device with stock boot.img by flashing 2.65, it goes into bootloop. I have seen root tutorials of other Moto devices like moto x pure, play or style, they all didn't use modified boot.img but I dnt know why it is different in motoG 2014 running android 6.0.
[SuperSU] Aakash Kaushal:
http://xdaforums.com/showthread.php?p=63615067

In case of bootloop firslty try to uninstall the supersu from the uninstaller (from the given link) and then try to flash the supersu again...
[SuperSU] :
Man i simply want to know if rooting of motog 2014 running marshmallow with supersu 2.65 is possible with stock boot.img because i didn't see anywhere the requirement of modified boot.img as was with previous versions..?

I also want to confirm that I get bootloop when tried rooting with 2.65 version on stock boot.img. In my case rooting with 2.65 is only successful if I use a modified boot. I think bootloop Im getting with stock boot is a bug. I hope [MENTION=631273]Chainfire[/MENTION] will looking into this matter to solve my confusion.
[SuperSU] paradoxiumwind:
Quick question; how do I get the supersu app available so I can run it and access it? I installed it via TWRP and also the pro unlock on the play store, but I can only access it by going to phone settings -> scrolling all the way down, whereas I used to be able to have an app icon for it that I could launch, how do I get that back? Probably something basic but any help appreciated

Thanks in advance.
[SuperSU] melvinaury:
Did you try going to market and downloading the supersu app
[SuperSU] egingell:
You're not going to get a list of supported devices. Backup + try it. If it works, you have your answer. If it doesn't, post your logs. But there's no reason it shouldn't work. And it has been states numerous times that flashing over a modified boot image will break something.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] :
Here Im not expecting the list of supported devices. What I reported here is indeed involves many back up and restoration process. so these are not solution to my queries.

I repeatedly posted several times that it doesn't works. I advise you to look at those, just few posts back.

for the same thing Im curious for but rooting with stock boot doesn't works what works is with modified boot.img. still Im not getting satisfactory solution apart from providing log of bootloop.

If there is any method to log bootloops please share
[SuperSU] crypking:
Is SuperSU 2.65 the recommended version to use or is 2.67 safe as well? also does it matter if I use TWRP 3.0.0 or 2.9.1.2?
[SuperSU] Tzfardaya:
And yet, there is a lovely thread linked in the op regarding situations where supersu doesn't update/install correctly. Have you looked into that one? Perhaps the solution to your situation has already been mentioned there.
[SuperSU] drezz2:
supersu in google play, still 2.46?
[SuperSU] manbat:
http://xdaforums.com/showthread.php?p=65321353

Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
[SuperSU] kato7youknow:
[MENTION=631273]Chainfire[/MENTION]

Thank you for your great work on super SU v2.65

I flashed the latest stable super SU v2.65. With twrp 3.0.0.0. On my Samsung Galaxy tab 3 7.0. SM-T210R and it is working great .thank you for your great work.??
[SuperSU] drezz2:
yes, I saw, but the commentary is from the 02.02.16, it's been 15 days and still saw 2.46, so..i dont know if its normal "the delay".. its simply curiosity

thanks
[SuperSU] Aakash Kaushal:
Dont worry bro even i am also seeing 2.46 in googleplay store...he will update it in google play store bytheway if u really want to check your genuine supersu version then it can only be seen by going into supersu settings and that version will be your original supersu version...
[SuperSU] dimebolt:
Hi all,

I tried flashing the stable supersu 2.65 over my current 2.49 supersu via twrp 3.0.0 on my note 5 N920I (5.1.1) on arter kenel 11. but after reboot my supersu icon is gone and root check show my root is gone. Can anyone please advice what i did wrong?

TIA.
[SuperSU] :
Well probably I didn't get solution there's too. Pardon me if I missed something while searching that forum.

but as a part of proper reporting I am posting here kmsg log and recovery log of bootloop.

These logs are produced after getting stuck on Motorola boot logo (bootloop due to failure in booting of kernel).

how I got bootloop is below-

-flashed supersu 2.65 version zip on non root device using official twrp 3.0.0-0 recovery for titan (motoG 2014 XT1068 )

-wiped ART/delvick cache and cache

-rebooted

-stuck on bootloop
[SuperSU] Aakash Kaushal:
Never try to flash the supersu over the supersu,always uninstall the previous supersu while flashing the new one...so now reflash the latest supersu again in the recovery and if twrp/anyotherrecovery ask u to root your phone (during reboot) then select no..thatz it..u will get your root.
[SuperSU] dimebolt:
Hi all, thanks for the advic. Aakash Kaushal i will try your method and update again. Thanks once again.
[SuperSU] zain mansuri:
Hay,bro when i install new rom in my samsung gt i8262(galaxy core dous) my super user binary update faild and thats situation is not good please helo me .and give me solution plz.... :'(
[SuperSU] dimebolt:
Hi Aakash Kaushal, i uninstall the supersu using the uninstall function in the supersu setting. Then reflash 2.65 and got the error shown in pic (boot image). Please advice.
[SuperSU] :
Further I want to report that only supersu version BETA-SuperSU-v2.62-3-20151211162651 is working on my device. I tried 2.64 also.. in this case device booted but I got constant FCS and sim cards were also not working.

All the flashing of su i performed is on clean installed firmware to avoid conflicts caused by incomplete removal of su files.
[SuperSU] Ketawa:
Not true, more recent versions of SuperSU can be flashed over itself, but older versions have different requirements. This is from the closed WIP thread:

If you are coming from any SuperSU install in /system, you must re-flash the stock system (and vendor and oem, if present) partition contents prior to installing this.

If you are coming from a SuperSU 2.56 system-less install, you must re-flash the stock boot image prior to installing this.

If you are coming from a SuperSU 2.60 system-less install, or were not rooted at all, then you can just flash the ZIP without any special prior instructions.

Coming from 2.49, you need to flash a stock system image first. You might want to flash a stock boot image also just to be safe. Then install SuperSU 2.65. Also, I'm not sure SuperSU is compatible with your setup. If you have a custom kernel then it may not be able to patch it the boot image correctly. I'm not an expert on this though, so don't take my word for it.

[MENTION=631273]Chainfire[/MENTION] maybe the update instructions from the WIP thread should be included in this thread?
[SuperSU] :
Whoaaah I corroborate it too. I was die flashing stable version 2.65 supersu zip on clean installed stock firmware but everytime result was bootloop. I experimented more and got supersu 2.62 beta working for me. Then in tricky experimentation I flashed 2.65 stable supersu over it...and got the stable version working.
[SuperSU] dimebolt:
Hi Ketawa, thanks for your advice. I will try by flashing stock img and upate again.

Hi gauravrai: thanks for your info too. Might look into it if stock img fail.

Much appreciated!
[SuperSU] Heathered:
Hello, I have one question. Will stable version working with official CM13? Now using beta version, 2.67 and it works without any problem...
[SuperSU] Badger50:
2.67 is stable. He just hasn't changed the name. If it ain't broke....don't fix it. I'm running 2.67 on CM-13 AICP rom without issue :)
[SuperSU] fubo73:
It depends on specific phone. For S2, there seems to be a problem with ramdisk compression, so it does not install properly. Chainfire is aware of.
[SuperSU] Badger50:
S2!!! Holy cow! That's ancient! Time to upgrade bruh :)
[SuperSU] fubo73:
I have a S5. But S2 is there for testing and as work mobile phone. Its longevity is impressive! :)
[SuperSU] daniu:
Hi

That's ot but why? Because of the 2?

S3 mini is slower ... and we just received nightlys of cm13 - why scrap working hardware? I am not ashamed to say that my s2 is my only smartphone. When it refuses to work I'll get a new one not before that ...

Regards

Sent from my x-phone using brain 2.0
[SuperSU] Badger50:
Just a little humorous sarcasm my friend. No offense intended. Enjoy your day :)
[SuperSU] autry7:
My i777 just kicked the bucket so I got a Nexus 5. That phone was a beast though.
[SuperSU] hgmichna:
S2 too old?

I think the S2 is a good phone. It is similar to the Galaxy Nexus (GT-I9250), and see how well that has been holding up and is being upgraded with official CM 12.1 and soon even 13. Impressive! There are nice tricks like zRAM to get over the weaknesses of these phones.

But let's slip back into the topic. I hope SuperSU will work on older phones as well as new ones.
[SuperSU] tet-bundy:
Exact same issue. Without supersu installed it opens. (Cm built in root management)

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] magnamentis:
and philz as well would ask to root and the same applies, don't, say NO
[SuperSU] ofir_a:
Hi , I have a HTC One M8 sense edition after updating to Marshmallow.

I also have TWRP and unlocked bootloader

would I just need to flash the SuperSU STABLE v2.65 with TWRP to have it rooted?

Thanks in advance
[SuperSU] mauam:
Well been using su 2.56 for some time & today wanted to test 2.65, but give me some errors flashing through twrp, so I did that & now have su2.65 working flawlessly.

-extract su 2.65 apk from the zip

-using root explorer, go to system/app/SuperSU folder & delete su apk

-move the extracted su 2.65 apk to SuperSU folder & give permissions 0644

-reboot

-open su app, update binaries, reboot & voila.

Tested on cm12.1. Hope this can help someone:)
[SuperSU] zzenyoo:
If i install SuperSu2.65.zip with TWRP (previously installed by Odin) on non rooted device (GT-I9305), will i have root?
[SuperSU] L.F.B.:
Well, its 15 days and no playstore update, so I took the apk and intalled over 2.46 and everything went well!

So all good here, using in kk and LP like normal super su system app and all smooth! :)
[SuperSU] xunholyx:
Yes. That is how you root a phone. Unlock bootloader (if needed), flash TWRP, then flash SuperSU or a rooted ROM.
[SuperSU] Digitalesis:
v2.65 and also v2.67 beta with TWRP seems to soft brick Moto G XT1541 which has been OTAS updated Marshallow. UPDATE-unSU.zip enables device to boot again.
[SuperSU] :
V2.62-3 is working well. You can update to v2.65 flashing it over 2.62 without any bootloop.
[SuperSU] coolizard:
Really sorry if already answered (did the search). In my motoG 2015 with MM, the update doesn't detect the need for systemless properly, so it installs in system, causing bootloop. But install version 2.62-3 (systemless only) works perfect. Thanks!
[SuperSU] msquare:
sorry for the noob question, but I have SuperSU 2.67 installed on my OnePlus Two. I need to go back to 2.52 as its giving some bizarre problems with Viper4Android. How should I go about in order to do this?
[SuperSU] d3kod3:
Hi, i want to know which version of SuperSu works perfect with Android 6.0.X marshmallow but doesn't patch boot.img i.e. not a systemless root.
[SuperSU] 5m4r7ph0n36uru:
A little bit of reading through this thread and using the search function always does the job. It would have lead you to the information that v2.52 was the last one to install root on /system only, instead of /boot and /data ...

Link to the post would be this one: http://xdaforums.com/showthread.php?p=65292763

Send by the swarm intelligence of my coffee machine ?.
[SuperSU] d3kod3:
i was little aware of it but just confirming. i did a lil' searches on thread but maybe i was using wrong keywords. Anyways Thanks. :good:
[SuperSU] muratturatci:
Why Google Play version isn't updating anymore. XDA v2.65 - Google Play v2.46. Am i missing something [MENTION=631273]Chainfire[/MENTION] ?
[SuperSU] :
Maybe an incremental rollout? I have same thing.
[SuperSU] Ketawa:
SuperSU always requires a patched boot image on Marshmallow. See the first post from the WIP thread, where Chainfire posted modified boot images for version 2.52 system root. http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

However, those modified boot images are for older versions of Marshmallow that are out of date. If you use SuperSU 2.65, there is a way to force it to use system root, I think. This will still patch your boot image. Try this from adb in TWRP:

echo SYSTEMLESS=false>>/data/.supersu
[SuperSU] 5m4r7ph0n36uru:
My mistake .. already forgot about those again. Thanks for reminding me mate!

As I changed to systemless root as soon as it became possible I didn't think of this since then.

Send by the swarm intelligence of my coffee machine ?.
[SuperSU] tramp20:
Successfully updated from 2.46 to 2.65 over Google Play Store :)
[SuperSU] iwearthebelt:
Have a problem. After updating to 2.65 all of my devices file folders located in/storage/emulated/0 are missing. It says the directory is empty. Any ideas on how to fix this?
[SuperSU] L.F.B.:
Just got an update for super SU pro! 2.65 yeay!

Master Chainfire never fails!;)
[SuperSU] muratturatci:
Thanks for your fast response [MENTION=631273]Chainfire[/MENTION] :)
[SuperSU] Fif_:
I'm having a very similar issue.

I've traced it to some kind of namespace separation problem.

With 2.65 running on a Nexus 5 with 5.1.1 LMY48M, under terminal emulator:

su -c 'ls /sdcard/'

Fails, but if I use:

su -mm -c 'ls /sdcard/'

Then the contents of the sdcard show up.

With 2.46, both su commands above succeed.
[SuperSU] iwearthebelt:
I just went back to version 2.46 and my files reappeared. Same thing happened on my Galaxy S4 running KK 4.4.2 and my S3 LP 5.0.1 Guess I'll stay with the older SU until the problem is fixed or I move on to MM.
[SuperSU] Hagakurje:
Titanium Backup stop working after 2.65 update...

Note 4 rooted stock 5.1.1
[SuperSU] Skiner:
I have the same issue. Some apps cannot work with the root access.
[SuperSU] egingell:
Works fine for me. It must be something you're doing.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] rspkt:
2.65 update causes Titanium Backup bugs

I experienced the exact same issue as Hagakurje described after the 2.65 update on my OnePlus One running stock 5.1.1. Titanium backup would always claim insufficient free space (among other issues) when there was over 30GB free space on my devices designated storage. Reverted to 2.46 via TWRP and problem immediately solved.
[SuperSU] siltdotstrider:
Have found a Bug!

How I can submit a bug?

When some software asking for admin rights SuperSU window is appear where I can allow or deny root access. So if I choose allow and check checkbox ask me after 15 minutes (for example) then SuperSU asking me again if the software wants to do some more actions that do need admin rights. If I open SuperSU app I see that software on the list, but selected Ask but not Allow + Time! So that does mean that SuperSU will want user decision every time when software wants to do some admin actions! Of course if I choose corresponding option manually - everything is OK. So its 100% a bug.

I have SuperSU Pro 2.65 with pin code enabled. System MIUI.
[SuperSU] f231f:
Same here. 2.65 is broken. Reverted to 2.46 and all works again.
[SuperSU] Tzfardaya:
Open the supersu app, toggle "mount namespace separation" in settings and try again...
[SuperSU] f231f:
Upgraded back to 2.65 and the "mount namespace separation" setting was already checkmarked. I unchecked it, then rechecked it and rebooted. It's working now.

Not sure what happens during the 2.46->2.65 upgrade process, but at least in my case it wasn't properly migrating the settings.

Thanks for the tip!
[SuperSU] hgmichna:
Settings or no settings

I wonder whether there is absolutely no way for SuperSU to detect the required setting automatically.

I dislike settings. If you give users settings, they will set them wrong, myself included.