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

Search This thread

xperiaf

Senior Member
Dec 1, 2018
226
6
The ones that come with Xperia Companion, or, if you install Flashtool (http://www.flashtool.net/downloads.php), the ones you can find in the Flashtool\drivers folder. Launch the EXE that's in there, select the first 2 drivers, and make sure driver signing is not enforced if you're using Windows 10.



Strange, also using Windows 10 v2004, and my drivers still work... Using the ones bundled with Flashtool, as explained just above!

i've install the Flashtool/driver/driver.exe with disabled signing enforcement and successfully installed, but it does not triggered by my H4113 phone.
 

irgendwer2

Member
Jan 10, 2015
14
11
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/
 

user1012

Member
Nov 9, 2017
38
4
I followed wiki and unlocked bootloader and then flashed the latest recovery available (it flashed it to slot A).
Then reboot and it said "your device software can't be checked for corruption....". After couple of boot loops it offered me a factory reset so I did it.
Then I checked again bootloader via service menu and it said it is unlocked (not unlocked allowed but just unlocked).
So I repeated flashing of recovery (it flashed it to slot B) and tried to reboot to recovery and now it says your device cannot be trusted and it won't start.
Any idea what just happened?
 

malerocks

Senior Member
Mar 6, 2018
429
102
I followed wiki and unlocked bootloader and then flashed the latest recovery available (it flashed it to slot A).
Then reboot and it said "your device software can't be checked for corruption....". After couple of boot loops it offered me a factory reset so I did it.
Then I checked again bootloader via service menu and it said it is unlocked (not unlocked allowed but just unlocked).
So I repeated flashing of recovery (it flashed it to slot B) and tried to reboot to recovery and now it says your device cannot be trusted and it won't start.
Any idea what just happened?
You only have to flash to 1 shot
 

user1012

Member
Nov 9, 2017
38
4
The recovery image lineage-17.1-20200423-recovery-pioneer.img did not work for me. I downloaded 3.3.1-6 and I was able to flash LOS.

---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------

Why does not counter of unread messages/emails work?
 

Corias

Senior Member
May 12, 2009
197
17
33
Moscow
Unlocked, installed, works OK, but.. Is there any way to replace Lineage recovery with TWRP permanently? Maybe I should patch kernel or something?
 

samhhmobil

Senior Member
May 25, 2017
342
179
Hamburg
Unlocked, installed, works OK, but.. Is there any way to replace Lineage recovery with TWRP permanently? Maybe I should patch kernel or something?
Look here:
https://twrp.me/sony/sonyxperiaxa2.html

Section "Installation". You need at least TWRP 3.3.1-6 to install permanently.

READ IT CAREFULLY AND FOLLOW ALL INSTRUCTIONS! Otherwise you may run into bootloops.

samhhmobil
 
  • Like
Reactions: inahardware

inahardware

Member
Aug 1, 2017
6
2
Thank very much to all people. Now yes, with TWRP 3.3.1-6 I can make a backup. In my beginning I was a novice, I had not installed the zip file: pioneer_modem_bt_dsp_50.2.A.3.22 . The sound didn't work on youtube, now everything work very well.
 

Seppppx

Senior Member
Jul 27, 2019
278
43
I followed wiki and unlocked bootloader and then flashed the latest recovery available (it flashed it to slot A).

What do you mean by flashed? What command did you use. You can only boot recovery by "fastboot boot recoveryname.img" the phone does not have a recovery partition since it's an a/b device.

Then reboot and it said "your device software can't be checked for corruption....". After couple of boot loops it offered me a factory reset so I did it.

The "your device software can't be checked for corruption" message is completely fine it just means that your device will not be checked if it was tampered with. This message also appears on my phone and basically on every XA2.

Then I checked again bootloader via service menu and it said it is unlocked (not unlocked allowed but just unlocked).

Sorry don't I understand what you mean by service menu and I also don't what the message means.

So I repeated flashing of recovery (it flashed it to slot B)

If you mean flashing to boot slot I don't recommend doing that. It might bootloop your phone if you don't do it correctly and if you flash lineageos over the same slot as you flashed your recovery it will LOS will overwrite the recovery with it's boot image. I recommend just booting your recovery.

and tried to reboot to recovery and now it says your device cannot be trusted and it won't start.
Any idea what just happened?

How did you try to boot your recovery? I will just assume you booted to stock os but that probably failed because the boot image was not properly replaced by recovery (if you want to flash twrp to your boot image you must use the twrp installer from twrp site. https://twrp.me/sony/sonyxperiaxa2.html What happened is that your device can't boot and thus the your device can't be trusted message. If you need any more help feel free to ask.
 

malerocks

Senior Member
Mar 6, 2018
429
102
Another reasonable explanation is that from Android 8, android moved natively to notification dots. LineageOS has always stayed close to vanilla android as much as possible (e.g. From android 10 they moved to native android styles in favour to their own styles).

The idea is you take what LineageOS has to offer and then customise it as per what you want - either by rooting, apps or your own dev work.
 

user1012

Member
Nov 9, 2017
38
4
Another reasonable explanation is that from Android 8, android moved natively to notification dots.
Do we know logic behind that?
I find number/counter more informative than a dot.

Besides, notification dots do not work properly.
Messages (texts/SMS) are groupped by sender. And If I have sender A opened and there's a new (unread) message from sender B I do not have notification dot on my homescreen.
 

chaos3

New member
May 21, 2020
1
0
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?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I found a "workaround" for staying with LOS17.1 on XA2 (for those people who cannot upgrade to 18.1 for different reasons).

    It's "iodéOS" for XA2 (to find in this forum), based on LOS17.1, but focused on much better privacy. And it's yet on security patch level of 2021/05. Not frequently updated, but when it's necessary, and OTA-updates are working.

    Nice. What else do I want?

    samhhmobil
    Another alternative also based on LOS17.1:

    /e/OS
    https://e.foundation/e-os/

    XA2 ROM install instructions and download links:
    https://doc.e.foundation/devices/pioneer/install/
  • 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)