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

Search This thread
By:
Advanced…
A

andy356

Senior Member
Jul 5, 2016
1,300
557
aleasto said:
No
Click to expand...
Click to collapse
Oops, I forgot to follow up. Going from 19 to 20 removed Magisk, as you said. And re-flashing the Magisk zip after the update worked absolutely fine. The APK stays installed through the upgrade, only the zip needs to be re-flashed. So here's the procedure for anyone needing reassurance.

- Upgrade from 19 to 20.
- Boot into the OS.
- Open the Magisk app and notice that the Magisk zip isn't installed.
- Reboot to recovery and sideload the Magisk zip like usual.
- Reboot and open the Magisk app again. Magisk is now installed.
 
M

mac62

Member
Sep 2, 2015
45
25
LG V30
Samsung Galaxy Tab S6 Lite
daaaquan said:
Love the 20 update! The Bluetooth finally works with 1my old soundbar again
Click to expand...
Click to collapse
I took the plunge to, and it seems to be pretty great except for the battement life. Curious what you are experiencing.

I'm rooted with Canary, Zygist and the most recent universal safety net fix. Lost 15% over night with no usage. Stock battery monitor says Duck Duck Go used 15%. I'm going to clear the app, and maybe disable it to see if it is really the problem.

Update. Looks like it was DDG. I was using the app tracking blocker, and it was chewing up the battery. Reached out to the DDG people to report bug.
 
Last edited:
B

barydos

Member
Apr 29, 2021
19
4
Google Pixel 5a
I used to love Pixel Experience, but since last year it doesn't work with Google Wallet/Pay.

Does this ROM work with Google Wallet/Pay? And does it have features such as brightness slider (status bar), and swapping the order of the navigation bar? Cheers
 
M

mac62

Member
Sep 2, 2015
45
25
LG V30
Samsung Galaxy Tab S6 Lite
andy356 said:
Oops, I forgot to follow up. Going from 19 to 20 removed Magisk, as you said. And re-flashing the Magisk zip after the update worked absolutely fine. The APK stays installed through the upgrade, only the zip needs to be re-flashed. So here's the procedure for anyone needing reassurance.

- Upgrade from 19 to 20.
- Boot into the OS.
- Open the Magisk app and notice that the Magisk zip isn't installed.
- Reboot to recovery and sideload the Magisk zip like usual.
- Reboot and open the Magisk app again. Magisk is now installed.
Click to expand...
Click to collapse
I just did my first update of 20.0 through the System/Updater and lost root then too. Flashing the patched boot image fixed it, but I never had to do this on 19.1. Root was always retained through updates.
 
A

andy356

Senior Member
Jul 5, 2016
1,300
557
mac62 said:
I just did my first update of 20.0 through the System/Updater and lost root then too. Flashing the patched boot image fixed it, but I never had to do this on 19.1. Root was always retained through updates.
Click to expand...
Click to collapse
You're using the incorrect method. You're not supposed to patch anything. Simply 'adb sideload magisk.zip' in LOS Recovery, like aleasto said earlier in the thread.
 
portsample

portsample

Senior Member
May 13, 2009
122
34
Installed the nightly build on my Pixel 5A with no problems after having been away from Lineage since Android 8. What is the accepted means of rooting at this point? Would Magisk with a patched boot.img be reasonable? TIA
 
portsample

portsample

Senior Member
May 13, 2009
122
34
BTK19 said:
Reboot to Recovery click Apply Update and then Apply from ADB then adb sideload Magisk
Click to expand...
Click to collapse
Yes, that worked.

Put the following in a directory on the PC to sideload onto device:
-Lineage recovery from here: https://download.lineageos.org/devices/barbet/builds
-LineageOS image for device from here: https://download.lineageos.org/devices/barbet/builds
-current GAPPS for 13.0 from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
-current Magisk-v25.2.apk from here: https://github.com/topjohnwu/Magisk/releases/tag/v25.2

Enable developer settings on device. Unlock boot partition by enabling OEM unlock in the developer options under device Settings.
Allow USB debug setting. Connect device to computer with USB cable.
Open command prompt in directory containing above files.
-----To unlock the bootloader do the following...
Type "adb server-start"
Type "adb reboot bootloader"
Type "fastboot devices" to confirm device is detected.
Type "fastboot flashing unlock" to unlock bootloader. Device should reboot.
May need to re-allow developer settings and USB debug, etc.
-----To install the LineageOS custom recovery do the following...
Type "adb reboot bootloader"
Type "fastboot devices" to confirm device detection.
Type "fastboot flash vendor_boot vendor_boot.img"
Reboot into recovery to verify the installation using the bootloader menu to navigate to and to select the Recovery option.
In recovery, select "Factory Reset", then "Format data / factory reset" and continue.
-----To sideload the LineageOS custom rom do the following...
Return to main menu.
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using (typing): "adb sideload lineage-20.0-20230309-nightly-barbet-signed.zip".
This can take a long time (5 mins)
-----To install GAPPS, do...
Even though you are already in recovery, click Advanced, then Reboot to Recovery
When your device reboots, click Apply Update, then Apply from ADB tobegin sideload.
On the host machine, sideload the package using (typing): "adb sideload MindTheGapps-13.0.0-arm64-20221025_100653.zip"
Reboot into LineageOS.
-----Rooting with Magisk
Change suffix from.apk to.zip, Magisk-v25.2.apk to Magisk-v25.2.zip.
Open a command prompt terminal in this directory.
Type "adb server-start"
Type "adb devices" to confirm detection.
Type "adb reboot recovery"
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using (typing): "adb sideload Magisk-v25.2.zip"
Wait for the process to complete. Once done, select Reboot System now.
Magisk should prompt for the user to complete installation.

Note: this method of rooting ("Custom recovery") is described as outdated on Magisk site here: https://topjohnwu.github.io/Magisk/install.html
 
Last edited:
  • Like
Reactions: BTK19
Super Jamie

Super Jamie

Senior Member
Oct 2, 2009
190
8
Many thanks to aleasto for keeping this alive.

I hadn't upgraded since the last LineageOS 18.1 image, so the process to upgrade to 20.0 wasn't quite straightforward. Flashing the latest LineageOS Recovery over the 18.1 recovery just boot-looped.

It was necessary to flash the Android 13 official factory image and boot into the official OS. Then installing LineageOS Recovery worked. It was also necessary to perform a Factory Reset inside LineageOS Recovery before installing, as portsample just listed above and as the official wiki says.

Note that this wipes all user data (including internal storage) but I intended to do that anyway to get a nice fresh start, so everything was copied off before I started. Always have a backup!

Hopefully that helps someone else in the same situation.
 
306bobby

306bobby

Member
Feb 22, 2023
7
2
Google Pixel 5a
portsample said:
Yes, that worked.

Put the following in a directory on the PC to sideload onto device:
-Lineage recovery from here: https://download.lineageos.org/devices/barbet/builds
-LineageOS image for device from here: https://download.lineageos.org/devices/barbet/builds
-current GAPPS for 13.0 from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
-current Magisk-v25.2.apk from here: https://github.com/topjohnwu/Magisk/releases/tag/v25.2

Enable developer settings on device. Unlock boot partition by enabling OEM unlock in the developer options under device Settings.
Allow USB debug setting. Connect device to computer with USB cable.
Open command prompt in directory containing above files.
-----To unlock the bootloader do the following...
Type "adb server-start"
Type "adb reboot bootloader"
Type "fastboot devices" to confirm device is detected.
Type "fastboot flashing unlock" to unlock bootloader. Device should reboot.
May need to re-allow developer settings and USB debug, etc.
-----To install the LineageOS custom recovery do the following...
Type "adb reboot bootloader"
Type "fastboot devices" to confirm device detection.
Type "fastboot flash vendor_boot vendor_boot.img"
Reboot into recovery to verify the installation using the bootloader menu to navigate to and to select the Recovery option.
In recovery, select "Factory Reset", then "Format data / factory reset" and continue.
-----To sideload the LineageOS custom rom do the following...
Return to main menu.
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using (typing): "adb sideload lineage-20.0-20230309-nightly-barbet-signed.zip".
This can take a long time (5 mins)
-----To install GAPPS, do...
Even though you are already in recovery, click Advanced, then Reboot to Recovery
When your device reboots, click Apply Update, then Apply from ADB tobegin sideload.
On the host machine, sideload the package using (typing): "adb sideload MindTheGapps-13.0.0-arm64-20221025_100653.zip"
Reboot into LineageOS.
-----Rooting with Magisk
Change suffix from.apk to.zip, Magisk-v25.2.apk to Magisk-v25.2.zip.
Open a command prompt terminal in this directory.
Type "adb server-start"
Type "adb devices" to confirm detection.
Type "adb reboot recovery"
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using (typing): "adb sideload Magisk-v25.2.zip"
Wait for the process to complete. Once done, select Reboot System now.
Magisk should prompt for the user to complete installation.

Note: this method of rooting ("Custom recovery") is described as outdated on Magisk site here: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
In regards to that method being outdated, read my post above. Also safetynet-fix mod by displax fixes safteynet and allows for google wallet and tap to pay to work
 
rodken

rodken

Senior Member
Jan 11, 2010
1,629
716
andy356 said:
Oops, I forgot to follow up. Going from 19 to 20 removed Magisk, as you said. And re-flashing the Magisk zip after the update worked absolutely fine. The APK stays installed through the upgrade, only the zip needs to be re-flashed. So here's the procedure for anyone needing reassurance.

- Upgrade from 19 to 20.
- Boot into the OS.
- Open the Magisk app and notice that the Magisk zip isn't installed.
- Reboot to recovery and sideload the Magisk zip like usual.
- Reboot and open the Magisk app again. Magisk is now installed.
Click to expand...
Click to collapse
What about the method to updating to a newer version of MindTheGapps without borking the system?
 
rasimsen

rasimsen

New member
Apr 27, 2023
2
0
Hello,

I am trying to build my own lineageos for Google Pixel 5A. I think that everyone built properly. I am getting an error after the following section:
Code: 
source build/envsetup.sh
breakfast barbet

# failed, then I tried the following

cd ~/android/lineage/device/google/barbet
./extract-files.sh

Error:
Code: 
  - vendor/firmware/CAMERA_ICP.elf
    !! vendor/firmware/CAMERA_ICP.elf: file not found in source
  - vendor/firmware/Data.msc
    !! vendor/firmware/Data.msc: file not found in source
  - vendor/firmware/TEST_MAPPING
    !! vendor/firmware/TEST_MAPPING: file not found in source
  - vendor/firmware/a615_zap.b00
    !! vendor/firmware/a615_zap.b00: file not found in source
  - vendor/firmware/a615_zap.b01
    !! vendor/firmware/a615_zap.b01: file not found in source
  - vendor/firmware/a615_zap.b02
    !! vendor/firmware/a615_zap.b02: file not found in source
  - vendor/firmware/a615_zap.elf
    !! vendor/firmware/a615_zap.elf: file not found in source
  - vendor/firmware/a615_zap.mdt
    !! vendor/firmware/a615_zap.mdt: file not found in source
  - vendor/firmware/a619_gmu.bin
    !! vendor/firmware/a619_gmu.bin: file not found in source
  - vendor/firmware/a620_zap.b00
    !! vendor/firmware/a620_zap.b00: file not found in source
  - vendor/firmware/a620_zap.b01
    !! vendor/firmware/a620_zap.b01: file not found in source
  - vendor/firmware/a620_zap.b02
    !! vendor/firmware/a620_zap.b02: file not found in source
  - vendor/firmware/a620_zap.elf
    !! vendor/firmware/a620_zap.elf: file not found in source
  - vendor/firmware/a620_zap.mdt
    !! vendor/firmware/a620_zap.mdt: file not found in source
  - vendor/firmware/a630_sqe.fw
    !! vendor/firmware/a630_sqe.fw: file not found in source
  - vendor/firmware/a650_gmu.bin
    !! vendor/firmware/a650_gmu.bin: file not found in source
  - vendor/firmware/a650_sqe.fw
    !! vendor/firmware/a650_sqe.fw: file not found in source
  - vendor/firmware/a650_zap.b00
    !! vendor/firmware/a650_zap.b00: file not found in source
  - vendor/firmware/a650_zap.b01
    !! vendor/firmware/a650_zap.b01: file not found in source
  - vendor/firmware/a650_zap.b02
    !! vendor/firmware/a650_zap.b02: file not found in source
  - vendor/firmware/a650_zap.elf
    !! vendor/firmware/a650_zap.elf: file not found in source
  - vendor/firmware/a650_zap.mdt
........
........

Next step:
Code: 
$ brunch barbet

Error:

Code: 
WITH_GMS=true
============================================
[100% 252/252] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
cd "$(dirname "out/soong/.bootstrap/bin/soong_build")" && BUILDER="$PWD/$(basename "out/soong/.bootstrap/bin/soong_build")" && cd / && env -i "$BUILDER"     --top "$TOP"     --out "out/soong"     -n "out
"     -d "out/soong/build.ninja.d"     -t -l out/.module_paths/Android.bp.list -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja --available_env out/soong/soong.environment.availa
ble --used_env out/soong/soong.environment.used Android.bp
error: vendor/google/barbet/Android.bp:831:1: module "libMpeg4SwEncoder" variant "android_vendor.32_arm64_armv8-a_shared": module source path "vendor/google/barbet/proprietary/vendor/lib64/libMpeg4SwEnco
der.so" does not exist
error: vendor/google/barbet/Android.bp:891:1: module "libthermalclient" variant "android_vendor.32_arm64_armv8-a_shared": module source path "vendor/google/barbet/proprietary/vendor/lib64/libthermalclien
t.so" does not exist
18:28:01 soong bootstrap failed with: exit status 1

#### failed to build some targets (02:30 (mm:ss)) ####

I think that I need proper 'vendor/google/barbet' folder. Is anyone having it as zip file? Or from where I can find it? I couldn't download it from device.

Thank you
Rasim
 
You must log in or register to reply here.

Similar threads

V0latyle
How To Guide [GUIDE] Pixel 5a "barbet": Unlock Bootloader, Update, Root, Pass SafetyNet
Replies
208
Views
32K
V0latyle
V0latyle
nijel8
Development [RECOVERY][UNOFFICIAL] TWRP for barbet
Replies
73
Views
15K
mikhailkurakhtanov
mikhailkurakhtanov
Slim2none4u
Development [ROM][13][barbet] PixelExperience [AOSP][OFFICIAL]&[UNOFFICIAL]
Replies
88
Views
10K
rchris494
rchris494
T
  • Locked
Development [CLOSED] PIXEL EXPERIENCE PIXEL 5A BARBET ANDROID 13 BETA UNOFFICIAL NOV. 7, 2022
Replies
129
Views
11K
Badger50
Badger50
Siluxsept
Development [SUPERCEEDED][ROM][OFFICIAL][barbet][11] - AICP 16.1 for Pixel 5a
Replies
43
Views
6K
M
megavolts

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 19
    aleasto
    aleasto
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android, 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.
    • To use the eSIM you need to have GApps
    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. You can use GoogleCamera.apk extracted from stock here
    Contributors
    mikeioannina
    aleasto
    The LineageOS team

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

    ROM OS Version: Android 13
    View
    6
    aleasto
    aleasto
    thx1200 said:
    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?
    Click to expand...
    Click to collapse
    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.
    View
    6
    aleasto
    aleasto
    Official builds set to start on Thursday at https://download.lineageos.org/barbet
    View
    3
    aleasto
    aleasto
    Source code temporarily on my github before it can be moved to the LineageOS organization
    View
    3
    aleasto
    aleasto
    New build with new kernel experiments targeting official release.
    Please test and report whether audio works still:
    View

New posts