yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ryuuga:
Okay someone help me on this.

I'm running CM12.1 trying to get this systemless+suhide thing to run but I guess it doesn't work on 5.1.1??

I've removed every trace of supersu and then ran the terminal echo code. But when i flash supersu, it still says "install in system mode"

And then when i flash suhide, it says "error not in systemless" etc.

Secondly, If I were to return to stock 6.0> flash systemless+suhide and then > flash custom ROM (CM13) wouldn't it remove systemless altogether since CM has supersu built in??

Running specifically sultanxda's CM12.1 build on OPO. Please send help. I've done a fair share of searching...
[SuperSU] Tsukiyohikage:
I have the same problem.
[SuperSU] corkiejp:
[MENTION=2887582]Ryuuga[/MENTION] [MENTION=5234988]Tsukiyohikage[/MENTION]

Systemless SuperSU only works on marshmallow or latter. You can not have systemless on Lollipop. Except Samsung devices.
[SuperSU] Tsukiyohikage:
I am on 6+,i just meant I just can't get it to install into systemless mode. I've done the echo "systemless=true">/data/supersu

But when I goto install it, it says system mode.
[SuperSU] corkiejp:
You left out a ".", was it just a typo here? Or did you forget on your device as well.

The command should be : -

echo "SYSTEMLESS=true">>/data/.supersu

You need to also remove all traces of system supersu first before flashing systemless.

Edit: forgot the "s
[SuperSU] grep_i:
The command is:

echo "SYSTEMLESS=true" > /data/.supersu
[SuperSU] Tsukiyohikage:
​

Forgot the. On the pogo reddit that is how they had it typed out, I will try it out and let you know if it works.
[SuperSU] corkiejp:
Thanks for the correction, I left out quotes in my post. (Copied from another earlier post). Now edited.

> creates and overwrites the file if it is already there.

>> appends to the file if already there or creates it.

Use >> if you are issuing other commands like compatibility mode.
[SuperSU] Captain_Throwback:
Safer to just always use >>, imo.

And the quotes aren't needed, as there aren't any spaces in the command (but I suppose it's safer to just use those, too).
[SuperSU] grep_i:
You're right it appends but than it does not change the setting as needed if there's already noted systemmode I want to install systemless it appends this option but the installer only reads the first option, so nothing changes.

That's why one > is preferred.

To be sure I have tested this a minute ago I have the first three lines in /data/.supersu like

SYSTEMLESS=true
SYSTEMLESS=true
SYSTEMLESS=true

I have appended it with your recommendation for systemmode:

echo "SYSTEMLESS=false" >>/data/.supersu

Now file looks like:

SYSTEMLESS=true
SYSTEMLESS=true
SYSTEMLESS=true
SYSTEMLESS=false

Now when I flash supersu it still installs in systemless.

But when I follow my own recommendation to change modes:

echo "SYSTEMLESS=false" > /data/.supersu

Now file looks like:

SYSTEMLESS=false

Now when I flashed it installs in systemmode.
[SuperSU] osm0sis:
Easiest thing for people not familiar with shell or the contents of their .supersu file is to edit it with a file explorer like FX.
[SuperSU] Captain_Throwback:
I like to use nano in TWRP to edit it ;). Thanks for that zip, btw :).
[SuperSU] grep_i:
Luckily I am experienced enough to handle this without file explorer and just using "vi" and basic shell commands from busybox. :cool:
[SuperSU] vt0r:
[IMG="HACKERMAN"]http://i.imgur.com/Hfzf14T.gif[/IMG]
[SuperSU] KaMyKaSii:
Someone with knowledge can confirm the following: BOOTIMAGE is the path to boot partition and STOCKBOOTIMAGE is to make installer patch boot.img of some previous backup and then install on path of BOOTIMAGE?
[SuperSU] Tsukiyohikage:
Thanks for the help guys. I got it to work, I didn't capitalize systemless, once I did it worked.
[SuperSU] Radit26:
how do I flash this systemlessly?
[SuperSU] Pkt_Lnt:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Read UP ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[SuperSU] Radit26:
Alright I see the command, but how do I know if I successfully flashed it systemlesslly?
[SuperSU] Captain_Throwback:
What did the recovery output say? It'll tell you if it installed systemlessly.
[SuperSU] androidfr33k:
Quick question. With the new naming scheme is 2.78 SR1 later than 2.78?

Here is what I found:

SR1-SuperSU-v2.78-SR1-20160915123031.zip

SuperSU-v2.78-201609011115.zip

Maybe the second one is not the new naming scheme and older than SR1?
[SuperSU] corkiejp:
If you looked at the changelogs, linked in the first post, you would see SR1 is newer!
[SuperSU] androidfr33k:
My fault thanks!!
[SuperSU] KevTN:
Did a clean install of PN N today. Everything flashed without a hitch except SR1 SU it said the file was corrupt. My question is this...can I just flash another SR file.. Or is there something else I need to do
[SuperSU] mobileman88:
What terminal app do you use? I am using mobile terminal and it sometimes does not behave properly. Simply fc

---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------

Did you check the file hash?
[SuperSU] KevTN:
Redownloaded and worked like a charm thanks
[SuperSU] grep_i:
terminal emulator for android no issues with fc.

But I prefer using this by using:

adb shell

from my Linux box so I can use normal computer keyboard.
[SuperSU] grep_i:
When booted up to system you should have an folder

/su

Or open SuperSU app and find the following, see screenshot:

Mind the greyed out area

View attachment 3902144
[SuperSU] RandomPooka:
To save trouble entering commands manually in the craptastic terminal emulator in TWRP, why not just create the file on your PC, copy it to your SDcard, and then use the TWRP file manager to copy it to /data after a wipe and before flashing SuperSU? It takes just a few taps and a confirmation swipe to accomplish, and there is ZERO chance for a typo ruining your day.

-- edit --

To be fair, the term in TWRP isn't actually any worse than any other term app. It's just really annoying to try to remember where all the special characters live in the keyboard layout that's provided in TWRP
[SuperSU] grep_i:
I'm using a Linux box so it's pretty easy to use (you must have installed "android-tools" package.

adb shell
su
echo "SYSTEMLESS=true" > /data/.supersu

Probably from Windows it's the same open command line with Android tools or SDK installed.

and do the above

And you can easily type the command to me that's easier than creating a file copying it to sdcard and in TWRP to

/data

Also this you can accomplish with

adb push "local filename" to "sdcard location on Android device"

Example:

adb push .supersu /sdcard/
adb shell
su
mv /sdcard/.supersu /data/
[SuperSU] mobileman88:
ADB works for me, but without terminal emulation in the command window, it's a little hard to use "vi" or any other text editor. Seems only way I get a proper terminal is using the terminal app or running a "sshd" on my android device. Would be great if my vi works without all the ASCII/ANSI characters going all over the place.
[SuperSU] ulxerker:
or you just have a look in the SuperSu app at settings -> system, there you can see the status, too.
[SuperSU] KyeWalker:
Safety Net Fail

Latest safety net fails, using SuperSu and Hides (whatever way round it is lol) using both stable and beta versions of SuperSu
[SuperSU] nyknight77:
Same here
[SuperSU] RandomPooka:
If my micro USB port wasn't unreliable, I'd probably do it that way as well. As it is, I have trouble using the cable connection to the PC, so I need to do most everything via the phone.

I will occasionally be able to get a good connection through the cable, and then I can use adb in recovery or fastboot. But, I can't count on it always being easy or fun
[SuperSU] Ch3vr0n:
That's because Safety net got updated again

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] grep_i:
I have no clue what you are talking about, the VI included with busybox is so minimalistic that what you are telling could not even happen with it.:confused:

I am sure it never happened to me because it would irritate the hell out of me.:mad:

I guess you are referring to VI on pc or server, they tend to act that way if you do not install "vim" and "vim-extras":victory:
[SuperSU] Radit26:
thanks for the replies, I looked at the SuperSU app settings and it says it's systemless
[SuperSU] benleonheart:
Probably late to the party packed with a powerfully stupid question, does 2.78-SR1 flash systemlessly by default via TWRP?

Thanks!
[SuperSU] egingell:
Phone and ROM dependent.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] mobileman88:
What I meant was there's no terminal emulation when using "vi" over ADB in Windows so I can't navigate around properly compared to using an "xterm". That's why it's irritating as hell to me.

Without terminal emulation, when I do a "busybox vi" I get

----

angler:/data/local # ./busybox vi

[?1049h[1;1H[J[2;1H~[3;1H~[4;1H~[5;1H~[6;1H~[7;1H~[8;1H~[9;1H~[10;1H

~[11;1H~[12;1H~[13;1H~[14;1H~[15;1H~[16;1H~[17;1H~[18;1H~[19;1H~[20;1H

~[21;1H~[22;1H~[23;1H~[24;1H~[1;1H[25;1H[K- No file 1/1 100%[1;1H

--

---------- Post added at 08:53 AM ---------- Previous post was at 08:36 AM ----------

Found a workaround for it. Had to use busybox vi in a Cygwin shell, that works. However my current working directory is not shown
[SuperSU] grep_i:
Great you found a workaround.

I did not know you could use vi the way you did.

As far as I know you can use vi directly without typing busybox, so the command to use it would be (even under windows) the payload would be on the android device and not on your windows box:

adb shell
su
vi

Maybe that's why it is working that strange because you are using the command "busybox" with parameters "vi"
[SuperSU] mobileman88:
Yup, it works as I did not symlinked the vi to busybox so all the busybox related commands have to be prepended with "busybox " before the actual command. Just need to solve the current working directory not being shown when using adb inside of Cygwin and I am all set. Thanks again for your inputs on this.
[SuperSU] _that:
Fixes for getting ANSI escape sequence support on Windows:

* Use https://conemu.github.io/

* Or use a recent version of Windows 10
[SuperSU] mobileman88:
Wow... this is really great stuff! Thanks !
[SuperSU] dazzlerdevil:
Hi, After trying all the ways to make my sim work with rooted stock rom i failed but as i told that i rooted it successfully so I flashed this custom rom http://xdaforums.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600 and with this rom everything is working except miracasting, yeah thats my only problem is now even though i have added ' persist.debug.wfd.enable=1 ' into the build.prop, However it has enabled the option to enable the wireless display but my lg smart tv disconnects with in 2 secs...
[SuperSU] :
i flashed this on HTC M9 running Marshmallow device its stuck at boot any solution for that ?
[SuperSU] gc_geforce:
I was able to install supersu as systemless root, but I had to uninstall root to test something and then now I cannot get supersu to install as systemless using the echo "SYSTEMLESS=true" > /data/.supersu am I missing something? it keeps installing as system mode.
[SuperSU] grep_i:
That's why I didn't have the problem than, the only windows I've tried on is windows 10 preview developer build.

That stuff is still not available as a daily driver for Windows 10

Are you sure the file gets even created at all ?

Did you check that ?
[SuperSU] Captain_Throwback:
You have to flash v2.65 on the M9. See the M9 TWRP thread FAQ.
[SuperSU] :
flashed this but still same
[SuperSU] Captain_Throwback:
Then your problem probably isn't related to SuperSU. You should start over.
[SuperSU] gc_geforce:
Yes I checked to make sure the file was created.
[SuperSU] :
downloading the stock RUU from HTC's official site :( :( :(
[SuperSU] grep_i:
Can you tell what the content of the file is, please ?
[SuperSU] gc_geforce:
This is what is in .supersu, SYSTEMLESS=True
[SuperSU] grep_i:
I'm not 100% sure but it could be that it is case sensitive and the content must be really:

SYSTEMLESS=true

Please try that and report back what happens.
[SuperSU] mihir85:
Please help. Supersu works on first reboot but doesnt stick on next reboot. Flashing the zip doesnt work either. Root checker shows phone is rooted. Im on custom ROM on S7-G930F.
[SuperSU] gc_geforce:
I will try this later and report my results, thanks

---------- Post added at 07:39 PM ---------- Previous post was at 06:52 PM ----------

Thank you for the help, that was the problem, the "true" has to be all lower case.

:good:
[SuperSU] nadejo:
Can someone help me? I red trough the whole thread but still couldnt Figuren out how to make root work systemless with data on f2fs using Nougat. Ive tried the terminal Command and also doing that unsu.ZIP before and mounting system and stuff still su APP telling no root and after reboot the APP uninstalls itself. Im in oneplus3 Tesla aosp Rom data&cache f2fs

Please help thanks!!

Nvm ive needed systemmode http://xdaforums.com/attachment.php?attachmentid=3876011&d=1473947629
[SuperSU] Tecalote:
[MENTION=631273]Chainfire[/MENTION] Huawei p8 phones cannot be rooted with flashing SuperSU in TWRP with force systemless.

The patching of the boot.img has the result that the phone cannot start. It stays on a rescue screen.

I wonder because it is possible to root the newest MM firmware with SuperSU 2.67 and update the binary after Playstore Update.

But it is not possible to flash just 2.75, 2.76, 2.78 stable or 2.78 SR1 without stuck on boot.

Why does SuperSU no more support Rooting Huawei p8, or is it an issue of the Huawei boot.img in newer MM builts. Example GRA-L09 b370, b830...
[SuperSU] grep_i:
That's a device specific question try to search for an answer in the device specific thread please.
[SuperSU] fw85:
Hello,

I'm trying to get SuperSU 2.78 and suhide0.55 to work, but I'm having issues installing SuperSU systemless-ly.

After issuing this command:

echo "SYSTEMLESS=true" > /data/.supersu

I flashed SuperSU 2.78 SR1 and it said "System-less mode" in the pre-install checks.

But then something goes wrong in this part:

Boot image patcher

- Finding boot image
--- Boot image: /dev/block/mmcblk0p18
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting

I've tried alot of googling and thread searching on xda, but I wasn't able to find any clear instructions on what to do in this case. I've read somewhere that the boot image needs to be packed as gzip, so I did some searching again, but wasn't able to find any comprehensive guide on how to do that either. I've seen some people in this thread saying they got it to work on a G3 - did you also have to go through such hassle?

Could someone please point me in the right direction perhaps?

Device: LG G3 D855, stock MM

Recovery: TWRP 3.0.2
[SuperSU] pkelly517:
LG needs a 'bump' to the kernel, I've heard.

Good luck, or get a Nexus ?
[SuperSU] fw85:
Yep I'm aware of the fact that I need to bump the boot image in order to avoid 'secure booting error', but I believe that's a different case.

I mean, I'm getting a OnePlus 3 soon, but I wanted to get this to work regardless. I'm sure there's a solution, I just couldn't find it anywhere.
[SuperSU] dark_boy99:
thanks for best support and new updates

1 free:

add a software example king root in your pack

---------- Post added at 02:06 PM ---------- Previous post was at 01:56 PM ----------

what mean is SR1?

---------- Post added at 02:10 PM ---------- Previous post was at 02:06 PM ----------

where are i can translate app for persian?
[SuperSU] Ch3vr0n:
KingRoot in SuperSU? No thanks and probably never going to happen. 2 different su apps, KingRoot is lousy compared to SuperSU, KingRoot locks the binary preventing updating by SuperSU,... Different app, different developer

SRx.. read the first post. SRx is the new naming scheme instead of beta
[SuperSU] KKTHX:
Hi,

Does 2.78 SR1 working on Moto X Style XT1572 EU?

And root device via TWRP 3.0.2.0 without any problems?

With standard flash procedure (flash zip in twrp) or moto x style need special way to do it, commands etc?
[SuperSU] Boosik:
SuperSU v2.78 SR1 has huge performance hit on my phone (Huawei Mate 8 eu) when flashed systemlessly. Hit is so big it renders my phone nearly unusable (recent apps opening after 15s instead of instantly and so on). Using stock rom and only supersu flashed wia twrp.

Has anybody experienced this problem? Is there any know way to fix it?
[SuperSU] X46X:
Hi, how can I unninstall this SuperSu?
[SuperSU] RandomPooka:
From the supersu app, I believe there's a full unroot option. To be sure, you should restore your original boot.img with TWRP after
[SuperSU] Khorodax:
Lol you can atleast boot through the Huawei logo ... what a lucker my phone wont even boot after the installation :/ which means im stuck with no root for now... :(
[SuperSU] Alxoom33:
There is a SU uninstall zip available from [MENTION=1143630]osmosis[/MENTION]. Use it with conjunction with unrooting on the App.
[SuperSU] sendlinger:
It works on my Samsung Galaxy S5 G-900F (systemless with suhide 0.55). But the phone is very SLOW. Therefore I removed it.

Does anybody know, if there is a fix for the slow system?
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION], this is just a short shout-out to you: THANK YOU for still providing SuperSU for all of us, I especially enjoy the fact that you still develop it with such enthusiasm and heart blood - and on top of that provide the PseudoPro option. Recently, I discovered your easy to remember website www.supersu.com. I love you for that! :cowboy:

One question about this BETA: I've recently flashed this Cyanogenmod ROM for a friend of mine and the SuperSU flashable ZIP complains that the boot image could not be found, therefore no SuperSU when rebooting. How to fix that? I've already tried to install SuperSU as a nomal app (which works, but the SuperSU binary doesn't stick). I'm open for your recommendations.
[SuperSU] Ch3vr0n:
It's not his website, it's the one CCMT setup recently after their takeover of SuperSU. That's all I'm going to say about that.
[SuperSU] ldeveraux:
Are you replying to anyone in particular?
[SuperSU] Ch3vr0n:
That should be obvious. There's only 1 post referring to 'your website'. The most above mine.
[SuperSU] davy4475:
How can i fully unroot?
[SuperSU] Ch3vr0n:
If you're running systemless, flash your rom boot image. Running system install, flash your rom system image.
[SuperSU] davy4475:
Boot image? Sorry, not sure
[SuperSU] Ch3vr0n:
Yes, boot or system image. Depends if you're running systemless or not. Systemless modifies boot.img, system install modified system.img
[SuperSU] davy4475:
I extracted The rom and cant find boot.img or system.img. Clueless hehe. Im just trying to get snapchat to work lol
[SuperSU] Ch3vr0n:
Then dirty flash your rom.
[SuperSU] cinderbane:
This probably doesn't come as a surprise, but I'm having problems on the Note 3. I am currently on JasmineROM v6.1 (N900VVRUEOF1) Release [Sep 11, 2015] which ships with [UNOFFICIAL] Xposed for Samsung Lollipop by arter97 and an older version of /system mode SuperSU. I removed xposed with the xposed-uninstaller-arter97.zip on the xposed thread and unrooted with UPDATE-unSU.zip from here after using the "Cleanup for permanent unroot" option within the app. I can't find any "su" binaries after that, and I have /data/.supersu setup correctly, but SuperSU just will not install systemlessly:

My console:

Drew@Drew-Desktop ~
$ adb reboot recovery

Drew@Drew-Desktop ~
$ adb shell
~ # su
su
/sbin/sh: su: not found
~ # find / -name su
find / -name su
~ #
Drew@Drew-Desktop ~
$ adb sideload "D:\Users\Drew\Desktop\UPDATE-unSU.zip"
Total xfer: 1.00x

Drew@Drew-Desktop ~
$ adb shell
~ # cat /data/.supersu
cat /data/.supersu
SYSTEMLESS=true
~ # ls -la /data | grep .supersu
ls -la /data | grep .supersu
-rw-rw-rw- 1 root root 16 Oct 17 21:57 .supersu
~ #
Drew@Drew-Desktop ~
$ adb sideload "D:\Users\Drew\Desktop\SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Total xfer: 1.48x

Drew@Drew-Desktop ~
$

TWRP log:

http://pastebin.com/raw/hfwBZtEP (too long to paste in code blocks)

Let me know if there's any more info I can provide.
[SuperSU] grep_i:
That's because that's a feature only working on marshmallow and up.

With the help of Magisk it is possible to make SuperSU systemless working or you could try Magisk with phh superuser.
[SuperSU] SecUpwN:
[MENTION=1754043]Ch3vr0n[/MENTION], is this reply meant for me? I am not sure how to find out which "version" mentioned ROM is. Plesse clarify in detail for better understanding.
[SuperSU] F3N!X:
Hi,

I have a bootloop issue after SuperSu install. Have already suffered lot of such issues when I've upgraded my ROM to Lollipop, it took me so much time to solve this situation and now... back again, oh noooooo :(

- my phone is Sam Galaxy S2 i9100 correctly partitionned (1GB /system, not 512MB)

- Recovery is TWRP 3.0.2-1 but I've also tried with TWRP 3.0.2-0 and 2.8.7.0 Lanchon IsoRec

- Freshly installed Mokee RoM 6.0.1 (AOSP based), reboot, check, everything working fine at this step, root-enabled but no superSU yet

- Tried to flash SuperSU zip files from TWRP (2.78-SR1, 2.78-20160905, 2.76, 2.65) but I get always the same bug explained here by fw85 a few days ago: "- Extracting ramdisk --- Failure, aborting"

- I've installed SELinuxModeChanger, set it to permissive, and installed SuperSU app, allowing it to update SU binary, and SuperSU said it worked ok

- But after reboot, bootloop were back, restarted phone several times but no luck I was stuck what the f*** :silly:

- Of course I've re-flashed my ROM zip to fix bootloop but SuperSU still says binary needs update to work

Update:

I've also tried to install 2 different ROMs with flashing script managing the SuperSU install. Same error in both cases "- Extracting ramdisk --- Failure, aborting" during SuperSU step of ROM install. So if it's not related to TWRP version nor ROM, could it be a problem with my device?

Don't know what to do now, not just bootloop but also brainloop lol. And I have to admit I'm a little bit discouraged, I need a break :)

More seriously, if anyone here would have an idea to share about something to try, I would be glad to test it.
[SuperSU] earth08:
How to confirm for systemless root?

Will it root systemless if flash 2.78 sr1 with twrp?

Do we need to put comand echo systemless for systemless root?
[SuperSU] Ch3vr0n:
[MENTION=4686037]SecUpwN[/MENTION] no it's not
[SuperSU] SecUpwN:
[MENTION=1754043]Ch3vr0n[/MENTION], do you know the solution to this?
[SuperSU] Ch3vr0n:
No, not a developer and this isn't your cm ROM topic. I'd do the same thing as you should always do if you have issues. Logs!
[SuperSU] SecUpwN:
You're right. But I guess my issue is rather a simple thing, it seems like something small is missing so that the flashable SuperSU does not flash (I suspect that I need to flash the boot image, extracted from the ROM?):

******************
Boot image patcher
******************
- Finding boot image
--- Boot image: not found, aborting

The full logfile is located here.
[SuperSU] ashyx:
Supersu will not work without a patched boot.img

There is something about your boot.img that is incompatible.

You may have to patch it manually or try PHH superuser instead.
[SuperSU] grep_i:
[MENTION=5076362]F3N!X[/MENTION]

Probably your devices ramdisk is not compressed with gzip and can therefore not be decompressed by the SuperSU installer as it only supports gzip.

You can try and do this step manually and unpack it with the right tool if possible and repack it as gzip and run the supersu installer again.

Can not guarantee that it works but you can give it a try.

But you can better go to your device specific thread and ask the question there probably somebody knows the answer to your problem there.
[SuperSU] Frantch:
I have freshly flashed CM 13 on my S4-mini and when I flash SuperSU 2.78 it keeps installing the su binary in /system/xbin/ which makes the flash of suhide fail. Please help

1) fresh CM13 install

2) flash opengapps

3) 'in case' it put echo "SYSTEMLESS=true" > /data/.supersu

4) I flash superSU 2.78

5) reboot and when I check the xbin/su is there :(

Please help