Develop Bugs

Safetynet API tripping for systemless root?

One of the biggest reasons why I used systemless root and stock Android was so that I could use Android Pay. All was fine and dandy for the longest time, I was passing the checks regularly.
Sometime between yesterday and last week, Safetynet Playground has been telling me I failed to pass the test. When I uninstall systemless root SuperSU it goes back to green for me. This seems to indicate that Google has updated Safetynet to detect systemless root.
For those who might not know: No there was no need to disable root before using Android Pay. No, disabling it now does not help. Yes, this worked, and I've been using it for a while now.
Can anyone else confirm this for me?

formula91 said:
One of the biggest reasons why I used systemless root and stock Android was so that I could use Android Pay. All was fine and dandy for the longest time, I was passing the checks regularly.
Sometime between yesterday and last week, Safetynet Playground has been telling me I failed to pass the test. When I uninstall systemless root SuperSU it goes back to green for me. This seems to indicate that Google has updated Safetynet to detect systemless root.
For those who might not know: No there was no need to disable root before using Android Pay. No, disabling it now does not help. Yes, this worked, and I've been using it for a while now.
Can anyone else confirm this for me?
Click to expand...
Click to collapse
I can still add cards to android pay. I used SuperSU 2.64 and removed /su/xbin today and had no issues. Just tried that app too and I passed.

Keithn said:
I can still add cards to android pay. I used SuperSU 2.64 and removed /su/xbin today and had no issues. Just tried that app too and I passed.
Click to expand...
Click to collapse
Are you on 6.0.1?
And could you clarify what you mean by removing /su/xbin? I see no such folder.
There isn't a /system/su folder
There is an /su/xbin_bind folder though.
Super edit: deleted /su/xbin_bind
Y I no read SuperSU post?
I thought it wouldn't cause problems. My bad

FireTV 1 unrooted?

Hi all,
I'd previously rooted, installed recovery, etc on my FireTV version 1. Everything was working great, and I thought I'd disabled updates. I turned it on recently and It somehow lost root. Everything is still installed, but can't open SuperSU, towelroot says the device isn't supported. Still says that Xposed is installed with the framework though.
The system says I'm now on 51.1.4.1_user_514013920 for some reason. Checking for system update still gives an error. What went wrong, and is there any way to fix it?
@AFTVNews, I'm mainly looking at you

Does anyone know?

If you disabled updates its probably the fact that the fire tv has updated its self, im afraid thats why su (root) isnt working & your device isn't supported because your firmware has upgraded. You have no way to root at the moment in time unless a os5 root for AFTV gen1 is created sometime in the near future? It is possible because Rbox is making a Os5 root for Gen 1.... But i think you need root already for that? My advice would be if you still want root, get a AFTV 2 while root is still possible & root/block updates & wait for the new recovery & rom being developed by Rbox which fingers crossed should be very near to be released. I still cant get over why you would want to unblock updates for when you had root & exposed framework? oh well whats done is done now.
If this helps press that thanks button

If he install clockword mod and if he can still get into it, couldn't he flash the latest rom and get root back?

That's very confusing?
Disabling updates should've been the first thing you did after rooting (presumably a long time ago if you have gen 1.)
Disabling updates, successfully or not, shouldn't've caused you to lose root. If you have CWM, your aftv should not be able to receive a stock update. Of course towel root won't work because your firmware is based on stock software that is not rootable. Are you certain you did nothing else other than disable updates?
I'm basing all of this off the assumption you have CWM. If so then just push the same firmware you currently have installed to /sdcard and flash it again. Install busybox and I'd think you'd be ok. You probably already know this but aftvnews has all rbox's prerooted roms.

Maybe you only disabled ota on your router? Have you taken it anywhere else? Or got a new router?
Sent from my SM-G900F using Tapatalk

Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...

ldeveraux said:
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
Click to expand...
Click to collapse
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk

deanr1977 said:
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.

ldeveraux said:
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
Click to expand...
Click to collapse
You're not understanding. First, the firmware you have MUST have boot menu installed. Therefore you can choose to boot recovery from there. OR connect adb and reboot recovery. Adbfire simplifies this...
You should be fine to flash a prerooted rom and it should fix whatever got messed up.
Again, theres NO way youre running stock because im fairly certain rbox's recovery wont allow the installation. Theres an issue with you su no doubt but im thinking youre still rooted.

Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.

AFTVnews.com said:
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
Click to expand...
Click to collapse
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?

ldeveraux said:
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
Click to expand...
Click to collapse
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3

AFTVnews.com said:
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
Click to expand...
Click to collapse
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?

ldeveraux said:
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
Click to expand...
Click to collapse
I haven't looked into the Google Play Store in a while. I plan to update my guide once Fire OS 5 is released to older devices, since any changes I make now likely won't work after the update.

Android pay on our OP3 with root?

Need help! Don't know if it's been answered. I've checked and haven't going anything. I've tried the chmod 751 in terminal and everything systemless and nothing has worked. Echo command did nothing.

It got patched yesterday. AP doesn't work anymore on rooted devices. Not sure if it's against the rules to link reddit but check r/android for updates like this

katsumex said:
It got patched yesterday. AP doesn't work anymore on rooted devices. Not sure if it's against the rules to link reddit but check r/android for updates like this
Click to expand...
Click to collapse
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?

It should work with systemless root, but you have to disable xposed.

lparcshinoda said:
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?
Click to expand...
Click to collapse
So if you haven't purchased anything yet, try to. It probably won't work. It fails on two parts, me trying to add a credit card after a factory reset and when I had the credit card on it and tried using a touch pay thing.

daClaus said:
It should work with systemless root, but you have to disable xposed.
Click to expand...
Click to collapse
As @katsumex stated, it was patched.
Thread here if you're curious: http://forum.xda-developers.com/oneplus-3/help/oos-3-2-2-safetynet-t3427833

Works fine systemless without xposed enabled

Thanks a lot guys. Well I am systemless and it did t work and this was before the patch. Also don't have exposed and still didn't work. Guess I'll be waiting for a newer setup. Urghhh. To root or not to root?, in the name of Android Pay!!!

lparcshinoda said:
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?
Click to expand...
Click to collapse
Any specific steps to set it up? I mean I am systemless and I don't have Xposed. Still nothing. Maybe I forgot to set something.

SuperSU v2.76 on 3.2.1 stopped working for me yesterday. Have over 20 transactions where it has. According to the play store the app itself last updated 11th July. And I have transactions done after. So whatever's changed is not on the app.
Btw, i will try systemless and report back.

TheLoverMan said:
Works fine systemless without xposed enabled
Click to expand...
Click to collapse
Not anymore.

Correct. The safetynet check no longer passes. The check is performed server side, so there is really no way to work around it at the moment, unless you fully unroot of course. So, even a fully proper systemless root method will fail. Oh well. I have never, nor ever will most likely, use Android Pay anyway. Lol. I was just curious why it wasn't working...so apparently Google has caught on for now. This goes for all phones too, not just the OP3. Good luck!

Tethering

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

Pixel 3 XL install Netflix on rooted device

Hi, I rooted my pixel, after that I tried to install Netflix all from the web but it says that my device is not supported. I tried to hide magisk and even google play and google play services and it didn't worked. How can I install the latest Netflix app on my device ? Thanks

You can't at the moment. It looks like the Play Store is seeing something that neither Magisk Hide or even a cloaked unlocked bootloader can hide. My guess is that it is an attestation similar to how Google Pay is working to fight root and unlocked bootloaders. Clearly, the Netflix help page that claims that certification is the kicker is dead wrong at this point and as of a moth or two ago. Maybe a return to stock, re-lock of your bootloader and facory reset (which locking your BL would do anyways) might get you there, but I am not about to do that. For now, sideload the most recent one off of APK Mirror and if you need to update due to some lost functionality, use one from there when it becomes available.

install netflix then root

pacman photog said:
install netflix then root
Click to expand...
Click to collapse
True, but Play Store will not update Netflix after that one time. I have 4 devices installed that way, and since the Play Store version with 3.14 in it the updates will not show. One of the devices hadn't got 3.14 when the others had and it got the Netflix update two ago. The others didn't get it. That device did not get the last update nor did the others. I suggested in another thread possibly uninstalling the Play Store o get it to revert to the original version and then checking to see if Netflix is available. Even if it works, I am not about to keep an older version of Play Store or have to do that every time Netflix updates. The older version of Netflix is working fine.

My Netflix is on version 7. Not sure what you speaking about version 3

pacman photog said:
My Netflix is on version 7. Not sure what you speaking about version 3
Click to expand...
Click to collapse
I was talking about the Play Store version itself (Play Store>settings).

#1 wait for final q and root.
#2 Netflix doesn't need update lol
#3 my bad lol

What I find fascinating about this is I assumed it was because the bootloader was unlocked. But, flashing the Android Q Beta, allows you to install Netflix with no issues unlocked. But, if you go back and flash P? It's no longer an option. So my theory is out the window..

jbarcus81 said:
What I find fascinating about this is I assumed it was because the bootloader was unlocked. But, flashing the Android Q Beta, allows you to install Netflix with no issues unlocked. But, if you go back and flash P? It's no longer an option. So my theory is out the window..
Click to expand...
Click to collapse
Rooted both ways, neither way? Safetynet?

sliding_billy said:
Rooted both ways, neither way? Safetynet?
Click to expand...
Click to collapse
Rooted, and non rooted. SafetyNet passes fine. I observed this on fresh installations. If I do a fresh factory install of P, I can't install Netflix even before rooting. If I flash stock P, and lock the bootloader? I can install Netflix.
Now with Q? Bootloader unlocked, factory flash Q, can install Netflix. It's very interesting that this doesn't happen with a factory flash of P..

jbarcus81 said:
Rooted, and non rooted. SafetyNet passes fine. I observed this on fresh installations. If I do a fresh factory install of P, I can't install Netflix even before rooting. If I flash stock P, and lock the bootloader? I can install Netflix.
Now with Q? Bootloader unlocked, factory flash Q, can install Netflix. It's very interesting that this doesn't happen with a factory flash of P..
Click to expand...
Click to collapse
This is leading me to believe my previous thoughts about Netflix on the Play Store. I think the Play Store is looking at SafetyNet/Device Certified 1st regardless of device. If that passes, move to the device/OS and see if it is listed for additional checking. Since Q has not been released publicly yet, I am guessing that the check goes no further and shows Netflix. This will probably change at public Q release if not sooner, and updates will cease even if the program is installed already. I believe my Tab S2 713 simply is not listed for additional checking since it is rooted and has an unlocked BL but passes SafetyNet. Play Store shows available and provides updates.
The big question is what additional testing is being performed. I doubt it is checking for unlocked BL unless the kernel masking of unlocked BL simply doesn't work anymore. I tend to think it is a database attestation check similar to what GPay does. Finding that or using MagiskHide Props Config module to set a working fingerprint might work long term, but since older versions of Netflix (already installed on all of my devices) are working OK without updating I am in no hurry to do too much testing.

sliding_billy said:
This is leading me to believe my previous thoughts about Netflix on the Play Store. I think the Play Store is looking at SafetyNet/Device Certified 1st regardless of device. If that passes, move to the device/OS and see if it is listed for additional checking. Since Q has not been released publicly yet, I am guessing that the check goes no further and shows Netflix. This will probably change at public Q release if not sooner, and updates will cease even if the program is installed already. I believe my Tab S2 713 simply is not listed for additional checking since it is rooted and has an unlocked BL but passes SafetyNet. Play Store shows available and provides updates.
The big question is what additional testing is being performed. I doubt it is checking for unlocked BL unless the kernel masking of unlocked BL simply doesn't work anymore. I tend to think it is a database attestation check similar to what GPay does. Finding that or using MagiskHide Props Config module to set a working fingerprint might work long term, but since older versions of Netflix (already installed on all of my devices) are working OK without updating I am in no hurry to do too much testing.
Click to expand...
Click to collapse
Same here.. it's not a deal breaker, it's just frustrating. There's another app from the Playstore that does this from T-Mobile. T-Mobile Device Unlock (or whatever it's called). What made me really raise my eye-brows is during the initial setup of the phone after a fresh flash. In P, during initial setup, when you get to 'install additional apps' it's not listed. If I flash Q, go through setup, it's listed in additional apps.. It's very strange.

jbarcus81 said:
Same here.. it's not a deal breaker, it's just frustrating. There's another app from the Playstore that does this from T-Mobile. T-Mobile Device Unlock (or whatever it's called). What made me really raise my eye-brows is during the initial setup of the phone after a fresh flash. In P, during initial setup, when you get to 'install additional apps' it's not listed. If I flash Q, go through setup, it's listed in additional apps.. It's very strange.
Click to expand...
Click to collapse
Too funny about the T-Mobile device unlock. I had that show up on my phone a few weeks ago, and I deleted it. I have 5 devices on T-Mobile, and that was the only one that it showed up on. I have seen that app before since my boys had a prepaid T-Mobile phone years ago that had that app. The app not showing in additional apps makes sense since it doesn't show up in Play Store from the device and if you search it on the PC it will say not compatible with any of your devices or compatible with some of your devices. I actually chatted with Netflix a little while ago and played stupid about the whole thing. The agent seemed to think that as long as your device was certified the app would show.

jbarcus81 said:
Rooted, and non rooted. SafetyNet passes fine. I observed this on fresh installations. If I do a fresh factory install of P, I can't install Netflix even before rooting. If I flash stock P, and lock the bootloader? I can install Netflix.
Now with Q? Bootloader unlocked, factory flash Q, can install Netflix. It's very interesting that this doesn't happen with a factory flash of P..
Click to expand...
Click to collapse
Glad I found you. That's exactly what I came on here to find -- glad someone else noticed like I did.

vonDubenshire said:
Glad I found you. That's exactly what I came on here to find -- glad someone else noticed like I did.
Click to expand...
Click to collapse
Where did you get the Netflix app? Play store says not compatible with my device. Rooted QB5.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 07:43 PM ---------- Previous post was at 07:27 PM ----------
Daisymae said:
Where did you get the Netflix app? Play store says not compatible with my device. Rooted QB5.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Forget above. My bad.
Sent from my [device_name] using XDA-Developers Legacy app

yeh appareently APK Mirror doesn't host the Netflix app anymore either, so get it from another site.

Something interesting... Did a clean install of July Pie.. Was using Q but was having some random issues with GPS.. Anyways, I installed the APK and now I'm being told by the application itself that it's not compatible with my device.. WTH!?!?!?? Can't even side-load now??

Pretty sure the Android DRM (Digital Rights Management) Framework does the Netflix locking. There's a magisk module for DRM Bypassing for Netflix

jbarcus81 said:
Something interesting... Did a clean install of July Pie.. Was using Q but was having some random issues with GPS.. Anyways, I installed the APK and now I'm being told by the application itself that it's not compatible with my device.. WTH!?!?!?? Can't even side-load now??
Click to expand...
Click to collapse
You also may need to spoof the device fingerprint. I am on Q so it lets me download right now no matter what. I just spoofed fingerprint for G Pay on top of the database

Just stumbled upon this thread and just wanted to comment. I'm rooted with an unlocked bootloader and I've had no issues with installing Netflix of having it update when needed. I've even had to uninstall and reinstall once with no issue.