Manual install
This is a guide for installing ProtonAOSP manually, using the command line. The web installer is recommended if you don’t have a specific need for this. Check the list of common misconceptions if you’re not sure.
You can only use a Windows, macOS, or Linux computer for this manual installation; use the web installer if you want to install from a Chromebook or another phone.
Download a build
Download the build you want to install in factory images format.
Prepare your phone
Put your device into bootloader mode by restarting it and holding the volume down button until you see a red warning sign or green Android robot.
Once your device is in bootloader mode, plug it into the computer or device you’re installing from. Make sure you use a high-quality USB cable, as many cables will cause issues. Avoid USB hubs if possible.
Your USB cable needs to be able to copy files. Charging-only cables won’t work.
If you’re switching from the stock OS or another ROM, make sure all your important data is backed up. You’ll need to wipe all your data in order to use ProtonAOSP.
Prepare your system
- Windows
- macOS
- Linux
First, open the “Command Prompt” app from the Start menu.
Next, download the Android SDK Platform Tools and extract them. Navigate to the extracted platform-tools
folder in the terminal by typing cd
(with the space at the end) and dragging the folder into Command Prompt. Then run the following command:
set PATH=%CD%;%PATH%
If it’s your first time installing from this computer, you also need to install drivers:
- Open Settings → Windows Update
- Click “Check for updates” and wait
- Click “View optional updates”
- Select the “Android Bootloader Interface” update (ignore the brand name; it doesn’t matter)
- Click “Download and install” and wait for it to finish
- Unplug your device and plug it back in
First, open the “Terminal” app from Applications -> Utilities.
Next, download the Android SDK Platform Tools and extract them. Navigate to the extracted platform-tools
folder in the terminal by typing cd
(with the space at the end) and dragging the folder into Terminal. Then run the following command:
export PATH="$PWD:$PATH"
First, open your terminal app of choice, such as Gnome Terminal, Konsole, or XTerm.
Next, install the Android platform tools. If you’re using Arch Linux:
sudo pacman -S android-tools
On other distributions, download the Android SDK Platform Tools and extract them. Navigate to the extracted platform-tools
folder in the terminal by typing cd
(with the space at the end) and dragging the folder into your terminal. Then run the following command:
export PATH="$PWD:$PATH"
If it’s your first time installing from this computer, you also need to install udev rules so that the tools can talk to your phone:
Distribution | Command |
---|---|
Arch Linux | sudo pacman -S android-udev |
Debian, Ubuntu | sudo apt install android-sdk-platform-tools-common |
Other | Instructions vary |
Wipe data
If you’re switching from the stock OS or another ROM, you need to wipe all data before installing ProtonAOSP:
fastboot -w
Otherwise, ProtonAOSP won’t boot and your phone will get stuck on the boot animation after the installation.
danger
All data on your phone will be lost, so make sure your important files are backed up before doing this.
Install the build
Factory images
Extract factory images
Extract the downloaded factory images package (e.g. proton-aosp_redfin-factory_11.5.0.zip
). Navigate to the new folder (e.g. redfin-rq2a.210505.003
) by typing cd
(with the space at the end) and dragging the folder into your terminal.
Flash factory images
Run the following command to flash the factory images:
- Windows
- macOS
- Linux
flash-all.bat
./flash-all.sh
./flash-all.sh
Don’t touch, unplug, or press any buttons on your device during the install. Your phone will restart several times, but don’t touch it. It will automatically boot into ProtonAOSP once the installation process completes.
Finish
You can now delete the factory images package, but don’t delete the platform tools — you’ll need them for updating in the future.
See First Steps for what to do next.
For security, you may also wish to re-lock the bootloader to enforce verified boot, which improves physical security and resistance against persistent attacks.