Related
I have a US unlocked HTC 10. I'm S-Off, but the bootloader is locked and I'm not rooted. Using totally stock software. Android Pay had been working fine up until a few weeks ago, but now it stopped working and my Play Store settings says my phone is "Uncertified" under "Device certification".
There were a few updates a few weeks ago. I'm wondering if one of them caused the device to be Uncertified when it is s-off? Or maybe it was a recent update to Android Pay or Play Services?
Can anyone verify that just having s-off breaks Android Pay?
Yea might be because of that s-off flag.... Google is stupid so many times
Sent from my HTC 10 using XDA Labs
xanadu1979 said:
I have a US unlocked HTC 10. I'm S-Off, but the bootloader is locked and I'm not rooted. Using totally stock software. Android Pay had been working fine up until a few weeks ago, but now it stopped working and my Play Store settings says my phone is "Uncertified" under "Device certification".
There were a few updates a few weeks ago. I'm wondering if one of them caused the device to be Uncertified when it is s-off? Or maybe it was a recent update to Android Pay or Play Services?
Can anyone verify that just having s-off breaks Android Pay?
Click to expand...
Click to collapse
This might not help you in your case, but I'm s-off with locked bootloader and fully stock other than rooted with Magisk, and I pass safetynet.
DeeZZ_NuuZZ said:
Yea might be because of that s-off flag.... Google is stupid so many times
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Not so sure about that. S-On/Off is an HTC lock, not Google.
pomponazzo said:
Not so sure about that. S-On/Off is an HTC lock, not Google.
Click to expand...
Click to collapse
Yes but Google has access to everything, so they can check whether you've modified it or not, but there are also some posts on the web that complete stock phones even non HTC can't use Android pay because of play store shows uncertified device. Don't blame HTC or so for that. It's Google ****
Sent from my HTC 10 using XDA Labs
I used Android Pay successfully yesterday. S-OFF, locked, ResurrectionRemix, Magisk.
tabp0le said:
I used Android Pay successfully yesterday. S-OFF, locked, ResurrectionRemix, Magisk.
Click to expand...
Click to collapse
Was this at a NFC payment terminal?
I'm on the latest Lineage 14.1 5/04 nightly and I pass Safety Net with the use of Magisk. I'm able to use Android Pay within the Uber app, but NFC terminal payments at stores don't work for me on thing but the stock HTC Sense software.
Edit: I forgot to mention I'm S-On and bootloader's unlocked.
tabp0le said:
I used Android Pay successfully yesterday. S-OFF, locked, ResurrectionRemix, Magisk.
Click to expand...
Click to collapse
yea, because magisk. but he's full stock with s-off and locked. for some ppl it might happen. not just for HTC, but it's very rarely that a stock htc user has this issue
tibere86 said:
Was this at a NFC payment terminal?
I'm on the latest Lineage 14.1 5/04 nightly and I pass Safety Net with the use of Magisk. I'm able to use Android Pay within the Uber app, but NFC terminal payments at stores don't work for me on thing but the stock HTC Sense software.
Edit: I forgot to mention I'm S-On and bootloader's unlocked.
Click to expand...
Click to collapse
Yeah it was at a terminal.
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.
Has anyone been able to get Netflix to work on a rooted device?
does anyone have any tricks for getting Netflix to work? I am on 10. 0.9, 1905 variant. Rooted with magisk
I'm rooted and Netflix works fine?
ChongoDroid said:
I'm rooted and Netflix works fine?
Click to expand...
Click to collapse
Really? I get an error saying not compatible with this device
Cowbell_Guy said:
Really? I get an error saying not compatible with this device
Click to expand...
Click to collapse
I forgot to mention I'm on aosip so maybe that's why.
Go into magisk hide and select Netflix from the list. Then go into magisk settings and click hide magisk manager from list.
Then wipe cache and data on Netflix and try that.
Cowbell_Guy said:
Really? I get an error saying not compatible with this device
Click to expand...
Click to collapse
while opening the app or in playstore?
Working here with rooted oos op7t for past 5 months.
Both, I keep getting an error saying it is not compatible with my device
Cowbell_Guy said:
Both, I keep getting an error saying it is not compatible with my device
Click to expand...
Click to collapse
Strange that it don't work for you, working without a problem on my latest oos beta 7t.
Have you tried latest builds from apkmirror.com or try a older build and test
Regards ysco..
Disable netflix app in setting and install another netflix via apk file, it will work
For me (European version) Netflix was pre-installed. In general: to see and install Netflix you need to pass SafetyNet. This means enabling Magisk Hide, clearing the data of the Play Store (then it should way "official device" in the Settings menu and maybe a patched custom kernel though I'm not sure if the latter is necessary. After that, I can see Netflix and also install it.
1 - Make sure you're aren't tripping the safetynet test.
2 - Make sure you have hidden magisk manager and magisk from detections
If you still find netflix incompatible, clear data and cache of play store and Google play services and reboot.
Macusercom said:
For me (European version) Netflix was pre-installed. In general: to see and install Netflix you need to pass SafetyNet. This means enabling Magisk Hide, clearing the data of the Play Store (then it should way "official device" in the Settings menu and maybe a patched custom kernel though I'm not sure if the latter is necessary. After that, I can see Netflix and also install it.
Click to expand...
Click to collapse
This worked with me, w/o the customer kernel - also EU version. Thanks!
Netflix(release 4.16.0) is working on my Galaxy S8 rooted by Magisk.
You need to add a 'liboemcrypto disabler' module to your device using Magisk. And the latest release of Netflix may not be working on rooted device.
Recommended to use 4.x
The most important is SafetyNet.
(After rooting with Magisk my test fails so I used MagiskHide Props Config and got new fingerprint certificat which allowed me to pass test)
As long as you still pass SafetyNet you are going to "see" Netflix in PlayStore and get updates. Of course use also Magisk Hide and select Google Play services.
Netflix latest, updated from store 7.73.1
Tapatalk via OnePlus 7T
good !!!
Sent from my iPhone using Tapatalk
What widevine level are you getting? Are you L1 or L3? Even if you can get Netflix installed you may be stuck with 480p due to Widevine L3.
Exactly, Netflix and other OTT apps work fine but Widevine drops to L3 bringing down the max supported resolution to just 480p.
L3+root isn't possible IMO.
Lost Dog said:
What widevine level are you getting? Are you L1 or L3? Even if you can get Netflix installed you may be stuck with 480p due to Widevine L3.
Click to expand...
Click to collapse
It's impossible to get L1 on a 7T with an unlocked bootloader as of now... As a general rule of thumb, a bootloader unlock will break the L1 certification. There are some exceptions to this rule though. Some Xiaomi devices and the OnePlus 8 series (on newer firmware) are able to maintain it.
I'm on an LG v20 that I just flashed LineageOS 17.1, and I couldn't get SafetyNet passing. I followed this process for props :
Oh and I'm running Gamma Kernel v20.0, if that matters to anyone. Hope this helps! (This is in addition to MagiskHide stuff of course).
Cowbell_Guy said:
Really? I get an error saying not compatible with this device
Click to expand...
Click to collapse
same
vibraniumdroid said:
It's impossible to get L1 on a 7T with an unlocked bootloader as of now... As a general rule of thumb, a bootloader unlock will break the L1 certification. There are some exceptions to this rule though. Some Xiaomi devices and the OnePlus 8 series (on newer firmware) are able to maintain it.
Click to expand...
Click to collapse
Hello!
I will receive a oneplus 9 pro next week and wonder if i shall root it or not. I want to use titanium backup and a few other apps that need root permission, but i also dont want to loose widevine level 1 for netflix and amazon video in hd, want to use my banking app and mcdonalds app.
i havent followed the magisk/root discussion for maybe a year or two (used a unrooted stock phone), so i am not up to date how things are at the moment.
just to be clear, please can someone answer the following questions:
1.) is unlocking bootloader (no root afterwards) enough to loose widevine level 1? can level 1 be gained again when bootloader is locked again or is lost permanent (like triggering knox with samsung).
2.) any problems with mcdonalds app and magisk? google pay?
after reading to the internet on the subject totday, i get the impression that rooting nowadays causes more problems thn benefits, but maybe i get a wrong impression.
flotsch1 said:
Hello!
I will receive a oneplus 9 pro next week and wonder if i shall root it or not. I want to use titanium backup and a few other apps that need root permission, but i also dont want to loose widevine level 1 for netflix and amazon video in hd, want to use my banking app and mcdonalds app.
i havent followed the magisk/root discussion for maybe a year or two (used a unrooted stock phone), so i am not up to date how things are at the moment.
just to be clear, please can someone answer the following questions:
1.) is unlocking bootloader (no root afterwards) enough to loose widevine level 1? can level 1 be gained again when bootloader is locked again or is lost permanent (like triggering knox with samsung).
2.) any problems with mcdonalds app and magisk? google pay?
after reading to the internet on the subject totday, i get the impression that rooting nowadays causes more problems thn benefits, but maybe i get a wrong impression.
Click to expand...
Click to collapse
Use the canary builds of Magisk, enable MagiskHide, and toggle the apps in question, and you're golden. Also, just to be sure, toggle it on for Google stuff like the Google app, Google Play Store, Google Play Services, Google Services Framework, Netflix, McDonald's, GPay, and any other banking or streaming subscription apps. Might want to have Magisk hide its self by changing the app name and signature as well.
GuyInDogSuit said:
Use the canary builds of Magisk, enable MagiskHide, and toggle the apps in question, and you're golden. Also, just to be sure, toggle it on for Google stuff like the Google app, Google Play Store, Google Play Services, Google Services Framework, Netflix, McDonald's, GPay, and any other banking or streaming subscription apps. Might want to have Magisk hide its self by changing the app name and signature as well.
Click to expand...
Click to collapse
thank you for the information.
so i will definitely not loose widevine l1 with unlocking bootloader and root?
to hide magisk itself (change name and signature), i just need to turn this option on in magisk and not need to do this in a manual way?
flotsch1 said:
thank you for the information.
so i will definitely not loose widevine l1 with unlocking bootloader and root?
to hide magisk itself (change name and signature), i just need to turn this option on in magisk and not need to do this in a manual way?
Click to expand...
Click to collapse
Correct, by default it will change to a "default" app icon and rename itself to "Settings" but you can easily still tell it from the device's own system Settings app.
one last question.
following this root instruction https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-11-2-7-7.4252373/ , do i have to use the provided boot images? i feel safer to download the full ota from oneplus official site and extract payload.bin and then use payload dumper to get a boot.img.
flotsch1 said:
one last question.
following this root instruction https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-11-2-7-7.4252373/ , do i have to use the provided boot images? i feel safer to download the full ota from oneplus official site and extract payload.bin and then use payload dumper to get a boot.img.
Click to expand...
Click to collapse
If you are leery of using someone else's boot.img, feel free to do that if you'd like. But regardless, be sure to boot the image, don't flash it. Booting it not only gives you the temporary root access to install Magisk yourself, but also ensures that the patched boot.img is actually valid.
v23 has a fix for SafetyNet API. It looks like that supersedes anything from the last canary/debug builds, so it's probably safe to stick with that. Everything else is the same, though.
GuyInDogSuit said:
v23 has a fix for SafetyNet API. It looks like that supersedes anything from the last canary/debug builds, so it's probably safe to stick with that. Everything else is the same, though.
Click to expand...
Click to collapse
V23?
flotsch1 said:
V23?
Click to expand...
Click to collapse
Latest stable Magisk build. I'm saying you won't need to mess with canary/debug.
When you turn on hide then hide the app the in the settings then your allowed to do anything you like but also hide it in the menu of magisk then your all done don't flash to much crap and magisk hide module is not really finished yet for this device good luck
I rooted it the second i got it
And don't use canary builds of magisk only if you want to run your phone very unstable i recommend the stable version
thanks alot for the information.
i still hazzle to root. i had a oneplus 3 2 years ago and had magisk root/custom rom/twrp, but i also had issues on regular basis and spent alot of time on xda and with flashing. dont know if i want this again or just a phone that works.
and just to be sure:
in case i loose my widevine level 1 because of root or bootloader unlock: will it come back when locking bootloader again and/or unroot. or will it be level 3 forever?
Wildvine L1 is not always retained when unlocking the bootloader. If I unlock mine, I go to L3 every single time, but when I lock it back, I go back to L1. I've tested this 3 times and it happened all 3 times.
flotsch1 said:
thanks alot for the information.
i still hazzle to root. i had a oneplus 3 2 years ago and had magisk root/custom rom/twrp, but i also had issues on regular basis and spent alot of time on xda and with flashing. dont know if i want this again or just a phone that works.
and just to be sure:
in case i loose my widevine level 1 because of root or bootloader unlock: will it come back when locking bootloader again and/or unroot. or will it be level 3 forever?
Click to expand...
Click to collapse
Well to be honest I never had that problem and i need to have my binance hidden as well and everything works well but with some games like slime hunter i really need to hide magisk it self too from the settings but when you do they everything will be working okay. And so far I have seen with magisk hide module what you can download is that there are no keys yet for using in op9p (could be changed didn't check it for a while now)
Hi!
Didn't rooted a phone since a long time, I discovered I couln't afterward install Netflix from the Playstore. Found out it's because of the unlocked bootloader, and also found the link to download the APK from Netflix directly: https://help.netflix.com/en/node/12983#android
Unfortunatelly, after installing it with adb, it still refuse to open, "this device isn't supported"
Is there any workaround?
EDIT: the netflix.com version didn't worked, but the latest "nodpi" beta one (v8.7.0_build_8_40058-40058) from apkmirror worked perfectly withtout the need for SafetyNet or anything else.
I think this is a question that really needs confirming by having a rooted user check the playback settings in the Netflix app for the Widevine L1 indicator.
look for an apk that you can manually install. I had to do that with the sammy s 20
Sine. said:
Hi!
Didn't rooted a phone since a long time, I discovered I couln't afterward install Netflix from the Playstore. Found out it's because of the unlocked bootloader, and also found the link to download the APK from Netflix directly: https://help.netflix.com/en/node/12983#android
Unfortunatelly, after installing it with adb, it still refuse to open, "this device isn't supported"
Is there any workaround?
Click to expand...
Click to collapse
You need to be able to pass safety net. There are threads about the topic on here. Once you achieve that, simply wipe data from Play Store and Play Services. Reboot and Play Store should be certified and Netflix should install.
eg1122 said:
You need to be able to pass safety net. There are threads about the topic on here. Once you achieve that, simply wipe data from Play Store and Play Services. Reboot and Play Store should be certified and Netflix should install.
Click to expand...
Click to collapse
This is was I was fearing, but...
lucky_strike33 said:
look for an apk that you can manually install. I had to do that with the sammy s 20
Click to expand...
Click to collapse
It didn't worked with the apk from netflix.com.
Meanwhile, I tried again with one from apkmirror, took the lastest beta "nodpi" one (8.7.0_build_8_40058-40058), and it now works perfectly
When I was bootloader unlocked but root wasn't out yet I couldn't find Netflix and Disney+ in the app store. I had to get them from apkmirror. At that time I still had L1. Now I'm rooted and passing SN and I can see them both in the app store and I'm still L1.
Superxdaer said:
I think this is a question that really needs confirming by having a rooted user check the playback settings in the Netflix app for the Widevine L1 indicator.
Click to expand...
Click to collapse
It says L1 while rooted in Netflix.
You can also use an app called DRM Info to see the widevine status
Sine. said:
This is was I was fearing, but...
It didn't worked with the apk from netflix.com.
Meanwhile, I tried again with one from apkmirror, took the lastest beta "nodpi" one (8.7.0_build_8_40058-40058), and it now works perfectly
Click to expand...
Click to collapse
Can confirm apk from apkmirror with version 8.7.0 build 9 nodpi works with my pixel 6 pro with open bootloader but no root. Thanx for the tip!
Indeed ... I also installed from APK mirror ... version 8.7.0build94006 ... I'm rooted (with Safetynet failing ... but I don't care so much about safetynet as I don't use GPay).