yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Yan25:
Hi,

I confirm that superuser-r266-hidesu is now detected by Safetynet. Yesterday evening I passed the Safetynet check. Since this morning it fails. I have uninstall the phh superuser application and flash my stock boot.img, now the Safetynet check passes with success. So, I can connect to PoGo but I have lost the root :(

Cat and mouse game continues...

Regards

Yan'
[Android Software/Hacking General [Developers Only]] rhyzan:
Let's experiment with something.

Flash it back, install root switch app (or any app that could temporarily unmount your root partition) and check again.
[Android Software/Hacking General [Developers Only]] Yan25:
Hi,

Thanks, but unfortunately not working on my device. I had already a problem before: Hidesu is only working at the startup of android 5.0.2. Two minutes later hidesu is not working and all the applications see the phone not rooted. I lived with this issue but now, due to the safetynet update of yesterday, safetynet fails probably because it detects hidesu on my device.

Root switch shows that root is disabled and when I try to enabled nothing happens, still disabled.

Regards

Yan'
[Android Software/Hacking General [Developers Only]] snke:
Doesn't work for me on my Nexus 6P with pure nexus Nougat and r266 hide su
[Android Software/Hacking General [Developers Only]] waylo:
Same result here with my stock lg ROM, rooted with v266, no verity. ?

Don't think the app actually does anything in my case as I still have root capable after it supposedly switches it off.
[Android Software/Hacking General [Developers Only]] dinc2010:
Those of you who are still using hidesu and getting safety net blue and can't load PoGo, keep trying to load the game by restarting the app until it fully loads. That's what I've been doing anyway....the only thing is my PoGo+ won't work but other than that the game still works fine. Try and let us know!
[Android Software/Hacking General [Developers Only]] Yan25:
Hi,

Yes, I'm using hidesu and cannot load PoGo since this morning. I tried several times but always failing. I use SafetyNet Playground application to check SafetyNet. This app request a SafetyNet check to Google but always failing since this morning. When I flash my stock boot.img, SafetyNet check passes with success and I can load PoGo. So, it seems that hidesu is now detected by SafetyNet.

Regards

Yan'
[Android Software/Hacking General [Developers Only]] schizophrenia:
quick question.

I am on Nexus 6P (angler) NRD90X but I dont see this build under "Build bot: https://superuser.phh.me/ ". Is it safe to use the version for NRD90U?
[Android Software/Hacking General [Developers Only]] adrman:
There's no images posted yet for 90X. Just use the latest superuser.zip from the op or search the thread for r266, which is the hidesu version. That's what I'm using on Franco r33. Unfortunately, the hidesu portion of that release is now being detected.
[Android Software/Hacking General [Developers Only]] cocchiararo:
Made no change with Tasker, can't test AdAway since I had fixed it manually.

I have installed beta7 of the root manager app

Enviado desde mi Nexus 6P mediante Tapatalk
[Android Software/Hacking General [Developers Only]] jerethi:
Sorry for asking such a basic question, but I can't seem to find an answer in the original post.

I am running the latest stock ROM on a 5X with ElementalX. I'd like to try to root with phh superuser. What step do I need to take? Do I just flash the update.zip? Or do I also need to flash one of linked boot images?

Thanks in advance.
[Android Software/Hacking General [Developers Only]] adrman:
Just flash the latest superuser.zip from the build bot that's linked in the op or the unofficial r266 hidesu that you can search for in this thread. The default configuration for the zip is "eng". If you want to change, the instructions and different configuration descriptions are also in the op.
[Android Software/Hacking General [Developers Only]] Reedith8:
Working po go

:)nexus 6 p android n with pure nexus rom latest build flashed magisk and the phhsu experimental had root used it toTitanum backup and theme then In magisk maniger (latest virsion) unchecked phhsu and rebooted twice pokemon go working on version 0.41.4 as of 10/15/16 12:00 pst hope this helps
[Android Software/Hacking General [Developers Only]] jerethi:
Thank you! One follow up question. Will this modify my boot.img so that I can keep my custom recovery?
[Android Software/Hacking General [Developers Only]] Reedith8:
no you flash magisk and the phhsu special version and install magisk in ur custom recovery then install the magisk manager from their xda and bam
[Android Software/Hacking General [Developers Only]] jerethi:
Thanks. Could I trouble you to post a link to step-by-step instructions on this?
[Android Software/Hacking General [Developers Only]] adrman:
Yes it will.

Magisk has nothing to do with this.
[Android Software/Hacking General [Developers Only]] Yan25:
Hi,

Finally, I found a solution for my ZTE Blade S6 (Android 5.0.2) that works fine for me:

1. I removed all root applications and flash my stock boot.img to have a clean system without root.

2. In TWRP, I did the echo "SYSTEMLESS=true" > /data/.supersu (not sure that it was useful because SU has been installed on the /system)

3. In TWRP, I flashed SU 2.78SR1

4. I rebooted the phone

5. I installed Root Switch (1.2.4) application

I don't need suhide or hidesu, just SuperSU and Root Switch application.

Before launching PoGo, disable the root with Root Switch => SafetyNet test passes and PoGo works fine until the next update of SafetyNet or PoGo ;)

Regards

Yan'
[Android Software/Hacking General [Developers Only]] dinc2010:
After getting annoyed with restarting PoGo few time today I decided to flash stock boot.img and now phone wont boot again. Keeps getting the message "Your device is corrupt" and then goes into Google in white letters and stays stock in there. :(
[Android Software/Hacking General [Developers Only]] jerethi:
Thank you for all of your help! One final question - I see that there are a number of folders with img files in the build bot link in the original post. What are those?

---------- Post added at 09:24 PM ---------- Previous post was at 09:13 PM ----------

Thank you for your assistance! I have just one last question. The link to the build bot in the original post contains folders with links to various img files. What are those?
[Android Software/Hacking General [Developers Only]] androcraze:
I'm seeing that you have a Nexus 5X ("Bullhead") listed as one of your devices...

superuser.phh.me/nexus/bullhead/ lists has a number of folders in it that correspond to releases. So you you know your release, you can go into that folder and pull down the ROM image of your choice and flash it via TWRP.

The only problem right now is that if you're current ROM-wise, the build bot missed the October releases. So you'll have to flash the zip insteam of the .img file.

Does that help?
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
Explained directly below the build bot link. Read carefully!
[Android Software/Hacking General [Developers Only]] rmead01:
Root switch? Can you link
[Android Software/Hacking General [Developers Only]] koron393:
https://www.asus.com/zentalk/tw/thread-173542-1-1.html
[Android Software/Hacking General [Developers Only]] Ronfallorock:
Does't works correctly for me :(, moto g xt1032 with AOSP 7.0 rom
[Android Software/Hacking General [Developers Only]] benlm72:
Hi all, and thanks for all your posts.

For me, POGO is still not working after numerous tries. Here is a summary of what I've done :

- using Samsung galaxy s4, optcm13 from JDCTeam

- r266 suihde from phh : SHN is blue, success but with an error message and POGO doesn't work

- modified r266 suhide to set noverity : SHN is blue, fail and an error message about payment

- modified r275 to set noverity : same pb

- either SELLinux permissive or enforcing : no difference for me

I don't know if these elements could help to identify the pb, but I hope !
[Android Software/Hacking General [Developers Only]] Alxoom33:
Why is everyone discussing Root switch, an app posted on a Chinese web site made by developers we don't know!

---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------

It provides and cuts off root acess! What else does it do?

---------- Post added at 05:33 PM ---------- Previous post was at 05:33 PM ----------

Does not seem very safe, to me.

---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------

It should not be posted or discussed on [MENTION=631273]Chainfire[/MENTION]'s thread!

---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------

Also, it's impossible to read this development thread with all of the same, redundant POGO discussions. 20 pages or more each day. We know, POGO doesn't work then it works then it doesn't work...repeat. It should all be on a POGO discussion thread.

---------- Post added at 05:37 PM ---------- Previous post was at 05:37 PM ----------

Rant done! ;) LOL!
[Android Software/Hacking General [Developers Only]] jerethi:
So I flashed the zip file in TWRP, and I seem to be stuck at the Google logo. Did I do something wrong?
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
Post your recovery log. And the options in the config file.
[Android Software/Hacking General [Developers Only]] androidfr33k:
Is there a way to clean uninstall other than re-flashing the boot partition? I am just doing some tests and rather uninstall by whatever instructions are available rather than re-flashing. Thanks!
[Android Software/Hacking General [Developers Only]] dinc2010:
Well I passed SafetyNet and all I did was:

- Unroot and flash stock images for Nexus 6P....keeping data

- flash SuperSU v2.78 SR1 systemless

- flash suhide-v0.55

- adb shell + su + suhide06 fix

- reboot

All is working! PoGo, SafetyNet (green), Android Pay
[Android Software/Hacking General [Developers Only]] jerethi:
I think the issue may be related to my boot.img. I had previously been using a modified boot.img on my 5X because I didn't want to root, but I did want to keep my custom recovery. Before installing phh, I decided to flash stock boot.img. This seems to be what's causing me to freeze at the Google logo. Is there something additional I need to do to flash back to stock boot.img?
[Android Software/Hacking General [Developers Only]] mitchdickson:
Wrong thread.
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
Nope, fastboot flash it should work.
[Android Software/Hacking General [Developers Only]] adrman:
You did the correct thing by flashing the stock boot image first. You were asking about ElX though weren't you? Did you then flash ElX followed by phh? If that's the case, try just the stock boot image and phh first. Post your recovery logs so we can get a look at what's happening though.
[Android Software/Hacking General [Developers Only]] jerethi:
So this is weird. Apparently, flashing the stock boot.img is what's causing me to get stuck at the Google logo. So, this eliminates phh as the problem. Any ideas on why the stock boot.img is doing this? Could the modified boot.img I've been using modified something somewhere that's causing this to break?
[Android Software/Hacking General [Developers Only]] adrman:
Really hard to say. You could just fastboot flash everything from the stock images except userdata and recovery before phh for a fresh start. What's successful for you now, ElX?
[Android Software/Hacking General [Developers Only]] jerethi:
Thanks for sticking with me on this. I ended up flashing system.img and boot.img and was finally able to get past the Google logo. I then flashed phh and successfully achieved root. Woohoo!
[Android Software/Hacking General [Developers Only]] adrman:
Great news. That's how I update every month. I actually don't even bother keeping TWRP on the phone anymore and just fastboot boot it when necessary.
[Android Software/Hacking General [Developers Only]] androidfr33k:
Sorry to bother. Is it possible to include a binary uninstaller in the apk. If the binary installs in the boot partition not sure if that can be done without just flashing a fresh boot.IMG. I know that chain's app does include a binary uninstaller. Thanks
[Android Software/Hacking General [Developers Only]] jerethi:
After successfully rooting, I'm not able to edit my build.prop file. Is this normal behavior?
[Android Software/Hacking General [Developers Only]] garrettsessions:
Follow the OP to edit the config file to install noverity to edit build prop.
[Android Software/Hacking General [Developers Only]] jerethi:
Thanks. Definitely learning as I go here. Is it possible to flash the zip over an existing root, or do I need to start from stock?
[Android Software/Hacking General [Developers Only]] adrman:
If you're using the default "eng" configuration, then yes. You want noverity. Check the op for instructions on editing the config.txt in the superuser.zip.
[Android Software/Hacking General [Developers Only]] jerethi:
Sigh. I tried editing the config file but I seem to be doing something wrong as I'm not able to achieve root anymore. I think I'm editing the file incorrectly. Do you know how the file should be edited so that I can edit build.prop?
[Android Software/Hacking General [Developers Only]] Pkt_Lnt:
Windows editors screw up the EOL (end of line) in editing. Get Notepad++ a free editor that works great. And 7zip will let you extract and repack archives correctly.
[Android Software/Hacking General [Developers Only]] jerethi:
Thanks. I used both programs to edit the config file and I'm still having trouble.

I edited the config file to read as follows:

noverity crypt

Is that correct if I want to be able to edit build.prop?
[Android Software/Hacking General [Developers Only]] jcase:
http://theroot.ninja

Debugging it isn't really possible without custom builds, and can be dangerous, i dont recommend it.
[Android Software/Hacking General [Developers Only]] adrman:
[MENTION=1915408]phhusson[/MENTION] boot-su-eng.img confirmed working for N6P (Angler). All tested root apps (TiBU, Flashify, FX File Explorer, Nova Launcher, Stickmount) seem to be working properly. Thanks for your work.
[Android Software/Hacking General [Developers Only]] r80ies:
I keep on receiving superuser binary out of date. However, I just flashed the latest superuser.zip. any thoughts on why why I am receiving this?
[Android Software/Hacking General [Developers Only]] phhusson:
But the device is indeed rooted?
[Android Software/Hacking General [Developers Only]] r80ies:
No I have lost root. I reflashed superuser.zip but I still get binary out of date.

Edit: Flashed for 2nd time and I have root access again. I am not sure how I lost root access in the first place as I did not update or touch the device for a couple of days.
[Android Software/Hacking General [Developers Only]] bzowk:
Hey Guys -

I try to do my research before posting, but have a newbish question. I've got an AT&T A9 which I've already rooted using the root method pinned to the top of the A9 forums and it works great - however - whenever I try to format an SD for internal storage, it would notify me it was a slow card and result in being corrupted.

I tried flashing supersu 2.62 beta plus used sunshine (& $25) to go s-off as it was suggested that would fix my issue, but neither did. Eventually, I found out that the SD format requires dm-verity to encrypt which is changed in the root method I used - but not the one on this thread.

Long story, short - based on my phone's current state of being rooted with a custom boot.img (before supersu could patch stock one), supersu & twrp installed, and having s-off; it seems I'll need to use the update.zip method, but didn't know where I needed to start / do different to apply it. I'm guessing that I'll at least have to first flash a factory boot.img which I am guessing I can get from extracting the ROM from HTC's site..

Sorry for the long post, but wanted to make sure before I potentially bricked my phone :)
[Android Software/Hacking General [Developers Only]] phhusson:
Hi,

I'm really doubtful SDcard's dm-crypt is linked to dm-verity, but whatever.

Anyway, you're right. To use it, flash factory boot.img, then from TWRP flash the superuser.zip

Edit: Ok I took a look at it again, my guess is that ChainFire delete every encryptable=xxx option in fstab, which disable encryption on SDCard as well.

I don't disable encryption, so that should make it work.
[Android Software/Hacking General [Developers Only]] phhusson:
I've added options to disable dm-verity and encryption, in experimental build, available in http://phhusson.free.fr/superuser-tmp.zip

By default it still only roots and keep dm-verity and encryption, but if you want to change, it, edit the config.txt in the zip

And you can change verity to noverity and crypt to nocrypt so it disable dm-verity, dm-crypt

The first argument is eng/power/user matching the buildbot.

I'd appreciate if someone could test, I have no device with TWRP available ATM.
[Android Software/Hacking General [Developers Only]] phhusson:
I also added "noverity" target in build bot, which has permissive selinux and dm-verity disabled.
[Android Software/Hacking General [Developers Only]] ETi_:
So I was bored last night and decided to try making a new icon for your app.

Any feedback on the design of the icon ? :confused:

I also made a "banner" for the app page in the Google Play Store.

I'm also thinking of a "Dark" mode for the app, the Light-Blue color scheme can be annoying in the dark some times.
[Android Software/Hacking General [Developers Only]] samsungmario:
[MENTION=1915408]phhusson[/MENTION] I am trying to build a boot.img using your scripts so I can root my NVidia Shield Tablet Marshmallow. I am getting the error:

bootimg.sh: line 45: of bootimg-extract: cannot execute binary file. I am using Ubuntu 32 bit. Should I be using a 64 bit Linux OS?

Attached is the original boot.img file - if you can kindly build boot-us-eng.img. Much appreciated.

https://www.dropbox.com/s/yxsgaf835o79n8j/boot.img?dl=0
[Android Software/Hacking General [Developers Only]] Lrs121:
You probably need a 64 bit os. Im looking at it now to see why it may not work.

Edit: I did a test build you can find it on my site https://lrsservers.ddns.net/download/devices/nvidia/shieldtablet-k1/boot/superuser/ -Note: if downloading on a mobile device use firefox and add a permanent certificate exception or it wont download. I am working on moving from a self signed certificate to one from letsencrypt.org
[Android Software/Hacking General [Developers Only]] samsungmario:
Thanks much for this. I will test the images. Cheers.

edit: Tibu works fine now. Thumbs up.
[Android Software/Hacking General [Developers Only]] MikeRL100:
I know this isn't the main focus of this fork, but would it be within reason to ask for full support for security contexts in this Superuser fork? SuperSu provides full support, including a -cn option, not just the limited --context option. I recently contacted a developer of a root application and we determined the issues in his app to stem from that limited support for security contexts. It'd be better if at least this version supported security contexts fully, instead of having to wait until a bunch of apps have issues and each developer codes in a workaround. I hope someone is knowledgeable enough to implement this.
[Android Software/Hacking General [Developers Only]] Lrs121:
Please read the todo section in the readme. https://github.com/seSuperuser/superuser this may or may cover what youre talking about.
[Android Software/Hacking General [Developers Only]] MikeRL100:
Ah, I see it. It's on the todo list.
[Android Software/Hacking General [Developers Only]] phhusson:
What's the difference between -cn and --context?

At the moment, in every cases I've hit of applications using --context/-cn, they didn't actually need it.

My opinion on the matter is that su context should be adapted to every usecase, rather than modifying the policy of other contexts to enable root access.

Anyway. Which application is it? Can I test by myself?

Can you provide logs (logcat -b all)? Does the app use --context? (In which case, is it possible to try without?)
[Android Software/Hacking General [Developers Only]] 3c:
I'm the dev of the app (3C Toolbox, link in signature). I've used the -cn option instead of --context, so I provided an updated APK to MikeRL100 that uses the --context so that it works with Superuser. Changing context is required for many things because root is often not enough since Android is being secured more and more since Lollipop. This can be because of binaries or files have specific context and cannot be used/read/written under the default security context. Furthermore not all files/binaries require the same context. It's often a trial and error method to find out which context can access which files.

FWIW, the app upon starting checks if the device is rooted, and checks if the -cn option is supported (running su -h), if supported it will use that option to run secure commands depending on the feature used. I've modified the app (not yet available on Play Store) to use the --context option instead and it should be available in next update (if it works ok with SuperSU). Any app dev that chose to use the -cn instead of --context will fail to use security context when using Superuser. At the moment (and as far as I know), only SuperSU and Superuser do support changing security context. Superuser still misses (as seen in TODO list) supporting mount master (required for linking folders).

For example, freezing/unfreezing apps do require to use a specific security context. Setting-up Android firewall as well.
[Android Software/Hacking General [Developers Only]] phhusson:
I'm more than well aware of that, since it is the reason of this fork

Yes I really have to put that higher in my todolist...

Wrong and wrong.

I have both Titanium Backup and AFWall+ working WITHOUT changing security context (they try, but I just ignore those parameters for them)

Obviously I had to change SELinux policy to support it, but it's changes I want to do.

Having apps running in *any* context, with total freedom of switching to contexts is dangerous. I want to prevent this as much as possible.
[Android Software/Hacking General [Developers Only]] 3c:
The security context can be changed with the -cn or --context option, manually or automatically.
[Android Software/Hacking General [Developers Only]] PunchUp:
eng noverity crypt
[Android Software/Hacking General [Developers Only]] coolwater22:
can u link me to the super su systemless zip?? I searched and cant seem to find it :(

and by adb shell and su do i flash those or what?
[Android Software/Hacking General [Developers Only]] bezeek:
Everything related to SuperSU is in the SuperSU forum. A search for "systemless" in the v2.78 SR1 thread will advise you to force systemless mode by creating the file /data/.supersu (from recovery) with the contents "SYSTEMLESS=true" before you flash the zip.
[Android Software/Hacking General [Developers Only]] coolwater22:
I just checked in supersu settings and turns out I did it right and had it systemless already lol. thanks for the help since the thread helped me find out if I had supersu systemless or not :)
[Android Software/Hacking General [Developers Only]] yosmokinman:
Great work.

For whatever reason su is not placed in /system/xbin only in /sbin. So Titanium Backup and Adaway can't detect root. Others root apps work fine.

SuperSu 2.78 does place the file there so everything works. That makes me think this is a problem on this side rather than the rom (or maybe TB's and AA's problem?).

Manually copying and pasting su from sbin into xbin fixes the problem.

I'm using the r259 zip (eng noverity nocrypt) with the AOSP 7.0 rom we have for the Nexus 7 2013.

After manually copying to xbin and doing the hosts bind for Adaway everything works :)