Make sure that your model is actually listed in the “Supported models” section here (exact match required!)
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!
warning
Warning: Before following these instructions please ensure that the device is currently using Android 13/14 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/14, please up- or downgrade to the required version before proceeding
(guides can be found on the internet!).
By clicking the following button you are confirming that you've met all of the basic requirements and read the warnings.
Pre-Install Instructions
warning
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option at least 7 times, in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Run Odin3 v3.14.4 found in the newly extracted “Odin_3.14.4” folder.
Check the box labeled next to the button labeled “AP”, and then click the “AP” button.
In the menu that pops up, select the downloaded vbmeta.tar file.
Power off the device, and again boot it into download mode:
With the device powered off, hold Volume Up + Volume Down and connect USB cable to PC.
Check in the top left of the Odin window that you see a valid device, it will show up as something like COM0.
check
Tip: The COM port, or the number succeeding COM, may be any valid number.
Click “Start”. A transfer bar will appear on the device showing the VBMeta image being flashed.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Important Information
info_outline
Note: The following instructions require a machine running Windows 10 build 17063 or newer.
Samsung devices come with a unique boot mode called “Download mode”, which is very similar to “Fastboot mode” on some devices with unlocked bootloaders.
Odin is a Samsung-made tool for interfacing with Download mode on Samsung devices.
The preferred method of installing a custom recovery is through Download Mode – rooting the stock firmware is neither necessary nor required.
Installing a custom recovery using Odin
info_outline
Note: If this device’s install instructions already had you download Odin/Enable OEM Unlocking earlier in the installation process, you can skip the steps for enabling OEM Unlock, as well as for downloading and extracting the drivers and Odin.
Enable Developer Options by pressing the “Build Number” option 10 times, in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Run Odin3_v3.14.4 found in the newly extracted “Odin_3.14.4” folder.
Check in the top left of the Odin window that you see a valid device, it will show up as something like COM0.
check
Tip: The COM port, or the number succeeding COM, may be any valid number.
In the left side of the Odin window, you will see an “Options” tab, click it, and then un-check the “Auto Reboot” option.
Check the box labeled next to the button labeled “AP”, and then click the “AP” button.
In the menu that pops up, select the newly downloaded custom recovery .tar or .tar.md5.
check
Tip: The filename may vary depending on your device, and the version of your custom recovery.
Click “Start”. A blue transfer bar will appear on the device showing the recovery image being flashed.
info_outline
Note: The device will continue to display Downloading... Do not turn off target!! even after the process is complete. When the status message in the top left of the devices’s display reports that the process is complete, you may proceed.
Manually reboot into recovery, press the Volume Down + Power buttons for 7~10 seconds (or unplugging the device, pulling device battery out and putting it back in, then replugging back the phone to a pc) until the screen turns black & release the buttons immediately when it does, then boot to recovery:
With the device powered off, hold Volume Up + Power while the device is connected to a PC via USB cable.
info_outline
Note: Be sure to reboot into recovery immediately after installing the custom recovery. If you don’t the custom recovery will be overwritten on boot.
With the device powered off, hold Volume Up + Power while the device is connected to a PC via USB cable.
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 the process succeeds the output will stop at 47% and report Total xfer: 0.98x or 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.
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.
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.