Install /e/OS on a SHIFT - SHIFT6mq axolotl
This guide installs /e/OS on your axolotl. Read it through once before you start, so you don’t hit surprises partway in. Downgrading from a newer OS version than the /e/OS build you’re about to install can cause instability or brick some devices — check your current OS version first. Flashing is done at your own risk: /e/OS builds are provided as best effort, without any guarantee, and the /e/OS project takes no responsibility for the consequences.
Requirements
- Back up your important data to an external storage device — some of the steps below format the phone, wiping any backup left on it.
- Charge your phone above 50%.
- Enable
adbandfastbooton your PC — setup instructions. - Download every file listed in the Downloads section below before you start.
- Use a real data cable — some cables only charge and can’t transfer data.
- Enable USB debugging on your device — instructions.
- Confirm your exact model in the Device Selector: where shown, hover the device name for the supported model number, and check it matches yours exactly.
- Boot the stock OS at least once and check everything works — SMS, calls, and both over WiFi and LTE if available (some devices need VoLTE/VoWiFi used once on stock to provision IMS). Whatever’s broken on stock stays broken on /e/OS.
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device. Click on Details below for detailed information
To check the security patch level on your phone with a locked bootloader, prior to installing /e/OS, open your phone
Settings » About Phone » Android Version » Android Security Patch Level.Then compare it against the level of the security patch on the /e/OS build as visible in the Downloads for axolotl section below.
The following values control whether anti-rollback features are triggered on axolotl:
* Rollback protection errors trigger if you install an update whose version number is LESS than the rollback index’s value stored on device.
* The value of rollback index is UPDATED to match ro.build.version.security_patch’s value of the currently installed version, but only if the bootloader is LOCKED.
* The value of rollback index is NOT dependent on the currently installed ANDROID VERSION.
* The value of rollback index can NEVER be DOWNGRADED.
* Rollback protection errors are FATAL when the bootloader is LOCKED.
* Rollback protection errors are IGNORED when the bootloader is UNLOCKED.
Here are some examples to help you understand how anti-rollback features work:
Example 1
* Your axolotl with Google Android has a Security Patch Level saying June 5, 2022
* The /e/OS build available says: /e/OS build : R official (Security patch: 2022-05-05)
* In this example, the /e/OS build has an older Security Patch level than the origin, so the anti-roll back protection will trigger, and you will brick your phone
Example 2
* Your axolotl with Google Android has a Security Patch Level saying June 5, 2022.
* The /e/OS build available says: /e/OS build : R official (Security patch: 2022-06-05)
* In this example, the /e/OS build has the same Security Patch level than the origin, so the anti-roll back protection will pass, and you will be able to install /e/OS with no issues.
Example 3
* Your axolotl runs Google Android -R while /e/OS is now available based on AOSP -S.
* Your axolotl with Google Android has a Security Patch Level saying 2022-10-03 or October 3rd, 2022.
* The /e/OS build available says: /e/OS build : S official (Security patch: 2022-06-05)
* In this example, the /e/OS build has an older Security Patch level than the origin, so the anti-roll back protection will trigger, even if the /e/OS version runs on a more recent version of AOSP. In this example, you will brick your phone.
Downloads for axolotl
Not sure which one to pick? See official vs. community builds.
Unlocking the bootloader
These steps only need to be run once per device. Unlocking the bootloader will erase all data on your device — make sure anything you want to keep is backed up (see Requirements above). Not sure what unlocking changes on your device? See Bootloader relocking.
no permissions fastboot while on Linux or macOS, try running fastboot as root.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 bootloaderYou can also boot into fastboot mode via a key combination:
- With the device powered off
- hold Volume Up + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devicesNow type the following command to unlock the bootloader:
fastboot flashing unlockIf 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.
Installing /e/OS
Windows users: run these commands in Git Bash, not in the default command prompt.
Let’s proceed with the installation:
Unzip the file you downloaded from the link in the
Downloads for axolotlsection above.unzip <fileyoudownloaded>Replace
<fileyoudownloaded>with the name of the file you downloaded. You can also unzip it using a File Manager/File Explorer.Confirm that the folder where you unzipped the files contains the following:
bin-linux-x86directory - which contains linux tools including fastboot and adbbin-msysdirectory - which contains Windows tools including fastboot and adb.imgfiles - The.imgfiles that are to be flashed onto the device.flash_axolotl_factory.sh- The installer script.
Boot your axolotl into bootloader/fastboot mode:
- With the device powered off
- hold Volume Up + Power.
Open a terminal (Linux) or Git Bash (Windows) in the folder that contains
flash_axolotl_factory.sh— right-click inside the folder and choose “Open terminal here” / “Open Git Bash here”. Then make the script executable and run it:chmod +x flash_axolotl_factory.sh && ./flash_axolotl_factory.shThe
chmodstep may require root/sudoprivileges.The device reboots automatically once all the required files have been installed.
To find some troubleshooting tips… click here
adb
- Getting a
Total xFer ':' 0.01xmessage - Try to upload the /e/OS to internal storage and retry to install adb ':' sideload connection failed ':' insufficient permissions for deviceerror - Try to execute the commandsadb kill-serverandadb start-serverand retry- Getting an
insufficient permissionserror - Try the solution given here - When running "adb devices" in bash a device is shown as "unauthorized" - Try the solution given here
Connectivity
- Trying to troubleshoot mobile connectivity issues - Read this guide
Please share your experience , suggest tips or changes to this install guide documentation by visiting the SHIFT6mq specific topic on our community forum. To report issues in /e/OS please refer this guide