Google Nexus 6P
How to enter flash mode
- Connect a USB cable
- Make sure, the device is powered off
- Hold power + volume down
- Continue holding until you se the bootloader menu
$ git clone https://gitlab.com/postmarketOS/pmbootstrap.git
$ cd pmbootstrap
$ ./pmbootstrap.py init
$ ./pmbootstrap.py install --no-fde
$ ./pmbootstrap.py flasher flash_rootfs
$ ./pmbootstrap.py flasher flash_kernel
Kernel configs applied
Configs changed from stock Lineage kernel:
- Various NFS client configs: CONFIG_NFS_V4_1=y
- CONFIG_BCMDHD_FW_PATH, CONFIG_BCMDHD_NVRAM_PATH
How to enter flash mode
The Nexus 6P, like all Google Nexus devices, uses Fastboot as the flashing protocol.
To enter Fastboot mode, hold Volume Down while powering on the device. Let go of Volume Down when a picture of a green Android mascot shows up on the screen.
There is a project to port the mainline kernel to Nexus 6P: as a result there's now some support for Nexus 6P in mainline. However, currently there's only support for serial output and input, no screen or USB. Thus, this port doesn't use a mainline kernel. (The mainlining team's members can be found at ##linux-msm on Freenode.)
Android boots the modem by mounting the modem partition to /firmware, then opening /dev/subsys_modem. Doing the same on postmarketOS (after linking all the firmware in /firmware/images to /lib/firmware/postmarketos) causes any `dmesg` call to freeze (?!), and the device would kernel panic with a "modem crashed" error in a few seconds.
The audio requires the blobs from Android's /vendor/adsp.* to be present in /lib/firmware/postmarketos. Then, opening /dev/subsys_adsp will boot the sound card. Currently ALSA recognizes the sound card but fails with an error when playing audio: the Android audio configuration files would need to be converted to Linux format by xml2ucm. See https://arunraghavan.net/2016/01/audio-devices-and-configuration/ for an explanation of the difference between Android and Linux audio, and see https://github.com/kholk/sony-alsa-ucm/tree/master/kitakami for a different SD810 device's ALSA config.
It seems Bluetooth is connected via H4 UART at /dev/ttyHS0. Tizen uses the hciattach_bcm43xx tool from BlueZ to load firmware to the Bluetooth dongle, but I can't find this utility in Alpine's bluez or bluez-deprecated package. btattach -B /dev/ttyHS0 doesn't seem to work.