The BlackBerry Passport is, without a doubt, one of the most unique pieces of mobile hardware ever created. Released in 2014, its bizarre 1:1 aspect ratio, physical keyboard with touch-sensitive navigation, and industrial steel frame made it an instant icon for productivity enthusiasts.
But in 2024, the Passport faces an existential crisis: BlackBerry 10 OS is effectively dead. The infrastructure is crumbling, the browser is outdated, and the Android runtime (which once saved the app ecosystem) is an ancient relic stuck on Jellybean.
So, what do you do with perfect hardware that has a dead brain? You perform a transplant. You install Linux.
Here is the current state of putting Linux on the BlackBerry Passport. linux on blackberry passport
A common misconception is that BlackBerry 10 is "Linux-based." Technically, it uses a microkernel (QNX), which is Unix-like but not Linux. It shares no driver compatibility with Android or mainstream ARM Linux.
This means you cannot simply download a Raspberry Pi image and flash it to the Passport. The bootloader is locked down, the partition table is proprietary, and the drivers for the GPU (Adreno 330), Wi-Fi, and the keyboard matrix are custom.
To run Linux, you have three paths:
Let’s focus on the most exciting: Native Linux via postmarketOS.
Thanks to the herculean efforts of the postmarketOS community and developers like bovarysme (on GitHub), the BlackBerry Passport (device codename: blackberry-passport) has reached a "bootable" status.
As of late 2025/early 2026, the project has achieved: The Square Peg in a Round Hole: Running
wcnss firmware must be extracted from an old BlackBerry 10 dump).What does not work?
The BlackBerry Passport (released 2014) is a unique smartphone with a square 4.5" 1440×1440 display, a mechanical keyboard, and Qualcomm Snapdragon S4 Pro or MSM8974 (depending on region). Running Linux on a Passport is possible but limited: community projects have explored installing Linux distributions (mostly Android-derived or lightweight GNU/Linux) by replacing or augmenting the device’s Android-compatible runtime layers or via chroot/containers. This article summarizes feasibility, methods, benefits, and limitations.