yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
Another

EDIT: found this https://github.com/Lenovo-YTX703-Devel/android_device_lenovo_YTX703-common/issues/24

maybe if we use that "fastboot erase *something*" command, we're losing the DRM keys? I migh have used that command... so probably that's why I lost them...I might have used fastboot erase userdata or so....
[Google Pixel 3 XL Questions & Answers] wangdaning:
There is not even a /factory directory in the root of my Pixel 3.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
No results with search on crypto or WVcdm. And I have done fastboot erase including data multiple times. Can you use crypto key of one device on another then purpose of a crypto key fails?

Nor does it look like you lost L1 after a restore or bootloader unlock as the rest has done the same process. There is something else which is messed up.

Trustzone agree but it doesn't get messed up in this manner of unlocking or flashing or installing a custom rom.
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
Have you opened drminfo or an app like Netflix or so which uses widevine?

For me it also showed just after opening one of these, but especially drminfo app.

Yea lost the Keys in-between... I know that I've used some of the fastboot erase commands.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
i think I had already posted the screenshot from Drminfo on one of the initial postings. Here please find attached screenshots for Netflix and drminfo
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
That's not what I wanted ? I meant the log after you've opened one of those apps.

Then search for crypto. For catching the log I used matlog.
[Google Pixel 3 XL Questions & Answers] Dark_Eyes_:
How about relocking the bootloader. I never thought I'd do that but I got pissed that GPay didn't work, so I relocked the bootloader. I can't say for sure that I had L1 just before relocking, but I sure don't have it now, and it's seems to be the one thing I have in common with [MENTION=4645599]DeeZZ_NuuZZ[/MENTION].
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
hahaha okies.....

attached....

Hmm interesting point, I can try to relock the bootloader over the weekend and If I lose L1 then you are definitely going to buy me a new device :p

Would unlocking back make any difference if relocking triggered the change?
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
Relocking won't tamper that. If it does, blame google and bomb their headquarters ?

Relocking normally should vendor fix that...

I gonna try something else the next days and gonna report back what I did and if it worked or not ?

And thx for the screenshot ?
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
[MENTION=5765135]sacreddevil[/MENTION]66

Can you please reboot and take a log for about 2 mins directly after reboot and attach it as a text file? You can open then also drminfo for example. Because we wanna see, what is gonna get logged for you.

Then we could proceed with the tests ?
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
to confirm you want me to reboot the device and take logs for 2 mins, save that log and then open drm info and save that log as well ?
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
Yea but no need for two logs, just straight away after reboot you open matlog then drminfo go back to home screen and let it catch the log for 1-2 mins and then save it :)
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
attached.

Ps:- i didn't know you were going to do the experiment on my phone :p
[Google Pixel 3 XL Questions & Answers] Freak07:
hey guys :)

so it seems the problem in the logs is here:

05-01 18:23:05.148 802 5640 E DrmWidevineDash: Error: OEMCrypto_GetKeyData keyDataLength = 0

This is the one line I get more than the healthy logs. it seems strange that the keydatalength would return 0.

afterwards:

05-01 18:23:05.148 802 5640 W WVCdm : [oemcrypto_adapter_dynamic.cpp(748):LoadLevel1] Could not find /factory/wv.keys. Falling Back to L3.

and the healthy log returns:

04-30 22:28:10.104 D/WVCdm (800): [oemcrypto_adapter_dynamic.cpp(592):Initialize] OEMCrypto_Initialize Level 1 success. I will use level 1.

For reference:

healthy log with widevine on L1

https://pastebin.com/h15B4u8R

Log with widevine reseting to L3:

https://pastebin.com/KbaTg4t3

[MENTION=1205214]SacredDeviL666[/MENTION] [MENTION=5445418]Dark_Eyes_[/MENTION] just so you get notified.

If anyone stumbles upon that. I flashed April to both slots and relocked. It did not change back to l1.

However I noticed i cannot flash certain .img's from the factory image via fastboot manually.

Like modem or keymaster.

Can onyone with l1 confirm if you're able to flash one of these via fastboot? Maybe we aren't supposed to flash them but i would Luke to confirm it.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
[MENTION=3428502]Freak07[/MENTION] As long as it doesn't brick ?share the .img files and I can try from fastboot to flash those files . .

If I recollect I had flashed vendor boot bootloader imgs from fastboot and went fine.
[Google Pixel 3 XL Questions & Answers] Freak07:
the files are nothing special. They are inside the april factory image, which is downloadable from here:

https://developers.google.com/android/images

I´ll upload the modem.img for you and paste the link below here:

MD5SUM:

4d336006460de2a76ccf7ab90221809a modem.img

https://drive.google.com/open?id=1BlHf-Wx9hPBTGh1lGKJfu0siY4cVi2EX

fastboot flash modem modem.img
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
yeap returned with this error.

C:\ADB>fastboot flash modem modem.img

Sending 'modem_b' (71132 KB) OKAY [ 2.439s]

Writing 'modem_b' FAILED (remote: 'Not allowed to flash (modem_b)')

fastboot: error: Command failed

C:\ADB>
[Google Pixel 3 XL Questions & Answers] Slim2none4u:
Not sure if this will help or is your problem but maybe it has something to do with the Titan M chip?

If you was on Android Q beta, you need to data factory reset on stock recovery to reset the M chip because twrp will not do it.

Like I said, not sure if this is even related to your issue.

I know when I was on Q beta I had a hard time getting back to Pie because I wasn't factory resetting in stock recovery.

My 2 cents

Carry on
[Google Pixel 3 XL Questions & Answers] Freak07:
thank you very very much for taking the time and verifying this. So it’s probably not related to this and we’re not supposed to flash these .imgs on pixel 3 devices.

The one thing [MENTION=4645599]DeeZZ_NuuZZ[/MENTION] device and mine have in common, is that they are both from the same German carrier. We just stumbled upon that fact yesterday evening.

Currently my best bet/guess is, that by flashing a stock factory image from Google, something gets overwritten/incompatible and L1 is lost.

For example if DRM keys are issued in the bootloader (which might be carrier specific in this case here), you’ll flash a factory image from Google and replace the bootloader with a non carrier specific one, you’ll lose L1.

This could explain our troubles. It would also fit to [MENTION=4645599]DeeZZ_NuuZZ[/MENTION] ‘s tale, that by first flashing “only” a custom rom he still had L1, because he was still on his “original” bootloader.

Then at some point L1 was lost and by then he also had flashed a factory image. It’s hard to verify in retrospect.

But so far that fits.

I know I had it on L3 for a long long time already, but I didn’t really bother as I always thought it’s due to my tinkering with the device.

But factory image and relocking should definitely solve this. As far as I understand it.

Hey :)

Thanks for taking the time and chiming in!

I never flashed the Q beta on my phone.

However I’m going to try your advice, because I actually haven’t tried factory resetting in stock recovery until now. Although fastboot also wipes the device, but maybe this will help.

Thanks again!
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
Yeah it looks like today i realized i could try flashing to inactive slot but meh that doesn't make much difference. Yeah we both cannot flash.

I am a little confused here, if your IMEI and mine is starting with 99 then its a google device right? does your device had any carrier imposed restrictions when you got the phone, maybe not thats why you could unlock the bootloader unlike verizon.

Mine was from google directly not through any carrier and yes if our bootloader was replaced with google's factory bootloader shouldn't we both be impacted? there was one more user who had the same issue was he also on a german carrier? if it is then you are 99.9% right.

Just thinking out loud... i had a strange issue with AOSIP rom the moment i flash substratum all the options within device admin wouldn't let me enable or disable and other system admin related notifications would return an error some overlays and i spend hours and hours and finally i tried another rom BL and it works fine with the same set of substratum. so i could only assume its incompatibility of subs with pie or with aosip but no one else had it other than me and post in that rom thread had no response

This seems like another trivial unsolved mystery L1 to L3
[Google Pixel 3 XL Questions & Answers] Freak07:
I tried your suggestion but sadly it didn´t change a thing.

Thanks for the suggestion though as this hadn´t crossed my mind!

Yes it appeared to me since I got my pixel 3 xl, that it is just a "google" google pixel 3 xl. IMEI start with 99 and is unlockable just fine. It had no restrictions, as far as I noticed. It worked just perfectly fine.

I would have bought it directly at Google, but I had to switch carriers and got it with the contract.

Yes [MENTION=4645599]DeeZZ_NuuZZ[/MENTION] got the phone second hand, but he knows it´s from the same german carrier. (Vodafone)

Just to rule everything out, I flashed from 2 different OSes on 2 different PC´s. Tried different cables, relocked, unlocked and relocked it back several times, switched slots....

It´s a strange issue indeed. My hands are currently bound.
[Google Pixel 3 XL Questions & Answers] Bryanx86:
maybe flash the first Android os that the phone shipped with? Take the q beta OTA? Probably won't fix the issue but if you're going to try everything, might as well try everything. If you haven't already that is. I always use the batch file in windows to flash stock factory img's, and before I was using custom roms and kernels. But I relocked, and took the q beta OTA, and mine is L1. IDK what it was while I was on custom kernels and roms though.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
Okay off topic here but apparently yesterday I came to know the culprit for above wasn't subs /layers but it was an option which was available in aosip and not there in BL. Missed that part - smartpixels was messing up the whole thing. Unexpected -

https://xdaforums.com/showthread.php?p=79470483
[Google Pixel 3 XL Questions & Answers] Subhrajyoti Sen:
I have the same issue but on the Pixel 3.

Suddenly I was on L3. Then I flashed the May stock image and I am still on L3 with locked bootlaoder
[Google Pixel 3 XL Questions & Answers] JeromeLeung:
Is RMA the only way to fix this?
[Google Pixel 3 XL Questions & Answers] Subhrajyoti Sen:
What is RMA?
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
Yes sadly, I need to send it in for RMA too. Gonna try via Vodafone (haven't bought it myself there bought it second hand but I have the delivery note)

Otherwise through Google directly, which can take up to 3 weeks and then I might just get an exchange device and not new. Well yea if it doesn't has any problems, working totally fine without issues, it's okay. ?

This widevine problem can't be fixed by us. The drm keys are lost, no way for us to have access to the tools (so we can create new keys in the trustzone)
[Google Pixel 3 XL Questions & Answers] JeromeLeung:
Return Merchandise Authorization aka warranty replacement
[Google Pixel 3 XL Questions & Answers] wangdaning:
Maybe a good idea for those of us who have not hit this issue to back up the TZ_A and TZ_B partitions.
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
If you're able to flash them afterwards. Can you maybe test it? Backup and flash it again? Or maybe backup those partitions so I could try them too. If it works, I doubt, but so we can see what works and what not
[Google Pixel 3 XL Questions & Answers] wangdaning:
I know an old app, Partitions Backup, by Wanam allows you to see the TZ_A/TZ_B partitions and back them up. Not sure I am willing to test it and risk borking my device. I bought from a third party and there is no chance of returns.

At your own risk. Get the app and backup a partition so the PartitionsBackups folder is generated on your internal memory. It has a few things that are particular to your device, such as mounts, and they might not match perfect between devices because it includes magisk mounts. Add the two attached files to the folder and attempt to restore.

***Again at your own risk. I am not willing to try, but you can if you want.
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
Yea I'm not rooted, but when I have to send the phone for RMA I might try it
[Google Pixel 3 XL Questions & Answers] wangdaning:
When you open the tar.gz there is a TZ_A.img and a TZ_B.img inside. I guess theoretically you could flash it in fastboot. Not sure if TZ.img is flashable in fastboot.
[Google Pixel 3 XL Questions & Answers] Paz9:
I'm on l3 unlocked rooted

Has anyone found the solution?

Maybe a modified fstab? Custom kernel?

What triggers L1 to L3?
[Google Pixel 3 XL Questions & Answers] Eudeferrer:
Just thinking or loud, but could the change between L1 to L3 have anything to do with flashing custom kernels?

Sent from my Pixel 3 XL
[Google Pixel 3 XL Questions & Answers] Paz9:
possible but re-locking BL means stock kernel.

and the OP says its not working

---------- Post added at 01:15 AM ---------- Previous post was at 01:12 AM ----------

how would i flash these?

ill try them on my 3XL

also how can i backup my ones now - to fall back on.
[Google Pixel 3 XL Questions & Answers] Eudeferrer:
Yes, but the question is: are the only people who had the change between L1 to L3 the ones who flashed custom kernels? Or was it caused by flashing something else? I understand that relocking bootloader means stock kernel again but by then the damage was already done.

Sent from my Pixel 3 XL
[Google Pixel 3 XL Questions & Answers] Paz9:
unsure - thats something someone with L1 will have to risk losing it will have to do lol.
[Google Pixel 3 XL Questions & Answers] Freak07:
If flashing a custom kernel would delete the keys, we probably would be able to have widevine L1 on devices that fall back to L3 once unlocked.

I had the issue myself and got my phone replaced. I tried everything I could think of to get back to L1. There was no way to return to L1. You can’t even flash all partitions manually on pixel 3 devices.

I reset the device multiple times in all ways I could think of. Via OS, factory image, stock recovery. I reset back to the first factory image and took all OTAs to May! I manually flashed all OTAs from first firmware to May. I upgraded to Q. Nothing helped.

It has nothing to do with a custom kernel or anything the user can change. If the trustzone isn’t granting L1 it’s out of our control.

This mechanism isn’t happening on any part of the phone we have access to as far as I understand.

I’m running my kernel along with my own DU builds on my replacement device and L1 is working just fine. Same for many others I asked.

If you’re L3 even with a locked bootloader, a completely wiped device on stock Rom and don’t get L1 back, go contact google and make them aware of it.

Maybe they start to listen then.
[Google Pixel 3 XL Questions & Answers] Paz9:
strange, ill definitely send an email to google.

it looks like the keys are located in /vendor/firmware_mnt/ <something called widevine> can you confirm? if you have L1
[Google Pixel 3 XL Questions & Answers] Freak07:
These files doesn’t matter. I had them when I was L3 and they are the same on my L1 replacement now.

L1 certification happens in the trustzone which is like a closed part of the phone. These files are part of the vendor.img.

You can’t get back to L1 by altering them I’m afraid.

if you find a way let us know :)
[Google Pixel 3 XL Questions & Answers] Paz9:
do you think the Titan chip has something to do with it?

you said before you formatted the phone when you locked the BL

if you formatted from stock recovery, and that didnt work i'd suspect it wouldnt work otherwise.

the only other thing i can think of is switching slots after a format in stock recovery.
[Google Pixel 3 XL Questions & Answers] Freak07:
I have no idea if the titan chip has something to do with it but I would assume no.

Every OTA switches slots. My phone was completely restored to stock a few times on both slots. It didn’t help.

Only somebody who can access parts of the phone we can’t access can fix the issue. If you care about L1 make google aware of it and say you want it fixed.
[Google Pixel 3 XL Questions & Answers] Paz9:
thanks ill get in contact hopefully they can provide a public fix.
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
So I was able to exchange my device (got a new one from Google). Finally back with working L1? but I won't root the phone for the time being (not enough time after work etc)
[Google Pixel 3 XL Questions & Answers] Ayman171:
im having the same issue with my google pixel c, i think mine got bricked when i fastboot erase bootloader. lol idk why i did that but i tried everything flash google factory images and nothing works, relock the bootloader i tried everything and also it seems like i think selinux is corrupted on my tablet. its not enabled and it wont enable because permission denied
[Google Pixel 3 XL Questions & Answers] Ayman171:
okay now i fixed selinux and encryption on my pixel c but still im stuck on L3 and also google factory doesnt include drm keys for pixel c. i flashed vendor multiple times it wont work because in google driver binaries the vendor image for pixel c doesnt have drm keys like i said i tried relock bootloader, but it didnt work and i also lost the serial number of my tablet. my pc cant recognize pixel c anymore hardware serial is unknown because i erased every partition in fastboot and reflash them again when i did that i lost drm keys, is it possible to take vendor image from someone that has drm keys?
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
no this won't work. DRM keys are specific to each hardware. means you can't take from another device.
[Google Pixel 3 XL Questions & Answers] Ayman171:
then its bootloader what caused this, erasing bootloader will result losing the drm keys and hardware serial number, im not only lost drm l1 but also serial number, i cant conmect it to pc anymore. never ever erase and reflash bootloader
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
no one said you should do that lol . never do something you don't need. mine was caused by something different, I haven't erased bootloader or so. don't know what happened. but got a new sealed p3xl from google and everything is fine. but it stays unrooted till I get the pixel 4 xl
[Google Pixel 3 XL Questions & Answers] Ayman171:
im pretty sure this is what cause my pixel c to lose drm. my question is when i checked google driver binaries. i dont see widevine drm being listed for pixel c. is it odd that google doesnt include them or is it they already have them there in google factory image?
[Google Pixel 3 XL Questions & Answers] Ayman171:
i installed matlog app to check and here the results, i searched for widevine but didnt find anything. i dont understand whats going on
[Google Pixel 3 XL Questions & Answers] DeeZZ_NuuZZ:
They are in no image or whatever included and we as normal people don't have access to the partition where they are stored, neither the files from Google. So if they are lost, you can recover them. Only google/widevine can. Also if your pixel C is our of warranty you most likely won't have a chance to get a new one from them.
[Google Pixel 3 XL Questions & Answers] Ayman171:
it is out of warranty, also i bought it from ebay, used but excellent condition and even if i have warranty i cant replace it anyway. i live in israel, so google customer service is not available here, in my country the stores doesnt even sell any google products, only the pixel 3 phone
[Google Pixel 3 XL Questions & Answers] MiKiPL:
Hey, I know I'm kinda late. I'm on Pixel 4 XL with Android 12. I was in the beta program and someday on Beta 5 Widevine just reverted to L3. Now I'm on the stable release and nothing. I reinstalled the system, unlocked, locked the bootloader, nothing helped.

You were talking about Trustzone, I assume it's a partition on the disk, right? I'm just thinking out loud, but what could happen if this partition was corrupted (with premeditation)? I'm not very into this topic, but maybe there's a script that would reset the partition to its original state to get the phone working again on it's own. I really don't know, just guessing, maybe the phone would just brick.
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] rashidmalyk:
Hey guys, well it's a great day to share another amazing port with you guys. This is the MIUI 10 EU Pie 9.0 Based ROM (Port) for our Redmi 5 plus (aka vince).

I also made a video for a brief guide for installation and also review the ROM intensively, it's much worth to watch the video.

What's working:

MI Account

3rd Party Themes

Auto-brightness

4G LTE+

WiFi (+hotspot), Bluetooth

Fingerprint Recognition

Face Unlock

Full Screen Gestures

Dark Mode (Pie Supported Only)

Media

Bugs:

Reading Mode (use my video guide to get reading mode like effect)

Wireless Display

On Screen Nav Bars

Link:

https://drive.google.com/file/d/1togSnMOBHLPtgTsU_A030lz37K-VSi4d/view?usp=sharing

Credits:

To ALLAH ALMIGHTY And Prophet P.B.U.H

Xiaomi

Xiaomi.EU

Me [MENTION=9093797]rashidmalyk[/MENTION] for porting, bugs fixing

ROM Info:

MIUI Version 9.4.11

Android Version 9.0

Kernel 3.18 (Zucc Kernel AOSP) Airpods v6​
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] rashidmalyk:
EU Pie ROM V2 Released at Youtube and Telegram Channels

Change log:

Based on the latest Xiaomi.EU based on latest China Beta ROM

Fixed Read Mode

Fixed WiFi display

Fixed Bluetooth bug for Media Devices

Fixed the hotspot visibility bug

Added the on-screen nav bar
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] mertcan9556:
Reserved :)
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] xKhronox:
good work, ward :)
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] CrazyBytesVE:
Does everything in everyday use work? Camera, Wifi, data, etc? Is it for daily use? THANK you for your excellent work.

Enviado desde mi Redmi 5 Plus mediante Tapatalk
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] rashidmalyk:
Yes it is, smooth like Official Oreo MIUI 10, everything is working to make it daily driver
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] shylord:
WOW

very thanks dude
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] obliviousryuk:
bro thanks for this port! this is the only miui rom that I can play my favorite game on without being forced closed in the middle of the game. good job! hopefully, there would be a fix for wireless display because I use it sometimes. :)
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] rashidmalyk:
Oh great to see your satisfaction, thanks for the feed back
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] Moon_420:
Black Bar in themes app.

I don't think this ROM gets as bright as the stock rom.

Some stutters in home screen but It's Miui stuff as It happened in Oreo too.1

Some stutters when locking/unlocking the phone.

Some stutters at the brightness slider at the end..

Very Minor but I notice these things.

The port is really good but MIUI isn't good xd anyway back to Stock..
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] goldbeard:
The ROM is really good. But somehow the hotspot is not listed in WiFi and couldn't connect. Any solution pls ??
[Xiaomi Redmi Note 5 / 5 Plus ROMs, Kernels, Recove] shylord:
pls fix On Screen Nav Bars :crying: