phh's SuperUser/ OpenSource SELinux-capable SuperUser

[talkaboom]

40 macros

 

[doomed151]

Ok, if running the command manually doesn't work, it most likely means it's an SELinux problem, and that your ROM has wrong SELinux.
Can you do, as su:
dmesg -c >/dev/null; mount -t ext4 -o loop,noatime,ro /stock_modules.img /system/lib/modules;dmesg -c
And give me the resulting output?

Here's the output on first attempt:

mount: Invalid argument
[  394.847789,5] type=1400 audit(1474904424.709:48): avc: denied { read } for uid=0 pid=13062 comm="mount" name="loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  394.848168,5] type=1400 audit(1474904424.709:49): avc: denied { open } for uid=0 pid=13062 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  394.848294,5] type=1400 audit(1474904424.709:50): avc: denied { ioctl } for uid=0 pid=13062 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 ioctlcmd=4c00 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  394.849694,6] type=1400 audit(1474904424.709:51): avc: denied { mounton } for uid=0 pid=13062 comm="mount" path="/system/lib/modules" dev="mmcblk0p47" ino=1851 scontext=u:r:su:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
[  394.849856,6] type=1400 audit(1474904424.709:52): avc: denied { use } for uid=0 pid=13065 comm="loop0" path="/stock_modules.img" dev="rootfs" ino=8984 scontext=u:r:kernel:s0 tcontext=u:r:su:s0 tclass=fd permissive=0
[  394.850117,4] EXT4-fs (loop0): unable to read superblock

and the second attempt:

ioctl LOOP_SET_FD failed: Device or resource busy
[  436.882578,5] type=1400 audit(1474904466.742:54): avc: denied { read } for uid=0 pid=13125 comm="mount" name="loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  436.883609,4] type=1400 audit(1474904466.742:55): avc: denied { open } for uid=0 pid=13125 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  436.883871,4] type=1400 audit(1474904466.742:56): avc: denied { ioctl } for uid=0 pid=13125 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 ioctlcmd=4c00 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1

 

[ZZZZXCC]

how to uninstall phh superuser? any steps?

 

[phhusson]

Here's the output on first attempt:

mount: Invalid argument
[  394.847789,5] type=1400 audit(1474904424.709:48): avc: denied { read } for uid=0 pid=13062 comm="mount" name="loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  394.848168,5] type=1400 audit(1474904424.709:49): avc: denied { open } for uid=0 pid=13062 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  394.848294,5] type=1400 audit(1474904424.709:50): avc: denied { ioctl } for uid=0 pid=13062 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 ioctlcmd=4c00 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  394.849694,6] type=1400 audit(1474904424.709:51): avc: denied { mounton } for uid=0 pid=13062 comm="mount" path="/system/lib/modules" dev="mmcblk0p47" ino=1851 scontext=u:r:su:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
[  394.849856,6] type=1400 audit(1474904424.709:52): avc: denied { use } for uid=0 pid=13065 comm="loop0" path="/stock_modules.img" dev="rootfs" ino=8984 scontext=u:r:kernel:s0 tcontext=u:r:su:s0 tclass=fd permissive=0
[  394.850117,4] EXT4-fs (loop0): unable to read superblock

and the second attempt:

ioctl LOOP_SET_FD failed: Device or resource busy
[  436.882578,5] type=1400 audit(1474904466.742:54): avc: denied { read } for uid=0 pid=13125 comm="mount" name="loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  436.883609,4] type=1400 audit(1474904466.742:55): avc: denied { open } for uid=0 pid=13125 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1
[  436.883871,4] type=1400 audit(1474904466.742:56): avc: denied { ioctl } for uid=0 pid=13125 comm="mount" path="/dev/block/loop0" dev="tmpfs" ino=12543 ioctlcmd=4c00 scontext=u:r:su:s0 tcontext=u:object_r:loop_device:s0 tclass=blk_file permissive=1

Ok, problem understood, I'll fix mounting from su soon.
Could you get dmesg right after booting to also get the error when called from init?
(I assume it is the same but from "init" instead of "su", but I'm not too sure)

 

[Deic]

So you run this every time you want to hide root, and run it again to restore? Have you tried it with android pay, does it work?

1- Yeah!
2- I don't use Android Pay or similar, so I don't know if they search for su binary or su daemon process... Try it and tell the result

 

[ilmank]

I rooted my phone with "phh's SuperUser 17 (Magisk Version) (2016.8.20)". It worked perfect. But now i need to unroot my phone becouse i will update android.
Can anyone please tell me how to unroot my phone if im rooted with "phh's SuperUser 17 (Magisk Version) (2016.8.20)"? i really couldn't find any guide or option.

 

[Primokorn]

If I'm asking it's because I think it could be related
I'm seeing a lot of network errors in your log, and you most probably have "Package Verification" enabled, which needs to have a stable internet connection (or no connection at all) to work.
If you have a flaky connection, you'll see a timeout, which is normal.

New log with no Internet connection (data and WiFi). FYI I use microG instead of Gapps.

 

[Wlkchnbndgr]

I rooted my phone with "phh's SuperUser 17 (Magisk Version) (2016.8.20)". It worked perfect. But now i need to unroot my phone becouse i will update android.
Can anyone please tell me how to unroot my phone if im rooted with "phh's SuperUser 17 (Magisk Version) (2016.8.20)"? i really couldn't find any guide or option.

Flash fresh Android IMG and done like in Op. (Fresh installiert)

 

[jellyfeels]

just want to ask, is there anyway to remove superuser from system or i need to flash the rom again? because the rom that i currently using have build in superuser. need to remove it before i can flash magisk

 

[Wlkchnbndgr]

just want to ask, is there anyway to remove superuser from system or i need to flash the rom again? because the rom that i currently using have build in superuser. need to remove it before i can flash magisk

Just unroot the buildin root via chainfires su.

 

[Only4givenOnceOfficial]

So the odds of getting support for the Grand Prime series? I have Sm-G530T1 running lollipop 5.1.1 looking for alternative root solutions for this device so that I may play Pokémon go while rooted and running closed no problem.

 

[GeekMcLeod]

Not sure which app is to blame but I don't get prompts for Viper4arise 2.3.4.0
Is there any way to manually give that app supersu?

 

[Robot76]

Not sure which app is to blame but I don't get prompts for Viper4arise 2.3.4.0
Is there any way to manually give that app supersu?

Yo! ViPER4Arise doesn't need or use SU, just normal permissions via settings/app/
ViPER4Arise has no business accessing system...
[emoji7]

For further troubleshooting, why not ask guitardedhero...

No SU:

A.R.I.S.E. Z3C SLiMM EliteKernel Phh.Superuser Rr.Xposed Substratum Systemless

 

[GeekMcLeod]

Yo! ViPER4Arise doesn't need or use SU, just normal permissions via settings/app/
ViPER4Arise has no business accessing system...
[emoji7]

For further troubleshooting, why not ask guitardedhero...

No SU:

A.R.I.S.E. Z3C SLiMM EliteKernel Phh.Superuser Rr.Xposed Substratum Systemless

It says I need it to install my driver. Before switching to magisk and phh, it was working fine.

 

[Toutatis_]

@PunchUp

Any chance you could change the position of the dial pad when we're prompted to enter our PIN code?

I wish it were at the bottom instead of the top. This placement is not very convenient, especially when you have a big display and/or only one hand available (I have a 6P).

Curious to read what other users think of this.

Cheers

 

[Robot76]

It says I need it to install my driver. Before switching to magisk and phh, it was working fine.

Oooo... My bad...

Try this:
Disabling Viper4arise fx, and install the systemless ViPER4Android at the OP here...

Also try asking Joe Blogs at the ViPER4Android thread about your predicament, he's also familiar with Arise project..

Sorry, not much help am I...
[emoji7]

A.R.I.S.E. Z3C SLiMM EliteKernel Phh.Superuser Rr.Xposed Substratum Systemless

 

[PunchUp]

@PunchUp

Any chance you could change the position of the dial pad when we're prompted to enter our PIN code?

I wish it were at the bottom instead of the top. This placement is not very convenient, especially when you have a big display and/or only one hand available (I have a 6P).

Curious to read what other users think of this.

Cheers

That's strange. I see a dialog on my device.

 

[exchequer598]

@PunchUp

Any chance you could change the position of the dial pad when we're prompted to enter our PIN code?

I wish it were at the bottom instead of the top. This placement is not very convenient, especially when you have a big display and/or only one hand available (I have a 6P).

Curious to read what other users think of this.

Cheers

I totally agree. A dialpad on the bottom of the screen also makes it easier for one-hand operation.

 

[ftarules]

I've Magisk V6 installed on my Nexus 6P. If I want to flash the latest superuser zip from this forum, I think it's v259, do I just flash that or do I need to do anything special? I like the ability to toggle superuser in Magisk to let Android Pay work.

 

[krelvinaz]

Hmmm did some searching but didn't see anything like what happened after I rebooted my Nexus 5x this evening and root was lost with a notice from superuser that a binary update was needed??

Everything was working just fine for more than a week with the configuration.

Nexus 5x
Android 7.0 NRD90S

Was configured with a flash via TWRP v3.0.2-2 Bullhead of both:

Magisk-v6.zip
phh-superuser-17.magisk.zip

and the apps for both:

Magisk_Manger_v1.2.apk
phh's superuser apk v1.0.3.3

Has been working just fine for more than a week however after the reboot tonight, there was a notification from superuser that binary needed to be updated but clicking on the notification just took you to the app itself with no indication of or how to update.

Root was lost in the reboot.

It is not clear how the binary for superuser is to be updated as there doesn't appear to be a newer version available or mentioned anywhere.

BTW there are a number of "reviews" on the phh superuser app google page that others are seeing the same so it is not just me.

It is late, so I will check back tomorrow to see if this rings any bells or a solution is available.

Thanks!