[ROM][OFFICIAL][pioneer][11] LineageOS 18.1

Search This thread

LuK1337

Recognized Developer
Jan 18, 2013
8,286
16,591
Samsung Galaxy S III I9300
Moto G 2014
2okPze5.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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.

What's not working :
  • WFD
Instructions :
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,286
16,591
Samsung Galaxy S III I9300
Moto G 2014
[ 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?
 

emc02

Senior Member
Jul 4, 2010
228
65
Vienna
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
 

Arbaazhussain

Senior Member
Nov 26, 2019
103
3
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?

The builds is always unofficial unless the lineage 18 is released as stable and then maintainers can make it official

So it is unofficial now
later official if luk sir does of course

---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------

Yeah, it is quite possible that @Arbaazhussain and other people asking about official builds / future plans will annoy me so much that I'll just drop support entirely.

Sorry if I have annoyed you
I ask for forgiveness from the depth of my heart
 

leugimp

Member
Sep 16, 2009
25
0
i have installed this ROM. very good. no problems. also have installed nikgapps BASIC. everything is OK. thanks to the dev luK1337

Enviado do meu H4113 através de Tapatalk
 

bobsright

Senior Member
Oct 1, 2015
164
35
Is there a way to activate VOLTE? I thought VOLTE and wifi calling were options on LOS 17. I had bricked this phone trying to update to the last LOS 17 and has been unused for a month or so, so I might be thinking of a rom I had on my XZP. Either way works good so far except I haven't been able to activate it on my new carrier, but that's another story.
 

DarkInvaderr

New member
Jul 1, 2016
2
0
Error installing

Hello,

I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.

The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1

Any help would be greatly appreciated,
Thanks.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,286
16,591
Samsung Galaxy S III I9300
Moto G 2014
Hello,

I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.

The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1

Any help would be greatly appreciated,
Thanks.
Try to fastboot boot latest twrp instead.
 

DarkInvaderr

New member
Jul 1, 2016
2
0
Try to fastboot boot latest twrp instead.

Tried doing that but i either get FAILED (Write to device failed in SendBuffer() (Too many links)) or FAILED (Write to device failed (no link)).
Flashed my firmware again just in case so i guess its not hard bricked?

Ill try to fastboot boot from a different PC to see if the issue is there.
Thanks for replying.
 

Top Liked Posts

  • 1
    Are you using magisk? I am wondering if this might be part of my problem...
    Yes. On 22.1. When I 1st installed the ROM, I used twrp. OTAs have obviously used lineage recovery
    1
    Thanks for your reply.
    Do you suggest that TWRP is the culprit? Or magisk?
    And did you find a way to get both magisk and OTA updates working?
    My 1st install kept failing when I installed ROM, MTG and magisk (using the recommended sequence). What finally worked for me was installing ROM and MTG, boot into system, set up phone and then install magisk (this time via lineage recovery).

    I only had twrp for initial install. Am not sure, but for OTAs I don't think trwp is recommended on this phone. I also have "update recovery" enabled in the options in the phone OTA updater.
    1
    Thanks. I came across the same problem when installing magisk: I also had to first boot into the system. I did the magisk installation with twrp after the initial boot and it also worked.
    I also noticed the "update recovery" switch. Did you see that you can't switch it off? ;)

    So are your OTAs working fine? No weird things happening afterwards like charging issues, apps and widgets disappearing from home screen and launcher?
    No issues with the OTAs. I installed the ROM the day it officially launched. So have been through 2 OTAs now. There was a charging issue initially (which others faced too) but that was fixed using a boot file that was provided by Luk
  • 3
    So I tried it and it seems to fix the issue. I had now two nights in which the phone charged properly without reboot, while before I had to reboot every evening to make it charge again.

    Please let me know if there is anything else I can do to help debugging!
    Let me know if it still works on April 13th.
    2
    You can try boot.img I uploaded here: https://forum.xda-developers.com/t/rom-official-pioneer-11-lineageos-18-1.4169357/post-84789249
    I assumed that someone would care to try it and drop their results here but I guess that was just my wishful thinking.
    I have the issue, too, and just now flashed the modified boot.img. I will report in one or two days if the problem reappears. For me it appears always after a while (some hours), and a reboot cures it.

    Btw: I observed a similar, yet more drastic issue with my wife's phone, a Sony X Compact (F5321). I tried an unofficial non-LineageOS Android 11 (https://forum.xda-developers.com/t/rom-11-0-4-9-aosp-kugo-explosive-lobster.4214465/). Charging the phone was then entirely impossible, even when switching it off or while being in recovery. I had to switch to the latest available LineageOS before the battery went down completely. Not sure if this is connected in any way, but maybe this gives a useful hint?
    1
    Thanks. I came across the same problem when installing magisk: I also had to first boot into the system. I did the magisk installation with twrp after the initial boot and it also worked.
    I also noticed the "update recovery" switch. Did you see that you can't switch it off? ;)

    So are your OTAs working fine? No weird things happening afterwards like charging issues, apps and widgets disappearing from home screen and launcher?
    No issues with the OTAs. I installed the ROM the day it officially launched. So have been through 2 OTAs now. There was a charging issue initially (which others faced too) but that was fixed using a boot file that was provided by Luk
    1
    So 18.1 has been announced officially. Can't wait to get my hands on it.
    1
    Finally got it to boot. Does anyone know of magisk works with this? Reason I ask is I redid everything but didn't use magisk (which I did flash the first time). Don't know if that got the phone to boot or I accidentally did something right.
    Magisk 22.0 works as it should (with the latest UNOFFICIAL build of LOS18.1).

    samhhmobil
  • 3
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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.

    What's not working :
    • WFD
    Instructions :
    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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
    3
    So I tried it and it seems to fix the issue. I had now two nights in which the phone charged properly without reboot, while before I had to reboot every evening to make it charge again.

    Please let me know if there is anything else I can do to help debugging!
    Let me know if it still works on April 13th.
    2
    [ 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?
    2
    You can try boot.img I uploaded here: https://forum.xda-developers.com/t/rom-official-pioneer-11-lineageos-18-1.4169357/post-84789249
    I assumed that someone would care to try it and drop their results here but I guess that was just my wishful thinking.
    I have the issue, too, and just now flashed the modified boot.img. I will report in one or two days if the problem reappears. For me it appears always after a while (some hours), and a reboot cures it.

    Btw: I observed a similar, yet more drastic issue with my wife's phone, a Sony X Compact (F5321). I tried an unofficial non-LineageOS Android 11 (https://forum.xda-developers.com/t/rom-11-0-4-9-aosp-kugo-explosive-lobster.4214465/). Charging the phone was then entirely impossible, even when switching it off or while being in recovery. I had to switch to the latest available LineageOS before the battery went down completely. Not sure if this is connected in any way, but maybe this gives a useful hint?
    1
    Thanks. I came across the same problem when installing magisk: I also had to first boot into the system. I did the magisk installation with twrp after the initial boot and it also worked.
    I also noticed the "update recovery" switch. Did you see that you can't switch it off? ;)

    So are your OTAs working fine? No weird things happening afterwards like charging issues, apps and widgets disappearing from home screen and launcher?
    No issues with the OTAs. I installed the ROM the day it officially launched. So have been through 2 OTAs now. There was a charging issue initially (which others faced too) but that was fixed using a boot file that was provided by Luk
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone