Link Search Menu Expand Document

Sailfish X Xperia Android 11 Build and Flash

Sailfish OS Hardware Adaptation Development Kit for Sony Xperia 10 III

Here you will find instructions how to build Sailfish OS image and flash it to Sony Xperia 10 III device, which can be used as reference to port any other Sony Xperia Open Device that has Android 11 support.


Please download the latest Sailfish OS HADK (Hardware Adaptation Development Kit) from within this link.

Please check the requirements for your build host:

Minimum Sailfish OS version for this port is You can also use Sailfish OS version Using Platform SDK version is strongly recommended. While it is possible to build with Platform SDK, these instructions assume using version

If you are new to HADK, please carefully read the disclaimer on page 1, then chapters 1 and 2.

The disk space requirement for this build is not what HADK says, but around 300GB . The download size requirement is around 50GB.

HADK uses LineageOS/CyanogenMod as reference base. Here we’ll instead have AOSP (Android Open Source Project) 11.0. Now you can read through chapter 3 of the HADK.

If you ever run into difficulties, please look through the links in the topic of the #sailfishos-porters channel on IRC at

In chapter 4 (Setting up the SDKs) setup the environment as requested in ~/.hadk.env, but then set and add the following additional variables (here we’ll build for Sony Xperia 10 III, Dual SIM variant being its only one):

export VENDOR=sony
export DEVICE=xqbt52
export HABUILD_DEVICE=pdx213
export FAMILY=lena

Follow through the chapter 4 until the end, and ignore chapter 5, instead perform the following:


sudo apt-get install cpio libssl-dev ccache
sudo mkdir -p $ANDROID_ROOT
sudo chown -R $USER $ANDROID_ROOT
git clone --recurse-submodules$FAMILY .

git config --global "Your Name"
git config --global ""

You’ll need to ensure you have the repo command from the AOSP source code repositories installed. See the Android Source instructions for how to install it. Once available you can continue:

# To save space, you can add "--depth=1 -c" flags to repo init:
repo init -u -b $HAVERSION -m tagged-localbuild.xml
# Adjust X to bandwidth capabilities
repo sync -jX
git clone --recurse-submodules droid-src -b "hybris-"$HAVERSION
ln -s droid-src/patches
droid-src/ --mb
./ --mb

source build/
export USE_CCACHE=1
export CCACHE_EXEC=/usr/bin/ccache
lunch aosp_$DEVICE-user
cd kernel/sony/msm-4.19/common-kernel
./ -d $HABUILD_DEVICE -O $ANDROID_ROOT/out/target/product/$HABUILD_DEVICE/obj/kernel || echo ERROR: kernel build failed, please inspect the log file
# FIXME after this is merged and reapplied:
cp dtbo-$HABUILD_DEVICE.img $ANDROID_ROOT/out/target/product/$HABUILD_DEVICE/dtbo.img
cd -
git clone external/droidmedia
make -j$(nproc --all) hybris-hal droidmedia
# This might take some time (1 hour on Intel Xeon's 12 cores)

If you encounter errors, check with HADK’s section 5.5 “Common Pitfalls”.

Once you have hybris-boot.img, hybris-recovery.img, and droidmedia files (including mini*service et al.) successfully built, go through chapter 6 of the HADK document.

Ignore chapter 7, but do the following instead:


sudo zypper ref
rpm/dhd/helpers/ --droid-hal

If the above command prints: Fatal: None of the selected test suites operate on the selected test levels. Nothing to do. Ignore the error message, instead check the output of:

ls droid-local-repo/xqbt52

The output should be like:


Now continue with:

git clone --recursive$FAMILY hybris/droid-configs -b upgrade-4.5.0
if [ -z "$(grep patterns-sailfish-consumer-generic $ANDROID_ROOT/hybris/droid-configs/patterns/patterns-sailfish-device-configuration-$" ]; then
  sed -i "/Summary: Jolla Configuration $DEVICE/aRequires: patterns-sailfish-consumer-generic\n\n# Early stages of porting benefit from these:\nRequires: patterns-sailfish-device-tools" $ANDROID_ROOT/hybris/droid-configs/patterns/patterns-sailfish-device-configuration-$
# Clean out unavailable packages
if [ -n "$(grep modem_auto_config $ANDROID_ROOT/hybris/droid-configs/patterns/patterns-sailfish-device-adaptation-$" ]; then
  sed -i "/modem_auto_config/d" $ANDROID_ROOT/hybris/droid-configs/patterns/patterns-sailfish-device-adaptation-$
if [ -n "$(grep ofono-vendor-qti-radio-plugin $ANDROID_ROOT/hybris/droid-configs/patterns/patterns-sailfish-device-adaptation-$" ]; then
  sed -i "/ofono-vendor-qti-radio-plugin/d" $ANDROID_ROOT/hybris/droid-configs/patterns/patterns-sailfish-device-adaptation-$
rpm/dhd/helpers/ --configs

If the above command prints: Fatal: None of the selected test suites operate on the selected test levels. Nothing to do. try running it again.

cd hybris/mw/libhybris
git checkout upgrade-4.5.0
cd -

rpm/dhd/helpers/ --mw # select "all" option when asked

Without waiting for the middleware to finish, open new shell terminal.


sudo mkdir -p $ANDROID_SYSPART
# If you plan to contribute to syspart (/system partition), remove the "--depth=1 -c" flags below
repo init -u -b $HAVERSION -m tagged-manifest.xml --depth=1 -c
# Adjust X to bandwidth capabilities
repo sync -jX --fetch-submodules
ln -s rpm/patches .
rpm/ --mb

source build/
export USE_CCACHE=1
export CCACHE_EXEC=/usr/bin/ccache
lunch aosp_$DEVICE-user
# Ensure the middleware in the previous shell terminal has finished building
# Change $(nproc --all) to your building capabilities, it will be very heavy on RAM if you go for more cores, proceed with care:
make -j$(nproc --all) systemimage vendorimage
# This might take some time (~2.5 hours on Intel Xeon's 12 cores)

mkdir -p $ANDROID_SYSPART-tmp
sudo mkdir -p $ANDROID_SYSPART-mnt-system
simg2img $ANDROID_SYSPART/out/target/product/$HABUILD_DEVICE/system.img $ANDROID_SYSPART-tmp/system.img.raw
sudo mount $ANDROID_SYSPART-tmp/system.img.raw $ANDROID_SYSPART-mnt-system

sudo mkdir -p $ANDROID_SYSPART-mnt-vendor/vendor
simg2img $ANDROID_SYSPART/out/target/product/$HABUILD_DEVICE/vendor.img $ANDROID_SYSPART-tmp/vendor.img.raw
sudo mount $ANDROID_SYSPART-tmp/vendor.img.raw $ANDROID_SYSPART-mnt-vendor/vendor

cd $ANDROID_ROOT/hybris/mw
git clone --recursive$D
cd $D
# The following command will throw up patch errors for `init.wod.rc`, `ld.config.28.txt` and `ld.config.29.txt`. These are to be expected and can be ignored.
sudo droid-system-device/helpers/ $ANDROID_SYSPART-mnt-system/system $ANDROID_SYSPART-mnt-vendor/vendor rpm/droid-system-$HABUILD_DEVICE.spec
sudo chown -R $USER .
# You can commit the changes, but before you push them out, make sure:
# - to check binary file/repo size limits
# - to rename the public repo as droid-system-sony-$FAMILY-$HABUILD_DEVICE
# - to not contribute binary files to this *-template repo
sudo umount $ANDROID_SYSPART-mnt-vendor/vendor
sudo umount $ANDROID_SYSPART-mnt-system
rm $ANDROID_SYSPART-tmp/{system,vendor}.img.raw
sudo rm -rf $ANDROID_SYSPART-mnt-{system,vendor}
rmdir $ANDROID_SYSPART-tmp || true

You can now close the above shell terminal. Next, please proceed with:


rpm/dhd/helpers/ --gg

rpm/dhd/helpers/ --mw=$FAMILY --spec=rpm/droid-hal-$HABUILD_DEVICE-img-boot.spec

rpm/dhd/helpers/ --mw= --spec=rpm/droid-system-$HABUILD_DEVICE.spec --spec=rpm/droid-system-$HABUILD_DEVICE-$DEVICE.spec

git clone --recursive$FAMILY hybris/droid-hal-version-$DEVICE
rpm/dhd/helpers/ --version

# The next two variables are explained in chapter 8
export RELEASE=
export EXTRA_NAME=-my1
sudo zypper in lvm2 atruncate pigz android-tools
sed -i "s @DEVICEMODEL@ $DEVICE " $srcks
rpm/dhd/helpers/ --mic

The command above will yield a flashable archive, such as $ANDROID_ROOT/SailfishOS-release-<version>-<device>-my1/SailfishOS--my1-<version>-<device>-<hw-version>.zip that you’ll use to flash your device as explained in the next section.


You will find the instructions for Xperia 10 II on our website that you can easily refer from (yet use your own built .zip bundle!):

Adaptation Status

Feel free to help out in areas that you like.

What works:

  • gps, bluetooth, wifi & internet sharing, mobile data, modem, camera, sensors, music/video playback
  • fingerprint works
  • USB networking

Known issues:

Contributing to Sony AOSP

If you want to help out with underlying issues in AOSP (fixing those will also fix them in SFOS, magic!:), follow this guide to build an AOSP 11 image:

Use this script to flash the AOSP images (the above website is pending an update for that step):

fastboot reboot fastboot
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash product_a product.img
fastboot flash recovery_a recovery.img
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.19_v9a_$FAMILY.img
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system_a vbmeta_system.img
fastboot flash vendor_a vendor.img
fastboot flash system_a system.img
fastboot flash system_ext_a system_ext.img
fastboot flash userdata userdata.img
fastboot erase metadata
fastboot --set-active=a
fastboot reboot


If you find bugs while building an image from this page, please report them in our IRC channel.

Have fun and enjoy the fully-flashable Sailfish OS image built by you! Your Jolla HW Team