[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Slim2none4u:
Install PixelExperience on bramble​

WARNING: I copy and pasted thes instuctions. Please go to the offical guide for your device Bramble https://wiki.pixelexperience.org/devices/barbet/install/

WARNING: These instructions only work if you follow every section and step precisely.

Do not continue after something fails!

Basic requirements​

Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!

Make sure your computer has adb and fastboot. Setup instructions can be found here.

Enable USB debugging on your device.

warning

WARNING: Before following these instructions please ensure that the device is on the latest Android 12 firmware.

This is not necessarily the newest available version! Please up- or downgrade to the required version before proceeding (guides can be found on the internet!).

Flashing the vendor boot partition​

warning

WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.

Download this vendor_boot.img file.

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

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

Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):

fastboot flash vendor_boot <vendor_boot>.img

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! 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 PixelExperience once installed.

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

Connect the device to your PC via USB.

On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:

adb reboot bootloader

You can also boot into fastboot mode via a key combination:

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

Once the device is in fastboot mode, verify your PC finds it by typing:

fastboot devices

If you don’t get any output or an error:

on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!

on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!

Now type the following command to unlock the bootloader:

fastboot flashing unlock

info_outline

NOTE: At this point the device may display on-screen prompts which will require interaction to continue the process of unlocking the bootloader. Please take whatever actions the device asks you to to proceed.

If the device doesn’t automatically reboot, reboot it. It should now be unlocked.

Since the device resets completely, you will need to re-enable USB debugging to continue.

Flashing the vendor boot partition​

warning

WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.

Download this vendor_boot.img file.

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

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

Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):

fastboot flash vendor_boot <vendor_boot>.img

Temporarily booting a custom recovery using fastboot​

Download the PixelExperience Recovery. Simply download the latest recovery file.

Connect your device to your PC via USB.

On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:

adb reboot bootloader

You can also boot into fastboot mode via a key combination:

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

Once the device is in fastboot mode, verify your PC finds it by typing:

fastboot devices

If you don’t get any output or an error:

on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!

on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!

check

TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ... , fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.

Temporarily flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):

fastboot flash boot <recovery_filename>.img

info_outline

NOTE: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.

Installing PixelExperience from recovery​

Download the PixelExperience installation package 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. Then use the menu to select Recovery Mode.

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 PixelExperience .zip package:

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

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

check

TIP: Normally, adb will report Total xfer: 1.00x, but in some cases, even if adb: failed to read command: Success/No error. 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.

Once you have installed everything successfully, 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

check

TIP: If the installation process reports the message "(~47%) adb: failed to read the command: No error", do not worry, the process was completed successfully and you can restart the device.