Bedhedd's xperia 5 III lineageos project

bedHedd · December 3, 2024, 3:21am

After my adventure rooting jelly star, I wanted to do this for my Sony Xperia 5 III.

This time I wanted to do it in more of a blog style with replies as updates so that I can keep track of my research and what I did.

Also don’t feel like writing a guide

bedHedd · December 3, 2024, 5:38am

Started by reading the guide on the LineageOS wiki
https://wiki.lineageos.org/devices/pdx214/install/

basic requirement section

Basic requirements

1. Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
2. Make sure your computer has adb and fastboot. Setup instructions can be found here.
3. Enable USB debugging on your device.
4. Make sure that your model number is one of the following (exact match required!):

XQ-BQ72

XQ-BQ62

XQ-BQ52

XQ-BQ42

5. Boot your device with the stock OS at least once and check every functionality.

Warning:
Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available), otherwise it won’t work on LineageOS either! Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.

6. LineageOS is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!

Warning: Before following these instructions please ensure that the device is currently using Android 13 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 13, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).

I bought and checked the model number, but let’s use adb to confirm. A quick internet search found me this command

I added the tag |release\| to get the android version and get the relevant sections

adb shell getprop | grep "model\|version.sdk\|manufacturer\|hardware\|platform\|revision\|release\|serialno\|product.name\|brand"

...
[ro.product.manufacturer]: [Sony]
...
[ro.semc.product.model]: [XQ-BQ72]
[ro.semc.product.name]: [Xperia 5 III]
...
[ro.soc.manufacturer]: [QTI]
[ro.soc.model]: [SM8350]
...
[ro.system_ext.build.version.release]: [13]
[ro.system_ext.build.version.release_or_codename]: [13]
[ro.system_ext.build.version.sdk]: [33]
...
[ro.vendor.build.version.release]: [11]
[ro.vendor.build.version.release_or_codename]: [11]
[ro.vendor.build.version.sdk]: [30]
[vendor.somc.syscore.product.name]: [pdx214]

Checking the correct firmware section

Checking the correct firmware

Installation on your device requires a specific firmware version to be installed before you continue.

Firmware refers to a device-specific set of images that are included in, and updated by the stock OS

LineageOS builds for this device require an Android 13 version of the stock OS to be installed prior to following the installation guide

Please ensure that you are checking the Android version, and not the vendor OS version

Being on another custom ROM, including unofficial builds of the same version of LineageOS, does not ensure that this requirement has been fulfilled

Please re-read this section as many times as necessary to fully understand the requirements

Note: If you are unsure what firmware version you are currently on, we strongly recommend returning to the corresponding stock OS before following the installation guide!

Failing to install the correct firmware version prior to installation may result in failure to install LineageOS, unexpected crashes post-installation, or permanent damage to your device!

Based on the previous section, I have android 13, my model number matches, and my product name matches the page name

sidequest to figure out which region and which firmware I would need to backup and recover the phone in case I flash the incorrect firmware

I wanted to backup my phone, so a quick internet search directed me to
https://xdaforums.com/t/tool-xperifirm-xperia-firmware-downloader-v5-7-0.2834142/

to install it, I needed to follow the Linux instructions and find the fedora equivalent packages

After installing it on Fedora, I needed to figure out which region my phone is so that I have the right firmware. The CDA seems to be a unique identifier and corresponds with a given region

xperifirm has instructions to access the service menu by dialing *#*#7378423#*#*.

When I did that, I did not find a CDA, however I found the following:

Global-C2 - user

However, this did not match up with the info online

I decided to search this to see if there was any others who had a mapping.
This post suggests looking at the certificate within the settings
https://old.reddit.com/r/SonyXperia/comments/16yxgcx/just_bought_1v_what_is_the_global_c2_region/kcj6yd4/

Matching it with the table on xpericheck and using process of elimination with the reply, I determined I have the CDA of 23243628 and a custom taiwan version Customized TW

CDA	Name	Latest Version	Avg Update Time	Discovered
23278672	Customized HK	61.2.A.0.472A	37 days	1 year 2 months ago
23243628	Customized TW	61.2.A.0.472A	38 days	1 year 2 months ago
23243684	Customized SEA	61.2.A.0.472A	37 days	1 year 2 months ago
23248625	Customized CN	61.2.G.0.72A	46 days	1 year 3 months ago
23243642	Customized RU	61.1.A.1.149	12 days	2 years 11 months ago

While researching the firmware, I came across this page
https://xdaforums.com/t/how-to-enable-volte-and-5g-without-permanent-root-on-xperia-5-iii-and-1-iii.4551847/

I’ll need to come back and review it another time as I am out of time for now

bedHedd · December 31, 2024, 12:06am

Getting stuck with the unlocking the bootloader

Unlocking the bootloader

info_outline
Note: The steps below only need to be run once per device.

warning
Warning: Unlocking the bootloader will erase all data on your device! This also includes your DRM keys, which are stored in the Trim Area partition (also called TA). Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed. If you wish to backup the TA partition first, you can find tutorials related to your device on the internet.

On the device, dial *#*#7378423#*#* (*#*#SERVICE#*#*) to launch the service menu.

Go to service info > configuration and check rooting status - you can only continue if it says Bootloader unlock allowed: Yes.

Go to System Settings > About Phone and record the first IMEI number, which is necessary to get an unlock code from Sony in a later step.

Enable OEM unlock in the Developer options under device Settings, if present.

Connect the device to your PC via USB.

These instructions worked and I was able to get my IMEI number for the unlock steps later

On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb -d reboot bootloader
You can also boot into fastboot mode via a key combination:

With the device powered off, hold Volume Up and connect the USB cable. The notification light should turn blue.

This also worked, as well as adb devices.

I had some issues with detecting fastboot, I enabled developer mode, usb debugging, and oem unlocking. However when I entered the bootloader, none of my fastboot commands worked.

When I ran lsusb, Sony Ericsson Mobile Communications AB XQ-BQ72 shows up when I have it booted up, but when I enter fastboot, the phone no longer shows up in fastboot.

intial attempts to figure out why fastboot was failing

Android file protocol

A quick search online I find this answer which gives me a hint
android - ADB stopping at <waiting for devices> - Stack Overflow

For me, I couldn’t even see my Android device in Windows 10 Device Manager until I went into Settings/General/Developer options and set Select USB Configuration to MTP (Media Transfer Protocol) instead of the default Charging Only, and also found a different USB cable that wasn’t a charging-only one. Then, as @sushanthkille indicated above, I still had to install an updated driver, but the way he describes via Device Manager didn’t work. For my LG G4, I had to go to https://www.lg.com/us/lgeai/Drivers/pages/mobile-drivers.html (found via googling for windows 10 LG G4 drivers) download the Windows driver, and install it manually. After all that, my G4 finally showed up in Windows 10.

Granted this answer has a different phone and is using windows, but the key point is MTP. I suspected that the configuration was set to something that isn’t MTP as when I tried to switch the usb controlled by setting, it wouldn’t let me change it to my pc

Sony’s documentation also has some references as well
My computer doesn't detect my Xperia device when connected through USB | Sony USA

filtering for my phone from the command `lsusb -v | nvim -`

...
Bus 001 Device 036: ID 0fce:520d Sony Ericsson Mobile Communications AB XQ-BQ72
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 [unknown]
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0fce Sony Ericsson Mobile Communications AB
  idProduct          0x520d XQ-BQ72
  bcdDevice            5.04
  iManufacturer           1 Sony
  iProduct                2 XQ-BQ72
  iSerial                 3 QV780DP49H
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x003e
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          4 mtp_adb
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         6 Imaging
      bInterfaceSubClass      1 Still Image Capture
      bInterfaceProtocol      1 Picture Transfer Protocol (PIMA 15470)
      iInterface              5 MTP
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x001c  1x 28 bytes
        bInterval               6
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     66 [unknown]
      bInterfaceProtocol      1 
      iInterface              6 ADB Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x0000211e
      BESL Link Power Management (LPM) Supported
    BESL value      256 us 
    Deep BESL value     8192 us 
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000f
      Device can operate at Low Speed (1Mbps)
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat           0 micro seconds
    bU2DevExitLat           0 micro seconds
Device Status:     0x0000
  (Bus Powered)
...

A quick review of the output returns the relevant sections

...
    iConfiguration          4 mtp_adb
...
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         6 Imaging
      bInterfaceSubClass      1 Still Image Capture
      bInterfaceProtocol      1 Picture Transfer Protocol (PIMA 15470)
      iInterface              5 MTP
...

There’s some conflicting information because it shows up as MTP and PTP.

USB auto detect dropping the connection

Since it has been a while since I last worked on this project, I suspected that dust may have thrown this error. I cleaned it out and attempted to change the settings, but was unable to pick the correct setting

I experienced this error earlier. I cleaned the usb out.

the cable, blasted unihertz cable

Unfortunately neither solutions above worked and with no other options I tried a different cable and port. I swapped my unihertz cable and tried using another Sony Xperia cable from my 5 ii. While researching, I came across this post
https://old.reddit.com/r/GalaxyTab/comments/sgj0ug/usb_controlled_by_connected_device_wont_switch/huxlivc/

I had this issue with my tab s7, the problem ended up being the USB I was using. Try using the one that came with the tablet, or another in general. There are some that don’t seem to let the tablet “talk” to the pc correctly. When I used a different usb it was fine.

With nothing to lose I gave the cable another shot

This time the phone was detected with lsusb -v and fastboot. To make it easier to read and copy, I used the | nvim -, Later while researching I learned I can also use | less to achieve the same

lsusb -v | nvim -

...
Bus 003 Device 058: ID 0fce:0dde Sony Ericsson Mobile Communications AB Android
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 [unknown]
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0fce Sony Ericsson Mobile Communications AB
  idProduct          0x0dde Android
  bcdDevice            1.00
  iManufacturer           1 Google
  iProduct                2 Android
  iSerial                 3 QV780DP49H
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     66 [unknown]
      bInterfaceProtocol      3 
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1

now I just need to update my udev rules and add a new entry for the sony. After some exhausting research, I had brave’s ai chatbot help me look for the needed commands.

These were the suggestions

brave's ai summary

Fedora Fastboot Device Permission

Based on the provided search results, here’s a concise answer to resolve the issue:

Verify udev rules: Check if the udev rules file /etc/udev/rules.d/51-android.rules exists and contains the correct rules for your device. You can use the following command to inspect the file:
sudo cat /etc/udev/rules.d/51-android.rules
 
If the file is missing or contains incorrect rules, you can create a new one or update the existing one. For example, if your device has an IDVendor of “8087” and IDProduct of “0020”, you can add the following rule:
SUBSYSTEM=="usb", ATTR{idVendor}=="8087", ATTR{idProduct}=="0020", MODE="0666", GROUP="plugdev"
 
Reload udev rules: After updating the udev rules file, reload the rules using:
sudo udevadm control --reload-rules
 
Trigger udev rules: Replug your device to trigger the udev rules update:
sudo udevadm trigger
 
Check permissions: Verify that your user is a member of the plugdev group:
id -nG | grep plugdev
 
If your user is not in the plugdev group, add them using:
sudo usermod -aG plugdev your_username
 
Try fastboot again: After updating the udev rules and verifying permissions, try running fastboot devices again:
fastboot devices
 
If you’re still encountering issues, you can try restarting your system or checking the system logs for any errors related to udev or fastboot.

Additionally, you can install the android-sdk-platform-tools-common package, which includes udev rules, using:
sudo dnf install android-sdk-platform-tools-common
 
This package provides a set of pre-configured udev rules for Android devices, which may resolve the issue.

Remember to replace “your_username” with your actual username, and “8087” and “0020” with your device’s actual IDVendor and IDProduct values.

In one of the searches it references this stackoverflow answer for the udev entry

Check device vendor id and product id:
$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 078: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 002 Device 003: ID 8087:07dc Intel Corp. 
Bus 002 Device 002: ID 5986:0652 Acer, Inc 
Bus 002 Device 081: ID 22b8:2e81 Motorola PCS 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Here my android device is Motorola PCS. So my vid=22b8 and pid=2e81.

Now create a udev rule:
$ sudo vi /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e81", MODE="0666", GROUP="plugdev"
Now the device is good to be detected once udev rule is reloaded. So, let’s do it:
$ sudo udevadm control --reload-rules
After this, again check if your device is detected by adb:
$ adb devices
List of devices attached
ZF6222Q9D9  device
So, you are done.

If it still doesn’t work, unplug/replug the device.

If it still doesn’t work, restart your OS.

so instead of the Motorola, it’s Sony

Bus 003 Device 058: ID 0fce:0dde Sony Ericsson Mobile Communications AB Android

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666", GROUP = "plugdev",

Then I reloaded the rules using the following commands from a response to a udev guide

Thanks for the guide!
Just want to mention that sudo service udev restart didn’t work for me - the device still didn’t show up.
But it did after running this:
sudo udevadm control --reload-rules
sudo udevadm trigger

gist.github.com

https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4?permalink_comment_id=2233307#gistcomment-2233307

fbootfix.md

## Determine your device id

1. Unplug your device from the computer and type `lsusb` in the terminal. You should get an output similar to this:
  ```bash
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller

This file has been truncated. show original

sudo udevadm control --reload-rules
sudo udevadm trigger

I don’t think it worked because I still needed to use sudo for my later fastboot commands

adding myself to the plugdev users group

Finally just to be safe, I ran the command brave suggested for adding my user to the plugdev group. I couldn’t find a source for this one, but it looked similar to this for the plugdev user

    sudo groupadd adbusers and sudo usermod -a -G adbusers $(whoami)

Android-tools not working? solved - #3 by gruhlstein - Fedora Discussion

sudo usermod -aG plugdev your_username

I thought since my last adventure, I wouldn’t need to deal with adding a udev entry nor updating my user group permissions, but I guess it is expected when working in Linux

Follow the instructions on Sony’s official unlocking website to generate an unlock code for your bootloader.
Use your code to unlock the bootloader of your device:
fastboot oem unlock <your_unlock_code>
Since the device resets completely, you will need to re-enable USB debugging to continue

These steps were pretty straight forward once I got the fastboot resolved. One Caveat is that Sony’s website for oem unlocking has a bunch of warnings of voiding my warranty for installing a custom rom.

checking out flashing additional partitions

Flashing additional partitions

warning

Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.

Download the following files from here.

dtbo.img

vbmeta.img

vendor_boot.img

Power off the device, and boot it into bootloader mode:

With the device powered off, hold Volume Up and connect the USB cable. The notification light should turn blue.

Flash the downloaded image files to your device by typing:
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot.img

These steps were pretty straight forward with fastboot detected

fumbling with recovery

In this section I made some missed inputs and got stuck trying to figure out how to access fastboot again. I got into a boot loop because I decided to reboot rather than power off and boot to recovery.

A major misconception was that I thought I needed to be in the bootloader to run fastboot commands. Being in the fastbootd menu is what I needed.

trying to figure out why I couldn’t interact with the fastboot cli

Aside from the misconception of being in the wrong menu/bootmode, I also wasn’t sure if my device was getting detected. Just to be safe, I updated my /etc/udev/rules.d/51-android.rules to update the entry for fastboot

lsusb
...
Bus 001 Device 060: ID 18d1:4ee0 Google Inc. Nexus/Pixel Device (fastboot)
...

udev entry

# /etc/udev/rules.d/51-android.rules
#Google Inc. 
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", TAG+="systemd", ENV{SYSTEMD_WANTS}="adb.service", GROUP = "plugdev"

Looking back I’m not sure if this actually changed it or not, but the combination of these got me a lineageos phone

Installing Lineage Recovery using fastboot

Download Lineage Recovery. Simply download the latest recovery file, named boot.img.

2.warning*

3.Important:* Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!

Flash recovery onto your device:
fastboot flash boot boot.img
Now reboot into recovery to verify the installation. Do not reboot into the existing OS, since it will overwrite the recovery you just installed!

With the device powered off, hold Volume Down + Power.

6.info_outline*

7.Note:* If you can’t power down the device, try long-pressing the key-combination (if any was used in the instructions above) until the device reboots and follow the instructions above

8.info_outline*

9.Note:* If your recovery does not show the LineageOS logo

, you accidentally booted into the wrong recovery. Please start at the top of this section!

after getting the device detected with sudo fastboot devices I redid this section to make sure I didn’t have the incorrect recovery.

verifying firmware partitions

Ensuring all firmware partitions are consistent

info_outline

Note: The steps below only need to be run once per device.

In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.

To do this, sideload the copy-partitions-20220613-signed.zip package by doing the following:

Download the copy-partitions-20220613-signed.zip file from here.

Sideload the copy-partitions-20220613-signed.zip package:

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using: adb -d sideload copy-partitions-20220613-signed.zip

3.info_outline*

4.Note:* The copy-partitions script was created by LineageOS developer erfanoabdi and filipepferraz

Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”

These steps were pretty straight forward and I didn’t run into any issues

actually installing it

These steps were pretty straight forward and I didn’t run into any issues

Installing LineageOS from recovery

Download the LineageOS zip file that you would like to install or build the package yourself.

If you are not in recovery, reboot into recovery:

With the device powered off, hold Volume Down + Power.

Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).

Return to the main menu.

Sideload the LineageOS .zip package but do not reboot before you read/followed the rest of the instructions!

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using: adb -d sideload filename.zip.

6.check*

7.Tip:* After the package is installed, recovery will inform you that reboot to recovery is required to install add-ons. In case you want to do that, please select “Yes,” otherwise “No”.

8.check*

9.Tip:* Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.

Installing Add-Ons

info_outline

Note: If you don’t want to install any add-on (such as Google Apps), you can skip this whole section!

warning

Warning: If you want to install Google Apps add-on package (use the arm64 architecture), you can download it from here. This add-on needs to be installed before booting into LineageOS for the first time!

Click Apply Update, then Apply from ADB, then adb -d sideload filename.zip for all desired packages in sequence.
When presented with a screen that says Signature verification failed, click Yes. It is expected as add-ons aren’t signed with LineageOS’s official key!

All set!

Once you have installed everything successfully, you can now reboot your device into the OS for the first time!

Click the back arrow in the top left of the screen, then “Reboot system now”.

info_outline

Note: The first boot usually takes no longer than 15 minutes, depending on the device. If it takes longer, you may have missed a step, otherwise feel free to get assistance.

bedHedd · January 19, 2025, 9:22pm

Since I opted for microg, my push notifications haven’t worked. This guide worked