We are pleased to announce our Android 14 1.2.0 Release for all our NXP i.MX-based Nitrogen Platforms!

For the impatient

You can download the prebuilt images from here:

Flashing using fastboot

The .zip archives include all the files to be flashed using fastboot. Note that fastboot will only flash to your eMMC device.

First you need to connect your Host PC to the target using micro-USB or TypeC USB cable depending on the platform.

Then you can enter fastboot mode from U-Boot prompt over the serial connection:

=> fastboot 0

Once the platform is in fastboot mode, you simply need to call the flashing script:

~/$ unzip u14*nitrogen8*.zip -d u14-nitrogen8
~/$ cd u14-nitrogen8
~/u14-nitrogen8$ ./device/boundary/scripts/flash_fastboot.sh

Since our i.MX platforms might come with different eMMC sizes, you can select the size you want to use at flashing time.

If you don’t provide that argument, the “default” size of 16GB will be flashed, otherwise you need to use the -s option:

~/u14-nitrogen8$ ./device/boundary/scripts/flash_fastboot.sh -s 8

Note that you can also use fastboot from a Windows Host PC, see following blog post to learn how:

Updating U-Boot

We recommend updating U-Boot once the image is flashed:

=> run upgradeu

What’s new?

Android 14 OS updates

Google provides a list of notable changes for developers:


Code based upon the android-14.0.0_r22 tag which includes all the security patches up until February 2024!

Notably, this release includes a new Ethernet menu that allows to set the IP from the Settings app: a14_settings_ethernet_menu


As usual, this release comes with SELinux enabled and enforced.

If you are using the userdebug build, you can switch to permissive mode by setting 1 variable in U-Boot:

=> setenv selinux permissive
=> saveenv


The image also supports Android Verified Boot 2.0!

So I can’t make any modification now? No, there’s a way to disable verity for userdebug builds:

$ adb root
$ adb disable-verity
$ adb reboot

At this point you will be able to modify every partition. However, it goes without saying that this disablement isn’t possible on user builds.

Non-A/B OTA updates

This release uses a non-A/B partitioning which allows to save some space and keep the most space for your applications.

In order to build an OTA package, you can simply enter this make command (once the env is setup properly):

$ make otapackage

Then, you can setup ota.conf to reflect your server settings if you plan on hosting your own updates.

Linux Kernel 6.1.x

This Android release is based on a 6.1.57 kernel from NXP.

Also, our number of patches has been drastically reduced in order to keep it closer to NXP release and make modification easier for customers.

Ezurio additions

Just like our previous releases, this one includes unique features that only Ezurio provides:

  • Dynamic display support
    • Our U-Boot version still detects the connected displays automatically
    • You can see our list of supported displays from our website here
  • Display rotation support
    • Possible via a simple env variable in U-Boot:
      => setenv hwrotation 270
      => saveenv
      => reset
  • USB Camera support with custom properties
    • USB cameras are declared as EXTERNAL in Android, we offer a way for them to appear as BACK/FRONT cameras:
      # setprop persist.vendor.cam.ext.facing 0
  • Extended camera sensors support
    • OV5640 support for all boards
    • Basler daA3840 raw camera support (8MP)
    • Sony imx219 raw camera support (8MP)
    • Custom camera layout settings for maximum flexibility:
      $ adb shell setprop persist.vendor.camera.config imx8mp-basler-ov5640
  • Unparalleled Wi-Fi / BT driver support
    • Backports modules integration, including latest security fixes
    • Sona IF573 Wi-Fi 6E + BT5.4 support
    • Serling LWB5+ Wi-Fi 5 + BT5.0 support
    • BD-SDMAC Wi-Fi 5 + BT5.0 support


Source code access

For the newcomers, please make sure to read our Android Getting Started Guide since it contains all the information you need to download, build and flash an Android image.

Since AOSP requirement is still to use old Ubuntu releases to build the OS, many might find it useful to use Docker.

For those we provide a dockerfile below:

Otherwise, for those already familiar with our releases, here is a condensed version to get the Android 14 source code:

~/$ mkdir myandroid
~/$ cd myandroid
~/myandroid$ repo init -u https://github.com/boundarydevices/android-manifest.git \
       -b boundary-android-14.0.0_1.2.0
~/myandroid$ repo sync
~/myandroid$ source build/envsetup.sh
~/myandroid$ lunch
... choose nitrogen8m / nitrogen8mm / nitrogen8mp / nitrogen8ulp from the list of boards 
~/myandroid$ ./imx-make.sh -j12

As you can see, we use a special make script instead of the regular make command.

The reason is that in order to have as few AOSP changes as possible, NXP created a separate script in order to build dependencies that are the kernel, dtbo, u-boot images.

One could also use the following approach to only build the dependencies with that script and then use standard Android build:

~/myandroid$ ./imx-make.sh kernel bootloader -j12
~/myandroid$ make -j12

As always, let us know your experiences (both good and bad) when you test out this image.