yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] duowing:
That's weird. Do you have Tasker set up to just run the command, and then you have the Use Root option checked? I've personally never had good luck with that route. Whenever I run a shell command I always have it do

su

then whatever you want to run

---------- Post added at 07:09 AM ---------- Previous post was at 07:08 AM ----------

the r266-hidesu is a root package+hidesu
[Android Software/Hacking General [Developers Only]] desztan:
So it still need a supersu installed?
[Android Software/Hacking General [Developers Only]] PunchUp:
Well no. Just flash it like you usually do to root the device
[Android Software/Hacking General [Developers Only]] JRJ442:
Yeah that's how its set up. I have the Use Root option checked. It's always worked fine until trying PunchUps. I'm back on the regular PHH version and it's working again. I tried running just a simple run shell task with just su as the command. I get the pop-up, Tasker gets root granted. Then if I hit the play button for my run shell setenforce 0 task, it says no root access. I also tried redoing the task. A1 was run shell su, then A2 was run shell setenforce 0. It fails on A2 saying no root. Also if I try tapping on the use root option, it says I don't appear to be rooted. I agree it's pretty weird.
[Android Software/Hacking General [Developers Only]] vlad48:
But please also provide us with convenient uninstaller when possible...
[Android Software/Hacking General [Developers Only]] alexpower:
Just flash backup from boot.img and phh is gone and delete/deactivate apk in app manager

Gesendet von meinem HTC 10 mit Tapatalk
[Android Software/Hacking General [Developers Only]] karimrim:
An how-to would be nice...

After uninstalling magisk, then flashing r266, pogo still not working, safetynet check is false :-/

Edit : on A510F with android 6.0.1

Edit2 : confirming, after factory resetting, pokemon go ok, flashing r266 breaks it
[Android Software/Hacking General [Developers Only]] semail00:
Ok i will not install busybox...... :)

Thanks and rgds
[Android Software/Hacking General [Developers Only]] stokholm:
I'm really confused about this whole phhusson/doitright/seSuperuser project.

doitright provides a boot image with SELinux enforcing and version 1.0.3.1 of the Superuser.apk. Even though SELinux is in enforcing mode, this seems to support everything I need.

phhusson provides three different boot images (one permissive, the other two... what?) and a Play Store version of the Superuser app, version 1.0.3.2.

I tried the Play Store version of the Superuser app (1.0.3.2) with doitright's boot image, and it didn't work. So they're not even the same app?

Which of the boot images am I supposed to use? Are you collaborating or are you competing? I'm really confused. I hope these questions aren't too stupid for anyone to answer them. I really want to test, promote and support anything and everywhere I can. But I need to understand it first. :)
[Android Software/Hacking General [Developers Only]] phhusson:
It's collaboration. There are two sides to SU: One part is the su binary and SuperUser application itself (which both are in the same git repo Superuser), and the other part is integrating this SU in the ROM.

It is at this stage that I complement doitright:

- doitright provides patches on Android sources to integrate SU: https://github.com/seSuperuser/AOSP-SU-PATCH

- I provide tools to integrate on binary ROMs (either via build-bot or via superuser.zip): https://github.com/seSuperuser/super-bootimg

Full-blown ROM makers will likely prefer doitright's way, "simple" users (or MODers) will prefer mine.

As for compatibility of APKs, I changed the build system of Superuser so that it is easy to customize, via the packageName file. doitright changed the packageName in his release, hence the APKs are not compatible.

So anyone can fork, and publish its fork easily (including on PlayStore)

As for version number, I think doitright is behind, both concerning the app and various SELinux changes (I have a separated su_daemon context he hasn't implemented yet).

As for the 3 builds existing in the build bot, both are with SELinux globally enforcing, and:

- eng has SU context permissive (but only him, every other context is left non-permissive), and includes all known policies (in long-term it should be used only for debugging)

- power has all known policies, but su is not permissive

- user: Its aim is to include only policies considered safe (i.e. you can give root access to any app, and your Android Pay data will remain safe, it won't be able to make itself uninstallable, ...)

Please be aware that "user" does NOT provide the aforementioned safety at the moment, because SuperUser was originally meant to really give full power to app.
[Android Software/Hacking General [Developers Only]] stokholm:
So which of these would you recommend at the moment, as a SuperSU substitute for an "ordinary" root user? And do you plan on keeping three different images in the long run?
[Android Software/Hacking General [Developers Only]] phhusson:
At the moment eng, and the superuser.zip currently generates an eng image. In the long run, I hope only user will stay, but I don't know how hard this will be.
[Android Software/Hacking General [Developers Only]] ddimple4:
Should Xposed be able to run in the current configuration?
[Android Software/Hacking General [Developers Only]] phhusson:
I don't know Xposed's requirement, though I think it should work when installed from recovery.
[Android Software/Hacking General [Developers Only]] westhaking:
Which path should busybox be installed to?
[Android Software/Hacking General [Developers Only]] stokholm:
I flashed boot-su-eng.img to my boot partition using TWRP on my Nexus 6. Stock, unencrypted, but with doitrigh's boot image and with a modified system partition. When I rebooted after flashing boot-su-eng.img, it wouldn't boot past the Google logo, so I had to restore my backup. Any idea what went wrong?
[Android Software/Hacking General [Developers Only]] vMAC:
Don't know if this has been stated, however, the superuser.zip is not working on Nexus 6.

After installing I can't even get it to boot the android logo, after telling me it is corrupt it goes to black screen and I have to start the phone up again.
[Android Software/Hacking General [Developers Only]] phhusson:
Please give recovery logs. (adb pull /tmp/recovery.log after applying the superuser.zip)
[Android Software/Hacking General [Developers Only]] stokholm:
I flashed the img, not the zip. Do you want the same log from me?
[Android Software/Hacking General [Developers Only]] phhusson:
Erf right, no...

I'll try to take a look then, but that's weird.
[Android Software/Hacking General [Developers Only]] stokholm:
I will try flashing with fastboot tomorrow, to rule out TWRP messing up. I should be able to flash over doitright's image no problem, right? No need for further action?
[Android Software/Hacking General [Developers Only]] alphahere:
Nexus 7 2013 LTE razorg - su not fully working.

Thought this was working but cannot write to /data or /system with adb shell or terminal (permission denied) using "power" but works with "eng". Power did not work at all. Eng worked but everything in the log was denied. See attached logcat. Thanks.

here is my known-image file.

known-imgs/nexus/razorg/MRA58V

https://dl.google.com/dl/android/aosp/razorg-mra58v-factory-b9440868.tgz
image-razorg-mra58v.zip
boot.img
[Android Software/Hacking General [Developers Only]] stokholm:
Well I tried flashing the Nov. 29 version of shamu/MRA58R/boot-su-eng.img with fastboot. Still hangs on the Google logo when rebooting. Strange thing is that doitright's boot image is working perfectly fine.
[Android Software/Hacking General [Developers Only]] phhusson:
First known-imgs contribution :)

Thanks.

"power" is not really supposed to be able to write to /data or /system randomly, as this is considered unsafe. I'm currently working on mechanisms which will replace blind writing to /system and /data, to properly prompt user of that the su app wants to do. But that's a long shot.
[Android Software/Hacking General [Developers Only]] BarrOff:
The zip is working on Lollipop AOSParadox Rom for Oneplus One but not on Marshmallow version. It can be flashed on Marshmallow and boots, doesnt work. Recovery.log attached.

Maybe this is due to changes to selinux by the maintainers of the Rom? They were the first one to get a booting rom with selinux set to enforced, so I'm just guessing.

Keep up with your great work! :good:
[Android Software/Hacking General [Developers Only]] alphahere:
Question: I did search but could not find it in the thread. What is the best way to setup an init.d directory (run a script at boot) without modifying the boot image?

Maybe you could put this information in the op. If it is already, I missed it.
[Android Software/Hacking General [Developers Only]] phhusson:
This is not yet supported. My intention is to be full-featured without changing /system at all, but I need to implement some additional functions for that.
[Android Software/Hacking General [Developers Only]] beatLeo:
I can't downoload supersu r266... Please could anybody upload it.
[Android Software/Hacking General [Developers Only]] battoniko:
Hello,

I'm completely going crazy since i can't make it to pass safetynet.

I uninstalled everything (magisk, xposed, phh) ...so i'm back to zero with safetynet test OK and ready to start over the whole installation process

My config: Huawei Ascend P7 with Android L 5.1.1

Can anyone give me step by step instruction for Magisk+phh(with hidesu) that would pass safetynet (and if possible with xposed also).

I can't use suhide 0.53 since it's not compatible with Lollipop.

My plan is to use Magisk v7.zip, magisk manager v2.0.apk, superuser r266 hidesu.zip, superuser 2.0 beta6.apk (or if not compatible, the one on play store) and for xposed: framework 86.6 systemless with material design installer.

I'm not used to ask this kind of help, i usually tend to find answers by myself but with this specific subject i'm going crazy.

Thx in advance for your help
[Android Software/Hacking General [Developers Only]] 4RK4N:
the hidesu is NOT compatible with magisk yet. topjohnwu needs to make a phh-superuser-r266-hidesu_magisk.zip out of the current r266_hidesu.zip

just install the superuser-r266-hidesu.zip when ur completely back to stock with all old files removed. the 2.0beta6 superuser app works with that.

this way u should be able to pass safetynet.
[Android Software/Hacking General [Developers Only]] battoniko:
Ok, it worked, thanks.

Correct me if i'm wrong but i assume xposed 86.6 can't be installed and work along with hidesu since magisk is not supported (and magisk being a perequisite for xposed installation)?
[Android Software/Hacking General [Developers Only]] Eddiemc:
I'm trying to get my head around something:

To get this superuser "systemless" is by using magisk and the magisk version of phh, right?

Basically phh superuser works perfectly as it is, but I've unfortunately got a stupid bank app that doesn't like root.

Rootcloak and exposed fixes it, but I'm now on android n so that option is out.

Systemless supersu works with this bank app, but I'd rather have phh.

So to repeat myself, is magisk and the modified phh my solution to this?
[Android Software/Hacking General [Developers Only]] phhusson:
su has a --init option as the --bind option

So you can su --init /data/local/tmp/somescript

And that script will be started on boot. You can use su --init --ls to list currently registered tasks, and su --init '!/data/local/tmp/somescript' to delete it from the list
[Android Software/Hacking General [Developers Only]] phhusson:
Someone did it there:

http://xdaforums.com/zenfone2/general/superuser-r272-magisk-v7-xposed-86-6-t3475045
[Android Software/Hacking General [Developers Only]] PunchUp:
If your bank app works with systemless SuperSU, then yes Magisk and modified phh's Superuser is the way to go.
[Android Software/Hacking General [Developers Only]] ioanovich:
After flashing superuser-r266-hidesu.zip my xiaomi rn3pro can't reboot .... hangs on logo. What's wrong?
[Android Software/Hacking General [Developers Only]] Tesla:
Thats impossible to say with only that information. And i have no experience with your phonemodell.

Tell us more, what did you do before you installed it?

Is it stock rom?

Did you have root?

Xposed?

Magisk?

Phone was fine and now won't get passed boot-logo?

Try to be more specific m8.

//

Tesla.
[Android Software/Hacking General [Developers Only]] igorneumann:
SOLUTION FOR ERROR 134: Flashing a different kernel solved the issue... but I cant pass safetynet. :(

------------------------------------------OLD------------------------------------

It gives me the error 134 when trying to flash using TWRP, any ideas?

LG G4 with TWRP 3.0.2 running Imperium rom 6.0
[Android Software/Hacking General [Developers Only]] jesssiii:
This worked for me to once again pass safety net and use Android Pay when Chainfire's unsu no longer does.

Nexus 6P
[Android Software/Hacking General [Developers Only]] alexpower:
This r266 and apk from play store worked for me

Safety net is green and I have root

Gesendet von meinem HTC 10 mit Tapatalk
[Android Software/Hacking General [Developers Only]] 4RK4N:
only thing i have different than u is that the ls output to check looks like this for me:

angler:/ # ls -l /system/etc/hosts /data/data/hosts
-rw-r--r-- 1 root root 2108268 2016-10-06 14:28 /data/data/hosts
-rw-r--r-- 1 root root 56 1970-10-28 22:07 /system/etc/hosts

can this be the problem? different id on the 2 lines? in ur example its the same. did everything like in ur explanation. or can it be the 2.0beta6 superuser app is the issue? gonna try the old 1.0.3.3 from playstore (says "support su --bind and su --init" in changelog)
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
That support is binary side - it has nothing to do with which version of the app you use.

I am also having the same issue as you.
[Android Software/Hacking General [Developers Only]] 4RK4N:
the moment u wrote that i was alrdy rebooting with the old superuser.apk to see if its still working. it didnt like u said.

the column which is different in my ls -l test output is the filesize. so the hosts file in /system/etc is 56 byte while the one in /data/data/ is 2mb. if the bind would have worked the one in /system/etc/ should show 2mb too like in the explanation in post 714, no?

su --bind --ls shows the bind "10163 /data/data/hosts => /system/etc/hosts" so it should work...
[Android Software/Hacking General [Developers Only]] ridobe:
I had the same problem. Delete the bind, reboot. Create the bind again then reboot.
[Android Software/Hacking General [Developers Only]] IzaacJ:
Does anyone with enough knowledge about shell scripts have a moment to maybe help me apply the changes made by superuser-r266-hidesu.zip manually to an existing boot.img that I later flash straight to my device? There is serious issues with detecting my boot.img when flashing the zip, all zips that modify the boot partition have issues, this is most likely due to the way the boot partition is setup on my device.

dumchar_info:

Part_Name	Size	StartAddr	Type	MapTo	Region
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd BOOT_1
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 USER
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 USER
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 USER
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 USER
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2 USER
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3 USER
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0 USER
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0 USER
bootimg 0x0000000001000000 0x0000000001d80000 2 /dev/block/mmcblk0 USER
recovery 0x0000000001000000 0x0000000002d80000 2 /dev/block/mmcblk0 USER
sec_ro 0x0000000000600000 0x0000000003d80000 2 /dev/block/mmcblk0p4 USER
misc 0x0000000000080000 0x0000000004380000 2 /dev/block/mmcblk0 USER
logo 0x0000000000300000 0x0000000004400000 2 /dev/block/mmcblk0 USER
expdb 0x0000000000a00000 0x0000000004700000 2 /dev/block/mmcblk0 USER
tee1 0x0000000000500000 0x0000000005100000 2 /dev/block/mmcblk0 USER
tee2 0x0000000000500000 0x0000000005600000 2 /dev/block/mmcblk0 USER
kb 0x0000000000100000 0x0000000005b00000 2 /dev/block/mmcblk0 USER
dkb 0x0000000000100000 0x0000000005c00000 2 /dev/block/mmcblk0 USER
frp 0x0000000000100000 0x0000000005d00000 2 /dev/block/mmcblk0 USER
android 0x0000000076c00000 0x0000000005e00000 2 /dev/block/mmcblk0p5 USER
cache 0x0000000010000000 0x000000007ca00000 2 /dev/block/mmcblk0p6 USER
usrdata 0x0000000144100000 0x000000008ca00000 2 /dev/block/mmcblk0p7 USER
bmtpool 0x0000000001500000 0x00000000ffff0000 2 /dev/block/mmcblk0 USER
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate

eemc:

partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00004800 00005000 "protect_f"
emmc_p3: 00009800 00005000 "protect_s"
emmc_p4: 0001ec00 00003000 "sec_ro"
emmc_p5: 0002f000 003b6000 "android"
emmc_p6: 003e5000 00080000 "cache"
emmc_p7: 00465000 00a20800 "usrdata"
[Android Software/Hacking General [Developers Only]] 4RK4N:
alrdy deleted and recreated that bind + reboot like 30 times. no change -.-
[Android Software/Hacking General [Developers Only]] elreydenj:
Are you guys doing this after flashing the adaway systemless v2 file or after the regular method for adaway?
[Android Software/Hacking General [Developers Only]] NeCr0mStR:
Android pay, while using this method, simply says:

Android Pay can't be used

Google is unable to verify that your device or the software running on it is Android Compatible.

I am using Nutty Nexus with superuser-r266-hidesu.zip and phh-superuser. In Superuser I disabled the root ability but in a root checker it still pops up for root ability, doesn't simply detect root is disabled like I would expect with superuser set to disabled.
[Android Software/Hacking General [Developers Only]] xstahsie:
Hi,

I am having trouble flashing superuser-r266-hidesu.zip on my Nexus 6P.

When I first flashed it, the phone was stuck on the "Google" screen. I had to uninstall magisk, Xposed, and Suhide in TWRP to get the phone to boot up properly again.

However, I am now unable to flash superuser-r266-hidesu.zip--even after a restoring the phone to factory and reinstalling TWRP. The error I get every time now is "zip signature verification failed" (in red text).

When I check SafetyNet Helper, everything is in green (passed) and the root checker apps that I've downloaded from a Google Play Store says my phone is not rooted.

What could be causing this? Should I try flashing without checking the signature?

FYI--I've redownloaded the superuser-r266-hidesu.zip file already from this here.
[Android Software/Hacking General [Developers Only]] ridobe:
Don't use the systemless zip at all.
[Android Software/Hacking General [Developers Only]] 4RK4N:
who the hell told u guys to flash r266 and another phh build ? r266 alrdy has root in it and the hidesu added. not like with chainfires suhide which needs a root to hide. r266 phh build NOT. there is one in the zip. just flash r266 and ur fine. passing safetynet here. i NEVER touched that root toogle in superuser app. its always "apps & adb" idk who told u it works that way. hidesu is by no means a on-off solution like magisk v6 was.

afaik the adaway systemless v2 zip is for supersu so it wouldnt work anyway. the approach we were trying does about the same just phh superuser way.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
Just use the superbootimg script to patch the boot.img manually on a PC.
[Android Software/Hacking General [Developers Only]] phhusson:
Looks like you enabled zip signature verification in Advanced settings, just disable it.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
Disable Zip Signature verification in TWRP.
[Android Software/Hacking General [Developers Only]] xstahsie:
Thanks Captain_Throwback. That worked.
[Android Software/Hacking General [Developers Only]] IzaacJ:
Do you mean the bootimg.sh that is included in the zip? :) If so, that feels waaaay to easy xD
[Android Software/Hacking General [Developers Only]] elreydenj:
Same here. Hosts file in system/etc/host is on 56 bytes.... Thank you for all the help everyone. I am hoping that someone can continue to point us in the right direction. Loving how PHH superuser r266 works well to pass safety net and his new beta app is very nice. Only thing missing is a fairly simple way to get adaway working and we are all set!
[Android Software/Hacking General [Developers Only]] IzaacJ:
Seems there's other issues as well. No tools seems to be able to unpack the ramdisk. Used split_bootimg.pl to get the kernel and the ramdisk, but the ramdisk fails to extract with gzip, cpio and lzma. The file command shows only ramdisk.cpio.gz: data

Slowly giving up on this. Might trade it in for another android tablet... Just hard to find 7" ones with gps, at least around here xD

EDIT: Attatching the stock boot.img if someone wants to take a closer look at it.
[Android Software/Hacking General [Developers Only]] ZedAz:
Titanium Backup fails to detect root....is that a known thing or just with me?
[Android Software/Hacking General [Developers Only]] 4RK4N:
any easy way to get busybox working with this root? it doesnt have busybox included so idk if http://xdaforums.com/showpost.php?p=64228091&postcount=420 breaks safetynet. the post says its systemless-compatible but i dont want to start over again (alrdy did 20 times from yesterday evening til now xD).

interestingly nougat only does "android is optimizing..." on a full wipe/factory reset, just wiping /system /cache and dalvik-cache didnt trigger art rebuilding of every app. speeds things up a lot and keeps the device cool during binge-flashing :D
[Android Software/Hacking General [Developers Only]] phhusson:
That's a (old) standard MTK boot.img, it should work with my tools, I'll check why it doesn't.
[Android Software/Hacking General [Developers Only]] phhusson:
Ok that was a stupid error on my side.

Can you try with:

http://phhusson.free.fr/superuser-r273.zip (this include https://github.com/phhusson/super-bootimg/commit/e04e0cda1b5411370ae5f8c6b8ddccd0651b6ce4)
[Android Software/Hacking General [Developers Only]] Mibutastic:
Hi, I've run into a problem in the last couple days. I had the superuser binary needs updating message and when I went clicked on the notification, it rebooted into TWRP but nothing happened. Since then, it seems that my root isn't hidden any more by magisk and pokemon go has stopped working again. I've got magisk v6, auto magisk, systemless xposed and your superuser app installed. I don't know how to manually update the binary since I used to be on Chainfire's superSU and it would auto update the binary. Any help is appreciated.
[Android Software/Hacking General [Developers Only]] _nick_:
Hi,

I was recently running Magisk until today and am now trying to change over to this method. I am on an Xperia Z2 and am getting stuck and the SONY logo screen after I reboot.

I started again from scratch to make sure everything was clean. I flashed a pre rooted rom with SuperSU. I used SuperSU to full unroot my phone and rebooted

After that I flashed this kernel http://xdaforums.com/xperia-z2/development/kernel-advanced-stock-kernel-t3347413 and rebooted again.

No problems at the point.

Then I flashed http://phhusson.free.fr/superuser-r266-hidesu.zip and after rebooting is when I get stuck.