Install /e/ on a Razer Phone 2 - “aura”

Tip: Please read through the instructions at least once before actually following them, so as to avoid any problems later.

Warning: Downgrading Smartphones already on Android Q or LineageOS 17.x to Pie or other OS can cause instability or at worst brick some devices

Caution: Flash your device only if you know what you are doing and are OK taking the associated risk. All builds are provided as best effort, without any guarantee. The /e/ project and its project members deny any and all responsibility about the consequences of using /e/ software and or /e/ services.

Requirements

If required take a backup of all important data from your phone on an external storage device before proceeding.
Do not take a backup on the same device as some of these actions will format the device and delete the backup.
Ensure your phone is charged more than 50%
Check that adb and fastboot are enabled on your PC. If not you can find the setup instructions here
Download all the files and images mentioned in the download section below before starting the installation
Make sure you have a working data cable to connect your device to the PC. There are cables which are only for charging and do not transfer data.
Enable USB debugging on your device. You can find the instructions here

Caution: Do not install /e/OS on top of a higher version of stock OS. Before installing /e/OS ensure your device has the latest stock OS of the same version as /e/OS. If only lower versions of the stock are available then install the last available lower version before installing /e/OS.

Downloads for the aura

Try the /e/ Recovery (limited functionality)

/e/ Recovery for dev build

/e/OS build : R dev

To understand the difference between /e/OS builds check this guide

Warning: Please note some of the above links can lead to external sites

Unlocking the bootloader

Tip: The steps given 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 an online drive

Enable OEM unlock in the Developer options under device Settings, if present.
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
```
Tip: If you see no permissions fastboot while on Linux or macOS, try running fastboot as root.
Now type the following command to unlock the bootloader:
```
 fastboot flashing unlock
```
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.

Temporarily Booting a custom recovery using `fastboot`

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
```
Once the device is in fastboot mode, verify your PC finds it by typing:
```
 fastboot devices
```
Flash a recovery image onto your device
```
 fastboot flash boot recoveryfilename.img
```
Replace the recoveryfilename with the name of the recovery image you downloaded in the previous section
Manually reboot into recovery mode

With the device powered off
hold Volume Up + Power.

Tip: 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 /e/ from recovery

Before proceeding ensure you have downloaded the /e/OS for your device, from the link given in the Downloads section above
If you aren’t already in recovery mode, reboot into recovery mode by typing the below command in the console of an adb enabled PC
```
 adb reboot recovery
```
Tip: You can also do this manually using the below key combination
- With the device powered off, hold Volume Up + Power.
In TWRP return to main menu, then tap Wipe
Now tap Format Data and continue with the formatting process.
Here a new screen may show where you will have to type Yes and confirm the action by clicking a button.
Caution: Format Data will remove encryption as well as delete all files stored on the internal storage. Remember to take a backup first. Check Requirements section above.
Return to the previous menu and tap Advanced Wipe.
Select the Cache and System partitions to be wiped and then Swipe to Wipe
Sideload the /e/ .zip package.
Tip: Sideload requires actions in two places to be done. One on your phone in the TWRP UI and secondly on the connected PC which should have adb enabled. Also note the sideload process while running may stop abruptly around 50%. The console would show a message Total xfer: 1.00x. This would mean that the transfer has successfully completed.
- On the device in TWRP,
  select Advanced, ADB Sideload, then swipe to begin sideload.
- On the host machine, in the console , start the sideload of the package by typing
```
 adb sideload filename.zip
```
Tip: Change the filename to the name of the file you downloaded
Once installation has finished, return to the main menu, tap Reboot, and then System

Warning: Avoid installing any additional apps or services if suggested by the recovery. They may cause your device to bootloop, as well as attempt to access and or corrupt your data.

Success: Congratulations !! Your phone should now be booting into /e/OS !!

To find some troubleshooting tips… click here

adb

Getting a Total xFer ':' 0.01x message - Try to upload the /e/OS to internal storage and retry to install
adb ':' sideload connection failed ':' insufficient permissions for device error - Try to execute the commands adb kill-server and adb start-server and retry
Running adb shell twrp install /sdcard/</e/ zip package> raise non-existent directory error - Try to check solution here
Getting an insufficient permissions error - Try the solution given here
When running "adb devices" in bash a device is shown as "unauthorized" - Try the solution given here

TWRP

Errors while running TWRP version 3.4.x.x or above - Try downloading and using a previous TWRP version.. below 3.4.x.x
In TWRP if this error shows up failed to mount /preload - Try in TWRP wipe screen in advanced menu select preload and swipe to wipe
/cache/recovery/xxx -> no such file or directory error while flashing a ROM - On PC run adb shell in the console now create a folder called recovery for e.g. here the devicecode name is violet "violet :/cache# mkdir recovery"

Connectivity

Trying to troubleshoot mobile connectivity issues - Read this guide

Tip: To suggest changes to this install guide documentation, please visit the Phone 2 specific topic on our community forum. To report issues in the build please refer this guide

This documentation “Install /e/ on a Razer Phone 2 - “aura”” is a derivative of “install LineageOS on aura” by The LineageOS Project, used under CC BY.