I've updated my phone to OOS 11.0.1.1 - Cause of worse performence and battery live i reverted back to 10.3.8 using the MSM tool.
But on 10 Widevine L1 without root and unlocked bootloader l1 is gone. It comes back when i upgrade to 11?!
Now i do have a backup of my persistent part back from 10 when 11 was not released and i had l1 on 10. My idea is to bring my phone back the exact same setup and flash the persistent backup img... Is this a good idea or is there another reason why l1 is lost on 10 ??
After new year or 11.0.5.1 update, widevine certificate went from L1 to L3. I never unlocked, rooted or modded my phone. Model is Oneplus 7 Pro GM1910 256gb. What is your widevine level?
Same for me, although I am not sure of the timing. Ever find a fix?
Try flashing latest OOS 11 image from MSM tool. Internet says it fixes the L3 issue.
Note:
1) Flashing ROM from MSM tool will wipe data so backup first.
2) The image necessarily needs to be Oxygen OS 11. Version 10 won't fix anything.
I have this issue as well. But I am living with it as I don't use Netflix stuffs. Let the community know if it fixes
Widevine L3 is always their no matter what i've tried (Msm tool, OTA update up to the latest OOS). Perhaps it has something to do with me partions (im on slot A). I also noticed its a widespread problem on multiple brands. Is their a definitive fix to getting back L1 without sending my device to OnePlus?
I have a stock GM1917, running OSS 11.0.9.1.GM21AA. I've never unlocked bootloader, ironically because I didn't want to lose L1. I just download DRM Info and it reports Widevine L3.
What's up with that, and is there anything I can do about it? I'm thinking about rooting now that I can see that you can retain L1.
Try flashing latest OOS 11 image from MSM tool. Internet says it fixes the L3 issue.
Note:
1) Flashing ROM from MSM tool will wipe data so backup first.
2) The image necessarily needs to be Oxygen OS 11. Version 10 won't fix anything.
I have this issue as well. But I am living with it as I don't use Netflix stuffs. Let the community know if it fixes.
MSM flashing didn't help. Tried multiple times/versions, including before ever unlocking the bootloader for the first time. I think some of us just have a bad device that can't be fixed by MSM.
I have the same problem on my 7 pro (GM1911), Did anyone found any solution to this issue ?
I have an International KB2005 OnePlus 8T. I had it working great on official Evolution X, F15 firmware copied to both slots, rooted with Magisk Delta 6, passing SafetyNet, banking apps, streaming apps EXCEPT for Netflix. I turned on Netflix spoof in The Evolver settings but this only let it install, when I launched it it would just hang forever.
I checked my Widevine info with DRM info. At the time I had L1 but an invalid System ID (very long digit, way longer than 5 numbers but I don't remember.) I'm pretty sure that was the issue based on some conversations I had.
Ok so I want to fix my widevine giving it L1 with a valid system ID. So I do the "nuclear" option and msmtool back to OOS 11.0.7.9. msmtool completes successfully, bootloader is locked but now widevine is L3 with System ID 8159.
I don't have any original backup files from the phone, I also didn't try the older msmtool to the earlier OOS release. What is the correct way to not only get L1 widevine with a valid system ID on OOS, but what's the correct procedure to unlock bootloader, install a ROM and still retain L1?
TL;DR: how to get L1 widevine with valid system id on KB2005?
I was on the same page as you. I tried searching everywhere and didn't find about it anywhere. There isn't any way to fix the system id as of now. However there is a workaround to get netflix working, if thats what you are trying to do.
Step 1: MSMtool back to oos 11.0
Step 2: Unlock bootloader. (it changes the system id to 4 digit number which is L1 secrity)
Step 3: Install netflix and other apps that dont work with broken system ID. Log in your account.
Step 4: Update your rom.
System ID breaks but your apps works fine.
AstronxD said:
I was on the same page as you. I tried searching everywhere and didn't find about it anywhere. There isn't any way to fix the system id as of now. However there is a workaround to get netflix working, if thats what you are trying to do.
Step 1: MSMtool back to oos 11.0
Step 2: Unlock bootloader. (it changes the system id to 4 digit number which is L1 secrity)
Step 3: Install netflix and other apps that dont work with broken system ID. Log in your account.
Step 4: Update your rom.
System ID breaks but your apps works fine.
Click to expand...
Click to collapse
So when going from OOS 11.0 to a custom ROM, are you suggesting to dirty flash and not wipe data (I always thought this was a terrible idea)? Or still do a clean flash of the ROM then re-install those apps and it will work?
It is a terrible for some ROM
Dopamin3 said:
So when going from OOS 11.0 to a custom ROM, are you suggesting to dirty flash and not wipe data (I always thought this was a terrible idea)? Or still do a clean flash of the ROM then re-install those apps and it will work?
Click to expand...
Click to collapse
I had tried restoring with titanium backup but the results were same, they dont work. So yeah dirty flash is a terrible idea for some rom while some ROM allow dirty flashing. I have only tested on updating ROM from OOS 11 to OOS 13 and its working.
AstronxD said:
It is a terrible for some ROM
I had tried restoring with titanium backup but the results were same, they dont work. So yeah dirty flash is a terrible idea for some rom while some ROM allow dirty flashing. I have only tested on updating ROM from OOS 11 to OOS 13 and its working.
Click to expand...
Click to collapse
I've never ever ever seen a ROM that doesn't require a wipe when going from stock to the ROM. However once you're on the ROM, you can usually dirty flash updates unless the maintainer specifically says a new build requires a clean flash. Maybe this would work if there was a modified ROM based on OOS.
I appreciate your responses, but OOS 13 is the worst version of Android I've ever tried. I guess my dream of getting the 8T working with an A13 AOSP/LOS based ROM is still dead (with the valid L1 cert, otherwise it works fine).
I'm sticking with Pixels from now on. On every Pixel I've ever messed with (3a XL, 5a 5G RIP mobo, 6a, 7 Pro) I've been able to do anything- unlock the bootloader, try any custom ROM and/or kernel, use a custom recovery, have safetynet passing or failing and the valid L1 widevine cert just persists. Seems like a silly reason to dump OnePlus, but I need that valid L1 cert and I'm not willing to stay on the good, outdated OOS 11 or use the terrible, new OOS 13.