Related
I rooted my phone only so I could use AdAway. So once I update the hosts file with AdAway, technically I can disable root and only enable root once a week or so to re-run AdAway and update the hosts file again correct?
So I want to use Android Pay too... I keep reading that if I disable root in SuperSU it'll work, but my Android Pay flat out rufuses to work.
Only other thing I can think of is disabling OEM Unlock. What does that even do? I'm currently running custom recovey (TWRP).
Does OEM Unlock need to remain enabled? Could that prevent Android Pay working when SuperSU root is disabled?
Thanks
If your root method modified /system/ then you will never be able to use Android Pay as it checks this. Even systemless root stopped working with the August security patch. It's why I didn't root my Note 7 when I got it because I figured this out on the 6P. Sad but true.
Is there a way to un-root and re-root quickly? I disabled root in SuperSU but it doesn't help.
All I really want to do is block ads via the host file with adaway (which is how it works right?) And I can enable root every time I want to update the ad block list.
Thanks for reply
I found a few ways to do it on other sections of this forum but they seemed tedious and I haven't really looked since the August patch flarked everything up for folks who want AP. Sorry. I wish I could answer.
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Nblufire12 said:
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Click to expand...
Click to collapse
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
sb1893 said:
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
Click to expand...
Click to collapse
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Nblufire12 said:
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Click to expand...
Click to collapse
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
sb1893 said:
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
Click to expand...
Click to collapse
is your build.prop edit still working on oreo for og pixel xl 1?
Nblufire12 said:
is your build.prop edit still working on oreo for og pixel xl 1?
Click to expand...
Click to collapse
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
I've been considering switching to the Pixel XL or the 2XL and this is a critical factor for me. From what I gathered from the 2XL forum, this wasn't working. I'm going to see if I can track down if the same Magisk tether module exists for the 2XL. If anyone knows ahead of time, I'd like to know.
Nblufire12 said:
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
Click to expand...
Click to collapse
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
sb1893 said:
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
Click to expand...
Click to collapse
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Nblufire12 said:
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Click to expand...
Click to collapse
I'd recommend following one of the many guides found on XDA. Here is the one I used to get up and running on magisk...you will need to determine which portions of the guide are relevant to your situation and needs.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Good luck!
S
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
scoobysnack said:
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
Click to expand...
Click to collapse
Interesting. I am unable to edit build.prop with Root Explorer (which does have Root Privs). Whenever I open the file for edit in Text Editor within Root Explorer, it allows me to edit the file, but when I "Save Changes and Exit" or "Save Changes" and then exit...those changes are not retained. The timestamp on the build.prop file is unaltered as is the file size. I wonder what the difference is that allows you to edit your build.prop but prevents me from changing mine...I have poked around on the forums and the magisk threads and haven't been able to figure it out. I stopped researching when I discovered the ability to insert those settings at boot time via the magisk modules and decided that was a viable solution (maybe better as it leaves build.prop stock and unchanged.)
Thanks,
S
I click "Save Changes" then I click "Save and Exit" it will say the original file is name .bak
Hi there!
First of all info about my device
Bootloader UNLOCKED via HTC Dev - OK
TWRP v3.2.3-0
SuperSU Free v.2.82-SR5
Android 7.0 - Sec. Patch Level April 1, 2017
MagiskManager-v5.8.3
I just want to 'hide' my root in order to play PoGo, Update some apks that won't, use my banking and payment apps, etc.
I followed an article to install MagisK on rooted devices, and everything went smooth till I was asked to 'download' / 'install from web' from the MagiskMgr. Gave me an error and never installed. Same result downloading the .zip and trying to flash it from TWRP. No f&%$#g way...
If ANY of you know a way of installing Magisk / making it install OK on such a device, I'd be more than grateful.
Thanks in advance,
J.
jsbouchez said:
Hi there!
I just want to 'hide' my root in order to play PoGo, Update some apks that won't, use my banking and payment apps, etc.
J.
Click to expand...
Click to collapse
Anyone?
Hi,
I have read and tried many things on the Internet to be able to pass safety on my Moto G5 (XT1676) under LOS 17.1 and then 18.1 but I did not managed to make it pass safetynet tests...
Using Magisk latest version and Hide/Props (fingerprints) makes in fact things worse than just LOS installed.
With LOS installed, I have only "CTS profile" failed but after using Magisk, depending on modules used, CTS profile is still "failed" and other categories are "failed" too.
Does anyone know how to pass safetynet tests on G5 (cedric) as of May 2021 with LOS 18.1 from Jarl-Penguin (Which tools/version/settings) ?
I just want to be able to use my banking app... I do not need to root my phone.
If not possible, my guess is I have to go back to stock ROM and to relock bootloader ?... I have tried once and I lost IMEIs... which I only managed to recover by reflashing LOS ! (other methods found on XDA did not apply and/or work for me)
Thank you
alxsj said:
Hi,
I have read and tried many things on the Internet to be able to pass safety on my Moto G5 (XT1676) under LOS 17.1 and then 18.1 but I did not managed to make it pass safetynet tests...
Using Magisk latest version and Hide/Props (fingerprints) makes in fact things worse than just LOS installed.
With LOS installed, I have only "CTS profile" failed but after using Magisk, depending on modules used, CTS profile is still "failed" and other categories are "failed" too.
Does anyone know how to pass safetynet tests on G5 (cedric) as of May 2021 with LOS 18.1 from Jarl-Penguin (Which tools/version/settings) ?
I just want to be able to use my banking app... I do not need to root my phone.
If not possible, my guess is I have to go back to stock ROM and to relock bootloader ?... I have tried once and I lost IMEIs... which I only managed to recover by reflashing LOS ! (other methods found on XDA did not apply and/or work for me)
Thank you
Click to expand...
Click to collapse
You can try flashing MicroG via TWRP (suggest the NanoDroid version plus their patcher) BUT you will have to uninstall Magisk, since I never knew how to pass the SafetyNet using a custom URL with in the settings of MicroG.
Tiki Thorsen said:
You can try flashing MicroG via TWRP (suggest the NanoDroid version plus their patcher) BUT you will have to uninstall Magisk, since I never knew how to pass the SafetyNet using a custom URL with in the settings of MicroG.
Click to expand...
Click to collapse
Thank you for your answer. Have you ever made it work this way or is it just a guess ?
alxsj said:
Thank you for your answer. Have you ever made it work this way or is it just a guess ?
Click to expand...
Click to collapse
Last time check it did (when i posted that), but AFAIK Google did some changes into SafetyNet and is not working anymore.
Tiki Thorsen said:
Last time check it did (when i posted that), but AFAIK Google did some changes into SafetyNet and is not working anymore.
Click to expand...
Click to collapse
OK. Thank you for the up-to-date information !
The latest version of MicroG now passes includes a Safetynet check and it passes.
Hi, with this tuto (https://forum.xda-developers.com/t/...motorola-moto-g5-stock-to-android-11.4524049/) I fail CTS check but Netflix and Disney+ work
As the title implies, the universal safetynet fix 2.2.0 has been released for those that want root + Google Pay + Netflix + banking apps + etc
Release v2.2.0 (Zygisk) ยท kdrag0n/safetynet-fix
Changes Ported module to Zygisk Fixed screen-off Voice Match in Google Assistant Fixed poor microphone quality with Voice Match enabled on Pixel 5 Fixed At a Glance weather display on Android 12 F...
github.com
Yep thanks. Just uninstalled Alpha channel with Riru and USNF v2.1.1 and installed official Canary with Zygist and USNF v2.2. Passing all checks and all root detecting apps are working.
Just for info: root detection and SN are 2 different things ... all my banking apps work OK once they are in Magisk's DenyList, so they check for root (e.g. check su binary or check if com.topjohnwu.magisk exists) but don't check SN. Google pay (which I personally do not use) does not work (only works with SN). Netflix needs SNF for it to appear on the Play store but does not care about root. Of course just unlocking the BL means that you have tampered with the device and that will make SN fail (even when youy are still unrooted).
foobar66 said:
Just for info: root detection and SN are 2 different things ... all my banking apps work OK once they are in Magisk's DenyList, so they check for root (e.g. check su binary or check if com.topjohnwu.magisk exists) but don't check SN. Google pay (which I personally do not use) does not work (only works with SN). Netflix needs SNF for it to appear on the Play store but does not care about root. Of course just unlocking the BL means that you have tampered with the device and that will make SN fail (even when youy are still unrooted).
Click to expand...
Click to collapse
Just wondering before I install this and try it is it safe to use? I understand there is a risk just like anything linked to rooting. However based on this posted you make it sound like this isn't needed, so just making sure before I install it, bc I do use Gpay.
Also is it the same as:
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
Some banking apps check for SN, other's don't. Most banking apps check for root nowadays ... Anyway does not "harm" if you install it (on the contrary). You will need it for GPay.
collegencmc said:
Just wondering before I install this and try it is it safe to use? I understand there is a risk just like anything linked to rooting. However based on this posted you make it sound like this isn't needed, so just making sure before I install it, bc I do use Gpay.
Also is it the same as:
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
Click to expand...
Click to collapse
It is the same as this but is now free instead of behind the Patreon/one time paywall. I can confirm it works with LSposed and I'm passing Safetynet.
Great thanks for the info on this!