Install PixelExperience on alioth
Back to the overviewWarning: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
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
andfastboot
. Setup instructions can be found here. - Enable USB debugging on your device.
- Boot your device with the stock OS at least once and check every functionality. 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 PixelExperience either! Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.
- PixelExperience is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!
Unlocking the bootloader
Note: The steps below only need to be run once per device.
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.
Note: The following instructions require a machine running Windows 7 or newer.
- Create a Mi account on Xiaomi’s website.
Tip: A Mi account is required to unlock the bootloader. Beware that one account is only allowed to unlock one unique device every 30 days.
- Add a phone number to your Mi account.
- Insert a SIM into your phone.
- Enable developer options in
Settings
>About Phone
by repeatedly tappingMIUI Version
. - Link the device to your Mi account in
Settings
>Additional settings
>Developer options
>Mi Unlock status
. - Download the Mi Unlock app (Windows is required to run the app).
- Run the Mi Unlock app and follow the instructions provided by the app.
Note: The app may tell you that you have to wait up to 30 days. If it does so, please wait the quoted amount of time before continuing to the next step.
- After device and Mi account are successfully verified, the bootloader should be unlocked.
- Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing the vendor boot partition
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. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
- Flash a the downloaded images to your device by typing (replace
<vendor_boot>
with the actual filename!):
fastboot flash vendor_boot <vendor_boot>.img
Booting a custom recovery using fastboot
-
Download the PixelExperience Recovery. Simply download the latest recovery file.
Important: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above! - Connect your device to your PC via USB if it isn’t already.
- If your device isn’t already in fastboot mode, 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. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
- 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 runningfastboot
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!
Tip: Some devices have buggy USB support while in bootloader mode, if you seefastboot
hanging with no output when using commands such asfastboot 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. - Flash a recovery on your device by typing (replace
<recovery_filename>
with the actual filename!):fastboot flash boot <recovery_filename>.img
Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash toboot__a
/boot__b
rather thanboot_a
/boot_b
if you try to flashboot
. In this case, you must updatefastboot
to a release newer than or equal to31.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 toboot__a
, you must flash toboot_a
. - Now reboot into recovery to verify the installation.
- Type the command:
fastboot reboot-recovery
Note: If your recovery does not show the PixelExperience logo, you accidentally booted into the wrong recovery. Please start at the top of this section! - Type the command:
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 Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
- 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
.Tip: Normally, adb will reportTotal xfer: 1.00x
, but in some cases, even if the process succeeds the output will stop at 47% and reportTotal xfer: 0.98x
oradb: failed to read command: Success
. In some cases it will reportadb: failed to read command: No error
oradb: 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”.
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.
Get assistance
After you’ve double checked that you followed the steps precisely, didn’t skip any and still have questions or got stuck, feel free to ask on our Telegram group.