Google Nexus 5X (lg-bullhead)
Users owning this device
In android go to→ → and tap the build number 7 times. Then go to → → and enable OEM unlocking
Reboot to the bootloader and run "fastboot oem unlock" Now selecton the phone screen with the volume button and use the power button to accept.
If your device says "SECURE BOOT: ENABLED (NO RPMB)" in the fastboot screen that means that the mainboard in your Nexus 5X is missing an image required by secureboot to function properly. If this is missing then oem-unlocking won't work on the device. It will re-lock every reboot.
No fix is available yet for this.
Special key combos
Boot to bootloader: hold volume down + power button until the screen turns on
Launch recovery: first boot to the bootloader, press the volume down button twice and press the power button to select
Mainline Kernel Status
|Y||Power Management||Uses Qualcomm's PM8994 controller, works since 4.11|
|Touch Screen||No driver in mainline tree.|
|DSI Panel||Out-of-tree driver generated using linux-mdss-dsi-panel-driver-generator. Untested|
|USB Gadget/OTG||No DT binding.|
|Y||SDHCI||The sd card is supported since 4.17.|
|Wi-Fi||Qualcomm QCA6174. Driver exists in mainline.|
|Y||GPIO keys||No DT bindings.|
|Bluetooth||Qualcomm QCA6174. Driver exists in mainline.|
|Sound||Qualcomm WCD9330, no driver in mainline.|
|Light Sensor||Rohm RPR0521. Driver exists in mainline.|
|Sixaxis||Bosch BMI160. Driver exists in mainline.|
|Camera||Sony IMX377. No driver in mainline.|
|GPU||Qualcomm Ardeno 418, needs DT bindings.|
|Modem||Qualcomm WTR3925. No driver in mainline.|
Here is the official Google page to download GPS, Audio, Camera, Gestures, Graphics, DRM, Video, Sensors firware blob. /developers.google
The Linux mainline kernel has very basic support for this phone since November 2016 (one cpu and uart). In January 2017 support for the onboard SDHCI was added and since March 2018 pstore-ramoops. Both should be included in 4.19.
To boot it using pmbootstrap follow the mainlining guide but note that it has a 64 Bit kernel. Also, compared to downstream "device-lg-bullhead" you need to change the debug tty to /dev/ttyMSM0 in the deviceinfo file.
Change deviceinfo (aports/device/device-lg-bullhead/deviceinfo)
deviceinfo_kernel_cmdline="console=ttyMSM0,115200,n8 androidboot.hardware=bullhead boot_cpus=0-5 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 buildvariant=userdebug PMOS_NO_OUTPUT_REDIRECT"
ttyMSM0 tells the kernel to write debug output to the debugger cable, PMOS_NO_OUTPUT_REDIRECT tells the initramfs script from pmOS to write there as well instead of to a (temporary) log file
Increase the pkgrel in the APKBUILD and rebuild the boot.img
$ pmbootstrap checksum device-lg-bullhead $ pmbootstrap export
Build your kernel as described in mainlining guide
Update the boot.img to include your local kernel
$ cp "/tmp/postmarketOS-export/boot.img-lg-bullhead" "$TEMP/boot.img" $ cd .output/arch/arm64/boot/ $ cat Image.gz dts/qcom/msm8992-bullhead-rev-101.dtb > "$TEMP/zImage-dtb" $ pmbootstrap chroot -- abootimg -u /tmp/mainline/boot.img -k /tmp/mainline/zImage-dtb $ pmbootstrap flasher list_devices
You can communicate with the device using
screen (or other software), so in a separate terminal start it:
$ screen /dev/ttyUSB0 115200
Boot your mobile to the bootloader (power + vol down) and you should see some debug output on the screen.
Boot the kernel using fastboot
$ pmbootstrap chroot -- fastboot boot /tmp/mainline/boot.img