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

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

Search This thread

LuK1337

Recognized Developer
Jan 18, 2013
8,509
16,982
Samsung Galaxy S III I9300
Moto G 2014
hello.

I have got a new xperia xa2 phone and want to install lineage os 17.1 on it. I am new to this and am afraid of doing something wrong. After reading this thread there seem to be some things with only one chance at doing them right. So please forgive me if I am too cautious.

The phone comes with android version 8.0.0, baseband version 20180829_BY120_Daily and build number 50.1.A.13.83.
I understood that the firmware should somehow be brought to version 50.2 and the baseband to something from 2019.
Is there any downside to let the device upgrade itself to android 9 first? Or is it just unnecessary? Would it upgrade my firmware and baseband as well or do I have to do it manually anyway?

Is there a way to backup the whole system before trying to install lineage os? So that I could restore all partitions if anything goes wrong? Is there anything I cannot backup and should I worry about that? (I think DRM keys were mentioned somewhere in this thread. Stuff like that.)
Is booting into twrp already changing the system? I read that twrp has a backup function. Can it access everything on the device?

OTA until there are no more OTAs before unlocking BL and you should be fine.
 

samhhmobil

Senior Member
May 25, 2017
364
191
Hamburg
How do you boot into twrp once it's installed?

I thought there would be a key to do it, but cant make it work
Have a look at:
https://wiki.lineageos.org/devices/pioneer
topic: Special boot modes

samhhmobil

PS
For myself (and just only for myself) I did decide, not to flash TWRP permanently into the phone. I can live with LOS recovery as it is included in LOS17.1, and if I really need TWRP, I'll boot it via fastboot from PC.

X:\> fastboot boot twrp.img <CR>
 
  • Like
Reactions: dwi336

inahardware

Member
Aug 1, 2017
6
2
Have a look at:
https://wiki.lineageos.org/devices/pioneer
topic: Special boot modes

samhhmobil

PS
For myself (and just only for myself) I did decide, not to flash TWRP permanently into the phone. I can live with LOS recovery as it is included in LOS17.1, and if I really need TWRP, I'll boot it via fastboot from PC.

X:\> fastboot boot twrp.img <CR>
I had flashed, but in my case twrp is not able to restore backup. I am looking for another way to backup. Maybe adb...
My xa2 worked fine after installing twrp, but after a few weeks my xa2 got corrupted. I don't know the reason.
 

malerocks

Senior Member
Mar 6, 2018
459
103
I see WiFi calling as an option now after the latest build. No indication whether it actually works though.
 

Attachments

  • Screenshot_20200531-101213_Settings.png
    Screenshot_20200531-101213_Settings.png
    62.2 KB · Views: 125

Arbaazhussain

Senior Member
Nov 26, 2019
102
3
Redmi Note 10 Pro
Can you bring more clock and fonts for this rom?
Can you also bring customisable grid options ? (Like on third party launchers)
Can all the customisable option put under one for easy access of these options?
And mainly wanted to know how to install twrp without causing any problems for this type of device.
 

kapibada

Member
Nov 7, 2015
18
4
Does anyone here have any idea if the Gapps+Magisk problems are resolved now? (i.e. no need to boot into recovery to avoid bootloop)
 

zupert

Member
Aug 7, 2018
8
0
Since the new OTA upgrades 2 days ago, the unlocking of the second SIM card never succeeds.
I am limited to booting with only one SIM.
Is it a known issue?
 

samhhmobil

Senior Member
May 25, 2017
364
191
Hamburg
Does anyone here have any idea if the Gapps+Magisk problems are resolved now? (i.e. no need to boot into recovery to avoid bootloop)
No idea yet.

Since end of February my H4113 and my H3113 did reboot flawlessly (LOS17.1, Gapps-nano, Magisk 20.3).

But mid of May I got a random (warm) reboot on my H4113, and since this event it does not reboot anymore, and I can only reboot into TWRP (via fastboot), clearing Dalvik, and from there, it reboots normally again. But reboot from inside the system is impossible now.

My second device, H3113, same configuration, reboots flawlessly up to now without any trouble, and I don't see a difference between both systems configuration.

It's quite strange.

samhhmobil
 
Last edited:

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)