yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] phhusson:
This version is definitely an improvement compared to previous ones, it's starting to get really nice.

I'm still against the "Allowed" VS "Denied" sections. What would you say of displaying both allowed and denied apps, but first Allowed ones, then a spacer, then Denied ones, and the floating button inverts this order?

I do like the grid view better than the view list, even if I don't use enough root apps for it to be useful.

The intro guide has got better again.

As for themes, I do like both black and dark, and I guess other will come. I have one concern with it, is that the list might become too heavy.

This might be stupid, but how about letting the user decide the primary color (and have like three different secondary colors to switch to depending on primary color)?

Again thanks for your work, I can't wait to merge it :)
[Android Software/Hacking General [Developers Only]] Wlkchnbndgr:
Thanks. Will try to update. Is there something spezial i need to know? I use Magisk. :)
[Android Software/Hacking General [Developers Only]] phhusson:
Well if you want to keep with Magisk, you'll have to edit the magisk/superuser.zip

In common/sepolicy_patch.sh, where there is allowSuClient untrusted_app, add two lines:

allowSuClient platform_app

allowSuClient system_app
[Android Software/Hacking General [Developers Only]] Wlkchnbndgr:
Must i change the authorization after that and is there a different order i have to flash?

Edit: in which subfolder is selpilicy_patch.SH?
[Android Software/Hacking General [Developers Only]] PunchUp:
Yea I get your point. I personally feel that perhaps it's better to keep both as separate sections. But I'll consider to change it to the way you want.

Regarding the themes. There will only be three. Black, dark and light. And I will try to add colour pickers for the main ones (But that's for later)

Thanks for reporting this. Had a feeling this might happen on some devices. I'll fix it in the next build.
[Android Software/Hacking General [Developers Only]] gr8st:
Is there any chance to have a shell script that obfuscate (i.e. add random characters) the name of su.sh script and have it run on every boot with init.d? So, su.sh will be renamed every boot with random characters. Will that really be all it takes to evade SafteyNet for Android Pay?

Magisk doesn't work with my kernel and I'd really like to use android pay to leave my wallet behind on small store runs. Supersu users have suhide now, hope users of Phh superuser can manage a workaround too (that doesn't require magisk). :highfive:
[Android Software/Hacking General [Developers Only]] Deic:
Works nice in Redmi Note 2!! This is better than SuperSU and hide root is as easy as rename /sbin/su with term emulator and I can run Pokémon GO w/o problems :)

This is my script I use for easie https://goo.gl/A3ljM7

[MENTION=752778]gr8st[/MENTION]

You can use $RANDOM variable to generate random numbers like this example, IDK what is that su.sh file, if it is ramdisk related remove the "if" code & "echo" of the example:

#!/system/bin/sh
random_su=${RANDOM}.sh
if [ -f /data/local/random_su.txt]; then
mv $(cat /data/local/random_su.txt) $random_su
fi
echo $random_su > /data/local/random_su.txt
mv su.sh $random_su
sh $random_su
:
[Android Software/Hacking General [Developers Only]] barturblits:
Confirmed! Running omnikernel with 259 right now :)

Thanks!
[Android Software/Hacking General [Developers Only]] Sam Nakamura:
Downloaded the r259 and flashed as it is on resurrection remix 5.7.4 for oneplus 2 with no issues at all... Very satisfying :)
[Android Software/Hacking General [Developers Only]] Primokorn:
With the same ROM (Dirty Unicorns), Android Studio version (v2.2), I can't install an apk using the "Run" feature.

No issue if I switch back to SuperSU.

Android Studio is stuck at "Installing apk".

Here is the log.

Nexus 5 - superuser-r242 (eng verity nocrypt)

TIA

EDIT: also tested with r259
[Android Software/Hacking General [Developers Only]] blastagator:
Have you considered making a "donate" version similar to how SuperSU has a separate play store item? Might be a good idea to do that so we can contribute that way. Then in the future if you decide to add "premium" features, we will already have the token for them.

I know it would be easy to get premium features for free with everything open source, but I like to contribute. I didn't need any of the SuperSU features but paid anyway just to support the dev.
[Android Software/Hacking General [Developers Only]] str8str:
If changing from chainfire to this do I just flash or must I follow the change su app instructions in super su app

Sect From Me, Is That You?
[Android Software/Hacking General [Developers Only]] garrettsessions:
I would unroot per the SuperSu app, reflash your original boot.img, then flash the latest superuser.zip and install PHH superuser app from Google Play.
[Android Software/Hacking General [Developers Only]] str8str:
I tried the change super user option in super su didn't work so I flashed your super user zip then my custom kernel I run, booted up uninstalled super su app and installed the apk, and all is running fine. I'm on an n6 running RR rom and singularity kernel.

Sect From Me, Is That You?
[Android Software/Hacking General [Developers Only]] gr8st:
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?
[Android Software/Hacking General [Developers Only]] Oswald Boelcke:
To add to Sam Nakamura's statement, r259 runs nearly without an issue on Samsung Galaxy S3 LTE (GT-I9305) with Resurrection Remix v5.7.4 Sammy version.

However, due to one problem I had to revert to Chainfire's SuperSU v2.76: The issue was already report at post #871 and post #896, and it still persists. As the AGNi kernel is the one and only kernel that provides me with my desired battery endurance I'm totally dependent on this kernel and the capability to control its settings i.e. a functional AGNi Control application.

Otherwise, all other root applications run excellently with SuperUser, flashing is conducted easily and without any issues, and the SuperUser APK is in permanent development and constantly receives improvements. Thanks for all the dedication and superb work!

BTW: Changelog at OP terminates at 2016-01-31 r170. Is the changelog avialable anywhere else?
[Android Software/Hacking General [Developers Only]] abuddlah:
Hi, I'm having some issue trying to make phh superuser work with magisk. I followed the tutorial on the Magisk thread where I use the v17. But when I open the app, it says the SU binary is out of date. How do I make this work? Could you offer some help please :(
[Android Software/Hacking General [Developers Only]] phhusson:
Your download URL is asking for a user/pass...
[Android Software/Hacking General [Developers Only]] phhusson:
Only changelog would be git history, sorry about that :s

To my knowledge, your problem should be fixed with r255. Is your current version older? (if you don't know, give the content of /super-bootimg)
[Android Software/Hacking General [Developers Only]] BarrOff:
Does it work on the primary Rom or is there no way of using it with multirom?
[Android Software/Hacking General [Developers Only]] phhusson:
It sounds plausible it works on primary ROM, but I can't tell for sure
[Android Software/Hacking General [Developers Only]] nicholseric:
For MultiROM, make the ROM you want to flash the primary, then after flashing the superuser.zip, try inject current boot sector. "Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector." Or, before installing MultiROM, install superuser.zip and then backup entire ROM to .zip. Then install MultiROM and restore as a secondary ROM.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
It still might not work. I just tried restoring a secondary backup of a ROM where I flashed superuser to it as a primary and had working root. Now, however, with it as a secondary, I no longer have root :confused:.
[Android Software/Hacking General [Developers Only]] nicholseric:
My bad, Inject current boot sector removes /sbin/su but reinstalling superuser.zip in primary gets my su back.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
So injecting MultiROM into the boot image is removing su? I wonder why it would be doing that?
[Android Software/Hacking General [Developers Only]] nicholseric:
I am poking around here.

https://github.com/Tasssadar/multir...4915d4cc8bd089965fe11/trampoline/trampoline.c
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
That code is related to device init/boot-up - that code doesn't affect what's injected into the boot.img in TWRP (that I can tell).

EDIT: I think you want to look around here: https://github.com/Tasssadar/Team-Win-Recovery-Project/blob/master/multirom.cpp#L1189

EDIT 2: I still see nothing in there that indicates that MultiROM would delete anything in the ramdisk that's already there. As far as I can tell, files are just being added, not removed. It seems that /sbin/su should remain intact on secondary ROM boot images.

EDIT 3: I'm not sure where these files are coming from that are listed here: https://github.com/Tasssadar/Team-Win-Recovery-Project/blob/master/multirom.cpp#L1624. If sepolicy is being modified by MultiROM, that might be a problem.
[Android Software/Hacking General [Developers Only]] phhusson:
The problem is here:

https://github.com/Tasssadar/Team-Win-Recovery-Project/blob/master/multirom.cpp#L1621

I've already notified Tasssadar in MP, but perhaps he ignores MP, or he is in vacation...?
[Android Software/Hacking General [Developers Only]] nicholseric:
So as long as you don't choose inject after flashing superuser.zip in primary, you will get su. If you have SuperSU enabled in the original ROM, you might get the message that the su binary needs to be updated. Don't confuse the two binary update messages.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
Who's talking about SuperSU? :confused:

---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------

Best place to find him is probably on IRC in #multirom. But he's definitely a hard guy to track down.
[Android Software/Hacking General [Developers Only]] nicholseric:
On the "Pure Nexus" ROM, SuperSU is built in but disabled. Flashing superuser.zip and adding phh superuser gets me what I want. If you had ever enabled the built in su "SuperSU" then you might get one or the other binary update message in your ROM, especially when using multirom.

The easiest way to tell is from the terminal or shell, do a "which su". You want:

u0_a101@shamu:/ $ which su

/sbin/su

u0_a101@shamu:/ $ su

root@shamu:/ # su -v

16 me.phh.superuser cm-su

root@shamu:/ #
[Android Software/Hacking General [Developers Only]] Lannig:
Hello folks,

Newbie in Android development here although a hardened Unix/Linux long-timer, so please bear with me.

I was under the impression that stock recoveries only accept zips signed by a limited set of authorized keys (original manufacturer, brand etc.). Am I wrong assuming that this project aims at producing zips than can be installed with any terminal's stock recovery? Does this mean that just "any" valid key is accepted or what? puzzled.

Please enlighten me.
[Android Software/Hacking General [Developers Only]] phhusson:
There are two different method of using this root:

1) The build-bot/desktop-side compilation which takes a boot.img and generates a new boot.img

2) the update.zip

They are both using the same scripts/tools, it's simply that one is running in recovery the other not.

So method 1) requires an open bootloader, and method 2) requires a custom recovery. (ATM the update.zip won't work on a standard Android recovery at all, even if you have the keys)
[Android Software/Hacking General [Developers Only]] semail00:
Hello,

sorry i'am newbie e and i want to try root my nexus 6 with this method Supeuser, so i am starting from stock MRA58N with unlocked bootloader what files I need and how to install ( via ADB command or with Recovery Stock or TWRP ) to obtain root?

Thanks and rgds.
[Android Software/Hacking General [Developers Only]] phhusson:
Why aren't you on MRA58R?

Either way, I've heard both 58R and 58N use same boot.img, so you can download http://superuser.phh.me/nexus/shamu/MRA58R/boot-su-eng.img and fastboot flash boot it
[Android Software/Hacking General [Developers Only]] semail00:
Thanks to your quick reply.

I don't know why at the moment don't received OTA MRA58R. I' am stop at MRA58N with security patch dated 01/11/2015.

After flash your boot.img will I have Superuser ? Also have I installer busybox or not?

Thanks again to your work and reply.

Rgds
[Android Software/Hacking General [Developers Only]] phhusson:
Ok, MRA58N with 01/11/2015 security is MRA58R.

Once boot.img is flashed, you have to install phh's Superuser from Play Store, and then you'll have working Superuser.

This doesn't provide a busybox, only su.
[Android Software/Hacking General [Developers Only]] semail00:
Thanks,many thanks.

OK i will flash boot.image and will install from playstore phh's Superuser.

Another matter....Can install Stefen's busybox from playstore, it is compatibile with your Superuser?

For futher OTA security patch will lose Su?

Many thanks again.
[Android Software/Hacking General [Developers Only]] phhusson:
https://play.google.com/store/apps/details?id=stericson.busybox ?

Not really compatible, it is trying to mount /system rw, which can't happen here, because dm-verity is still enabled.

You might have some luck by specifying /sbin as install path, but it would need to be done at every boot.
[Android Software/Hacking General [Developers Only]] Oswald Boelcke:
Negative, as stated in my first sentence I used r259. Copied on the changelog.
[Android Software/Hacking General [Developers Only]] phhusson:
Could you provide logs then?
[Android Software/Hacking General [Developers Only]] Oswald Boelcke:
Currently, I'm back on SuperSU v2.76. Within the next days, I'll go for SuperUser again. Log is coming afterwards.

Thanks for taking care.

Which type of log/logging do you require? ...probably I didn't capture yet a "real" logging capability within the APK.
[Android Software/Hacking General [Developers Only]] android404:
Hey. I'd like to switch to this from superSU on my European moto g4 plus. Does the issue you described persist? Is there a work around simple enough for a regular user like me?

Edit: is it sufficient to run the command after each boot? And do all of the versions of this superuser solution work with the elementalx kernel?

Edit 2: I got systemless root, does that play a role when it comes to choosing a version and flashing it? Sorry for all the questions, I hope for answers...
[Android Software/Hacking General [Developers Only]] paed808:
I have Superuser installed on the unofficial CM14 build for the Moto G 2014 (titan) and it works good except AdAway still uses the built in CyanogenMod privacyguard root while all other applications use Superuser.

Any fix? Worked fine in CM13.
[Android Software/Hacking General [Developers Only]] Primokorn:
Sorry, this one should work : https://webcloud.zaclys.com/index.php/s/0QxA10Slky8wDro/download
[Android Software/Hacking General [Developers Only]] phhusson:
Does it do the same with internet connection (both 4G and WiFi) disabled?

If yes, could you provide logs when your internet connection is off?
[Android Software/Hacking General [Developers Only]] str8str:
You should turn off the built in super user in dev options they will conflict

Sect From Me, Is That You?
[Android Software/Hacking General [Developers Only]] doomed151:
The issue is still there. Executing the command manually does not work either. I had to manually copy the modules inside stock_modules.img into /system/lib/modules in order to make Wi-Fi work.

So, you only really have 2 options right now:

1) Copy the modules manually.

2) Use SuperSU (systemless, any recent versions will work).
[Android Software/Hacking General [Developers Only]] phhusson:
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?
[Android Software/Hacking General [Developers Only]] CyberZeus1977:
Just a question: I'm currently on Chroma ROM with Franco Kernel and Chainfire SuperSu. I'd like to switch to PHH.

If I am correct, I should unroot from SuperSu app, flash superuser-r259.zip from TWRP and then install SuperUser app. Do I need to reflash Franco Kernel after superuser-r259.zip? Or do I need the kernel in the repo?

Sorry, I'm a bit confused...

Thanks

Nexus 6P with Chroma rocks!
[Android Software/Hacking General [Developers Only]] Primokorn:
No need to flash Franco kernel but check the options into config.txt. You may want to change them.
[Android Software/Hacking General [Developers Only]] CyberZeus1977:
What do you mean?

Nexus 6P with Chroma rocks!
[Android Software/Hacking General [Developers Only]] paed808:
I tried that, but then AdAway doesn't detect root at all.
[Android Software/Hacking General [Developers Only]] Primokorn:
Read OP:
[Android Software/Hacking General [Developers Only]] Primokorn:
I didn't try yet but I guess it's the same. I'll send you a new log as soon as I can.

BTW OS Monitor doesn't seem to work. I have attached 2 screenshots (no information displayed) and a log.

In addition, I noticed that AFWall+ and Macrodroid don't work every time:

• Sometimes I can't reach the main screen of AFWall+ and I'm stuck at a blank screen (see screenshot).

• About Macrodroid, it can happen that my macros (automated tasks) don't work well.

I'll try to record a log but it doesn't happen each time I use them.
[Android Software/Hacking General [Developers Only]] phhusson:
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.
[Android Software/Hacking General [Developers Only]] Primokorn:
[MENTION=1915408]phhusson[/MENTION] Here is a log for my AFWall+ / Macrodroid issue.

After choosing AFWall+ from the notification panel, I have the blank screen and I have to force close AFWall+. At the same time, Macrodroid's macros didn't work. It looks like Superuser is frozen and no root app can work properly.

Hope the log will help.

FWIW about 40 su requests have been granted to Macrodroid one minute after the bug occurs. I tried to launch a macro a few times only.

Merci.

EDIT [MENTION=1915408]phhusson[/MENTION]

I'll check out the next AFWall+ update and come back to you if something changes. It seems there are su bugs in the current release.

https://github.com/ukanth/afwall/issues/583#issuecomment-250691298
[Android Software/Hacking General [Developers Only]] talkaboom:
Could you please share the macrodroid macros. Maybe its something about how you set them up.

I use only 3, and 2 of them are Wi-Fi toggles that work fine. One is intended to turn on the wifi when my SSID is in range. The other is to turn wifi off and turn on mobile data when said SSID is out of range.

The 3rd macro is a shake for flashlight that works a bit to too well for me, often turning on the flashlight when I am walking. :D

Point is my macrodroid seems to be working okay. I don't use AFwall+, so cant say about that.
[Android Software/Hacking General [Developers Only]] Primokorn:
Actually I have 40 macros. The one used in the log is very simple: toggle mobile data (empty trigger) which is launched from LMT Launcher (PIE controls).

EDIT: FYI I use this macro for a while and no issue with SuperSU. Likewise for AFWall+
[Android Software/Hacking General [Developers Only]] talkaboom:
:eek:
[Android Software/Hacking General [Developers Only]] doomed151:
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
[Android Software/Hacking General [Developers Only]] ZZZZXCC:
how to uninstall phh superuser? any steps?
[Android Software/Hacking General [Developers Only]] phhusson:
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)
[Android Software/Hacking General [Developers Only]] Deic:
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 :)
[Android Software/Hacking General [Developers Only]] 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.
[Android Software/Hacking General [Developers Only]] Primokorn:
New log with no Internet connection (data and WiFi). FYI I use microG instead of Gapps.
[Android Software/Hacking General [Developers Only]] Wlkchnbndgr:
Flash fresh Android IMG and done like in Op. (Fresh installiert)
[Android Software/Hacking General [Developers Only]] 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
[Android Software/Hacking General [Developers Only]] Wlkchnbndgr:
Just unroot the buildin root via chainfires su.
[Android Software/Hacking General [Developers Only]] 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.