Development [ROM][OFFICIAL][barbet] LineageOS 20

[aleasto]

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.

 

[thx1200]

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]

OK weird, it was the USB cable.

The cable worked for file transfer under Windows and also fastboot, but somehow with adb, it did not work. I have never seen that before, but, well, here we are.

If anybody else runs into this, don't overlook the USB cable.

 

[thx1200]

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]

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]

@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.

 

[Pixel86]

@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?

 

[aleasto]

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?

You do need Magisk with Riru and Universal Safetynet fix modules

 

[MrPolite]

Received a brand new Pixel 5a 5G today and flashed this rom. @aleasto thank you for making this. This rom was the main criteria in my choice of phone.

 

[FitGirl32]

I saw in LineageOS site latest build - 20211022, is this an Android 12 version update?

 

[Slim2none4u]

I saw in LineageOS site latest build - 20211022, is this an Android 12 version update?

No. Its says 18.1

 

[MrPolite]

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]

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)

 

[MrPolite]

Use the Updater app for updating. Otherwise you need to manually reinstall all your addons (namely, gapps)

Oh ya that works. Thank you again for all you do.

 

[MrPolite]

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]

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]

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

adb shell settings list secure

and got this on the LG

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]

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://xdaforums.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]

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://xdaforums.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]

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!