yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Darkcommand:
Can this work in moto g5 Cedric ?
[Android Software/Hacking General [Developers Only]] ashesall:
Using this for a while now and everything's working great so far. I'd like to ask a few questions that I hope you can answer:

If I delete the Superuser apk, will superuser requests be denied automatically?

Is it possible to show in log which files or directories were modified, or commands ran by the app granted with superuser access?

Or is it possible to show in the superuser request screen which files or directories the app requesting access wishes to modify or what commands it would like to run?

Thanks for your great work.
[Android Software/Hacking General [Developers Only]] androcraze:
Good question, as I may need to figure this one out too. Do the forums for your device have any insight?
[Android Software/Hacking General [Developers Only]] Younex:
Anyone tested noencrypt on android 8 ?
[Android Software/Hacking General [Developers Only]] androcraze:
We need a hero! Go! Go! Go! Go!
[Android Software/Hacking General [Developers Only]] Younex:
I don't have any device where I can put 8.0 yet :(

Just asking for future decisions :)

If I get my hands on a 8.0 ROM I will try that, but for now I can only wait.
[Android Software/Hacking General [Developers Only]] jessyjoseph2044:
I have a Nexus 6p on lineage is latest nightly. 7.1.2

Have no root privelages for reason of playing Pokemon go with my 3 year old daughter and wife. My question is is this a root option other than chainfire or is this a hide su app that'll hide chainfire root privelages. I want to be rooted to mod the little games like hill climber. But can't be because pk go blocks loading while rooted. So any help would be greatly appreciated. Need to n

Know what to use for root, what to use to hide the root and what not. Thank you guys
[Android Software/Hacking General [Developers Only]] androcraze:
This implementation won't hide root. Magisk is what you want for that; it has its own root.
[Android Software/Hacking General [Developers Only]] jessyjoseph2044:
It used to, apparently they removed it. It's posted in in if the comments there and directed ppl here which is how I got here
[Android Software/Hacking General [Developers Only]] androcraze:
It never "hid" root; it only moved it to boot.img, leaving /system untouched ("systemless"). That was more than enough at one point to placate the (then) newer security systems and implementations on Android.

A program can always look for a SU binary.

Again, Magisk is what you want if you're trying to hide root:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Android Software/Hacking General [Developers Only]] rooboshraja43:
Hi when I am donig root my system shown like this .how can rectify this pls reply me
[Android Software/Hacking General [Developers Only]] chudy_85:
Magisk v14.0 have root. Why you try flash phh',s root???
[Android Software/Hacking General [Developers Only]] rooboshraja43:
But magisk us failed
[Android Software/Hacking General [Developers Only]] Black-FR:
It's because your boot.img is already modified by another su, that's why magisk fails.

Reflash a non modified boot.img and then you could use magisk.
[Android Software/Hacking General [Developers Only]] mrfrantastic:
Any luck? My device is stuck in bootloader after flashing superuser.zip from OP... Had to reflash my ROM.
[Android Software/Hacking General [Developers Only]] androcraze:
I'm running a G5+ (Potter), and would love to be able to root with phh's solution as well. I still need to unlock the bootloader (OK, I've been busy).

Per this thread:

https://xdaforums.com/showpost.php?p=71602207&postcount=1

"noverity" is required for Magisk. Did you edit the zip to make that an option?

BTW, you shouldn't have to reflash the entire ROM if you have issues, only the boot.img.

[MENTION=1915408]phhusson[/MENTION], what else do you need for testing/de-bugging?
[Android Software/Hacking General [Developers Only]] MichaBit:
Note: on Sony XperiaX @ Omni 7.1.2 its superusing exxcellent! :good:
[Android Software/Hacking General [Developers Only]] mrfrantastic:
Tried it with eng noverity but ran into the same problem: stuck in bootloader. Damn, why did my Nexus 5 have to commit suicide :(
[Android Software/Hacking General [Developers Only]] androcraze:
I'm in the same boat. My trusty N5 died after 3.5+ years. The G5+ seems to be a worthy successor though.

Hopefully we can get this root version going.
[Android Software/Hacking General [Developers Only]] R1kM@n:
Hello, I hope you can help me... I try to install zip from recovery, but it finish the flash with 139 error. What it means? Thank
[Android Software/Hacking General [Developers Only]] ktmom:
There is more useful information in the TWRP log - assuming you are using TWRP recovery. Save it before rebooting out of recovery.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Android Software/Hacking General [Developers Only]] levone1:
Working great - Sony Xperia Z3 compact, MM 6.0.1 eXistenZ, (stock-based), rom... Had to use UnSU zip from 0sm0sis first to get rid of SuperSU.
[Android Software/Hacking General [Developers Only]] R1kM@n:
Thank you very much. Then i try to save the log and see if I found something... Yes, I use TWRP ?
[Android Software/Hacking General [Developers Only]] zputnyq:
Hi guys,

I wanna use phh's SuperUser on my mt6572 device.

Does this SuperUser support mtk devuce?
[Android Software/Hacking General [Developers Only]] zputnyq:
I get error when flashing superuser.zip

-- Installing: /storage/sdcard1/Download/superuser.zip

I:skiping set_bootloader_message: no /misc

Finding update package...

I:Update location: /storage/sdcard1/Download/superuser.zip

Opening update package...

Installing update...

+ fd=19

+ [ ! -L /proc/self/fd/19 ]

+ zip=/storage/sdcard1/Download/superuser.zip

+ ui_print Installing seSuperuser...

+ echo ui_print Installing seSuperuser...

+ rm -RfInstalling seSuperuser... /tmp/superuser

+ mkdir -p /tmp/superuser

+ unzip -o /storage/sdcard1/Download/superuser.zip -d /tmp/superuser/

Archive: /storage/sdcard1/Download/superuser.zip

creating: scripts/

inflating: scripts/bootimg.sh

inflating: scripts/.gitignore

inflating: scripts/kernel_subkey.vbprivk

creating: scripts/su/

inflating: scripts/su/changes.sh

inflating: scripts/su/su-communication.sh

inflating: scripts/su/rights.sh

inflating: scripts/README.md

inflating: scripts/kernel_data_key.vbprivk

inflating: scripts/kernel_data_key.vbpubk

inflating: scripts/gitversion

creating: scripts/keystore_tools/

inflating: scripts/keystore_tools/README

inflating: scripts/keystore_tools/make_key

inflating: scripts/keystore_tools/BootKeystoreSigner.jar

inflating: scripts/keystore_tools/BootSignature.jar

inflating: scripts/kernel_subkey.vbpubk

creating: scripts/bin/

inflating: scripts/bin/su-x86

inflating: scripts/bin/sepolicy-inject

inflating: scripts/bin/sepolicy-inject-v2

inflating: scripts/bin/futility-arm

inflating: scripts/bin/bootimg-repack

inflating: scripts/bin/su-arm

inflating: scripts/bin/strip-cpio

inflating: scripts/bin/bootimg-extract

inflating: config.txt

creating: META-INF/

creating: META-INF/com/

creating: META-INF/com/google/

creating: META-INF/com/google/android/

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

inflating: META-INF/com/google/android/update-binary

+ cat /tmp/superuser/config.txt

+ modes=eng verity crypt

+ cd /tmp/superuser/scripts/su/

+ fstab=/etc/recovery.fstab

+ [ ! -f /etc/recovery.fstab ]

+ grep -E \b/boot\b /etc/recovery.fstab

+ grep -oE /dev/[a-zA-Z0-9_./-]*

+ bootimg=

E:Error in /storage/sdcard1/Download/superuser.zip

(Status 1)

E:Installation aborted

I'm using Acer Z205 running on stock 4.4.2 with mtk 6572.

The superuser.zip I got it from the download link provided on the 1st page.
[Android Software/Hacking General [Developers Only]] _yen_:
retry using last beta: https://superuser.phh.me/superuser-r310-beta.zip

It works well for me, at least on N.

bye

yen
[Android Software/Hacking General [Developers Only]] zputnyq:
Ok, thank you for your suggestion.

I appreciate it.

Still the same, still get the same error
[Android Software/Hacking General [Developers Only]] Zepar7:
Urgent ..How to uninstall the root can anyone please tell me
[Android Software/Hacking General [Developers Only]] Sands207:
Hi! if i want to flash this on a samsung stock rom can i flash OVER superSU or do i need to flash on an untouched unrooted build?
[Android Software/Hacking General [Developers Only]] Alxoom33:
Use [MENTION=1143630]osmosis[/MENTION] unSU.zip
[Android Software/Hacking General [Developers Only]] androcraze:
Reflash the boot.img from your ROM and remove the SuperUser app.

---------- Post added at 20:28 ---------- Previous post was at 20:26 ----------

Look at osmosis' unSU.zip to remove SuperSU. Then install PHH.
[Android Software/Hacking General [Developers Only]] R1kM@n:
Hello, this can be installed for system root like supersu? Or it can be used only for systemless root? Thanks
[Android Software/Hacking General [Developers Only]] androcraze:
I used it as a standard root with the default zip setup. I was able to access the /system folder.

This is a "systemless" root in that no modifications are made to /system to initiate root; the only thing modified is the the boot.img.
[Android Software/Hacking General [Developers Only]] SkyeNymph:
Is it possible to pass safetynet with this root implement?
[Android Software/Hacking General [Developers Only]] zaabolla:
why there is no script to uninstall this root, why we have to flash original boot?

and to boot, a huawei nova plus takes a lot of time, is that mean the boot file is recompiled on every boot?
[Android Software/Hacking General [Developers Only]] androcraze:
Some people would consider installing a boot.img much easier than running a script.

Installing the boot.img returns things to the EXACT original condition; a script can't do that.
[Android Software/Hacking General [Developers Only]] levone1:
Might be somewhat ot, but maybe someone here has insight... I'm running a custom Nougat rom on Xperia Z3c, (m-rom). Rom installs in Aroma, and automatically installs SuperSU. I haven't found any way to get the rom to boot without SuperSU...

- original boot img included in the rom zip, flashed without installing SuperSU will not boot, (bootloop)

- kernel12, (custom LOS 14 kernel), flashed without SuperSU will boot, but SuperSU is still active as root, (I guess it's included as system root and systemless root{?})

- flashing kernel12, then using UnSU by [MENTION=4544860]osm0sis[/MENTION] will not boot, (bootloop)

- flashing kernel12, then flashing phh superuser, or Magisk will not boot, (bootloop) - either one flashes and installs fine, without error, in TWRP.

- booting rom as-is, and using file manager in recovery to delete SuperSU files will not boot, (bootloop)

- modifying install script to skip SuperSU installation - no boot

- another dev recently posted an update to the rom with the option to skip SuperSU installation - no boot, (even for him)

So, I'm wondering, what would be going on in the rom that would require SuperSU specifically to be installed, and how to change it?

Any ideas? Thanks
[Android Software/Hacking General [Developers Only]] kurtn:
[MENTION=1915408]phhusson[/MENTION] is this root method still maintained? It works well for some nougat and Oreo ROMs but not for aex 5.1 on xiaomi redmi 2 tried superuser.zip and r310-beta.
[Android Software/Hacking General [Developers Only]] phhusson:
It's no longer maintained, though I accept patches to support new ROM/devices.

I recommend using Magisk.
[Android Software/Hacking General [Developers Only]] MichaBit:
Nono, i dont need disguised root and foolish stuff, i do NOT like Magisk, its intrusive and not useable; as long as phh is working, its my choise cause full conviction - i dont want to turn back to SuperSu 4 root nexxt year. :rolleyes::eek: :eek:
[Android Software/Hacking General [Developers Only]] ryanallaire:
Magisk and SuperSU are not the same.. And between those two I would go with magisk..
[Android Software/Hacking General [Developers Only]] Bludwurst:
Then don't use Magisk Hide if you don't need it ?

Just use it for root.
[Android Software/Hacking General [Developers Only]] ashesall:
Thank you so much for SuperUser! Any plans to bring r310 out of beta? Maybe policy updates same to Magisk?
[Android Software/Hacking General [Developers Only]] MichaBit:
Good News - im pleased

phh's SU is working on Z Yuga @ Lineage 15.1! :good:
[Android Software/Hacking General [Developers Only]] Bludwurst:
It tragically fails to install on a TR10RS1 (Intel Education Tablet) running KitKat 4.4.4 and using TWRP 2.8.somethingorotheriforgot

Attached log. (Relevant info begins at line 582).

Checking the log, it whines about a syntax error (unexpected ~= operand/operator) on line 69 of bootimg.sh

And I tried pretty much all flashable zips available: none work.

SuperSU does work, but I'd rather use this.

EDIT: I just realized this had been discussed previously, but what I find odd is that I'm using TWRP 2.8.7.0, not ≥3.0.3.0 (which is when support for the operator was removed, no?).

EDIT 2: I decided to try using CWM to flash it. Still doesn't work ? My brilliant plan failed!
[Android Software/Hacking General [Developers Only]] Gilanio:
does it work on LG X POWER (LGK220)?
[Android Software/Hacking General [Developers Only]] alpha8196:
[MENTION=1915408]phhusson[/MENTION] stupid question , but how do I uninstall this?
[Android Software/Hacking General [Developers Only]] ktmom:
A quick search of the thread finds;

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Android Software/Hacking General [Developers Only]] jhedfors:
As I understand it, you need to flash/restore the original boot partition.

EDIT: already answered above.:)
[Android Software/Hacking General [Developers Only]] Knoth:
So the only way to get SU is Magisk? There is not an updated option that works, of an SU without any addition?
[Android Software/Hacking General [Developers Only]] androcraze:
There's a closed-source version that everyone loves. Magisk is open-source, and it's using some of the fundamentals as found in this thread.

Rooting got much more complex with Nougat and later ROMs. This root version was quite simple but very effective; I think the days of a simple root method are long-gone.
[Android Software/Hacking General [Developers Only]] partcyborg:
Hi,

Just to make sure I understand after skimming through the thread, This root management system does not as of now support SYSTEM only root, where SYSTEM only means that absolutely no modifications are made to the boot image, and instead made directly to the /system partiton. Correct?

Assuming the answer is "Correct, it does not" would you accept patches to make it support this if I make them? I am sick and tired of supersu's closed source system which is starting to break down, and I'll hopefully say it preemptively so that no one will tell me to "Just run Magisk!" again, because I can't. I have (and maintain a rom for) the USA Snapdragon version of the Galaxy s8/s8+/Note8 which all have locked bootloaders and therefore only system root can be achieved. This makes installing systemless root, or magisk in any form impossible.

Thanks for your time and for doing this, I was thinking of starting a similar project myself :good::good:
[Android Software/Hacking General [Developers Only]] androcraze:
You can make changes to /system with this method of rooting. It's the implementation that's different. This method modifies the boot.img to implement root and nothing else; that's why it's "systemless". Whether YOU modify /system or not after rooting is up to you.
[Android Software/Hacking General [Developers Only]] ktmom:
[MENTION=5061138]androcraze[/MENTION], You missed the point. The boot.img can not be modified on devices with a locked bootloader. Therefore, the point was, "is there a system mode install of this method?".

[MENTION=8360749]partcyborg[/MENTION], this root method is done only through the boot.img, so your answer is no. I'm not familiar with how Lineage OS roots, but maybe that is a direction you could look towards. Or, one of the older SuperSu releases, but they may disappear soon based on Chainfire's G+ post today.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Android Software/Hacking General [Developers Only]] partcyborg:
Yea thanks for the clarification, I had no idea the system root concept was so unfamiliar to other parts of the Android community, at least those on this thead.

So just to clarify a point for everyone who is reading to hopefully prevent misunderstandings in the future:

The terminology of "system root" vs "systemless root", as implicitly laid out by chainfire through SuperSU, defines each by what parts of the device you must modify

to obtain root

. What you choose to modify outside of that is not relevant, only what is necessary to be able to do run su or whatever to gain root. By this definition, this implementation as currently built is a systemless method. What I will be working on here soon is to build a fully system method of obtaining root using this system, or a variant of it. To start off with I will just fork the project viavgithub and start hacking away, but it would be nice to eventually merge things in once it's fully baked.

[MENTION=6617276]ktmom[/MENTION] thanks for the lineage recommendation I wasn't aware they were doing system roots there but I guess it's a wide enough platform to have pretty much everything. The system version of SuperSU is what everyone uses now, and what I want at least an option outside of for all these devices as despite them being unable to take away what we already have, it's already breaking down on bleeding edge Android versions and without the source to modify it before long it wont work at all, and I have no intentionb to try to get system only root support into magisk, as once you modify system at all things like safety net are out the door anyhow so ask that extra magisk complexity is for naught.

I guess I'll just get started when I can and look into how much work this will be and will likely bug this thread if I get stuckb it have questions. Thanks everyone.
[Android Software/Hacking General [Developers Only]] ktmom:
[MENTION=8360749]partcyborg[/MENTION] I just want to point out, I'm not saying Lineage provides a system root. I'm not familiar with their OS. I do know they provide a separate zip to root that is their own.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Android Software/Hacking General [Developers Only]] mangkon:
+ [[ toto2 =~ toto ]]
sh: =~: unknown operand

I have this problem before and it seems to be TWRP related.

Mine was solved by updating TWRP from v3.0 to v3.1.

I am a LineageOS user --LOS-14.1 and yes, currently a separate addonsu ZIP is required to root it (system mode).

The root ZIP basically:

-1. place the "su" binary in /system/xbin/

-2. place an activation script "superuser.rc" in /system/etc/init/

* Fyi, the rom is pre-patched (sepolicy) for su activation.

phh root (systemless mode) place the "su" binary in /sbin/ in bootimg.

I THINK it also patches the sepolicy... ?

For system mode root, phh explained in github here, How To Install.

Wish you luck.
[Android Software/Hacking General [Developers Only]] BeeWall:
I'm currently running TWRP 3.2 I believe, I'll try downgrading.

The placeholder mentioned in the instructions was removed years ago.
[Android Software/Hacking General [Developers Only]] androcraze:
The issue with the "=~" operand had to do with a switch from "sh" to "mksh" around TWRP 3.03:

https://xdaforums.com/showpost.php?p=70182720&postcount=2164

PHH's builds after that (after r275) supposedly compensated for it.
[Android Software/Hacking General [Developers Only]] mangkon:
I have a 2014 Samsung device (if relevant) on a LOS-14.1 rom rooted with superuser-r310-beta ZIP.

I have previously tested every known phh ZIP with TWRP from v2.8.7 till v3.0.3 but always ended with errors.

In my case, root is only possible with TWRP-v3.1 and the ZIP version doesnt matter, fyi.
[Android Software/Hacking General [Developers Only]] phhusson:
Basically, what's different between system-less and system-root is how to patch the SELinux policy

My su has basically four components

- the su daemon, which run as root, and is merely a gateway, apps send commands to it, and it executes the commands for the apps

- the app which basically serves a database to the daemon to tell which app is allowed what

- the selinux patcher, with a list of all policies updated needed

- scripts and tools to integrate the su daemon and the selinux patching inside a boot.img

You can basically reuse the first three, but not the last. You'll need to do live SELinux patching, but on Samsung devices, that should be possible (Nexus/Pixel don't allow live SELinux patching, but Samsung does)

The split between selinux patcher and boot.img patcher is not really well defined, but the boot.img patcher uses https://github.com/phhusson/super-bootimg/blob/master/scripts/su/changes.sh as an entry point for selinux patcher
[Android Software/Hacking General [Developers Only]] partcyborg:
Thanks for the help! That is great news. Especially as the current system root is only possible in permissive boot images anyway so I should be able to get a proof of concept working quickly
[Android Software/Hacking General [Developers Only]] blakegriplingph:
Is it possible to install this without having to mess with boot.img? I am trying to flash this on a LeapFrog Epic as I was looking for a safe and up to date alternative to SuperSU. Attempting to install this via TWRP results in an error, presumably due to issues with the boot image.
[Android Software/Hacking General [Developers Only]] ashyx:
Good luck with this, many are crying out for system root which basically died on many bootloader locked devices since android 7.
[Android Software/Hacking General [Developers Only]] ikunikun:
bootimg.sh in superuser-r310-beta

rwx_file_perms is defined as rwx_file_perms="$rx_file_perms $w_dir_perms"

isn't it rwx_file_perms="$rx_file_perms $w_file_perms" ?
[Android Software/Hacking General [Developers Only]] matrix_guy:
Does this work with latest Android pie?
[Android Software/Hacking General [Developers Only]] ashyx:
Not able to get it to work on oreo Samsung device.
[Android Software/Hacking General [Developers Only]] Alan90:
Good idea

A twist on SuperSU would suit me better using direct system viper anyway the point is both system and systemless are good for security ccmt I hope they replace SuperSU but pph I would like a separate build by you not needing magisk but equal to chain fire root SuperSU access
[Android Software/Hacking General [Developers Only]] hakimarx:
i use cm 13 with magisk 18, root detected by ebanking app. either super su. i flash nethunter to my nexus 5 before
[Android Software/Hacking General [Developers Only]] L_R_N:
Weird question: i need to root an old Android 4 device, and i find it impossible to install TWRP on it, and without TWRP i don't think i can install SuperUser (there's stock RockChip recovery, but it doesn't seem like it can install anything useful). But i might be able to obtain a firmware image and a RockChip tool to flash that directly onto the device. With some perseverance it should be possible to unpack that image and access partition images (boot.img, misc.img, recovery.img, system.img, etc).

So, the question is: would it be possible to just inject SuperUser into that boot.img right here, on my PC, then pack everything back and flash the whole thing?
[Android Software/Hacking General [Developers Only]] androcraze:
I don't have an answer, although it should work; you'd probably have better luck running under a Linux environment while attempting it.