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

Development [ROM][OFFICIAL][barbet] LineageOS 18.1

Search This thread

aleasto

Senior Member
Jul 15, 2012
1,015
2,621
Milan
i9100
Samsung Galaxy S5
I successfully flashed recovery but when I try to flash LineageOS I get the "device offline" error. adb devices shows no devices attached. Fastboot works and I can flash both recovery builds on the Lineage website, but again can't flash Lineage from ADB inside recovery.

adb.exe sideload lineage-18.1-20210930-nightly-barbet-signed.zip
adb: sideload connection failed: device offline
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: device offline

adb.exe devices
List of devices attached
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
 
  • Like
Reactions: rhewins2268

thx1200

Inactive Recognized Developer
Yes I did that. It has the "cancel" option but it is not responsive to the host. I tried another PC. I tried Linux and Windows. I made sure I was running either adb admin (windows) and sudo as Linux. I tried "enable adb" and "mount system" options in recovery as well (in case there was something there). I also tried the old recovery that is on Sourceforge. I redownloaded latest SDK (adb) for both Windows and Linux.

So in summary, same behavior (no devices listed) with:
- Two different PCs
- Linux and Windows
- LineageOS recovery, all three versions for this device
- Fastboot works
- Latest ADB
- Entering recovery, apply update, apply from adb, look for "now send the package" message, only other option is "cancel"
- run the adb sideload command, device not found.
 

thx1200

Inactive Recognized Developer
Two update questions:

- I just got notice for OTA update. For the OTA updates, do we need to disable/uninstall Magisk before applying the update?

- Is there a way to do a Nandroid (or similar) backup in recovery before applying an update so we can roll back if it goes wrong?
 

aleasto

Senior Member
Jul 15, 2012
1,015
2,621
Milan
i9100
Samsung Galaxy S5
Two update questions:

- I just got notice for OTA update. For the OTA updates, do we need to disable/uninstall Magisk before applying the update?

- Is there a way to do a Nandroid (or similar) backup in recovery before applying an update so we can roll back if it goes wrong?
If you installed Magisk by sideloading in recovery it will persist the update. Otherwise you'll need to reinstall it after the update if you want to keep root.
 

zachariahpope

Senior Member
May 5, 2012
264
220
@aleasto I just wanted to say thank you as this rom is so clean fluid, and fast. Much faster than stock Android. Camera quality is unreal. I was having a great experience on the Android 12 beta, but this is an even better experience. It's been a long time since I've had an Android device on lineage (or any custom OS), but your builds and the updates (as far as 10-14-21) have given me no issues whatsoever. I've retained root through every update and I'm still passing safetynet checks. Thanks again for all your hard work... For anyone curious, this is the best you can run on the Pixel 5a yet. 👍👍
 
  • Like
Reactions: tlby

Pixel86

Member
Aug 6, 2021
12
0
@aleasto I just wanted to say thank you as this rom is so clean fluid, and fast. Much faster than stock Android. Camera quality is unreal. I was having a great experience on the Android 12 beta, but this is an even better experience. It's been a long time since I've had an Android device on lineage (or any custom OS), but your builds and the updates (as far as 10-14-21) have given me no issues whatsoever. I've retained root through every update and I'm still passing safetynet checks. Thanks again for all your hard work... For anyone curious, this is the best you can run on the Pixel 5a yet. 👍👍
To pass SafetyNet, do I need to install Magisk? I guess my real question is, does Lineage 18.1 pass SafetyNet out of the box, without root?
 

MrPolite

Member
Aug 10, 2017
48
12
Google Pixel 5a
Need a bit of direction. I've been running the 10/14 build and it's great. But my sideload of the 10/28 build wont boot...

Do i need the latest corresponding recovery image, or was using the older recovery image with the newer build not the problem?
TIA
 

aleasto

Senior Member
Jul 15, 2012
1,015
2,621
Milan
i9100
Samsung Galaxy S5
Need a bit of direction. I've been running the 10/14 build and it's great. But my sideload of the 10/28 build wont boot...

Do i need the latest corresponding recovery image, or was using the older recovery image with the newer build not the problem?
TIA
Use the Updater app for updating. Otherwise you need to manually reinstall all your addons (namely, gapps)
 
  • Like
Reactions: MrPolite

MrPolite

Member
Aug 10, 2017
48
12
Google Pixel 5a
Night Light
The red shift intensity is less on this phone, compared to LOS 18.1-10/21 on my LG-V20.

I have my linux computer's monitor at 2700K and I can turn my LG's screen to the same color with the slider at about 90%.

2700k is the color of a candle flame. The burning light our species evolved with.
 

aleasto

Senior Member
Jul 15, 2012
1,015
2,621
Milan
i9100
Samsung Galaxy S5
Night Light
The red shift intensity is less on this phone, compared to LOS 18.1-10/21 on my LG-V20.

I have my linux computer's monitor at 2700K and I can turn my LG's screen to the same color with the slider at about 90%.

2700k is the color of a candle flame. The burning light our species evolved with.
Not entirely sure why, but the slider for Pixel 5a is configured to range 2596~4082 (that's default on AOSP) while on the V20 it was lowered to 1200~4082
 

MrPolite

Member
Aug 10, 2017
48
12
Google Pixel 5a
Not entirely sure why, but the slider for Pixel 5a is configured to range 2596~4082 (that's default on AOSP) while on the V20 it was lowered to 1200~4082
Interesting, thanks for looking into it.
I did
Code:
adb shell settings list secure
and got this on the LG
Code:
night_display_color_temperature=1430

I'm guessing this needs to be changed at the kernel level, which is beyond my hardware and technical abilities.
 

Super Jamie

Senior Member
Oct 2, 2009
188
8
Thank you aleasto for building this image. It's so hard to get a good phone with a headphone jack these days. I sent some money via PayPal to show my appreciation.

I wasn't able to install following the instructions from the LineageOS wiki, so I hope my solution below saves someone else some time too.

When doing the Factory Reset step, I kept getting an error E:can't send spi message: Try again. Then trying to flash LineageOS failed with message Logical partitions are mapped. Please reboot recovery before installing an OTA update.

The solution is to disable Verified Boot as described here: https://forum.xda-developers.com/t/read-this-before-updating.4356221/

Doing Factory Reset still throws the spi message, but it works. I could then sideload LineageOS, reboot into recovery and sideload Open GApps. Reboot and do the usual LineageOS setup. All good.
 

aleasto

Senior Member
Jul 15, 2012
1,015
2,621
Milan
i9100
Samsung Galaxy S5
Thank you aleasto for building this image. It's so hard to get a good phone with a headphone jack these days. I sent some money via PayPal to show my appreciation.

I wasn't able to install following the instructions from the LineageOS wiki, so I hope my solution below saves someone else some time too.

When doing the Factory Reset step, I kept getting an error E:can't send spi message: Try again. Then trying to flash LineageOS failed with message Logical partitions are mapped. Please reboot recovery before installing an OTA update.

The solution is to disable Verified Boot as described here: https://forum.xda-developers.com/t/read-this-before-updating.4356221/

Doing Factory Reset still throws the spi message, but it works. I could then sideload LineageOS, reboot into recovery and sideload Open GApps. Reboot and do the usual LineageOS setup. All good.
You don't need to do that, it was only a coincidence. As the message suggested you just had to reboot to recovery before you could sideload LineageOS (you probably hit Mount/unmount system or tried to sideload some different zip before LineageOS, and it needed a clean reboot).

I appreciate the tip.
 

Super Jamie

Senior Member
Oct 2, 2009
188
8
You don't need to do that, it was only a coincidence. As the message suggested you just had to reboot to recovery before you could sideload LineageOS (you probably hit Mount/unmount system or tried to sideload some different zip before LineageOS, and it needed a clean reboot).

I appreciate the tip.
Ah, thanks for clarifying. I saw others say they solved the same problem by rebooting into recovery multiple times. I tried 3 times in a row but no luck. I guess the boot where I flashed vbmeta just happened to be the one that worked. I definitely hadn't tried to flash anything before, all I had downloaded to flash was LineageOS and GApps. Never mind, it all worked in the end :) Cheers!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I am currently running LOS 18.1 with pico Open Gapps and Magisk 23.0. I don't have much experience with stock Pixel 5a as I installed LOS the same day I got the phone. I have been running it for about 1.5 months and have had zero issues. I use the magisk modules recommended by aleasto in this forum to pass safety net. I run Google Camera version 8.3. The OTA updates have worked flawlessly. I do run Nova launcher as I prefer the way they implement app organization in the app drawer. A lot of the customizations I used to use root to achieve on my previous phones are already baked into LOS. My battery life has been very good too. My only major complaint about the OS is that it does not have native support for exfat formatted external drives, so I have to use a 3rd party app to be able to access external hard drives. This is made worse because of the phone's lack of micro SD slot. The main reason I got this phone is so I could install LOS. Otherwise, I would have gotten something that takes a micro SD card. Hope this info is helpful.
    2
    for me i have been on the stock rom for about 1 month. it is so buggy when you update apps from the google store. especially when you are using 3 button gestures. google maps locks up and you cant exit it if you update. google messages doesn't format correctly you get a big blank spot between the message window and the keyboard. half the time you get the notification sound of a text message. a lot of times you don't. i flashed the nov stock from again from the web and now. google play store doesnt update some of the apps i select. i'm kind of sorry i bought is phone. no custom roms. no TWRP. the phone is not faster or better than my HTC U11 6gb/128gb i came from. probably will never have twrp or a selection of custom roms due to pixel 6 coming out 1+ month later after 5a was released.
    You're posting in the LOS 18.1 thread and everything you said is wrong, irrelevant and your own fault for not doing research before buying.
    1
    i used the stock OS for about 1 day before deciding to switch. The stock OS has really limited rotation features compared to Lineage. Most of the other things i disliked about the stock OS (gestures, app-settings) could all be changed but to get more advanced rotation settings that worked would take rooting anyway.

    as far as lineage on the 5a, no complaints from me. It does all of the phone like things i expect, and can be used more like a regular computer than pretty much any other android distro.
    1
    So maybe I'm doing something wrong, but on stock android 12 I can't seem to get my phone to respond to fastboot or adb commands when I'm in the bootloader with it OEM unlocked. I'm new to pixel phones, is there some other step I may have missed while getting to the bootloader to install LOS? Any suggestions would be greatly appreciated. Thanks.
    install the USB drivers from the google pixel developer rom website. i had the same problem in the beginning. adb and fastboot would not issue commands to the phone in bootloader mode. also make sure you are using the latest adb and fastboot exe. i was using an older version that didnt seem to fully work when trying to root my pixel 5a. i'm also new to the pixel. so its been a learning curve. that always make me nervous because i dont want to brick the phone. probably want scares me away from LOS. ive bricked too many phone in my life.
  • 12
    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. LineageOS does still include various proprietary hardware-specific code.

    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.

    Informations :
    • This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
    • This ROM bundles the latest firmware so you don't have to worry about updating firmware beforehand.
    • To use the eSIM you need to have GApps
    Instructions :
    • Download the latest recovery image and rom zip
    • Boot to bootloader
    • fastboot flash boot lineage-recovery.img
    • Boot to recovery
    • Format data
    • Sideload LineageOS zip
    • Optionally flash any addons:
      • Advanced > Reboot to recovery
      • Sideload the addons
    • Reboot
    See https://wiki.lineageos.org/devices/barbet/install for more detailed instructions​
    Downloads :
    Reporting Bugs
    • 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/*
    • 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.

    Known Issues
    • Google Play Store provides a very out of date version of Google Camera
    Contributors
    aleasto
    The LineageOS team

    Source Code: https://github.com/LineageOS

    ROM OS Version: Android 11
    6
    Official builds set to start on Thursday at https://download.lineageos.org/barbet
    6
    Two update questions:

    - I just got notice for OTA update. For the OTA updates, do we need to disable/uninstall Magisk before applying the update?

    - Is there a way to do a Nandroid (or similar) backup in recovery before applying an update so we can roll back if it goes wrong?
    If you installed Magisk by sideloading in recovery it will persist the update. Otherwise you'll need to reinstall it after the update if you want to keep root.
    3
    Source code temporarily on my github before it can be moved to the LineageOS organization
    3
    Thanks for putting this together so quickly! I've been running for a couple of days now with MindTheGapps and haven't noticed any significant issues. I'm now pretty darn satisfied with my new 5a (Even though it's a friggin chonk). I'm on Visible and I was able to just pop my SIM card in and everything worked. Wifi calling, texting, 5G connection, etc - all good.

    Only weird thing I've noticed is that after setting up fingerprints for device locksreen security I'm not able to then use fingerprint security within my other apps. For example - Chase app tells me "You haven't set up fingerprint sign in on this device", PayPal app says "We're having trouble confirming your fingerprint right now" and Bitwarden app doesn't present an option to enable "Unlock with Biometrics". So I'm using currrently using PINs for these apps which is a fine compromise for me - would be curious to know whether others have experienced this.

    There have been some changes to SafetyNet in the past couple of days that tripped ctsProfile on my Pixel 4a running official LineageOS but I was able to pass SafetyNet check in this ROM by installing kdrag0n's Universal SafetyNet Fix v2.0.0 and using MagiskHide Props Config to set device fingerprint to Pixel 5.
    I doubt you need to set device fingerprint to Pixel 5 for safetynet.

    Will fix fingerprint in apps in the next build now fixed