[ROM][OFFICIAL][voyager][10] LineageOS 17.1

Search This thread
By:
Advanced…
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,824
17,793
Samsung Galaxy S III I9300
Moto G 2014
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][voyager][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 2020-04-21
Last Updated 2020-04-21
 
  • Like
Reactions: hamirali
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,824
17,793
Samsung Galaxy S III I9300
Moto G 2014
[ protip: These 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=4349826312261777345 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?
 
Last edited:
  • Like
Reactions: hamirali
C

cecja

New member
Apr 29, 2020
1
1
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja

twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
 
  • Like
Reactions: magullo
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,824
17,793
Samsung Galaxy S III I9300
Moto G 2014
cecja said:
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja

twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
Click to expand...
Click to collapse
Ask me again on irc; I don't like guessing on forums.
 
H

hamirali

Senior Member
May 1, 2019
69
7
Samsung Galaxy A71
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:

1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,824
17,793
Samsung Galaxy S III I9300
Moto G 2014
hamirali said:
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:

1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
Click to expand...
Click to collapse
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
 
  • Like
Reactions: hamirali
H

hamirali

Senior Member
May 1, 2019
69
7
Samsung Galaxy A71
LuK1337 said:
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
Click to expand...
Click to collapse
Most definitely your assessment is correct, since you are the expert. What would be your advice? Should I perform step 6 now anyway? Especially since I don't seem to have any issues as yet. Thanks!
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,824
17,793
Samsung Galaxy S III I9300
Moto G 2014
hamirali said:
I just wanted to report a somewhat minor issue just for record purposes.

When I try to restart my device, it gets stuck at the LineageOS logo. I have then have to enter into twrp recovery and reboot to system.

I don't restart that often and otherwise all works fine, so not much of an issue for me.

H4493 Voyager
LineageOS 4.30.2020
Click to expand...
Click to collapse
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
 
  • Like
Reactions: hamirali
H

hamirali

Senior Member
May 1, 2019
69
7
Samsung Galaxy A71
LuK1337 said:
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
Click to expand...
Click to collapse

Reporting an issue: H4493 Voyager updated to the latest version lineage-17.1-20200529-nightly-voyager.

Cannot seem to make any calls - No service - requests to turn off airplane mode to make calls. However, the airplane mode is infact already off.

Also, strangely enough (for me at least) I can receive calls and sms.

I (maybe stupidly) thought it might be installation error, so I flashed the latest version from recovery - reinstalled everything.

No luck.

Should I not be able to sort it out, I will have to revert back to my previous version. What would you advise?
 
You must log in or register to reply here.

Similar threads

LuK1337
[ROM][OFFICIAL][pioneer][10] LineageOS 17.1
Replies
715
Views
80K
S
schmatzler
LuK1337
[ROM][OFFICIAL][pioneer][9] LineageOS 16.0
Replies
1K
Views
118K
E
exzombie
LuK1337
[ROM][OFFICIAL][pioneer][8.1] LineageOS 15.1
Replies
615
Views
76K
A
automizzer
LuK1337
[ROM][OFFICIAL][pioneer][11] LineageOS 18.1
Replies
272
Views
44K
M
malerocks
LuK1337
[RECOVERY][pioneer] TWRP Touch Recovery [OFFICIAL]
Replies
272
Views
55K
L
lobotron

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 1
    LuK1337
    LuK1337
    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][voyager][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 2020-04-21
    Last Updated 2020-04-21
    View
    1
    LuK1337
    LuK1337
    [ protip: These 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=4349826312261777345 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?
    View
    1
    C
    cecja
    Hey Luk,
    thanks for working on this great phone.
    I sadly got some problems while installing your release on a H4413 (DUAL SIM).
    I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
    After that I follow the instructions from the linage install page.
    It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
    the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
    Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
    and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
    Do you have any hint how to go from here? (After restore through emma the phone works normal again)
    best cecja

    twrp version: twrp-3.3.1-1-voyager
    lineage version: lineage-17.1-20200427-nightly-voyager-signed
    View
    1
    LuK1337
    LuK1337
    hamirali said:
    OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:

    1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
    2. Did not do item 6 above.
    3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
    4. Again from twrp, I flashed gapps - again pressed do not install twrp.
    5. Issue with Google service - I reset the phone from settings.
    6. Success!
    7.At the moment restoring my apps and stuff
    Click to expand...
    Click to collapse
    Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
    View
    1
    LuK1337
    LuK1337
    hamirali said:
    Just a query, I have downloaded and flashed a version which is no longer appearing on LineageOS voyager page. Should I flash now the one which is appearing (an earlier version) or should I just wait for a newer version, whenever it is available? Thanks in advance.
    Click to expand...
    Click to collapse
    Wait for newer one.
    View

New posts