Install PixelExperience on a7y17lte
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
. Setup instructions can be found here. - Enable USB debugging on your device.
- 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: Before following these instructions please ensure that the device is currently using Android 8.0 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 8.0, please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
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 8.0, please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
Preparing for installation
Samsung devices come with a unique boot mode called “Download mode”, which is very similar to “Fastboot mode” on some devices with unlocked bootloaders. Heimdall is a cross-platform, open-source 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.
- Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
- From within the Developer options menu, enable OEM unlock.
- Download and install the appropriate version of the Heimdall suite for your machine’s OS
- Windows: Extract the Heimdall suite zip and take note of the new directory containing
heimdall.exe
. You can verify Heimdall is functioning by opening a Command Prompt or PowerShell in that directory and runningheimdall version
.- If you receive an error, install the Microsoft Visual C++ 2015-2019 Redistributable Package (x86) on your computer.
- Linux: Extract the Heimdall suite zip and take note of the new directory containing
heimdall
. Now copyheimdall
into a directory in $PATH, a common one on most distros will be /usr/local/bin. For examplecp heimdall /usr/local/bin
. You can verify Heimdall is functioning by opening a Terminal and runningheimdall version
. - macOS: Mount the Heimdall suite DMG. Now drag
heimdall
down into the/usr/local/bin
symlink provided in the DMG. You can verify Heimdall is functioning by opening a Terminal and runningheimdall version
.
Note: These Heimdall suite distributions were built by LineageOS Developers Nolen Johnson (npjohnson) and Jan Altensen (Stricted), as the Heimdall suite executables distributed on the official Heimdall website were outdated and the repo mostly abandoned. Modifications were made to make it build and function on modern OSes. - Windows: Extract the Heimdall suite zip and take note of the new directory containing
- Power off the device, and boot it into download mode:
- With the device powered off, hold Volume Down + Home + Power.
- Now, click the button that the on screen instructions correlate to “Continue”, and insert the USB cable into the device.
- For Windows users only: install the necessary drivers. A more complete set of instructions can be found in the Zadig user guide.
- If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Samsung Kies.
- Run
zadig.exe
found in your extracted Heimdall directory.Note: For the interested, source and documentation for zadig.exe can be found here. - Choose Options » List all devices from the menu.
- Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu.
- Click Replace Driver, then selecting Install Driver from the drop down list built into the button.
- If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that accept the warnings and allow you to carry on.
- On your machine, open a Command Prompt or PowerShell (Windows) window, or Terminal (Linux or macOS) window, and type:
heimdall print-pit
- If the device reboots that indicates that Heimdall is installed and working properly. If it does not, please refollow these instructions to verify steps weren’t missed, try a different USB cable, and a different USB port.
Installing a custom recovery using heimdall
- Download the custom recovery.
Tip: Ensure you download the
.img
file and not the .tar
or .tar.md5
versions.<div class="alert alert-warning" role="alert"><div class="alert-icon"><i class="material-icons">warning</i></div><div class="alert-text" markdown="span"><b>Important:</b> Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!</div></div>
- Power off the device, and boot it into download mode:
- With the device powered off, hold Volume Down + Home + Power.
- Now, click the button that the on screen instructions correlate to “Continue”, and insert the USB cable into the device.
- On your machine, open a Command Prompt or PowerShell (Windows) window, or Terminal (Linux or macOS) window, and type:
heimdall flash --RECOVERY <recovery_filename>.img --no-reboot
Tip: The file may not be named identically to what stands in this command, so adjust accordingly. If the file is wrapped in a zip or tar file, extract the file first, because Heimdall is not going to do it for you. - A blue transfer bar will appear on the device showing the recovery image being flashed.
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 device’s display reports that the process is complete, you may proceed. - Unplug the USB cable from your device.
- Manually reboot into recovery, this may require pulling the device’s battery out and putting it back in, or if you have a non-removable battery, press the Volume Down + Power buttons for 8~10 seconds until the screen turns black & release the buttons immediately when it does, then boot to recovery:
- With the device powered off, hold Volume Up + Home + Power.
Note: Be sure to reboot into recovery immediately after installing the custom recovery. If you don’t the stock ROM will overwrite the custom recovery with the stock recovery, and you’ll need to flash it again.
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 + Home + Power.
- Now tap Wipe.
- Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
- Sideload the PixelExperience
.zip
package:- On the device, select “Advanced”, “ADB Sideload”, then swipe 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, run ‘adb reboot’.
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.
Warning: Depending on which recovery you use, you may be prompted to install additional apps and services.
We strongly advise you to opt out of installing these, as they may cause your device to bootloop,
as well as attempt to access or corrupt your data.
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.