yashsingh1/xdaforums huggingface dataset:
[SuperSU] bon122728:
in the first few seconds of flashing it was doing well i thought , but in the end when boot patcher shows up it then says "boot image not found, aborting" so yeah then it continues to flash and said finished and done, but when i booted, I opened supersu and viola "there is no SU binary installed", im unrooted. help.
[SuperSU] Starphish:
Extracted Superuser.apk, selected install, and then "App not installed".

This has to be simple. What am I missing?
[SuperSU] egingell:
That means it's: already installed and the same version, already installed and a newer version, or a different superuser app is installed. (Although, I think the last one will whine about signatures not matching.)

Look in Settings or dial *#*#7873778#*#* with the phone app.

Edit: or use an app like QuickShortcutMaker to make a shortcut. Most third-party launchers have an option to add custom shortcuts as well.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] naeco:
Apology in advance for the noob question, but should I expect any information from the terminal after hitting that command? I ran it and nothing came back (1st pic).

This is my second attempt. The last time, I ran it and went to to install 2.78 SR1 + hideSU0.53 then got an error at flashing hideSU, indicating that my root is not systemless (see pix with red notes)

By the way, how do I verify, with in TWRP, that SuperSU is systemless or not? I hate to switch back and forth between recovery and rom. Which command should I enter in the terminal to check that? Or where should I look?

Thanks!
[SuperSU] gothicVI:
First, echo piped into a file does not return anything on the standard output. Second,

you're using the wrong version of SuperSU and of xposed framework AND you're not following the very important installation ordering given by [MENTION=631273]Chainfire[/MENTION] in the suhide thread. In your screenshots you're clearly not using 2.78sr1 but 2.78 and you're not using the systemless version of xposed.

The last part I cannot answer.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] naeco:
Thanks for providing your answers in both threads!

My SuperSU version was actually correct. I flashed Magisk.zip > SuperSU-v2.76-magisk.zip > "SYSTEMLESS=true" > /data/.supersu > SR1-SuperSU-v2.78-SR1-20160915123031.zip

But during the process, the command line I entered in the terminal was wrong (didn't type 'echo') so the root was installed in system mode. I only found out much later when I re-read the log and saw 'System mode' detected during v2.78SR1 installation.

Re-ran the whole thing and got v2.78SR1 in systemless mode (pic). The key was to correctly enter the command line in the terminal.. oh well.. that's how noobs I am..

So a fool-proof walkthrough for anyone like me who want to install systemless SuperSU:

If you have already had Magisk and systemless SuperSU installed, skip to step 3

1. Flash Magisk-v6.zip

2. Flash SuperSU-v2.76-magisk.zip

3. Advanced > Terminal > Enter: echo "SYSTEMLESS=true" > /data/.supersu

4. Flash SR1-SuperSU-v2.78-SR1-20160915123031.zip. During the process, look for the line after "Detecting system compatibility". If it's 'System mode', you don't have systemless SuperSU and you must reflash Magisk.zipand SuperSU-v2.76-magisk.zip and begin at step 3 again. If it's "Systemless-mode, ...", then you're flashing systemless SuperSU.

5.If anyone also wants to install suhide, you must first remove all xposed versions by flashing xposed-uninstaller-topjohnwu-20160820.zip and probably this too xposed-uninstaller-20150831-arm.zip.

6. Flash SUhide-0.53.zip.
[SuperSU] EViollet:
Why steps 1 and 2?

To me they're totally unnecessary.

Or am I missing something?

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[SuperSU] naeco:
If you had read right above, you would have seen that I said to skip to step 3 in such case.

Envoyé de mon HTC J One en utilisant Tapatalk
[SuperSU] simmusss:
Not working with dual divice(Rom aosp7.0 nougot) after flashing SR1 zip after simcards was not detecting, anybody tried? If any solution plz post here ill try
[SuperSU] EViollet:
Then I suggest you read your text again.

What you're saying is that if Magisk IS NOT installed, then the user MUST install it. Again, I don't understand why. From what I understand, it would even be counterproductive. It is much better to start of with a system that DOESN'T have Magisk or systemless SU installed.

Once again, maybe I'm missing a point here. But I really fail to understand.

Regards
[SuperSU] Starphish:
I uninstalled SuperSU (via Settings/Apps). Installed the extracted apk (installed w/o error), then updated via Play Store. Rebooted and SuperSU now appears in the app drawer. Root was retained through all this.

FWIW there's no phone dialer (Nexus 7); I tried Hangouts dialer but it didn't bring up the app. Thanks.
[SuperSU] Bureizu:
APP says no SU Binary

Hi Everyone, [MENTION=631273]Chainfire[/MENTION]!

I'm trying to install 2.78-SR1 on a Samsung Galaxy S5 Exynos (G900H), I come from System SuperSU, then Magisk+PHH, and now I'm tying to get to the suhide workaround for SafetyNet. (but If I don't get SuperSU, how am I going to try suhide?)

I have installed the ZIP a lot of times, the last time I flashed stock ROM, then TWRP, Factory Reset, and then flashed 2.76 -> 2.78-SR1, with SYSTEMLESS and BINDSYSTEMXBIN lines in /data/.supersu, but every time the phone boots and I run the SuperSU APP it says the phone is not rooted.

If I re-flash 2.78-SR1 says it's already patched, restores stock boot, patches again, but when I reboot I have the same issue.

Do you guys know what may be happening on my phone, and any way to solve it?

Thanks in advance for your help!

--

Bureizu
[SuperSU] sound2005:
Please delete
[SuperSU] bon122728:
Same problem.
[SuperSU] srt10coupe:
Same oneplus One, oneplus 2, oneplus 3
[SuperSU] arubamon:
Thanks for providing this extremely helpful posted... it wasn't easy to find. I was able to successfully install systemless SuperSU, however, when attempting to update the binary, it fails. I tried flashing phh-superuser-17-magisk.zip instead of SuperSU-v2.76-magisk.zip. I'll now try flashing Magisk-uninstaller.zip, then flash SuperSU-v2.76-magisk.zip; hopefully that works. If there's anything special you have to do in order to update the binary, please let me know. Thanks again. :)

EDIT: Looks like that worked. Awesome. Thanks again!
[SuperSU] rochian_adrian:
Do i need a unlocked bootloader?

Hi guys,

I spend countless nights trying to make this work but i failed.

I have a Sony Z3c with locked bootloader (Allow unlock=NO).

I have stock 6.0.1 MM with TWRP 3.0.2-0 installed.

If i try to install SR1-SuperSU-v2.78-SR1 (on stock fresh firmware) in systemless mode with terminal command: echo "SYSTEMLESS=true">/data/.supersu

i allways get this error when trying to install SR1-SuperSU-v2.78-SR1xxxxx.zip

********************

Boot image patcher

********************

- Finding boot image

--- Boot image: /dev/block/mmcblk0p14

- Extracting ramdisk

--- Failure, abording

After i type the above command in TWRP terminal i can`t even install other version of superSU (2.76, etc). Even after phone reboot.

But if i try to install SR1-SuperSU-v2.78-SR1 after a fresh firmware install, without the systemless command, it install correctly. I have superSU app and root after system reboot. But is not SYSTEMLESS.

It is the locked bootloader or what am I doing wrong? Why can't i have SYSTEMLESS root?

A want to have SYSTEMLESS root, so i can use suhide 0.53 to hide root from 3 app.

Please help... :(
[SuperSU] casouzaj:
You have root and TWRP installed in your the system partition, located in /system/etc/mm_twrp_recovery, in your Z3C. So, install SuperSU in system mode, not systemless. Besides, whenever I tried to install the SR1 version, the SupeSU app disappears from my Z3C (also running the 291 firmware), for what I have to reinstall SuperSU from the Play Store. Just my $0.02,
[SuperSU] rochian_adrian:
Sry, but i did not understand too well. In my case i can't have systemless root because the way i have instaled TWRP? system/etc/mm_twrp_recovery
[SuperSU] casouzaj:
You have rooted and instaled TWRP trough this tool http://xdaforums.com/z3-compact/general/recovery-root-mm-575-lb-t3418714, right? So, your root is installed in the system partition. So, systemless mode won't work for you.
[SuperSU] rochian_adrian:
Yes, i use that tool :( I will try to find another way to root my locked bootloader phone, and try again. thx for the information. Have a nice Day.
[SuperSU] casouzaj:
Directly on MM there is no other way. You can, of course, downgrade to either Lollipop or Kitkat, root, install XZDualRecovery, enter recovery (preferably TWRP) and install a pre-rooted Marshmallow ROM. But through that path everything will also be installed in the system partition. So, I'm afraid that no systemless mode is possible for our devices.
[SuperSU] ashyx:
I don't know much about Sony devices and I'm surprised your locked bootloader allows you to flash a custom recovery, what kind of locked bootloader is that?

However your boot image probably is packed using an incompatible compression method.

Supersu only supports gzip.

For systemless to work the boot image needs patching.

You can manually patch your boot.img and repack it and then systemless will work.

You can find info in the supersu beta thread how to do this.
[SuperSU] cnnoi33:
Is the sim problem being worked on? I can try and give some logcats if you don't have.
[SuperSU] geek85:
there is a method to unlock temporarly the bootloader and relock it after the modifications.

with the zenfone ZE551ML, my problem is that the system boot on recovery (twrp) instead of booting the system with systemless superSU 2.78 SR1
[SuperSU] rmess2222:
Ze551ml

Is this even compatible with ASUS ze551ml? Thanks
[SuperSU] guhvanoh:
The bootloader is locked on my Tablet Z and Z2 and I have both root and recovery. The old Sony devices allow this. My Z5P however has to have its bootloader unlocked to get root. Regarding the OP, as his device cannot be unlocked, he cannot have systemless install. He has no way around this.
[SuperSU] kh34d:
[MENTION=631273]Chainfire[/MENTION] hi

Please super su broken dual sim with nougat,

Our developer [MENTION=4343949]PecanCM[/MENTION] in my device section said :

(I guess supersu somehow disabling qcom-c_main-sh script service that start 2nd ril daemon, adb shell ps | grep rild can tell if daemon running or not)

Can you please fix it?

Thanx for your great work
[SuperSU] ameel:
I would like to know too please! Is it compatible with ASUS Zenfone 2 ZE551ML x86, running marshmallow? If so, how?

Similarly, when I flash SuperSU v2.78 SR1, it only boots into recovery mode.
[SuperSU] rolandvrielink:
Is the v2.78 sr1 only 5,67kb in size?
[SuperSU] KaMyKaSii:
4,8MB
[SuperSU] rolandvrielink:
strange, when I click on the download link and download the file its only 5,67kb
[SuperSU] grep_i:
Use another browser
[SuperSU] rolandvrielink:
it worked
[SuperSU] Pkt_Lnt:
You will need to post a logcat if you want a solution.
[SuperSU] grep_i:
So what you say is when you flash nougat rom (please specify which one) on your device (please specify which one) dual sim is still working but as soon as you flash SuperSU (please tell us which version) the second sim stops working but the first sim is still working ?

Is this correct ?
[SuperSU] gottlasz:
I also have the same failure:

- Finding boot image

--- Boot image: /dev/block/mmcblk0p4

- Extracting ramdisk

--- Failure, abording

i understand my boot.img is compressed by "lz4" method (Lg K8 k350n)

However i cannot find the info about manually patch my boot.img. I was looking around on xda but nothing. Any idea?

And anyone knows the method how supersu finds the boot.img? I mean is it using the fstab file from twrp and if it does is it using the one in the ramdisk folder or the one in the ramdisk\etc folder.

Thanks!
[SuperSU] simmusss:
Xperia M dual, aosp 7.0 developd by Ron,flashed Su SR1 zip, and after flashed super su zip sims not detecting at all and also imei also shows only 1
[SuperSU] kh34d:
Check this post please,I hope it help.

http://xdaforums.com/showthread.php?p=68855844
[SuperSU] cnnoi33:
just adding, that sim bug also happens on stock software. my android one device received android nougat and i also get that no sim problem on it .
[SuperSU] kh34d:
Xperia m dual c2005

With this rom

http://xdaforums.com/showthread.php?t=3448481

As [MENTION=6776585]simmusss[/MENTION] said
[SuperSU] Only4givenOnceOfficial:
[MENTION=631273]Chainfire[/MENTION] can you help me please. I am trying to get some stuff done for people using my device that have found no solid solutions. I need systemless root for my SM-G530T1

Trying to play pokemon go but I have CM ROM.. I dont need CM ROM I can use stock for all I care. I would like to have xposed and root on my phone but be able to still play pokemon go. Due to that lovely update I can now no longer enjoy pokemon go without having to to use mods.

I need to be able to hide root access and xposed framework. From what I am reading everyone is saying I need systemless root and systemless xposed to used Magisk to hide my root access.

Also I have tried your CF-Autoroot for the SM-G530T since it is basically the same device as mine. However there are bugs. I will install it and nothing else at all. let the phone run for a good while and not make changes. then out of no where everything starts going crazy on the phone. This and that shutting down and stopped work messages start popping up. Then finally the UI has stopped working and only thing that fixes it for me is reflash stock firmware.

I have a working TWRP no problems there. If you could help me achieve my goal here it would be appreciated. I have always followed your work. Keep up the Good job!!
[SuperSU] noobSU:
I don't know why but SuperSU is causing my phone service to break. I loose my signals whenever i update my SU binaries. SuperSU 2.44 working just fine. But updating from playstore & then updating binaries causes that. Any fix guys plz?
[SuperSU] nicolap8:
Dont update!

If your current version works, dont touch it!
[SuperSU] Ch3vr0n:
Wrong, new versions can contain security fixes and others. If you'd check the changelog you'd know that.
[SuperSU] d4nvjpl0ng4n:
What problem with me? HOw can I fix it?

I am using HTC one e8 - Android 6.0.1

Thank you
[SuperSU] gothicVI:
Delete
[SuperSU] egingell:
You can start by using a different root checking app.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ashyx:
I find Root validator one of the better ones.
[SuperSU] egingell:
Obviously not since its call to su is hard-coded.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ashyx:
Hard coded? It detects systemless root just fine.
[SuperSU] egingell:
Well then you should post logs and other required information on the support thread. Screenshots of a root checker do nothing to help.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] d4nvjpl0ng4n:
Why do I have to use another app? anything wrong with this app? thanks
[SuperSU] ben_pyett:
Are you using chrome with data saver switched on, if so turn it off for downloads
[SuperSU] egingell:
Apparently nothing. Post your logs and other required information in the support thread. As I said in my previous post, screenshots of a root checker do nobody any good.

These screenshots are from two different apps. [MENTION=4899305]ashyx[/MENTION], if you're going to compare the results of one app to another, it's best to use the same app.

Edit: Nevertheless, they both found root on my phone, so...logs, which ROM, which recovery, what device, support thread.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Debeski1:
After trying to install systemless su on cm by twrp I get success but when I boot device there is no su app and when I installed it from playstore it says no su binary detected, can it actually be done or am I just wasting my time with this?
[SuperSU] ashyx:
I think you'd better reread the previous posts. #7344

I simply replied to the OP, quoting your post as reference, offering a better root checker app.

You responded saying it apparently wasn't and quoted the post saying its path was hard coded. I provided a screenshot proving it wasn't.

A bit of miscommunication probably. [emoji6]
[SuperSU] grep_i:
I guess you better ask this question in your device specific thread.
[SuperSU] d4nvjpl0ng4n:
So, how can I get the logs file and what are the required information?

I also check with Safetynet. It shows the result as below
[SuperSU] egingell:
^ your post

I've re-read it several times now. Tell me how this is offering an alternative. Besides, if you want to offer [MENTION=6449525]d4nvjpl0ng4n[/MENTION] an alternative, you should probably reply to him rather than me.

(edit: My bad, that was the wrong one. I think I thought you and other dude were the same dude. It's all irrelevant anyway.)

Regardless, both apps work fine. He needs to post in the proper thread with far more details than just a screenshot of a root checker.

Read the OP of the support thread. Recovery log, ROM, device. Those are the basic things you need.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ashyx:
My post:

Your post:

You got yourself confused as to what was being referred to.
[SuperSU] egingell:
Yes, I did. It happens when you get to be my age.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ashyx:
And mine [emoji54]
[SuperSU] Didgeridoohan:
I think you're a little confused. [MENTION=4899305]ashyx[/MENTION] suggested a different root checker than what [MENTION=6449525]d4nvjpl0ng4n[/MENTION] was using, that's all.

I think you didn't quite pay attention to who was answering and who you were quoting. :)

Sorry... Already cleared up. My browser wasn't showing the newest replies.
[SuperSU] egingell:
Thanks, but we got it sorted out about half an hour ago.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] d4nvjpl0ng4n:
Hi,

So now what kind of log should I need to make for you to help me with my Problem?

--------------

I would like to use supersu + suhide to play pokemon GO but when I flash superSU, I can not pass SafetyNet (see picture below)

When I check root with Root checker, it shows:

But when I check with Root validator, it shows:

Could you help me??
[SuperSU] ashyx:
You have system less root. If you want to play Pokémon go, Install magisk.

http://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[SuperSU] SnajperKRS:
How to install SuperSu on CyanogenMod in systemless mode?
[SuperSU] Bureizu:
Was this solved? I have exactly the same issue on the same phone with stock 6.0.1 ROM.

---------- Post added at 04:31 PM ---------- Previous post was at 04:25 PM ----------

Actually that's exactly how I have rooted the very same phone multiple times... Flashing Custom Recovery (TWRP) and then flashing SuperSU/PHH_SuperUser/etc...

After that you restart and voila! Phone's rooted... but strangely enough I have exactly the same issue with my G900H.
[SuperSU] d4nvjpl0ng4n:
Dear all,

after I format data and factory reset my phone, the Supersu Installer still appear and force me to install Supersu for rooting. How can I remove it permantly?

My phone is HTC one e8 Dual m8sd - Vietnam using Android M and twrp 3.0.2

Thank you so much
[SuperSU] egingell:
What is "forcing" you?

Edit: The only thing a factory reset does is clear /data. Anything in /system remains including a system install of SuperSU.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] grep_i:
Use the unroot option from within SuperSU app and just to be sure flash also in custom recovery unsu.zip from [MENTION=4544860]osm0sis[/MENTION] or remove all SuperSU related files and folders manually in terminal or file explorer, hint:

/system/(x)bin/su

/data/su.img

/su/(x)bin/su

And reboot to system.
[SuperSU] d4nvjpl0ng4n:
This one

I will try
[SuperSU] gottlasz:
Any news on "lz4"? :) Or shell we consider some other methods... :S

Nice job anyways....

cheers!
[SuperSU] NWTSCL:
Magisk is not necessary.
[SuperSU] ashyx:
Then explain the details.
[SuperSU] RandomPooka:
Presumably SuperSU and SUhide?
[SuperSU] NWTSCL:
They have been explained many times already. Read the thread, especially the OP.
[SuperSU] ashyx:
No, the info isn't for me. If you cant be bothered dont interject.
[SuperSU] NWTSCL:
Just trying to do you a favor by saving you from hassle. In not at my computer, so I can't search the entire thread add quote everything for you.

But considering that this isn't for you, why did you ask for the steps?

I know now that you don't appreciate help unless you are given every little detail and you can't be bothered to read, so I'll refrain from helping you
[SuperSU] Alxoom33:
You should read. If you don't bother reading you will inevitably brick your device. Makes a great ash tray![emoji6]
[SuperSU] -Happy Feet-:
Read the thread and the OP. Very often explained.

1. Complete Unroot

2. Flash the SUPERSU 0,78 SR1

3. Flash suhide

And then add pokemon to th suhide list. Read the OP.
[SuperSU] Ch3vr0n:
Again, you don't need to add Pogo to the list. That thing uses safety net, which uses play services, which is added by default in suhide.
[SuperSU] ashyx:
Why don't you try reading the thread yourself?

I dont need the info, I dont play Pokémon or any other games.

I offered another poster a suggestion. Someone else interjected saying it wasnt necessary, but couldnt be bothered explaining why?

So its not for my benefit. If it was I would have found the answer myself.

---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------

I have bricked more devices than youve probably had hot dinners. It's part of the territory when developing.

I know how to recover from a bricked device thanks.

---------- Post added at 09:25 AM ---------- Previous post was at 09:13 AM ----------

Look, dont take this the wrong way, I'm sure you mean well. You're a junior member with 11 posts.

I have been a member of XDA for a long time and I'm well aware of XDA rules and how to conduct myself around them. I wouldn't be an RC if I didnt.

Im sorry you seem to have taken offense, but that wasn't my intention.
[SuperSU] RandomPooka:
The important thing to remember here is that a phone would make a HORRIBLE ashtray. It has no sides.
[SuperSU] Alxoom33:
I love your analysis and logic :)
[SuperSU] ste22032:
Hi guys, correct me if I'm wrong, to install SuperSU in systemless mode correctly is not sufficient to flash the zip provided in the OP from recovery, but we need first to create a file with the following command: echo "SYSTEMLESS=true" > /data/.supersu from TWRP terminal and then installing SuperSU zip, can you confirm?
[SuperSU] JulGer01:
Depends...

Gesendet von meinem SM-G900F mit Tapatalk
[SuperSU] ste22032:
What do you mean? I'm waiting for my OP3, once it arrives I'll unlock the bootloader, flash TWRP and SuperSU, but I haven't understood if the systemless mode installation requires the creation of that file or not.
[SuperSU] grep_i:
Depends on the rom you're on I'm on Nexus 5 with Google developers stock factory images which defaults to systemless so I do not need to create that file.

I heard somewhere but I'm not absolutely sure it's true that CM roms do install systemmode and for those you have to create the systemless .supersu file, and of course other roms which default to systemmode too.

If you don't wanna find out or search what your rom defaults to you better create the file just in case that way you know for sure it will install systemless.
[SuperSU] pkelly517:
If you want systemless, use the command. It can only help. It can't hurt.

It's also one less variable you need to deal with later.
[SuperSU] ameel:
Makes phone x86 (Zenfone 2) VERY slow and sluggish. Happy to provide whatever log is needed.