• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][pioneer][10] LineageOS 17.1

Search This thread

Rhino Cracker

New member
Nov 10, 2020
2
0
backup TA before unlock?

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
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.

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.
jfcarter.net/~jimc/hardware/sony-xperia-xa2/setup.shtml said:
Thus I'm cutting off this project with the decision to not back up the DRM keys. However, I will use TWRP Recovery to back up the TA partition (minus DRM keys) after unlocking the bootloader.


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?
 

xleng

Senior Member
Jan 3, 2016
101
14
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.
 

Rhino Cracker

New member
Nov 10, 2020
2
0
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? :)
 

xleng

Senior Member
Jan 3, 2016
101
14
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? :)

Sure one can always improve user guidance and manuals. You could also decide to volunteer to lineage in consideration of your free time and skills
;)

Frankly speaking (please don't take it personally), I think there is not much interest in this point. From a developer's perspective, you want to focus on the code itself and not loose too much of your time on such elements. You rather want to keep consistent manuals, with a good amount of "re-use" of explanations across devices. The existance of such root scripts etc depends rather strongly on the actual device. I'm sure, with the above suggested additional explanations, you would also have people complaining ;)

In summary, it's still a fair and correct assumption that this functionality is lost in the first place. Possibility to recover eventually depends on many things, is not tested etc, and can therefore be considered as not existent.

On the other hand, I was running Cyanogenmod on the Xperia L before, for which I made a backup of the drm keys thanks to such root scripts, but I never used this drm key backup...
 

zupert

Member
Aug 7, 2018
8
0
Hello,
i can't get the Wifi hotspot to work :(
It starts, and other devices can connect to it, but they report having no internet connectivity.
Am i missing some config step, or is it a known bug?

For the record: the issue was caused by Blokada.
It is unclear if only the custom DNS are causing it, or the whole filtering.
But without Blokada, the wifi thetering works just fine. So problem solved.

Also LuK1337, I wanted to say thanks for your time and efforts in this project! :good:
 

malerocks

Senior Member
Mar 6, 2018
442
103
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.
 

80c535

Member
Jul 8, 2019
9
1
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.
Same here, down to 2.6 GB free space.
I saw the first warning some days ago in Google Play Store.
 

samhhmobil

Senior Member
May 25, 2017
354
190
Hamburg
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.
Same here too. But I can see the collected (garbage) files in BrowserMetrics are going back until October '20...

What happens there in LOS since that times?

samhhmobil
 

samhhmobil

Senior Member
May 25, 2017
354
190
Hamburg
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.

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...

--
samhhmobil
 

malerocks

Senior Member
Mar 6, 2018
442
103
OK. 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...

--
samhhmobil
Awesome. Hopefully v87 will be merged in the webview that comes with LineageOS
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    • Download the latest build and gapps
    • Boot to recovery
    • Flash the latest build
    • Boot to recovery again
    • Flash gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    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:

    XDA:DevDB Information
    [ROM][OFFICIAL][pioneer][10] LineageOS 17.1, ROM for the Sony Xperia XA2

    Contributors
    LuK1337
    Source Code: https://github.com/LineageOS

    ROM OS Version: Windows 8 Mobile

    Version Information
    Status: Testing

    Created 2019-10-08
    Last Updated 2020-04-01
    11
    [ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]

    However if you want to flash whole firmware package onto both slots, you can follow the guide below:

    1. Download latest firmware with XperiFirm.
    NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
    Code:
    for f in FILE_*; do unzip $f; done
    unzip boot.zip -d boot
    2. Go to the directory where the firmware got downloaded to and remove following files:
    - boot_X-FLASH-ALL-18AE_0x00.hash
    - boot_X-FLASH-ALL-18AE.sin
    - persist_X-FLASH-ALL-18AE_0x00.hash
    - persist_X-FLASH-ALL-18AE.sin
    - system_other_X-FLASH-ALL-18AE_0x00.hash
    - system_other_X-FLASH-ALL-18AE.sin
    - system_other_X-FLASH-ALL-9B8D_0x00.hash
    - system_X-FLASH-ALL-18AE_0x00.hash
    - system_X-FLASH-ALL-18AE.sin
    - system_X-FLASH-ALL-9B8D_0x00.hash
    - userdata_X-FLASH-CUST-18AE.sin
    - vendor_X-FLASH-ALL-18AE_0x00.hash
    - vendor_X-FLASH-ALL-18AE.sin
    - vendor_X-FLASH-ALL-9B8D_0x00.hash
    3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
    4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
    5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
    6. Flash https://androidfilehost.com/?fid=4349826312261712574
    7. Profit?
    7
    PSA: Official downloads are back again.
    6
    Anyone have any clue on when the builds will resume? Is the hacking incident sorted?
    From Twitter (for the sake of completeness):

    LineageOS @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.
    https://twitter.com/LineageAndroid/status/1256821056100163584

    From Reddit (haggertk = a LOS director):

    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.

    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.
    https://www.reddit.com/user/haggertk/comments/
    5
    [announcement]
    I just released new builds /w Nov SPL but there's a c-catch.
    If you're updating from 20191025-20191102 to newer build you'll need to do: `rm -rf /data/data/com.android.providers.downloads /data/data/com.android.providers.media /data/misc/wifi /data/misc_ce/0/wifi` in root shell (adb root && adb shell or adb shell × su if using Magisk or something)