https://wiki.pine64.org/api.php?action=feedcontributions&user=Dukla2000&feedformat=atomPINE64 - User contributions [en]2024-03-28T09:42:57ZUser contributionsMediaWiki 1.37.1https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20391PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-10T21:29:40Z<p>Dukla2000: /* Build sxmo partition */ tidy formatting</p>
<hr />
<div>= Rk2Aw BootLoader & Multi-Distro on SD Card for PinePhonePro =<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/''<br />
<br />
== Flash Rk2Aw BootLoader to SPI ==<br />
<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
== Flash Multi-Distro SD Card ==<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
<code>sudo sfdisk /dev/sdb/ <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF</code><br />
<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
Device Start End Sectors Size Type<br />
/dev/sdb1 64 32767 32704 16M unknown<br />
/dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
/dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
/dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo su</code> ''# login with your psw''<br />
## <code>dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441</code><br />
## <code>scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''<br />
## <code>mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
# ''Copy files for ManJaro''<br />
## <code>dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/</code><br />
## <code>scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''<br />
## <code>mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>mount /dev/sdb4 /media/xxx/rootfs1/</code><br />
## <code>scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''<br />
## <code>nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
= Rk2Aw BootLoader & Multi-Distro on eMMC for PinePhonePro =<br />
Make sure you boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below, arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
== Flash Rk2Aw BootLoader to SPI ==<br />
<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
== Build multi-distro eMMC ==<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
=== Mount the images ===<br />
<code>cd ~/Downloads</code> ''# enter to directory''<br />
<code>sudo su</code> ''# login with your psw''<br />
<code>losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img </code><br />
<code>losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img </code><br />
<code>ls -l /mnt/</code><br />
<br />
total 0<br />
<code>mkdir /mnt/phosh </code><br />
<code>mkdir /mnt/sxmo </code><br />
<code>mkdir /mnt/phosh/boot </code><br />
<code>mkdir /mnt/phosh/root </code><br />
<code>mkdir /mnt/sxmo/boot </code><br />
<code>mkdir /mnt/sxmo/root </code><br />
<code>mkdir /mnt/ephosh </code> # e for the partition on the eMMC<br />
<code>mkdir /mnt/esxmo </code> # e for the partition on the eMMC<br />
<code>mount /dev/loop0p1 /mnt/phosh/boot/ </code><br />
<code>mount /dev/loop0p2 /mnt/phosh/root/ </code><br />
<code>mount /dev/loop1p1 /mnt/sxmo/boot/ </code><br />
<code>mount /dev/loop1p2 /mnt/sxmo/root/ </code><br />
<code>lsblk </code><br />
<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
=== Prepare eMMC ===<br />
<code>dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress</code> # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
<br />
<code>sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF</code><br />
<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
<br />
<code>lsblk</code><br />
<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
=== Build phosh partition ===<br />
<br />
<code>dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync </code><br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
<br />
<code>mount /dev/mmcblk2p1 /mnt/ephosh/</code><br />
<code>scp -r /mnt/phosh/boot/* /mnt/ephosh/boot</code><br />
<code>mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG</code><br />
<code>nano /mnt/ephosh/etc/fstab</code> # set PARTLABEL for / and comment /boot<br />
<code>cat /mnt/ephosh/etc/fstab</code> <br />
<br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=PHOSH / ext4 rw,relatime 0 1<br />
# UUID=52CA-6165 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
<br />
<code>mkdir /mnt/ephosh/boot/extlinux</code><br />
<code>nano /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
<code>cat /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL phosh<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Build sxmo partition ===<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
<br />
mount /dev/mmcblk2p2 /mnt/esxmo/ <br />
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
cat /mnt/esxmo/etc/fstab<br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
<br />
mkdir /mnt/esxmo/boot/extlinux<br />
nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
cat /mnt/esxmo/boot/extlinux/extlinux.conf<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.<br />
# The end result is a boot screen as follows:<br />
[[File:P1090461.JPG|200px|thumb|left|Options to boot phosh or sxmo]]</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20349PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-10T00:37:12Z<p>Dukla2000: /* Build multi-distro SD Card */ add lines to mount each partition after dd and comment out /boot in fstab</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441</code><br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/</code><br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>mount /dev/sdb4 /media/xxx/rootfs1/</code><br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure you boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below, arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the partition on the eMMC<br />
[root@PPP Downloads]# mkdir /mnt/esxmo # e for the partition on the eMMC<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/ephosh/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=PHOSH / ext4 rw,relatime 0 1<br />
# UUID=52CA-6165 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/ephosh/boot/extlinux/extlinux.conf<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL phosh<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.<br />
# The end result is a boot screen as follows:<br />
[[File:P1090461.JPG|200px|thumb|left|Options to boot phosh or sxmo]]</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20348PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-10T00:20:25Z<p>Dukla2000: /* Follow-up comments */ add photo</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure you boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below, arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the partition on the eMMC<br />
[root@PPP Downloads]# mkdir /mnt/esxmo # e for the partition on the eMMC<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/ephosh/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=PHOSH / ext4 rw,relatime 0 1<br />
# UUID=52CA-6165 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/ephosh/boot/extlinux/extlinux.conf<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL phosh<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.<br />
# The end result is a boot screen as follows:<br />
[[File:P1090461.JPG|200px|thumb|left|Options to boot phosh or sxmo]]</div>Dukla2000https://wiki.pine64.org/index.php?title=File:P1090461.JPG&diff=20347File:P1090461.JPG2023-08-10T00:16:22Z<p>Dukla2000: Megi U-boot on PPP showing multi-boot options</p>
<hr />
<div>== Summary ==<br />
Megi U-boot on PPP showing multi-boot options<br />
== Licensing ==<br />
{{PD|PD}}</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20346PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:31:17Z<p>Dukla2000: /* Build phosh partition */</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure you boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below, arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the partition on the eMMC<br />
[root@PPP Downloads]# mkdir /mnt/esxmo # e for the partition on the eMMC<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/ephosh/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=PHOSH / ext4 rw,relatime 0 1<br />
# UUID=52CA-6165 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/ephosh/boot/extlinux/extlinux.conf<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL phosh<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20345PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:30:41Z<p>Dukla2000: /* Mount the images */ create all the /mnt subdirectories here</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure you boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below, arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the partition on the eMMC<br />
[root@PPP Downloads]# mkdir /mnt/esxmo # e for the partition on the eMMC<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/ephosh/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=PHOSH / ext4 rw,relatime 0 1<br />
# UUID=52CA-6165 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/ephosh/boot/extlinux/extlinux.conf<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL phosh<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20344PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:27:52Z<p>Dukla2000: /* Flash rk2aw BootLoader to SPI & multi-distro eMMC */ typo</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure you boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below, arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/ephosh/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=PHOSH / ext4 rw,relatime 0 1<br />
# UUID=52CA-6165 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/ephosh/boot/extlinux/extlinux.conf<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL phosh<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20343PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:22:20Z<p>Dukla2000: /* Build phosh partition */ formatting, add resulting files fstab & extlinux.conf</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure your boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/ephosh/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=PHOSH / ext4 rw,relatime 0 1<br />
# UUID=52CA-6165 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/ephosh/boot/extlinux/extlinux.conf<br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL phosh<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20342PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:15:28Z<p>Dukla2000: /* Build sxmo partition */ tidy formatting</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure your boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<code><br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and remove /boot<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20341PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:13:46Z<p>Dukla2000: /* Prepare eMMC */ tidy formatting</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure your boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
[root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Build phosh partition ==== <br />
<code><br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and remove /boot<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<code><br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input</code><br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20340PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:12:18Z<p>Dukla2000: /* Mount the images */ tidy formatting</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure your boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
[me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
<br />
==== Prepare eMMC ====<br />
<code> [root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]</code><br />
==== Build phosh partition ==== <br />
<code><br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and remove /boot<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<code><br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input</code><br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20339PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T23:09:47Z<p>Dukla2000: /* Download and Run rk2aw SPI Flasher */ Add query showing results</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure your boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:<br />
<nowiki>#</nowiki> ./rk2aw-spi-flasher <br />
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)<br />
SPI NOR Flash:<br />
- Total size: 16384 KiB<br />
- Erase block size: 4 KiB<br />
- Write size: 1<br />
- Manufacturer: gigadevice<br />
- Part name: gd25lq128e<br />
- JEDEC ID: 257018<br />
Bootable images currently present in SPI NOR flash:<br />
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content<br />
-------------------------------------------------------------------------------<br />
0 0 2048 6144 0 0 (padded) 0='rk2aw'<br />
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'<br />
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'<br />
Auto-calculated layout for rk2aw dual bootloader scheme:<br />
Area Offset Size <br />
---------------------------------------------------<br />
rk2aw primary 0 65536 <br />
rk2aw backup 65536 65536 <br />
spl fallback 131072 393216 <br />
spl primary 524288 389120 <br />
itb fallback 913408 2097152 <br />
itb primary 3010560 2097152<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
<code> [me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]</code><br />
==== Prepare eMMC ====<br />
<code> [root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]</code><br />
==== Build phosh partition ==== <br />
<code><br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and remove /boot<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<code><br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input</code><br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20338PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T22:57:36Z<p>Dukla2000: /* Download and Run rk2aw SPI Flasher */ clarify installs bootloader to SPI</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure your boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash.<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
<code> [me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]</code><br />
==== Prepare eMMC ====<br />
<code> [root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]</code><br />
==== Build phosh partition ==== <br />
<code><br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and remove /boot<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<code><br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input</code><br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Pro/Create_a_multi-distribution_image_using_rk2aw&diff=20337PinePhone Pro/Create a multi-distribution image using rk2aw2023-08-09T22:49:33Z<p>Dukla2000: Add example to setup eMMC with multi-distro, consistently use rk2aw as per megi & multi-distro</p>
<hr />
<div>= How to flash rk2aw and setup multi-distro disks on PinePhonePro =<br />
== Flash rk2aw BootLoader to SPI & multi-distro SDcard ==<br />
<br />
''References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL and https://xnux.eu/rk2aw/''<br />
<br />
''Requirements: SSH connection from linux machine to PinePhonePro, internet connection.''<br />
<br />
''Note: Preloader and userspace utility to flash it are non-free.''<br />
<br />
''Thanks: Megi at https://xnux.eu/log/ ''<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
# ''Connect PinePhonePro to linux machine and start a ssh connection''<br />
# <code>ssh <user>@<phoneip></code> ''# set a connection''<br />
# <code>cd ~/Downloads</code> ''# enter to directory''<br />
# <code>curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz</code> ''# download installer''<br />
# <code>tar -xvzf ppp.tar.gz -C ~/Downloads</code> ''# extract''<br />
# <code># scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads</code> ''# copy to phone, non needed''<br />
# <code>sudo ./spinor-flash-initial-setup.sh</code> ''# flash SPI''<br />
<br />
=== Build multi-distro SD Card ===<br />
<br />
# ''Get distro compressed images and decompress them. (i.e. Manjaro.phosh.beta34, Mobian.6.1, ArchLinux)'' <br />
# ''Mount distro images both partitions "/boot", "/root" for each distro''<br />
# <code>lsblk</code> ''# find /loop, /sd references. Use <code>blkid</code> to see the UUID for the partition''<br />
#: ├─loop0p1 /media/xxx/BOOT_MNJRO<br />
#: └─loop0p2 /media/xxx/ROOT_MNJRO<br />
#: ├─loop1p1 /media/xxx/boot<br />
#: └─loop1p2 /media/xxx/rootfs<br />
#: ├─loop2p1 /media/xxx/52CA-6165 <br />
#: └─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<br />
#: └─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''<br />
# <code>sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress</code> ''# quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''<br />
# or <code>sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress</code> ''# slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta) )''<br />
# ''Partition sd card (min <del>64</del>32GB)''<br />
sudo sfdisk /dev/sdb <<EOF<br />
label: gpt<br />
first-lba: 64<br />
table-length: 8<br />
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition<br />
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"<br />
EOF<br />
# <code>lsblk</code> ''# list partitions on sd and mounted distro images''<br />
##: Device Start End Sectors Size Type<br />
##: /dev/sdb1 64 32767 32704 16M unknown<br />
##: /dev/sdb2 32768 16809983 16777216 8G Linux filesystem<br />
##: /dev/sdb3 16809984 33587199 16777216 8G Linux filesystem<br />
##: /dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem<br />
# ''Copy files for Arch Linux ARM''<br />
## <code>sudo dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part2''<br />
## <code>sudo scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot</code> ''# copy bootfs to to part2/boot''<br />
## <code>sudo mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/etc/fstab</code> ''# add PARTLABEL=ALARM and delete UUID=xxx from second line''<br />
## <code>sudo mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/extlinux/extlinux.conf</code> ''# add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ALarm<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for ManJaro''<br />
## <code>sudo dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part3''<br />
## <code>sudo scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot</code> ''# copy bootfs to to part3/boot''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/etc/fstab</code> ''# change UUID=xxx to PARTLABEL=MANJARO''<br />
## <code>sudo mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG</code> ''# hide auto-menu item''<br />
## <code>sudo mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux</code> ''# add directory''<br />
## <code>sudo nano /media/xxx/ROOT_MNJRO1/boot/extlinux/extlinux.conf</code> ''#add file''<br />
<nowiki>#</nowiki>/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL ManJaro<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
# ''Copy files for MObian''<br />
## <code>sudo dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync</code> ''# copy rootfs to sd part4''<br />
## <code>sudo scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot</code> ''# copy bootfs to to part4/boot''<br />
## <code>sudo nano /media/xxx/rootfs1/etc/fstab</code> ''# replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line.''<br />
## <code>sudo nano /media/xxx/rootfs1/boot/extlinux/extlinux.conf</code> ''# edit path from /bootfs to /part4/boot''<br />
>linux '''/boot'''/vmlinuz-6.1-rockchip<br />
>initrd '''/boot'''/initrd.img-6.1-rockchip<br />
>fdtdir '''/boot'''/dtb-6.1-rockchip/<br />
APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input<br />
<br />
== Flash rk2aw BootLoader to SPI & multi-distro eMMC ==<br />
Make sure your boot from the SDcard in your PPP as we are going to be building the eMMC. Note that below arch is booted from the SDcard and the SDcard shows as /dev/mmcblk1<br />
<br />
=== Download and Run rk2aw SPI Flasher ===<br />
Same as above<br />
<br />
=== Build multi-distro eMMC ===<br />
In this example we are going to build 2 partitions on the eMMC, the first with Arch/phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.<br />
<br />
==== Mount the images ==== <br />
<code> [me@PPP Downloads]$ sudo su<br />
[sudo] password for me: <br />
[root@PPP Downloads]# losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img <br />
[root@PPP Downloads]# losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img <br />
[root@PPP Downloads]# ls -l /mnt/<br />
total 0<br />
[root@PPP Downloads]# mkdir /mnt/phosh<br />
[root@PPP Downloads]# mkdir /mnt/sxmo<br />
[root@PPP Downloads]# mkdir /mnt/phosh/boot<br />
[root@PPP Downloads]# mkdir /mnt/phosh/root<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/boot<br />
[root@PPP Downloads]# mkdir /mnt/sxmo/root<br />
[root@PPP Downloads]# mount /dev/loop0p1 /mnt/phosh/boot/<br />
[root@PPP Downloads]# mount /dev/loop0p2 /mnt/phosh/root/<br />
[root@PPP Downloads]# mount /dev/loop1p1 /mnt/sxmo/boot/<br />
[root@PPP Downloads]# mount /dev/loop1p2 /mnt/sxmo/root/<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 122M 0 part <br />
└─mmcblk2p2 179:2 0 115.1G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]</code><br />
==== Prepare eMMC ====<br />
<code> [root@PPP Downloads]# dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress # overwrite the front to clear any bootloaders<br />
985759744 bytes (986 MB, 940 MiB) copied, 3 s, 329 MB/s<br />
32768+0 records in<br />
32768+0 records out<br />
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 8.14441 s, 132 MB/s<br />
[root@PPP Downloads]# sfdisk /dev/mmcblk2 << EOF<br />
> label: gpt<br />
> first-lba: 64<br />
> table-length: 8<br />
> size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"<br />
> EOF<br />
Checking that no-one is using this disk right now ... OK<br />
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors<br />
Units: sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Script header accepted.<br />
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).<br />
The maximal number of partitions is 8 (default is 128).<br />
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.<br />
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.<br />
/dev/mmcblk2p3: Done.<br />
New situation:<br />
Disklabel type: gpt<br />
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461<br />
Device Start End Sectors Size Type<br />
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem<br />
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem<br />
The partition table has been altered.<br />
Calling ioctl() to re-read partition table.<br />
Syncing disks.<br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot<br />
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root<br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]</code><br />
==== Build phosh partition ==== <br />
<code><br />
[root@PPP Downloads]# dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync<br />
5225054208 bytes (5.2 GB, 4.9 GiB) copied, 215 s, 24.3 MB/s5238685696 bytes (5.2 GB, 4.9 GiB) copied, 215.606 s, 24.3 MB/s<br />
4996+0 records in<br />
4996+0 records out<br />
5238685696 bytes (5.2 GB, 4.9 GiB) copied, 218.565 s, 24.0 MB/s<br />
[root@PPP Downloads]# mkdir /mnt/ephosh # e for the eMMC!<br />
[root@PPP Downloads]# mount /dev/mmcblk2p1 /mnt/ephosh/<br />
[root@PPP Downloads]# scp -r /mnt/phosh/boot/* /mnt/ephosh/boot<br />
[root@PPP Downloads]# mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/ephosh/etc/fstab # set PARTLABEL for / and remove /boot<br />
[root@PPP Downloads]# mkdir /mnt/ephosh/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/ephosh/boot/extlinux/extlinux.conf</code><br />
==== Build sxmo partition ====<br />
<br />
We have unmounted all the phosh devices, so <br />
<code><br />
[root@PPP Downloads]# lsblk<br />
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS<br />
loop0 7:0 0 5G 0 loop <br />
├─loop0p1 259:0 0 122M 0 part <br />
└─loop0p2 259:1 0 4.9G 0 part <br />
loop1 7:1 0 3.5G 0 loop <br />
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot<br />
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root<br />
mmcblk2 179:0 0 115.2G 0 disk <br />
├─mmcblk2p1 179:1 0 32G 0 part <br />
└─mmcblk2p2 179:2 0 83.2G 0 part <br />
mmcblk2boot0 179:32 0 4M 1 disk <br />
mmcblk2boot1 179:64 0 4M 1 disk <br />
mmcblk1 179:96 0 59.6G 0 disk <br />
├─mmcblk1p1 179:97 0 122M 0 part /boot<br />
└─mmcblk1p2 179:98 0 59.5G 0 part /<br />
zram0 254:0 0 1.5G 0 disk [SWAP]<br />
[root@PPP Downloads]# dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync<br />
3613392896 bytes (3.6 GB, 3.4 GiB) copied, 153 s, 23.6 MB/s3628072960 bytes (3.6 GB, 3.4 GiB) copied, 153.543 s, 23.6 MB/s<br />
3460+0 records in<br />
3460+0 records out<br />
3628072960 bytes (3.6 GB, 3.4 GiB) copied, 156.292 s, 23.2 MB/s<br />
[root@PPP Downloads]# mount /dev/mmcblk2p2 /mnt/esxmo/<br />
[root@PPP Downloads]# scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot<br />
[root@PPP Downloads]# mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG<br />
[root@PPP Downloads]# nano /mnt/esxmo/etc/fstab # set PARTLABEL for / and comment /boot<br />
[root@PPP Downloads]# cat /mnt/esxmo/etc/fstab <br />
# Static information about the filesystems.<br />
# See fstab(5) for details.<br />
# <file system> <dir> <type> <options> <dump> <pass><br />
PARTLABEL=SXMO / ext4 rw,relatime 0 1<br />
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2<br />
[root@PPP Downloads]# mkdir /mnt/esxmo/boot/extlinux<br />
[root@PPP Downloads]# nano /mnt/esxmo/boot/extlinux/extlinux.conf<br />
[root@PPP Downloads]# cat /mnt/esxmo/boot/extlinux/extlinux.conf <br />
#/boot/extlinux/extlinux.conf<br />
MENU TITLE Pinephone Pro Boot Menu<br />
LABEL l0<br />
MENU LABEL sxmo<br />
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb<br />
KERNEL /boot/Image<br />
INITRD /boot/initramfs-linux.img<br />
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait fbcon=rotate:0 pinephone_keyboard.disable_input</code><br />
<br />
=== Follow-up comments ===<br />
<br />
# On first boot neither phosh nor sxmo resized their partition - sudo resize2fs sorted that.<br />
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5863ROCKPro64 Software Releases2020-06-05T23:24:55Z<p>Dukla2000: /* Official Debian */ update</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases - Ubuntu and Debian==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header (or expanding the "assets" section under the Changelog) will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by Mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Mrfixit has engineered 2 releases based on Debian.<br />
<br />
=== Feature complete desktop release ===<br />
<br />
See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
=== Minimal Debian ===<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== Official Debian ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
As of April 2020 Debian have a ROCKPro64 image available. See forum thread [https://forum.pine64.org/showthread.php?tid=9744 here.]<br />
<br />
Instructions for creating a bootable image are in the README file on the Debian website, as at June 2020 these were in short<br />
* Download firmware.rockpro64-rk3399.img.gz<br />
* Download partition.img.gz<br />
* zcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img<br />
* dd if=complete_image.img of=your_chosen_boot_device bs=4M<br />
<br />
What you now have is the official Debian installer that will boot and run on your ROCKPro64. You will need an Ethernet connection and to answer the various installer questions/options.<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
<br />
Manjaro ARM now provide XFCE and KDE Plasma images for the ROCKPro64. Download locations for the 20.04 release [https://forum.manjaro.org/t/manjaro-arm-20-04-released/133374 are in this Manjaro forum thread.]<br />
<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5862ROCKPro64 Software Releases2020-06-05T22:30:33Z<p>Dukla2000: /* Debian by Mrfixit2001 */ add official Debian</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases - Ubuntu and Debian==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header (or expanding the "assets" section under the Changelog) will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by Mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Mrfixit has engineered 2 releases based on Debian.<br />
<br />
=== Feature complete desktop release ===<br />
<br />
See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
=== Minimal Debian ===<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== Official Debian ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
As of April 2020 Debian have a ROCKPro64 image available. See forum thread [https://forum.pine64.org/showthread.php?tid=9744 here.]<br />
<br />
Instructions for creating a bootable image are in the README file on the Debian website, as at June 2020 these were in short<br />
* Download firmware.rockpro64-rk3399.img.gz<br />
* Download partition.img.gz<br />
* zcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img<br />
* dd if=complete_image.img of=your_chosen_boot_device bs=4M<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
<br />
Manjaro ARM now provide XFCE and KDE Plasma images for the ROCKPro64. Download locations for the 20.04 release [https://forum.manjaro.org/t/manjaro-arm-20-04-released/133374 are in this Manjaro forum thread.]<br />
<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5856ROCKPro64 Software Releases2020-06-05T08:21:42Z<p>Dukla2000: /* Ayufan releases - Ubuntu and Debian */ expand where to find downloads</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases - Ubuntu and Debian==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header (or expanding the "assets" section under the Changelog) will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by Mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Mrfixit has engineered 2 releases based on Debian.<br />
<br />
=== Feature complete desktop release ===<br />
<br />
See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
=== Minimal Debian ===<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
<br />
Manjaro ARM now provide XFCE and KDE Plasma images for the ROCKPro64. Download locations for the 20.04 release [https://forum.manjaro.org/t/manjaro-arm-20-04-released/133374 are in this Manjaro forum thread.]<br />
<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5845ROCKPro64 Software Releases2020-06-04T19:52:14Z<p>Dukla2000: /* Debian by Mrfixit2001 */ tidy/consistency</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases - Ubuntu and Debian==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by Mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Mrfixit has engineered 2 releases based on Debian.<br />
<br />
=== Feature complete desktop release ===<br />
<br />
See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
=== Minimal Debian ===<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
<br />
Manjaro ARM now provide XFCE and KDE Plasma images for the ROCKPro64. Download locations for the 20.04 release [https://forum.manjaro.org/t/manjaro-arm-20-04-released/133374 are in this Manjaro forum thread.]<br />
<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5844ROCKPro64 Software Releases2020-06-04T19:49:44Z<p>Dukla2000: /* Ayufan releases */ update heading</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases - Ubuntu and Debian==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by Mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Mrfixit has engineered 2 releases based on Debian.<br />
<br />
=== Feature complete desktop release ===<br />
<br />
See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
=== Minimal Debian ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
<br />
Manjaro ARM now provide XFCE and KDE Plasma images for the ROCKPro64. Download locations for the 20.04 release [https://forum.manjaro.org/t/manjaro-arm-20-04-released/133374 are in this Manjaro forum thread.]<br />
<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5843ROCKPro64 Software Releases2020-06-04T19:48:25Z<p>Dukla2000: /* Manjaro ARM */ update</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by Mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Mrfixit has engineered 2 releases based on Debian.<br />
<br />
=== Feature complete desktop release ===<br />
<br />
See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
=== Minimal Debian ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
<br />
Manjaro ARM now provide XFCE and KDE Plasma images for the ROCKPro64. Download locations for the 20.04 release [https://forum.manjaro.org/t/manjaro-arm-20-04-released/133374 are in this Manjaro forum thread.]<br />
<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5842ROCKPro64 Software Releases2020-06-04T19:42:05Z<p>Dukla2000: /* Debian by mrfixit2001 */ tidy, add Feature Complete version</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by Mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Mrfixit has engineered 2 releases based on Debian.<br />
<br />
=== Feature complete desktop release ===<br />
<br />
See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
=== Minimal Debian ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
=== Manjaro KDE Plasma Release [20.02.1] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde-plasma/20.02.1/ Download links and signatures]<br />
*** size: 1015.84 MB<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] [preview1] ===<br />
* [http://pumath.dl.osdn.jp/storage/g/m/ma/manjaro-arm/rockpro64/kde/preview1/Manjaro-ARM-kde-rockpro64-preview1.img.xz Direct download from Manjaro]<br />
*** size: 992MB<br />
*** MD5 (Zip file): c77edb0ad49cefcf16afc88548ffa177<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde/19.06/Manjaro-ARM-kde-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 991MB<br />
*** MD5 (Zip file): fe009307c2cb37748ac85952decc261f<br />
<br />
=== Manjaro LXQT ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/lxqt/19.06/Manjaro-ARM-lxqt-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 762MB<br />
*** MD5 (Zip file): 58bce45e4a05e26636193d5abee283b7<br />
<br />
=== Manjaro ARM Minimal Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/minimal/19.06/Manjaro-ARM-minimal-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 337MB<br />
*** MD5 (Zip file): 87576a1a25ad542f2b4bfeb33069ce38<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5841ROCKPro64 Software Releases2020-06-04T19:32:30Z<p>Dukla2000: /* Debian Stretch */ removed - now covered in Ayfan section</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
=== Minimal Debian [microSD / eMMC Boot] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
=== Manjaro KDE Plasma Release [20.02.1] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde-plasma/20.02.1/ Download links and signatures]<br />
*** size: 1015.84 MB<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] [preview1] ===<br />
* [http://pumath.dl.osdn.jp/storage/g/m/ma/manjaro-arm/rockpro64/kde/preview1/Manjaro-ARM-kde-rockpro64-preview1.img.xz Direct download from Manjaro]<br />
*** size: 992MB<br />
*** MD5 (Zip file): c77edb0ad49cefcf16afc88548ffa177<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde/19.06/Manjaro-ARM-kde-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 991MB<br />
*** MD5 (Zip file): fe009307c2cb37748ac85952decc261f<br />
<br />
=== Manjaro LXQT ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/lxqt/19.06/Manjaro-ARM-lxqt-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 762MB<br />
*** MD5 (Zip file): 58bce45e4a05e26636193d5abee283b7<br />
<br />
=== Manjaro ARM Minimal Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/minimal/19.06/Manjaro-ARM-minimal-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 337MB<br />
*** MD5 (Zip file): 87576a1a25ad542f2b4bfeb33069ce38<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5840ROCKPro64 Software Releases2020-06-04T19:31:38Z<p>Dukla2000: /* Ubuntu 18.04 Bionic */ Update/re-write</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ayufan releases ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]<br />
<br />
Clicking through on any chosen release header will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.<br />
<br />
== Debian by mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
=== Minimal Debian [microSD / eMMC Boot] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== Debian Stretch ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Minimal 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-minimal-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 223MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
=== Manjaro KDE Plasma Release [20.02.1] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde-plasma/20.02.1/ Download links and signatures]<br />
*** size: 1015.84 MB<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] [preview1] ===<br />
* [http://pumath.dl.osdn.jp/storage/g/m/ma/manjaro-arm/rockpro64/kde/preview1/Manjaro-ARM-kde-rockpro64-preview1.img.xz Direct download from Manjaro]<br />
*** size: 992MB<br />
*** MD5 (Zip file): c77edb0ad49cefcf16afc88548ffa177<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde/19.06/Manjaro-ARM-kde-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 991MB<br />
*** MD5 (Zip file): fe009307c2cb37748ac85952decc261f<br />
<br />
=== Manjaro LXQT ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/lxqt/19.06/Manjaro-ARM-lxqt-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 762MB<br />
*** MD5 (Zip file): 58bce45e4a05e26636193d5abee283b7<br />
<br />
=== Manjaro ARM Minimal Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/minimal/19.06/Manjaro-ARM-minimal-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 337MB<br />
*** MD5 (Zip file): 87576a1a25ad542f2b4bfeb33069ce38<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5839ROCKPro64 Software Releases2020-06-04T19:16:10Z<p>Dukla2000: /* Armbian */ Update - remove obsolete links, consolidate as Armbian page has all required details</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ubuntu 18.04 Bionic ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== LXDE Desktop 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** size: 689MB<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-lxde-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Mate Desktop 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** size: 1.03GB<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-mate-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Minimal 64bit (arm64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-minimal-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 296MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Minimal 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-minimal-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 307MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Containers 64bit (arm64) (DockerCE & Kubernetes) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-containers-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 389MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
== Debian by mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
=== Minimal Debian [microSD / eMMC Boot] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== Debian Stretch ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Minimal 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-minimal-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 223MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
=== Manjaro KDE Plasma Release [20.02.1] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde-plasma/20.02.1/ Download links and signatures]<br />
*** size: 1015.84 MB<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] [preview1] ===<br />
* [http://pumath.dl.osdn.jp/storage/g/m/ma/manjaro-arm/rockpro64/kde/preview1/Manjaro-ARM-kde-rockpro64-preview1.img.xz Direct download from Manjaro]<br />
*** size: 992MB<br />
*** MD5 (Zip file): c77edb0ad49cefcf16afc88548ffa177<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde/19.06/Manjaro-ARM-kde-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 991MB<br />
*** MD5 (Zip file): fe009307c2cb37748ac85952decc261f<br />
<br />
=== Manjaro LXQT ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/lxqt/19.06/Manjaro-ARM-lxqt-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 762MB<br />
*** MD5 (Zip file): 58bce45e4a05e26636193d5abee283b7<br />
<br />
=== Manjaro ARM Minimal Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/minimal/19.06/Manjaro-ARM-minimal-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 337MB<br />
*** MD5 (Zip file): 87576a1a25ad542f2b4bfeb33069ce38<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=ROCKPro64_Software_Releases&diff=5838ROCKPro64 Software Releases2020-06-04T19:11:25Z<p>Dukla2000: /* Linux Images */</p>
<hr />
<div>= Linux Images =<br />
<br />
<br />
== Armbian==<br />
http://files.pine64.org/sw/pine64_installer/json/armbian.png<br />
<br />
=== Armbian Debian Buster Desktop [microSD / eMMC Boot] [5.91] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dl.armbian.com/rockpro64/archive/Armbian_5.91_Rockpro64_Debian_buster_default_4.4.184_desktop.7z Direct download from Armbian]<br />
*** File Size: 557MB<br />
*** MD5 (XZ file): b1650050a32104f87f6504ede94b26f4<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
=== Armbian Debian Stretch Desktop [microSD / eMMC Boot] [5.90] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dl.armbian.com/rockpro64/archive/Armbian_5.90_Rockpro64_Debian_stretch_default_4.4.182_desktop.7z Direct download from Armbian]<br />
*** File Size: 535MB<br />
*** MD5 (XZ file): ac8c807cda0a73de7014cd014e936136<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
=== Armbian Ubuntu 18.04 Bionic Desktop [microSD / eMMC Boot] [5.90]===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dl.armbian.com/rockpro64/archive/Armbian_5.90_Rockpro64_Ubuntu_bionic_default_4.4.182_desktop.7z Direct download from Armbian]<br />
*** File Size: 420MB<br />
*** MD5 (XZ file):8d46f3f57b3f70fc16ac2589ff2d2add<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
=== Armbian Debian Buster Minimal [microSD / eMMC Boot] [5.91] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dl.armbian.com/rockpro64/archive/Armbian_5.91_Rockpro64_Debian_buster_default_4.4.184.7z Direct download from Armbian]<br />
*** File Size: 301MB<br />
*** MD5 (XZ file): 7b01c2141858b931ff722b5a4b6df761<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
=== Armbian Debian Stretch Minimal [microSD / eMMC Boot] [5.90] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dl.armbian.com/rockpro64/archive/Armbian_5.90_Rockpro64_Debian_stretch_default_4.4.182.7z Direct download from Armbian]<br />
*** File Size: 269MB<br />
*** MD5 (XZ file): 8cdb69b29ec13d8940eef26cf1cd0eec<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
=== Armbian Ubuntu 18.04 Bionic Minimal [microSD / eMMC Boot] [5.90]===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dl.armbian.com/rockpro64/archive/Armbian_5.90_Rockpro64_Ubuntu_bionic_default_4.4.182.7z Direct download from Armbian]<br />
*** File Size: 199MB<br />
*** MD5 (XZ file):29366d5f40c7ef0dd46f2ef0bc89b702<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]<br />
<br />
== Ubuntu 18.04 Bionic ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/penguin.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== LXDE Desktop 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** size: 689MB<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-lxde-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Mate Desktop 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** size: 1.03GB<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-mate-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Minimal 64bit (arm64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-minimal-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 296MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Minimal 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-minimal-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 307MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
=== Containers 64bit (arm64) (DockerCE & Kubernetes) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-containers-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 389MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
== Debian by mrfixit2001 ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]<br />
<br />
=== Minimal Debian [microSD / eMMC Boot] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]<br />
* Login with<br />
** username: rock<br />
** password: rock<br />
<br />
== Debian Stretch ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/debian.png<br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Minimal 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-minimal-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 223MB<br />
* Login with<br />
** username: rock64<br />
** password: rock64<br />
<br />
== DietPi ==<br />
http://files.pine64.org/sw/pine64_installer/json/dietpi.png<br />
<br />
=== DietPi Community Build Image [microSD / eMMC boot] ===<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]<br />
<br />
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]<br />
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4<br />
** size: 59.4MB<br />
* Login with<br />
** username: root<br />
** password: dietpi<br />
<br />
== Arch ==<br />
<br />
Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]<br />
<br />
== OpenMediaVault ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/omv.png<br />
<br />
OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.] <br />
<br />
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]<br />
<br />
=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]<br />
** size: 392MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]<br />
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]<br />
** size: 340MB<br />
* WebGUI Login:<br />
** username: admin<br />
** password: openmediavault<br />
* SSH/ Console Login:<br />
** username: root<br />
** password: openmediavault <br />
*** '''NB! You need to enable root login in OMV WebGUI'''<br />
* [[OpenMediaVault|OpenMediaVault Basic Setup]]<br />
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]<br />
<br />
== LibreELEC(KODI) ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/libreelec.png<br />
<br />
=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===<br />
<br />
* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]<br />
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532<br />
*** File Size: 135MB<br />
<br />
<br />
== Slackware==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/slackware.png<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (http://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)<br />
<br />
=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584<br />
*** File Size: 271MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]<br />
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668<br />
*** File Size: 779MB<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===<br />
* System without a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c<br />
*** File Size: 256MB<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737<br />
*** File Size: 729MB<br />
<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
* To run the OS on eMMC<br />
**Flash the image to micro SD, power up the board with micro SD and login<br />
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''<br />
**After finish copy the file, power off the board and add eMMC module to the board<br />
**Bootup the board, run below command for flashing to eMMC module<br />
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M<br />
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''<br />
***then edit 2 files in eMMC module:<br />
***>> mount /dev/mmcblk1p1 /media<br />
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt<br />
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab<br />
**After done, power off board and remove micro SD. Then bootup with only eMMC module.<br />
<br />
== Nems Linux==<br />
http://files.pine64.org/sw/pine64_installer/json/nems.jpg<br />
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.<br />
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]<br />
* Login with<br />
** Username: nemsadmin<br />
** Password: nemsadmin<br />
<br />
=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===<br />
* DD image (for 16GB micoSD card and above)<br />
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]<br />
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]<br />
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]<br />
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5<br />
*** File Size: 1.32GB<br />
<br />
== NextCloudPi==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png<br />
<br />
=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===<br />
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.<br />
* Visit the project's [http://nextcloudpi.com website]<br />
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]<br />
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7<br />
*** File Size: 312MB<br />
* Login with<br />
** username: root<br />
** password: 1234<br />
<br />
== Cent OS ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/centos.jpg<br />
<br />
=== CentOS-7 Community Build Image [microSD Boot] ===<br />
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)<br />
** DD image (for 8GB micoSD card and above)<br />
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]<br />
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]<br />
* Login with<br />
** username: root<br />
** password: centos<br />
<br />
== Manjaro ARM ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
* Console and SSH default login:<br />
** username: manjaro<br />
** password: manjaro<br />
<br />
=== Manjaro KDE Plasma Release [20.02.1] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde-plasma/20.02.1/ Download links and signatures]<br />
*** size: 1015.84 MB<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] [preview1] ===<br />
* [http://pumath.dl.osdn.jp/storage/g/m/ma/manjaro-arm/rockpro64/kde/preview1/Manjaro-ARM-kde-rockpro64-preview1.img.xz Direct download from Manjaro]<br />
*** size: 992MB<br />
*** MD5 (Zip file): c77edb0ad49cefcf16afc88548ffa177<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde/19.06/Manjaro-ARM-kde-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 991MB<br />
*** MD5 (Zip file): fe009307c2cb37748ac85952decc261f<br />
<br />
=== Manjaro LXQT ARM Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/lxqt/19.06/Manjaro-ARM-lxqt-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 762MB<br />
*** MD5 (Zip file): 58bce45e4a05e26636193d5abee283b7<br />
<br />
=== Manjaro ARM Minimal Community Build Image [microSD Boot] [19.06] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/minimal/19.06/Manjaro-ARM-minimal-rockpro64-19.06.img.xz Direct download from Manjaro]<br />
*** size: 337MB<br />
*** MD5 (Zip file): 87576a1a25ad542f2b4bfeb33069ce38<br />
<br />
== Chromium ==<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/chromium.jpg<br />
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
<br />
=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===<br />
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]<br />
*** size: 357MB<br />
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e<br />
<br />
== Batocera Linux ==<br />
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png<br />
* It is an operating system in retrogaming<br />
* Visit the project's website here (https://batocera.org/)<br />
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]<br />
*** File Size: 834MB<br />
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0<br />
<br />
=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]<br />
*** File Size: 857MB<br />
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4<br />
<br />
== Recalbox ==<br />
http://files.pine64.org/sw/pine64_installer/json/recalbox.png<br />
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! <br />
* Visit the project's website here (https://www.recalbox.com/)<br />
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)<br />
<br />
=== Recalbox Community Build Image [microSD / eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]<br />
<br />
== Odroid Retro Arena==<br />
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png<br />
<br />
=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===<br />
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.<br />
* Visit the project's [http://odroidarena.com/downloads/]<br />
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]<br />
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]<br />
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc<br />
*** File Size: 4.06GB<br />
<br />
== OpenWrt ==<br />
<br />
[[File:Openwrt-logo.png|300px]]<br />
<br />
=== OpenWrt Snapshot Build [microSD Boot] ===<br />
* OpenWrt with 5.4 mainline linux kernel<br />
** DD image (for 512MB micoSD card and above)<br />
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]<br />
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]<br />
* Login with SSH on<br />
** default IP: 192.168.1.1<br />
** username: root<br />
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]<br />
<br />
= BSD Images =<br />
==NetBSD==<br />
[[File:Netbsd2.png]]<br />
<br />
To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
<br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]<br />
** size: 339 MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
==OpenBSD==<br />
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg<br />
<br />
Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]<br />
<br />
Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]<br />
<br />
= Android Images =<br />
== Android 9.0.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_9.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20190427] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 16GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7<br />
*** File Size: 609MB<br />
* DD image for 32GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C<br />
*** File Size: 627MB<br />
* DD image for 64GB eMMC module<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF<br />
*** File Size: 663MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20190506] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image for 8GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A<br />
*** File Size: 599MB<br />
* DD image for 16GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C<br />
*** File Size: 609MB<br />
* DD image for 32GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B<br />
*** File Size: 627MB<br />
* DD image for 64GB microSD card<br />
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284<br />
*** File Size: 663MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20190427] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341<br />
** File Size: 592MB<br />
<br />
== Android 8.1.0 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_8.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180828] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A<br />
** File Size: 414MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20181212] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* DD image (for 8GB micoSD card and above)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405<br />
** File Size: 616MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180828] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE<br />
** File Size: 415MB<br />
<br />
== Android 7.1.2 ==<br />
http://files.pine64.org/sw/pine64_installer/json/android_7.png<br />
<br />
=== Stock for DD method [eMMC Boot] [20180809] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 00F194017557017C2588724686E90CEA<br />
** File Size: 498MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180809] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9<br />
** File Size: 483MB<br />
<br />
=== Stock for DD method [micro SD Boot] [20180920] ===<br />
* DD image to microSD card and boot. <br />
* Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]<br />
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE<br />
** File Size: 765MB<br />
<br />
=== Stock for DD method [eMMC Boot] [20180518] ===<br />
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B<br />
** File Size: 345MB<br />
<br />
=== Stock for RK Flash tool [eMMC Boot] [20180518] ===<br />
* Please unzip first and then using Android tool to flash in<br />
* The OTG port located at USB type-C connector, needs USB type A to type C cable.<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920<br />
** File Size: 342MB<br />
<br />
=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]<br />
* Please allow 3-5 minutes boot up time on first time for initialization<br />
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)<br />
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]<br />
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9<br />
** File Size: 350MB<br />
<br />
== Android SDK ==<br />
<br />
=== Android P SDK [v9.0] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E<br />
** File Size: 125.16GB<br />
<br />
=== Android NN (Neural Network) SDK Release Note ===<br />
* <span style="color:#ff0000"> The Android NN will be included in the upcoming stock Android 8.1 build release. </span><br />
* [http://files.pine64.org/os/sdk/ROCKPro64/RK3399_Android8.1_AndroidNN_SDK_V1.0_20180605_Release_Note.pdf This SDK document provides GPU acceleration support for Tensorflow AI related applications AndroidNN API.]<br />
<br />
=== Android O SDK [v8.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android8.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 7C1908C1F73759DF8D9117B3DDDD3436<br />
** File Size: 93.54GB<br />
<br />
=== Android N SDK [v7.1] ===<br />
* [http://files.pine64.org/os/sdk/ROCKPro64/ROCKPro64_SDK_android7.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 71A227652A700AE41354E179A3734133<br />
** File Size: 53.30GB<br />
<br />
= For Linux Developer =<br />
<br />
The Ayufan github page<br />
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]<br />
<br />
Below are the LPDDR4 driver for RK3399<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]<br />
<br />
ROCKPro64 related files<br />
<br />
* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]<br />
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]<br />
<br />
= Miscellaneous tools =<br />
<br />
** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]<br />
** [[Set MacAddress on ROCK64]]<br />
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]<br />
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]<br />
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]<br />
<br />
::::::::::[[ROCKPro64_Software_Release#top | Top of page]]</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5673PinePhone Software Releases2020-05-20T23:09:23Z<p>Dukla2000: /* To use the USB port for networking */</p>
<hr />
<div>This page contains a list of all available releases for the PinePhone as well as links to further resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operation systems.<br />
<br />
Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
= Software Releases =<br />
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you.<br />
<br />
Note: pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password.<br />
<br />
{{Hint|The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use only numbers in your password.}}<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install Firefox browser (or are using a demo image that already has it installed) then [https://wiki.postmarketos.org/wiki/Firefox these hints] in the pmOS wiki are recommended.<br />
<br />
* ''' How to contribute and report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
== Ubuntu Touch by UBports ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
* ''' user-id/password '''<br />
Set up during boot<br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' How to contribute and report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
== Mobian ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9850 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html Phosh user interface] (developed by Purism, Phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://images.mobian-project.org/ Mobian downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/mobian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/mobian1/wiki/-/wikis/Install project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
mobian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' How to contribute and report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
For serial port access:<br />
<br />
sudo apt install pinephone-devtools<br />
<br />
Note that this also installs openssh-server, see [https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 here].<br />
<br />
If you want to share your PinePhone mobile data internet connection via the USB port then in addition to the above, you should<br />
sudo nmcli connection modify USB-gadget ipv4.method shared<br />
<br />
==== To enable WiFi hotspot ====<br />
<br />
In "Settings > WiFi" enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev yad<br />
<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]. When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
Instructions:<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
* ''' user-id/password ''' Set PIN on initialization.<br />
<br />
* ''' What works, what does not work '''<br />
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.<br />
<br />
May 9th 2020: Voice calls now work in pipeline, arriving in builds within days. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi is intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.<br />
<br />
If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.<br />
<br />
=== Updates ===<br />
OTA is supported: `zypper refresh && zypper update` as root (`devel-su` to get root access). Things that need reflash are bootloader specific at the moment. If improvements like crust or changes of partition layout are added then you need to reflash.<br />
<br />
=== How to contribute and report defects ===<br />
<br />
* See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues SailfishOS wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* See the [https://sailfishos.org/wiki/SailfishOS SailfishOS wiki] for options to contribute<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' source code '''<br />
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [http://pureos.ironrobin.net/git/clover/pinephone/ repository.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' How to contribute and report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See the end of the announcement here.]<br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' How to contribute and report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' How to contribute and report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
= Factory Test OS =<br />
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.<br />
<br />
Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.<br />
<br />
Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.<br />
<br />
Links:<br />
* [https://images.postmarketos.org/pinephone/ Software Images]: (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)<br />
* [https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
= Installing other ARM64 distributions =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs and writing u-boot and the bootloader.<br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the BraveHeart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5672PinePhone Software Releases2020-05-20T23:08:50Z<p>Dukla2000: /* To use the USB port for networking */</p>
<hr />
<div>This page contains a list of all available releases for the PinePhone as well as links to further resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operation systems.<br />
<br />
Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
= Software Releases =<br />
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you.<br />
<br />
Note: pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password.<br />
<br />
{{Hint|The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use only numbers in your password.}}<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install Firefox browser (or are using a demo image that already has it installed) then [https://wiki.postmarketos.org/wiki/Firefox these hints] in the pmOS wiki are recommended.<br />
<br />
* ''' How to contribute and report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
== Ubuntu Touch by UBports ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
* ''' user-id/password '''<br />
Set up during boot<br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' How to contribute and report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
== Mobian ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9850 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html Phosh user interface] (developed by Purism, Phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://images.mobian-project.org/ Mobian downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/mobian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/mobian1/wiki/-/wikis/Install project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
mobian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' How to contribute and report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
For serial port access:<br />
<br />
sudo apt install pinephone-devtools<br />
<br />
Note that this also installs openssh-server, see [https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 here].<br />
<br />
If you want to share your mobile data internet connection via the USB port then in addition to the above, you should<br />
sudo nmcli connection modify USB-gadget ipv4.method shared<br />
<br />
==== To enable WiFi hotspot ====<br />
<br />
In "Settings > WiFi" enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev yad<br />
<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]. When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
Instructions:<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
* ''' user-id/password ''' Set PIN on initialization.<br />
<br />
* ''' What works, what does not work '''<br />
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.<br />
<br />
May 9th 2020: Voice calls now work in pipeline, arriving in builds within days. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi is intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.<br />
<br />
If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.<br />
<br />
=== Updates ===<br />
OTA is supported: `zypper refresh && zypper update` as root (`devel-su` to get root access). Things that need reflash are bootloader specific at the moment. If improvements like crust or changes of partition layout are added then you need to reflash.<br />
<br />
=== How to contribute and report defects ===<br />
<br />
* See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues SailfishOS wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* See the [https://sailfishos.org/wiki/SailfishOS SailfishOS wiki] for options to contribute<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' source code '''<br />
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [http://pureos.ironrobin.net/git/clover/pinephone/ repository.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' How to contribute and report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See the end of the announcement here.]<br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' How to contribute and report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' How to contribute and report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
= Factory Test OS =<br />
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.<br />
<br />
Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.<br />
<br />
Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.<br />
<br />
Links:<br />
* [https://images.postmarketos.org/pinephone/ Software Images]: (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)<br />
* [https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
= Installing other ARM64 distributions =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs and writing u-boot and the bootloader.<br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the BraveHeart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5671PinePhone Software Releases2020-05-20T23:04:54Z<p>Dukla2000: /* To enable WiFi hotspot */ it now works out of the box</p>
<hr />
<div>This page contains a list of all available releases for the PinePhone as well as links to further resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operation systems.<br />
<br />
Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
= Software Releases =<br />
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you.<br />
<br />
Note: pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password.<br />
<br />
{{Hint|The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use only numbers in your password.}}<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install Firefox browser (or are using a demo image that already has it installed) then [https://wiki.postmarketos.org/wiki/Firefox these hints] in the pmOS wiki are recommended.<br />
<br />
* ''' How to contribute and report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
== Ubuntu Touch by UBports ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
* ''' user-id/password '''<br />
Set up during boot<br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' How to contribute and report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
== Mobian ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9850 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html Phosh user interface] (developed by Purism, Phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://images.mobian-project.org/ Mobian downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/mobian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/mobian1/wiki/-/wikis/Install project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
mobian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' How to contribute and report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
For serial port access:<br />
<br />
sudo apt install pinephone-devtools<br />
<br />
Note that this also installs openssh-server, see [https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 here].<br />
<br />
==== To enable WiFi hotspot ====<br />
<br />
In "Settings > WiFi" enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev yad<br />
<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]. When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
Instructions:<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
* ''' user-id/password ''' Set PIN on initialization.<br />
<br />
* ''' What works, what does not work '''<br />
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.<br />
<br />
May 9th 2020: Voice calls now work in pipeline, arriving in builds within days. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi is intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.<br />
<br />
If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.<br />
<br />
=== Updates ===<br />
OTA is supported: `zypper refresh && zypper update` as root (`devel-su` to get root access). Things that need reflash are bootloader specific at the moment. If improvements like crust or changes of partition layout are added then you need to reflash.<br />
<br />
=== How to contribute and report defects ===<br />
<br />
* See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues SailfishOS wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* See the [https://sailfishos.org/wiki/SailfishOS SailfishOS wiki] for options to contribute<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' source code '''<br />
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [http://pureos.ironrobin.net/git/clover/pinephone/ repository.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' How to contribute and report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See the end of the announcement here.]<br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' How to contribute and report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' How to contribute and report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' How to contribute and report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
= Factory Test OS =<br />
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.<br />
<br />
Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.<br />
<br />
Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.<br />
<br />
Links:<br />
* [https://images.postmarketos.org/pinephone/ Software Images]: (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)<br />
* [https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
= Installing other ARM64 distributions =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs and writing u-boot and the bootloader.<br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the BraveHeart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5619PinePhone Software Releases2020-05-17T21:39:22Z<p>Dukla2000: /* Mobian */</p>
<hr />
<div>This page contains a list of all available releases for the PinePhone as well as links to further resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operation systems.<br />
<br />
Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
= Software Releases =<br />
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBports ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
* ''' user-id/password '''<br />
Set up during boot<br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Mobian ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9850 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html Phosh user interface] (developed by Purism, Phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://images.mobian-project.org/ Mobian downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/mobian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/mobian1/wiki/-/wikis/Install project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
mobian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
Or for serial port access you should<br />
sudo apt install pinephone-devtools<br />
Note this also installs openssh-server.<br />
[https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 See this post.]<br />
<br />
==== To enable WiFi hotspot ====<br />
sudo apt install dnsmasq-base<br />
Then you need to configure a suitable range of available IP addresses in /etc/dnsmasq.conf e.g. the following single line:<br />
dhcp-range=10.42.0.50,10.42.0.150,24h<br />
Finally in Settings, WiFi, enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev yad<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. <br />
Unlike other solutions, this works across reboots.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
* ''' user-id/password ''' Set PIN on initialization.<br />
<br />
* ''' What works, what does not work '''<br />
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.<br />
<br />
May 9th 2020: Voice calls now work in pipeline, arriving in builds within days. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi is intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.<br />
<br />
If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.<br />
<br />
=== Updates ===<br />
OTA is supported: `zypper refresh && zypper update` as root (`devel-su` to get root access). Things that need reflash are bootloader specific at the moment. If improvements like crust or changes of partition layout are added then you need to reflash.<br />
<br />
=== Where/how to report defects ===<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' source code '''<br />
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [http://pureos.ironrobin.net/git/clover/pinephone/ repository.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Factory Test OS =<br />
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.<br />
<br />
Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.<br />
<br />
Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.<br />
<br />
Links:<br />
* [https://images.postmarketos.org/pinephone/ Software Images]: (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)<br />
* [https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing other ARM64 distributions =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the BraveHeart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5618PinePhone Software Releases2020-05-17T21:38:35Z<p>Dukla2000: /* Debian-PinePhone */ Initial re-brand to Mobian</p>
<hr />
<div>This page contains a list of all available releases for the PinePhone as well as links to further resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operation systems.<br />
<br />
Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
= Software Releases =<br />
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBports ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
* ''' user-id/password '''<br />
Set up during boot<br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Mobian ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html Phosh user interface] (developed by Purism, Phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://images.mobian-project.org/ Mobian downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/mobian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/mobian1/wiki/-/wikis/Install project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
mobian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
Or for serial port access you should<br />
sudo apt install pinephone-devtools<br />
Note this also installs openssh-server.<br />
[https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 See this post.]<br />
<br />
==== To enable WiFi hotspot ====<br />
sudo apt install dnsmasq-base<br />
Then you need to configure a suitable range of available IP addresses in /etc/dnsmasq.conf e.g. the following single line:<br />
dhcp-range=10.42.0.50,10.42.0.150,24h<br />
Finally in Settings, WiFi, enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev yad<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. <br />
Unlike other solutions, this works across reboots.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
* ''' user-id/password ''' Set PIN on initialization.<br />
<br />
* ''' What works, what does not work '''<br />
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.<br />
<br />
May 9th 2020: Voice calls now work in pipeline, arriving in builds within days. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi is intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.<br />
<br />
If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.<br />
<br />
=== Updates ===<br />
OTA is supported: `zypper refresh && zypper update` as root (`devel-su` to get root access). Things that need reflash are bootloader specific at the moment. If improvements like crust or changes of partition layout are added then you need to reflash.<br />
<br />
=== Where/how to report defects ===<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' source code '''<br />
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [http://pureos.ironrobin.net/git/clover/pinephone/ repository.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Factory Test OS =<br />
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.<br />
<br />
Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.<br />
<br />
Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.<br />
<br />
Links:<br />
* [https://images.postmarketos.org/pinephone/ Software Images]: (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)<br />
* [https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing other ARM64 distributions =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the BraveHeart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5520PinePhone Software Releases2020-04-30T21:48:24Z<p>Dukla2000: /* To adjust screen resolution */ add yad to install list</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Reuse SD card for data storage on system booting from eMMC==<br />
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.<br />
<br />
This can be done as follows on any linux system:<br />
lsblk<br />
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0<br />
then<br />
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card. <br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
This is a list of OSs that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
Or for serial port access you should<br />
sudo apt install pinephone-devtools<br />
Note this also installs openssh-server.<br />
[https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 See this post.]<br />
<br />
==== To enable WiFi hotspot ====<br />
sudo apt install dnsmasq-base<br />
Then you need to configure a suitable range of available IP addresses in /etc/dnsmasq.conf e.g. the following single line:<br />
dhcp-range=10.42.0.50,10.42.0.150,24h<br />
Finally in Settings, WiFi, enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev yad<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. <br />
Unlike other solutions, this works across reboots.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
SFOS for pinephone no longer has a defect with the auto brightness! There is currently (21-04) a problem with the lockscreen not displaying unless you have a sim card in the phone - doesn't have to be an active one. Wifi is also very intermittent and slow when it does work. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' and maintained by "clover" that can be downloaded [https://droppy.ironrobin.net/#/Images/PureOS here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to sd card on the pinephone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5512PinePhone Software Releases2020-04-28T14:12:09Z<p>Dukla2000: /* To enable WiFi hotspot */</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Reuse SD card for data storage on system booting from eMMC==<br />
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.<br />
<br />
This can be done as follows on any linux system:<br />
lsblk<br />
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0<br />
then<br />
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card. <br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
This is a list of OSs that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
Or for serial port access you should<br />
sudo apt install pinephone-devtools<br />
Note this also installs openssh-server.<br />
[https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 See this post.]<br />
<br />
==== To enable WiFi hotspot ====<br />
sudo apt install dnsmasq-base<br />
Then you need to configure a suitable range of available IP addresses in /etc/dnsmasq.conf e.g. the following single line:<br />
dhcp-range=10.42.0.50,10.42.0.150,24h<br />
Finally in Settings, WiFi, enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
SFOS for pinephone no longer has a defect with the auto brightness! There is currently (21-04) a problem with the lockscreen not displaying unless you have a sim card in the phone - doesn't have to be an active one. Wifi is also very intermittent and slow when it does work. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to sd card on the pinephone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5511PinePhone Software Releases2020-04-28T13:49:10Z<p>Dukla2000: /* Debian-PinePhone */ Update & rework user experience section</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Reuse SD card for data storage on system booting from eMMC==<br />
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.<br />
<br />
This can be done as follows on any linux system:<br />
lsblk<br />
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0<br />
then<br />
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card. <br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
This is a list of OSs that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
Or for serial port access you should<br />
sudo apt install pinephone-devtools<br />
Note this also installs openssh-server.<br />
[https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 See this post.]<br />
<br />
==== To enable WiFi hotspot ====<br />
sudo apt install dnsmasq <br />
Then you need to configure a suitable range of available IP addresses in /etc/dnsmasq.conf e.g. the following single line:<br />
dhcp-range=10.42.0.50,10.42.0.150,24h<br />
Finally in Settings, WiFi, enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
SFOS for pinephone no longer has a defect with the auto brightness! There is currently (21-04) a problem with the lockscreen not displaying unless you have a sim card in the phone - doesn't have to be an active one. Wifi is also very intermittent and slow when it does work. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to sd card on the pinephone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5477PinePhone Software Releases2020-04-16T21:18:29Z<p>Dukla2000: /* Boot priority */ move megi multi boot to other resources</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Reuse SD card for data storage on system booting from eMMC==<br />
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.<br />
<br />
This can be done as follows on any linux system:<br />
lsblk<br />
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0<br />
then<br />
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card. <br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
* ''' User Experience Notes '''<br />
<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
'''The Chatty app''' requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
'''Most of Debian's repository is available.''' There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
'''Apps that don't work with Wayland''': if you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (9 Apr) version of Sailfish no longer has a defect with the auto brightness! To install on an sdcard you need to have a sim card in the phone - doesn't have to be an active one. If you then unset the device lock password in settings you can take the simcard out. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5476PinePhone Software Releases2020-04-16T21:18:24Z<p>Dukla2000: /* Other Resources */</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image. <br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Reuse SD card for data storage on system booting from eMMC==<br />
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.<br />
<br />
This can be done as follows on any linux system:<br />
lsblk<br />
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0<br />
then<br />
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card. <br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
* ''' User Experience Notes '''<br />
<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
'''The Chatty app''' requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
'''Most of Debian's repository is available.''' There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
'''Apps that don't work with Wayland''': if you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (9 Apr) version of Sailfish no longer has a defect with the auto brightness! To install on an sdcard you need to have a sim card in the phone - doesn't have to be an active one. If you then unset the device lock password in settings you can take the simcard out. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5475PinePhone Software Releases2020-04-16T21:07:29Z<p>Dukla2000: Add section to clear SPL & Uboot to use SDcard for data storage</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image. <br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Reuse SD card for data storage on system booting from eMMC==<br />
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.<br />
<br />
This can be done as follows on any linux system:<br />
lsblk<br />
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0<br />
then<br />
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card. <br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
* ''' User Experience Notes '''<br />
<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
'''The Chatty app''' requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
'''Most of Debian's repository is available.''' There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
'''Apps that don't work with Wayland''': if you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (9 Apr) version of Sailfish no longer has a defect with the auto brightness! To install on an sdcard you need to have a sim card in the phone - doesn't have to be an active one. If you then unset the device lock password in settings you can take the simcard out. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5474PinePhone Software Releases2020-04-16T21:00:37Z<p>Dukla2000: Move "any ARM64 distribution" to its own chapter. And after 'normal' releases to avoid confusing noobs!</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image. <br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
* ''' User Experience Notes '''<br />
<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
'''The Chatty app''' requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
'''Most of Debian's repository is available.''' There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
'''Apps that don't work with Wayland''': if you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (9 Apr) version of Sailfish no longer has a defect with the auto brightness! To install on an sdcard you need to have a sim card in the phone - doesn't have to be an active one. If you then unset the device lock password in settings you can take the simcard out. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5465PinePhone Software Releases2020-04-14T20:56:38Z<p>Dukla2000: /* postmarketOS */ Clarify numeric password is for Phosh</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image. <br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Installing Any ARM64 Distribution ==<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
* ''' User Experience Notes '''<br />
<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
'''The Chatty app''' requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
'''Most of Debian's repository is available.''' There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
'''Apps that don't work with Wayland''': if you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (9 Apr) version of Sailfish no longer has a defect with the auto brightness! To install on an sdcard you need to have a sim card in the phone - doesn't have to be an active one. If you then unset the device lock password in settings you can take the simcard out. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5464PinePhone Software Releases2020-04-14T20:53:48Z<p>Dukla2000: /* Backlight */ reduce all to some - Debian eg is fine</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image. <br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Installing Any ARM64 Distribution ==<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
== Backlight ==<br />
Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
* ''' User Experience Notes '''<br />
<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
'''The Chatty app''' requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. Unlike other solutions, this works across reboots.<br />
<br />
'''Most of Debian's repository is available.''' There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
'''Apps that don't work with Wayland''': if you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (9 Apr) version of Sailfish no longer has a defect with the auto brightness! To install on an sdcard you need to have a sim card in the phone - doesn't have to be an active one. If you then unset the device lock password in settings you can take the simcard out. If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. You may need to get the rpm onto the phone by other means as the built in browser is not working at the moment. Press the rpm file and you will be asked to install it. Once you have the Storeman app installed browse the store and add repository first from the pulley menu before installing the app you want. The Webcat browser on openstore works.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
* ''' What works, what does not work '''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.<br />
<br />
<cite><br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5425PinePhone Software Releases2020-04-03T09:35:54Z<p>Dukla2000: /* Ubuntu Touch by UBPorts */ remove modem scripts as no longer needed</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image. <br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Installing Any ARM64 Distribution ==<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
Don't forget to extract the image: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
March 9th release: [https://forum.pine64.org/showthread.php?tid=9016&pid=61968#pid61968 thread]<br />
<br />
Known issues as of March 27th, 2020:<br />
* headphone jack insertion is still not detected, you need to manually switch to the "Headphone" output in "Settings" -> "Sound"<br />
* bluetooth doesn't work on reboots, you need to turn your phone off and power it on again<br />
* camera is still not usable, even though the low-level drivers seem to work<br />
* a few voice calls issues: unable to mute the mic, audio quality to be improved (if the hardware is capable of more)<br />
* Chats app: In order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps<br />
<br />
Most of Debian's repository is available. There are packages that need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Currently their wiki page is out of date.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (2 Apr) version of Sailfish no longer has a defect with the auto brightness! If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. Browse the apps and add repository first from the pulley menu before installing the app. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [https://droppy.ironrobin.net/#/Images/PureOS here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
BYOP sim card: works with T-Mobile and ATT compatible SIM cards provided in BYOP kit<br />
"Activation was as simple as putting the card in the phone and sending a text message."<br />
"I went to a different area today with better cell tower coverage and was able to make my first call from my pinephone."<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5424PinePhone Software Releases2020-04-03T09:35:11Z<p>Dukla2000: /* Ubuntu Touch by UBPorts */ update link to video</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image. <br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<br />
<br />
Using Parted: <br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone: ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Installing Any ARM64 Distribution ==<br />
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distro to the PinePhone.<br />
<br />
'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.<br />
<br />
If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<br />
# Follow the README instructions, which involves copying the kernel modules into the sd card rootfs and writing u-boot and the bootloader.<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
Don't forget to extract the image: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
March 9th release: [https://forum.pine64.org/showthread.php?tid=9016&pid=61968#pid61968 thread]<br />
<br />
Known issues as of March 27th, 2020:<br />
* headphone jack insertion is still not detected, you need to manually switch to the "Headphone" output in "Settings" -> "Sound"<br />
* bluetooth doesn't work on reboots, you need to turn your phone off and power it on again<br />
* camera is still not usable, even though the low-level drivers seem to work<br />
* a few voice calls issues: unable to mute the mic, audio quality to be improved (if the hardware is capable of more)<br />
* Chats app: In order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
<br />
'''To adjust screen resolution''' [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
# <code>sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev</code><br />
# Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
# When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps<br />
<br />
Most of Debian's repository is available. There are packages that need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Currently their wiki page is out of date.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (2 Apr) version of Sailfish no longer has a defect with the auto brightness! If you're not familiar with SFOS, be prepared by having a (free) Jolla account and pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store. To enable openrepos.net install the Storeman app by downloading the rpm from https://openrepos.net/content/osetr/storeman. Browse the apps and add repository first from the pulley menu before installing the app. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [https://droppy.ironrobin.net/#/Images/PureOS here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
BYOP sim card: works with T-Mobile and ATT compatible SIM cards provided in BYOP kit<br />
"Activation was as simple as putting the card in the phone and sending a text message."<br />
"I went to a different area today with better cell tower coverage and was able to make my first call from my pinephone."<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5336PinePhone Software Releases2020-03-18T19:23:30Z<p>Dukla2000: /* Carriers That Do Not Work */ insert link to top of page</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
https://forum.pine64.org/showthread.php?tid=9444<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card<br />
# once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Resize partition to fill the SD card<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct.<br />
# Turn off phone, remove SD card. Turn on phone.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
March 9th release: [https://forum.pine64.org/showthread.php?tid=9016&pid=61968#pid61968 thread]<br />
<br />
Known issues as of March 9th, 2020:<br />
* ModemManager acts weirdly if your SIM card needs PIN code verification, it is recommended to disable it for now<br />
* headphone jack insertion is still not detected, you need to manually switch to the "Headphone" output in "Settings" -> "Sound"<br />
* bluetooth and camera are still not usable, even though the low-level drivers seem to work<br />
* a few voice calls issues: unable to mute the mic, headset mic not working, audio quality to be improved (if the hardware is capable of more)<br />
* Chatty app: In order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
* To adjust screen resolution, see these threads: [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
Most of Debian's repository is available. There are packages that need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Currently their wiki page is out of date.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://www.mozzwald.com/pp/pureos-pinephone-20200226.img.xz here.] Instructions to create your own image are [http://www.mozzwald.com/pp/pureos-pinephone-build-instructions.txt here.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
The UI is smooth, WiFi, Bluetooth, incoming SMS, and the modem all work.<br />
Voice calls, SMS (outgoing), and mobile data don't work (yet).<br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
USB DHCP doesn't work yet, so you'll have to assign 172.16.42.2/24 to the phone's network interface.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
== ATT-based ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Mint Mobile (USA) ==<br />
<br />
https://www.mintmobile.com/setup-for-android/<br />
<br />
APN settings for Mint Mobile on Debian + Phosh:<br />
<br />
Simply go to Settings > Mobile > Access Point Names > + button to add new,<br />
Name: Ultra<br />
APN: Wholesale.<br />
Then save it.<br />
<br />
Call their customer service to activate using the number on their website. No need to use website or mobile apps to activate.<br />
<br />
Reboot phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
BYOP sim card: works with T-Mobile and ATT compatible SIM cards provided in BYOP kit<br />
"Activation was as simple as putting the card in the phone and sending a text message."<br />
"I went to a different area today with better cell tower coverage and was able to make my first call from my pinephone."<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5335PinePhone Software Releases2020-03-18T19:22:33Z<p>Dukla2000: /* Software Releases */ Drop NixOS & LuneOS down page and clarify Android.</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
https://forum.pine64.org/showthread.php?tid=9444<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card<br />
# once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Resize partition to fill the SD card<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct.<br />
# Turn off phone, remove SD card. Turn on phone.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
March 9th release: [https://forum.pine64.org/showthread.php?tid=9016&pid=61968#pid61968 thread]<br />
<br />
Known issues as of March 9th, 2020:<br />
* ModemManager acts weirdly if your SIM card needs PIN code verification, it is recommended to disable it for now<br />
* headphone jack insertion is still not detected, you need to manually switch to the "Headphone" output in "Settings" -> "Sound"<br />
* bluetooth and camera are still not usable, even though the low-level drivers seem to work<br />
* a few voice calls issues: unable to mute the mic, headset mic not working, audio quality to be improved (if the hardware is capable of more)<br />
* Chatty app: In order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
* To adjust screen resolution, see these threads: [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
Most of Debian's repository is available. There are packages that need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Currently their wiki page is out of date.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://www.mozzwald.com/pp/pureos-pinephone-20200226.img.xz here.] Instructions to create your own image are [http://www.mozzwald.com/pp/pureos-pinephone-build-instructions.txt here.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
The UI is smooth, WiFi, Bluetooth, incoming SMS, and the modem all work.<br />
Voice calls, SMS (outgoing), and mobile data don't work (yet).<br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
USB DHCP doesn't work yet, so you'll have to assign 172.16.42.2/24 to the phone's network interface.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
== ATT-based ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Mint Mobile (USA) ==<br />
<br />
https://www.mintmobile.com/setup-for-android/<br />
<br />
APN settings for Mint Mobile on Debian + Phosh:<br />
<br />
Simply go to Settings > Mobile > Access Point Names > + button to add new,<br />
Name: Ultra<br />
APN: Wholesale.<br />
Then save it.<br />
<br />
Call their customer service to activate using the number on their website. No need to use website or mobile apps to activate.<br />
<br />
Reboot phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
BYOP sim card: works with T-Mobile and ATT compatible SIM cards provided in BYOP kit<br />
"Activation was as simple as putting the card in the phone and sending a text message."<br />
"I went to a different area today with better cell tower coverage and was able to make my first call from my pinephone."<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5334PinePhone Software Releases2020-03-18T09:58:35Z<p>Dukla2000: /* Safe & Easy Method */ change link to the release page</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
https://forum.pine64.org/showthread.php?tid=9444<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card<br />
# once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Resize partition to fill the SD card<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct.<br />
# Turn off phone, remove SD card. Turn on phone.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run: <br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from lsblk).<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
March 9th release: [https://forum.pine64.org/showthread.php?tid=9016&pid=61968#pid61968 thread]<br />
<br />
Known issues as of March 9th, 2020:<br />
* ModemManager acts weirdly if your SIM card needs PIN code verification, it is recommended to disable it for now<br />
* headphone jack insertion is still not detected, you need to manually switch to the "Headphone" output in "Settings" -> "Sound"<br />
* bluetooth and camera are still not usable, even though the low-level drivers seem to work<br />
* a few voice calls issues: unable to mute the mic, headset mic not working, audio quality to be improved (if the hardware is capable of more)<br />
* Chatty app: In order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text. <br />
* To adjust screen resolution, see these threads: [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685] <br />
<br />
Most of Debian's repository is available. There are packages that need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Currently their wiki page is out of date.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://www.mozzwald.com/pp/pureos-pinephone-20200226.img.xz here.] Instructions to create your own image are [http://www.mozzwald.com/pp/pureos-pinephone-build-instructions.txt here.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
The UI is smooth, WiFi, Bluetooth, incoming SMS, and the modem all work.<br />
Voice calls, SMS (outgoing), and mobile data don't work (yet).<br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
USB DHCP doesn't work yet, so you'll have to assign 172.16.42.2/24 to the phone's network interface.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This may actually be a very useful one, since GNU/Linux images aren't ready for daily usage yet. Maybe, one could dual boot Android and its OS of choice to have the best of both worlds.<br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
== ATT-based ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Mint Mobile (USA) ==<br />
<br />
https://www.mintmobile.com/setup-for-android/<br />
<br />
APN settings for Mint Mobile on Debian + Phosh:<br />
<br />
Simply go to Settings > Mobile > Access Point Names > + button to add new,<br />
Name: Ultra<br />
APN: Wholesale.<br />
Then save it.<br />
<br />
Call their customer service to activate using the number on their website. No need to use website or mobile apps to activate.<br />
<br />
Reboot phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
BYOP sim card: works with T-Mobile and ATT compatible SIM cards provided in BYOP kit<br />
"Activation was as simple as putting the card in the phone and sending a text message."<br />
"I went to a different area today with better cell tower coverage and was able to make my first call from my pinephone."<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5279PinePhone Software Releases2020-03-09T10:50:43Z<p>Dukla2000: /* Backlight */ clarify auto backlight</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC ==<br />
* Prepare a new SD card as above<br />
* Boot the phone with your new SD card image<br />
* The eMMC appears as /dev/mmcblk2 and so any standard Linux mechanism to move your image there will work, e.g. dd.<br />
<br />
You can dd the current installation to eMMC using this command:<br />
<br />
dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M<br />
<br />
Where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct.<br />
<br />
It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it. Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC. <br />
<br />
This is method is more convenient because you don't have to rebuild the image from within the PinePhone, which usually requires resizing partitions and other extra steps.<br />
<br />
Also, in the default/factory installed image provided to you upon shipment, there is an option to install any image to the eMMC.<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space. To do so after you've booted the device, install growpart and resize2fs on the phone and then run:<br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X and Y correspond to your SD card's identifier (viewable from lsblk).<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Ryodebianphosh.png]]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
The UI works fine, as well as Wifi, mobile data and text messaging.<br />
Voice calls, however, don't work for now, as is the case for bluetooth and the camera.<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for more details.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://www.mozzwald.com/pp/pureos-pinephone-20200226.img.xz here.] Instructions to create your own image are [http://www.mozzwald.com/pp/pureos-pinephone-build-instructions.txt here.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
The UI is smooth, WiFi, Bluetooth, incoming SMS, and the modem all work.<br />
Voice calls, SMS (outgoing), and mobile data don't work (yet).<br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5278PinePhone Software Releases2020-03-09T10:46:16Z<p>Dukla2000: /* Installation to eMMC */ add typical device names.</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
== Installation to eMMC ==<br />
* Prepare a new SD card as above<br />
* Boot the phone with your new SD card image<br />
* The eMMC appears as /dev/mmcblk2 and so any standard Linux mechanism to move your image there will work, e.g. dd.<br />
<br />
You can dd the current installation to eMMC using this command:<br />
<br />
dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M<br />
<br />
Where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct.<br />
<br />
It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it. Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC. <br />
<br />
This is method is more convenient because you don't have to rebuild the image from within the PinePhone, which usually requires resizing partitions and other extra steps.<br />
<br />
Also, in the default/factory installed image provided to you upon shipment, there is an option to install any image to the eMMC.<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space. To do so after you've booted the device, install growpart and resize2fs on the phone and then run:<br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X and Y correspond to your SD card's identifier (viewable from lsblk).<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is currently the only OS that initially uses automatic backlight control. This makes the screen to appear blank. When shining a bright light on the screen, you can still navigate the screen. (and maybe the screen switches on temporarily due to the light sensor) This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Ryodebianphosh.png]]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
The UI works fine, as well as Wifi, mobile data and text messaging.<br />
Voice calls, however, don't work for now, as is the case for bluetooth and the camera.<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for more details.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://www.mozzwald.com/pp/pureos-pinephone-20200226.img.xz here.] Instructions to create your own image are [http://www.mozzwald.com/pp/pureos-pinephone-build-instructions.txt here.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
The UI is smooth, WiFi, Bluetooth, incoming SMS, and the modem all work.<br />
Voice calls, SMS (outgoing), and mobile data don't work (yet).<br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone&diff=5277PinePhone2020-03-09T10:35:45Z<p>Dukla2000: correct BraveHeart test image charge/change</p>
<hr />
<div>The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. The "BraveHeart" edition was the first publicly-available version of the phone, though it came without a fully functional OS (factory test image) and was geared specifically towards tinkerers and hackers. People looking for a stable consumer-grade phone should wait for the final release, which is expected to occur in March 2020 and will be available for at least five years.<br />
<br />
<br />
<br />
<br />
== "BraveHeart" PinePhone Unboxing and First Time Preparation Guide ==<br />
<br />
[[File:PinePhone1.jpg|400px|thumb|right|PinePhone is capable of running a multitude of different Linux mobile OSes]]<br />
<br />
From the factory the battery has a sticker on it that isolates the battery from the phone. The battery '''will not''' charge until this is removed.<br />
<br />
After unboxing remove the back panel. Then remove the battery and peel off the clear plastic sticker below it that isolates the charging contact. Then replace the battery. See [[#Battery]] for more info.<br />
<br />
If you power on the phone the factory test image will boot. RTL8723CS (WiFi modem) will fail unless there is a WiFi network in range for it to see and the battery is charged. EG25 will fail until battery is charged.<br />
<br />
By default there is no true OS image installed on Braveheart phones. An SD card with a bootable image needs to be inserted into the phone. See section 12 below for a list of OS options. Note the SD and sim sockets are stacked on each other The SD slot is the "shallower" socket and the SIM card goes in the "deeper" socket.<br />
<br />
'''Some videos that illustrate the process:'''<br />
<br />
[https://www.youtube.com/watch?v=ACcxegtDVBI Excellent first time guide video from Rob Braxman Tech]<br />
<br />
[https://www.youtube.com/watch?v=Z0FMW72_OYcI Flash an OS to microSD card video from Rob Braxman Tech]<br />
<br />
== Specifications ==<br />
<br />
'''Dimensions:''' 160.5 x 76.6 x 9.2mm <br><br />
'''Weight:''' Between 180-200 grams <br><br />
'''SIM Card:''' Micro-SIM <br><br />
'''Display:'''<br />
: '''Size:''' 5.95 inches (151mm) diagonal<br />
: '''Type:''' HD IPS capacitive touchscreen, 16M colors<br />
: '''Resolution:''' 1440x720, 18:9 ratio <br><br />
'''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64] <br><br />
'''RAM:''' 2GB LPDDR3 SDRAM <br><br />
'''Internal Storage:''' 16GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC <br><br />
'''Back Camera:''' Single 5MP, 1/4", LED Flash <br><br />
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" <br><br />
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) <br><br />
'''Communication: [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf EG25-G]'''<br />
: '''LTE:''' B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41<br />
: '''WCDMA:''' B1, B2, B4, B5, B6, B8, B19<br />
: '''GSM:''' 850, 900, 1800, 1900 (MHz)<br />
: '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot<br />
: '''Bluetooth:''' 4.0, A2DP<br />
: '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
'''Sensors:''' Accelerometer, gyro, proximity, ambient light, compass <br><br />
'''[[#Killswitch configuration|Killswitches]]:''' Modem, Wifi & Bluetooth, Microphone, Cameras <br><br />
'''[[#Battery|Battery]]:''' [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf Lithium ion] Rated Capacity 2800mAh (10.64Wh), Typical Capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery) <br><br />
'''I/O:''' USB Type-C (SlimPort), USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== PinePhone Board Information, Schematics and Certifications ==<br />
* PinePhone Main Board Schematic:<br />
** [http://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]<br />
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]<br />
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]<br />
* PinePhone USB-C Small Board Schematic:<br />
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf "Braveheart" PinePhone USB-C small board Schematic ver 1.0]<br />
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf "Braveheart" PinePhone USB-C small board component top placement drawing ver 1.0]<br />
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf "Braveheart" PinePhone USB-C small board component bottom placement drawing ver 1.0]<br />
* PINE A64 Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Allwinner A64 SoC information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]<br />
* X-Powers AXP803 PMU (Power Management Unit) information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 (178 Balls) SDRAM:<br />
** [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 Datasheet]<br />
* CMOS Camera module information:<br />
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]<br />
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]<br />
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module Datasheet]<br />
* LCD Touch Screen Panel information:<br />
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel Specification]<br />
** [http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller Datasheet]<br />
<br />
** [http://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller Datasheet]<br />
* Lithium Battery information:<br />
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery Specification]<br />
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV Curve Chart]<br />
* Wifi/BT module information:<br />
<br />
* LTE module information:<br />
** [http://files.pine64.org/doc/datasheet/pinephone/Quectel_EG25-G_LTE_Specification_V1.0.pdf Quectel EG25-G LTE Module Specification]<br />
** [[Media:Quectel EC25EC21 AT Commands Manual V1.2.pdf|EC25&EC21 AT Commands Manual]]<br />
* Sensors:<br />
** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]<br />
** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS Datasheet]<br />
** [http://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]<br />
* Digital Video to USB-C Bridge:<br />
** [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 Product Brief]<br />
* Case information:<br />
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone Case Exploded Diagram]<br />
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone Back Battery Cover 3D file]<br />
<br />
== Developer works ==<br />
<br />
=== Megous ===<br />
[https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting start with PinePhone Hardware]<br />
<br />
[https://xnux.eu/devices/pine64-pinephone.html#toc-pine64-pinephone State of development progress]<br />
<br />
[https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]<br />
<br />
== Hardware Revisions ==<br />
<br />
# [[Project Anakin]]<br />
# [[Project Don't be evil|"Project Don't Be Evil" devkit]]<br />
# [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]<br />
# [[PinePhone v1.1 - Braveheart]]<br />
<br />
== Hardware Addons ==<br />
<br />
===[[PinePhone Hardware Accessory Compatibility]] list===<br />
List of devices working with the PinePhone (depending on OS support)<br />
<br />
=== USB-C Connector ===<br />
The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, HDMI port and Ethernet connection. The driver that would make this connection available is not supported at this time.<br />
<br />
===Pogo Pins===<br />
<br />
The PinePhone has 6 "pogo pins" on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3v power source, and an I2C interface.<br />
<br />
'''A step/stl/stp (3D model) file for the back cover is [http://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp freely available] for creating custom cases that interface with the pogo pins.'''<br />
<br />
=== Serial console ===<br />
[[File:Uart pinephone connection.gif|250px|thumb|left|UART serial connector for PineBook and PinePhone]]<br />
The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is on then the headphone connector is in audio mode, if it's off then it's in UART mode. This uart serial connection can also be used for communication with other devices from the PinePhone.<br />
<br />
The uart is 115200n8<br />
<br />
The pinout for the serial connector on the tablet side is:<br />
<br />
* Tip: RX<br />
* Ring: TX<br />
* Sleeve: GND<br />
<br />
The serial connection is 3.3V<br />
<br />
You can also buy the debug cable from [https://store.pine64.org PINE64 Store]<br />
The store cable uses a 4 ring plug, as seen in the [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf PDF], but a 3 ring plug works just as well. That cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Killswitch configuration ==<br />
<br />
The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their on position is toward the top of the phone.<br />
<br />
[[File:PinePhone switches.jpeg|600px|thumb|left|Photo of Brave Heart switches from OSAKANA TARO on Twitter]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
# Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.<br />
# WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.<br />
# Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.<br />
# Rear camera: On enables the rear camera, off disables.<br />
# Front camera: On enables the front camera, off disables.<br />
# Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Battery ==<br />
<br />
The [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf supplied battery] is [https://forum.pine64.org/showthread.php?tid=8120&pid=53307#pid53307 meant to be] compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. There is [https://forum.pine64.org/showthread.php?tid=8563&pid=55053#pid55053 a report] that the EB-BJ700CBE isn't quite the same size, causing the back not to fit properly.<br />
<br />
The battery terminals, in order from nearest the edge to nearest the middle, are:<br />
<br />
# +ve<br />
# thermistor<br />
# -ve<br />
# not connected<br />
<br />
The battery includes a protection circuit that isolates it in a number of fault conditions, including if it is discharged too far. The fully discharged battery [https://forum.pine64.org/showthread.php?tid=8563&pid=55377#pid55377 can be recharged] by connecting the phone to a charger. Once it has charged sufficiently you will be able to boot the phone.<br />
<br />
If your battery is hard to remove from the phone, try loosening the screws around it. Possibly cutting up a piece of plastic and sliding it under the battery as a pull tab can work too.<br />
<br />
'''Your Brave Heart phone ships with a plastic sticker between the battery and the phone. You need to open the back cover (gently), then remove the battery and finally remove the sticker. This is to protect the device from turning on during shipping.<br />
<br />
[[File:PinePhone battery1.png|600px|thumb|centre|Photo of Brave Heart case from OSAKANA TARO on Twitter]]<br />
[[File:PinePhone battery3.jpeg|600px|thumb|centre|Photo of Brave Heart battery sticker from OSAKANA TARO on Twitter]]<br />
<br />
There has been [https://forum.pine64.org/showthread.php?tid=8960 a report on the forum] that this sticker can bend the pins that make connection between the battery and the phone: please check your setup carefully after removing the sticker.<br />
<br />
'''Note''': the EG25 modem and RTL8723CS wifi/bluetooth do not work without battery power, even if you are supplying enough power to the Pinephone with USB-C.<br />
<br />
== Modem and Carrier Support ==<br />
There is a document about using the modem by user ''megi'' [https://megous.com/dl/tmp/modem.txt here.] This is from circa 18 Jan 2020. <br />
<br />
Note at this date there is no TL;DR version - the script at the end to disable the modem before power off is pretty essential to avoid corrupting your modem's flash memory.<br />
<br />
<br />
To check if the PinePhone is supported on your carrier: <br />
<br />
Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed under the [[#Specifications|specifications]] section).<br />
<br />
It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.<br />
<br />
== Factory Test Requirements ==<br />
<br />
Most of the self tests should just work, but a couple of them will fail unless certain requirements are met.<br />
<br />
=== RTL8723CS - WiFi ===<br />
<br />
* The self test needs a visible access point nearby so it can discover an SSID.<br />
* The self test may fail if the battery charge is too low. <br />
<br />
=== EG25 - Modem ===<br />
<br />
* A working micro-SIM that doesn't require a PIN to unlock<br />
* Enough battery charge<br />
<br />
== Operating Systems ==<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for <br />
<br />
The [[PinePhone Software Release#Software_Releases|'PinePhone Software Releases']] page has a complete list of currently supported Operating System images that work with the PinePhone as well as other related software information. <br />
<br />
The list includes OS images and descriptions of:<br />
<br />
[{{fullurl:PinePhone_Software_Release#postmarketOS}} http://files.pine64.org/sw/pine64_installer/json/postmarketos.png] [[PinePhone_Software_Release#postmarketOS|'''postmarketOS''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#Ubuntu_Touch_by_UBPorts}} http://files.pine64.org/sw/pine64_installer/json/ubports.png] [[PinePhone_Software_Release#Ubuntu_Touch_by_UBPorts|'''Ubuntu Touch by UBPorts''']]<br />
<br />
[[File:Ryodebianphosh.png]] [[PinePhone_Software_Release#Debian_.2B_Phosh|'''Debian + Phosh''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#Maemo_Leste}} http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png] [[PinePhone_Software_Release#Maemo_Leste|'''Maemo Leste''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#SailfishOS}} http://files.pine64.org/sw/pine64_installer/json/sailfishos.png] [[PinePhone_Software_Release#SailfishOS|'''SailfishOS''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/manjaro.png] [[PinePhone_Software_Release#Manjaro_ARM|'''Manjaro ARM''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#NixOS}} http://files.pine64.org/sw/pine64_installer/json/nixos.png] [[PinePhone_Software_Release#NixOS|'''NixOS''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#LuneOS}} http://files.pine64.org/sw/pine64_installer/json/luneos.jpg] [[PinePhone_Software_Release#LuneOS|'''LuneOS''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#Nemo_Mobile}} http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png] [[PinePhone_Software_Release#Nemo_Mobile|'''Nemo Mobile''']]<br />
<br />
[{{fullurl:PinePhone_Software_Release#KDE_Neon}} http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png] [[PinePhone_Software_Release#KDE_Neon|'''KDE Neon''']]<br />
<br />
[[File:Auroraos.jpeg]] [[PinePhone_Software_Release#Aurora|'''Aurora''']]</div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5267PinePhone Software Releases2020-03-05T21:43:21Z<p>Dukla2000: /* PureOS */ add userID/password</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
You may also need to expand the flashed image to fill your SD card. To do so after you've booted the device, install growpart and resize2fs on the phone and then run...<br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
... where X and Y correspond to your SD card's identifier (viewable from lsblk).<br />
<br />
== Installation to eMMC ==<br />
* Prepare a new SD card as above<br />
* Boot the phone<br />
* The eMMC appears as /dev/mmcblk2 and so any standard Linux mechanism to move your image there will work, e.g. dd.<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is currently the only OS that initially uses automatic backlight control. This makes the screen to appear blank. When shining a bright light on the screen, you can still navigate the screen. (and maybe the screen switches on temporarily due to the light sensor) This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Ryodebianphosh.png]]<br />
<br />
A Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
The UI works fine, as well as Wifi, mobile data and text messaging.<br />
Voice calls, however, don't work for now, as is the case for bluetooth and the camera.<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for more details.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://www.mozzwald.com/pp/pureos-pinephone-20200226.img.xz here.] Instructions to create your own image are [http://www.mozzwald.com/pp/pureos-pinephone-build-instructions.txt here.]<br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5266PinePhone Software Releases2020-03-05T21:40:39Z<p>Dukla2000: /* Aurora */ add PureOS</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
You may also need to expand the flashed image to fill your SD card. To do so after you've booted the device, install growpart and resize2fs on the phone and then run...<br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
... where X and Y correspond to your SD card's identifier (viewable from lsblk).<br />
<br />
== Installation to eMMC ==<br />
* Prepare a new SD card as above<br />
* Boot the phone<br />
* The eMMC appears as /dev/mmcblk2 and so any standard Linux mechanism to move your image there will work, e.g. dd.<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is currently the only OS that initially uses automatic backlight control. This makes the screen to appear blank. When shining a bright light on the screen, you can still navigate the screen. (and maybe the screen switches on temporarily due to the light sensor) This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Ryodebianphosh.png]]<br />
<br />
A Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
The UI works fine, as well as Wifi, mobile data and text messaging.<br />
Voice calls, however, don't work for now, as is the case for bluetooth and the camera.<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for more details.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism, this is an unofficial/unsupported creation by ''mozzwald'' that can be downloaded [http://www.mozzwald.com/pp/pureos-pinephone-20200226.img.xz here.] Instructions to create your own image are [http://www.mozzwald.com/pp/pureos-pinephone-build-instructions.txt here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000https://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5264PinePhone Software Releases2020-03-04T20:42:50Z<p>Dukla2000: /* postmarketOS */ update firefox hint</p>
<hr />
<div><br />
This page is intended to help you install a software release on your PinePhone. In addition it provides details of all the available releases so that you can do some background reading about them to help inform your choice. Finally it provides a number of links to other resources related to your PinePhone. <br />
<br />
= General instructions =<br />
<br />
Initial (new) release installation should be to a micro SD card. It is recommended to choose a card with fast I/O of small files for best performance of your PinePhone. See [[#Other Resources]] for tests on SDcards.<br />
<br />
Generic installation instructions are in this section, please see the releases below for specific installation options they may offer/require.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
User ''megi'' has demonstrated his multi-boot development [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube,] see Other Resouces at the bottom of this page for a link to his notes.<br />
<br />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards]] then return to this page.<br />
<br />
You may also need to expand the flashed image to fill your SD card. To do so after you've booted the device, install growpart and resize2fs on the phone and then run...<br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
... where X and Y correspond to your SD card's identifier (viewable from lsblk).<br />
<br />
== Installation to eMMC ==<br />
* Prepare a new SD card as above<br />
* Boot the phone<br />
* The eMMC appears as /dev/mmcblk2 and so any standard Linux mechanism to move your image there will work, e.g. dd.<br />
<br />
== Backlight ==<br />
All current distributions do not have a good setup for the backlight at low brightness.<br />
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.<br />
<br />
Sailfish is currently the only OS that initially uses automatic backlight control. This makes the screen to appear blank. When shining a bright light on the screen, you can still navigate the screen. (and maybe the screen switches on temporarily due to the light sensor) This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image [https://wiki.postmarketos.org/wiki/Installation_guide postmarketOS recommend] the use of their script, pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: currently some lock screens require your password, but only present a numeric keyboard. So you should use [[only]] numbers in your password until you've verified you can unlock with other characters.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBPorts ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 5 Feb 2020) [https://youtu.be/ST_BjKicTAk demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' user-id/password '''<br />
The default password is <code>phablet</code><br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
To get the modem to work (as at 10 Feb) you need to manually:<br />
sudo /usr/share/ofono/scripts/enable-modem<br />
sudo /usr/share/ofono/scripts/online-modem<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian + Phosh ==<br />
[[File:Ryodebianphosh.png]]<br />
<br />
A Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server Xorg]). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, Wifi chip firmware) being built from modified sources (as well as the kernel and u-boot, of course). Current version is Debian Sid, as needed packages are not yet in testing (Debian Bullseye). <br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone image builds]<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
The UI works fine, as well as Wifi, mobile data and text messaging.<br />
Voice calls, however, don't work for now, as is the case for bluetooth and the camera.<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for more details.<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.]<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
* ''' Download location '''<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds.] There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]<br />
<br />
* ''' Development '''<br />
Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available. <br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card. '''Note:''' The script will format and erase the SD card!<br />
<br />
''Instructions:''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
Note that after baking µSD card and booting phone, as per [https://www.reddit.com/r/pinephone/comments/f1l7bm/sailfish_os_on_pinephone_best_os_so_far_in_my/fh8o0s2/ Reddit comment] you have to adjust autobrightness settings in order to actually see interface.<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
The current (6 Feb) version of Sailfish has a defect with the auto brightness: on first boot this means you get a blank screen. You need to hold your phone up to a bright light to enable the screen, then disable the auto brightness in Settings, Display. [https://forum.pine64.org/showthread.php?tid=9054 See this forum thread.] If you're not familiar with SFOS, be prepared by having a Jolla account and skip the tutorial by touching all 4 corners starting top left. This is just because holding a light over the sensor can be tricky, otherwise the SFOS tutorial is necessary as the UI is not that intuitive. <br />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
* ''' Download location '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro forum announcement of Alpha4 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha4-for-pinephone-and-pinetab/127684 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
* ''' Download location '''<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
See [https://nixos.org/nixos/community.html Bugs section on this page.]<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9043 this forum thread] for how to get going.<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.]<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here.]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://store.pine64.org/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on linux distributions and desktop environments on mobile devices.]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>Dukla2000