Same problem on Mi 9t Davinci. Widevine has gone from L1 to L3 for no reason.
Thanks to the developers for trying to analyze and help us.
Thanks to the developers for trying to analyze and help us.
Resolved Widevine L3 without any flash
- Thread starter floone
- Start date
- Status
- 6 Oct 2016
- 9,999
- 322
A small task for all participants, those who had L1 and it turned to L3 suddenly:
1) Install "DRM Info" from Play Store (if you haven't done that already).
2) Connect the phone to the PC and have ADB tools ready.
3) Enter the command:
4) Enter the command:
5) Launch DRM Info, and once it's fully loaded, Ctrl+C to stop logging.
Post the drm.txt log here with your device model and ROM version. (the log does not contain any sensitive information)
Example: Redmi Note 8 (21.4.22)
1) Install "DRM Info" from Play Store (if you haven't done that already).
2) Connect the phone to the PC and have ADB tools ready.
3) Enter the command:
Code:
adb logcat -c
Code:
adb logcat -s DrmUtils,DrmLibTime,OPS_SERVICE,QC-time-services,QCOM-OEMCrypto,QSEECOMAPI,WVCdm > drm.txtPost the drm.txt log here with your device model and ROM version. (the log does not contain any sensitive information)
Example: Redmi Note 8 (21.4.22)
gromez
Members
- 21 Jan 2016
- 3
- 15
Here is a drm.txt
I did a persist partition restore from a dump I'm sure it was L1, but still the same.
Xiaomi Mi 9 (21.4.21)
EDIT: I've just looked into /vendor/firmware_mnt/image, I don't have widevine.mdt but I have widevine.mbn file
Last edited:
- 6 Oct 2016
- 9,999
- 322
Normal. widevine.mdt was used up to Android 10, while widevine.mbn is used instead since Android 11.
- 6 Oct 2016
- 9,999
- 322
If there's anyone who still has L1 on Mi 9 (cepheus), Mi 9T/Redmi K20 (davinci), Mi 9T Pro/Redmi K20 Pro (raphael) or Redmi Note 8 (ginkgo), please share us a a log so we would try to find out what the difference is that causes the failure for others.
- 6 Oct 2016
- 9,999
- 322
The following is relevant to Mi 9 (cepheus) and Mi 9T Pro/Redmi K20 Pro (raphael) only, and does not apply to Mi 9T (davinci) or Redmi Note 8 (ginkgo), for which we need more logs from users with L1 or L3:
From what we learned so far, users of these 2 devices simply lost their L1 keys or they got somehow corrupted.
The OEMCrypto libs are compatible and work properly, as confirmed by a Mi 9T Pro/Redmi K20 Pro user of our ROM (latest Weekly), who still has his L1 key working properly, and as evident by this part from his log, which shows the L1 key being read properly:
While logs from users who lost their L1 key look like this:
As you can see, the key is completely lost. One thing you may want to try is flash the latest official Global fastboot ROM and relock the bootloader. It may, or may not, restore the key. Will be interesting to hear the results.
From what we learned so far, users of these 2 devices simply lost their L1 keys or they got somehow corrupted.
The OEMCrypto libs are compatible and work properly, as confirmed by a Mi 9T Pro/Redmi K20 Pro user of our ROM (latest Weekly), who still has his L1 key working properly, and as evident by this part from his log, which shows the L1 key being read properly:
Code:
I QCOM-OEMCrypto: LibOEMCrypto version 1.30
I QCOM-OEMCrypto: TA version 1.74
I QCOM-OEMCrypto: Api version 16.3
D WVCdm : [oemcrypto_adapter_dynamic.cpp(729):Initialize] OEMCrypto_Initialize Level 1 success. I will use level 1.
I WVCdm : [oemcrypto_adapter_dynamic.cpp(732):Initialize] Level 1 Build Info (v16): Build Information: API_Version: 16.3 LibOEMCrypto_Version: 1.30 TA_Version: 1.74
Code:
I QCOM-OEMCrypto: LibOEMCrypto version 1.30
I QCOM-OEMCrypto: TA version 1.74
I QCOM-OEMCrypto: Api version 16.3
E QCOM-OEMCrypto: Error at trusted_app_is_keybox_or_oemcert_valid : 735
E QCOM-OEMCrypto: TA Result : 17 OEMCryptoResult : 10
I QCOM-OEMCrypto: -----------------------------------------------------------------
I QCOM-OEMCrypto: Error stack trace[1] for TA version 1:74
E QCOM-OEMCrypto: i_widevine_oemcrypto_is_keybox_or_oemcert_valid : 914
I QCOM-OEMCrypto: -----------------------------------------------------------------
E QCOM-OEMCrypto: Error at _oecc05 : 637
W WVCdm : [oemcrypto_adapter_dynamic.cpp(916):LoadLevel1] Could not find /factory/wv.keys. Falling Back to L3.- 6 Oct 2016
- 9,999
- 322
Thank you. This confirms that what is said above for cepheus and raphael is also true for davinci:
Code:
I QCOM-OEMCrypto: LibOEMCrypto version 1.30
I QCOM-OEMCrypto: TA version 1.71
I QCOM-OEMCrypto: Api version 16.3
E QCOM-OEMCrypto: Error at trusted_app_is_keybox_or_oemcert_valid : 735
E QCOM-OEMCrypto: TA Result : 17 OEMCryptoResult : 10
I QCOM-OEMCrypto: -----------------------------------------------------------------
I QCOM-OEMCrypto: Error stack trace[1] for TA version 1:71
E QCOM-OEMCrypto: i_widevine_oemcrypto_is_keybox_or_oemcert_valid : 912
I QCOM-OEMCrypto: -----------------------------------------------------------------
E QCOM-OEMCrypto: Error at _oecc05 : 637
W WVCdm : [oemcrypto_adapter_dynamic.cpp(916):LoadLevel1] Could not find /factory/wv.keys. Falling Back to L3.Users of certain devices from another brand had their L1 keys lost when they had their bootloader unlocked, and restored once they relocked it. We don't know yet if it's a possibility with Xiaomi devices.
Log from my Mi 9T (12.1.2 Stable), comparing to your posted logs it seems like the key ist lost completely
- 6 Oct 2016
- 9,999
- 322
Yes initially I tried the Android 11 Weekly about 1,5 months ago, but decided that the stable was fine for me and used the stable since then (and I also had Widevine L1 on the stable until a week ago).
When I realized I lost Widevine L1 somehow I also tried the Android 11 Weekly again to see if that fixes it, but that didn't change the Widevine level.
- 6 Oct 2016
- 9,999
- 322
Yeah, it almost looks like the keys expired/invalidated. Might have been done automatically by Xiaomi's Cloud Service.
I would like to do it, but I need my mobile for work and I don't have another one to replace it.
If at some point I have time, I will, but now it is impossible.
I really appreciate your time and efforts to offer us the roms weekly.
Thanks.
I had some time and went back to the latest Mi 9T stock ROM (12.0.4QFJEUXM) + locked bootloader. Unfortunately, Widevine is still L3.
Mi 9T Pro (21.4.21)
I also tried to install the Global ROM a long time ago but Widevine stayed at L3...
Xiaomi appears to be silently blocking/invalidating Widevine L1 keys on unlocked devices... with no recovery option like other companies offer... very sad
I also tried to install the Global ROM a long time ago but Widevine stayed at L3...
Xiaomi appears to be silently blocking/invalidating Widevine L1 keys on unlocked devices... with no recovery option like other companies offer... very sad
- 6 Oct 2016
- 9,999
- 322
I've no idea what you're saying. Those devices don't officially support installing a new Widevine key, something we're working to overcome.
Poney70
Donator
- 3 Oct 2019
- 5,488
- 337
But does a remote server could check and valid or invalid (and delete???) a Widevine key? It's very strange...
- 6 Oct 2016
- 9,999
- 322
Delete - very probably, but install a new one - definitely no.But does a remote server could check and valid or invalid (and delete???) a Widevine key? It's very strange...
I just flashed the latest Global EEA rom from Xiaomi on my Mi9/cepheus and relocked the bootloader. There seems to be no effect on my Widevine level, which is still L3.
- Status
