Open main menu
SHIFT SHIFT6mq
SHIFT SHIFT6mq (axolotl)
SHIFT SHIFT6mq (axolotl)
Manufacturer SHIFT
Name SHIFT6mq
Codename shift-axolotl
Released 2020
Category community
Original software Android 10.0
postmarketOS kernel Mainline
Hardware
Chipset Qualcomm SDM845 Snapdragon 845
CPU Octa-core (4x 2.8 GHz Kryo 385 Gold & 4x 1.7 GHz Kryo 385 Silver)
GPU Adreno 630
Display 1080 x 2160 AMOLED
Storage 128 GB UFS 2.1
Memory 8 GB
Architecture aarch64
Features
USB Networking
Works
Flashing
Works
Touchscreen
Works
Display
Works
WiFi
Works
FDE
Works
Mainline
Works
Battery
Works
3D Acceleration
Works
Audio
Broken
Bluetooth
Works
Camera
Broken
GPS
Broken
Mobile data
Works
SMS
Works
Calls
Broken
USB OTG
Broken
NFC
Broken
USB-A
HDMI/DP
Keyboard
Touchpad
Sensors
Accelerometer
Broken
Magnetometer
Ambient Light
Proximity
Hall Effect
Barometer
Power Sensor
Misc
Ir TX
Unavailable
TrustZone
FOSS bootloader



Contributors

Users owning this device

  • Amartinz (Notes: Main device)
  • Kalube (Notes: postmarketOS porting)
  • Maxnet (Notes: daily driver with Android Distro (for now))


Boot modes

By holding various button combinations while booting the device can be made to boot into different modes.

Unplug from USB, power off the device and press and hold the below buttons to enter the specific boot mode.

Boot mode Power Up Down
Fastboot Y Y N
Recovery Y N Y
EDL Y Y Y

Bootloader

Unlock bootloader

To unlock the bootloader, you need to allow unlocking it via enabling OEM unlocking within Android.

  1. Go to Settings within Android and select About
  2. Tap on Build number seven times to enable developer options
  3. Go back and select System, Advanced and scroll down to Developer options
  4. Enable Advanced restart and OEM unlocking
  5. Reboot into bootloader by long pressing the power button, selecting Restart and Bootloader

After it has successfully rebooted into Fastboot mode, initiate unlocking the bootloader using fastboot:

$ fastboot flashing unlock

Please follow the prompts on the screen to finish unlocking the bootloader.

  WARNING: This will erase your data, please back up important data before unlocking the bootloader.

Customization

Custom AVB key

  This is not fully relevant for postmarketOS, as AVB is currently unsupported, but documented for the future.

The bootloader has support for setting an user provided AVB key to allow relocking the bootloader if an OS with proper support is flashed.

This is realized with exposing a virtual partition avb_custom_key where the custom user key can be flashed to:

$ fastboot flash avb_custom_key avb_key.bin

For more information please refer to the commit FastbootCmds: oem device-info: check if user public key is set.

Mainline support

Bootloaders since version 202205227 support additional fastboot oem commands to enable certain Quality of Life improvements when running mainline.

For example this will ignore the slot retry count, until we have userspace support for marking bootup attempts as successful.

To enable mainline support:

$ fastboot oem enable-mainline-support

To disable mainline support:

$ fastboot oem disable-mainline-support

To check the current status of mainline support:

$ fastboot oem device-info
(bootloader) Mainline support enabled: true/false

Fastbootd

Fastbootd is a userspace implementation of Fastboot. For axolotl it is located within the recovery.

To access it, you can boot the recovery and select a menu option to enter fastbootd mode. Optionally you can also enter it via ADB and Fastboot:

$ # Enter fastbootd via adb
$ adb reboot fastboot
$ # Enter fastbootd via fastboot
$ fastboot reboot fastboot

You can only access dynamic partitions within fastbootd.

  As fastbootd lives within the recovery, you need a valid recovery image installed in the currently active slot to access it.

Installation

Follow the installation guide's "Initialization" section, using shift as the vendor and axolotl as the codename but stop before following flashing instructions, as these are different for axolotl.

There are currently different ways to install postmarketOS (only select one).

Installation on userdata partition

Installation on userdata is the most generic and universally supported way, however it does not allow for dual boot or utilizing the full flash storage of the device.

Reboot into Fastboot mode and install postmarketOS:

$ # Flash rootfs to userdata partition
$ pmbootstrap flasher flash_rootfs --partition userdata
$ # Flash kernel to boot
$ pmbootstrap flasher flash_kernel
$ # Erase dtbo partition, as it conflicts with our mainline kernel
$ # Note: this operation takes some time to complete
$ fastboot erase dtbo
$ # Reboot into postmarketOS
$ fastboot reboot
  fastboot can sometimes misbehave, if any of the fastboot commands fail you should run fastboot reboot bootloader (or reboot manually using the interface on the device) and then repeat the failed command.

Installation on super partition

  WARNING: This is currently work in progress and actively worked on.

First select a slot (a or b) you want to install postmarketOS on.

  This guide assumes you want to install onto the a slot. Replace a with b depending on the slot you want to install on.

To install on super partition, a valid recovery with proper fastbootd implementation needs to be installed into the slot, which you want to install postmarketOS on. You can download the stock recovery image, provided by the manufacturer and install it within Fastboot mode:

  You can select the slot to install on via appending _SLOT to the partition name (for example boot_a, boot_b, ...).
$ # Install recovery in "a" slot
$ fastboot flash recovery_a recovery_stock.img

Enter Fastbootd and ensure it is working as expected:

$ # Set "a" as active slot and reboot to fastbootd
$ fastboot --set-active=a
$ fastboot reboot fastboot
$ # Verify current slot is "a"
$ fastboot getvar current-slot

After you verified fastbootd works in the slot you have selected, you can install postmarketOS:

$ # Flash rootfs to system_a partition
$ pmbootstrap flasher flash_rootfs --partition system_a
$ # Flash kernel to boot
$ pmbootstrap flasher flash_kernel --partition boot_a
$ # Reboot to bootloader, as erasing dtbo is not working in fastbootd
$ fastboot reboot bootloader
$ # Erase dtbo_a partition, as it conflicts with our mainline kernel
$ # Note: this operation takes some time to complete
$ fastboot erase dtbo_a
$ # Reboot into postmarketOS
$ fastboot reboot

See also