yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] 52wiseson:
Hi, shared your issues raised. Since you have confirmed that the suggestion (courtesy of [MENTION=1222466]denl[/MENTION]o) didn't work, please any more suggestions?

Thank you all.
[Android Software/Hacking General [Developers Only]] teddy0209:
If you shared the same issue with the same setup, then this is not the right thread, go to the magisk thread...
[Android Software/Hacking General [Developers Only]] tag68:
If you installed phh superuser and flashed Magisk. you are not rooted using phh superuser. You are rooted using MagiskSU and try to configure MagiskSU using phh superuser app. It can't find its binary because it is not installed.

Solution 1 Magisk using MagiskSU:

Uninstall phh superuser in Play Store (you only have the app if I'm right, you also just may ignore any message it shows but it makes no sense), and update Magisk Manager in PlayStore. Go to Magisk thread.

Solution 2 using phh superuser:

Restore original boot-Partition. Flash phh superuser. If you want Magisk additionally, flash this on top, but I'm not sure if it still is possible to use for phh. If you want Magisk, I'd recommend solution 1 ;)
[Android Software/Hacking General [Developers Only]] hyewiz:
Solution 1 worked
[Android Software/Hacking General [Developers Only]] Sovetskiy-Soyuz:
[MENTION=1915408]phhusson[/MENTION] the phh SuperUser worked for me, I have rooted normally, my phone is : Honor 8, android 7.0 and emui 5.0, Frd-l09c432b360, there is only permission s error, when I try to change files on root explorer...
[Android Software/Hacking General [Developers Only]] Taivotat2:
You can compress and sign natively in your Android device using MiXplorer, edit config.txt with inbuilt editor too. ??
[Android Software/Hacking General [Developers Only]] Taivotat2:
[MENTION=5050193]abhinavk[/MENTION] here you go.

These ones are with config.txt edited as you requested. Hope it helps. Maybe you didn't zip the files correctly. You need to pick meta-inf folder, scripts folder and config.txt file and compress them straightly. If you zipped them inside a folder, no way to work correctly. Did you understand? Hope it helps you ??

If works don't forget to thanks Hootan Parsa for amazing MiXplorer.
[Android Software/Hacking General [Developers Only]] ScaryBugThing:
I've been trying to get PHH Superuser to work as a manual replacement for MagiskSU with Magisk on a stock Axon 7. This involves Magisk, but I think it may be relevant here because it appears that PHH Superuser is what is not properly providing root.

Background: Axon 7 has some problems with Magisk and installing Magisk directly from TWRP never results in MagiskSU actually installing, but using methods I catalog in this thread I am able to install Magisk Manager 12.0, install the current PHH Superuser, and pass SafetNet with MagiskHide. The PHH Superuser is in fact shown as "MagiskSU" in Magisk Manager, and listed as properly installed/rooted. The PHH Superuser APK manager also installs fine.

The issue is that after installing, trying to use any rooted app results in a notification window that "[App] is denied superuser rights." Even if I set PHH to grant root access or set it to prompt for access, there is no prompt or allowed notification, and eventually it just fails.

Since Magisk seems functional, I'm inferring the problem must be with the PHH Superuser root. It's possible I'm confused about this being a PHH SU issue, but if anyone can help, I'd be grateful.
[Android Software/Hacking General [Developers Only]] Black-FR:
According to your screenshot, you are using magiskSU and not phhSU.

And as you now installed two superuser apps, and maybe even flashed phhSU on top of magisk, you did totally confuse the root management on your device.

I would suggest, to use magisk and magiskSU or if you want phhSU, then uninstall magisk completely and afterwards flash phhSU.

But remember, you have to flash a unmodified boot.img, before you flash phhSU.
[Android Software/Hacking General [Developers Only]] ScaryBugThing:
Thanks for the response, appreciate it. Actually it says "MagiskSU" but in fact I only flashed PHH - trying to flash Magisk did not properly apply root, so prior to flashing PHH, Magisk (and other programs) failed to detect any root.

But gladly this is resolved, my cross-post to Magisk linked me to Magisk betas, and the beta versions correctly installed MagiskSU. Appreciate the help.
[Android Software/Hacking General [Developers Only]] blakegriplingph:
So what if I want to manually replace SuperSU, or perhaps the likes of Kingoroot, with this? Has anyone come up with a way to do so, well since I am yet to cobble up a recovery for my LeapFrog Epic, and it doesn't help that the bootloader on that thing is locked.
[Android Software/Hacking General [Developers Only]] roytam1:
N00b question: Does PHH Superuser work on devices with *LOCKED* bootloader?

I have a docomo SO-02G and docomo locked device's bootloader and no way to unlock it.
[Android Software/Hacking General [Developers Only]] chudy_85:
No way
[Android Software/Hacking General [Developers Only]] mel2000:
My Android phone is already rooted and is currently using SuperSU as the root manager. Could I simply uninstall SuperSU and install the phh superuser app from the Play Store as a replacement?
[Android Software/Hacking General [Developers Only]] yochananmarqos:
Fully unroot in SuperSU, reboot into recovery, flash your stock boot.img & phh superuser, reboot and install the phh superuser app.
[Android Software/Hacking General [Developers Only]] mel2000:
Thanks for your prompt reply yochananmarqos. That solution seems awfully convoluted just for changing SU managers. And one of my two rooted phones still has stock recovery. Why does the SU manager substitution need to be so involved if the phone is already rooted?

For now, I've blocked the Chainfire SuperSU app with my firewall. Hope that helps to keep it in check.
[Android Software/Hacking General [Developers Only]] yochananmarqos:
SuperSU modifies the boot.img and uses its own proprietary binary that is not compatible with phh.
[Android Software/Hacking General [Developers Only]] mel2000:
OK, that makes sense. Thanks again.
[Android Software/Hacking General [Developers Only]] TheKaptone:
I have a mate9 which is unlocked and has twrp3.0.3-1 working no probelm, whenever i try to flash the su zip if i put it on the internal sd card twrp does not see it. There is only a whole heaps of folders with long combinations of letters shown instead. If i put the su.zip on the external sd card some of the versions I have tried show error 139 and fail to install or other versions seems to flash with success but when i try to open the Su app it says root not detected. Not sure what the next step is. I have had root on Nexus4 and 6P as well as Mate 7 and HTC desire and have never encountered this problem

any help would be good because i need adaway asap
[Android Software/Hacking General [Developers Only]] tag68:
This seems not to be a question about phh superuser, is it? Wouldn't ​the problem be the same if you try to flash Magisk or SuperSU or any other zip? My advice is to ask for help in your device's forum, probably in the twrp thread there.

BTW: Do you need a VPN, or what is your benefit not switching to DNS66 instead of adaway at least until rooted?
[Android Software/Hacking General [Developers Only]] androcraze:
Did you have another root on the device?

You could reinstall the boot.img with the original for your ROM. If it was modified with another root method, it may need to be cleared.
[Android Software/Hacking General [Developers Only]] Berdi86:
No, nothing was encrypted. These su was really outdated
[Android Software/Hacking General [Developers Only]] _horst:
Galaxy Tab S2 SM-T813

Hi,

I tried to install phh superuser on Galaxy Tab S2 SM-T813. I flashed the superuser.zip, getting no error. But I don't have root. The app "Verifiy root" gives me : "Busybox not installed or not symlinked".

What causes this error and how could it be resolved?
[Android Software/Hacking General [Developers Only]] androcraze:
You installed the app as well?

https://play.google.com/store/apps/details?id=me.phh.superuser
[Android Software/Hacking General [Developers Only]] _horst:
yes, I did. I also tried the f-droid version, without success. I flashed superuser.zip with twrp 3.1.1–1
[Android Software/Hacking General [Developers Only]] androcraze:
There are different types of root:

- eng makes su SELinux-permissive

- power makes su SELinux-enforced, but with every rights known of

- user makes su SELinux-enforced, but possibly safer

- noverity disables dm-verity

- nocrypt disables encryption

- nocrypt_all disables encryption on all partitions, not just /data (possibly works better than nocrypt, but breaks adoptable storage)

I can only recommend reading through the documentation and seeing which works best on your phone. You can edit the config within the zip, re-zip, and install to your heart's content. Some phones have different requirements than others.

My N5 works well with the defaults: "eng", "verity", "crypt". I don't encrypt my phone, yet.

"user" didn't seem to work well for me. The big item to play with will be the "noverity". There are also issues with some phones not liking encryption with this version of root.

As long as you can re-flash your original boot.img via TWRP, you can play all you like.
[Android Software/Hacking General [Developers Only]] _horst:
I applied already a "no-verity-no-encrypt" patch from this thread. Perhaps they interfere.

I'll have a look into this. Thanks.
[Android Software/Hacking General [Developers Only]] androcraze:
So you'll need to edit the config.txt in the zip file to:

eng noverity nocrypt

That just might fix it.
[Android Software/Hacking General [Developers Only]] _horst:
That was my hope. Unfortunately it didn't work. I tried a couple combinations in config.txt. No success.

Adding some logs. Perhaps they clarify things little bit.
[Android Software/Hacking General [Developers Only]] PunchUp:
Hang on. The error that you've mentioned in this post is completely unrelated to root. The app is telling you that busybox is not installed

Here's what you should try:

Install Busybox first of all

https://f-droid.org/app/ru.meefik.busybox

That should make it work, assuming that you flashed the superuser zip correctly

There's also an AROMA installer which I made some time ago (in case you want to give it another try)

https://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394/post68730104

Also, if it works, there's a new and improved Superuser app available on this thread

https://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394/post70150700
[Android Software/Hacking General [Developers Only]] _horst:
Seems obvious. Never had to install busybox on custom roms. Perhabs this is due to stock rom.

In meantime I flashed LinageOS with su addon and it works well.

I'm keeping your advice in mind should I turn back to stock rom. Thx.
[Android Software/Hacking General [Developers Only]] bsd1101:
I've just switched from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any suggestions?
[Android Software/Hacking General [Developers Only]] androcraze:
I don't see how this is a root issue; either the apps are there, or they aren't.

I have a solution: use a debloating script.

https://xdaforums.com/google-nexus-5/themes-apps/gapps-debloating-scripts-aosp-t3457204

You can use any of the thread's scripts as a starting point. Items to edit:

/system/addon.d/74-brs.sh

/META-INF/com/google/android/updater-script

NOTE 1: What you add or remove in one of the above, you need to add or remove in the other.

NOTE 2: the last entry in "updater-script" ***DOES NOT*** have a comma after it.

I have a custom version built; I debloat ***AFTER*** I've installed and configured all of the apps that I want on my phone, not before.
[Android Software/Hacking General [Developers Only]] bsd1101:
You're right as this isn't really a root issue. I'm just assuming that someone would know the difference about why supersu hides the apps I deleted in recovery, but superuser does not. They're definitely not deleted; even though it looks that way in recovery. That debloater script would do the same thing I do manually in recovery, so it wouldn't work
[Android Software/Hacking General [Developers Only]] androcraze:
I'm thinking your issue might be the /system/addon.d/74-brs.sh. Are you manually adding that as well?
[Android Software/Hacking General [Developers Only]] bsd1101:
I'm not. Why do I need to though? Isn't /system/app the same in recovery and running os? Where are the backups of the aps then store; and retrieved from on boot?
[Android Software/Hacking General [Developers Only]] androcraze:
I think it has something to do with backups, and making sure the system doesn't try pulling-in the app again.

What apps are you trying to remove? Are some of them "stubs"? Stubs automatically pull-down the app, withouth the app actually installed.
[Android Software/Hacking General [Developers Only]] bsd1101:
From memory as I went back to supersu for the time being, BookmarksProvider, GooglePinyn, GoogleJapanese, Maps, Music2, YouTube, talkback, CloudPrint, and several others.
[Android Software/Hacking General [Developers Only]] androcraze:
Again, I'd use my scripts as an example, and modify both files.

The scripts are designed for AOSP users wanting to install GApps; I don't see why they won't work for factory ROM users.
[Android Software/Hacking General [Developers Only]] pc_magas:
I would like this (open source?) solutions like this to run on my device (Huawei P8 lite).
[Android Software/Hacking General [Developers Only]] adinechin:
Installing on my Lenovo K5 Plus (A6020A46) on MIUI 8 (chainfire's SuperSU does not work)....

Yes ! Working nice, thanks !
[Android Software/Hacking General [Developers Only]] dnle71:
Is this still alive? Specially the beta app, it needs an update to fix the UI bugs.
[Android Software/Hacking General [Developers Only]] PunchUp:
Which UI bugs exactly?
[Android Software/Hacking General [Developers Only]] maybeme2:
I have a rooted (twrp) nexus 5 running stock 5.1.1 with xposed and SuperSu 2.79. I am not happy with the latest SuperSu versions and would like to try phh's Superuser. But, it's been years since I rooted my phone and need a step by step tutorial on how to make the change.

A thread I found said

"In order to replace SuperSU with Phh's Superuser you need to:

1. Go to SuperSU and fully unroot your device

2. Download Phh's binary from this thread - http://xdaforums.com/andr...ruser-t3216394 (TWRP flashable zip direct download link)

3. Flash the zip in TWRP

4. Download Phh's Superuser - https://f-droid.org/repository/brows....phh.superuser

5. Install Superuser and enjoy"

But if I fully unroot the phone won't that make twrp unavailable to perform steps 2 and 3?

Furthermore how do I "go to supersu and fully unroot... " There is no unroot option in my SuperSu.

Confused.
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
TWRP has its own su active in recovery, so no worry. You are missing something in SuperSU, it should have an unroot option. Also get the UNSU zip from osm0sis here on XDA.
[Android Software/Hacking General [Developers Only]] maybeme2:
Thank you. I found the unroot option. Had not seen it.

Will I need to root the phone again or will flashing the Superuser binary root the phone?

Do I need to uninstall xposed first?

What do I do with the unsu zip? And when do I use it?

Is the Superuser binary the "update.zip?

Thanks for helping.
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
Supersu roots your phone.

I would uninstall Xposed first, to save complications.

After you unroot in SuperSU, boot to recovery and flash UNSU to clean any leftovers.

Not sure, post 1 should explain that. (I have not updated this in a long time, works fine.)
[Android Software/Hacking General [Developers Only]] maybeme2:
Searched for UNSU in xda and on Google. Couldn't find it. Any other hints to find it?
[Android Software/Hacking General [Developers Only]] Nevermindthelabel:
https://xdaforums.com/showthread.php?t=2239421 in [MENTION=4544860]osm0sis[/MENTION] thread with a lot of great stuff. UnSu zip is in the OP
[Android Software/Hacking General [Developers Only]] maybeme2:
Thank you. You're super!.....
[Android Software/Hacking General [Developers Only]] maybeme2:
Did everything including UNSU.

Reinstalled xposed.

All seems to be working fine including Superuser and the xposed modules.

Question:

whenever I tell twrp to 'reboot system' it always asks me "install SuperSu? Your device does not seem to be rooted". I obviously didn't reinstall supersu but why does twrp keep asking me about it? Did I miss doing something? What should I do to stop that. The phone is rooted.

Edit

Also stickmount no longer works to let me use usb storage. I get an error message telling me I'm using an out of date SuperSu and I can't access the usb. Is there a work around?
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
Requesting to install Supersu comes from an old TWRP. Install a current version.

I know nothing about stickmount.
[Android Software/Hacking General [Developers Only]] maybeme2:
Will do.

How do you mount a usb drive when using phh's Superuser?

When I used supersu, I used Chainfire's stickmount to do this but it doesn't work without supersu. So how do Superuser users access usb sticks?
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
Mine is mounted automatically by Root Explorer file manager.
[Android Software/Hacking General [Developers Only]] maybeme2:
Mine won't. Must be a setting.

I'll keep checking.
[Android Software/Hacking General [Developers Only]] pro.aggro:
Coming from marshmallow and with the release of xposed for nougat i tried to update my phone. With this changes i want to give superuser a try and not supersu.

So i wiped all old files, installed nougat, superuser.zip and the superuser app. Root is working for AFWALL+, AdAware and Root Explorer. But it is not working for Titanium Backup.

"Sorry. I could not acquire root privileges....This attempt was made using the "/system/xbin/su" command."

Where is my fault?

Nexus 6 shamu

Dirty Unicorns 11.6 Nougat 7.1.2

TWRP 3.1.1.0
[Android Software/Hacking General [Developers Only]] ktmom:
I know you said you wiped everything, but when switching root methods, you really should unroot properly. At this point I would try using osm0sis' unSu script . Dirty flash your ROM, then start over with phh's superuser.

Keep the log after installing superuser so if you have trouble still, you can see what happened during flash. Specifically if there are bind errors.
[Android Software/Hacking General [Developers Only]] pro.aggro:
Same issue after flashing unSu script.

Where can i save the log?

Root Checker says "Root access is proberly installed on this device"
[Android Software/Hacking General [Developers Only]] ktmom:
You have to save the TWRP recovery log before booting. It's lost after a boot.

Advanced->Copy Log to SDCard

-or-

adb pull /tmp/recovery.log

Did you dirty flash your ROM after flashing unsu?

Try pulling a log while launching TiBu and see what it points you to.

You have authorized TiBu access to root, right?
[Android Software/Hacking General [Developers Only]] pro.aggro:
Ok thanks. I will do it again and post the log. But because of twrp error 7 it will only be available after flashing unsu.

I flashed the unsu script, then tried my rom but error 7 was shown. Rebooted recovery, flashed the rom, no error, then flashed superuser.

I can't authorizied Titanium. After starting the app the error with "no root found at /system/xbin/su" shows up.
[Android Software/Hacking General [Developers Only]] ktmom:
Why would you continue on with a TWRP error 7? That's telling you the ROM updater script reports the ROM is incompatible with your device.
[Android Software/Hacking General [Developers Only]] pro.aggro:
I know what error 7 means. But it only shows up after i flashed the unsu script. When i reboot and try again or without it there is no error. So i think the rom is ok. ;)
[Android Software/Hacking General [Developers Only]] ktmom:
I guess I misunderstood. You need to save the log after dirty flashing your ROM, then superuser. You don't need to keep flashing unsu.
[Android Software/Hacking General [Developers Only]] pro.aggro:
Here is the log after flashing superuser.zip. Rom was flashed before but i cutted it out from the log.
[Android Software/Hacking General [Developers Only]] _yen_:
[MENTION=4183521]pro.aggro[/MENTION] are you using latest beta?

https://superuser.phh.me/superuser-r310-beta.zip

No problem with Titanium Backup here using it... it seems to me some kind of bug from an older release, if i remember well if you delete (or rename) su binary in /system/xbin you should be now prompted for superuser permission running TiBu

bye

yen
[Android Software/Hacking General [Developers Only]] pro.aggro:
No i used the "normal" https://superuser.phh.me/superuser.zip

Will try the beta. Thanks.

Beta did not work > same error.

Deleting the su file works! Thanks
[Android Software/Hacking General [Developers Only]] irfanhutomo:
can anyone tell me how to instal this superuser on lineage os 14.1 ? only flash this phh superuser or must first flash the addonsu official from LOS?
[Android Software/Hacking General [Developers Only]] buffer overflow:
Flash what is recommended by LineageOS, that means addonsu.
[Android Software/Hacking General [Developers Only]] op3n:
i think i did a mistake; i had installed magisk and after i flashed phh superuser on a lineage version. now magisk crash. how can i remove totaly phh s. to make magisk work again?
[Android Software/Hacking General [Developers Only]] androcraze:
Reinstall your ROM's boot.img via TWRP.
[Android Software/Hacking General [Developers Only]] op3n:
i installed bbefore but is same. i flashed also entire rom without wipe, vut is same

---------- Post added at 12:09 PM ---------- Previous post was at 11:50 AM ----------

look what i did:

1. i installed via twrp, the boot.img ; magisk manager is starting to work, but say to me: no root

2. i flashed magisk 13.3 zip via twrp ; magisk manager is starting again to crash ...

i forgot to tell u that i have installed also supersu free 2.82 version and when i enter in su app is say to me: su binary occupied - so im confused about what i did and what i must do
[Android Software/Hacking General [Developers Only]] androcraze:
If you re-installed the boot.img and removed the SuperUser app, then it's not a PHH issue.

If you installed SuperSU, that complicates things. You need to completely uninstall SuperSU.

Magisk has its own SU; I'd chat with the folks in that forum to see if you can get it running.
[Android Software/Hacking General [Developers Only]] op3n:
ya, i reinstalled boot.img and remove super user app

i installed supersu after i observed that magisk dont aquire root privileges; so the problem i saw was before flashing supersu; and for remove supersu i tryed to flash that without resulty: https://xdaforums.com/showpost.php?p=63615067

i didnt remember until now to tell u: the reason of my decision to install phh su was magisk crash while accesing root option inside manager.. manager was ok, i could install zips,blabla but was giving to me that crash in root...anyway, thanks for ur help. If u find out something...tell me, if not i'll make a fresh install. have a good day!
[Android Software/Hacking General [Developers Only]] MichaBit:
-uninstalled SuperSU ✓

Working fine on Z3 leo. :good: