Hi,
So a bit of a noob question, but I was on beta OOS11 prior to going over to Open Beta and my Widewine support is L3 and not L1. I thought this was a result of unlocking the bootloader but was told this should not be the case. Any chance I can fix this as the Oneplus 8 Pro should have L1?!
Thanks in advance.
Shredz98 said:
Hi,
So a bit of a noob question, but I was on beta OOS11 prior to going over to Open Beta and my Widewine support is L3 and not L1. I thought this was a result of unlocking the bootloader but was told this should not be the case. Any chance I can fix this as the Oneplus 8 Pro should have L1?!
Thanks in advance.
Click to expand...
Click to collapse
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
efex said:
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
Click to expand...
Click to collapse
My bootloader is unlocked, I'm rooted, magisk and magiskhidr props config is installed and safety net passes but still I'm on L3
Shredz98 said:
My bootloader is unlocked, I'm rooted, magisk and magiskhidr props config is installed and safety net passes but still I'm on L3
Click to expand...
Click to collapse
Did you try clearing data/cache for Netflix (or whatever app you're using)? Does DRM Info (app) also show L3? Then I'm out of ideas.. Always worked for me on all versions since OOS 10.5.10. I'm on EU model IN2023
efex said:
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
Click to expand...
Click to collapse
efex said:
Did you try clearing data/cache for Netflix (or whatever app you're using)? Does DRM Info (app) also show L3? Then I'm out of ideas.. Always worked for me on all versions since OOS 10.5.10. I'm on EU model IN2023
Click to expand...
Click to collapse
Yeah that's the the thing the DRM info (app) shows L3 as does Netflix, tried clearing cache, uninstalling and reinstalling, everything but lock my bootloader again.
Thanks for your help in any case
Shredz98 said:
Yeah that's the the thing the DRM info (app) shows L3 as does Netflix, tried clearing cache, uninstalling and reinstalling, everything but lock my bootloader again.
Thanks for your help in any case
Click to expand...
Click to collapse
One more thing, is your play store certified? Shouldn't make a difference, but worth a try.
If not certified, clear data för Play store and Play services and it should be after self-updating.
efex said:
One more thing, is your play store certified? Shouldn't make a difference, but worth a try.
If not certified, clear data för Play store and Play services and it should be after self-updating.
Click to expand...
Click to collapse
Play store is certified. I wonder whether it is because I bought the 8 pro and it immediately updated to 10.5.12EU i believe it was but then I unlocked bootloader and went to OOS 11 DP3 though I didn't root nor check my Widewine status then, then updated to DP4 and then to OB1. It was only on OB1 that I rooted my phone and installed Magisk and only then that I checked Widewine status.
So I'm thinking I'm one of the unlucky ones who lost their L1 status via official update from OnePlus.
Shredz98 said:
Play store is certified. I wonder whether it is because I bought the 8 pro and it immediately updated to 10.5.12EU i believe it was but then I unlocked bootloader and went to OOS 11 DP3 though I didn't root nor check my Widewine status then, then updated to DP4 and then to OB1. It was only on OB1 that I rooted my phone and installed Magisk and only then that I checked Widewine status.
So I'm thinking I'm one of the unlucky ones who lost their L1 status via official update from OnePlus.
Click to expand...
Click to collapse
I was L3 until update 10.5.10 (or maybe 10.5.9). After that L1 all the way. I even clean installed DP4, updated to unrooted OB1, rooted, and still L1.
I would suggest that you MSMDtool back to an earlier OOS, unlock and root (and fix fingerprint issue that relocking BL causes), and then check L1 status. If it's L1 you should be good to update to OB1 again and root. I know I was L3 before that one update från OP so it's definetly reversable.
efex said:
I was L3 until update 10.5.10 (or maybe 10.5.9). After that L1 all the way. I even clean installed DP4, updated to unrooted OB1, rooted, and still L1.
I would suggest that you MSMDtool back to an earlier OOS, unlock and root (and fix fingerprint issue that relocking BL causes), and then check L1 status. If it's L1 you should be good to update to OB1 again and root. I know I was L3 before that one update från OP so it's definetly reversable.
Click to expand...
Click to collapse
Had a feeling you would say this and honestly the only reason I didn't MSMDtool back to an earlier OS is because of the whole fingerprint issue and scared of not being able to fix it.
I'll see what I can do, thanks mate!
Shredz98 said:
Had a feeling you would say this and honestly the only reason I didn't MSMDtool back to an earlier OS is because of the whole fingerprint issue and scared of not being able to fix it.
I'll see what I can do, thanks mate!
Click to expand...
Click to collapse
The fingerprint issues is easy to fix, I've done it a couple of times myself.. The instructions are good so just do what it says.
efex said:
The fingerprint issues is easy to fix, I've done it a couple of times myself.. The instructions are good so just do what it says.
Click to expand...
Click to collapse
Does the fingerprint issue always happen when relocking the bootloader or just sometimes? Anything I can do to avoid it?
Shredz98 said:
Does the fingerprint issue always happen when relocking the bootloader or just sometimes? Anything I can do to avoid it?
Click to expand...
Click to collapse
Not sure about that.. I've run the msmdtool twice, had to fix the reader both times.
efex said:
Not sure about that.. I've run the msmdtool twice, had to fix the reader both times.
Click to expand...
Click to collapse
Ugh, I'll now need to figure out whether L1 is worth it ?
Related
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.
Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.
suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!
robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.
Magisk V10 and phh SU r266 working fine for me on 20s
Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.
Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.
are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.
I could not pass safety net, got CM13, with MAGISK installed. Dang=)
squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks
I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.
Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?
When I first booted the phone I checked for Widivine level and it came back with level 1.
Now after rooting with Magisk I noticed the device marked as being "not certified" in Play Store and only having Widivine level 3.
My understanding is that the unlock leads to this but so far (on my OP 3, 3T and 5T) rooting with Magisk and installing a custom kernel, my devices would still be "certified".
I am wondering if things changed for Android Pie, or if e.g. installing Magisk with preserving DM-Verity would help. I was tempted to give this a try but verity errors are quite annoying and I don't want to completely wipe phone just to play around with that switch.
Any ideas?
dreinulldrei said:
When I first booted the phone I checked for Widivine level and it came back with level 1.
Now after rooting with Magisk I noticed the device marked as being "not certified" in Play Store and only having Widivine level 3.
My understanding is that the unlock leads to this but so far (on my OP 3, 3T and 5T) rooting with Magisk and installing a custom kernel, my devices would still be "certified".
I am wondering if things changed for Android Pie, or if e.g. installing Magisk with preserving DM-Verity would help. I was tempted to give this a try but verity errors are quite annoying and I don't want to completely wipe phone just to play around with that switch.
Any ideas?
Click to expand...
Click to collapse
This seems to be an issue with Magisk and some versions of OxygenOS.
There is a GitHub issue about that: https://github.com/topjohnwu/Magisk/issues/585
I read a comment in another thread that if you use magisk hide for the play store, then wipe data from the play store app you'll be good to go. immediately after rooting I checked the play store app in the magisk hide section and haven't had an issue.
Pain-N-Panic said:
I read a comment in another thread that if you use magisk hide for the play store, then wipe data from the play store app you'll be good to go. immediately after rooting I checked the play store app in the magisk hide section and haven't had an issue.
Click to expand...
Click to collapse
I just did exactly what you said. In magiskhide check the box for google play store. Force stop play store and wipe it's data. Reopen play store. No longer marked "not certified"
You'll still only have widevine 3. Download "drm info" from the play store and you'll still see L3 not L1. I believe it's the bootloader being unlocked that causes it.
Thanks guys, Play store now says certified but Widevine still only offers L3.
dreinulldrei said:
Thanks guys, Play store now says certified but Widevine still only offers L3.
Click to expand...
Click to collapse
Has been asked several times.
Bootloader unlocked = L3
Always
https://storage.googleapis.com/wvdocs/Widevine_DRM_Getting_Started_Devices.pdf
Thanks, yes, but since it - to my understanding - can be remedied by re-locking, the corresponding code or keys must be somewhere. It's like Safety Net, which is bypassed by Magisk ...
hey guys i somehow messed up my sensors so i flashed persist.img and after that i lost my widewine L1 certification is there any way i can enjoy hd content on netflix and prime.?
Unfortunately not, it's gone forever. I have done the same. I believe there is a magisk module that can fix with some devices, someone tested on around 10 devices and it worked on 3 of them, hit or a miss I think.
Hello,
I tried the magisk module and for me worked. I had to delete data and cache from Netflix as far as after the module installation the app was still showing L3.
After that I had L1
Give It a try!
Ciao
Claudio67 said:
Hello,
I tried the magisk module and for me worked. I had to delete data and cache from Netflix as far as after the module installation the app was still showing L3.
After that I had L1
Give It a try!
Ciao
Click to expand...
Click to collapse
can you give me a link on how and which file to use.?
Hello,
It's for eu Roms, check in themes and apps!
Ciao
Can anyone check this, My DRM app is showing widevine as L1 while as Netflix is showing Widevine L3 on oneplus 6T. Even the system id's are different(check ss) . I thought it would have been fixed in the new hotfix released today but No. I have tried every possible troubleshooting way, clearing data, cache, Reinstalling, restarting. Everything.
xubairsarwar said:
Can anyone check this, My DRM app is showing widevine as L1 while as Netflix is showing Widevine L3 on oneplus 6T. Even the system id's are different(check ss) . I thought it would have been fixed in the new hotfix released today but No. I have tried every possible troubleshooting way, clearing data, cache, Reinstalling, restarting. Everything.
Click to expand...
Click to collapse
L3
SOK seila said:
L3
Click to expand...
Click to collapse
Is your bootloader locked. What Rom are you on?
xubairsarwar said:
Is your bootloader locked. What Rom are you on?
Click to expand...
Click to collapse
Locked with oxygen 11 beta.
Is there any way of making Netflix work with magisk? Phone passes all the safety checks and app still ends up with 15001 issue.
nomtix said:
Is there any way of making Netflix work with magisk? Phone passes all the safety checks and app still ends up with 15001 issue.
Click to expand...
Click to collapse
Did you hide the Magisk app?
yes i did
nomtix said:
yes i did
Click to expand...
Click to collapse
Try using this app. It will tell you everything that could indicate that your phone is rooted. Add it to denylist first.
I use
Universal Safteynet Fix MOD https://forum.xda-developers.com/t/...tynet-fix-2-4-0.4217823/page-91#post-87198517
with liboemcrypto.so disabler 1.5 https://www.androidacy.com/magisk-modules-repository/
nomtix said:
Is there any way of making Netflix work with magisk? Phone passes all the safety checks and app still ends up with 15001 issue.
Click to expand...
Click to collapse
Im having the exact issue. I have the OnePlus 10 Pro running Android 13 + in Rooted with all safetynet in place. However i continue getting this error, (15001). (-93). I tried EVERYTHING, but NOTHING seems to fix my issue. Any help will be truly appreciated. Thanks.
LowaEastSide said:
Im having the exact issue. I have the OnePlus 10 Pro running Android 13 + in Rooted with all safetynet in place. However i continue getting this error, (15001). (-93). I tried EVERYTHING, but NOTHING seems to fix my issue. Any help will be truly appreciated. Thanks.
Click to expand...
Click to collapse
LowaEastSide said:
I tried EVERYTHING, but NOTHING seems to fix my issue.
Click to expand...
Click to collapse
So you're using the liboemcrypto.so disabler as well? Also try wiping data for Google Play Services/Store and Netflix.
Wiped everything as well. Even went into Configure DenyList, checked the google playstore, framework, plus services. noting seems to work. I tried some steps I found online but that didn't work as well. Its Crazy Cause i have my Oneplus 8 Pro running Android 11 and its working Fine on the Rooted device, with the Bootloader unlocked as well. So im assuming it has to be Android 13 O.S. Has anyone been able to get it working on there Rooted Device, with an Unlocked Bootloader, running Android 13? Any Help would Be Apricated. Its honestly bugging me Cause i cant get it working. Truly appreciate any Feed Back, Bless..!!
ethical_haquer said:
So you're using the liboemcrypto.so disabler as well? Also try wiping data for Google Play Services/Store and Netflix.
Click to expand...
Click to collapse
Yes, i am using liboemcrypto.so disable Plus Saftynet and a Couple Other Modules.