yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Ofthecats:
Hey everyone,

I'm looking to start using this super user method from supersu.

I'm having trouble understanding the first post, and lack some technical knowledge. Also, xda search isn't getting my questions answered.

I want the same configuration as supersu, systemless.

From what I understand, I need to download the superuser.zip file for my device (angler), and edit the config. I'm supposed to add the keywords noverity nocrypt.

I'm unsure if these actions will result in the same setup I run now.

I assume selinux is often left enforcing. I also assume I can easily just change that with an app if I so choose.

I'm unsure about nocrypt vs nocrypt_all. With supersu systemless, I assume no partitions are encrypted?

My main concern is putting myself in a corner and having to wipe userdata, or generally breaking things.
[Android Software/Hacking General [Developers Only]] PunchUp:
You won't get systemless root with just this. It has to be combined with Magisk. So head over to the Magisk thread and read the instructions there.
[Android Software/Hacking General [Developers Only]] phhusson:
Actually this is a systemless root

Though it doesn't bypass Safetynet, and I don't want to bypass it
[Android Software/Hacking General [Developers Only]] Ofthecats:
So in order to use android pay, magisk is required. Understood.

But what about the keywords for editing superuser.zip?

Nocrypt_all results in no encrypted partitions. But in order to maintain adoptable storage, we use nocrypt. But then which partitions are encrypted? Would it be similar to having stock without encryption?
[Android Software/Hacking General [Developers Only]] PunchUp:
Actually, if your device is already encrypted, you won't lose it just by flashing the zip. This only disables forced encryption. You still have to format your partitions to unencrypt.

nocrypt only disables encryption for data partition.
[Android Software/Hacking General [Developers Only]] gobak:
Sorry for being noob. I have also encountered the Substratum/Masquerade fail so I flashed this one. Substratum started working but Pokemon Go stopped (Magisk toggled for no root). Am I doing something wrong or does this file break the cloaking?
[Android Software/Hacking General [Developers Only]] aamadorj:
Never mind.
[Android Software/Hacking General [Developers Only]] gobak:
Yeah of course. But it uses SafetyNet for checking the root. Magisk works perfectly but with phh's SU and Magisk Substratum stopped working. With flashing the SU mentioned a couple of pages back Substratum works but P:Go stopped. So I am wondering if I have to do something else than just to reflash the SU file.
[Android Software/Hacking General [Developers Only]] PunchUp:
I haven't tried Magisk and I don't play Pokémon. But I've read a lot of people mentioning that it works fine with Magisk + phh's SU. So you're probably doing something wrong.
[Android Software/Hacking General [Developers Only]] Ofthecats:
If my device is encrypted, twrp can read userdata even after clean flash?

Nocrypt disables force encrypt on userdata as well?
[Android Software/Hacking General [Developers Only]] cthulhu1987:
How about whitelisting apps a user knows to be benign (like the apps I just mentioned)? Is that even technically possible?
[Android Software/Hacking General [Developers Only]] OmegaBlaze:
I'm not sure about your first question, but Nocrypt ONLY stops devices from encrypting when a phone is already decrypted.
[Android Software/Hacking General [Developers Only]] phhusson:
I will not do trusting on the behalf of the user.

Does those app require root? We could whitelist apps which already got root permission (since they could already screw as much as they want...)

I've reported the fix to topjohnwu (he hasn't published the fix yet).

In the meantime, you can edit common/sepolicy_patch.sh inside phh-superuser-17-magisk.zip

and line 425, after "allowSuClient untrusted_app"

add a new line with "allowSuClient platform_app"
[Android Software/Hacking General [Developers Only]] cthulhu1987:
You misunderstood me, I meant disabling tapjack protection, when only whitelisted overlay-apps are active.
[Android Software/Hacking General [Developers Only]] PunchUp:
Userdata is part of the /data partition. So yes, nocrypt will disable forced encryption for that.

And TWRP can read data from both encrypted and unencrypted partitions. So, you don't have to worry about that.

Also, keep in mind that it's not absolutely necessary to unencrypt your device for rooting

---------- Post added at 03:42 AM ---------- Previous post was at 03:37 AM ----------

I'll take another look at the code but it's probably not possible to detect which app's overlay is currently active. So a whitelist doesn't really sound like a viable option
[Android Software/Hacking General [Developers Only]] phhusson:
Who does the whitelisting, and how?
[Android Software/Hacking General [Developers Only]] PunchUp:
I think he wants to whitelist certain apps with overlay, so that superuser will ignore these apps when their overlay is active.

Edit : Let me be more clear. He's asking to add a setting for that (whitelist) in the app.
[Android Software/Hacking General [Developers Only]] Ofthecats:
Thanks. In which partition is the encryption key stored?

Edit: apologies for all the questions. Last one
[Android Software/Hacking General [Developers Only]] gobak:
Works like a charm, thanks so much!
[Android Software/Hacking General [Developers Only]] phhusson:
It depends.

It can be in a dedicated partition, it can be saved by trustzone, or it can be in the userdata partition itself, at the end.
[Android Software/Hacking General [Developers Only]] Ofthecats:
Depends on what?

So, in review, encryption won't cause issues after clean system flashes, restores, backups, etc?

Is the only purpose of decrypting to improve performance?

Why do root solutions aim to decrypt? No verity makes sense. Idk the consequences of failing the check, but from short reading I assume you can't root with verity enabled.

I'm simply trying to determine what the use cases are for nocrypt, noverity, selinux permissive, etc. I had always thought it was either required for root and ROM, or at least convenience.

Edit: feel free to stop me from questioning lol
[Android Software/Hacking General [Developers Only]] JavaTiggy:
just checking in to see if there will be a boot img posted here: https://superuser.phh.me/nexus/shamu/ for the latest MOB31E?
[Android Software/Hacking General [Developers Only]] PunchUp:
That depends on which device and Android version you're using I believe. Not all devices have TrustZone, for instance.

Encryption shouldn't cause any trouble, other than slight performance hit. If you really want to keep it in case your device gets stolen, etc. then you may do so.

You can root with verity enabled, I think. But then you will see boot time warnings in case you/an app modifies system.

Also, su permissive and SELinux permissive are two different things. Right now, enforced su is not usable. So "eng" is the only one you should be considering to use at the moment.

Besides that, noverity also makes more sense than verity. But crypt or nocrypt is up to your personal preference.
[Android Software/Hacking General [Developers Only]] phhusson:
The usual reason not to crypt is that it is easier then in recovery to backup/restore in /data

It is provided with root mostly for convenience. Many people just use stock ROM + a root + custom recovery, so having uncrypt there is handy.
[Android Software/Hacking General [Developers Only]] Ofthecats:
Why is it easier to backup/restore? As in faster, or encrypted would break backups.

Back on topic, have you considered aroma installer to contain all the options? Or are you leaving a gap in knowledge to discourage the uninformed from messing around?
[Android Software/Hacking General [Developers Only]] PunchUp:
Latest versions of TWRP are fairly reliable for making backups on an encrypted device. But other than that, yes, encryption could break backup.

And yes, an AROMA installer is in phh's plans
[Android Software/Hacking General [Developers Only]] phhusson:
Well it does happen now and then that encryption is broken for one device's TWRP.

But I don't know if there is a real rationale.

I do consider making an Aroma installer, I just have other priorities at the moment.

If someone wants to do that, I'll be happy to merge it.

Making it hidden to discourage people wouldn't be a bad idea, but ATM I publish nocrypt variant in my buildbot, so that would be schizophrenic.
[Android Software/Hacking General [Developers Only]] OmegaBlaze:
[MENTION=1915408]phhusson[/MENTION] I flashed the newest nougat boot image (no crypt) and flashed the 242.zip with noverity & nocrypt in the config.text.

Still getting this message when I try and add a file to my system folder.
[Android Software/Hacking General [Developers Only]] apatal:
Hi OP,

Just noticed the build bot hasn't came out with a boot image for the bullhead (Nexus 5x) for the NRD90S build. I can only see the folder for NRD90M. Am I missing something? Or does the 2 builds have share the same kernel? Does the latest build have the September security patches?

Thanks!
[Android Software/Hacking General [Developers Only]] ryanallaire:
When I went from encrypted to unencrypted I could definitely tell a difference, mostly with read/write speed. If you do a lot of file transferring, TWRP backups, etc. it's a lot faster unencrypted.. Just my .02
[Android Software/Hacking General [Developers Only]] iam.z.jerold:
when i reboot it tells me binary is not up to date.. how do i update the su binary ? when i click on the notification it just goes straight to the app but it dont update anything
[Android Software/Hacking General [Developers Only]] ridobe:
What zip/image did you flash?
[Android Software/Hacking General [Developers Only]] iam.z.jerold:
phh-superuser-r242-20160908-magisk.zip
[Android Software/Hacking General [Developers Only]] ridobe:
Did you flash the magisk-v6 zip too?
[Android Software/Hacking General [Developers Only]] adrman:
Where did you find this? I've not found it on either phusson's buildbot or the OP of the Magisk thread.
[Android Software/Hacking General [Developers Only]] iam.z.jerold:
yes i flash Magisk-v6 then phh-superuser-r242-20160908-magisk.zip then Magisk-module-template.zip then xposed-v86.5-sdk23-topjohnwu.zip rebooted then installed Magisk_Manager_v1.2.apk and XposedInstaller_by_dvdandroid and downloaded phh superuser from playstore

toggle root works pokemon go(0.37) works the Xposed modules work its been 3 days all good but i just dont know how to update su binary T_T when i rebooted my phone phh's superuser notification pops up says su binary not up to date ??

im on CM13 RR rom for my s5

phh-superuser-r242-20160908-magisk.zip i found it on the xposed for magisk thread
[Android Software/Hacking General [Developers Only]] westeight:
Could you please post the link to phh-superuser-r242-20160908-magisk.zip
[Android Software/Hacking General [Developers Only]] iam.z.jerold:
here
[Android Software/Hacking General [Developers Only]] Wlkchnbndgr:
I am using Magisk and your Su. It works, but i habe a few problems. A couplets of time my device is self rebooting. Then a notification says: please update your su bin libery (vor somesthing near). What habe i to do?
[Android Software/Hacking General [Developers Only]] dreamland2000:
I get the message in TiBu that the binary may be out of date but all my root apps work fine.
[Android Software/Hacking General [Developers Only]] Wlkchnbndgr:
When i get the message, SavetyNet Helper shows a error till i reboot. Not all root apps works for me. Aicp Extras dont work
[Android Software/Hacking General [Developers Only]] ftarules:
Where to download the zip file for this superuser to use with magical?
[Android Software/Hacking General [Developers Only]] JudgeDread11:
Assuming you mean magisk, is in the op of the magisk thread.
[Android Software/Hacking General [Developers Only]] phhusson:
magical?

Anyway you can download it at http://superuser.phh.me/superuser.zip
[Android Software/Hacking General [Developers Only]] LucentBirch:
Has anyone gotten it to boot on their OnePlus One? I've flashed the latest zip, but I can never get past the boot animation. I'm on 6.0.1 on Darkobas rom (AOSP).
[Android Software/Hacking General [Developers Only]] Triviox:
Hello all,

Works in Galaxy J5 Dual SIM (sm-j500m/ds), someone test?

Thanks!
[Android Software/Hacking General [Developers Only]] JavaTiggy:
Any chance there will be updated boot imgs from your bot for the latest shamu Roms?
[Android Software/Hacking General [Developers Only]] kfasheldon:
Think he means Magisk systemless interface . I have just installed alongside and it now says su binary is out of date ..if I allow update will it still remain Magisk comparable and not mess up android pay and Pokemon.
[Android Software/Hacking General [Developers Only]] blempka:
I was going to ask the same thing. Anyone know?
[Android Software/Hacking General [Developers Only]] phhusson:
Added. Thanks for the report.
[Android Software/Hacking General [Developers Only]] tofu:
I first installed Slim6 without root, booted it, encrypted it, and then flashed the latest version of phh root. Boots and works fine.

Time to let go Darkobas, no more support. Slim has september security patches now too.
[Android Software/Hacking General [Developers Only]] LucentBirch:
Which slim are you using? It's just tough because darkobas had the AOSP base with the specific features I wanted and nothing else. Smooth too.
[Android Software/Hacking General [Developers Only]] tofu:
This https://dl.slimroms.org/downloads/Slim-bacon-6.0.1.build.1.3-WEEKLY-20160916-0859.zip
[Android Software/Hacking General [Developers Only]] timo_capa:
OP2 on Android N with "Bens test kernel" seems to work!
[Android Software/Hacking General [Developers Only]] rollerce:
Superuser goes away?

After reboot, superuser goes away, and I have to go back into recovery and reinstall the zip. How do I fix this?
[Android Software/Hacking General [Developers Only]] LucentBirch:
Well, I got it to boot with another rom, but nothing pops up in the app when I boot.
[Android Software/Hacking General [Developers Only]] PunchUp:
[MENTION=1915408]phhusson[/MENTION] here's the AROMA installer
[Android Software/Hacking General [Developers Only]] tofu:
Not sure what you mean with "nothing pops up when you boot". In order to get the root working you also need to install the SuperSU apk from play store or fdroid as indicated in OP.
[Android Software/Hacking General [Developers Only]] LucentBirch:
I thought I was supposed to install phh's app?? The whole point was to not use supersu stuff....
[Android Software/Hacking General [Developers Only]] PunchUp:
Yep, you're supposed to use phh's Superuser app. SuperSU won't even work with this
[Android Software/Hacking General [Developers Only]] LucentBirch:
Yeah, so I use candysix and I used the root removal zip they provided. Rebooted and confirmed that there was no root. Flashed superuser.zip from here, booted, installed phh's app, but still no root.
[Android Software/Hacking General [Developers Only]] PunchUp:
Are you sure that the zip installation was successful?

Try to flash the zip again. If you're using TWRP go to advanced, click on copy log and provide that file
[Android Software/Hacking General [Developers Only]] hoeni:
i9305 on a cm 13 based rom:

I re-installed everything well over 4 times now, yet I can't get it to work.

The issue everything boils down to seems to be that the flashable zip for phh root provided over at magisk's thread doesn't do anything. Or not enough :p

Magisk app never asks for root and ofc the toggle won't stay off either (although the app tells me I'm rooted)

I opened a pre installed kernel related app which complained about not getting root access.

I deleted everything SU related beforehand,

I followed the installation instructions carefully,

and I don't know what went wrong :(

Is the s3 simply too old?

Edit:

I tried the method using the modified chainfire SU.

It seemed to work, at first. Root can be toggled on and off, but I can't enter PoGo, nor will it pass safety net.
[Android Software/Hacking General [Developers Only]] LucentBirch:
It says it was. I have supersu installed again in the meantime, but I can try it later. I shouldn't have to do anything in the supersu app beforehand, right?
[Android Software/Hacking General [Developers Only]] PunchUp:
Other than removing SuperSU completely, no.
[Android Software/Hacking General [Developers Only]] manthes:
I have the same problem. It was working fine until it appears this message and now i don't have root access. I tried again all the steps but it didn't work.

Could it be a problem because i installed busybox?
[Android Software/Hacking General [Developers Only]] metrize:
which root for s6 please?
[Android Software/Hacking General [Developers Only]] talkaboom:
The latest zip should work. I use r229
[Android Software/Hacking General [Developers Only]] ftarules:
Auto correct messed up. I meant Magisk. The link the OP thread of Magisk had v17? This thread has superuser v242. This I'm confused.
[Android Software/Hacking General [Developers Only]] teddy0209:
Use the v17 in the magisk thread...
[Android Software/Hacking General [Developers Only]] iam.z.jerold:
when we download the phh superuser from the playstore does it update the su binary ? if not can you add this option
[Android Software/Hacking General [Developers Only]] Robot76:
Waaaaaaaaaaaa!!!

Thank you phhusson,

[emoji7]

Working awesome on Xperia z3c

A.R.I.S.E. Z3C SLiMM EliteKernel Phh.Superuser Nova Substratum
[Android Software/Hacking General [Developers Only]] mklmkl:
I also switched to phh's superuser (Nexus 6p, AICP MM + Nexus Tilapia w/Slimkat) and I'm also using Afwall+ (donate version) on both devices.

No issues at all!
[Android Software/Hacking General [Developers Only]] doomed151:
I have an issue with a kernel that requires SuperSU to load its modules. The modules won't load, so Wi-Fi is broken.

Device: Moto G4 Plus (XT1642)

Kernel: ElementalX 0.03 (download)

The kernel has its modules stored inside stock_modules.img within the ramdisk and it's supposed to be mounted on boot through init.qcom.rc with the following code:

on boot
mount ext4 loop\@\/stock_modules\.img \/system\/lib\/modules noatime ro

That's the only issue, everything else works beautifully. Thank you in advance.
[Android Software/Hacking General [Developers Only]] barturblits:
Any chance you could update the nvidia shield K1 kernel to 1.4? superuser-r242.zip (nocrypt, noverity) is not working for me on 1.4. The prebuilt 1.1.1 kernel does work.
[Android Software/Hacking General [Developers Only]] phhusson:
No it doesn't, though updating the SU binary is mostly useless, most changes are in SELinux policy, which is in the zip not the bin.

Though I think I'll change this mechanism.
[Android Software/Hacking General [Developers Only]] phhusson:
Would you have more informations? A mount line in init.rc will NOT need su

Latest release I see on nVidia website ( https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20K1&tx=$additional,shield ) is 1.3. Factory images are late?

If it is the case, would you have an official OTA link?
[Android Software/Hacking General [Developers Only]] doomed151:
What kind of information do you require? I forgot to mention that I flashed the superuser.zip with eng noverity nocrypt inside config.txt if that makes any difference. Running 6.0.1 build MPJ24.

Here's the actual script from init.qcom.rc:

on boot
mount ext4 loop@/stock_modules.img /system/lib/modules noatime ro

It's weird that it mounts fine with SuperSU but not your Superuser.
[Android Software/Hacking General [Developers Only]] Lrs121:
You can unpack the boot image and add that line in yourself after you flash the kernel and root. Just back up the boot image from twrp and use Osmosis's tools to unpack the image. Once that's done restore the modified boot image an the modules image should be mounted on boot.
[Android Software/Hacking General [Developers Only]] tofu:
Afwall+ works fine here. Running Slim6 on Oneplus one.
[Android Software/Hacking General [Developers Only]] drawde40599:
working great

so im using "noverity" 249-250 on my nexus 6P and its working great (THANK YOU), but i have a question about the "user" build , so if i made all the system changes and anything else i needed to do and now all i need is root permissions for apps i can switch from noverity to user right? from this description

- "user" is meant to give a safe su. su-apps won't be able to access to your Android Pay (for instance) informations, or keep persistent su access without your consent

im assuming user is the least "level" of root and closest to having a stock device ?
[Android Software/Hacking General [Developers Only]] oldman_58:
I loaded "N" from Google and using PHH Root, I found 2 directories that are suspect in System:

fake-libs

fake-lib64

anyone else see these?
[Android Software/Hacking General [Developers Only]] barturblits:
Correct, I just got the device and it seems the 1.4 update is only a couple of days old. Got it through the OTA. I am now running the custom kernel BitO-K6-006 patched with superuser 242 noverity nocrypt and works correctly. I will give you a message when 1.4 goes online, no need to check yourself.

Any progress on the omnirom kernels? Running your prepatched nexus6p stock kernel now on omnirom6 and works very nice. Too bad there is no omnirom for the nvidia shield k1. Only blissrom and CM13. Really love the combination omnirom+superuser+microg, no more proprietary gapps and su.
[Android Software/Hacking General [Developers Only]] marko207:
I'm trying to make AdAway work because it's saying there isn't root (other root apps working normally). Flashed last superuser. Changed in config.txt noverity and no matter what I do twrp want flash it (always getting error). I did try same with older superuser, same error...

What I'm doing wrong?

P.S. Unpacked with root explorer, changed verity to noverity, zip it and twrp keep returning error. Android 7, Nexus 7 2013.
[Android Software/Hacking General [Developers Only]] nathanchance:
Type this into a terminal emulator as root:

mount -o rw,remount -t auto /system
[Android Software/Hacking General [Developers Only]] marko207:
I did and nothing happened. AdAway still want work, twrp keep returning error. This shouldn't be that complicated...
[Android Software/Hacking General [Developers Only]] icaros1530:
Can't flash the superuser.zip I just downloaded from https://superuser.phh.me/superuser.zip with keywords "eng noverity nocrypt"

TWRP Install Zip Failed:

...

Installing seSuperuser...

seSuperuser: Found bootimg @ /dev/block/platform/msm_sdcc.1/by-name/boot

Updater process ended with ERROR: 139

...

What does that mean and how do I fix it? I removed root via SuperSU's full unroot to install phh.
[Android Software/Hacking General [Developers Only]] phhusson:
Could you retrieve full logs? from /tmp/recovery.log
[Android Software/Hacking General [Developers Only]] icaros1530:
here it is: https://www.dropbox.com/s/tg2t7t22bvn4r57/recovery.log?dl=0

and here the last few line from the log prior to error:

...

+ startBootImgEdit /dev/block/platform/msm_sdcc.1/by-name/boot

+ readlink -f /dev/block/platform/msm_sdcc.1/by-name/boot

+ f=/dev/block/mmcblk0p20

+ homedir=/tmp/superuser/scripts/su

+ mktemp -d

+ bootimg_extract=/tmp/tmp.D8MP75

+ cd /tmp/tmp.D8MP75

+ /tmp/superuser/scripts/bin/bootimg-extract /dev/block/mmcblk0p20

Unknown ramdisk type

Segmentation fault

+ cleanup

+ rm -Rf /tmp/tmp.D8MP75

Updater process ended with ERROR: 139

I:Legacy property environment disabled.

Error installing zip file '/external_sd/phhsuperuser.zip'

...
[Android Software/Hacking General [Developers Only]] phhusson:
Erf, what device is this? Could you link me to a stock boot.img?
[Android Software/Hacking General [Developers Only]] phhusson:
This is correct, but the thing is that "user" does NOT disable dm-verity, so you won't be able to boot with your modified /system