Since our Axon 7 only supports Widevine L3 (L1 is needed for HD Streaming on Netflix), does anyone know how to fix this problem?
https://www.xda-developers.com/android-netflix-hd-amazon-prime-video-hd-drm/
Not sure but you could probably take the DRM libs from a Pixel factory image.
Don't think it can be done on our end
I was looking for this sort of thing, but only found a pdf from widevine (google Widevine_DRM_Getting_Started_Devices). I don't really see how this could be done. L1 requires a locked bootloader but it's only necessary for certification requirements during the manufacturer's demonstration (as far as I can tell from this document).
Officially ZTE need to submit for certification and get themselves an L1 device key from Widevine. Another requirement for L1 is that this key isn't software accessible or is wiped after unlocking the bootloader, which makes that (alot) trickier. Unofficially, [I guess] you need an leaked certified-device key and have to spoof present this (and the fact you are device X) to Widevine for every request. Bit of a nightmare from that perspective.
@ Lycidias,
ZTE would consider to apply the L1 DRM latter.
Thanks for your suggestion!
That's one main reason I sold my Axon 7.
https://www.xda-developers.com/android-netflix-hd-amazon-prime-video-hd-drm/
Sorry for a noob question.
I rooted my previous device, Xperia Z3 compact, without unlocking bootloader, so I am completely new to this stuff.
I am looking into buying a used X Compact and worried that the device no longer has its TA intact.
I've searched the forum but didn't quite find an answer to my question.
So, for X compact and many other xperia models, there is DRM fix that restore DRM keys on a bootloader-unlocked device, even if you didn't backup your TA and your TA is completely wiped by unlocking, correct?
Then, how can you tell the difference between a device that has its original TA (either still intact or TA properly restored from backup) and a device without TA but DRM keys restored?
And, if you can't tell the difference, what is the point of having TA backup and restoring it later?
Sorry it seems pretty basic stuff but I can't find any direct answer to it.
Hope someone can help. Thanks in advance!
tapa_t said:
So, for X compact and many other xperia models, there is DRM fix that restore DRM keys on a bootloader-unlocked device, even if you didn't backup your TA and your TA is completely wiped by unlocking, correct?
Click to expand...
Click to collapse
Not exactly - the drm fix is a mod that attempts to replicate the features and functions that are lost when wiping ta. I've never used it, so can't say myself, but it seems like people who have are happy with it. The main issue with wiping ta is the loss of Sony camera features and quality. I believe there are also other things attached to the ta, but most people probably wouldn't ever miss them.
If you wipe the ta without backing it up, then it is gone, and your only option is drm fix. Most people would probably rather have the ta intact...
levone1 said:
Not exactly - the drm fix is a mod that attempts to replicate the features and functions that are lost when wiping ta. I've never used it, so can't say myself, but it seems like people who have are happy with it. The main issue with wiping ta is the loss of Sony camera features and quality. I believe there are also other things attached to the ta, but most people probably wouldn't ever miss them.
If you wipe the ta without backing it up, then it is gone, and your only option is drm fix. Most people would probably rather have the ta intact...
Click to expand...
Click to collapse
Thanks -- but that doesn't really answer my question. Question is *HOW* do you tell apart a phone with drm fix and no TA from a phone with an intact TA. If you can't tell the difference, people can't be sure they've got the TA intact whether they prefer it or not.
tapa_t said:
Thanks -- but that doesn't really answer my question. Question is *HOW* do you tell apart a phone with drm fix and no TA from a phone with an intact TA. If you can't tell the difference, people can't be sure they've got the TA intact whether they prefer it or not.
Click to expand...
Click to collapse
Service menu > service tests > security
See in screen shot :
- Widevine... "OK"
- ckb... "OK"
- Fido keys provisioned
with drm fix
zokkii said:
with drm fix
Click to expand...
Click to collapse
Interesting - and thats with drm keys missing (TA wiped)?
yes,without drm keys
That's only half of the story. The DRM Fix library has two working modes, and what defines which mode it'll pick depends if you have your unique device key (that get wiped when you unlock the bootloader) flashed in an alternate TA Unit. You can extract your device key and then flash it on an alternate unit as long as you have a TA backup taken before unlocking the bootloader (the RootKernel utility from @tobias.waldvogel ships with the required tools to extract and flash your device key).
On the "normal" mode (DRM Fix + device key flashed on alternate TA unit) you have exactly the same functionality you would get on a bootloader locked device with its TA intact, everything works. But, in case you don't have your device key flashed into an alternate TA unit (e.g. unlocked the bootloader without backing up the TA first, lost backup, etc), then DRM Fix will work in emulation mode. On emulation mode, most features that check for DRM will still work (e.g. camera algorithms, X-Reality Engine, etc) but some specific DRM features that requires the device key (e.g. Widevine L1 decryption, HDCP on Screen Mirroring, etc.) won't work. As it was increasingly more difficult to find exploits for newer devices and firmwares, that's the mode most DRM Fix users utilize, I guess.
Now, how to tell a DRM Fix restored device apart a device with intact TA is a little tricky, but you basically have 3 situations:
• Bootloader locked device, security test in Service Menu shows both Widevine and CKB as [OK] [Active] => stock device with TA partition intact
• Security test in Service Menu shows [unknown] or [generic error] on Widevine or CKB (or both) => TA partition wiped, DRM Fix not applied
• Bootloader unlocked device, security test in Service Menu shows both Widevine and CKB as [OK] [Active] => TA partition wiped, DRM Fix applied
When a device has the DRM Fix applied, it's not possible to tell if it's working in normal or emulation mode until you try something that requires the device keys (e.g. Widevine L1 or HDCP on Screen Mirroring). If it works, DRM Fix is in normal mode, otherwise it's in emulation mode. Also, you can't trust the "Bootloader Status" info on the Security Test of the Service menu to tell whether the bootloader was unlocked or not, as it'll always report "locked" if you have the DRM Fix applied. A safe way to tell the bootloader status is (re)booting the device and observing if the "Your device has been unlocked and can't be trusted" message appears before the Sony logo. If that message appears, the bootloader was unlocked.
You'll also find many people debating whether FIDO Keys being provisioned or not actually indicates the status of the DRM Fix, but from my experience, they aren't related. Fact is that I had FIDO Keys not provisioned on my Xperia X right after I turned it on for the first time (brand new device, had just taken it from the box), but upon registering a fingerprint, FIDO Keys became Provisioned again. Same thing occurred after I backed up my TA with the dirtycow exploit then unlocked the bootloader, FIDO Keys became not provisioned but after enrolling a fingerprint they became Provisioned again, even through I hadn't installed DRM Fix yet at that point.
And to finish, keep in mind all I said on this post is only valid for Xperia devices that launched before Xperia XZ Premium. With XZ Premium launch, Sony reworked many parts of the DRM protection and the original DRM Fix from previous devices didn't work at all. Another user eventually developed a new DRM Fix solution for those newer devices, but it works completely different and I have absolutely zero experience with it.
Does this work on the Android 9.0 custom roms? DRM Camera fix for 9.0?
sheeplings said:
Does this work on the Android 9.0 custom roms? DRM Camera fix for 9.0?
Click to expand...
Click to collapse
No
mbc07 said:
That's only half of the story. ...
Click to expand...
Click to collapse
Thanks A LOT for this information!
I have searched for a long time for something similar but everyone seems to just know this and expecting everyone else too, so it's never thoroughly described, until now!
mbc07 said:
On the "normal" mode (DRM Fix + device key flashed on alternate TA unit)
Click to expand...
Click to collapse
Do you have any information that would help a noob accomplish this? Link to a good, noob adopted, step-by-step guide? So far I'm out of luck finding anything that will give me confidence enough to try it.
Thanks again!
Holton181 said:
Do you have any information that would help a noob accomplish this? Link to a good, noob adopted, step-by-step guide? So far I'm out of luck finding anything that will give me confidence enough to try it.
Click to expand...
Click to collapse
Sorry, nope. The process is "half" streamlined if your phone happens to be supported by the original Root Kernel tool or the modded version posted on the last pages of that thread, but you would still need knowledge on how to get a TA backup on your particular device and on unlocking the bootloader / flashing a modded kernel. If your phone isn't supported then the process also involves manually modding the kernel to include the DRM Fix library too, and none of that is noob-friendly, at all...
If you can't/don't want to deal with it, your best bet is searching at your device's subforum, perhaps somebody already did the work for your particular phone model and published a ready to flash, DRM Fixed kernel there...
mbc07 said:
Sorry, nope.
Click to expand...
Click to collapse
Okay, thanks anyways. My understanding of this is much better already after your description.
Backing up TA, unlocking bootloader and rooting is the easy part, pretty good understanding how its done. It's how to make good use of the DRM:s that's all new to me.
My device is the full size X (not Compact as in this sub-forum), my wife's old working phone. I'll try to search the forum for it.
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Most with L3 Widevine in RUI 2.0 after unlocked/locked bootloader could follow this procedure to fix Widevine to L1
Install apk com.oplus.widevine v1.0.3
Open installed apk
If nothing happens then open Settings -> App Management ->App List -> Click : on the right top to show system apps -> Search widevine -> click com.oplus.widevine -> Open
Agree to the terms to send IMEI Information.
Displays information like region, device locked status, Widevine-key Status
Click WIDEVINE
Displays Windevine-Key written successfully
Download DRM info app from Play Store to confirm L1 Status
Repeat from Step 2 if any issues or confirm Widevine-key Status as true
If still has L3, then contact CN/IN/Globalsupport online chat and provide them your IMEI and mention them to Fix Widevine L3 DRM issue to Widevine L1 (specifically mention if you have locked or unlocked bootloader).
After 48 hours, IMEI given to support for L1 Fix. Use this app to authenticate your phone on the server side to issue a Widevine-key for your IMEI.
Clear Data and cache of any apps (like OTT apps) requiring L1 security level to recognise the change.
Root on RUI 2.0 is currently not recommended for this to work.
Tested and works 100% on RMX1931 RUI 2.0 F11 (India Variant) with Unlocked Bootloader.
This didn't work for me. Realme need to fix this issue.
Tamooh15 said:
This didn't work for me. Realme need to fix this issue.
Click to expand...
Click to collapse
Most with locked bootloader are having issues and many with unlocked bootloader was able to fix widevine to L1 directly or after contacting the support. Mention specifically about locked or unlocked bootloader when contacting them for the fix.
How did you get a solution with realme support? I have been 2 hours and the different assores and they have no idea what I am talking about
Even with an unlocked bootloader I have the "failed to write widevine-key"..
Hi guys, i couldnt find any expert here about my IMEI trouble. I tried every method but couldnt fix it. Xiaomi or OnePlus methods are not working in this device i guess there is a shield/block in this phone
Unfortunately in Turkey i can't use my phone with stock imei
hack-os said:
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Most with L3 Widevine in RUI 2.0 after unlocked/locked bootloader could follow this procedure to fix Widevine to L1
Install apk com.oplus.widevine v1.0.3
Open installed apk
If nothing happens then open Settings -> App Management ->App List -> Click : on the right top to show system apps -> Search widevine -> click com.oplus.widevine -> Open
Agree to the terms to send IMEI Information.
Displays information like region, device locked status, Widevine-key Status
Click WIDEVINE
Displays Windevine-Key written successfully
Download DRM info app from Play Store to confirm L1 Status
Repeat from Step 2 if any issues or confirm Widevine-key Status as true
If still has L3, then contact CN/IN/Globalsupport online chat and provide them your IMEI and mention them to Fix Widevine L3 DRM issue to Widevine L1 (specifically mention if you have locked or unlocked bootloader).
After 48 hours, IMEI given to support for L1 Fix. Use this app to authenticate your phone on the server side to issue a Widevine-key for your IMEI.
Clear Data and cache of any apps (like OTT apps) requiring L1 security level to recognise the change.
Root on RUI 2.0 is currently not recommended for this to work.
Tested and works 100% on RMX1931 RUI 2.0 F11 (India Variant) with Unlocked Bootloader.
Click to expand...
Click to collapse
Hi, the app is not working for me either, same as other members have mentioned. After decompiling the app I see that this version of oplus widevine was built for rmx1851 (realme 3 pro). Could you check with someone who received similar app from Realme for rmx1931 (x2 pro)?