yashsingh1/xdaforums huggingface dataset:
[SuperSU] KaMyKaSii:
Try to force the installation in systemless before installing zip, going on terminal with the command "echo SYSTEMLESS=true>>/data/.supersu"
[SuperSU] hyno111:
In my last install I see the log imply systemless mode, then some message about Boot image patcher, then some error about ramdisk is thrown..

Because of my stupidity, now I lost root/recovery/busybox on this device, so I can not test about it for now..
[SuperSU] nicolap8:
It would be usefull if someone (Chainfire?) writes a small app/script that can say if it's possible to install in systemless mode or not (and why not).

This can help a lot.
[SuperSU] evildog1:
SuperSu: Boot image not found

SuperSu 2.65 and 2.74 gives me "Boot image not found" error when i flash it over CM12 ROM. It makes SuperSu not functioning. It ask me to update the binary, but it fails to update normal and it does not request TWRP to flash it. Some peoples said it solves the problem when flashing SuperSu 2.67 and up but still getting "Boot image not found" error

My device is Samsung Galaxy S3 Mini running CM12 by Maclaw. I have reported the logs to ROM developer, too.

Link to ROM: http://xdaforums.com/galaxy-s3-mini/orig-development/rom-cyanogenmod-12-1-t3071937

TWRP logs: http://pastebin.com/5Ai5T3Wb
[SuperSU] rgavioli:
---------- Post added at 09:38 PM ---------- Previous post was at 09:35 PM ----------

Hi ktmon,

I haven't. Will find out how to do that and try it.

Thanks!
[SuperSU] ridobe:
Look back about 5 posts.
[SuperSU] BORETS24:
hi, i heard that possible to use systemless root without ramdisk modification, it's true or no? I ask because I try to get root access on Asus Zenfone 2 ZE551ML(CPU Intel Atom Z3580) with android 6.0.1 via temporary CWM recovery, SuperSU flashed successfully, but device have not unlock bootloader method for 6.0.1 yet therefore device can't start after SuperSU ramdisk modification. If return stock boot.img device started but have not root. have solutions?
[SuperSU] mielletseed:
Where did you hear that? AFAIK for systemless the boot image has to be altered. There are two main reasons: SE Linux has to be patched AND the path to the su binary must be found. So in my opinion there is no chance to get root without modifying system (system mode) or boot image (systemless mode).
[SuperSU] BORETS24:
1.I hear on 4pda in thread about Nexus.

2. I suppose, that if i try to get root on 6.0.1 by system mode I get boot loop?

3. Therefore in my case i have no chance to get root without unlock bootloader?
[SuperSU] cloud_strife84:
I have a French Lg G3 with official Marshmallow software 30c and if i root then radio fm doesn't work... Any solution?
[SuperSU] ktmom:
I have a N6 so no experience with your phone. I did a quick Google search though and it looks like fm radio functionality is carrier, kernel and ROM dependant. This thread is focused on the beta version of the SuperSU app. I'm thinking you'll get more help in a LG G3 forum.
[SuperSU] The Saint Kopite:
Hello.

I just did a TWRP recovery on my Redmi Note 3 to change its ROM to Cyanogen ROM.

I read that I had to install the add-on back-up script for it to work smoothly. Bot, how do we install the add-on back-up script? I just installed SuperSU on my Redmi Note 3 and everything seems to be working alright and it also shows that the phone has been rooted. But I didn't get the "Install the add-on back-up script option?" when I opened SuperSU. Any idea what to do next or how to add the add-on back-up script?

Thanks.
[SuperSU] Pkt_Lnt:
SuperSU > Settings > Custom ROM > Install SuperSU backup script
[SuperSU] usaff22:
Is anyone else getting random freezing with NP4 with SuperSU 2.74 installed in systemless mode? It was happening to me, did a complete wipe and started NP4 from scratch - there wasn't any freezing. Flashed SuperSU 2.74 last night and today I'm getting freezing.
[SuperSU] Ryya:
Have you tried the previous version if SuperSU in order to confirm that it's only v2.74 causing the issue?

SM-N920C (Note 5) - Dr Ketan Pro M rom - Xtreme Kernel - TWRP Recovery
[SuperSU] :
Yes.
[SuperSU] The Saint Kopite:
I am not getting that Custom ROM option.

Do, I need to install a Custom ROM first or is it necessary for me to upgrade it to PRO version for it to work?

Cheers.
[SuperSU] Pkt_Lnt:
Not sure, I have Pro, a pre-rooted ROM based on AOSP on a Nexus 6 and it shows for me. It is just there, so not sure what the requirement is, but I bet the OP on SuperSU stable or Chainfire's site will explain it for you.
[SuperSU] quanqw:
It don't work on latest touchwiz lollipop. I use touchwiz 5.1.1 baseband BE1.
[SuperSU] The Saint Kopite:
Hmmm.

Can anyone else help me out? :(

Cheers!
[SuperSU] Pkt_Lnt:
Get lazy much? ;)

Do you have CM installed?

http://xdaforums.com/showpost.php?p=23427715&postcount=1
[SuperSU] ktmom:
What doesn't work? The more specific you are, the more likely you will get help.
[SuperSU] The Saint Kopite:
Wait. I have to install CM to get that option?

FFS. No, I haven't installed CM.
[SuperSU] pkelly517:
Upgrade to pro.

Sheesh!
[SuperSU] osm0sis:
Good news! Finally got an email response from Stericson and /su/xbin should be the default for a systemless install location in the next release he makes (v50). :good:

Bye-bye busybox breakage complaints. Now someone just needs to make ES Explorer fix their ****. ;)

Edit: If anyone wants to clean up a mistaken /su/bin busybox install (since I doubt Stericson's installer will be smart enough to do that), my busybox installer zip is still the best option, of course. :)
[SuperSU] drewski_1:
I have Pro and don't have that option with Stock N.

May be only custom ROM option as stock won't use addon.d scripts.
[SuperSU] ayamgoreng:
just wondering if I the only one experience script (v4e policy) in the su.d not executed during boot with 2.74 ?

I use custom rom (erobot) that has 2.74 bundled in if it matter.

Installing 2.65 always fix the problem.

Thank you
[SuperSU] Ch3vr0n:
[MENTION=4544860]osm0sis[/MENTION] I mailed him about that again a few days ago too.
[SuperSU] ratson:
yeah, same for me, like 4-5 freezes/day, seems like some memory management issue
[SuperSU] ktmom:
If you submit logs maybe the problem could be resolved.
[SuperSU] ratson:
I have already reverted to dp3...
[SuperSU] ratson:
now I am not sure this is SuperSU related, posted a new xda thread and an android bug report. Please join if you experience the same with DP4.
[SuperSU] kylepsp:
Yea I was getting the same on dp3, wasn't sure if it was SuperSu or adaway but something was slowing my phone down to a crawl constantly
[SuperSU] ratson:
How did you solve it? I try to disable adaway now and see if it makes a difference...
[SuperSU] quanqw:
No. My rom has error.
[SuperSU] kylepsp:
I couldnt solve it, tried factory resetting a few times, a complete reinstall, still happened. Only way I could fix it was a clean install and not rooting or installing adaway. Let us know if just disabling adaway fixes the problem!
[SuperSU] ratson:
Unfortunately not, I had to revert to dp3...
[SuperSU] Alxoom33:
Haven't had any troubles on my Nexus 6 or Pixel C. Both rooted, debloated and set up nicely.
[SuperSU] farunkel:
can't make supersu work

I have LG G3 with Marshmallow. I used KingRoot to root according to instructions here http://www.droidviews.com/root-lg-g3-d855-stock-android-6-0-marshmallow/ (using KingRoot, then installing TWRP, then Hacer Permisivo and finally supersu 2.65 from 2015)

I ran into some snags getting into recovery, maybe that has to do with it. Once I was there I installed the SuperSU zip linked in the article but after reboot I can't see it in the apps. I then tried to install 2.65 from another place as well as 2.67 and 2.74, but can't see it in the app. Tried to download from the market, but clicking on the option to install in twrp doesn't work. And indeed, root checker shows I don't have root.

What did I do wrong?

---------- Post added at 09:08 AM ---------- Previous post was at 08:19 AM ----------

I installed KingRoot again and now I have root, seems to stay after reboot. Still can't see SuperSU though.
[SuperSU] souvikpal:
Some apps can't detect root in v2.74 (like ES file manager, System app uninstaller etc). But all were working fine with v2.65.

Android version 5.1.1
[SuperSU] ianmacd:
This is a FAQ. It's because you installed systemless SuperSU. Search the thread for compatibility mode.
[SuperSU] Mr.Yawnie:
You can open SuperSU by typing "*#*#1234#*#*" in dialer.
[SuperSU] corkiejp:
Now available and working.

Edit: In the Pro version anyway (Currently on Sale).
[SuperSU] farunkel:
this does nothing
[SuperSU] kylepsp:
I installed root again on my 6p running N, the slowdowns pretty much started straight away and persisted for a day, making the phone unusable at times until a hard restart. Uninstalling root through SuperSU fixed the problem immediately!

SO root isn't playing nice with the 6p running dp4 of the N preview! Also occurred for dp3!
[SuperSU] Mr.Yawnie:
Did you try it without quotation marks? Try this out

*#*#7873778#*#* (*#*#SUPERSU#*#*)
[SuperSU] ratson:
Can you provide logs please? It would help in development...
[SuperSU] usaff22:
Neither the thread nor the bug report disprove that it is SuperSU/root related. [MENTION=3637238]kylepsp[/MENTION]'s findings seem to further confirm my own.
[SuperSU] ratson:
sure it can be. the question is if we can find a reliable way to reproduce it or provide logs to let [MENTION=631273]Chainfire[/MENTION] inspect it
[SuperSU] kylepsp:
Sorry I'm away from my PC so can't reinstall root. I'm beginning to think the problem may be adaway. I was running for a while yesterday with just root and it seemed ok. Can anyone else collaborate this?
[SuperSU] Ch3vr0n:
You think wrong. Adaway works just fine
[SuperSU] NLBeev:
Just installed Adaway. A long list of url's that will be blocked are added to the 'hosts' file.

The app itself needs root acces to change that hosts file.

When the app Adaway is killed or uninstalled the blocking will go on for all the url's listed and redirected to 127.0.0.1; the default internal ip-number.
[SuperSU] Ch3vr0n:
And your point is? It works just fine requesting su access.
[SuperSU] NLBeev:
Sorry wrong QUOTE.

I wanted to inform [MENTION=3637238]kylepsp[/MENTION], so he may conclude that probably Adaway has nothing to do with the problem he wrote about.
[SuperSU] JulGer01:
Does exactly what its supposed to do...
[SuperSU] OhayouBaka:
Hey Chainfire, just a suggestion for SuperSU.

Can you include an option for users to be able to choose from System or Systemless root (due to systemless root being a bit unreliable for some)? Like in the SuperSU app, or an AROMA installer, or heck just give us seperate ZIPs.
[SuperSU] pinnockio:
Supersu hangs

Hey everybody (and Chainfire if he's reading),

After some time without rebooting the phone (1,5 - 2 days), Supersu doesn't respond anymore and opening the Supersu app, the tab with the apps granted permissions keep loading forever. I haven't been able to find a related logcat :(. Some other people have mentioned the same problem on this forum ... . Does anybody has a suggestion?

I'm on a stock Sony Xperia z3 Compact MM6.0.1 rom with no major custimizations to the kernel and Supersu 2.74 installed ... .

Kind regards.
[SuperSU] grep_i:
Did you unlock bootloader and how ?

How did you install Supersu ?

What do you mean with a stock rom with no major customizations to the kernel, is it stock or not ?

Have you tried reinstalling Supersu ?

Are you saying that in a full logcat you can't find to see an error regarding the Supersu app ?
[SuperSU] Aria.A97:
Does anyone knows what is this "Catch Me If You Can" thing? :confused: I never grant unknown SuperSU requests...
[SuperSU] Spannaa:
A quick Google shows that catch_.me_.if_.you_.can_ is the package name for GameGuardian - an app for hacking and cheating in games!
[SuperSU] Aria.A97:
Thanks for clarification, Titanium Backup shows com.machinezone.gw for GameGaurdian name :|

I already Googled but it seems like we are using different versions of Google :laugh:
[SuperSU] Spannaa:
I probably used more specific search terms ;)

Re: The package name, apparently they changed it to avoid detection but, as you'd already given it root privileges, it still shows in SuperSU > apps

Enough OT ;)
[SuperSU] pinnockio:
Supersu hangs

Hi mr. Grep_i,

First of all thanks for your reply!

Bootloader unlocked when I was on Lollipop.

Installed Supersu as Zip using TWRP 3.0.2.

I installed the original MM-image from Sony. But I compiled the kernel myself from the developer-sources that are also available from Sony because I needed a minor change in a config file (all the rest are the untouched presets loaded from the Sony-kernel-config file). So no weird kernel-schizzle for custom schedulers etc.

Of course I tried reinstalling Supersu :).

And yes I don't find an error in the logcat of the Supersu app.

Kind regards.
[SuperSU] shoey63:
Your bootloader is obviously unlocked, and you have TWRP flashed to the FOTAKernel/recovery partition. You shouldn't be able to install supersu 2.74 on a stock kernel (Sony elf format is not supported), Or are you on the "concept" rom?
[SuperSU] danilo_scala:
thanks for share friend, all app ok, but es file explorer i can not enable root (permission), show i no rooted
[SuperSU] NLBeev:
ES Explorer is a known issue; use another explorer (RootExplorer).
[SuperSU] danilo_scala:
ok, thanks help [MENTION=528201]NLBeev[/MENTION], try too solid explorer
[SuperSU] pinnockio:
Hey Shoey,

Thanks for the reply! Well, now you're talking about it, I do remember I first installed a custom rom, but wasn't happy with it. Can't seem to remember which one though :). But I remember I extracted its boot image afterwards and used that boot-images ram-file to repack it to a new boot.img with the custom kernel from the developer sources from Sony I compiled myself (with some minor changes to have 27Mhz-frequency for the GPU).

I installed a MM firmware using Flashtool on windows and afterwards I flashed that boot.img I describe above. I don't know the ins and outs of the fotakernel etc. .

But do you think it is relevant to why after some time, the SU seems to hang? To me it seems like there is some kind of deadlock or that the SU-process (or any other related process to make root work) gets dozed by MM and doesn't wake up correctly ... .

Kind regards and looking forward to your answers!
[SuperSU] Fif_:
Memory leak in SuperSU daemon?

I'm seeing a daemonsu:master process eating lots of memory.

This is happening on a:

Nexus 5X

Running Omni 6.0.1 2016-06-18

SuperSU 2.74-2, flashed with TWRP 3.0.2

My symptoms is that after a random amount of time, one of the SuperSU processes starts eating at the RAM.

# /system/bin/ps l daemonsu:master
USER PID PPID VSIZE RSS WCHAN PC NAME
root 5017 1 2980304 128696 __skb_recv 7f9a3f11a4 S daemonsu:master

Look at the VSIZE (Virtual Memory Size) of that process. That's 2.9 GB.

One hour earlier, that figure was as 2.4GB.

Just after boot, VSIZE is a few megabytes.

Anyone seeing this?
[SuperSU] iotse:
Ty
[SuperSU] vecino:
Hi all, please I have one bank aplication which can´t run if I have enable SuperSU = "root device". Is working after disable Superuser in settings but if I enable superuser again SuperSU: "instalation failed". I have to flash supersu again via twrp. Any tips? My curent ROM is dirty unicorns 6.0.1 . Thanks
[SuperSU] shoey63:
Well, your self compiled kernel may have minimal changes, but it is a custom kernel nonetheless. It may or may not be the cause of the issue. Especially since you used the ramdisk of yet another custom kernel.

Try the advanced stock kernel for your device by [MENTION=4102242]Gustavo RD78[/MENTION] and see if you fare any better.
[SuperSU] ratson:
It is virtual size, doesn't really matter... what you shall look at is RSS and it is normal I guess
[SuperSU] JudgeDread11:
A storage zip does already exist.

http://xdaforums.com/showthread.php?t=3286120
[SuperSU] Surge1223:
Chainfire, I'm hoping you'll answer this, as it will probs save quite a few of us from getting similar questions, not to mention you as well.

With systemless root, do you force corrupt cache so e2fsck forces a remount?

Another question, when you live patch fstab and sepolicy, is it determinisitcially done? That is do you add Permissive contexts based on what is present currently, or what you think will be needed for the device in general?

The reason I ask, is because I made a modification to flash rom + systemless su zip in zip, but it seems the vendor partition isn't mounted by your zip, so what ended up happening is that the contexts for imsdameon and by extention netd and all the rild libs that live in vendor (but are symlinked to system/vendor) didnt end up getting the the right contexts defined by sepolicy, so I had to just restorecon and fix perms on a few things in vendor dir.

I can't believe I'm saying this, but normally I wouldn't care, but every single themer and layers user is about to have a meltdown if this modification we made the PureNexus ROM gets popular.

I should note, that the errors this causes are Nfc and systemui fc's, and it's attributed to selinux error for fd not able to open dirs, and netd errors pretty much always kills boot anyways, and usually is caused by rmt_storage not being able to call functions from libqmi(because it lives in vendor/lib,)

So I tried a bunch of things and fixed all the issues, I'm just not sure what caused the fix, if you could help narrow it down that'd be awesome.

TL;DR

A) Essentially flashing a systemless root after everything = always success

B) Flashing systemless su with rom, then flashing gapps and vendor = 50/50 success

Is there anything you could help she'd light on for the discrepancy?

Thanks mate. I'm about to lose my mind if one more person asks me why layers doesnt work lol.

I have a feeling gapps zip is likely a culprit, but I was able to fix my issues with simply using restorecon.
[SuperSU] pinnockio:
Hey mr. Shoey,

I think it could have been that rom :). But it didn't support the 27Mhz mode I think.

For now, I'm going to stick with the occasional reboot every 1-2 days.

Thanks for the answers!
[SuperSU] Fif_:
Confirmed memory leak in SuperSU 2.74-2

I think you are guessing wrong ;)

After further analysis, it looks like SuperSU 2.74-2 leaks 20kiB of heap or so every time the "su" command is invoked.

Maybe [MENTION=631273]Chainfire[/MENTION] can take a look at this...

Proof:

# /system/bin/ps l daemonsu:master
USER PID PPID VSIZE RSS WCHAN PC NAME
root 2055 1 184436 7396 __skb_recv b6eaf850 S daemonsu:master
# su -c true
# /system/bin/ps l daemonsu:master
USER PID PPID VSIZE RSS WCHAN PC NAME
root 2055 1 185456 7732 __skb_recv b6eaf850 S daemonsu:master

Every single time su is ran, the VSIZE gets bumped by 20kiB. And this is real memory...

Further proof: (pid 2055 is the PID of the daemonsu:master process)

# cp /proc/2055/maps .
# diff maps /proc/2055/maps
# su -c true
# diff maps /proc/2055/maps
--- maps
+++ /proc/2055/maps
@@ -1,3 +1,5 @@
+ab834000-ab835000 ---p 00000000 00:00 0
+ab835000-ab933000 rw-p 00000000 00:00 0
ab933000-ab934000 ---p 00000000 00:00 0
ab934000-aba32000 rw-p 00000000 00:00 0
aba32000-aba33000 ---p 00000000 00:00 0

Every time su is ran, a new chunk of memory is eaten by daemonsu:master.

I can see this behavior on a bunch of different devices as well: Nexus 5, 5X, 10.

I have lots of su'ing happening on my devices and this is killing my devices after a few days.

If I run:

while su -c true; do true; done

the phone will die in minutes.
[SuperSU] Chainfire:
Eh... no?

It is deterministic in the sence that the same source sepolicy from the stock boot image will always create the same output sepolicy in the patched boot image, regardless of any other files present on the device.

I have no idea what is going on here. The patcher does not care about or look at vendor.

What is it that you have done?

At this point I have no idea where to even look.

It's weird, flashing gapps and/or vendor should have no effect on sepolicy at all, unless I'm missing something.

Well, the interesting part there is, if restorecon fixes the problem, then the problem is _probably_ not sepolicy itself.

...

I'm pretty beat right now so perhaps I'm overlooking something that should be obvious, but it all sounds rather strange to me.
[SuperSU] Chainfire:
I am investigating this.
[SuperSU] boomop:
[MENTION=631273]Chainfire[/MENTION]:

Can't find a checksum for the download...
[SuperSU] ratson:
There is the topic of freezes on dp4 when ram runs out, I could solve it by raising minfree values, many said that this doesn't happen without su so maybe there is some correlation... [MENTION=631273]Chainfire[/MENTION] add this to the list of memory related issues
[SuperSU] shoey63:
You don't need it. Just enable zip signature verification before you flash. If it succeeds, the integrity of the zip is sound.
[SuperSU] RandomPooka:
Nice! Never knew that one
[SuperSU] gothy.gothy:
Hi guys,

Where is the 2.75? I found it on Playstore, but ... not here.

Thanks
[SuperSU] ulxerker:
on google play there is only 2.65 as far as I can see, not 2.75.
[SuperSU] Darke5tShad0w:
2.65 is the latest on the playstore and the latest in the stable thread.

Beta's are never released on the playstore.
[SuperSU] ulxerker:
also, the latest beta is 2.74-2, not 2.75.
[SuperSU] Darke5tShad0w:
I am already aware of that or did you not mean to quote me but [MENTION=5266159]gothy.gothy[/MENTION]?
[SuperSU] ulxerker:
my post was meant to be an additional answer for gothy.gothy, sorry for the confusion. :)
[SuperSU] valkyrjur:
Aptoide shows a newer versión than here, 2.75, but 100% sure is a fake versión.
[SuperSU] gothy.gothy:
Sorry, guys, in the Playstore there is only 2.65, you are right.
[SuperSU] catalyst05:
I think 2.75 is out . Flash this

https://dailyuploads.net/k720huyhpm73
[SuperSU] anttaz:
I nhave seen SuperSU 7.5 all over the web
[SuperSU] ulxerker:
for security reasons I'd wait for an official announcement by chainfire.
[SuperSU] Ch3vr0n:
Me too. Unless it's on XDA by cf himself or through play store I'm not taking it. Too much can go wrong with root access if the wrong app gets it (visible or hidden).
[SuperSU] haseoxth:
I also seen 2.75 version in a local app store, but I won't install it and also a suggestion to other users. I never seen Chainfire release a new version without update this thread before.
[SuperSU] MigoMujahid:
So i'm wondering, if supersu isn't supported in the S2 devices with cm13 because of the compression type of the ram-disk, then how some new s2 cm13 based roms comes pre-rooted using latest stable supersu?!, is there any way around this?! ????
[SuperSU] ldeveraux:
Latest beta always shows up on aptoide about a week before chainfire releases it on xda. He probably adds it to his release schedule which would explain why it appears there.
[SuperSU] Alxoom33:
I wouldn't flash it, unless released by [MENTION=631273]Chainfire[/MENTION] on this thread! You are asking for problems.
[SuperSU] _that:
Because it's the installer that doesn't support repacking the ramdisk. Workaround is to inject the SuperSU files into the ramdisk by other means.
[SuperSU] Archon810:
Guys, I just talked to Chainfire, and he hasn't released this 2.75 APK. He's looking into what's going on within the next couple of hours, and then we'll hopefully know more.

In the meantime, DO NOT INSTALL the 2.75 APK floating around.

It's also suspiciously 1MB lower than the previous releases, which was the initial red flag for me.

I hope the key wasn't compromised...
[SuperSU] anagramgenius:
It's strange that the signature SHA1 of v2.75 matches with v2.74.
[SuperSU] Archon810:
Yup, that's the worrisome bit.
[SuperSU] MigoMujahid:
Thanks for the reply, so will it be possible that one day the installer would support the repacking of the ramdisk? ????, you know we miss supersu in cm13....there must be a solution..you know ????

Who knows, we maybe get cm14 one day, and it could have the same problem...