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

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

Search This thread

LuK1337

Recognized Developer
Jan 18, 2013
8,468
16,913
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.

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,468
16,913
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
Redmi Note 10 Pro
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
162
36
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,468
16,913
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

  • There are no posts matching your filters.
  • 1
    @LuK1337 then this might actually be related to the rom itself?
    Getting back to this issue I have a log on a freshly flashed XA2 with just Threema on it and 1 picture taken with the default camera app:
    09-21 15:27:07.039 1730 1823 I ActivityTaskManager: Displayed ch.threema.app/.mediaattacher.MediaAttachActivity: +188ms
    09-21 15:27:07.052 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.056 736 736 I android.hardware.power-service-qti: Power setMode: 5 to: 0
    09-21 15:27:07.066 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.067 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.069 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.069 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.069 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.070 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.071 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.071 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.071 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.072 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.073 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.073 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.073 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.073 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.075 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.075 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.075 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.075 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.090 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.096 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.100 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.100 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.100 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.100 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.102 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.103 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.103 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.103 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.111 805 1045 W APM::AudioPolicyEngine: getDevicesForStrategy() unknown strategy: -1
    09-21 15:27:07.112 1730 2455 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
    09-21 15:27:07.153 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.161 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.162 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.163 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.163 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.163 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.164 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.164 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.164 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.164 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.165 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.166 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.167 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.167 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.167 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.180 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.186 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.190 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.190 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.191 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.191 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.193 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.194 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.194 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.194 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.264 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:06.949 0 0 E q6asm_callback: payload size of 8 is less than expected.

    Sending the picture to another device using bluetooth file transfer actually causes this issue on the other phone as well. Apparently there is actually something wrong with the jpeg itself pointing it to the direction of the camera app?!
    Update:
    I tried using different Camera Apps (such as Simple Camera from F-Droid) and the problem is non-existing. Thus I assume that there is something wrong mit the standard "org.lineageos.snap"-app. But surprisingly only in this rom. On my XZ2 Compact the app works just fine. How can this XA2-specific app-problem be fixed?
  • 9
    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.

    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:
    6
    @LuK1337 I just wanted to say thank you for your great work! Your work makes our phones live longer, and that's worth real money (donation is on it's way ;-))! I am really happy with how my phone works now. Usually you are only hearing from us when something is not working, which is probably not super motivating :)
    4
    [ 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?
    4
    As it's already tomorrow and a new build is released, I dare to give a hint:

    dead // 636865636b20746f6d6f72726f77203a5e29
    In the left (input) view, switch the format from binary to hexadecimal.
    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.