yashsingh1/xdaforums huggingface dataset:
[SuperSU] shaggyskunk:
SuperSU is almost certainly installed - Just because you don't see it in the App Drawer means nothing - Check in System Settings

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] robertogl:
Well, it works because I've root access, but it should be present in the app drawer...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] shaggyskunk:
Uh - No - it's not necessarily going to be in the App Drawer - Depends on how the Dev built the Rom - Sometimes you'll see it in the App Drawer - Sometimes in Settings - Sometimes in a Rom's custom interface...

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] robertogl:
Even if i flash the zip from Chainfire?

The true problem is that it doesn't ask the permission, it gives root access to every app...
[SuperSU] shaggyskunk:
Yes - Even if you flashed the zip... It's going to depend on how the Dev built the Rom.

Check in Settings (as I already mentioned) look for a Custom Menu (which Rom are you running?) look in Developer Options - You could also look in Root/System/Apps - Or - Root/Data/data for the apk

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] robertogl:
I'm using CyanogenMod 13. I've the superSU apk in /data/app/eu.chainfire.supersu-1 that is installed by the zip.

I've disabled root in Developer Options, so i'm using 'supersu root' (i know that because in this way i haven't the root symbol on status bar) but i can't find any menu.

P.S. Thanks for your help!
[SuperSU] shaggyskunk:
Well I suppose that you could always click on the SU Folder - Long Press on the apk - Select - Create a Shortcut... If you really wanted to...

As for disabling Root Access in Developer Options - I wouldn't - but it's your device....

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] dadykhoff:
First off, I think the OTA will fail since you have a modified boot.img. Secondly, if you were to manually flash the update, it would remove root since it would overwrite the boot.img where systemless root is obtained. If I were you I would manually flash the update, and use the opportunity to update to the latest SU :)

You can follow the steps found here if you've never manually flashed before: https://www.reddit.com/r/Android/comments/3vtfl7/android_marshmallow_601_factory_images/cxrs3ny
[SuperSU] robertogl:
Wait. What should that do? I mean, if i open that file it asks me to install SuperSU, and then it fails...

I have to. Using CM13 root access i can't do a lot of things. Don't ask me why, but for example 'reboot in recovery' doesn't work without SuperSU. It simply reboots... Probably it will be solved in future, but for now i need supersu.
[SuperSU] pkelly517:
As you've asked essentially the same question multiple times without a successful solution, maybe you should be asking in the CM thread.
[SuperSU] wilflare:
noob question but where can I check in TWRP if it's R/O or R/W?
[SuperSU] Ch3vr0n:
How about you ask that in the twrp thread, you're in the SuperSU thread.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] wilflare:
my bad. was following the discussion a couple of pages back where they were talking about the whole R/O R/W setting.

thanks nevertheless

EDIT: on a separate note,

updated to 2.66 from 2.65 without issue on my Nexus 6P 6.0.1

flashed via TWRP
[SuperSU] anakdayak:
Hi i'm on xperia z1 rooted 5.1.1 and on supersu2.46.My question is can i just flash the beta 2.52 ontop of 2.46?
[SuperSU] shaggyskunk:
Yes

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] anakdayak:
Several tnx hits.
[SuperSU] TMFGO45:
Previously I asked if Xposed would still prevent an OTA even if I used Systemless root with SuperSU. New question, can I uninstall Xposed, then take the OTA? Or will it still fail?
[SuperSU] KonoeKyon:
It will still fail since you modified /system.
[SuperSU] TMFGO45:
Thanks.
[SuperSU] CaliSoul1707:
I have this zip on my sd card, but I cannot install it to my device( RCA viking pro). I'm new to this, I cannot figure out how to update the binary. Please help
[SuperSU] drewski_1:
How are you trying to install? You need to flash in recovery
[SuperSU] ridobe:
Don't update the binaries from the app. Flash it in recovery.
[SuperSU] CaliSoul1707:
I tried to install in recovery. It says "install a booted and goes right back to recovery menu.

---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------

I tried to install from recovery mode from my SD card it says "install aborted" and goes right back to recovery menu.
[SuperSU] Bolumstar:
Is there any need to flash system less root on a custom Rom CM13 Based Rom on GT-N7100?

RR MM comes with supersu in the ROM likewise

Bliss pop v 6.0 only [MENTION=4610599]Ivan_Meler[/MENTION] CM13 comes without (supersu) in the ROM by default for the Note 2 Marshmallow.

Is there any special advantage of v 2.66 over v2.52 in terms of root management?

Which CF supersu version is best for GT-N7100 running CM based marshmallow?
[SuperSU] kaustubh_lipare:
Latest supersu 2.66 not working with moto g3 stock marshmallow.. Stuck at boot logo :(
[SuperSU] ashyx:
Custom recovery not stock.
[SuperSU] _insayn_:
If i may ask (short search in topic didn't find anything):

does: "adb shell wm density 380" (instead of 480) modify "system"?

will OTA work after?

thanks
[SuperSU] RG16:
Do I Have To Install Modified Boot.img Befor Flashing The Latest BETAsupersu build zip?
[SuperSU] spainter:
No. But if you have been rooted before you must have stock boot image flashed before flashing the 2.66 zip.
[SuperSU] RandomPooka:
Only if you want things to break. The newest releases of the flashable zip auto-patch your boot.img. No additional boot.img required.
[SuperSU] shaggyskunk:
I had no issues flashing 2.66 on a Rooted Note 3 running SlimLP - A Nexus 7 running CM based Rooted 6.01 mm and Flashed 2.65 on a Rooted Note 4 running CM based 6.01 (I flashed 2.65 on the Note 4 because I saw that someone lost their baseband flashing 2.66 and I was lazy) All with no issues other than having to uncheck Mount Namespace for tb
[SuperSU] _that:
No. /system is strictly read only in Android. (that's why it's called "ROM" :))
[SuperSU] _insayn_:
thanks mate.

can't stand 480 on n5 and always had to modify build.prop.

finally found a way ^^
[SuperSU] star314:
Hello!

I spent quite a lot time to reproduce the following bug. First, I flashed a fresh factory image of 6.0.1 (MMB29S) on my Nexus 6. Afterward, I wiped everything and performed a factory reset, just to be sure. At this stage, everything still works fine. However, if I flash the modified boot image, then several things around the battery notification start to get weird. In particular, the battery charge notification at the top of the screen shows something like 4136% which is quite unbelievable. ;) Moreover, in "Settings", the menu "Battery" - which is normally located between "Storage & USB" and "Memory" - disappears.

Did anyone else discover this problem?
[SuperSU] Ingenium13:
There is no modified boot image anymore. There hasn't been for over a month. Read the instructions for SuperSU, it's spelled out clearly what to do. There is no mention at all about flashing a modified boot image.

Sent from my Nexus 6P
[SuperSU] bunklung:
When I try to flash 2.66 TWRP reboots almost instantaneously with no error. Does anyone else have this problem?

I am using "echo SYSTEMLESS=true>>/data/.supersu" prior to flash.

N6 6.01/(MMB29S) Stock/encrypted w/TWRP 2.8.7.1

I used 2.62-3 instead and it worked flawlessly.
[SuperSU] Alxoom33:
Redownload 2.66 check md5.
[SuperSU] doomscooter:
Do yogi mean twrp 2.8.7.1???

I think in the official website twrp still in 2.8.7.0

Do you have link?
[SuperSU] asj0422:
question: how do we know when the supersu version is updated? i had to update my phone's software (n6p) and so had to reflash it anyway, so the only way i knew was because i manually checked before reflashing. also, how is the stable version (is there a stable version? where is it posted?) different from the regular beta systemless builds we're using now? is it not systemless? and are those stable builds updated via the app in the play store?

sorry for all the questions, thanks in advance for the answers.
[SuperSU] Profeta11:
hi guys, i'm on wiko fever, lollipop 5.1, supersu 2.52 beta and CWM as recovery. I followed this procedure to root http://xdaforums.com/showpost.php?p=63803008&postcount=5. All worked properly until 2-3 days ago, when the phone started to have problems with root with automated tasks (app like llama, timed toggle or simply the alarm not working and i have to reboot everytime). I want try to update the supersu with the 2.66, may i flash simply the zip with new version or i have to do something different? I'm losing between posts and i need help

if i can flash the updated zip, is correct the one i can find here? http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] yasars:
ok where can help me...

i have an HTC m8 with latest cyanogen mod 13 .. and i need supersu for Titanium Backup... after install supersu 2.66 , phone booting up all working fine, but after a reboot i became a boot loop an cyanogen bootlogo... i reflash supersu, wipe cache but nothing helped.... can anyone help me??

regards
[SuperSU] shoey63:
Assuming you are on MM

* Latest version is on the MM WIP thread.

* There is no stable version for MM roms, it's a WIP.

* You can't update on playstore for MM. It MUST be flashed in recovery.

* You need to be on stock MM boot.img before flashing latest version , or need to have flashed a previous version.

* If you are not on MM or Samsung LP 5.1.1, disregard the above and flash the stable 2.46 in recovery.
[SuperSU] magnamentis:
just a little hint as to how to be sure to have conventional root on latest SSU version without going through the terminal command procedure:

a) flash superSU 2.52, boot into system and install the apk from the 2.66 zip from a file browser that gives access to zip contents.

b) open superSU app and it will ask you to update binaries. choose "normal" hence not via recovery, wait till success, reboot and you will have 2.66 conventional root

EDIT: i know that not everyone needs that, it depends on the kernel and/or flashing order of course
[SuperSU] jcadduono:
Since SuperSU is unable to handle some stockbootimage.img, this is why I was asking for the option to perform operations on a pre-extracted ramdisk ex. /sutmp/ramdisk (not as a cpio archive) as my installer already picks apart the ramdisks and has support for all compression methods and rebuilding already. Can you explain why sukernel --patch requires boot.img? Why does sukernel have to operate on cpio archives instead of a folder?

This is not so much of an issue for me now, however, with the realization I can just extract supolicy and apply it to the sepolicy (is this necessary in system install?), then echo SYSTEMLESS=false > /system/.supersu and run the SuperSU installer zip.
[SuperSU] milojoseph:
My only problem is that on my s5 5.1.1 rom as some user had problems is when trying systemless it says abort after patch sepolicy.

Sent from my SM-G900T powered by AllianceROM

and boosted by speedy kernel

Lollipop ?
[SuperSU] Chainfire:
Misread you there. My understanding of your post was that you wanted to perform the operations on a decompressed ramdisk file, not a completely extracted archive. In this case I'd recommend using the sukernel commands on the repackaged cpio before the final (re)compression stage.

A hash of the stock boot image is stored at the end of init.rc to help identify the correct boot image backup to restore on unroot.

Because (again), supporting eight different platforms across dozens of Android versions across thousands of different devices is not as easy as it appears. Instead of finding, building and testing the right tools, I simply wrote my own, which is both significantly less work and more stable - that's not even mentioning the ZIP file size savings. I have no need to extract and rebuild the archive and all the extra edge cases that come with that, and thus it isn't implemented.

There is nothing stopping you from re-implementing all the changes that are done using a 'proper' cpio tool and whatever scripting you may need to add. sukernel tells you exactly what it does when you run the commands.

Whether applying supolicy to sepolicy is necessary on a system install depends on the firmware. On 6.0 it is, on Samsung 5.1 it is, older stuff it isn't. GENERALLY.
[SuperSU] garyd9:
(This references the samsung note5/edge+ devices)

I can't elaborate on it, but I can confirm it. It seems that once KNOX is tripped, those block devices will forever be mounted RO - regardless of which boot/system/recovery partitions are on the device. The end result, as you know, is that the cache flushes on standby fail, preventing deep sleep.

In addition, I've seen this same behavior on a device that was only ODIN flashed with a stock/signed samsung firmware (and therefore still had the KNOX fuse intact.) (That was a n920C device. The reports from others on this are mixed.) I'm unable to CONFIRM that the deep sleep issue on the "knox intact, purely stock firmware" is due to the failed cache flushes, and I no longer have the device. However, the symptoms are identical to the known issue.

On the knox-tripped, but otherwise completely stock firmware, I've been able to confirm (via the messages in the kernel log) that it's the same issue. (Kernel message is similar to: "[0: system_server: 3858] PM: Device 0:0:0:x failed to suspend: error -5")

It appears to me that samsung is a bit overly aggressive in marking those devices RO in the bootloader. I don't think there is anything you can do about it once the device has had KNOX tripped (without, of course, a custom boot image that works around the issue.)

Take care

Gary
[SuperSU] jcadduono:
Great thanks. As for your compression/decompression library issue:

I would go about it by taking the minimal cross-platform compressor/decompressor code from the latest Linux stable and making a few adjustments (ex. swap kmallocs out) to have it compile into one small binary which you can release sources for separate from your proprietary stuff, maintaining compatibility with GPL. (I think?)

PS if you do this I'm stealing it. Thought about it myself but haven't had the time.
[SuperSU] mielletseed:
Okay, I have this on a G928F device - knox tripped, rooted in systemless mode, no deep sleep. So what can I do know?
[SuperSU] Chainfire:
Yikes. Makes sense though.
[SuperSU] Chainfire:
Yeah, I'll probably end up doing something like that. It's either that or implement each separately. Either way, the end result has to be NDK buildable.
[SuperSU] garyd9:
Either flash a custom kernel (that fixes the issue), or if you are adventurous, read this post and follow the directions as well as you can: http://xdaforums.com/showpost.php?p=64658736&postcount=133 (this documents how to make 2.66 more compatible with the note5/edge+ devices in the short term.)

Note: As mentioned in that post, DO NOT DISTRIBUTE/POST the resulting changed archive. As well, being that you are already using a BETA concept, it's assumed that you have an idea what you're doing. The linked modifications are UNSUPPORTED and once you do them, do NOT bug Chainfire or this thread with anything that goes wrong.
[SuperSU] uramisten:
battery over 3000%

After flashing the newest 'stock' rom on nexus 5 (hammerhead-mmb29s), Whenever I flash this custom boot, my battery charge goes straight to over 3000% and the battery section disappears from the system config. I'm getting this without custom recovery or anything, just

flashing the modified boot image instead of, or after (tried both) the one in the new f/w.

Anyone else run into this, or can tell me what I'm doing wrong? :(:confused:

Thanks
[SuperSU] dbzgod:
Canadian Note 4 SM-N910W8

Firmware N910W8VLU1COK3

Not sure what is causing the signal/IMEI loss, my guess was maybe it had to do with your deep sleep patch? As there wasn't any deep sleep issues that I've seen before hand. But this is just a shot in the dark.

Uninstalling 2.66 and going back to 2.65 restored IMEI.

To rule out the patch, could you make a zip of 2.66 without the deep sleep fix and I could try it again to see if don't lose IMEI.
[SuperSU] Chainfire:
The deep sleep fix can be removed simply by removing /su/su.d/000000deepsleep with any file manager and rebooting
[SuperSU] bunklung:
That was it! Thanks. I could not locate the MD5, but downloaded it twice and compared the MD5 a few times.

I would like to mention that in 2.66,

echo SYSTEMLESS=true>>/data/.supersu

and

echo BINDSYSTEMXBIN=false>>/data/.supersu

still work. BINDSYSTEMXBIN saves you a step from later having to boot up, delete/rename su/xbin_bind, the rebooting again. SYSTEMLESS seems to be redundant for a stock Nexus device.

---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------

Shamu/N6 is 2.8.7.1

https://dl.twrp.me/shamu/
[SuperSU] dbzgod:
Sadly still no data/IMEI.

I recall in one of your posts talking about 2.66 having some kernel changes that custom kernel creators employ?

Something to note that I've seen in the Canadian threads that often custom kernels cause data loss problems for the Canadian devices and data fixes were needed. I was thinking that this might also be related to the issue.

Apologies if this is a bit vague, trying to help narrow down the problem.
[SuperSU] nixie2121:
quick question, im using share 2.62-3, all is well, any reason to flash more recent? thanks!
[SuperSU] Manuel15:
I had an idea that could be useful. Try to use an app to check the battery voltage and tell us if it's the same that appear as %
[SuperSU] GROGG88:
Sure. You're flashing an outdated boot.img for your current system.img. Follow directions in the WIP thread...
[SuperSU] uramisten:
Apparently with the new BETA-SuperSU, one should NOT use the custom boot image - it uses a systemless root. cool. All working now. Found a good howto here:

https://www.reddit.com/r/Nexus5/comments/3vvwl3/how_to_rooting_on_601/
[SuperSU] Ch3vr0n:
That 'don't use a custom boot' is nothing new, been the case for over a month now.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] bunklung:
I run stock/rooted/encrypted N6 and was using 2.62-3 without issues.

Then the January/monthly Google/Nexus security update hit and I updated to 2.66 without issue. I did have an issue with a corrupt download, but other than that all seems normal.

I *think* "echo BINDSYSTEMXBIN=false>>/data/.supersu" did NOT work for me in 2.62-3, but it certainly worked for 2.66.
[SuperSU] BigD14Tn:
Note 5

Any chance this will work to root the Verizon Note 5?
[SuperSU] Ch3vr0n:
Not on its own, no. You'll probably need 'flashfire'. Anyway this is the wrong place to ask. Check your device forum.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Rebel25:
Quick question. How to I remove SuperSU 2.66 systemless without having to redo everything on my phone?
[SuperSU] shoey63:
Do a full unroot from within the supersu app. Kernel and recovery will revert to pure stock.
[SuperSU] Rebel25:
Unfortunately when I did that my phone went into a bootloop. If I then reflash SuperSU 2.66 everything boots just fine.
[SuperSU] rubaboo:
Man, I knew this was gonna happen one day. Swiped in TWRP, instead of hitting "Do not install" button. Now recovering from bootloop. Good thing I backed up everything just prior.
[SuperSU] taszilo235:
2.66 and MMB29S problem

Hi,

I've just reflashed the whole (MMB29S) on my Nexus 5. Working well. I flashed TWRP (twrp-2.8.7.1-hammerhead.img) and then SuperSu 2.66. I have 2 applications where I tried to use it: Toggle Data 5.0 and busybox. For both of them I have problem. When I started the phone without su for example the Toggle widget was appeard immediately however without root error message is comming when I tried to press. After su installed some strange happens: widget is not shown on the home screen only after some minutes (more then 10) and not allways, sometimes I had to restart the phone. The functionality itself is not allways working. The same was true for BUsyBox. For example getting the first screen for busybox takes some time and the functionality was slow too. The popups which notify me that the app has already root permission was comming after some minutes and in big batches (I mean that many popup after each other), like it would have been in a queue and something would happen in the background and now it could be processed. After seems to be working well, but after a while again the same happens. Does anybody have the same behaviour, instability? Is there any solution or it is a bug?
[SuperSU] iw2ngg:
SuperSU Log problem

Hi.

This is my first post on XDA.

My problem:

SuperSU Log page is always empty on my device: never one single entry. This happens with any log configuration (even per-app setting).

Apps that require root privileges are still working well.

But... sometimes (about one time every two days) they _ALL_ (SuperSU app included) hang, at the same time, and remain waiting for an answer from su.

Then I need to reboot the system.

My configuration:

Nexus 5, stock Marshmallow 6.0.1 (recently clean-installed with google rom images), SuperSU 2.66 (systemless).

Thanks
[SuperSU] Gregorypac:
Hi [MENTION=631273]Chainfire[/MENTION]

I need your help , I did root in J2 and it worked, I'm trying to put Permissive kernel and can not ? , I use the version 2.66.

I used L Speed , http://xdaforums.com/andr...-2015-t3020138

I can not find CF Auto Root for J2

Sorry my English I from Brazil
[SuperSU] sansnil:
I feel like I'm going to do the same thing eventually...I hope TWRP gets updated soon so it doesn't show that option if systemless rooted.
[SuperSU] Naudiz:
Anyone else having trouble with logging in SuperSU 2.66?

I'm using it on a Nexus 7 2013 stock-Android with systemless install.

Inside the app the log window is always empty (I enabled full logging). I can see that all logs are saved in /data/data/eu.chainfire.supersu/logs, so the logging process itself works, it's just not shown inside the app...
[SuperSU] Calnyx:
Used 2.66, worked great on my S6, deep sleep bug did not occur as promised. But suddenly my root disappeared? Supersu says no su binary is installed. I checked and I still have /su/ and everything in that directory. Does anyone know what happened?

Edit: Nevermind, resolved by rebooting. I think this issue may have occurred when I cleared cache from the settings app.
[SuperSU] pkelly517:
How about that? I'm seeing the same thing! (maybe) N5X running PureNexus, full logging, systemless 2.66.

There are plenty of entries for logs in the LOGS tab, but tapping any of them gives a blank page with a big X and a couple arrows.

I added the (maybe) because I wasn't quite sure if your LOGS tab was empty, or you saw what I described.
[SuperSU] Naudiz:
Interesting...

For me the log tab is entirely empty, just stating "no logs available". Have you looked inside /data/data/eu.chainfire.supersu/logs as well?
[SuperSU] pkelly517:
Yup. Lots of text files. Lots of info in the text files ( I didn't look very closely, as I only really try to interpret logs when I'm seeing an issue). But nothing shows up when I click on the log in the SuperSU app, except for the Previous, Close and Next arrows/X on the bottom. I'm running PN by [MENTION=4395895]BeansTown106[/MENTION], so the SuperSU access is built into the firmware. I couldn't say if it's related. I clean flashed just a couple days ago.

I've got no Layers running, so it can't be a white on white issue..
[SuperSU] mrRobinson:
I stumbled upon this and am glad it exists; here. Enjoy.