Just found that some people on the LineageOS thread for the oneplus 3 are facing the same issue as well. Maybe it is a recent issue in LineageOS rom then
https://wiki.lineageos.org/devices/pioneer/install said:WARNING: Unlocking the bootloader will erase all data on your device! This also includes your DRM keys, which are stored in the Trim Area partition (also called TA). Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed. If you wish to backup the TA partition first, you can find tutorials related to your device on the internet.
Hi, I'm a little bit confused about the processes until the phone is flashed.
The installation manual clearly states, that you should backup your Trim Area Partition (in short TA) before unlocking the bootloader
I cannot find useful informations on how to backup and restore it (including the DRM keys).
The most promising and detailed article just told that he gave up on trying to backup DRM keys. Which, in his words, will disable his device e.g. from playing back Netflix in more than 480p.
So, how do I backup and restore the Trim Area Partition including DRM Keys on my XA2 Dual?
Or - if it is not necessary - why does the official installation manual say, that I have to ensure, that I backed it up, before unlocking the bootloader?
Obviously, when unlocking the boot loader and installing a custom, you're leaving the application scenario as envisaged by the manufacturer, and in the case of most Sony devices (including the XA2), when unlocking the bootloader, the DRM keys are erased and thus the functionality of using the Sony's proprietary photo processing algorithms is lost. This is not really recoverable (at least not without sending the device back, don't know if Sony repair can do this in exchange for some money) and the instructions include a warning of this effect.
Now, in order to backup the keys, you would need to have root access first. Personally, I'm not aware that anyone in the community has identified / developed a rooting script or app for the Sony Xperia XA2, in order to gain root access prior to unlocking the bootloader.
Of course after unlocking the bootloader it would be relatively easy to enable root, but then it's already too late.
I think most people here who have installed Lineage have simply accepted the consequence to lose this functionality. Of course this is at your own risk.
Thanks for your detailed explanaton!
So, I just misunderstood, what this warning box was trying to tell me. ("you will loose it and there is no known way to avoid it" instead of "back it up or you will loose it")
Maybe the text should say something like "there is no known way for this device to backup the drm keys, you will loose widevine, cameraAlgorithms, ... which will lead to Netflix only 480p, Camera having effect XYZ, ..."
or "for this device, there is this way <link to tested tutorial> to backup and restore Trim Area Partition. If you don't do this, you will loose <same as above>"
then, instead of literally "TA (...) ensure, the data (...) is backed up (...). You can find tutorials (...) on the internet", while there are non?
Same here, down to 2.6 GB free space.A weird thing is happening on my phone. In the last 2 weeks, the used space has increased by about 6 GB. It seems that suddenly all the apps have started increasing a lot of the user data that they store. My usage pattern is the same. And its weird that all the apps are going this. Not sure why this is happening. I am now down to only 2 GB free space.
Check app_webview browser metrics. It seems that chrome webview is spilling hundreds of files of browser metrics ...Just delete them, but I do not know how to stop them ...
Root explorer, go to data/data/app_xxx/app_webview/BrowserMetrics/ and delete everything from there. You can view which app is swalling itself up with 1tap clear pro...I had 6gb of browser metrics for one app!!!
Thanks. That helped tremendously!
Thanks. That helped tremendously!
Same here too. But I can see the collected (garbage) files in BrowserMetrics are going back until October '20...A weird thing is happening on my phone. In the last 2 weeks, the used space has increased by about 6 GB. It seems that suddenly all the apps have started increasing a lot of the user data that they store. My usage pattern is the same. And its weird that all the apps are going this. Not sure why this is happening. I am now down to only 2 GB free space.
My guess is that is around the time system webview was updated to v86 and that started this. All a wild guess though.
OK. You may be right.
Awesome. Hopefully v87 will be merged in the webview that comes with LineageOSOK. You may be right.
JFYI... I cleared all */app_webview/BrowserMetrics (8GB of data erased).'
Then I did install via PlayStore(!) „Android System Webview“ by Google(!). It's version 87.x! Then I switched in Developer Settings the Webview engine to this Google-Version 87.x (away from the LOS-shipped Version 86.x).
It seems, the bug is gone now.
But I will report in a few days again...
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
for f in FILE_*; do unzip $f; done unzip boot.zip -d boot
From Twitter (for the sake of completeness):
https://twitter.com/LineageAndroid/status/1256821056100163584LineageOS @LineageAndroid · 3. Mai
Around 8PM PST on May 2nd, 2020 an attacker used a CVE in our saltstack master to gain access to our infrastructure.
We are able to verify that:
- Signing keys are unaffected.
- Builds are unaffected.
- Source code is unaffected.
See http://status.lineageos.org for more info.
haggertk · 7 days ago
Well, it looked like the compromise was fairly contained (more details will be forthcoming in a blog post), but burning it all to the ground and rebuilding, using backups where appropriate, is better than hoping you fully cleaned it all.
No, we're in the process of rebuilding pretty much everything except signing - web, mail, gerrit, buildbots, mirrorbits, etc.
If it's public and up right now it's because it was rebuilt.
https://www.reddit.com/user/haggertk/comments/haggertk · 3 days ago
Something completely independent from the salt exploitation happened somewhere around/just after April 23. The build trees on some of our build servers got "stuck" and weren't picking up submitted changes. Because the build date would be a lie, and it wasn't worth the effort to map which specific builds came off the "stuck" servers, we removed all builds for all devices after the apparent fault timeframe.
They aren't unsafe, just potentially with a codebase that is a few days older than what's represented in the build info.
If the concern is in any way related to the infra exploit, I will repeat what we publicly stated a week ago - no completed builds, source code, keys, or signing servers were compromised in any way.
Did we run into problems? Sure, if you call people's actual paying jobs and personal lives a problem.
Still in work, hoping for by the end of weekend, which is rather good for a "rebuild the entire world" kind of situation. If we miss the date, we miss the date.
It's important to note that development was only halted for less than two days. And let's be honest, the vast majority of devices haven't had anything truly important submitted in a way that really needs a new build.