• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

marsssss

Member
Aug 5, 2016
11
2
Does gogle pay work on L17.1 ?

when I try to use pay goggles I get a message :
pay goggle error , please complete action required by google pay .
 

80c535

Member
Jul 8, 2019
9
1
In theory: Will all data be kept when upgrading from 16.0 to 17.1 using the LineageOS Wiki Page /devices/pioneer/upgrade (sorry, outside links not possible yet), including Google Apps upgrade before booting the first time?
Backups will be created anyway...
 

malerocks

Senior Member
Mar 6, 2018
434
102
In theory: Will all data be kept when upgrading from 16.0 to 17.1 using the LineageOS Wiki Page /devices/pioneer/upgrade (sorry, outside links not possible yet), including Google Apps upgrade before booting the first time?
Backups will be created anyway...
Yes. I tried that but ended up messing something. Got a data corrupt error and had to reset my phone anyway. Took a couple of hours to set up everything again and all is working fine now.
 

axxx007xxxz

Senior Member
Jul 1, 2014
1,278
821
World
Oh btw lineage-17.1-20200224_122908-UNOFFICIAL-pioneer.zip+ ( and newer 16.0 ) builds will support Widevine L1 for people who unlocked their devices while on stock Android P ^.^
( if you unlocked on Android O then L1 keys got erased ;-; )
Hi, thanks for your work as usual! :good:
I was wondering if it's possible for users who still have L1 keys on an unlocked phone to backup them so that people who don't (everyone that unlocked pre-P) can flash them. Do you know anything about this?
 

malerocks

Senior Member
Mar 6, 2018
434
102
I had to restart my phone a couple of times today. It forever stayed at the startup lineage logo. I had to force the phone to the bootloader, load recovery and then choosing to reboot to system from there finally fully booted the phone. This happened twice.
 

hoxirm

Member
Mar 31, 2018
9
0
Installed Lineage OS17.1(no gaps) over 16 last night Everything seems ok, except missing sound in lagging videos.
Thank you LuK1337 for your hard work!
 
Last edited:

bungphe

Senior Member
May 12, 2008
61
10
Installed 3/4 nightly fine.
Now the 4/4 nightly available via OTA, is it ok to install via OTA?
Edit: OTA works fine!
 
Last edited:

malerocks

Senior Member
Mar 6, 2018
434
102
How's the battery life for you guys? Mine is amazing!!
 

Attachments

  • Screenshot_20200405-204636_Settings.png
    Screenshot_20200405-204636_Settings.png
    111.6 KB · Views: 191
  • Like
Reactions: Meloferz

Anosognosia

New member
Apr 6, 2020
3
1
Lyon
Hi there,

I tried to upgrade my Xperia XA2 (H4113) from Lineage OS 16.0 + MicroG to LineageOS 17.1 + Magisk but it didn't work for me. Flashing with LOS 17.1 is OK but when I try to flash Magisk 20.4, my phone won't boot anymore. It is stucked on the animated LOS logo.

Is anyone experiencing the same problem?
 
  • Like
Reactions: budgies

budgies

Member
Jan 4, 2016
11
4
Hi there,

I tried to upgrade my Xperia XA2 (H4113) from Lineage OS 16.0 + MicroG to LineageOS 17.1 + Magisk but it didn't work for me. Flashing with LOS 17.1 is OK but when I try to flash Magisk 20.4, my phone won't boot anymore. It is stucked on the animated LOS logo.

Is anyone experiencing the same problem?
Yes, when I try flashing Magisk (tested v20.4 and v20.3) I get a bootloop and have to reflash LineageOS.:rolleyes:
I don't use Gapps or MicroG.
 

samhhmobil

Senior Member
May 25, 2017
344
179
Hamburg
Yes, when I try flashing Magisk (tested v20.4 and v20.3) I get a bootloop and have to reflash LineageOS.:rolleyes:
I don't use Gapps or MicroG.
I tried on my second XA2, it's a H3113, flashed first LOS17.1, then Gapps nano, then Magisk (different tries with 20.4, 20.1 and 20.3).

Each try of that did work flawlessly, and the system was running stable in all tries.

samhhmobil
 

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)