PINE64 - User contributions [en]

Main Page

2024-11-20T12:50:51Z

Fxc: Changed protection settings for "Main Page": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the [[PINE64 brand and logo|article about our brand and logo]].

== Devices ==

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Phone accessories: '''[[PinePhone (Pro) Add-ons]]''' and '''[[PinePhone (Pro) Keyboard]]'''
* Tablets: '''[[PineTab]]''', '''[[PineTab2]]''', '''[[PineTab-V]]''' and '''[[PineNote]]'''
* Wearable: '''[[PineBuds Pro]]''', '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''' and '''[[Pinebook Pro]]'''
* Laptop accessories: '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Oz64]]''','''[[Ox64]]''', '''[[STAR64]]''', '''[[Quartz64]]''', '''[[QuartzPro64_Development|QuartzPro64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS]]''', '''[[PINE H64 Model A]]''' and '''[[PINE H64|PINE H64 Model B]]'''
* Set-top box: '''[[RockBox]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPINE]]''', '''[[SOPINE Baseboard]]''', '''[[SOEDGE]]''', '''[[SOEDGE Baseboard]]''', and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Power adapter: '''[[PinePower]]'''
* Soldering iron: '''[[Pinecil]]'''
* Makerspace: '''[[PineCone]]''' and '''[[Pinedio]]'''

== Community and Support ==

Community collaboration and support is focused around the chat platforms and forums described below. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

=== Chat Platforms ===

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

{{hint|PINE64 community is not some always-responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently. More precisely:
* The activity of community members varies depending on the time of day and the number of active users.
* Whether your questions will be answered and whether the answers are right and definitive, depends on the information you provide, the difficulty of your questions, the current state of the involved PINE64 products and their software support, and the community members' ability.
* Read [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] to learn more.
* Please read [[PINE64 Community Rules and Code of Conduct]].

'''Note:'''
* PINE64 uses a bridge bot (''[https://github.com/42wim/matterbridge matterbridge]'' with some modifications) that allows Discord, IRC, Matrix, and Telegram users to see each other and participate together in the community chat.
* The bot name is "Pine64 Protocol Droid" or "P64ProtocolBot", depending on the chat platform, and if you see this, look in the message to see the actual author of the message.
* When the bot relays messages, it will show the chat platform the user is using by prefixing their nickname with "[D]" for Discord, "[I]" for IRC, "[M]" for Matrix, and "[T]" for Telegram.
}}

The community chat platforms are the following:

* '''Discord''': Use this '''[https://discord.gg/pine64 invite link]'''. All PINE64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below.
* '''IRC''': The server is '''irc.pine64.org''', and the ports are '''6667''' (plain) and '''6697''' (TLS). Use <code>/LIST</code> command or the table below to see the full list of channels. This server experienced abuse by spam bots in early October 2023, which resulted in requiring registration and authentication with <code>NickServ</code> before users could join channels between October 3, 2023 and October 11, 2023. Using <code>NickServ</code> to join channels has become required again on October 23, 2023, due to the server experiencing repeated abuse by spam bots.
* '''Matrix and Telegram''': See the table below.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://matrix.to/#/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://matrix.to/#/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://matrix.to/#/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://matrix.to/#/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://matrix.to/#/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://matrix.to/#/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz-dev
|-
| Star64
| [https://matrix.to/#/#star64:matrix.org #star64:matrix.org]
| [https://t.me/star64_sbc @star64-sbc]
| Unavailable
|-
| Pinebook and Pinebook Pro
| [https://matrix.to/#/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://matrix.to/#/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://matrix.to/#/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://matrix.to/#/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://matrix.to/#/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://matrix.to/#/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| PineBuds Pro
| [https://matrix.to/#/#pinebuds:matrix.org #pinebuds:matrix.org]
| [https://t.me/+nJVhM0mZ9KhlYmZl @pinebuds]
| Unavailable
|-
| Pinecil
| [https://matrix.to/#/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinecil Development
| [https://matrix.to/#/#pinecil-dev:matrix.org #pinecil-dev:matrix.org]
| [https://t.me/+8_pdKqXrVuQ4OTk1 Pinecil-dev]
| Unavailable
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| PineCube
| [https://matrix.to/#/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker, Ox64, Oz64
| [https://matrix.to/#/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://matrix.to/#/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://matrix.to/#/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #offtopic
|}

There is also an unofficial Matrix Space at [https://matrix.to/#/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.

=== Forums ===

PINE64 runs an official forum powered by the open-source forum server software ''MyBB''. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

== Helpful Information for Beginners ==

* '''[[Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[How to Contribute]]''': Information about how to contribute to different partner projects
* '''[[Where to Report Bugs]]''': Information about how to report bugs
* '''[[Project]]''': A variety of well documented PINE64 projects to serve as inspiration

Main Page

2024-11-20T12:48:17Z

Fxc: Reverted edits by Archibald (talk) to last revision by Tllim

PinePhone Pro

2024-09-24T18:47:26Z

Fxc: Undo revision 21552 by JohnA (talk), I don't agree with these contents, the style is to be optimized and potentially causes more confusion than helping. No or a broken installation is one cause.

[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]

The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

The PinePhone Pro is PINE64’s second smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a open system stack. Achieving this goal will, however, take time as the software and overall smartphone software ecosystem needs to mature.

=== State of the software ===
([[PinePhone Pro Software State|view separately]])

{{:PinePhone Pro Software State}}

=== Editions and revisions ===
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.

* [[PinePhone Pro Developer Edition]]
* PinePhone Pro Explorer Edition

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this Wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time setup ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Devices shipped after the end of July 2022 do only accept a nano-SIM, the SIM is inserted into a carriage released by slightly pulling on the handle in the lower slot (for information regarding devices shipped prior to end of July 2022 see below).

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the SIM card in the lower slot.]]

{{Info|Information regarding devices shipped prior to end of July 2022: The PinePhone Pros shipped prior to the end of July 2022 come with a micro-SIM slot instead of a nano-SIM slot. Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

== Software ==

The software section explains how to install the available software releases for the PinePhone Pro to the internal eMMC or a microSD card, how to boot them and how to solve common booting issues.

=== Software releases ===

The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.

{{Info|Images of the regular PinePhone are not compatible with the PinePhone Pro.}}

=== Boot order ===

The RK3399S processor in the PinePhone Pro searches for the bootloader (such as ''U-Boot'' or ''Tow-Boot'') in the following order:

# SPI flash
# eMMC (the internal memory)
# MicroSD card

==== Boot from microSD card temporarily ====

To temporarily boot from an inserted '''microSD card''' do the following:

* On the '''Explorer Edition ordered after November 2023''' the microSD card is first in boot order due to using ''rk2aw'' instead of ''Tow-Boot'', see [https://xnux.eu/rk2aw/ here].

* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while powering on the device. The batches bought after July 2022 come with ''Tow-Boot'' flashed to the SPI, which offers additional functionality over ''U-Boot'' as bootloader.

* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the cover for a few seconds, while powering on the device. If the button is labeled ''RESET'' instead of ''RE'' please verify if the device is a regular [[PinePhone]] (or the Developer Edition). This is required because older batches don't ship with ''Tow-Boot'' on the SPI. Flashing ''Tow-Boot'' can be caught up by following [https://tow-boot.org/devices/pine64-pinephonePro.html this] instruction. Note: If ''Tow-Boot'' is flashed later, the microSD card can be selected at boot with the volume down key as well.

* On the '''Developer Edition (sold to selected developers only)''' the SPI and the eMMC can be bypassed by shorting the bypass test points while booting. The process is explained in the article [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation|PinePhone Pro Developer Edition]]. Please join the community chat for any questions regarding the process.

The RE button disables the SPI and the eMMC at the hardware level while the button is held and the PinePhone Pro will try to boot from the next available boot medium, which is the microSD card. Note: When holding the ''RE'' button (or when shorting the contact points in case of the ''Developer Edition'') for a longer time at boot the operating system will not initialize the SPI and eMMC and it will not be possible to write to these storage mediums until the next reboot.

{{Template:Info|The bootloader uses its own boot order for loading the kernel and other core operating system components at boot, which for example may result in the boot loader residing on the eMMC loading and booting the kernel from a microSD card.}}

==== Boot from microSD card permanently ====

The bootloader (such as ''U-Boot'') resides in the free space in front of the first partition. Wiping the bootloader from the eMMC to make the PinePhone Pro boot from microSD card can be done using <code>sudo dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=400 conv=fsync</code>. Formatting the drive or deleting the partition table is not sufficient to wipe the bootloader.

==== Notes ====

If you received your device after July of 2022, the bootloader resides on the SPI.

See [[RK3399 boot sequence]] for further details regarding the boot sequence.

=== Installation instructions ===

The software releases can be installed (the process is being referred to as ''flashing'') to the eMMC or to an microSD card.

==== Flashing to microSD card ====
To install an image to the microSD card:

# Download a compatible image from [[PinePhone Pro Software Releases]].
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Write the image to your microSD card using your favorite method, examples:
#* Using ''dd'': On the device you're flashing the microSD card from, find the correct device under <code>lsblk</code> and then flash the image to the microSD card using <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>. Make sure the target is the whole microSD card and not its first partition (''sdc1'' or ''mmcblk0p1'' are wrong!).
#* Using ''bmaptool'': Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device: Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 GB file.
#* Using ''a graphical tool'': A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
# Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore, see [[:File:Pinephone_slots.png|here]].
# Boot the device using the following method:
#* On the '''Explorer Edition ordered after November 2023''' boot the phone without any further action.
#* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while booting.
#* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the back cover while booting (or use the ''volume down key'' if you flashed ''Tow-Boot'').
#* On the '''Developer Edition (sold to selected developers only)''' apply the bypass by shorting the testing pads while booting according to the datasheet (or use the ''volume down key'' if you flashed ''Tow-Boot'').

Details regarding the boot order can be found in the [[PinePhone Pro#Boot order|Boot order]] section.

==== Flashing to the eMMC ====
Flashing to the eMMC (the internal memory of the PinePhone Pro) can either be done using ''Tow-Boot'''s USB Mass Storage mode (see [[#Boot order]] if you are unsure if the device comes with Tow-Bot pre-installed) or by booting an operating system from the microSD card (see the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]) and by writing to the eMMC directly from there:

By using Tow-Boot:

# Power off the device
# Power on the device and hold the ''volume up'' key before and during the second vibration
# The LED will turn blue if done successfully. This will only work if Tow-Boot is installed
# When connecting the device to a computer via USB it will behave like an USB drive now
# Check if the eMMC appears under <code>lsblk</code>, the output might look like the following:
#: '''''mmcblk2''' 179:0 0 115.2G 0 disk''
#: ''├─mmcblk2p1 179:1 0 122M 0 part /boot''
#: ''└─mmcblk2p2 179:2 0 115.1G 0 part /''
#: {{Info|In this example, '''/dev/mmcblk2''' is the device, while ''mmcblk2p1'' and ''mmcblk2p2'' are partitions of the device. The downloaded images are images from full devices, which means that the full device (''mmcblk2'' in this example) needs to be flashed. Ignore the partitions!}}
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/'''DEVICE''' bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'' and replace ''DEVICE'' with the correct device from the ''lsblk'' command)
# Reboot the PinePhone Pro

By booting a microSD card:

# Boot an operating system [[PinePhone Pro#Flashing to microSD card|from the microSD card]]. If there is already a bootloader on the eMMC installed see the section [[PinePhone Pro#Boot order|Boot order]] to bypass it.
# Download or copy the desired image to the microSD card as file
# Check if the eMMC appears under <code>lsblk</code>. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/mmcblk2 bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'').
# Reboot the PinePhone Pro

=== Troubleshooting ===

If the PinePhone Pro is not booting (either booting incompletely into a boot splash or tty or if the PinePhone Pro is showing no signs of life) this will typically have the following two reasons:

==== The battery is fully drained ====

If the battery is drained then the board can reset during boot causing a boot loop because of undervoltage condition. It can happen on all stages of the boot including ''U-Boot'' bootloader, display initialization and USB (re-)configuration. In that case it is not possible to charge the phone. The battery can be charged by interrupting the boot loop by booting the PinePhone Pro into ''Maskrom mode'' or by charging the battery externally. It is possible to follow these instructions without a computer by using a wall charger, however it would not be possible to determine if Maskrom mode was started successfully. To boot the PinePhone Pro into ''Maskrom mode'':

* Remove any microSD card from the phone and keep it removed for the below procedure
* Remove the battery, any USB cable and any serial cable
* Reinsert the battery
* Hold the ''RE'' button underneath the back cover of your ''Explorer Edition'' (or short the bypass contact points on the ''Developer Edition'')
{{Info|Confirm that the label of the button says ''RE'' and not ''RESET''! If the button label says ''RESET'' instead you probably have a regular PinePhone and you're reading the wrong page.}}
* Connect the phone to an USB port of a computer, while still holding the button for some time
* Confirm if the phone was booted in Maskrom mode:
** On ''Linux'' check if the Maskrom mode appears as device in the output of the terminal command <code>lsusb</code> on the computer, the expected ''VID:PID'' of the device is ''2207:330c''.
** On ''Windows'' this can be checked using the ''Device Manager'' and checking the VID "2207" and PID "330c" of an ''Unknown device'' appears.
** On ''macOS'' this can be checked in ''/Applications/Utilities/System Information.app'' under ''USB'' and by checking if the VID "2207" and PID "330c" is appearing for a ''Composite Device''.
* Let the phone charge for multiple hours

{{Info|If the device doesn't appear under ''lsusb'' please try again with a different known good USB-C cable and make sure that there is no microSD card in the phone inserted.}}

The device should now be able to boot from the boot medium again. If that is not the case the installation got corrupted, as explained below.

==== The installation is corrupted ====
The PinePhone Pro won't be able to boot if the installation on the SPI flash, the eMMC or the microSD card got corrupted. To boot a working operating system:

* Prepare a microSD card as explained in the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]
* Remove any USB-C cable or device or add-on case from the PinePhone Pro
* Make sure the device is powered off by shortly removing the battery for a second
* Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore.
* Power on the device (bypassing the SPI and eMMC might be required, see [[PinePhone Pro#Boot order|Boot order]])

The device should now boot from the microSD card. If the phone does not boot from the microSD card the microSD card was flashed with an incompatible image or the battery got drained as explained above.

=== Bootloaders ===
The following section contains notes regarding compatible bootloaders with the PinePhone Pro.

==== U-Boot ====
The pre-installed operating system on the PinePhone Pro Explorer Edition, if sold prior to the end of July of 2022, is using [[U-Boot]] as default bootloader. Batches sold after July of 2022 are using ''Tow-Boot''

==== Tow-Boot ====
Current batches of the PinePhone Pro ship with ''Tow-Boot'' pre-installed to the SPI flash, which is an opinionated distribution of ''U-Boot'' and brings numerous advantages over stock ''U-Boot'', such as the possibility to choose from booting the eMMC or microSD card using the volume buttons during boot, as well as a ''USB Mass Storage mode'', where the device can be written to by connecting the device to a computer via USB.

The user can flash Tow-Boot to the PinePhone Pro using the [https://tow-boot.org/devices/pine64-pinephonePro.html instructions on the Tow-Boot website].

==== levinboot ====
The levinboot bootloader is another option for the PinePhone Pro. The project repository can be found [https://gitlab.com/DeltaGem/levinboot/-/tree/master/ here]. (Pinephone Pro supporting fork is [https://xff.cz/git/levinboot/ here].)

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

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.

{| class="wikitable"
|-
! Number
! Name
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART¹ mode.
|}

¹ Note: The baud rate may be 1500000 instead of 115200.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

''atinout'' example:

echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -

''minicom'' example:

minicom -D /dev/ttyUSB2

=== VoLTE ===

The PinePhone and PinePhone Pro modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

AT+QMBNCFG="select","ROW_Generic_3GPP"

Then enable Voice over LTE using:

AT+QCFG="ims",1

And reboot the modem to apply the settings:

AT+CFUN=1,1

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to power off the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone Pro. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone and PinePhone Pro modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===

The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the documentation section.

As with most smartphones, the PinePhone Pro has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone Pro may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Nano-SIM (Micro-SIM before 07/2022)
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''NOR Flash:''' Listed as [GigaDevices] GD25LQ128EWIGR, but physical inspection found a SiliconKaiser SK25LP128.
* '''Back Camera:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' Wi-Fi 802.11AC, hotspot capable + Bluetooth V5.0
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery; unglue bottom black plastic with your nail from Samsung battery before installation in order to match the dimensions)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Modifications and repairs ==

Most parts are available from the [https://pine64.com/product-category/pinephonepro-spare-parts/ Pine store]. Take care to use this link to avoid unintentionally ordering parts for the original PinePhone instead.

=== Replacing the mainboard ===

The mainboard can be replaced if it is faulty. The replacement board does not have an operating system pre-installed, to test if everything is working after swapping the mainboard a flashed SD card is required.

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an operating system from a microSD card.}}

Prior to replacing your PinePhone Pro’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the mainboard.
# Remove the phone's back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone, including the screw under the warranty sticker.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio and UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam for the regular PinePhone can be found [https://www.youtube.com/watch?v=5GbMoZ_zuZs here] or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here].

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Replacing the mainboard|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.
* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.
* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.
* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a silver-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the Pine Store ===

The following parts are not available on the Pine Store for the '''regular PinePhone'''. The replacements are listed below and have not been validated for the PinePhone Pro.

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| LCD
| Himax HX8394 compatible
|-
| Rear camera
| IMX258
|-
| Front camera
| OV8858
|-
| Camera flash
| AW3641EDNR
|-
| WiFi + Bluetooth
| [https://www.azurewave.com/img/wireless-modules/AW_CM256SM_DS_Rev15_CYW.pdf AzureWave AW-CM256SM]
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| <s>3 Axis Magnetometer</s>
| <s>[https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL]</s> '''''Note:''''' The ''AF8133J'' is used instead.
|-
| Geo Magnetic Sensor
| [http://www.voltafield.com/products01.html Voltafield AF8133J]
|-
| Ambient light / Proximity
| STK3311-A
|-
| Accelerometer / Gyroscope
| [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6500/ TDK MPU-6500]
|-
| Vibration motor
|
|-
| Notification LED
| LED0603RGB
|-
| Audio Codec
| ALC5616 and ALC5640
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| [https://rockchip.fr/RK818%20datasheet%20V1.0.pdf RK818]
|}

== Datasheets, schematics and certifications ==

PinePhone Pro mainboard schematic:
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf PinePhone Pro mainboard Explorer Edition Released Schematic ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-top.pdf PinePhone Pro mainboard Explorer Edition component top placement ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-bottom.pdf PinePhone Pro mainboard Explorer Edition component bottom placement ver 1.0 20211127]

PinePhone Pro USB-C small board schematic:
* TBD

Certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20FCC%20Certificate-S21101902805001.pdf PinePhone Pro FCC Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20SAR%20Evaluation%20Report-S21101902806001.pdf PinePhone Pro SAR Evaluation Report]
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20CE%20RED%20Certificate-S21101902802-R1.pdf PinePhone Pro CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20RoHS%20Test%20Report.pdf PinePhone Pro ROHS Test Report]

== Factory Test Build for Hardware Checking ==
[[File:PPP_Abdroid_Test_Utility-5.jpg|400px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by the support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, take out the PinePhone Pro Explorer Edition, then insert it into microSD slot (upper slot).
* Insert battery, press the RE button (bypass SPI and eMMC boot) underneath the back cover while plugging in the USB-C power. After 3 seconds release the RE button.
* When powering up, a battery icon screen will show up blow, press power key for two seconds, then the Rockchip logo screen shows up.


* Wait for the home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that the SD test is disabled due in this is SD boot build.
* After running a particular test function, please snapshot the test result and pass it back to support team

Notes:
* Please insert a functional SIM card when performing the SIM test
* When perform GPS test, the first result may fail and please ignore this false message.
* For light sensing test, please have a light shine to the PinePhone Pro when performing the test.


== Using Factory Test Build for Battery charging ==
[[File:PPP_Abdroid_Test_Utility-1.jpg|300px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and battery will start charging.
* The battery icon display for few seconds and then LCD panel turn off while charging. To check charging status, just quick press power button (about 0.5 second) and battery icon will display progress.

== Press ==

For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Press]].

== External links ==
* [https://www.pine64.org/pinephonepro/ Product Page]
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement

[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]

PinePower

2024-06-26T16:27:15Z

Fxc: Readded text

[[File:PinePower_Charger_65W.jpeg|400px|thumb|right|PinePower 65W render]]

The '''PinePower''' devices (the ''PinePower'' and the ''PinePower Desktop'') are power supplies, which pack plenty of power. They capable of powering or charging multiple PINE64 devices, such as the Pinebook Pro, PinePhone and the PineTime simultaneously.

== PinePower 65W GaN Charger ==
The PinePower is a small and compact palm size 65W wall socket power adapter. It features 2 USB-C ports and 1 USB-A port charger. [https://en.wikipedia.org/wiki/Gallium_nitride Gallium Nitride] technology ensures a small and light charger with high charging efficiency. It has a retractable US plug.

=== General specifications ===
Body:

* Dimensions: 74.8mm x 36.6mm x 32mm
* Weight: 130 grams
* Build: Plastic
* Color: Black

Power:

* Input: AC 100-240V 50/60Hz 1.5A Max
* Output: 65W
* Power switch

Connections:

* 240Vac input US plug, adapters for AU, EU, and UK,
* 1x USB-A
* 2x USB-C

=== Power specifications ===
{| class="wikitable"
! Output
! Max output power
! Power ranges PD
! Power ranges QC
! Power ranges PPS
|-
| Single USB-C1 or C2
| 65W
| 5V3A, 9V3A, 12V3A, 15V3A, 20V3.5A
| -
| 3.3-11V5A
|-
| Single USB-A
| 65W
| -
| QC3.0 4.5V5A, 5V4.5A, 9V3A, 12V3A, 20V3A
| -
|-
|USB-C1 &
USB-C2 combined
|
*45W
*18W
|
*5V3A, 9V3A, 12V3A, 15V3A
*5V3A, 9V2A, 12V1.5A
| -
| -
|-
| USB-C1 &
USB-A combined
|
*45W
*18W
|
*5V3A, 9V3A, 12V3A, 15V3A
*-
|
*-
*5V3A, 9V2A, 12V1.5A
| -
|-
|USB-C1 &
USB-C2 + USB-A combined
|
*45W
*15W
|
*5V3A, 9V3A, 12V3A, 15V3A
*5V3A
| -
| -
|}

=== Certifications ===
* [https://files.pine64.org/doc/cert/65W%20PinePower%20FCC-SDO%20Certificate-LCSA110222005E.pdf 65W PinePower GaN Charger FCC Certificate]
* [https://files.pine64.org/doc/cert/65W%20PinePower%20GaN%20Charger%20CE%20EMC%20Certificate-LCSA110222003E.pdf 65W PinePower GaN Charger CE EMC Certificate]
* [https://files.pine64.org/doc/cert/65W%20PinePower%20GaN%20Charger%20CE%20LVD%20Certificate-LCSA110222004S.pdf 65W PinePower GaN Charger CE LVD Certificate]

=== Internals ===
''TBA''

== PinePower 120W Desktop Power Supply ==
[[File:PinePower-Desktop-2.jpg|400px|thumb|right|PinePower Desktop 120W render]]

A 120W desktop power adapter. It features 1 USB-C port and 4 USB-A port. The 120W output is not per port, but total output power. This is calculated by combining the 65W USB-C, 3x15W USB-A and the 18W USB-A QC, making a total of 128W. The only difference between the US and EU edition is the supplied power cable. Every port, with exception of the wireless Q-charger, has a display, portraying the output voltage and amps. The display back light can be turned on and off by capacitive touch button, located on the top left side of the unit.

=== General specifications ===

Body:

* Dimensions: 123mm x 115mm x 48mm
* Weight: 543 grams
* Build: Plastic
* Color: Black

Display:

* Individual port voltage status display
* Individual port current status display

Controls:

* Mains power toggle switch
* Capacitive power output display switch

Power:

* Input: AC 100-240V 50/60Hz ?A Max
* Output: 120w

Connections:

* 110/240VAC input (either US/EU/UK figure of 8 plug is supplied)
* 4x USB-A
* 1x USB-C

=== Power specifications ===

{| class="wikitable"
! Output
! Protocol
! Version
! Max output power
! Power ranges
|-
| USB-C
| [https://en.wikipedia.org/wiki/USB_hardware#USB_Power_Delivery_(USB_PD) PD]
| ?
| 65W
| 5V3A, 9V3A, 12V3A, 15V3A, 20V3.25A
|-
| USB-A
| [https://en.wikipedia.org/wiki/Quick_Charge QC]
| 3.1
| 18W
| 5V3A, 9V2A, 12V1.5A
|-
| USB-A
| USB
| ?
| 15W
| 5V3A
|-
| Wireless charger
| [https://en.wikipedia.org/wiki/Qi_(standard) Qi]
| 1.2
| 10W
| -
|}

=== Certifications ===
* [https://files.pine64.org/doc/cert/120W%20Desktop%20PinePower%20FCC%20Certificate-DL-20221129012C.pdf 120W PinePower Desktop Power Supply FCC Certificate]
* [https://files.pine64.org/doc/cert/120W%20Desktop%20PinePower%20CE%20EMC%20Certificate-DL-20221129011C.pdf 120W PinePower Desktop Power Supply CE EMC Certificate]

=== Internals ===

The power unit is not made to be disassembled, do so at your own risk. The front plate is secured with 4 tabs, that can be disengaged with a screwdriver. The complete assembly can be slid out, but do mind the same tab in the casing. The power button at the back of the case has a plug that can be disconnected from the main PCB. The wireless charging PCB has to be de-soldered, or forcefully removed from the inner casing, as it is glued to the top of the case.

<gallery mode="packed-hover" heights="180">
File:PinPower-Desktop-front-plate-removal.jpg | (Removal of the front plate)
File:PinPower-Desktop-Display-front.jpg | (Front view display PCB)
File:PinPower-Desktop-Display-back.jpg | (Back side display PCB)
File:PinPower-Desktop-PCB-top.jpg | (Top side main PCB)
File:PinPower-Desktop-PCB-bottom.jpg | (Bottom view main PCB)
File:PinPower-Desktop-wireless-charger.jpg | (Wireless charger)
</gallery>

Some remarks:

* This main PCB is marked as XR SEMI v1.1
* Two unmarked packages, control the display.
* An antenna is connected on the display PCB, lining up with the 'lamp' symbol. This is the capacitive touch button to control the display back light.
* The 65W PD USB-C port is controlled by a [http://www.hynetek.com/product/pdController/HUSB339/document/HUSB339_DS_EN_V1.2.pdf HUSB339] controller, paired with a GOFORD G16 MOSFET.
* The other ports have a [http://www.lshchip.com/pdf/Deep-pool/NDP1360KC_EN_Rev1.1.pdf NDP1360KC] as final power converter.

== External links ==
* [https://www.pine64.org/2020/12/15/december-update-the-longest-one-yet/ Pine blog, containing news about the PinePower products]
* [https://pine64.com/product/pinepower-65w-gan-2c1a-charger-with-international-plugs/ PinePower 65W on the official Pine store]
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-eu-version/ PinePower 120W EU version on the official Pine store]
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower 120W US version on the official Pine store]
* [https://www.printables.com/model/923335-pinepower-120w-under-shelf-mount-and-cable-organiz 3D printed PinePower 120W Under-Shelf Mount] ([https://makerworld.com/en/models/510799 in makerworl])

[[Category:PinePower]]

PinePower

2024-06-26T16:26:27Z

Fxc: Categorization doesn't make sense

[[File:PinePower_Charger_65W.jpeg|400px|thumb|right|PinePower 65W render]]

The '''PinePower''' devices (the ''PinePower'' and the ''PinePower Desktop'') are power supplies, which pack plenty of power. They capable of powering or charging multiple PINE64 devices, such as the Pinebook Pro, PinePhone and the PineTime simultaneously.

== PinePower 65W GaN Charger ==
The PinePower is a small and compact palm size 65W wall socket power adapter. It features 2 USB-C ports and 1 USB-A port charger. [https://en.wikipedia.org/wiki/Gallium_nitride Gallium Nitride] technology ensures a small and light charger with high charging efficiency. It has a retractable US plug.

=== General specifications ===
Body:

* Dimensions: 74.8mm x 36.6mm x 32mm
* Weight: 130 grams
* Build: Plastic
* Color: Black

Power:

* Input: AC 100-240V 50/60Hz 1.5A Max
* Output: 65W
* Power switch

Connections:

* 240Vac input US plug, adapters for AU, EU, and UK,
* 1x USB-A
* 2x USB-C

=== Power specifications ===
{| class="wikitable"
! Output
! Max output power
! Power ranges PD
! Power ranges QC
! Power ranges PPS
|-
| Single USB-C1 or C2
| 65W
| 5V3A, 9V3A, 12V3A, 15V3A, 20V3.5A
| -
| 3.3-11V5A
|-
| Single USB-A
| 65W
| -
| QC3.0 4.5V5A, 5V4.5A, 9V3A, 12V3A, 20V3A
| -
|-
|USB-C1 &
USB-C2 combined
|
*45W
*18W
|
*5V3A, 9V3A, 12V3A, 15V3A
*5V3A, 9V2A, 12V1.5A
| -
| -
|-
| USB-C1 &
USB-A combined
|
*45W
*18W
|
*5V3A, 9V3A, 12V3A, 15V3A
*-
|
*-
*5V3A, 9V2A, 12V1.5A
| -
|-
|USB-C1 &
USB-C2 + USB-A combined
|
*45W
*15W
|
*5V3A, 9V3A, 12V3A, 15V3A
*5V3A
| -
| -
|}

=== Certifications ===
* [https://files.pine64.org/doc/cert/65W%20PinePower%20FCC-SDO%20Certificate-LCSA110222005E.pdf 65W PinePower GaN Charger FCC Certificate]
* [https://files.pine64.org/doc/cert/65W%20PinePower%20GaN%20Charger%20CE%20EMC%20Certificate-LCSA110222003E.pdf 65W PinePower GaN Charger CE EMC Certificate]
* [https://files.pine64.org/doc/cert/65W%20PinePower%20GaN%20Charger%20CE%20LVD%20Certificate-LCSA110222004S.pdf 65W PinePower GaN Charger CE LVD Certificate]

=== Internals ===
''TBA''

== PinePower 120W Desktop Power Supply ==
[[File:PinePower-Desktop-2.jpg|400px|thumb|right|PinePower Desktop 120W render]]

A 120W desktop power adapter. It features 1 USB-C port and 4 USB-A port. The 120W output is not per port, but total output power. This is calculated by combining the 65W USB-C, 3x15W USB-A and the 18W USB-A QC, making a total of 128W. The only difference between the US and EU edition is the supplied power cable. Every port, with exception of the wireless Q-charger, has a display, portraying the output voltage and amps. The display back light can be turned on and off by capacitive touch button, located on the top left side of the unit.

=== General specifications ===

Body:

* Dimensions: 123mm x 115mm x 48mm
* Weight: 543 grams
* Build: Plastic
* Color: Black

Display:

* Individual port voltage status display
* Individual port current status display

Controls:

* Mains power toggle switch
* Capacitive power output display switch

Power:

* Input: AC 100-240V 50/60Hz ?A Max
* Output: 120w

Connections:

* 110/240VAC input (either US/EU/UK figure of 8 plug is supplied)
* 4x USB-A
* 1x USB-C

=== Power specifications ===

{| class="wikitable"
! Output
! Protocol
! Version
! Max output power
! Power ranges
|-
| USB-C
| [https://en.wikipedia.org/wiki/USB_hardware#USB_Power_Delivery_(USB_PD) PD]
| ?
| 65W
| 5V3A, 9V3A, 12V3A, 15V3A, 20V3.25A
|-
| USB-A
| [https://en.wikipedia.org/wiki/Quick_Charge QC]
| 3.1
| 18W
| 5V3A, 9V2A, 12V1.5A
|-
| USB-A
| USB
| ?
| 15W
| 5V3A
|-
| Wireless charger
| [https://en.wikipedia.org/wiki/Qi_(standard) Qi]
| 1.2
| 10W
| -
|}

=== Certifications ===
* [https://files.pine64.org/doc/cert/120W%20Desktop%20PinePower%20FCC%20Certificate-DL-20221129012C.pdf 120W PinePower Desktop Power Supply FCC Certificate]
* [https://files.pine64.org/doc/cert/120W%20Desktop%20PinePower%20CE%20EMC%20Certificate-DL-20221129011C.pdf 120W PinePower Desktop Power Supply CE EMC Certificate]

=== Internals ===

The power unit is not made to be disassembled, do so at your own risk. The front plate is secured with 4 tabs, that can be disengaged with a screwdriver. The complete assembly can be slid out, but do mind the same tab in the casing. The power button at the back of the case has a plug that can be disconnected from the main PCB. The wireless charging PCB has to be de-soldered, or forcefully removed from the inner casing, as it is glued to the top of the case.

<gallery mode="packed-hover" heights="180">
File:PinPower-Desktop-front-plate-removal.jpg | (Removal of the front plate)
File:PinPower-Desktop-Display-front.jpg | (Front view display PCB)
File:PinPower-Desktop-Display-back.jpg | (Back side display PCB)
File:PinPower-Desktop-PCB-top.jpg | (Top side main PCB)
File:PinPower-Desktop-PCB-bottom.jpg | (Bottom view main PCB)
File:PinPower-Desktop-wireless-charger.jpg | (Wireless charger)
</gallery>

* This main PCB is marked as XR SEMI v1.1
* Two unmarked packages, control the display.
* An antenna is connected on the display PCB, lining up with the 'lamp' symbol. This is the capacitive touch button to control the display back light.
* The 65W PD USB-C port is controlled by a [http://www.hynetek.com/product/pdController/HUSB339/document/HUSB339_DS_EN_V1.2.pdf HUSB339] controller, paired with a GOFORD G16 MOSFET.
* The other ports have a [http://www.lshchip.com/pdf/Deep-pool/NDP1360KC_EN_Rev1.1.pdf NDP1360KC] as final power converter.

== External links ==
* [https://www.pine64.org/2020/12/15/december-update-the-longest-one-yet/ Pine blog, containing news about the PinePower products]
* [https://pine64.com/product/pinepower-65w-gan-2c1a-charger-with-international-plugs/ PinePower 65W on the official Pine store]
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-eu-version/ PinePower 120W EU version on the official Pine store]
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower 120W US version on the official Pine store]
* [https://www.printables.com/model/923335-pinepower-120w-under-shelf-mount-and-cable-organiz 3D printed PinePower 120W Under-Shelf Mount] ([https://makerworld.com/en/models/510799 in makerworl])

[[Category:PinePower]]

Oz64

2024-06-24T16:52:58Z

Fxc: Typo

[[File:Oz64_SBC_600x600.jpg|thumb|right|The Oz64 SBC]]
[[File:Oz64_3D_model.png|thumb|right|The Oz64 3D model]]
[[File:RISC-V.png|thumb|right]]

The '''Oz64''' is a low cost single-board computer based on the Sophgo SG2000 SoC with dual T-Head C906 64-bit RISC-V cores, an ARM Cortex A53 64-bit RISC CPU core and an 8051 8-bit core supported by 512 MB of embedded DRAM memory, with WiFi and Bluetooh radio interfaces. The Oz64 SBC comes in a model-B form-factor, has a microSD card slot, an eMMC plugin connector, an USB 2.0 Type-A host port, and many other peripheral interfaces for makers to integrate with sensors and other devices.

== Software Releases ==

=== Quick Links to the Source of OS Images Build ===

There is a community effort to bring updated kernels, peripherals and buildroot - Lots of communication happening in the #ox64-nutcracker channel.

* [https://github.com/lupyuen2/wip-nuttx/releases/download/sg2000-1/Image Nuttx Released Image] by Lup Yuen

Toolchain:

* elf_newlib_toolchain/bin/riscv64-unknown-elf-gcc (Xuantie-900 elf newlib gcc Toolchain V2.2.5 B-20220323) 10.2.0
* linux_toolchain/bin/riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.2.4 B-20211227) 10.2.0
* cmake version 3.19.3

=== Software Development Kits ===
* [https://github.com/sophgo/tdl_models SG200x NPU TDL SDK]
* [https://github.com/Fishwaldo/sophgo-sg200x-debian/releases Fishwaldo SG200x Debian]
* [https://github.com/lupyuen/nuttx-sg2000 Lup Yuen Apache NuttX RTOS]

== SoC and Memory Specification ==

[[File:Sophgo-icon.jpg|right|200px]]

Based on the [https://en.sophgo.com/sophon-u/product/introduce/sg200x.html Sophgo SG-200x]

[[File:SG2000_Block_Diagram.png|500px]]

=== CPU Architecture ===

[[File:T-Head.png|right|200px]]

T-Head C906 1GHz MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64KB
* Level-2 128KB cache
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

T-Head C906 700Mhz MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 16 KB and a cache line of 16KB
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

[[File:Arm-logo.png|right|200px]]

ARM Cortex-A53 1GHz 64-bit RISC CPU:

* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core Cortex-A53 up to 1.0GHz CPU]
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Unified system L2 128KB cache
* Includes VFP v3 hardware to support single and double-precision operations
* Integrated 32KB L1 instruction cache, 32KB 4-way set associative L1 data cache
* TrustZone technology support
* PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3

8051 25-300MHz 8-bit CPU:
* Integrated 8K SRAM

=== System Memory ===
* SIP DRAM 512MB

== Board Features ==

=== Network ===
* 2.4 GHz 1T1R WiFi6
* Bluetooth 5.2
* 10/100 Mbit/s Ethernet with optional PoE capability

=== Storage ===
* On-board eMMC module socket
* MicroSD, supports SDHC and SDXC

=== Expansion Ports ===
* USB 2.0 Host port
* 26 GPIO pins, including SPI, I2C and UART functionality
* 2x Dual-lane MiPi CSI port
* Optional dual-lane MiPi DSI port

== Board Information, Schematics and Certifications ==

Board Dimensions: 85mm x 56mm x 18.8mm, see the [https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf model-B board dimension drawing]

Input Power: +5V @2A with 3.5mm/1.35mm Type H Barrel type DC connector (@1.5A will work if there is no heavy load on the USB 2.0 port)

Pre-Production version schematic:

* [https://files.pine64.org/doc/oz64/PINE64_Oz64_Schematic-20240517.pdf Oz64 Schematic 20240517 v1.0.0]
* [https://files.pine64.org/doc/oz64/PINE64_Oz64_PCB_Placement-Top-20240517.pdf Oz64 PCB Component placement(ToP) 20240517 v1.0.0]
* [https://files.pine64.org/doc/oz64/PINE64_Oz64_PCB_Placement-Bottom-20240517.pdf Oz64 PCB Component placement(Bottom) 20240517 v1.0.0]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary.
* Not yet available

== Datasheets for Components and Peripherals ==
Sophgo SG2000 SoC information:
* [https://github.com/sophgo/sophgo-doc/releases/download/sg2000-trm-v1.0/sg2000_trm_en.pdf Sophgo SG2000 SoC Technical Reference Manual]

Wifi/BT information:
* [https://files.pine64.org/doc/datasheet/oz64/AIC8800DC%20Datasheet%20v1.0.pdf AIC Semi AIC8800DC Datasheet]

Power Regulator information:
* [https://files.pine64.org/doc/datasheet/oz64/ETA3414_V1.6.pdf Empower ETA3414 1.5A 3MHz Step_down Converter Datasheet]
* [https://files.pine64.org/doc/datasheet/oz64/ETA3418_V1.4.pdf Empower ETA3418 2.5A 3MHz Step_down Converter Datasheet]
* [https://files.pine64.org/doc/datasheet/oz64/ETA5050_V2.4.pdf Empower ETA5050 500mA Low Noise, High PSRR, Fast Transient Response LDO Datasheet]

MicroSD socket information:
* [https://files.pine64.org/doc/datasheet/ox64/TF%20PUSH%20type%20socket%20specification.pdf Push type microSD socket specification]

== Resources and Articles ==

== Development Efforts ==

== Build==

* [https://lupyuen.github.io/articles/sg2000#appendix-build-nuttx-for-sg2000 Nuttx Build] by Lup Yuen

[[Category:Oz64]]
[[Category:Sophgo SG2000]]

Ox64

2024-06-23T07:28:51Z

Fxc: Reverted edits by Kuratius (talk) to last revision by Pavlos1

[[File:Ox64_board.jpg|thumb|right|The Ox64]]
[[File:Ox64 pinout.png|thumb|Pinout of the production version]]
[[File:RISC-V.png|thumb|right|Powered by RISC-V]]

The '''Ox64''' is a RISC-V based single-board computer based on the Bouffalo Lab BL808 RISC-V SoC with C906 64-bit and E907/E902 32-bit CPU cores supported by 64 MB of embedded PSRAM memory, and with built-in WiFi, Bluetooh and Zigbee radio interfaces. The Ox64 comes in a breadboard-friendly form-factor, has a microSD card slot, a USB 2.0 Type-C port, and many other peripheral interfaces for makers to integrate with sensors and other devices.

== Software Releases ==

=== Quick Links to the Source of OS Images Build ===

There is a community effort to bring updated kernels, peripherals and buildroot - Lots of communication happening in the #ox64-nutcracker channel.

* [https://github.com/openbouffalo/buildroot_bouffalo buildroot] bringing all the work below together with a bootable kernel and updated filesystem images for SD cards
* [https://github.com/smaeul/u-boot/tree/bl808 U-Boot] and [https://github.com/smaeul/opensbi/tree/bl808 OpenSBI] work by Smauel
* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others
* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others

Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.

* [https://github.com/bouffalolab/bl808_linux Linux for BL808]
* [https://wiki.pine64.org/wiki/File:Linux_BL808.pdf Installation Instructions for Linux on BL808 (Chinese)]
* [https://wiki.pine64.org/wiki/File:Linux_BL808_en.pdf Installation Instructions for Linux on BL808 (machine translated to English)]

Toolchain:

* elf_newlib_toolchain/bin/riscv64-unknown-elf-gcc (Xuantie-900 elf newlib gcc Toolchain V2.2.5 B-20220323) 10.2.0
* linux_toolchain/bin/riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.2.4 B-20211227) 10.2.0
* cmake version 3.19.3

=== Software Development Kits ===
* [https://github.com/bouffalolab/bl_mcu_sdk BL808 MCU SDK]
* [https://dev.bouffalolab.com/download BLDevCube Flashing Tool for Windows, macOS and Ubuntu x64]
* [https://wiki.pine64.org/wiki/File:Ox64_BL808UART_connect.pdf Ox64 UART Flashing Guide], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/bl808_demo_event.bin BL808 Demo Firmware: bl808_demo_event.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/whole_flash_data.bin BL808 UART Log Firmware: whole_flash_data.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/BL808.DVK.Quick.Start.pdf BL808 DVK Quick Start]
* [https://github.com/bouffalolab/bl808_linux/tree/main/opensbi-0.6-808 OpenSBI for BL808]
* [https://github.com/bouffalolab/bl-pac/tree/main/bl808 Rust Peripheral Access Crate (PAC) for BL808]
* [https://github.com/bouffalolab/bl-pac/blob/main/bl808/bl808.svd System View Description (SVD) for BL808]

== SoC and Memory Specification ==

[[File:Bouffalo_Lab_icon.png|right]]

Based on the [https://en.bouffalolab.com/product/ Bouffalo Lab BL808]

[[File:BL808_Block_Diagram.jpg|500px]]

=== CPU Architecture ===

[[File:T-Head.png|right|200px]]

T-Head C906 480 MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64B
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

T-Head E907 320 MHz 32-bit RISC-V CPU:

* Supports RISC-V RV32IMAFCP instruction set
* Supports RISC-V 32-bit/16-bit mixed instruction set
* Supports RISC-V machine mode and user mode
* Thirty-two 32-bit integer general purpose registers (GPR) and thirty-two 32-bit/64-bit floating-point GPRs
* Integer (5-stage)/floating-point (7-stage), single-issue, sequentially executed pipeline
* Supports AXI 4.0 main device interface and AHB 5.0 peripheral interface
* 32K instruction cache, two-way set associative structure
* 16K data cache, two-way set associative structure
* See [https://www.t-head.cn/product/e907?lang=en here]

T-Head E902 150 MHz 32-bit RISC-V CPU:

* See [https://www.t-head.cn/product/e902?lang=en here]

=== System Memory ===
* Embedded 64MB PSRAM

== Board Features ==

=== Network ===
* 2.4 GHz 1T1R WiFi 802.11 b/g/n
* Bluetooth 5.2
* Zigbee
* 10/100 Mbit/s Ethernet (optional, on expansion board)

=== Storage ===
* On-board 16 Mbit (2 MB) or 128 Mbit (16 MB) XSPI NOR flash memory
* MicroSD, supports SDHC and SDXC (only on the 128 Mbit version)

=== Expansion Ports ===
* USB 2.0 OTG port
* 26 GPIO pins, including SPI, I2C and UART functionality, possible I2S and GMII expansion
* Dual-lane MiPi CSI port, located at USB-C port, for camera module

=== Audio ===
* Microphone (optional, on the camera module)
* Speaker (optional, on the camera module)

== Board Information, Schematics and Certifications ==
[[File:Ox64 ethphy.png|thumb|Pinout for wiring ethernet PHY to EMAC]]

* Baseboard dimensions: 51 mm x 21 mm x 19 mm x 3.5 mm (breadboard friendly)
* Input power: 5 V, 0.5 A through the microUSB or USB-C ports

Production version schematic:

* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221018.pdf Ox64 Schematic 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221018.pdf Ox64 PCB Component placement(ToP) 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221018.pdf Ox64 PCB Component placement(Bottom) 20221018 v1.1]

Prototype (dispatched to developers) schematic:
* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221007.pdf Ox64 Schematic 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221007.pdf Ox64 PCB Component placement(ToP) 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221007.pdf Ox64 PCB Component placement(Bottom) 20221007 v1.0]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary.
* Not yet available

== Datasheets for Components and Peripherals ==

Bouffalo BL808 SoC information:
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_DS/en/BL808_DS_1.2_en.pdf Bouffalo Lab BL808 SoC Datasheet]
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_RM/en/BL808_RM_en_1.3.pdf Bouffalo Lab BL808 SoC Reference Manual]

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/ox64/gd25lq16e_rev1.2_20210108.pdf GigaDevice 16Mb XSPI-Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/star64/gd25lq128e_rev1.0_20210513.pdf GigaDevice 128Mb XSPI-Flash Datasheet]
* [https://wiki.pine64.org/images/5/5d/W25Q128JW_RevB_11042019-1761358.pdf Winbond 128Mb QSPI-Flash Datasheet] (W25Q128JWSQ)

Power Regulator information:
* [https://files.pine64.org/doc/datasheet/ox64/IA2014-03.pdf Innovation Analog Tech IA2014 Step_down Converter Datasheet]

MicroSD socket information:
* [https://files.pine64.org/doc/datasheet/ox64/TF%20PUSH%20type%20socket%20specification.pdf Push type microSD socket specification]

== Compatible UARTs when in bootloader mode ==

When the Ox64 is in bootloader mode, some UARTs are unable to communicate with it. When this is the case, utilities such as BLDevCube are unable to actually program the device. If you see "Shake hand fail" and an empty ack, and your device is in bootloader mode, then it is likely an incompatible UART.

The below devices have been tested and verified as working:
* Raspberry Pi Pico - running the following [https://github.com/sanjay900/ox64-uart/releases/tag/v1.1 UART firmware] (GP4 and GP5 are used for port 0, GP12 and GP13 for port 1)
* Compiled binary for Pi Pico and connectivity diagram is [https://github.com/Kris-Sekula/Pine64_Ox64_SBC/tree/main/uart here]
* ESP32 with CP210x - bridge the EN pin to ground to disable the ESP32 itself, and then connect the TX on the esp32 to 14 on the Ox64 and RX to pin 15. Note that only baud rate 115200 works, and this doesn't seem to work for everyone)
* Stand-alone CP2102 dongle works at 115200 baud. Brand used was HiLetgo.
* STM32F401 BlackPill - running the [https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/blackpillv2 Black Magic Debug] firmware
* STM32F103C8T6 BluePill - running Black Magic Debug.
* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)
* Some CH340G based adapters work and some don't.

== Resources and Articles ==
* [https://youtube.com/watch?v=czRtF-UNiEY A short video] on how to connect to the Ox64, flash and boot
* [https://youtu.be/vPAk5sq_Ilc Another video] that covers soldering pins, connecting via Pi Pico and flashing Linux and U-Boot
* [https://wiki.pine64.org/images/5/59/How_to_Run_Ox64.pdf Step-by-step tutorial] for how to build, flash and run Ox64
* [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff First batch of Ox64 won't appear as USB serial port]
* [https://gist.github.com/lupyuen/2087e9b3fb40aab5e0795bb02a265a3b First batch of Ox64 tested OK with CH340C/G]
* [https://www.robertlipe.com/bl808-not-symmetric/ First thoughts on the (a)symmetry of Bouffalo Labs BL808 as in Pine64 Ox64]
* [https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html The $8 linux computer (with picoprobe-rp2040 programming instructions)]
* [https://github.com/p4ddy1/pine_ox64/blob/main/build_toolchain_macos.md Building the Xuantie GNU Toolchain for Ox64 on macOS and Apple Silicon]

Ox64 BL808 RISC-V SBC articles by [https://lupyuen.codeberg.page/ Lup Yuen LEE]:
* [https://lupyuen.codeberg.page/articles/ox64.html Booting Linux and (maybe) Apache NuttX RTOS]
* [https://lupyuen.codeberg.page/articles/ox2.html Starting Apache NuttX real-time operating system]
* [https://lupyuen.codeberg.page/articles/mmu.html Sv39 Memory Management Unit]
* [https://lupyuen.codeberg.page/articles/app.html NuttX Apps and Initial RAM Disk]
* [https://lupyuen.codeberg.page/articles/plic2.html UART Interrupt and Platform-Level Interrupt Controller (PLIC)]
* [https://lupyuen.codeberg.page/articles/plic3.html Fixing the UART Interrupt and Platform-Level Interrupt Controller]
* [https://www.hackster.io/lupyuen/8-risc-v-sbc-on-a-real-time-operating-system-ox64-nuttx-474358 $8 RISC-V SBC on a Real-Time Operating System: Ox64 + NuttX]
* [https://lupyuen.codeberg.page/articles/nim.html Nim on a Real-Time Operating System: Apache NuttX RTOS + Ox64 BL808 SBC]

Git repositories:
* [https://github.com/sfranzyshen/arduino-bl808 Community made Arduino Core specifically for the Bouffalo Labs BL808 RISC-V MCU] (initial development has been postponed until further notice)

== Development Efforts ==
* [https://twitter.com/gamelaster/status/1583916501400068096 Ox64 boots Linux successfully]
* [https://twitter.com/btashton/status/1586381334439923713?t=w5xRRUR74HGK2O1Zg_aFyw&s=19 Brennan Ashton is porting Apache NuttX RTOS and OpenAMP (Asymmetric Multiprocessing) to BL808]
* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]

== Build==
Open the terminal and create a new directory for the build:

cd ~/Downloads/ox64
mkdir buildroot_bouffalo && cd buildroot_bouffalo

Clone the primary Buildroot repository and the specific Buildroot Bouffalo repository:

git clone https://github.com/buildroot/buildroot
git clone https://github.com/openbouffalo/buildroot_bouffalo

Define an environment variable for the Buildroot Bouffalo overlay path:

export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo

Change directory into the cloned Buildroot folder:

cd ~/Downloads/ox64/buildroot_bouffalo/buildroot

Apply the default configuration for Pine64 Ox64:

make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig
# make clean # deletes all the already compiled object files

Use the <code>menuconfig</code> tool to adjust the build settings:

make menuconfig

[[File:target ABI setting.png|thumb|right|200px|target ABI setting]]
[[File:toolchain setting.png|thumb|right|200px|toolchain setting]]

Within <code>menuconfig</code>, configure the following:
* Navigate to <code>Target Options</code>
* Enable <code>Integer Multiplication and Division (M)</code>
* Enable <code>Atomic Instructions (A)</code>
* Enable <code>Single-precision Floating-point (F)</code>
* Enable <code>Double-precision Floating-point (D)</code>
* Set <code>Target ABI</code> to <code>lp64d</code>
* Under <code>Toolchain</code>, enable <code>Fortran support</code> and <code>OpenMP support</code>

Initiate the build process, but make sure first that your <code>PATH</code> variable contains no spaces:

make

You will get the image files required for flashing in the <code>output/images</code> directory

== Flashing Ox64 SBC and microSD Card ==
This section explains how to flash an Ox64 board and a microSD card to boot the system.

=== Prepare the Environment ===
You need a Linux machine, a Raspberry Pi Pico to act as a UART adapter, the Ox64 board, and a microSD card.

Start a terminal session and set the working directory to download some files.

cd ~/Downloads
mkdir ox64 ox64/pico
cd ~/Downloads/ox64/pico
wget https://github.com/Kris-Sekula/Pine64_Ox64_SBC/blob/main/uart/picoprobe.uf2

cd ~/Downloads/ox64
mkdir ox64/devcube
cd ~/Downloads/ox64/devcube

Get the DevCube 1.8.8 flasher from one of mirror servers listed below.

* https://dev.bouffalolab.com/media/upload/download/BouffaloLabDevCube-v1.8.8.zip

Verify the file hashes listed below.

* SHA1: <code>0f2619e87d946f936f63ae97b0efd674357b1166</code>
* SHA256: <code>e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913</code>

Finally, uncompress the downloaded archive; for example:

wget https://dev.bouffalolab.com/media/upload/download/BouffaloLabDevCube-v1.8.8.zip
sha256sum BouffaloLabDevCube-v1.8.8.zip
unzip BouffaloLabDevCube-v1.8.8.zip
chmod u+x BLDevCube-ubuntu

Download compressed file from https://github.com/openbouffalo/buildroot_bouffalo/releases/ and decompress it.

(You can also get the compressed the file from https://github.com/openbouffalo/buildroot_bouffalo/releases/download/v1.0.1/bl808-linux-pine64_ox64_full_defconfig.tar.gz)

cd ~/Downloads/ox64
mkdir openbouffalo && cd openbouffalo
wget https://github.com/openbouffalo/buildroot_bouffalo/releases/download/v1.0.1/bl808-linux-pine64_ox64_full_defconfig.tar.gz
tar -xvzf bl808-linux-pine64_ox64_full_defconfig.tar.gz

You'll need the following files for the flashing process.

* <code>m0_lowload_bl808_m0.bin</code>
* <code>d0_lowload_bl808_d0.bin</code>
* <code>bl808-firmware.bin</code>
* <code>sdcard.img</code>

=== Establish Serial Communication from PC to Ox64 using Pi Pico ===
Open a terminal and check the connected USB serial devices.

ls /dev/ttyACM*

Set the Raspberry Pi Pico board into programming mode.

* Press the BootSel button
* Apply power by plugging the USB cable to PC
* Release the BootSel button

''Note: you could also ground pin28 to TP6 while powering.''

Copy <code>picoprobe.uf2</code> file into the new device <code>/media/<user>/RPI-RP2</code>.

cp ~/Downloads/ox64/pico/picoprobe.uf2 /media/<user>/RPI-RP2

After flashing, the device will auto-set in serial UART communication mode according to the following wiring diagram.

[[File:Pine Serial v2.png|thumb|right|Wiring Raspberry Pi Pico to Pine64 Ox64 SBC]]

OX64 PI PICO
uart0_Tx_GPIO14_pin1 <-> uart0_Rx_pin17
uart0_Rx_GPIO15_pin2 <-> uart0_Tx_pin16
Rxd_GPIO17_pin31 <-> uart1_Tx_pin6
Txd_GPIO16_pin32 <-> uart1_Rx_pin7
gnd_pin38 <-> gnd_pin38/3
vbus5v_pin40 <-> vbus5v_pin40

=== Flash Your Ox64 ===
There are two new ports to choose from, <code>/dev/ttyACM0</code> for serial console and <code>/dev/ttyACM1</code> for DevCube flashing.

minicom -b 2000000 -D /dev/ttyACM0

Set the Ox64 board into programming mode.

* Press the BOOT button
* Apply power or re-plug the USB cable
* Release the BOOT button

Close <code>minicom</code>. Open a new terminal window to run the DevCube flasher.

cd ~/Downloads/ox64/devcube
./BLDevCube-ubuntu

Select chip [BL808], press Finish and switch to [MCU] tab.

M0 Group[group0] Image Addr [0x58000000] [PATH to m0_lowload_bl808_m0.bin]
D0 Group[group0] Image Addr [0x58100000] [PATH to d0_lowload_bl808_d0.bin]
Interface: UART
Port/SN: /dev/ttyACM1 (make sure you don't use /dev/ttyACM0, it's used by the minicom console)
Uart rate 2000000
UART TX is physical pin 1/GPIO 14.
UART RX is physical pin 2/GPIO 15.
Click 'Create & Download' and wait until it's done

Switch to the [IOT] tab.

Enable 'Single Download', set Address with 0x800000, choose [PATH to bl808-firmware.bin]
Port/SN: /dev/ttyACM1 (make sure you don't use ACM0, it's used by minicom console)
Click 'Create & Download' again and wait until it's done
Close DevCube

==== Open-Source Flashing Using CLI ====
For those who do not want to use the DevCube, BouffaloLab provides open-source flashing packages <code>bflb-iot-tool</code> and <code>bflb-mcu-tool</code>.

''Note: While these packages do contain binaries in addition to the Python source code, those binaries do not appear to be used for UART flashing.''

First, install <code>bflb-iot-tool</code> using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows.

sudo apt install virtualenv python3-virtualenv python3.11-venv
python3 -m venv ~/ox64_venv
. ~/ox64_venv/bin/activate
pip install bflb-iot-tool ''# we are *not* using bflb-mcu-tool''

Note that each time you open a new terminal window you will need to re-run <code>. ~/ox64_venv/bin/activate</code> to reactivate the virtual environment.

Next, put Ox64 in programming mode (press the BOOT button when first applying power) and flash the BL808.

PORT=/dev/ttyACM1 ''# this will depend on which serial adapter you use''
BAUD=115200 ''# safe value for macOS, if using Linux set to 2000000 for faster flashing''
cd ~/Downloads/ox64/buildroot_bouffalo/buildroot/output/images

bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x000000 --firmware m0_lowload_bl808_m0.bin --single
bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x100000 --firmware d0_lowload_bl808_d0.bin --single
bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x800000 --firmware bl808-firmware.bin --single

If you get permission errors when running the commands above, you may need to add your user to the <code>dialout</code> group. Running the commands as <code>root</code> is not recommended since this will make <code>bflb-iot-tool</code> create <code>root</code>-owned files in your home directory.

==== BL808 Address Details ====
Note that the addresses are different according to the flashing method, DevCube or CLI.

DevCube CLI
M0 address 0x58000000 0x000000
D0 address 0x58100000 0x100000
LP address 0x58200000 0x200000

=== Flash Your microSD Card ===
Insert microSD card into PC, locate its device file (<code>/dev/sdb</code>, for example), erase the start of the card and proceed to flashing.

cd ~/Downloads/ox64/buildroot_bouffalo/buildroot/output/images
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768
sudo dd if=sdcard.img of=/dev/sdb bs=1M status=progress conv=fsync

=== Booting for the First Time ===
Insert microSD card into Ox64 and set a UART connection to the Ox64 board, using the following parameters.

* UART TX is physical pin 32/GPIO 16
* UART RX is physical pin 31/GPIO 17
* Baud rate is 2000000

Choose from serial devices <code>/dev/ttyACM0</code> and <code>/dev/ttyACM1</code>, using the lower number.

minicom -b 2000000 -D /dev/ttyACM0

Re-apply power to the Ox64 and enjoy the booting!

[[Category:Ox64]]
[[Category:Bouffalo BL808]]

PinePhone Pro

2023-12-21T21:30:26Z

Fxc: /* The installation is corrupted */ updated

PinePhone Pro

2023-12-21T21:29:30Z

Fxc: /* Flashing to microSD card */ +1

[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]

The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

The PinePhone Pro is PINE64’s second smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a open system stack. Achieving this goal will, however, take time as the software and overall smartphone software ecosystem needs to mature.

=== State of the software ===
([[PinePhone Pro Software State|view separately]])

{{:PinePhone Pro Software State}}

=== Editions and revisions ===
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.

* [[PinePhone Pro Developer Edition]]
* PinePhone Pro Explorer Edition

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this Wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time setup ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Devices shipped after the end of July 2022 do only accept a nano-SIM, the SIM is inserted into a carriage released by slightly pulling on the handle in the lower slot (for information regarding devices shipped prior to end of July 2022 see below).

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the SIM card in the lower slot.]]

{{Info|Information regarding devices shipped prior to end of July 2022: The PinePhone Pros shipped prior to the end of July 2022 come with a micro-SIM slot instead of a nano-SIM slot. Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

== Software ==

The software section explains how to install the available software releases for the PinePhone Pro to the internal eMMC or a microSD card, how to boot them and how to solve common booting issues.

=== Software releases ===

The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.

{{Info|Images of the regular PinePhone are not compatible with the PinePhone Pro.}}

=== Boot order ===

The RK3399S processor in the PinePhone Pro searches for the bootloader (such as ''U-Boot'' or ''Tow-Boot'') in the following order:

# SPI flash
# eMMC (the internal memory)
# MicroSD card

==== Boot from microSD card temporarily ====

To temporarily boot from an inserted '''microSD card''' do the following:

* On the '''Explorer Edition ordered after November 2023''' the microSD card is first in boot order due to using ''rk2aw'' instead of ''Tow-Boot'', see [https://xnux.eu/rk2aw/ here].

* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while powering on the device. The batches bought after July 2022 come with ''Tow-Boot'' flashed to the SPI, which offers additional functionality over ''U-Boot'' as bootloader.

* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the cover for a few seconds, while powering on the device. If the button is labeled ''RESET'' instead of ''RE'' please verify if the device is a regular [[PinePhone]] (or the Developer Edition). This is required because older batches don't ship with ''Tow-Boot'' on the SPI. Flashing ''Tow-Boot'' can be caught up by following [https://tow-boot.org/devices/pine64-pinephonePro.html this] instruction. Note: If ''Tow-Boot'' is flashed later, the microSD card can be selected at boot with the volume down key as well.

* On the '''Developer Edition (sold to selected developers only)''' the SPI and the eMMC can be bypassed by shorting the bypass test points while booting. The process is explained in the article [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation|PinePhone Pro Developer Edition]]. Please join the community chat for any questions regarding the process.

The RE button disables the SPI and the eMMC at the hardware level while the button is held and the PinePhone Pro will try to boot from the next available boot medium, which is the microSD card. Note: When holding the ''RE'' button (or when shorting the contact points in case of the ''Developer Edition'') for a longer time at boot the operating system will not initialize the SPI and eMMC and it will not be possible to write to these storage mediums until the next reboot.

{{Template:Info|The bootloader uses its own boot order for loading the kernel and other core operating system components at boot, which for example may result in the boot loader residing on the eMMC loading and booting the kernel from a microSD card.}}

==== Boot from microSD card permanently ====

The bootloader (such as ''U-Boot'') resides in the free space in front of the first partition. Wiping the bootloader from the eMMC to make the PinePhone Pro boot from microSD card can be done using <code>sudo dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=400 conv=fsync</code>. Formatting the drive or deleting the partition table is not sufficient to wipe the bootloader.

==== Notes ====

If you received your device after July of 2022, the bootloader resides on the SPI.

See [[RK3399 boot sequence]] for further details regarding the boot sequence.

=== Installation instructions ===

The software releases can be installed (the process is being referred to as ''flashing'') to the eMMC or to an microSD card.

==== Flashing to microSD card ====
To install an image to the microSD card:

# Download a compatible image from [[PinePhone Pro Software Releases]].
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Write the image to your microSD card using your favorite method, examples:
#* Using ''dd'': On the device you're flashing the microSD card from, find the correct device under <code>lsblk</code> and then flash the image to the microSD card using <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>. Make sure the target is the whole microSD card and not its first partition (''sdc1'' or ''mmcblk0p1'' are wrong!).
#* Using ''bmaptool'': Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device: Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 GB file.
#* Using ''a graphical tool'': A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
# Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore, see [[:File:Pinephone_slots.png|here]].
# Boot the device using the following method:
#* On the '''Explorer Edition ordered after November 2023''' boot the phone without any further action.
#* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while booting.
#* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the back cover while booting (or use the ''volume down key'' if you flashed ''Tow-Boot'').
#* On the '''Developer Edition (sold to selected developers only)''' apply the bypass by shorting the testing pads while booting according to the datasheet (or use the ''volume down key'' if you flashed ''Tow-Boot'').

Details regarding the boot order can be found in the [[PinePhone Pro#Boot order|Boot order]] section.

==== Flashing to the eMMC ====
Flashing to the eMMC (the internal memory of the PinePhone Pro) can either be done using ''Tow-Boot'''s USB Mass Storage mode (see [[#Boot order]] if you are unsure if the device comes with Tow-Bot pre-installed) or by booting an operating system from the microSD card (see the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]) and by writing to the eMMC directly from there:

By using Tow-Boot:

# Power off the device
# Power on the device and hold the ''volume up'' key before and during the second vibration
# The LED will turn blue if done successfully. This will only work if Tow-Boot is installed
# When connecting the device to a computer via USB it will behave like an USB drive now
# Check if the eMMC appears under <code>lsblk</code>, the output might look like the following:
#: '''''mmcblk2''' 179:0 0 115.2G 0 disk''
#: ''├─mmcblk2p1 179:1 0 122M 0 part /boot''
#: ''└─mmcblk2p2 179:2 0 115.1G 0 part /''
#: {{Info|In this example, '''/dev/mmcblk2''' is the device, while ''mmcblk2p1'' and ''mmcblk2p2'' are partitions of the device. The downloaded images are images from full devices, which means that the full device (''mmcblk2'' in this example) needs to be flashed. Ignore the partitions!}}
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/'''DEVICE''' bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'' and replace ''DEVICE'' with the correct device from the ''lsblk'' command)
# Reboot the PinePhone Pro

By booting a microSD card:

# Boot an operating system [[PinePhone Pro#Flashing to microSD card|from the microSD card]]. If there is already a bootloader on the eMMC installed see the section [[PinePhone Pro#Boot order|Boot order]] to bypass it.
# Download or copy the desired image to the microSD card as file
# Check if the eMMC appears under <code>lsblk</code>. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/mmcblk2 bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'').
# Reboot the PinePhone Pro

=== Troubleshooting ===

If the PinePhone Pro is not booting (either booting incompletely into a boot splash or tty or if the PinePhone Pro is showing no signs of life) this will typically have the following two reasons:

==== The battery is fully drained ====

If the battery is drained then the board can reset during boot causing a boot loop because of undervoltage condition. It can happen on all stages of the boot including ''U-Boot'' bootloader, display initialization and USB (re-)configuration. In that case it is not possible to charge the phone. The battery can be charged by interrupting the boot loop by booting the PinePhone Pro into ''Maskrom mode'' or by charging the battery externally. It is possible to follow these instructions without a computer by using a wall charger, however it would not be possible to determine if Maskrom mode was started successfully. To boot the PinePhone Pro into ''Maskrom mode'':

* Remove any microSD card from the phone and keep it removed for the below procedure
* Remove the battery, any USB cable and any serial cable
* Reinsert the battery
* Hold the ''RE'' button underneath the back cover of your ''Explorer Edition'' (or short the bypass contact points on the ''Developer Edition'')
{{Info|Confirm that the label of the button says ''RE'' and not ''RESET''! If the button label says ''RESET'' instead you probably have a regular PinePhone and you're reading the wrong page.}}
* Connect the phone to an USB port of a computer, while still holding the button for some time
* Confirm if the phone was booted in Maskrom mode:
** On ''Linux'' check if the Maskrom mode appears as device in the output of the terminal command <code>lsusb</code> on the computer, the expected ''VID:PID'' of the device is ''2207:330c''.
** On ''Windows'' this can be checked using the ''Device Manager'' and checking the VID "2207" and PID "330c" of an ''Unknown device'' appears.
** On ''macOS'' this can be checked in ''/Applications/Utilities/System Information.app'' under ''USB'' and by checking if the VID "2207" and PID "330c" is appearing for a ''Composite Device''.
* Let the phone charge for multiple hours

{{Info|If the device doesn't appear under ''lsusb'' please try again with a different known good USB-C cable and make sure that there is no microSD card in the phone inserted.}}

The device should now be able to boot from the boot medium again. If that is not the case the installation got corrupted, as explained below.

==== The installation is corrupted ====
The PinePhone Pro won't be able to boot if the installation on the SPI flash, the eMMC or the microSD card got corrupted. To boot a working operating system:

* Prepare a microSD card as explained in the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]
* Remove any USB-C cable or device or add-on case from the PinePhone Pro
* Make sure the device is powered off by shortly removing the battery for a second
* Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore.
* Power on the device while bypassing the SPI and eMMC as explained under [[PinePhone Pro#Boot order|Boot order]]

The device should now boot from the microSD card. If the phone does not boot from the microSD card the microSD card was flashed with an incompatible image or the battery got drained as explained above.

=== Bootloaders ===
The following section contains notes regarding compatible bootloaders with the PinePhone Pro.

==== U-Boot ====
The pre-installed operating system on the PinePhone Pro Explorer Edition, if sold prior to the end of July of 2022, is using [[U-Boot]] as default bootloader. Batches sold after July of 2022 are using ''Tow-Boot''

==== Tow-Boot ====
Current batches of the PinePhone Pro ship with ''Tow-Boot'' pre-installed to the SPI flash, which is an opinionated distribution of ''U-Boot'' and brings numerous advantages over stock ''U-Boot'', such as the possibility to choose from booting the eMMC or microSD card using the volume buttons during boot, as well as a ''USB Mass Storage mode'', where the device can be written to by connecting the device to a computer via USB.

The user can flash Tow-Boot to the PinePhone Pro using the [https://tow-boot.org/devices/pine64-pinephonePro.html instructions on the Tow-Boot website].

==== levinboot ====
The levinboot bootloader is another option for the PinePhone Pro. The project repository can be found [https://gitlab.com/DeltaGem/levinboot/-/tree/master/ here]. (Pinephone Pro supporting fork is [https://xff.cz/git/levinboot/ here].)

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

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.

{| class="wikitable"
|-
! Number
! Name
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART¹ mode.
|}

¹ Note: The baud rate may be 1500000 instead of 115200.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

''atinout'' example:

echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -

''minicom'' example:

minicom -D /dev/ttyUSB2

=== VoLTE ===

The PinePhone and PinePhone Pro modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

AT+QMBNCFG="select","ROW_Generic_3GPP"

Then enable Voice over LTE using:

AT+QCFG="ims",1

And reboot the modem to apply the settings:

AT+CFUN=1,1

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to power off the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone Pro. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone and PinePhone Pro modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===

The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the documentation section.

As with most smartphones, the PinePhone Pro has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone Pro may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Nano-SIM (Micro-SIM before 07/2022)
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''NOR Flash:''' Listed as [GigaDevices] GD25LQ128EWIGR, but physical inspection found a SiliconKaiser SK25LP128.
* '''Back Camera:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' Wi-Fi 802.11AC, hotspot capable + Bluetooth V5.0
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery; unglue bottom black plastic with your nail from Samsung battery before installation in order to match the dimensions)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Modifications and repairs ==

Most parts are available from the [https://pine64.com/product-category/pinephonepro-spare-parts/ Pine store]. Take care to use this link to avoid unintentionally ordering parts for the original PinePhone instead.

=== Replacing the mainboard ===

The mainboard can be replaced if it is faulty. The replacement board does not have an operating system pre-installed, to test if everything is working after swapping the mainboard a flashed SD card is required.

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an operating system from a microSD card.}}

Prior to replacing your PinePhone Pro’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the mainboard.
# Remove the phone's back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone, including the screw under the warranty sticker.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio and UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam for the regular PinePhone can be found [https://www.youtube.com/watch?v=5GbMoZ_zuZs here] or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here].

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Replacing the mainboard|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.
* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.
* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.
* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a silver-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the Pine Store ===

The following parts are not available on the Pine Store for the '''regular PinePhone'''. The replacements are listed below and have not been validated for the PinePhone Pro.

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| LCD
| Himax HX8394 compatible
|-
| Rear camera
| IMX258
|-
| Front camera
| OV8858
|-
| Camera flash
| AW3641EDNR
|-
| WiFi + Bluetooth
| [https://www.azurewave.com/img/wireless-modules/AW_CM256SM_DS_Rev15_CYW.pdf AzureWave AW-CM256SM]
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| <s>3 Axis Magnetometer</s>
| <s>[https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL]</s> '''''Note:''''' The ''AF8133J'' is used instead.
|-
| Geo Magnetic Sensor
| [http://www.voltafield.com/products01.html Voltafield AF8133J]
|-
| Ambient light / Proximity
| STK3311-A
|-
| Accelerometer / Gyroscope
| [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6500/ TDK MPU-6500]
|-
| Vibration motor
|
|-
| Notification LED
| LED0603RGB
|-
| Audio Codec
| ALC5616 and ALC5640
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| [https://rockchip.fr/RK818%20datasheet%20V1.0.pdf RK818]
|}

== Datasheets, schematics and certifications ==

PinePhone Pro mainboard schematic:
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf PinePhone Pro mainboard Explorer Edition Released Schematic ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-top.pdf PinePhone Pro mainboard Explorer Edition component top placement ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-bottom.pdf PinePhone Pro mainboard Explorer Edition component bottom placement ver 1.0 20211127]

PinePhone Pro USB-C small board schematic:
* TBD

Certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20FCC%20Certificate-S21101902805001.pdf PinePhone Pro FCC Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20SAR%20Evaluation%20Report-S21101902806001.pdf PinePhone Pro SAR Evaluation Report]
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20CE%20RED%20Certificate-S21101902802-R1.pdf PinePhone Pro CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20RoHS%20Test%20Report.pdf PinePhone Pro ROHS Test Report]

== Factory Test Build for Hardware Checking ==
[[File:PPP_Abdroid_Test_Utility-5.jpg|400px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by the support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, take out the PinePhone Pro Explorer Edition, then insert it into microSD slot (upper slot).
* Insert battery, press the RE button (bypass SPI and eMMC boot) underneath the back cover while plugging in the USB-C power. After 3 seconds release the RE button.
* When powering up, a battery icon screen will show up blow, press power key for two seconds, then the Rockchip logo screen shows up.


* Wait for the home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that the SD test is disabled due in this is SD boot build.
* After running a particular test function, please snapshot the test result and pass it back to support team

Notes:
* Please insert a functional SIM card when performing the SIM test
* When perform GPS test, the first result may fail and please ignore this false message.
* For light sensing test, please have a light shine to the PinePhone Pro when performing the test.


== Using Factory Test Build for Battery charging ==
[[File:PPP_Abdroid_Test_Utility-1.jpg|300px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and battery will start charging.
* The battery icon display for few seconds and then LCD panel turn off while charging. To check charging status, just quick press power button (about 0.5 second) and battery icon will display progress.

== Press ==

For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Press]].

== External links ==
* [https://www.pine64.org/pinephonepro/ Product Page]
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement

[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]

PinePhone Pro

2023-12-21T21:28:40Z

Fxc: /* Notes */ Removed outdated instructions

[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]

The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

The PinePhone Pro is PINE64’s second smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a open system stack. Achieving this goal will, however, take time as the software and overall smartphone software ecosystem needs to mature.

=== State of the software ===
([[PinePhone Pro Software State|view separately]])

{{:PinePhone Pro Software State}}

=== Editions and revisions ===
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.

* [[PinePhone Pro Developer Edition]]
* PinePhone Pro Explorer Edition

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this Wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time setup ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Devices shipped after the end of July 2022 do only accept a nano-SIM, the SIM is inserted into a carriage released by slightly pulling on the handle in the lower slot (for information regarding devices shipped prior to end of July 2022 see below).

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the SIM card in the lower slot.]]

{{Info|Information regarding devices shipped prior to end of July 2022: The PinePhone Pros shipped prior to the end of July 2022 come with a micro-SIM slot instead of a nano-SIM slot. Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

== Software ==

The software section explains how to install the available software releases for the PinePhone Pro to the internal eMMC or a microSD card, how to boot them and how to solve common booting issues.

=== Software releases ===

The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.

{{Info|Images of the regular PinePhone are not compatible with the PinePhone Pro.}}

=== Boot order ===

The RK3399S processor in the PinePhone Pro searches for the bootloader (such as ''U-Boot'' or ''Tow-Boot'') in the following order:

# SPI flash
# eMMC (the internal memory)
# MicroSD card

==== Boot from microSD card temporarily ====

To temporarily boot from an inserted '''microSD card''' do the following:

* On the '''Explorer Edition ordered after November 2023''' the microSD card is first in boot order due to using ''rk2aw'' instead of ''Tow-Boot'', see [https://xnux.eu/rk2aw/ here].

* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while powering on the device. The batches bought after July 2022 come with ''Tow-Boot'' flashed to the SPI, which offers additional functionality over ''U-Boot'' as bootloader.

* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the cover for a few seconds, while powering on the device. If the button is labeled ''RESET'' instead of ''RE'' please verify if the device is a regular [[PinePhone]] (or the Developer Edition). This is required because older batches don't ship with ''Tow-Boot'' on the SPI. Flashing ''Tow-Boot'' can be caught up by following [https://tow-boot.org/devices/pine64-pinephonePro.html this] instruction. Note: If ''Tow-Boot'' is flashed later, the microSD card can be selected at boot with the volume down key as well.

* On the '''Developer Edition (sold to selected developers only)''' the SPI and the eMMC can be bypassed by shorting the bypass test points while booting. The process is explained in the article [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation|PinePhone Pro Developer Edition]]. Please join the community chat for any questions regarding the process.

The RE button disables the SPI and the eMMC at the hardware level while the button is held and the PinePhone Pro will try to boot from the next available boot medium, which is the microSD card. Note: When holding the ''RE'' button (or when shorting the contact points in case of the ''Developer Edition'') for a longer time at boot the operating system will not initialize the SPI and eMMC and it will not be possible to write to these storage mediums until the next reboot.

{{Template:Info|The bootloader uses its own boot order for loading the kernel and other core operating system components at boot, which for example may result in the boot loader residing on the eMMC loading and booting the kernel from a microSD card.}}

==== Boot from microSD card permanently ====

The bootloader (such as ''U-Boot'') resides in the free space in front of the first partition. Wiping the bootloader from the eMMC to make the PinePhone Pro boot from microSD card can be done using <code>sudo dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=400 conv=fsync</code>. Formatting the drive or deleting the partition table is not sufficient to wipe the bootloader.

==== Notes ====

If you received your device after July of 2022, the bootloader resides on the SPI.

See [[RK3399 boot sequence]] for further details regarding the boot sequence.

=== Installation instructions ===

The software releases can be installed (the process is being referred to as ''flashing'') to the eMMC or to an microSD card.

==== Flashing to microSD card ====
To install an image to the microSD card:

# Download a compatible image from [[PinePhone Pro Software Releases]].
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Write the image to your microSD card using your favorite method, examples:
#* Using ''dd'': On the device you're flashing the microSD card from, find the correct device under <code>lsblk</code> and then flash the image to the microSD card using <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>. Make sure the target is the whole microSD card and not its first partition (''sdc1'' or ''mmcblk0p1'' are wrong!).
#* Using ''bmaptool'': Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device: Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 GB file.
#* Using ''a graphical tool'': A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
# Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore, see [[:File:Pinephone_slots.png|here]].
# Boot the device using the following method:
#* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while booting.
#* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the back cover while booting (or use the ''volume down key'' if you flashed ''Tow-Boot'').
#* On the '''Developer Edition (sold to selected developers only)''' apply the bypass by shorting the testing pads while booting according to the datasheet (or use the ''volume down key'' if you flashed ''Tow-Boot'').

Details regarding the boot order can be found in the [[PinePhone Pro#Boot order|Boot order]] section.

==== Flashing to the eMMC ====
Flashing to the eMMC (the internal memory of the PinePhone Pro) can either be done using ''Tow-Boot'''s USB Mass Storage mode (see [[#Boot order]] if you are unsure if the device comes with Tow-Bot pre-installed) or by booting an operating system from the microSD card (see the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]) and by writing to the eMMC directly from there:

By using Tow-Boot:

# Power off the device
# Power on the device and hold the ''volume up'' key before and during the second vibration
# The LED will turn blue if done successfully. This will only work if Tow-Boot is installed
# When connecting the device to a computer via USB it will behave like an USB drive now
# Check if the eMMC appears under <code>lsblk</code>, the output might look like the following:
#: '''''mmcblk2''' 179:0 0 115.2G 0 disk''
#: ''├─mmcblk2p1 179:1 0 122M 0 part /boot''
#: ''└─mmcblk2p2 179:2 0 115.1G 0 part /''
#: {{Info|In this example, '''/dev/mmcblk2''' is the device, while ''mmcblk2p1'' and ''mmcblk2p2'' are partitions of the device. The downloaded images are images from full devices, which means that the full device (''mmcblk2'' in this example) needs to be flashed. Ignore the partitions!}}
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/'''DEVICE''' bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'' and replace ''DEVICE'' with the correct device from the ''lsblk'' command)
# Reboot the PinePhone Pro

By booting a microSD card:

# Boot an operating system [[PinePhone Pro#Flashing to microSD card|from the microSD card]]. If there is already a bootloader on the eMMC installed see the section [[PinePhone Pro#Boot order|Boot order]] to bypass it.
# Download or copy the desired image to the microSD card as file
# Check if the eMMC appears under <code>lsblk</code>. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/mmcblk2 bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'').
# Reboot the PinePhone Pro

=== Troubleshooting ===

If the PinePhone Pro is not booting (either booting incompletely into a boot splash or tty or if the PinePhone Pro is showing no signs of life) this will typically have the following two reasons:

==== The battery is fully drained ====

If the battery is drained then the board can reset during boot causing a boot loop because of undervoltage condition. It can happen on all stages of the boot including ''U-Boot'' bootloader, display initialization and USB (re-)configuration. In that case it is not possible to charge the phone. The battery can be charged by interrupting the boot loop by booting the PinePhone Pro into ''Maskrom mode'' or by charging the battery externally. It is possible to follow these instructions without a computer by using a wall charger, however it would not be possible to determine if Maskrom mode was started successfully. To boot the PinePhone Pro into ''Maskrom mode'':

* Remove any microSD card from the phone and keep it removed for the below procedure
* Remove the battery, any USB cable and any serial cable
* Reinsert the battery
* Hold the ''RE'' button underneath the back cover of your ''Explorer Edition'' (or short the bypass contact points on the ''Developer Edition'')
{{Info|Confirm that the label of the button says ''RE'' and not ''RESET''! If the button label says ''RESET'' instead you probably have a regular PinePhone and you're reading the wrong page.}}
* Connect the phone to an USB port of a computer, while still holding the button for some time
* Confirm if the phone was booted in Maskrom mode:
** On ''Linux'' check if the Maskrom mode appears as device in the output of the terminal command <code>lsusb</code> on the computer, the expected ''VID:PID'' of the device is ''2207:330c''.
** On ''Windows'' this can be checked using the ''Device Manager'' and checking the VID "2207" and PID "330c" of an ''Unknown device'' appears.
** On ''macOS'' this can be checked in ''/Applications/Utilities/System Information.app'' under ''USB'' and by checking if the VID "2207" and PID "330c" is appearing for a ''Composite Device''.
* Let the phone charge for multiple hours

{{Info|If the device doesn't appear under ''lsusb'' please try again with a different known good USB-C cable and make sure that there is no microSD card in the phone inserted.}}

The device should now be able to boot from the boot medium again. If that is not the case the installation got corrupted, as explained below.

==== The installation is corrupted ====
The PinePhone Pro won't be able to boot if the installation on the SPI flash, the eMMC or the microSD card got corrupted. To boot a working operating system:

* Prepare a microSD card as explained in the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]
* Remove any USB-C cable or device or add-on case from the PinePhone Pro
* Make sure the device is powered off by shortly removing the battery for a second
* Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore.
* Power on the device while bypassing the SPI and eMMC as explained under [[PinePhone Pro#Boot order|Boot order]]

The device should now boot from the microSD card. If the phone does not boot from the microSD card the microSD card was flashed with an incompatible image or the battery got drained as explained above.

=== Bootloaders ===
The following section contains notes regarding compatible bootloaders with the PinePhone Pro.

==== U-Boot ====
The pre-installed operating system on the PinePhone Pro Explorer Edition, if sold prior to the end of July of 2022, is using [[U-Boot]] as default bootloader. Batches sold after July of 2022 are using ''Tow-Boot''

==== Tow-Boot ====
Current batches of the PinePhone Pro ship with ''Tow-Boot'' pre-installed to the SPI flash, which is an opinionated distribution of ''U-Boot'' and brings numerous advantages over stock ''U-Boot'', such as the possibility to choose from booting the eMMC or microSD card using the volume buttons during boot, as well as a ''USB Mass Storage mode'', where the device can be written to by connecting the device to a computer via USB.

The user can flash Tow-Boot to the PinePhone Pro using the [https://tow-boot.org/devices/pine64-pinephonePro.html instructions on the Tow-Boot website].

==== levinboot ====
The levinboot bootloader is another option for the PinePhone Pro. The project repository can be found [https://gitlab.com/DeltaGem/levinboot/-/tree/master/ here]. (Pinephone Pro supporting fork is [https://xff.cz/git/levinboot/ here].)

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

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.

{| class="wikitable"
|-
! Number
! Name
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART¹ mode.
|}

¹ Note: The baud rate may be 1500000 instead of 115200.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

''atinout'' example:

echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -

''minicom'' example:

minicom -D /dev/ttyUSB2

=== VoLTE ===

The PinePhone and PinePhone Pro modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

AT+QMBNCFG="select","ROW_Generic_3GPP"

Then enable Voice over LTE using:

AT+QCFG="ims",1

And reboot the modem to apply the settings:

AT+CFUN=1,1

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to power off the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone Pro. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone and PinePhone Pro modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===

The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the documentation section.

As with most smartphones, the PinePhone Pro has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone Pro may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Nano-SIM (Micro-SIM before 07/2022)
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''NOR Flash:''' Listed as [GigaDevices] GD25LQ128EWIGR, but physical inspection found a SiliconKaiser SK25LP128.
* '''Back Camera:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' Wi-Fi 802.11AC, hotspot capable + Bluetooth V5.0
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery; unglue bottom black plastic with your nail from Samsung battery before installation in order to match the dimensions)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Modifications and repairs ==

Most parts are available from the [https://pine64.com/product-category/pinephonepro-spare-parts/ Pine store]. Take care to use this link to avoid unintentionally ordering parts for the original PinePhone instead.

=== Replacing the mainboard ===

The mainboard can be replaced if it is faulty. The replacement board does not have an operating system pre-installed, to test if everything is working after swapping the mainboard a flashed SD card is required.

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an operating system from a microSD card.}}

Prior to replacing your PinePhone Pro’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the mainboard.
# Remove the phone's back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone, including the screw under the warranty sticker.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio and UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam for the regular PinePhone can be found [https://www.youtube.com/watch?v=5GbMoZ_zuZs here] or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here].

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Replacing the mainboard|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.
* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.
* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.
* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a silver-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the Pine Store ===

The following parts are not available on the Pine Store for the '''regular PinePhone'''. The replacements are listed below and have not been validated for the PinePhone Pro.

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| LCD
| Himax HX8394 compatible
|-
| Rear camera
| IMX258
|-
| Front camera
| OV8858
|-
| Camera flash
| AW3641EDNR
|-
| WiFi + Bluetooth
| [https://www.azurewave.com/img/wireless-modules/AW_CM256SM_DS_Rev15_CYW.pdf AzureWave AW-CM256SM]
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| <s>3 Axis Magnetometer</s>
| <s>[https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL]</s> '''''Note:''''' The ''AF8133J'' is used instead.
|-
| Geo Magnetic Sensor
| [http://www.voltafield.com/products01.html Voltafield AF8133J]
|-
| Ambient light / Proximity
| STK3311-A
|-
| Accelerometer / Gyroscope
| [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6500/ TDK MPU-6500]
|-
| Vibration motor
|
|-
| Notification LED
| LED0603RGB
|-
| Audio Codec
| ALC5616 and ALC5640
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| [https://rockchip.fr/RK818%20datasheet%20V1.0.pdf RK818]
|}

== Datasheets, schematics and certifications ==

PinePhone Pro mainboard schematic:
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf PinePhone Pro mainboard Explorer Edition Released Schematic ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-top.pdf PinePhone Pro mainboard Explorer Edition component top placement ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-bottom.pdf PinePhone Pro mainboard Explorer Edition component bottom placement ver 1.0 20211127]

PinePhone Pro USB-C small board schematic:
* TBD

Certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20FCC%20Certificate-S21101902805001.pdf PinePhone Pro FCC Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20SAR%20Evaluation%20Report-S21101902806001.pdf PinePhone Pro SAR Evaluation Report]
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20CE%20RED%20Certificate-S21101902802-R1.pdf PinePhone Pro CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20RoHS%20Test%20Report.pdf PinePhone Pro ROHS Test Report]

== Factory Test Build for Hardware Checking ==
[[File:PPP_Abdroid_Test_Utility-5.jpg|400px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by the support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, take out the PinePhone Pro Explorer Edition, then insert it into microSD slot (upper slot).
* Insert battery, press the RE button (bypass SPI and eMMC boot) underneath the back cover while plugging in the USB-C power. After 3 seconds release the RE button.
* When powering up, a battery icon screen will show up blow, press power key for two seconds, then the Rockchip logo screen shows up.


* Wait for the home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that the SD test is disabled due in this is SD boot build.
* After running a particular test function, please snapshot the test result and pass it back to support team

Notes:
* Please insert a functional SIM card when performing the SIM test
* When perform GPS test, the first result may fail and please ignore this false message.
* For light sensing test, please have a light shine to the PinePhone Pro when performing the test.


== Using Factory Test Build for Battery charging ==
[[File:PPP_Abdroid_Test_Utility-1.jpg|300px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and battery will start charging.
* The battery icon display for few seconds and then LCD panel turn off while charging. To check charging status, just quick press power button (about 0.5 second) and battery icon will display progress.

== Press ==

For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Press]].

== External links ==
* [https://www.pine64.org/pinephonepro/ Product Page]
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement

[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]

PinePhone Pro

2023-12-21T21:26:35Z

Fxc: /* Boot from microSD card temporarily */ addition

[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]

The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

The PinePhone Pro is PINE64’s second smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a open system stack. Achieving this goal will, however, take time as the software and overall smartphone software ecosystem needs to mature.

=== State of the software ===
([[PinePhone Pro Software State|view separately]])

{{:PinePhone Pro Software State}}

=== Editions and revisions ===
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.

* [[PinePhone Pro Developer Edition]]
* PinePhone Pro Explorer Edition

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this Wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time setup ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Devices shipped after the end of July 2022 do only accept a nano-SIM, the SIM is inserted into a carriage released by slightly pulling on the handle in the lower slot (for information regarding devices shipped prior to end of July 2022 see below).

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the SIM card in the lower slot.]]

{{Info|Information regarding devices shipped prior to end of July 2022: The PinePhone Pros shipped prior to the end of July 2022 come with a micro-SIM slot instead of a nano-SIM slot. Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

== Software ==

The software section explains how to install the available software releases for the PinePhone Pro to the internal eMMC or a microSD card, how to boot them and how to solve common booting issues.

=== Software releases ===

The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.

{{Info|Images of the regular PinePhone are not compatible with the PinePhone Pro.}}

=== Boot order ===

The RK3399S processor in the PinePhone Pro searches for the bootloader (such as ''U-Boot'' or ''Tow-Boot'') in the following order:

# SPI flash
# eMMC (the internal memory)
# MicroSD card

==== Boot from microSD card temporarily ====

To temporarily boot from an inserted '''microSD card''' do the following:

* On the '''Explorer Edition ordered after November 2023''' the microSD card is first in boot order due to using ''rk2aw'' instead of ''Tow-Boot'', see [https://xnux.eu/rk2aw/ here].

* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while powering on the device. The batches bought after July 2022 come with ''Tow-Boot'' flashed to the SPI, which offers additional functionality over ''U-Boot'' as bootloader.

* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the cover for a few seconds, while powering on the device. If the button is labeled ''RESET'' instead of ''RE'' please verify if the device is a regular [[PinePhone]] (or the Developer Edition). This is required because older batches don't ship with ''Tow-Boot'' on the SPI. Flashing ''Tow-Boot'' can be caught up by following [https://tow-boot.org/devices/pine64-pinephonePro.html this] instruction. Note: If ''Tow-Boot'' is flashed later, the microSD card can be selected at boot with the volume down key as well.

* On the '''Developer Edition (sold to selected developers only)''' the SPI and the eMMC can be bypassed by shorting the bypass test points while booting. The process is explained in the article [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation|PinePhone Pro Developer Edition]]. Please join the community chat for any questions regarding the process.

The RE button disables the SPI and the eMMC at the hardware level while the button is held and the PinePhone Pro will try to boot from the next available boot medium, which is the microSD card. Note: When holding the ''RE'' button (or when shorting the contact points in case of the ''Developer Edition'') for a longer time at boot the operating system will not initialize the SPI and eMMC and it will not be possible to write to these storage mediums until the next reboot.

{{Template:Info|The bootloader uses its own boot order for loading the kernel and other core operating system components at boot, which for example may result in the boot loader residing on the eMMC loading and booting the kernel from a microSD card.}}

==== Boot from microSD card permanently ====

The bootloader (such as ''U-Boot'') resides in the free space in front of the first partition. Wiping the bootloader from the eMMC to make the PinePhone Pro boot from microSD card can be done using <code>sudo dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=400 conv=fsync</code>. Formatting the drive or deleting the partition table is not sufficient to wipe the bootloader.

==== Notes ====

If you received your device after July of 2022, the bootloader (''Tow-Boot'') resides on the SPI. To boot to an SD card, place the SD card in your PinePhone Pro and turn it on. The phone will vibrate once. At this point, hold down the volume down button until you feel the device vibrate again then release the button. The LED color should change to blue and your display should remain black for a few seconds. In a few seconds you should see the SD card booting, the indications of which are dependent on what image you chose. If the LED is flashing instead, the boot from SD failed. Erasing the SPI can be achieved via the Tow-Boot installer image. Instructions are available here [https://tow-boot.org/devices/pine64-pinephonePro.html Tow-Boot PinePhone Pro Instructions].

See [[RK3399 boot sequence]] for further details regarding the boot sequence.

=== Installation instructions ===

The software releases can be installed (the process is being referred to as ''flashing'') to the eMMC or to an microSD card.

==== Flashing to microSD card ====
To install an image to the microSD card:

# Download a compatible image from [[PinePhone Pro Software Releases]].
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Write the image to your microSD card using your favorite method, examples:
#* Using ''dd'': On the device you're flashing the microSD card from, find the correct device under <code>lsblk</code> and then flash the image to the microSD card using <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>. Make sure the target is the whole microSD card and not its first partition (''sdc1'' or ''mmcblk0p1'' are wrong!).
#* Using ''bmaptool'': Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device: Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 GB file.
#* Using ''a graphical tool'': A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
# Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore, see [[:File:Pinephone_slots.png|here]].
# Boot the device using the following method:
#* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while booting.
#* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the back cover while booting (or use the ''volume down key'' if you flashed ''Tow-Boot'').
#* On the '''Developer Edition (sold to selected developers only)''' apply the bypass by shorting the testing pads while booting according to the datasheet (or use the ''volume down key'' if you flashed ''Tow-Boot'').

Details regarding the boot order can be found in the [[PinePhone Pro#Boot order|Boot order]] section.

==== Flashing to the eMMC ====
Flashing to the eMMC (the internal memory of the PinePhone Pro) can either be done using ''Tow-Boot'''s USB Mass Storage mode (see [[#Boot order]] if you are unsure if the device comes with Tow-Bot pre-installed) or by booting an operating system from the microSD card (see the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]) and by writing to the eMMC directly from there:

By using Tow-Boot:

# Power off the device
# Power on the device and hold the ''volume up'' key before and during the second vibration
# The LED will turn blue if done successfully. This will only work if Tow-Boot is installed
# When connecting the device to a computer via USB it will behave like an USB drive now
# Check if the eMMC appears under <code>lsblk</code>, the output might look like the following:
#: '''''mmcblk2''' 179:0 0 115.2G 0 disk''
#: ''├─mmcblk2p1 179:1 0 122M 0 part /boot''
#: ''└─mmcblk2p2 179:2 0 115.1G 0 part /''
#: {{Info|In this example, '''/dev/mmcblk2''' is the device, while ''mmcblk2p1'' and ''mmcblk2p2'' are partitions of the device. The downloaded images are images from full devices, which means that the full device (''mmcblk2'' in this example) needs to be flashed. Ignore the partitions!}}
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/'''DEVICE''' bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'' and replace ''DEVICE'' with the correct device from the ''lsblk'' command)
# Reboot the PinePhone Pro

By booting a microSD card:

# Boot an operating system [[PinePhone Pro#Flashing to microSD card|from the microSD card]]. If there is already a bootloader on the eMMC installed see the section [[PinePhone Pro#Boot order|Boot order]] to bypass it.
# Download or copy the desired image to the microSD card as file
# Check if the eMMC appears under <code>lsblk</code>. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/mmcblk2 bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'').
# Reboot the PinePhone Pro

=== Troubleshooting ===

If the PinePhone Pro is not booting (either booting incompletely into a boot splash or tty or if the PinePhone Pro is showing no signs of life) this will typically have the following two reasons:

==== The battery is fully drained ====

If the battery is drained then the board can reset during boot causing a boot loop because of undervoltage condition. It can happen on all stages of the boot including ''U-Boot'' bootloader, display initialization and USB (re-)configuration. In that case it is not possible to charge the phone. The battery can be charged by interrupting the boot loop by booting the PinePhone Pro into ''Maskrom mode'' or by charging the battery externally. It is possible to follow these instructions without a computer by using a wall charger, however it would not be possible to determine if Maskrom mode was started successfully. To boot the PinePhone Pro into ''Maskrom mode'':

* Remove any microSD card from the phone and keep it removed for the below procedure
* Remove the battery, any USB cable and any serial cable
* Reinsert the battery
* Hold the ''RE'' button underneath the back cover of your ''Explorer Edition'' (or short the bypass contact points on the ''Developer Edition'')
{{Info|Confirm that the label of the button says ''RE'' and not ''RESET''! If the button label says ''RESET'' instead you probably have a regular PinePhone and you're reading the wrong page.}}
* Connect the phone to an USB port of a computer, while still holding the button for some time
* Confirm if the phone was booted in Maskrom mode:
** On ''Linux'' check if the Maskrom mode appears as device in the output of the terminal command <code>lsusb</code> on the computer, the expected ''VID:PID'' of the device is ''2207:330c''.
** On ''Windows'' this can be checked using the ''Device Manager'' and checking the VID "2207" and PID "330c" of an ''Unknown device'' appears.
** On ''macOS'' this can be checked in ''/Applications/Utilities/System Information.app'' under ''USB'' and by checking if the VID "2207" and PID "330c" is appearing for a ''Composite Device''.
* Let the phone charge for multiple hours

{{Info|If the device doesn't appear under ''lsusb'' please try again with a different known good USB-C cable and make sure that there is no microSD card in the phone inserted.}}

The device should now be able to boot from the boot medium again. If that is not the case the installation got corrupted, as explained below.

==== The installation is corrupted ====
The PinePhone Pro won't be able to boot if the installation on the SPI flash, the eMMC or the microSD card got corrupted. To boot a working operating system:

* Prepare a microSD card as explained in the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]
* Remove any USB-C cable or device or add-on case from the PinePhone Pro
* Make sure the device is powered off by shortly removing the battery for a second
* Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore.
* Power on the device while bypassing the SPI and eMMC as explained under [[PinePhone Pro#Boot order|Boot order]]

The device should now boot from the microSD card. If the phone does not boot from the microSD card the microSD card was flashed with an incompatible image or the battery got drained as explained above.

=== Bootloaders ===
The following section contains notes regarding compatible bootloaders with the PinePhone Pro.

==== U-Boot ====
The pre-installed operating system on the PinePhone Pro Explorer Edition, if sold prior to the end of July of 2022, is using [[U-Boot]] as default bootloader. Batches sold after July of 2022 are using ''Tow-Boot''

==== Tow-Boot ====
Current batches of the PinePhone Pro ship with ''Tow-Boot'' pre-installed to the SPI flash, which is an opinionated distribution of ''U-Boot'' and brings numerous advantages over stock ''U-Boot'', such as the possibility to choose from booting the eMMC or microSD card using the volume buttons during boot, as well as a ''USB Mass Storage mode'', where the device can be written to by connecting the device to a computer via USB.

The user can flash Tow-Boot to the PinePhone Pro using the [https://tow-boot.org/devices/pine64-pinephonePro.html instructions on the Tow-Boot website].

==== levinboot ====
The levinboot bootloader is another option for the PinePhone Pro. The project repository can be found [https://gitlab.com/DeltaGem/levinboot/-/tree/master/ here]. (Pinephone Pro supporting fork is [https://xff.cz/git/levinboot/ here].)

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

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.

{| class="wikitable"
|-
! Number
! Name
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART¹ mode.
|}

¹ Note: The baud rate may be 1500000 instead of 115200.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

''atinout'' example:

echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -

''minicom'' example:

minicom -D /dev/ttyUSB2

=== VoLTE ===

The PinePhone and PinePhone Pro modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

AT+QMBNCFG="select","ROW_Generic_3GPP"

Then enable Voice over LTE using:

AT+QCFG="ims",1

And reboot the modem to apply the settings:

AT+CFUN=1,1

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to power off the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone Pro. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone and PinePhone Pro modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===

The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the documentation section.

As with most smartphones, the PinePhone Pro has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone Pro may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Nano-SIM (Micro-SIM before 07/2022)
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''NOR Flash:''' Listed as [GigaDevices] GD25LQ128EWIGR, but physical inspection found a SiliconKaiser SK25LP128.
* '''Back Camera:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' Wi-Fi 802.11AC, hotspot capable + Bluetooth V5.0
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery; unglue bottom black plastic with your nail from Samsung battery before installation in order to match the dimensions)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Modifications and repairs ==

Most parts are available from the [https://pine64.com/product-category/pinephonepro-spare-parts/ Pine store]. Take care to use this link to avoid unintentionally ordering parts for the original PinePhone instead.

=== Replacing the mainboard ===

The mainboard can be replaced if it is faulty. The replacement board does not have an operating system pre-installed, to test if everything is working after swapping the mainboard a flashed SD card is required.

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an operating system from a microSD card.}}

Prior to replacing your PinePhone Pro’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the mainboard.
# Remove the phone's back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone, including the screw under the warranty sticker.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio and UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam for the regular PinePhone can be found [https://www.youtube.com/watch?v=5GbMoZ_zuZs here] or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here].

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Replacing the mainboard|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.
* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.
* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.
* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a silver-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the Pine Store ===

The following parts are not available on the Pine Store for the '''regular PinePhone'''. The replacements are listed below and have not been validated for the PinePhone Pro.

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| LCD
| Himax HX8394 compatible
|-
| Rear camera
| IMX258
|-
| Front camera
| OV8858
|-
| Camera flash
| AW3641EDNR
|-
| WiFi + Bluetooth
| [https://www.azurewave.com/img/wireless-modules/AW_CM256SM_DS_Rev15_CYW.pdf AzureWave AW-CM256SM]
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| <s>3 Axis Magnetometer</s>
| <s>[https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL]</s> '''''Note:''''' The ''AF8133J'' is used instead.
|-
| Geo Magnetic Sensor
| [http://www.voltafield.com/products01.html Voltafield AF8133J]
|-
| Ambient light / Proximity
| STK3311-A
|-
| Accelerometer / Gyroscope
| [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6500/ TDK MPU-6500]
|-
| Vibration motor
|
|-
| Notification LED
| LED0603RGB
|-
| Audio Codec
| ALC5616 and ALC5640
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| [https://rockchip.fr/RK818%20datasheet%20V1.0.pdf RK818]
|}

== Datasheets, schematics and certifications ==

PinePhone Pro mainboard schematic:
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf PinePhone Pro mainboard Explorer Edition Released Schematic ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-top.pdf PinePhone Pro mainboard Explorer Edition component top placement ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-bottom.pdf PinePhone Pro mainboard Explorer Edition component bottom placement ver 1.0 20211127]

PinePhone Pro USB-C small board schematic:
* TBD

Certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20FCC%20Certificate-S21101902805001.pdf PinePhone Pro FCC Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20SAR%20Evaluation%20Report-S21101902806001.pdf PinePhone Pro SAR Evaluation Report]
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20CE%20RED%20Certificate-S21101902802-R1.pdf PinePhone Pro CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20RoHS%20Test%20Report.pdf PinePhone Pro ROHS Test Report]

== Factory Test Build for Hardware Checking ==
[[File:PPP_Abdroid_Test_Utility-5.jpg|400px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by the support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, take out the PinePhone Pro Explorer Edition, then insert it into microSD slot (upper slot).
* Insert battery, press the RE button (bypass SPI and eMMC boot) underneath the back cover while plugging in the USB-C power. After 3 seconds release the RE button.
* When powering up, a battery icon screen will show up blow, press power key for two seconds, then the Rockchip logo screen shows up.


* Wait for the home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that the SD test is disabled due in this is SD boot build.
* After running a particular test function, please snapshot the test result and pass it back to support team

Notes:
* Please insert a functional SIM card when performing the SIM test
* When perform GPS test, the first result may fail and please ignore this false message.
* For light sensing test, please have a light shine to the PinePhone Pro when performing the test.


== Using Factory Test Build for Battery charging ==
[[File:PPP_Abdroid_Test_Utility-1.jpg|300px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and battery will start charging.
* The battery icon display for few seconds and then LCD panel turn off while charging. To check charging status, just quick press power button (about 0.5 second) and battery icon will display progress.

== Press ==

For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Press]].

== External links ==
* [https://www.pine64.org/pinephonepro/ Product Page]
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement

[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]

PineTab2 FAQ

2023-12-15T21:10:55Z

Fxc: Please no html code, the wiki is not a website

This is a collection of tutorials and frequently asked questions for the [[PineTab2]].

== Tutorials ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, plug the included debug adapter into the charging USB-C port and switch the white switch to its "ON" position to bypass eMMC/SPI boot. This tries to boot from SD, and if no SD is inserted, enters Maskrom mode.

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

Make sure to open the iPhone once you reconnect.

==== Performing USB Tethering with a KaiOS phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use a KaiOS phone for mobile Internet use with your PineTab2.

You'll need:

* A KaiOS phone
* A USB OTG adapter
* Your device’s charging cable
* Some knowledge of your KaiOS phone

Do the following in order:

* Plug the device into the PineTab2 using the USB cable and a USB OTG adapter
* On your KaiOS phone, open settings (specifics from here may vary on version)
* Navigate to "Network & Connectivity"
* Navigate to "Internet Sharing"
* Select "USB" and select On under USB tethering (Note: This option will be greyed out unless connected to the PineTab2)

You should now see a new network interface on the PineTab2 and it should show a wired connection icon.

=== Screen Rotation ===
==== Auto-rotating the Screen ====
Auto-rotation is handled by your operating system. However, the following general steps should work on distributions that support iio-sensor-proxy:

* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* Some desktop environments, such as KDE, default to only allowing screen rotation while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor -> Display Configuration -> Uncheck "Only when in tablet mode" and click "Apply."

==== Rotating the Login Screen ====
Login screen orientation is handled by your operating system. Below are the instructions for the SDDM login screen that ships with the factory image:

By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
* Reboot, and your login screen should now display in landscape mode.

== Frequently Asked Questions ==

=== General ===

==== How does the PineTab2 compare to the Pinebook Pro? ====
It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

==== What is the Performance of the PineTab2 compared to the PineTab-V? ====
The PineTab2 is notably faster than the PineTab-V. You can see this by [https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md comparing the Quartz64 sbc-bench results to the Star64 ones]. Performance should not be a factor of consideration when purchasing a PineTab-V.

==== I am a casual user with minimal Linux experience. Is this device for me? ====
The PineTab 2 is considered early release at this point, and the community is expected to develop support for it over time. For example, the [[PineTab2#Known_Issues]] page details several features that are not yet fully working. You may at times need to troubleshoot this device and some development experience is ideal if you want to realize the tablet's full potential at this stage.

For these reasons, the PineTab2 may not be the ideal device for casual users. However, if you feel up to the challenge and want to learn while joining a great community, you are more than welcome! Please join one of our [[Main_Page#Chat_Platforms|chat platforms]]: the community is always happy to help!

==== What works, what doesn't? ====

Please see [[PineTab2#Known_Issues]].

==== I only know Python, can I help with drivers? ====
Drivers are (at least typically) written in the C programming language. Unfortunately, there is no way to "code drivers in Python" because usually drivers need to access and process memory allocation directly. If you feel like this is interesting to you, we suggest you to spend some time learning the C programming language, maybe with an emphasis in device driver development. The good news is that, since you already know a programming language, you already know part of the skill.

In short, you can only help with drivers development if you learn the C programming language first.

=== Hardware ===

==== Does the Tablet support a Pen? ====
No, adding a digitiser for pen inputs would make the price too high.

==== Is there SPI Flash? ====
Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== Software ===
==== What operating systems are currently available? ====
The PineTab2 uses ARM operating systems. Please see [[PineTab2 Releases]] for a current list of software releases.

==== How can I install an operating system on the SD card / eMMC? ====

See the article [[PineTab2]].

==== Can I run Android on it? ====

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, and you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====

The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. Please see the [[PineTab2]] for more detailed information.

==== Can I install a different OS on my PineTab2? ====

Yes! While all PineTab2 come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card. See [[PineTab2]] and [[PineTab2 Releases]] for how to install them.

=== Bluetooth ===

==== The Bluetooth isn't working ====

The BES2600 Bluetooth driver still needs to be implemented. Please see the [[#Networking Using USB]] section above for a workaround.

=== Wi-Fi ===

==== The Wi-Fi isn't working ====
The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing: at the moment it causes system crashes. Please see the [[#Networking Using USB]] section above for a workaround.

=== Video ===

==== Can PineTab2 play back DRM content such as Netflix? ====

Yes. Procedure below was confirmed to get working Disney+, Amazon Prime and Netflix, as of 2023-12-14.

1 '''Install [https://aur.archlinux.org/packages/glibc-widevine glibc-widevine] from AUR.'''

This adds the necessary bits that are missing from glibc versions below 2.36. It's available in AUR, so you can follow the standard installation process for any AUR package. E.g. <code>yay -S glibc-widevine</code> if you use <code>yay</code>. During installation it says it conflicts with, and will replace, glibc. That's OK, as expected.

Doing this explicitly is no longer actually necessary, as installing [https://aur.archlinux.org/packages/widevine widevine] should automatically install <code>glibc-widevine</code> too.

2. '''Install [https://aur.archlinux.org/packages/widevine widevine] from AUR.'''

It automatically registers the libraries with Firefox and Chromium. After first installation, you will need to log out and back in. It might also be required to restart the browser up to 2 times before the widevine library is fully recognized and registered.

3. '''Test.'''

At this point, playing some DRM content should already work. It is best to test https://bitmovin.com/demos/drm . Disney+ and Amazon Prime also should already work fine.

4. '''User agent spoofing for Netflix.'''

For Netflix, you will need an extra step -- spoof the user agent, i.e. pretend you're using a different device. For some reason, Netflix doesn't tolerate "WWW browser on Linux on 64-bit Arm" which you use. You can use various Firefox or Chromium extensions to change the user agent, like like [https://addons.mozilla.org/en-US/firefox/addon/user-agent-string-switcher/ User-Agent Switcher and Manager for Firefox]. You have to pretend to be a user agent coming from ChromeOS, so it matches the ARM architecture (choosing a popular user agent like Windows on x86_64 will not work). You can peek at sample user agent strings on https://user-agents.net/platforms/chromeos/user-agents .

User agent confirmed to work on 2023-12-11:

Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36

In the preferences of the extension (for Firefox or Chromium) you should be able to define a new entry to pretend you're using ''ChromeOS'' with the user agent string as above. Double-check you changed the user agent correctly by visiting e.g. [https://duckduckgo.com/?q=my+user+agent&t=ffab&ia=answer DuckDuckGo answer for "my user agent"].

Once this is set up correctly, Netflix should work.

When you're confident Netflix works, you can change the "user agent spoofing" extension preferences to only change the user agent for the <code>*.netflix.com</code> domains. Otherwise you are pretending for all sites that you come from ''ChromeOS'' -- which is unnecessary (albeit harmless).

'''Notes:'''

* https://aur.archlinux.org/packages/glibc-widevine has version 2.35 . And that is OK, despite e.g. https://github.com/AsahiLinux/widevine-installer saying that ''"Using Widevine requires glibc version 2.36 or later."'' . The https://aur.archlinux.org/packages/glibc-widevine adds the necessary glibc RELRO bits and that's enough for widevine to work.
* In case you have <code>mobile-config-firefox</code> installed, it may cause issues according to https://forum.pine64.org/showthread.php?tid=18933&pid=120956#pid120956 . Check do you have it by a command like <code>sudo pacman -Qi mobile-config-firefox</code>. Remove it by a command like <code>sudo pacman -R mobile-config-firefox</code>.

[[Category:Rockchip RK3566]]

PinePhone

2023-10-23T15:26:14Z

Fxc: /* Pogo pins */ Pulled more information, changed the style

[[File:PinePhone Beta Edition.png|400px|thumb|right|Rendering of the PinePhone Beta Edition]]

The '''PinePhone''' is a smartphone created by PINE64. It is capable of running mainline Linux and is supported by many partner projects.

The Braveheart Edition of the PinePhone was the first publicly available version of the phone. It shipped without a fully functional operating system and was geared specifically towards early adopters. The Braveheart Edition's successors were the Community Editions, which featured a branded backcover and box of selected community projects. The Community Editions became available in June 2020. The Beta Edition featuring Manjaro with Plasma Mobile is the latest edition, it became available in March 2021.

== Introduction ==

The PinePhone is not a regular phone and you might not get the latest and greatest hardware and this years' newest innovation. You will get a device with good mainline support with a great community behind it.

=== State of the software ===

First things first, the PinePhone is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive operating system experience.

Bear in mind that the software for these smartphones is very early, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the community chat (see [[Main Page#Community and Support]])!

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The PinePhone's SIM slot only accepts a micro-SIM, please do not insert a nano-SIM without an adapter and make sure that the nano-SIM does not get released from its adapter. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot.

{{Info|Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the micro-SIM in the lower slot.]]

An adapter from a nano to a micro-SIM might be included under tape in the camera notch of the phone's packaging. Some nano-SIMs will not fit firmly into that adapter that comes with the PinePhone and if the included adapter is used without a well-fitting nano-SIM, the contact pins might get damaged. In that case it is highly recommended to acquire a better fitting adapter.

== Operating systems ==

The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distribution (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for mobile use on devices like the PinePhone.

=== Software releases ===

The [[PinePhone Software Releases]] page has a complete list of currently supported phone-optimized Operating System images that work with the PinePhone as well as other related software information. As soon as more patches get mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device. To update any installed operating system please see [[PinePhone Updating Instructions]].

=== Installation instructions ===

The instructions to install an operating system to the internal memory ("eMMC") or a microSD card can be found here: [[PinePhone Installation Instructions]].

=== Troubleshooting ===

If the PinePhone is not booting from eMMC and/or microSD card anymore it can have two causes:

==== The battery is drained ====

If the battery is fully drained, most operating systems and distributions won't boot anymore. One of the exceptions which still boots is the utility ''Jumpdrive'', which can usually be used to expose the eMMC and microSD card as drives to a USB-connected computer. Mind that JumpDrive won't expose the eMMC and microSD card with a drained battery but it still can be flashed and booted from microSD card to confirm that the phone still functions and boots up fine.

JumpDrive can be downloaded from [https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz here] (not compatible with the PinePhone Pro!).

{{Info|If JumpDrive boots and other releases do not boot, the battery is likely drained. In that case let it charge while running JumpDrive with a compatible charger for multiple hours and make sure to not fully drain the battery in the future anymore, as that significantly reduces the battery lifetime.}}

Alternatively to testing JumpDrive, the issue can also be diagnosed by checking the battery charge. Simply remove the battery from the device and measure the voltage on the (+) and (-) contacts on the battery. Make sure to not shorten the contacts as shorting battery pins is a severe life and safety danger.

==== The installation is corrupted or incorrect ====

If the installation of the prioritized boot medium is corrupted or incorrect, the PinePhone will not boot anymore. The following problems are common:

* The microSD card is in the wrong slot (see [[#First time installation|first time installation]])
* The image file was flashed to partition 1 (example: ''sdx1'', ''nvme0x1p1'') instead of the whole device (example: ''sdx'', ''nvme0x1'')
* An image without bootloader was flashed (mind the ''Tow-Boot'' bootloader requirements of ''Mobian'' and ''postmarketOS'')
* The operating systems got corrupted, for example after running updates (reflash the device, see [[PinePhone Installation Instructions]])
* An incompatible image was flashed (make sure that the images are compatible. Images for the PinePhone Pro won't boot on the PinePhone and vice versa. Check your invoice to see if you ordered a PinePhone or a PinePhone Pro).

== Specifications ==

* '''Dimensions:''' 160.5 x 76.6 x 9.2mm
* '''Weight:''' Between 180 ~ 200 grams
* '''SIM Card:''' Micro-SIM
* '''Display:'''
** '''Size:''' 5.95 inches (151mm) diagonal
** '''Type:''' HD IPS capacitive touchscreen, 16M colors
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64]
* '''RAM:''' 2GB or 3GB LPDDR3 SDRAM
* '''Internal Storage:''' 16GB or 32GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back Camera:''' Single 5MP, 1/4", LED Flash
* '''Front Camera:''' Single 2MP, f/2.8, 1/5"
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot
** '''Bluetooth:''' 4.0, A2DP
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| Rear camera
| OmniVision OV5640
|-
| Camera flash
| SGMICRO SGM3140
|-
| Front camera
| GalaxyCore GC2145
|-
| LCD
| Xingbangda XBD599
|-
| WiFi
| Realtek RTL8723CS
|-
| Bluetooth
| Realtek RTL8723CS
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| Magnetometer
| ST LIS3MDL
|-
| Ambient light / Proximity
| SensorTek STK3335
|-
| Accelerometer / Gyroscope
| InvenSense MPU-6050
|-
| Vibration motor
| Unknown model
|-
| Notification LED
| LED0603RGB
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
| X-Powers AXP803
|-
| Battery fuel gauge
| X-Powers AXP803
|}

See the [[PinePhone_component_list|PinePhone Component List]].

== Hardware revisions ==

[[File:Pinephone_revisions.png|400px|thumb|right|The history of the PinePhone CEs]]

The following are all hardware revisions of the PinePhone that have existed, ordered by the time of their releases:

* [[Project Anakin]] - Development kit
* [[Project Don't be evil]] - Development kit
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] - Developer Edition
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] - Braveheart Edition
* [[PinePhone v1.2]] - Ubports Community Edition
* [[PinePhone v1.2a]] - postmarketOS Community Edition
* [[PinePhone v1.2b]] - Manjaro Community Edition, KDE Community Edition, Mobian Community Edition and Beta Edition

== Hardware accessory ==

=== Add-ons ===
The PinePhone (and PinePhone Pro) is compatible with the official add-on cases, such as the keyboard, the LoRa add-on, the Qi wireless charging add-on and the fingerprint reader add-on. Details can be found under:

* [[PinePhone (Pro) Add-ons]]
* [[PinePhone (Pro) Keyboard]]

=== PinePhone Accessories ===
See [[PinePhone Hardware Accessory Compatibility]] for a list of devices working with the PinePhone (depending on their OS support).

The USB-C can be used to power the device, and offers USB2 host and OTG capabilities, 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, an HDMI port and Ethernet connection.

=== Pogo pins ===

[[File:Pinephone pogo.png|400px|thumb|right|The pogo pins, as visible under the back cover.]]

The PinePhone has six pogo pins on the back allowing for custom hardware extensions such as wireless charging, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power inputs/outputs and an I2C interface.

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| DCIN
| USB-5V
| GND
|}

PINE64 store currently sells the [https://pine64.com/product/pinephone-flex-break-out-board/?v=0446c16e2e66 PinePhone Flex Breakout Board]. With the pitch being 2.54 mm, this Flex Breakout Board may have leads soldered directly to the contacts for use in a solderless board. A non-soldered solution would be to use a [https://www.digikey.com/en/products/detail/te-connectivity-amp-connectors/5-520315-6/2258879 TE AMP Connector] that will accept a Flat Flexible Cable 2.54 mm pitch.

The following community resources are using the pogo pin connections:
* The [https://github.com/SMR404/PinephonePogoBreakout ''PinephonePogoBreakout''] breakout board from the community member ''SMR404''
* Martijn Braams' [https://blog.brixit.nl/making-a-backcover-extension-for-the-pinephone/ ''Making a backcover extension for the PinePhone'']

{{Warning|The following information in this subsection is only partially correct. A rewrite is currently pending.}}

DCIN and USB-5V are the names used in the schematics. The actual behavior of these pogo pins is not obvious based on their names. DCIN is connected both to the VBUS line of the USB Type-C connector and to the ACIN/VBUS inputs on the PMIC. This means that, depending on a number of factors, DCIN may be at 0 V or 5 V. USB-5V is connected at the output of an LP6226 DC/DC boost converter (5 V), which in turn is fed by the PS output of the PMIC. The boost converter is enabled or disabled by a GPIO output from the A64 SoC, controlled by software (e.g. the Linux kernel). Depending on inputs and decision made by the PMIC, PS may be at the battery voltage (fed "directly" by the battery through a [https://www.zxcompo.com/ transistor] controlled by the PMIC), or at the "USB" voltage (fed by the PMIC's ACIN/VBUS inputs). This means that depending on a number of factors, USB-5V may be at battery voltage (between 3.0 V and 4.3 V), or at 5 V.

Because the PinePhone may act as a USB host (providing 5 V at the USB Type-C connector's VBUS to a connected device) or as a USB device (drawing from a 5 V source on the USB Type-C connector's VBUS), DCIN is actually not strictly an input nor an output. Some community analysis of the PinePhone schematic (and some testing) indicates that you can connect a 5 V power supply to DCIN in order to power the phone at the PMIC's ACIN/VBUS inputs (and, as a side effect, charge the battery). This may not be safe to do in all conditions, e.g., when the phone is acting as a USB host to a connected USB device. It should also be safe to use DCIN as a power output from the PinePhone, e.g., when a USB Type-C charger is connected, you can draw current directly from the USB Type-C port's VBUS, which is provided by the charger. Please note that, when using DCIN as an output from the PinePhone, DCIN isn't "always on"; it may be 0 V. It is currently not documented on how much current can be safely drawn.

USB-5V should be safe to use as an "always on" power output from the PinePhone. Depending on a number of factors, voltage may be from 3 V to 5 V; thus, if you are using USB-5V to power your pogo-pins expansion board, you will probably need to use DC/DC converters/regulators as appropriate. USB-5V is on even while the A64 SoC is powered down.

The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3v3 by the phone.

=== Back cover ===
A step file for the back cover for creating custom cases is freely available [https://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp here].

=== Serial console ===

[[File:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter. This shows signals from the PinePhone's point of view, so connect the adapter's Rx to Ring 1 and Tx to Tip]]

The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is set to "on", the headphone connector is in audio mode, if it is set to "off" it's in UART mode. The UART serial connection can also be used for communication with other devices from the PinePhone.

The UART is 115200n8.

The pinout for the serial connector is:

* Tip: RX
* Ring: TX
* Sleeve: GND

You can buy a serial debug cable from the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ PINE64 Store]. The store cable uses a 4 ring plug, as seen in the [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf here], but a 3 ring plug works just as well. The cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used. Because it is a "host"/DTE it means that you need a ''cross modem cable'' ([https://en.wikipedia.org/wiki/Null_modem Null Modem]) with TX on Tip to be connected to RX. A cable like e.g. [https://www.ftdichip.com/Products/Cables/USBTTLSerial.htm FTDI TTL-232R-3V3-AJ] which has TX on Tip and RX on Ring fits perfectly.

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

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.

{| class="wikitable"
|-
! Number
! Name
! Explanation
! Description
|-
| 1
| Modem
| Pulls Q1501 gate up (FET killing modem power)
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| Pulls up CHIP_EN
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| Breaks microphone bias voltage from the SoC
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| Pulls up PWDN on OV5640
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| Pulls up PWDN on GC2145
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| Pulls up IN2 on analog switch BCT4717ETB
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART mode.
|}

== Camera ==

The PinePhone has two cameras, OmniVision OV5640 with 5MP (up to 2592 x 1944 pixels) as rear camera and GalaxyCore GC2145 with 2MP (up to 1600 x 1200 pixels) as front camera.

[[File:Rose.jpg|400px|thumb|none|Example picture taken on the PinePhone's rear camera by Martijn Braam using his app ''Megapixels''.]]

Further details regarding the camera and the Megapixels camera app can be found on [https://blog.brixit.nl/tag/phones/ Martijn's blog].

== Battery ==

The phone ships with a protective plastic sticker between the battery and the phone to protect the device from turning on during shipping. You need to gently open the back cover, then remove the battery and finally remove the sticker and check that the pins aren't bent. Note: If the battery is stuck inside the phone, the mid screw in the lower part of the midframe needs to be slightly loosened, see [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|here]].

{{Info|The EG25-G modem and the RTL8723CS WiFi and Bluetooth do not work without a battery and with a drained battery, even when enough power is supplied to the PinePhone via the USB Type-C port. Most operating systems won't boot without a battery or with a drained battery.}}

The [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf supplied battery] is meant to be compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. The extended life aftermarket BBU does fit, although it is a tight fit.

{{Warning|Using an aftermarket battery with a higher capacity is done at own risk. Batteries with a higher capacity especially in combination with an external charger can lead to overvoltage, which fries the modem and/or the Bluetooth and WiFi chip.}}

The battery terminals, from the nearest to the battery edge to the nearest to the middle of battery, are as follows:

{| class="wikitable"
| style="min-width: 90px; text-align: center;" | +ve
| style="min-width: 90px; text-align: center;" | thermistor
| style="min-width: 90px; text-align: center;" | -ve
| style="min-width: 90px; text-align: center;" | not connected
|}

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 can be recharged by connecting the phone to a charger with a sufficient output. Once it has charged sufficiently you will be able to boot the phone.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

atinout example:
<pre>
echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -
</pre>

minicom example:

<code>minicom -D /dev/ttyUSB2</code>

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

<pre>
AT+QMBNCFG="select","ROW_Generic_3GPP"
</pre>

Then enable Voice over LTE using:

<pre>
AT+QCFG="ims",1
</pre>

And reboot the modem to apply the settings:

<pre>
AT+CFUN=1,1
</pre>

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to poweroff the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===
The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the [[PinePhone#Datasheets for components and peripherals|documentation section]] below.

As with most smartphones, the PinePhone has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Safety ==

=== General recommendations ===

Due to the greater control the user is having over the device and its software comes also greater responsibility. It is necessary to verify the configuration of the device to make sure that responsible settings are used. The different operating systems may come with non-sane default settings, including SSH with weak password authentication being enabled by default and exposed to the public Internet, the absence of a firewall, default passwords, unencrypted files, too high temperature zones and emergency shutoff values or an enabled root account. The usage of public resources to verify such settings (such as the in case of GNU/Linux, the Arch Linux [https://wiki.archlinux.org/title/security security] wiki page, or the [https://wiki.archlinux.org/title/general_recommendations general recommendations]) as well as the corresponding operating system's or distribution's resources are strongly recommended.

=== Charging safety ===

The PinePhone supports up to 5V 3A (15W) Quick Charge, it follows the USB Power Delivery specification. Only compatible phone chargers may be used, charging the phone with incompatible chargers (for example laptop chargers with a higher voltage) is prohibited. Charging the phone releases heat, general safety recommendations must be followed, see the section ''Thermal safety''.

=== Thermal safety ===

With the Allwinner A64 being an older generation SoC with a large 40nm chip, the phone produces quite some heat with medium or higher use and especially also during charging or when using USB accessories, like a docking station. Measurements to prevent damage to the phone and to its surroundings need to be taken by the user. This includes especially a proper handling of the phone: do not charge the phone in a way where heat builds up around the phone without being able to escape. Especially don't charge your phone under a pillow, blankets, in pockets or bags. Charging the phone produces heat and charging the phone in a way, where the excessive heat can't dispose around the phone poses an immediate fire risk.

The user might notice that the phone gets warm under usage, compared to phones with more up-to-date hardware. Under normal circumstances these temperatures don't pose a risk while being in the levels within the safe operating temperatures (which lay far beyond the point where components can be too hot to touch). Higher temperatures might especially be experienced on the top side of the screen and on the inside of the phone at the RF shield of the modem. The higher temperature of the RF shield of the modem is commonly caused by the SoC on the opposite side of the mainboard, the RF shield of the modem is used to disperse heat of the SoC. In newer mainboard revisions starting from 1.2a there are also thermal pads on the back cover and between the SoC's RF shield and the screen, dispersing heat on the screen and on the back cover. In the past there has been safety issues regarding thermal safety functions, causing temperature reads to not properly work over an extended period of time, which was causing heat damage in some cases (see the documentation of that issue by the developer Megous [http://xnux.eu/log/#018 here] and [http://xnux.eu/log/#017 here]). While the developers are working hard to prevent such issues, they can't be excluded under all circumstances (see [[PinePhone#State_of_the_software|state of the software]]). The users are expected to monitor their phones' thermal safety at every point at this state of the software.

It is highly recommend to update the phone on a regular basis to always get the latest improvements. The default settings to throttle the performance and to shut down the phone when reaching critical temperatures might be set to a too high point depending on the specific usage and usage length. Under GNU/Linux the phone's thermal management behavior can be modified via the Thermal Sysfs driver to achieve lower temperatures and preventing the screen and other components to potentially take damage, see [[PinePhone Thermal Tweaks]] for the details.

== Frequently asked questions ==

For a list of frequently asked questions (including information regarding the shipping) see [[PinePhone FAQ]].

== Modifications and repairs ==

=== Swapping in a new mainboard revision ===

The mainboard can be replaced, for example for upgrading to a newer hardware revision or if it is faulty. The replacement board does not have an OS preinstalled, to test if everything is working after swapping the mainboard a flashed SD card is required. The mainboard also comes with a non-functional firmware on the ANX chip, a newer firmware version has to be flashed as explained below to get certain USB functionality to work.

==== Replacing the mainboard ====

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an OS from SD card.}}

Prior to replacing your PinePhone’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the PinePhone’s mainboard.
# Remove the PinePhone’s back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio/ UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Check that the rubber proximity sensor housing is in the chassis, not stuck to the removed mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam can be found here (or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here]):
[[File:Pinephone_martijn_pcb_replacement.png|thumb|none|600px|link=https://www.youtube.com/watch?v=5GbMoZ_zuZs|Watch Martijn Braam's video tutorial here: https://www.youtube.com/watch?v=5GbMoZ_zuZs.]]

==== Flashing the ANX firmware ====

===== Method 1 =====

After swapping the mainboard the ANX7688 chip has to be flashed for full USB functionality.

Under GNU/Linux this can be done by downloading the latest ANX7688 firmware image on the phone:

wget https://xff.cz/git/linux-firmware/plain/anx7688-fw.bin

and executing as root ("sudo su") on the phone:

cp anx7688-fw.bin /lib/firmware/
echo 1 > /sys/class/typec/port0/device/flash_eeprom

===== Method 2 =====

Booting a factory test image will automatically flash the ANX7688 chip. See [[PinePhone Software Releases#Factory Test OS|Factory Test OS]] for such an image.

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Swapping in a new mainboard revision|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.

* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.

* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.

* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a gold-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the PINE64 store ===

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

=== Other hardware issues ===

See also [[PinePhone Hardware Issues]] for more issues and how-to's.

== Press ==

For an overview about media of the PinePhone you can use for the news, blogs, or similar see [[PinePhone Press]].

== PinePhone board information, schematics and certifications ==

PinePhone mainboard schematic:
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2b]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2]
* [[PinePhone_v1.2|PinePhone schematic ver 1.2 change list]]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
* [[PinePhone component list]]

PinePhone USB-C small board schematic:
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component top placement drawing ver 1.0]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component bottom placement drawing ver 1.0]

PinePhone certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20FCC%20SDOC%20Certificate-S19112602605001.pdf PinePhone FCC Certificate]
* [https://fcc.report/FCC-ID/2AWAG-PINEPHONE RF Exposure SAR Information from FCC ID site]
* [https://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinePhone CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]
* Note: PinePhone's Type Allocation Code (TAC) is 86769804

== Datasheets for components and peripherals ==

Allwinner A64 SoC information:
* [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
* [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
* [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

X-Powers AXP803 PMIC (Power Management IC) information:
* [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

eMMC information:
* [https://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC datasheet]

CMOS camera module information:
* [https://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
* [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
* [https://usermanual.wiki/Document/OV5640FirmwareUserGuideV10.952852672.pdf OV5640 Embedded Firmware User Guide – VCM AF Module]
* [https://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
* [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

LCD touch screen panel information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel specification]
* [https://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller datasheet]
* [https://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller datasheet]

Lithium battery information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery specification]
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV curve chart]
* [https://cad.onshape.com/documents/5194d6303f021e6f300b70a0/w/7b63ac4c32ed63dfd78c7840/e/5d43c0ce5b665bae10082a08 PinePhone Lithium Battery 3D onshape drawing]

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

LTE module information:
* [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
* [[File:Quectel_EG25-G_Hardware_Design_V1.4.pdf]]
* [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
* [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]
* [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_GNSS_Application_Note_V1.3.pdf]]

Sensors:
* [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetometer Datasheet]
* [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS datasheet]
* [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]

Digital video to USB-C bridge:
* [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 product brief]

Case information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone case exploded diagram]
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone back cover 3D file]

Other components:
* See the [[PinePhone_component_list|Component List]]

== Resources ==

The following articles contain more specific information:
* [[PinePhone Accessibility]]
* [[PinePhone Power Management]]
* [[PinePhone Security]]
* [[PinePhone UBports OS Design Discussion]]

The following resources have been made available by Ondřej Jirman, a developer for the Pinephone:
* [https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting started with PinePhone Hardware]
* [https://xnux.eu/devices/pine64-pinephone.html State of development progress]
* [https://xnux.eu/log/ Development log]
* [https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]
* [https://xnux.eu/contribute.html Contributions to the kernel development]

== External links ==
* [https://pine64.com/product-category/pinephone/ The PinePhone on the official Pine store]
* [https://pine64.com/product-category/smartphone-spare-parts/ PinePhone spare parts on the official Pine store]
* [https://pine64.com/product-category/smartphone-accessories/ PinePhone accessories on the official Pine store]

[[Category:PinePhone]] [[Category:Allwinner A64]]

PinePhone

2023-10-23T15:22:12Z

Fxc: /* Pogo pins */ Pulled unproblematic information on top

[[File:PinePhone Beta Edition.png|400px|thumb|right|Rendering of the PinePhone Beta Edition]]

The '''PinePhone''' is a smartphone created by PINE64. It is capable of running mainline Linux and is supported by many partner projects.

The Braveheart Edition of the PinePhone was the first publicly available version of the phone. It shipped without a fully functional operating system and was geared specifically towards early adopters. The Braveheart Edition's successors were the Community Editions, which featured a branded backcover and box of selected community projects. The Community Editions became available in June 2020. The Beta Edition featuring Manjaro with Plasma Mobile is the latest edition, it became available in March 2021.

== Introduction ==

The PinePhone is not a regular phone and you might not get the latest and greatest hardware and this years' newest innovation. You will get a device with good mainline support with a great community behind it.

=== State of the software ===

First things first, the PinePhone is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive operating system experience.

Bear in mind that the software for these smartphones is very early, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the community chat (see [[Main Page#Community and Support]])!

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The PinePhone's SIM slot only accepts a micro-SIM, please do not insert a nano-SIM without an adapter and make sure that the nano-SIM does not get released from its adapter. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot.

{{Info|Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the micro-SIM in the lower slot.]]

An adapter from a nano to a micro-SIM might be included under tape in the camera notch of the phone's packaging. Some nano-SIMs will not fit firmly into that adapter that comes with the PinePhone and if the included adapter is used without a well-fitting nano-SIM, the contact pins might get damaged. In that case it is highly recommended to acquire a better fitting adapter.

== Operating systems ==

The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distribution (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for mobile use on devices like the PinePhone.

=== Software releases ===

The [[PinePhone Software Releases]] page has a complete list of currently supported phone-optimized Operating System images that work with the PinePhone as well as other related software information. As soon as more patches get mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device. To update any installed operating system please see [[PinePhone Updating Instructions]].

=== Installation instructions ===

The instructions to install an operating system to the internal memory ("eMMC") or a microSD card can be found here: [[PinePhone Installation Instructions]].

=== Troubleshooting ===

If the PinePhone is not booting from eMMC and/or microSD card anymore it can have two causes:

==== The battery is drained ====

If the battery is fully drained, most operating systems and distributions won't boot anymore. One of the exceptions which still boots is the utility ''Jumpdrive'', which can usually be used to expose the eMMC and microSD card as drives to a USB-connected computer. Mind that JumpDrive won't expose the eMMC and microSD card with a drained battery but it still can be flashed and booted from microSD card to confirm that the phone still functions and boots up fine.

JumpDrive can be downloaded from [https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz here] (not compatible with the PinePhone Pro!).

{{Info|If JumpDrive boots and other releases do not boot, the battery is likely drained. In that case let it charge while running JumpDrive with a compatible charger for multiple hours and make sure to not fully drain the battery in the future anymore, as that significantly reduces the battery lifetime.}}

Alternatively to testing JumpDrive, the issue can also be diagnosed by checking the battery charge. Simply remove the battery from the device and measure the voltage on the (+) and (-) contacts on the battery. Make sure to not shorten the contacts as shorting battery pins is a severe life and safety danger.

==== The installation is corrupted or incorrect ====

If the installation of the prioritized boot medium is corrupted or incorrect, the PinePhone will not boot anymore. The following problems are common:

* The microSD card is in the wrong slot (see [[#First time installation|first time installation]])
* The image file was flashed to partition 1 (example: ''sdx1'', ''nvme0x1p1'') instead of the whole device (example: ''sdx'', ''nvme0x1'')
* An image without bootloader was flashed (mind the ''Tow-Boot'' bootloader requirements of ''Mobian'' and ''postmarketOS'')
* The operating systems got corrupted, for example after running updates (reflash the device, see [[PinePhone Installation Instructions]])
* An incompatible image was flashed (make sure that the images are compatible. Images for the PinePhone Pro won't boot on the PinePhone and vice versa. Check your invoice to see if you ordered a PinePhone or a PinePhone Pro).

== Specifications ==

* '''Dimensions:''' 160.5 x 76.6 x 9.2mm
* '''Weight:''' Between 180 ~ 200 grams
* '''SIM Card:''' Micro-SIM
* '''Display:'''
** '''Size:''' 5.95 inches (151mm) diagonal
** '''Type:''' HD IPS capacitive touchscreen, 16M colors
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64]
* '''RAM:''' 2GB or 3GB LPDDR3 SDRAM
* '''Internal Storage:''' 16GB or 32GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back Camera:''' Single 5MP, 1/4", LED Flash
* '''Front Camera:''' Single 2MP, f/2.8, 1/5"
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot
** '''Bluetooth:''' 4.0, A2DP
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| Rear camera
| OmniVision OV5640
|-
| Camera flash
| SGMICRO SGM3140
|-
| Front camera
| GalaxyCore GC2145
|-
| LCD
| Xingbangda XBD599
|-
| WiFi
| Realtek RTL8723CS
|-
| Bluetooth
| Realtek RTL8723CS
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| Magnetometer
| ST LIS3MDL
|-
| Ambient light / Proximity
| SensorTek STK3335
|-
| Accelerometer / Gyroscope
| InvenSense MPU-6050
|-
| Vibration motor
| Unknown model
|-
| Notification LED
| LED0603RGB
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
| X-Powers AXP803
|-
| Battery fuel gauge
| X-Powers AXP803
|}

See the [[PinePhone_component_list|PinePhone Component List]].

== Hardware revisions ==

[[File:Pinephone_revisions.png|400px|thumb|right|The history of the PinePhone CEs]]

The following are all hardware revisions of the PinePhone that have existed, ordered by the time of their releases:

* [[Project Anakin]] - Development kit
* [[Project Don't be evil]] - Development kit
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] - Developer Edition
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] - Braveheart Edition
* [[PinePhone v1.2]] - Ubports Community Edition
* [[PinePhone v1.2a]] - postmarketOS Community Edition
* [[PinePhone v1.2b]] - Manjaro Community Edition, KDE Community Edition, Mobian Community Edition and Beta Edition

== Hardware accessory ==

=== Add-ons ===
The PinePhone (and PinePhone Pro) is compatible with the official add-on cases, such as the keyboard, the LoRa add-on, the Qi wireless charging add-on and the fingerprint reader add-on. Details can be found under:

* [[PinePhone (Pro) Add-ons]]
* [[PinePhone (Pro) Keyboard]]

=== PinePhone Accessories ===
See [[PinePhone Hardware Accessory Compatibility]] for a list of devices working with the PinePhone (depending on their OS support).

The USB-C can be used to power the device, and offers USB2 host and OTG capabilities, 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, an HDMI port and Ethernet connection.

=== Pogo pins ===

[[File:Pinephone pogo.png|400px|thumb|right|The pogo pins, as visible under the back cover.]]

The PinePhone has six pogo pins on the back allowing for custom hardware extensions such as wireless charging, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power inputs/outputs and an I2C interface.

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| DCIN
| USB-5V
| GND
|}

PINE64 store currently sells the [https://pine64.com/product/pinephone-flex-break-out-board/?v=0446c16e2e66 PinePhone Flex Breakout Board]. With the pitch being 2.54 mm, this Flex Breakout Board may have leads soldered directly to the contacts for use in a solderless board. A non-soldered solution would be to use a [https://www.digikey.com/en/products/detail/te-connectivity-amp-connectors/5-520315-6/2258879 TE AMP Connector] that will accept a Flat Flexible Cable 2.54 mm pitch.

{{Warning|The following information in this subsection is only partially correct. A rewrite is currently pending.}}

DCIN and USB-5V are the names used in the schematics. The actual behavior of these pogo pins is not obvious based on their names. DCIN is connected both to the VBUS line of the USB Type-C connector and to the ACIN/VBUS inputs on the PMIC. This means that, depending on a number of factors, DCIN may be at 0 V or 5 V. USB-5V is connected at the output of an LP6226 DC/DC boost converter (5 V), which in turn is fed by the PS output of the PMIC. The boost converter is enabled or disabled by a GPIO output from the A64 SoC, controlled by software (e.g. the Linux kernel). Depending on inputs and decision made by the PMIC, PS may be at the battery voltage (fed "directly" by the battery through a [https://www.zxcompo.com/ transistor] controlled by the PMIC), or at the "USB" voltage (fed by the PMIC's ACIN/VBUS inputs). This means that depending on a number of factors, USB-5V may be at battery voltage (between 3.0 V and 4.3 V), or at 5 V.

Because the PinePhone may act as a USB host (providing 5 V at the USB Type-C connector's VBUS to a connected device) or as a USB device (drawing from a 5 V source on the USB Type-C connector's VBUS), DCIN is actually not strictly an input nor an output. Some community analysis of the PinePhone schematic (and some testing) indicates that you can connect a 5 V power supply to DCIN in order to power the phone at the PMIC's ACIN/VBUS inputs (and, as a side effect, charge the battery). This may not be safe to do in all conditions, e.g., when the phone is acting as a USB host to a connected USB device. It should also be safe to use DCIN as a power output from the PinePhone, e.g., when a USB Type-C charger is connected, you can draw current directly from the USB Type-C port's VBUS, which is provided by the charger. Please note that, when using DCIN as an output from the PinePhone, DCIN isn't "always on"; it may be 0 V. It is currently not documented on how much current can be safely drawn.

USB-5V should be safe to use as an "always on" power output from the PinePhone. Depending on a number of factors, voltage may be from 3 V to 5 V; thus, if you are using USB-5V to power your pogo-pins expansion board, you will probably need to use DC/DC converters/regulators as appropriate. USB-5V is on even while the A64 SoC is powered down.

The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3v3 by the phone.

For a breakout board see [https://github.com/SMR404/PinephonePogoBreakout here]. For an example project see Martijn's blog post [https://blog.brixit.nl/making-a-backcover-extension-for-the-pinephone/ "Making a backcover extension for the PinePhone"].

=== Back cover ===
A step file for the back cover for creating custom cases is freely available [https://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp here].

=== Serial console ===

[[File:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter. This shows signals from the PinePhone's point of view, so connect the adapter's Rx to Ring 1 and Tx to Tip]]

The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is set to "on", the headphone connector is in audio mode, if it is set to "off" it's in UART mode. The UART serial connection can also be used for communication with other devices from the PinePhone.

The UART is 115200n8.

The pinout for the serial connector is:

* Tip: RX
* Ring: TX
* Sleeve: GND

You can buy a serial debug cable from the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ PINE64 Store]. The store cable uses a 4 ring plug, as seen in the [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf here], but a 3 ring plug works just as well. The cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used. Because it is a "host"/DTE it means that you need a ''cross modem cable'' ([https://en.wikipedia.org/wiki/Null_modem Null Modem]) with TX on Tip to be connected to RX. A cable like e.g. [https://www.ftdichip.com/Products/Cables/USBTTLSerial.htm FTDI TTL-232R-3V3-AJ] which has TX on Tip and RX on Ring fits perfectly.

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

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.

{| class="wikitable"
|-
! Number
! Name
! Explanation
! Description
|-
| 1
| Modem
| Pulls Q1501 gate up (FET killing modem power)
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| Pulls up CHIP_EN
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| Breaks microphone bias voltage from the SoC
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| Pulls up PWDN on OV5640
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| Pulls up PWDN on GC2145
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| Pulls up IN2 on analog switch BCT4717ETB
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART mode.
|}

== Camera ==

The PinePhone has two cameras, OmniVision OV5640 with 5MP (up to 2592 x 1944 pixels) as rear camera and GalaxyCore GC2145 with 2MP (up to 1600 x 1200 pixels) as front camera.

[[File:Rose.jpg|400px|thumb|none|Example picture taken on the PinePhone's rear camera by Martijn Braam using his app ''Megapixels''.]]

Further details regarding the camera and the Megapixels camera app can be found on [https://blog.brixit.nl/tag/phones/ Martijn's blog].

== Battery ==

The phone ships with a protective plastic sticker between the battery and the phone to protect the device from turning on during shipping. You need to gently open the back cover, then remove the battery and finally remove the sticker and check that the pins aren't bent. Note: If the battery is stuck inside the phone, the mid screw in the lower part of the midframe needs to be slightly loosened, see [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|here]].

{{Info|The EG25-G modem and the RTL8723CS WiFi and Bluetooth do not work without a battery and with a drained battery, even when enough power is supplied to the PinePhone via the USB Type-C port. Most operating systems won't boot without a battery or with a drained battery.}}

The [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf supplied battery] is meant to be compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. The extended life aftermarket BBU does fit, although it is a tight fit.

{{Warning|Using an aftermarket battery with a higher capacity is done at own risk. Batteries with a higher capacity especially in combination with an external charger can lead to overvoltage, which fries the modem and/or the Bluetooth and WiFi chip.}}

The battery terminals, from the nearest to the battery edge to the nearest to the middle of battery, are as follows:

{| class="wikitable"
| style="min-width: 90px; text-align: center;" | +ve
| style="min-width: 90px; text-align: center;" | thermistor
| style="min-width: 90px; text-align: center;" | -ve
| style="min-width: 90px; text-align: center;" | not connected
|}

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 can be recharged by connecting the phone to a charger with a sufficient output. Once it has charged sufficiently you will be able to boot the phone.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

atinout example:
<pre>
echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -
</pre>

minicom example:

<code>minicom -D /dev/ttyUSB2</code>

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

<pre>
AT+QMBNCFG="select","ROW_Generic_3GPP"
</pre>

Then enable Voice over LTE using:

<pre>
AT+QCFG="ims",1
</pre>

And reboot the modem to apply the settings:

<pre>
AT+CFUN=1,1
</pre>

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to poweroff the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===
The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the [[PinePhone#Datasheets for components and peripherals|documentation section]] below.

As with most smartphones, the PinePhone has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Safety ==

=== General recommendations ===

Due to the greater control the user is having over the device and its software comes also greater responsibility. It is necessary to verify the configuration of the device to make sure that responsible settings are used. The different operating systems may come with non-sane default settings, including SSH with weak password authentication being enabled by default and exposed to the public Internet, the absence of a firewall, default passwords, unencrypted files, too high temperature zones and emergency shutoff values or an enabled root account. The usage of public resources to verify such settings (such as the in case of GNU/Linux, the Arch Linux [https://wiki.archlinux.org/title/security security] wiki page, or the [https://wiki.archlinux.org/title/general_recommendations general recommendations]) as well as the corresponding operating system's or distribution's resources are strongly recommended.

=== Charging safety ===

The PinePhone supports up to 5V 3A (15W) Quick Charge, it follows the USB Power Delivery specification. Only compatible phone chargers may be used, charging the phone with incompatible chargers (for example laptop chargers with a higher voltage) is prohibited. Charging the phone releases heat, general safety recommendations must be followed, see the section ''Thermal safety''.

=== Thermal safety ===

With the Allwinner A64 being an older generation SoC with a large 40nm chip, the phone produces quite some heat with medium or higher use and especially also during charging or when using USB accessories, like a docking station. Measurements to prevent damage to the phone and to its surroundings need to be taken by the user. This includes especially a proper handling of the phone: do not charge the phone in a way where heat builds up around the phone without being able to escape. Especially don't charge your phone under a pillow, blankets, in pockets or bags. Charging the phone produces heat and charging the phone in a way, where the excessive heat can't dispose around the phone poses an immediate fire risk.

The user might notice that the phone gets warm under usage, compared to phones with more up-to-date hardware. Under normal circumstances these temperatures don't pose a risk while being in the levels within the safe operating temperatures (which lay far beyond the point where components can be too hot to touch). Higher temperatures might especially be experienced on the top side of the screen and on the inside of the phone at the RF shield of the modem. The higher temperature of the RF shield of the modem is commonly caused by the SoC on the opposite side of the mainboard, the RF shield of the modem is used to disperse heat of the SoC. In newer mainboard revisions starting from 1.2a there are also thermal pads on the back cover and between the SoC's RF shield and the screen, dispersing heat on the screen and on the back cover. In the past there has been safety issues regarding thermal safety functions, causing temperature reads to not properly work over an extended period of time, which was causing heat damage in some cases (see the documentation of that issue by the developer Megous [http://xnux.eu/log/#018 here] and [http://xnux.eu/log/#017 here]). While the developers are working hard to prevent such issues, they can't be excluded under all circumstances (see [[PinePhone#State_of_the_software|state of the software]]). The users are expected to monitor their phones' thermal safety at every point at this state of the software.

It is highly recommend to update the phone on a regular basis to always get the latest improvements. The default settings to throttle the performance and to shut down the phone when reaching critical temperatures might be set to a too high point depending on the specific usage and usage length. Under GNU/Linux the phone's thermal management behavior can be modified via the Thermal Sysfs driver to achieve lower temperatures and preventing the screen and other components to potentially take damage, see [[PinePhone Thermal Tweaks]] for the details.

== Frequently asked questions ==

For a list of frequently asked questions (including information regarding the shipping) see [[PinePhone FAQ]].

== Modifications and repairs ==

=== Swapping in a new mainboard revision ===

The mainboard can be replaced, for example for upgrading to a newer hardware revision or if it is faulty. The replacement board does not have an OS preinstalled, to test if everything is working after swapping the mainboard a flashed SD card is required. The mainboard also comes with a non-functional firmware on the ANX chip, a newer firmware version has to be flashed as explained below to get certain USB functionality to work.

==== Replacing the mainboard ====

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an OS from SD card.}}

Prior to replacing your PinePhone’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the PinePhone’s mainboard.
# Remove the PinePhone’s back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio/ UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Check that the rubber proximity sensor housing is in the chassis, not stuck to the removed mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam can be found here (or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here]):
[[File:Pinephone_martijn_pcb_replacement.png|thumb|none|600px|link=https://www.youtube.com/watch?v=5GbMoZ_zuZs|Watch Martijn Braam's video tutorial here: https://www.youtube.com/watch?v=5GbMoZ_zuZs.]]

==== Flashing the ANX firmware ====

===== Method 1 =====

After swapping the mainboard the ANX7688 chip has to be flashed for full USB functionality.

Under GNU/Linux this can be done by downloading the latest ANX7688 firmware image on the phone:

wget https://xff.cz/git/linux-firmware/plain/anx7688-fw.bin

and executing as root ("sudo su") on the phone:

cp anx7688-fw.bin /lib/firmware/
echo 1 > /sys/class/typec/port0/device/flash_eeprom

===== Method 2 =====

Booting a factory test image will automatically flash the ANX7688 chip. See [[PinePhone Software Releases#Factory Test OS|Factory Test OS]] for such an image.

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Swapping in a new mainboard revision|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.

* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.

* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.

* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a gold-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the PINE64 store ===

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

=== Other hardware issues ===

See also [[PinePhone Hardware Issues]] for more issues and how-to's.

== Press ==

For an overview about media of the PinePhone you can use for the news, blogs, or similar see [[PinePhone Press]].

== PinePhone board information, schematics and certifications ==

PinePhone mainboard schematic:
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2b]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2]
* [[PinePhone_v1.2|PinePhone schematic ver 1.2 change list]]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
* [[PinePhone component list]]

PinePhone USB-C small board schematic:
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component top placement drawing ver 1.0]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component bottom placement drawing ver 1.0]

PinePhone certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20FCC%20SDOC%20Certificate-S19112602605001.pdf PinePhone FCC Certificate]
* [https://fcc.report/FCC-ID/2AWAG-PINEPHONE RF Exposure SAR Information from FCC ID site]
* [https://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinePhone CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]
* Note: PinePhone's Type Allocation Code (TAC) is 86769804

== Datasheets for components and peripherals ==

Allwinner A64 SoC information:
* [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
* [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
* [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

X-Powers AXP803 PMIC (Power Management IC) information:
* [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

eMMC information:
* [https://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC datasheet]

CMOS camera module information:
* [https://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
* [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
* [https://usermanual.wiki/Document/OV5640FirmwareUserGuideV10.952852672.pdf OV5640 Embedded Firmware User Guide – VCM AF Module]
* [https://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
* [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

LCD touch screen panel information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel specification]
* [https://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller datasheet]
* [https://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller datasheet]

Lithium battery information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery specification]
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV curve chart]
* [https://cad.onshape.com/documents/5194d6303f021e6f300b70a0/w/7b63ac4c32ed63dfd78c7840/e/5d43c0ce5b665bae10082a08 PinePhone Lithium Battery 3D onshape drawing]

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

LTE module information:
* [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
* [[File:Quectel_EG25-G_Hardware_Design_V1.4.pdf]]
* [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
* [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]
* [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_GNSS_Application_Note_V1.3.pdf]]

Sensors:
* [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetometer Datasheet]
* [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS datasheet]
* [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]

Digital video to USB-C bridge:
* [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 product brief]

Case information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone case exploded diagram]
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone back cover 3D file]

Other components:
* See the [[PinePhone_component_list|Component List]]

== Resources ==

The following articles contain more specific information:
* [[PinePhone Accessibility]]
* [[PinePhone Power Management]]
* [[PinePhone Security]]
* [[PinePhone UBports OS Design Discussion]]

The following resources have been made available by Ondřej Jirman, a developer for the Pinephone:
* [https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting started with PinePhone Hardware]
* [https://xnux.eu/devices/pine64-pinephone.html State of development progress]
* [https://xnux.eu/log/ Development log]
* [https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]
* [https://xnux.eu/contribute.html Contributions to the kernel development]

== External links ==
* [https://pine64.com/product-category/pinephone/ The PinePhone on the official Pine store]
* [https://pine64.com/product-category/smartphone-spare-parts/ PinePhone spare parts on the official Pine store]
* [https://pine64.com/product-category/smartphone-accessories/ PinePhone accessories on the official Pine store]

[[Category:PinePhone]] [[Category:Allwinner A64]]

PinePhone (Pro) Keyboard

2023-10-21T11:01:04Z

Fxc: Reverted edits by Zo (talk) to last revision by Fxc

[[File:PP_KB_Front-1024x576.jpg|400px|thumb|right|Picture of the PinePhone (Pro) Keyboard]]

The '''PinePhone (Pro) Keyboard Case''' is a case compatible with the [[PinePhone]] and [[PinePhone Pro]], adding a keyboard functionality to the phone. It features a clam-shell design and uses the pogo pins located on the smartphone’s midsection and attaches by replacing the default back cover. This add-on effectively turns the PinePhone (Pro) into a PDA with an in-built LTE modem.

== Getting started ==
[[File:Ppkb_description.png|thumb|upright=1.2|
① Contact pads 
② Battery switch 
③ USB-C connector]]

The keyboard case works with both the PinePhone and PinePhone Pro and features a clam-shell design. It uses pogo pins located on the phone’s midsection and attaches by replacing the default back cover. When folded, the phone’s screen and the keyboard rest securely against each other. The hinge features a 180° design, which not only allows for two-hand typing on a surface but also for comfortable thumb-typing when fully extended. The etched keycaps can be easily relocated for alternate layouts such as AZERTY or QWERTZ. The keyboard case runs an [https://xff.cz/git/pinephone-keyboard/ open firmware], which means that anyone with the know-how can alter existing functions or add new ones. The bottom (keyboard) and top (phone) sections of the assembly are well-balanced thanks to the large, 6000mAh, internal battery capable of charging the PinePhone (Pro) during operation. The internal battery effectively triples the phone’s battery life. The internal keyboard battery can be manually toggled on/off and the keyboard’s battery charge level can be read in the supported operating systems; the keyboard remains functional with the battery fully depleted.

You do not lose access to the PinePhone (Pro)’s USB-C port, speaker, microphone, or any external features, such as volume and lock buttons, with the keyboard attached. There is also a cut-out for the camera, torch, and headphone jack. The USB-C port on the keyboard is capable of powering both the keyboard and PinePhone (Pro) simultaneously. This means that you can plug in a USB-C charger into the keyboard to charge the keyboard's internal battery, while the PinePhone (Pro) is charging via the internal connection between phone and keyboard.

{{warning|Do not plug in a charger into the keyboard and the phone at the same time. Using the USB-C port of the PinePhone (Pro) while a charger to is connected to the USB-C port of the keyboard is also discouraged for the same reason. Technical details regarding the issue can be found in the blog post of the developer ''megi'' [http://xnux.eu/log/072.html here], in [https://www.pine64.org/2022/05/31/may-update-worth-the-wait/ this] blog post and the [[PinePhone (Pro) Keyboard#Safety|safety]] section.}}

Please keep in mind that the keyboard case transforms the PinePhone (Pro) into a PDA, which means that taking calls will likely prove awkward without a wired or wireless headset connected (try speakerphone button if available).

=== Mounting the keyboard ===
Power off your PinePhone and remove the back case. To remove the back case of the PinePhone use your fingernail or another soft object to pry up the back case. A notch to easily remove the cover is located at the bottom left of the PinePhone with the backcover facing the user.

Open and place the keyboard flat on a hard surface with the hinge fully extended. Proceed to insert the PinePhone into the keyboard at an angle of approx. 15 degrees. Make sure that the PinePhone’s pogo pins and the corresponding pads ① on the keyboard are aligned. The leading edge with volume and power buttons should make contact first. Firmly press the PinePhone into place. Multiple clicks should be heard as the two snap into place. Pay special attention to the plastic pin below the camera hole. Firmly push from the rear, below the camera hole, to click it into position. Failing to do so may cause an insufficient pin contact and prevent the case from charging the phone.

The PinePhone can be removed from the keyboard easily using a notch similar to the one found on the back case. The notch is located at the bottom of the leading edge with the power and volume buttons.

=== Operation ===
The keyboard will function automatically once a PinePhone running a compatible operating system is mounted. For alterations to physical layout and firmware see the relevant sections respectively.

The keyboard features an in-built 6000mAh battery. The battery can be turned ON/OFF using the button on the right leading edge of the keyboard ②. A short button press activates the internal battery while a long (15 seconds) press or double press deactivates it. Compatible operating systems display both the PinePhone’s and keyboard’s battery status together.

You should charge the PinePhone and the keyboard only using the USB-C ③ port on the keyboard. The keyboard’s USB-C port cannot be used for peripherals. The PinePhone’s USB-C port remains operational when mounted in the keyboard and can be used for data and peripherals.

=== Troubleshooting ===
There are multiple possible hardware issues users could face. It is recommend to check the following most common hardware issues and their solutions and workarounds.

==== Pogo pins not making proper contact ====
Under certain scenarios the keyboard's contacts are not making proper contact with the pogo pins of the phone. To address the issue:

* Power down the phone!
* Apply '''slight''' pressure in the upper mid of the PinePhone's backside until the plastic holder pin towards the upper middle of the keyboard cover, until an audible click can be heard.
* Make sure the contacts and pogo pins are clean and the pogo pins can be slightly pressed individually.
* If the above does not work, a shim under the keyboard's contacts might be required, as explained [https://xnux.eu/pinephone-keyboard/faq.html#ts FAQ troubleshooting section]. See also this [https://freiburg.social/system/media_attachments/files/107/684/243/421/870/279/original/a5e9c68ff3510ec8.jpeg photo of where to place the shim], or [https://www.youtube.com/watch?v=4ixPjz6SPIA this video].

==== Top row is less responsive ====
The keys of the top row may be less responsive. The issue can be worked around by adding inserts to the underside of the top row key caps to decrease the travel distance. More details regarding the workaround can be found in the corresponding section of the FAQ page of the developer megi: https://xnux.eu/pinephone-keyboard/faq.html#ts

==== Software issues ====
For any software issue please see the [[PinePhone (Pro) Keyboard#Software support|Software support section]] and the [[PinePhone (Pro) Keyboard#Frequently asked questions|FAQ section]].

== Safety ==

Do not plug in a charger into the keyboard and the phone at the same time. Doing so may result in damage or loss of the keyboard charging functionality. Using the USB-C port of the PinePhone (Pro) while a charger to is connected to the USB-C port of the keyboard is also discouraged for the same reason. Technical details regarding the issue can be found in the blog post of the developer ''megi'' [http://xnux.eu/log/072.html here] and [https://www.pine64.org/2022/05/31/may-update-worth-the-wait/ this] blog post.

Please note: Only use mild isopropyl alcohol when wiping down the clamshell of the device. Stronger solutions may partially strip the coatings. Do not lube the keyboard with GPL 205G0 switch grease, it can cause problems with the key responsiveness and tactility.

== Software support ==

=== Kernel-space driver ===

Kernel driver implementation from Samuel Holland: CONFIG_IP5XXX_POWER (module ip5xxx_power) and CONFIG_KEYBOARD_PINEPHONE (module pinephone_keyboard) https://github.com/smaeul/linux/commits/wip/pp-keyboard

Note: If you've upgraded to >=5.18, don't forget to upgrade the dtb as kb151 now appears to be a stub.

=== User-space driver ===
The user-space driver is available [https://xff.cz/git/pinephone-keyboard/ here]. Use git to clone the repository. You're going to need sdcc 4.1+ installed to build it, so use your package manager to install that first. Next you'll cd into the directory you cloned pinephone-keyboard and use the command "make" to build. After the build is completed, cd into the build directory and you'll notice several new files starting with ppkb-. To use your keyboard case, you'll want to run the following command: <code>sudo ./ppkb-i2c-inputd</code>  Open something you can type into like a new terminal window or text editor and you should now be able to use the keyboard case!

=== Notes ===
Virtual keyboards such as squeekboard are opening whenever a text field is selected.

To disable this behavior under Linux running '''Phosh''' you can change the corresponding settings under ''Settings'' > ''Accessibility'' > ''Screen Keyboard'' (see [https://forum.pine64.org/showthread.php?tid=15789&pid=105152 here]). The virtual keyboard can also be disabled temporarily for one session using:

* To temporarily disable the virtual keyboard: <code>gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled false</code>

* To temporarily enable the virtual keyboard: <code>gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true</code>

The virtual keyboard needs to be activated before removing the keyboard case again.

Under '''Plasma Mobile''' the keyboard can be disabled via a widget, see [https://forum.pine64.org/showthread.php?tid=14789&pid=105077#pid105077 here].

In '''Sxmo''' disabling the keyboard is not required, as the keyboard will only shown when the corresponding hotkey button is pressed.

== Keyboard layout ==
The keyboard features a default layout (pictured below) created and agreed upon by the community. The keyboard layout can be altered using software as well as by physically repositioning keycaps. All keycaps, with the exception of space and return keys, can be easily and safely relocated for alternative layouts corresponding to software settings.

<gallery mode="nolines" widths="500px" heights="400px">
Image:Ppkb_layout2.png|The keyboard layout how the keys were originally intended
</gallery>

== Keyboard firmware ==
PinePhone’s keyboard firmware was developed independently by Ondřej Jirman as a free-of-charge contribution to PINE64. The firmware source code is freely and publicly available and you can modify it, and the supporting utilities, using common FOSS tools.

=== Firmware and supporting utilities ===
The design of the firmware allows the keys, modifier keys, and their combinations to be handled in virtually unlimited ways, without a need to flash a customized version of the firmware. Mapping of keys is defined at runtime, using the supporting utilities, and is not hardcoded in the firmware. Different keyboard layouts can be loaded dynamically to support various use cases.

The repository that contains the source code of the firmware, supporting utilities and associated documentation is located at https://xnux.eu/pinephone-keyboard/.

You are welcome to contribute patches and improvements to the firmware and the supporting utilities. A summary of firmware development history is available at https://xnux.eu/log/ alongside other development updates from the firmware author.

Much time and effort went into the development of this firmware. If you wish to send a token of appreciation or support the development efforts in any way, please consider making a donation to the author via one of the methods listed at the bottom of this web page: https://xnux.eu/contribute.html.

=== Firmware License ===

<blockquote>Copyright (C) 2021 Ondřej Jirman <megi@xff.cz>

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, with either version 3 of the License or
(at your discretion) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See GNU General Public License for more details.

GNU General Public License http://www.gnu.org/licenses/</blockquote>

== Hardware ==
Key hardware specifications:
* Dimensions (closed): 161 x 95 x 25mm
* Weights (without / with PinePhone mounted): ~ 191 / ~391 grams
* Number of keys: 54
* Number of rows: 5
** Keyboard IC: Keyboard IC: EM85F684A 8-bit microcontroller with 256 bytes RAM, 2048/ bytes XRAM; 16kB for user’s own firmware
* Battery capacity: 6000mAh (22.2Wh 3.7V)
* Charger input: 5V, 3A (15W)
** Charging and battery IC chip: IP5209 power management IC with charge indicate controller and boost converter

== Frequently asked questions ==
{{Under construction}}

''' What is the keyboard driver situation? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#drivers

''' Are keyboard drivers included in my distribution? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#distros

''' What's the status of the existing software for the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#sw-status

''' My keyboard doesn't work (well)! ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#faq-ts

''' How does charging work? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#charging

''' What charger is best for the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#chargers

''' How safe is the charger circuit in the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#safety

''' Keyboard doesn't react to any key presses ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Keyboard works but top row of keys is less responsive ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Phone is not charging from the keyboard ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Phone is charging slowly from the keyboard battery ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts
and https://forum.pine64.org/showthread.php?tid=16979&pid=111414#pid111414#ts

''' Can you open the keyboard and add extra functionality? ''' 
It is possible to do so, however the production units can be extremely difficult to open. Do not attempt to open the keyboard if you do not want to risk cosmetic damage (scaring and scratching of the plastic).

''' How can I rotate the screen display in tty ? ''' 
Under Linux this can be done using the command <code>echo 1 | sudo tee /sys/class/graphics/fbcon/rotate</code>

''' Top row stopped displaying symbols! (kernel > 5.17) ''' 
* For Phosh (at the example of Mobian) see: https://wiki.mobian-project.org/doku.php?id=ppaccessories
* For TTY and SWMO see: https://codeberg.org/HazardChem/PinePhone_Keyboard
* For Plasma Mobile, one of either ''/etc/xdg/kxkbrc'' or ''~/.config/kxkbrc'' is necessary, with contents as described in https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3438

== Documents ==

* [https://files.pine64.org/doc/PinePhone/USER%20MANUAL-KEYBOARD-V2-EN-DE-FR-ES.pdf PinePhone Keyboard 4 language user manual ver 2.0 in PDF format]
* [https://files.pine64.org/doc/PinePhone/USER%20MANUAL-KEYBOARD-V2-EN-DE-FR-ES.odt PinePhone Keyboard 4 language user manual ver 2.0 in ODT format]

== Schematics, Datasheet and certifications ==

* Schematic:
** [https://files.pine64.org/doc/PinePhone/PinePhone%20Keyboard%20Schematic%20V1.0-20211009.pdf PinePhone Keyboard Schematic ver 1.0 20211009]

* Datasheet:
** [https://files.pine64.org/doc/datasheet/pinephone/EM85F684A.pdf PEM85F684A USB Microcontroller Datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/IP5209.pdf IP5209 Power Bank SOC Datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/txs0104e.pdf TXS0104E 4-Bit Bidirectional Voltage-Level Translator Datasheet]

* Certifications:
** [https://files.pine64.org/doc/cert/PinePhone%20Keyboard%20FCC%20Certificate-S21111804102001.pdf PinePhone Keyboard FCC Certificate]
** [https://files.pine64.org/doc/cert/PinePhone%20Keyboard%20CE%20Certificate-S21111804101001.pdf PinePhone Keyboard CE RED Certificate]

== External links ==
* [https://www.pine64.org/2022/01/11/pinephone-pro-explorer-edition-pre-orders-open-january-11/ Pre-order announcement]
* FAQ of the developer megous: https://xnux.eu/pinephone-keyboard/faq.html

[[Category:PinePhone]]
[[Category:PinePhone Pro]]
[[Category:PinePhone (Pro) Add-Ons]]

PinePhone Pro Software State

2023-10-09T07:48:25Z

Fxc: clarified

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>Bootloader</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]. '''Note:''' Tow-Boot is now pre-installed on the SPI from the factory - issues need verification to be issues with Tow-Boot.
|-
| <code>SPI</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Implemented
| Devices bought after end of July 2022 come with Tow-Boot flashed to the SPI memory, making it considerably easier to flash the device and boot from microSD card.
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
|
|-
| <code>Suspend</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Experimental
| Audio is often higher pitched after waking up from suspend due to a bug, make sure to update your system[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report][https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro/-/issues/3 Report]
|-
| <code>Updates</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| [https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem connection crashes frequently, which can lead to missed calls[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34#note_984212350 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report]; Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report][https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro/-/issues/3 Report]
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:lightyellow; text-align:center;" | WIP
| '''Hardware issue'''[https://xnux.eu/log/#055 Details]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | WIP
| Camera work-in-progress with DTS fix[Citation]; userspace still needs to do some catching up[[PinePhone Pro/IMX258 Camera Debugging|debugging article]]; Green image tint[Citation]
|-
| <code>Front camera</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | WIP
| Camera work-in-progress with DTS fix[Citation]; userspace still needs to do some catching up[[PinePhone Pro/IMX258 Camera Debugging|debugging article]]; Green image tint[Citation]
|-
| <code>Camera flash</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical issues
| '''Hardware issue'''[https://xnux.eu/log/#069 Details]; Note: <code>/sys/class/leds/white:flash</code>
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. The firmware does not support monitor mode and package injection. '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[[PinePhone#GPS_/_GNSS|See original PinePhone article]]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| "Geo Magnetic Sensor" (<code>af8133j</code>): Status unknown (at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Working after updating
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The keyboard add-on compatibility is work-in-progress.
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Partial
| Some spare parts now available in the store.[https://pine64.com/product-category/pinephonepro-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Waydroid is an Android container used to run Android applications.
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

[[Category:PinePhone Pro]]

PinePhone Pro Software State

2023-10-09T07:25:37Z

Fxc: Clarified

Presently the PinePhone Pro Explorer Edition is aimed at '''Linux developers with an extensive knowledge of embedded systems and/or experience with mobile Linux'''. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile operating systems, in more general, to reach a higher degree of maturity.

Bear in mind that the software for these smartphones is still in a very early stage, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

The following table lists the feature functionality status of the unaltered pre-installed factory image of the current shipping batch and as comparison an up-to-date reference image (no responsibility is accepted for the accuracy of this information, the list is provided and updated by the community). If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the [[Main Page#Community and Support|community chat]] '''before buying the device''':

* Discord: ''#pinephone'' under https://discord.gg/pine64
* IRC: ''#pinephone'' on ''irc.pine64.org''. Note: please consider Matrix, Discord or Telegram due to the volatile nature of IRC
* Matrix: https://app.element.io/#/room/#pinephone:matrix.org
* Telegram: https://t.me/pinephone

{{Hint|The software is '''written by the community''', any contributions towards the community projects are greatly appreciated! Please see "[[How to Contribute]]" to learn about how to contribute to the software projects and "[[Where to Report Bugs]]" to learn about where to report bugs.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Functionality
! scope="col" style="min-width: 260px;" | Component
! scope="col" style="width: 120px;" | Status (factory)¹
! scope="col" style="width: 120px;" | Status (updated)²
! scope="col" | Notes
|-
! scope="row" rowspan="3" | Bootloader
| <code>Bootloader</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical bugs
| Some critical software bugs currently not fixed yet: A drained battery causes U-Boot to bootloop (cause is known and currently being worked on);[[PinePhone_Pro#The battery is fully drained|Workaround]] Occasionally the eMMC fails to initialize[https://gitlab.com/postmarketOS/pmaports/-/issues/1424 Report]. '''Note:''' Tow-Boot is now pre-installed on the SPI from the factory - issues need verification to be issues with Tow-Boot.
|-
| <code>SPI</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Implemented
| Devices bought after end of July 2022 come with Tow-Boot flashed to the SPI memory, making it considerably easier to flash the device and boot from microSD card.
|-
| <code>Boot GUI</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Currently there is no graphical boot selection implemented[https://tow-boot.org/ Possibly planned]
|-
! scope="row" rowspan="3" | Operating System
| <code>Stability</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
|
|-
| <code>Suspend</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Experimental
| Audio is often higher pitched after waking up from suspend due to a bug, make sure to update your system[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report][https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro/-/issues/3 Report]
|-
| <code>Updates</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The pre-flashed and outdated operating system on the eMMC often gets corrupted after updating[https://forum.pine64.org/showthread.php?tid=15950 Example]; Pacman database lock preventing updates[https://wiki.archlinux.org/title/pacman#%22Failed_to_init_transaction_(unable_to_lock_database)%22_error Solution]; Keyring bug[Solution is to run "pinephonepro-post-install" script as root]
|-
! scope="row" rowspan="5" | Modem
| <code>General</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| [https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; Some carriers blocking specific TANs in their network[[PinePhone Carrier Support]]; '''Note:''' Proprietary firmware
|-
| <code>Phone</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The modem connection crashes frequently, which can lead to missed calls[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34#note_984212350 Report][https://github.com/Biktorgj/pinephone_modem_sdk Alternative firmware]; Slow wakeup[https://gitlab.com/mobian1/devices/eg25-manager/-/issues/34 Report]; bad call audio quality[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/249 Report]; Audio is often higher pitched after waking up from suspend due to a bug[https://github.com/dreemurrs-embedded/Pine64-Arch/issues/381 Report][https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-pinephonepro/-/issues/3 Report]
|-
| <code>SMS</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| SMS functionality is expected to work. In certain cases the functionality might be blocked by a clogged modem[https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/203 Report]; Some bugs
|-
| <code>MMS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| MMS functionality is integrated into the application "Spacebar", some bugs remaining and expected
|-
| <code>Push notifications</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| Receiving push notifications while the phone is suspended is not implemented
|-
! scope="row" rowspan="12" | Components
| <code>LCD</code>
| colspan="2" style="background:lightyellow; text-align:center;" | WIP
| '''Hardware issue'''[https://xnux.eu/log/#055 Details]
|-
| <code>Touch</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Rear camera</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | WIP
| Camera work-in-progress with DTS fix[Citation]; userspace still needs to do some catching up[[PinePhone Pro/IMX258 Camera Debugging|debugging article]]; Green image tint[Citation]
|-
| <code>Front camera</code>
| style="background:lightcoral; text-align:center;" | Not working
| style="background:LightYellow; text-align:center;" | WIP
| Camera work-in-progress with DTS fix[Citation]; userspace still needs to do some catching up[[PinePhone Pro/IMX258 Camera Debugging|debugging article]]; Green image tint[Citation]
|-
| <code>Camera flash</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Critical issues
| '''Hardware issue'''[https://xnux.eu/log/#069 Details]; Note: <code>/sys/class/leds/white:flash</code>
|
|-
| <code>WiFi</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| WiFi is expected to work. Driver does not support monitor mode and package injection. '''Note:''' Proprietary firmware
|-
| <code>Bluetooth</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Bluetooth not necessarily working for calls yet due to missing audio routing[Citation]; Bluetooth in general dodgy under Pulseaudio.[https://wiki.archlinux.org/title/bluetooth_headset#Headset_via_Pipewire Info] '''Note:''' Proprietary firmware
|-
| <code>GNSS/GPS</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| aGPS to be implemented[[PinePhone#GPS_/_GNSS|See original PinePhone article]]; long loading times to get a GPS fix[Citation]; No preinstalled application[Citation]
|-
| <code>Sensors</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| "Geo Magnetic Sensor" (<code>af8133j</code>): Status unknown (at <code>/sys/bus/i2c/devices/4-001c/iio:device1</code>) 
"Accelerometer / Gyroscope" (<code>mpu6500</code>): Working (at <code>/sys/bus/i2c/devices/4-0068/iio:device2</code>) 
"Ambient light / Proximity" (<code>stk3311</code>): Working after updating
|-
| <code>Vibration motor</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Notification LED</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
|
|-
| <code>Buttons</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Power buttons and volume buttons are working.
|-
! scope="row" rowspan="5" | Accessory compatibility, spare parts
| <code>Keyboard Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| The keyboard add-on compatibility is work-in-progress.
|-
| <code>LoRa Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Qi Wireless Charging Add-on</code>
| colspan="2" style="background:LightYellow; text-align:center;" | WIP
| Wireless charging with the add-on case is expected to work to some degree. Certain software functionality and a driver is currently missing[Citation]
|-
| <code>Fingerprint Reader Add-on</code>
| colspan="2" style="background:lightcoral; text-align:center;" | Not implemented
| No software support implemented
|-
| <code>Spare parts</code>
| colspan="2" style="background:LightYellow; text-align:center;" | Partial
| Some spare parts now available in the store.[https://pine64.com/product-category/pinephonepro-spare-parts/ Store]
|-
! scope="row" rowspan="1" | Software notes
| <code>Waydroid</code>
| colspan="2" style="background:LightGreen; text-align:center;" | Working
| Waydroid is an Android container used to run Android applications.
|-
|}

¹ Status of the features at the time of the last factory installation without updates

² Status of the features with an up-to-date reference image

[[Category:PinePhone Pro]]

User:Fxc

2023-09-22T22:41:03Z

Fxc: +1

== Export ==

https://wiki.pine64.org/wiki/Special:AllPages?from=&to=&namespace=0&hideredirects=1

https://wiki.pine64.org/wiki/Special:Export

[[User:Fxc/export]]

Cutoff: 16 April 2023

22 September 2023: PineTab-V, PineTab2

== Wiki keep ==

* [[PinePhone APN Settings]]
* [[PinePhone Carrier Support]]

== Getting started ==

The Ox64 can be flashed using an UART connection or by connecting the device to the computer using USB-C.

=== Using UART ===

To flash the Ox64 using an UART connection, first connect your UART device as pictured below:

[[File:|360px]]

Then do the following steps:

* Do not connect the micro-USB cable or ''VBUS'' yet
* Press and hold the ''BOOT'' button
* Connect the micro-USB cable or connect ''VBUS''
* Wait for a few seconds
* Release the ''BOOT'' button

=== Using USB ===

To flash the Ox64 using a USB-C connection to a computer:

{{Info|This won't be possible on the first batch of Ox64 devices from October 2022, see [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff here].}}

* ...

== Chaos ==
* [[ROCKPro64 Software Releases#Android]]
* [[Special:ListFiles]]
* [[Pinebook Pro]]
* [[Getting started]]
* [[SOEDGE Software Releases]]
* [[PineBuds Pro]] -> stub sections, lacks user manual steps
* [[Special:UncategorizedPages]]
* [[Accessories_Step_by_Step_Guides]] -> Explanation for which devices this applies
* Rename Accessories_Step_by_Step_Guides section to Accessories everywhere
* [[PineTime#Community]] redundant information. Might be solved with a template per article
* [[SOQuartz Software Releases]]

== ChatGPT: Flashing with dd ==
Flashing a disk image to a microSD card using the dd command involves writing the disk image file to the microSD card. This process is performed through the terminal on Linux or macOS. Here are the steps to flash a disk image to a microSD card using <code>dd</code>:

1. Determine the device name of the microSD card: On Linux or macOS, you can use the <code>lsblk</code> or <code>diskutil list</code> command to find the name of the microSD card (e.g., ''/dev/sdb''). Make sure to properly identify the microSD card, as using the wrong device name can result in data loss.

2. Unmount the microSD card: If the microSD card is already mounted, you need to unmount it before flashing the disk image. On Linux, you can use the <code>umount</code> command. On macOS, you can use the <code>diskutil unmount</code> command.

3. On Linux or macOS, open a terminal window.

4. Flash the disk image to the microSD card: Use the following command to flash the disk image to the microSD card:

sudo dd if='''path_to_disk_image.img''' of='''/dev/sdX''' bs=4M conv=fsync

* Replace '''path_to_disk_image.img''' with the path to the disk image file.
* Replace '''/dev/sdX''' with the device name of the microSD card you determined in step 1.

5. Wait for the process to complete: The ''dd'' command will not provide any output until it has completed the process. This may take several minutes, depending on the size of the disk image and the speed of your computer and microSD card.

6. Eject the microSD card: Once the ''dd'' command has completed, eject the microSD card. On Linux, you can use the <code>eject</code> command. On macOS, you can use the <code>diskutil eject</code> command.

Note: Before flashing the disk image, make sure to backup any important data on the microSD card, as this process will erase all existing data on the card.

== ChatGPT: Flashing with Etcher ==
Here are the steps to flash a disk image to a microSD card:

# Download and install a disk image writing tool: A commonly used tool for this purpose is Etcher, which is available for Windows, Mac, and Linux.
# Insert the microSD card into your computer: Make sure that you have an SD card reader, or an adapter to connect the microSD card to your computer.
# Open the disk image writing tool: Launch Etcher and select the disk image file you want to flash to the microSD card.
# Select the target device: In Etcher, select the microSD card from the list of available drives.
# Start the flashing process: Click the "Flash" button to start the process of writing the disk image to the microSD card. This process may take a few minutes, depending on the size of the disk image and the speed of your computer.
# Verify the flash: After the flash is complete, Etcher will verify the integrity of the image to make sure it was written correctly.
# Eject the microSD card: Once the flash is complete and verified, safely eject the microSD card from your computer. You can now use the microSD card with the device it was intended for.

Note: Before flashing the disk image, make sure to backup any important data on the microSD card, as this process will erase all existing data on the card.

== Main example ==

=== Devices ===

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

Phones:
* [[PinePhone]]
* [[PinePhone Pro]]

Phone accessories:
* [[PinePhone (Pro) Add-ons]]
* [[PinePhone (Pro) Keyboard]]

Tablets:
* [[PineNote]]
* [[PineTab]]

Wearable:
* [[PineBuds Pro]]
* [[PineTime]]

Laptops:
* [[Pinebook]], [[1080P Pinebook]], [[Pinebook Pro]] and [[Pinebook Pro Dock|Pinebook Pro Docking station]]

Single-board computers:
* [[Ox64]], [[STAR64]], [[Quartz64]], [[QuartzPro64_Development|QuartzPro64]], [[ROCKPro64]], [[ROCK64]], [[PINE A64]], [[PINE A64-LTS/SOPine|PINE A64-LTS]] and [[PINE H64]]

Set-top box:
* [[RockBox]]

Clusters and modules:
* [[Clusterboard]]
* [[SOPINE]] and [[SOPINE Baseboard]]
* [[SOEDGE]] and [[SOEDGE Baseboard]]
* [[SOQuartz]]

IP camera:
* [[PineCube]]

Makerspace:
* [[Pinecil]], [[PinePower]], [[PineCone]] and [[Pinedio]]

== Pinebook notes ==
Merge https://wiki.pine64.org/wiki/1080P_Pinebook_Software_Releases into https://wiki.pine64.org/wiki/Pinebook_Software_Releases

{| class="wikitable" style="text-align: center;"
|+ Compatibility
|-
! Pinebook 11.6″ !! Pinebook 11.6" 1080p !! Pinebook 14″
|-
| ✅ || ❓ || ❌
|-
|}

== Collapsible test ==

{| role="presentation" class="mw-collapsible mw-collapsed wikitable" style="max-width: 60%"
| Notes
|-
| Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.
|}

PinePhone Carrier Support

2023-09-22T22:39:26Z

Fxc: Formatting

This page contains hints on setting up cellular network connectivity for specific carriers. For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].

== Check compatibility ==

To check if the PinePhone is supported on your carrier:

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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

== Tested and working carriers ==

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

=== Asia ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || SoftBank Mobile || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || 楽天モバイル / Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || 楽天モバイル / Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || NTT Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || China Mobile || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || China Telecom || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| Japan || 楽天モバイル / Rakuten Mobile || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (revised from January 2021)
|-
| China || China Unicom || Yes || Not tested || Yes || Yes || [https://postmarketos.org/ pmOS] 22.06.3 Phosh, [[PineModems#Bootloader_unlocking | BLunlck'd]], [[PinePhone#Firmware_update|upd'd]] to [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_30.006.30.006 *8M2G_30.006*], November 2022
|}

=== Africa ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

=== Europe ===
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Fello (uses Telia network) || Yes || No (data and MMS APN are different) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Hallon (uses Tre network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Comviq (uses Tele2 network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested (should NOT work, data and MMS APN are different) || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || RWG || Yes || Not tested || Yes || Yes [https://neilzone.co.uk/2022/06/rwg-mobile-apn-for-non-data-sims (special APN)] || postmarketOS Phosh (Edge) - 11 March 2023
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| UK || Honest Mobile (Three) || Yes || No || Yes || Yes || postmarketOS 23.06 (Phosh) - 9 July 2023
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || Plasma Mobile
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

=== North America ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
* Arch Linux Arm (Phosh,SXMO) 2021/04/29
* Manjaro - Phosh 2021/04/29
* Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
* Manjaro - Plasma Dev 2020/11/21
* Ubuntu Touch - 2020/11/26
* KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
* Mobian - Phosh 2021/3/14
* postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
* Ubuntu Touch 2021/5/24
* Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
* DanctNIX (Arch Linux ARM) - Phosh 2023/03/29
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
* DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
* postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
* Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
* Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
* Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
* Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
* Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
* postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
* Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
* Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
* Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
* Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
* Mobian - Phosh Weekly 2022/04/13
* PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
* PostmarketOS - Phosh v21.12 (stable) 2022/04/13
* PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
* PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
* Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
* Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

=== South America ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

=== Australia / Oceania ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Aldi Mobile（Telstra） || Yes || Untested || Yes || Untested || Mobian, mobian 6.1-rockchip kernel, 2023-06-08 with Phosh and Plasma (modem needs to be enabled from Phosh)
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Kogan Mobile（Vodafone） || Yes || Yes after manually configure MMS APN in Phosh Chat || Yes || Yes || Mobian, mobian 6.1-rockchip kernel, 2023-06-08 with Phosh and Plasma (modem needs to be enabled from Phosh)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

=== Middle East ===
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-
|}

== Special carrier notes ==

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:

=== USA ===

==== AT&T ====

According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.

==== Consumer Cellular ====

Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.

==== Cricket Wireless ====

Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).

==== Faith Wireless ====

Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

==== SimpleMobile ====

SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.

==== Sprint ====

Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

==== T-Mobile ====

According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], T-Mobile's primary frequency band for the United States is 12 (700ac MHz).

T-Mobile's bands and protocols are summarized on [https://www.frequencycheck.com/carriers/t-mobile-united-states this page].

While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.

==== Verizon ====

According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on [https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.

==== TracFone ====

Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

==== Google Fi ====

Only T-Mobile service works currently, not US Cellular or Sprint. The APN is <code>h2g2</code>. Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.

=== Europe ===

==== Telekom Germany ====

With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.

==== Orange Poland ====

Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

==== Sweden ====

Calls, SMS, and data (2G, 3G, and 4G) should work out of the box (tested three carriers on Mobian Phosh). On about half of Swedish carriers, MMS works when set manually, the rest have different data APN and MMS APN. VoLTE (i.e. 4G calls) did not work out of the box ([https://github.com/Eliot-Roxbergh/notes_pinephone for me]) but worked well after [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md#adsp-versions updating firmware] to ADSP Version 01.003.01.003 and installing [https://github.com/the-modem-distro/pinephone_modem_sdk Pinephone Modem SDK]. Regarding call quality, from my experience; 3G has the best quality, then 4G also works well although you often hear electrical white noise sound (on your side), 2G works well but there is a risk of strong noise when on bad coverage (this can affect both sides of the call). Voicemail should work, you should get a SMS when you have a missed call etc. Only issue I had was that when getting sent to voicemail in a call, for some target carriers (?) it was completely silent.

=== Asia ===

==== China Telecom ====

The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:

AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1

==== SoftBank ====

SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. A free SIM is available, but that one is data only. The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

== Known issues ==

Known issues:

* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

== MMS workarounds ==

These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

== Resources ==

* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]

[[Category:PinePhone]]

User:Fxc

2023-09-22T21:20:53Z

Fxc:

== Export ==

https://wiki.pine64.org/wiki/Special:AllPages?from=&to=&namespace=0&hideredirects=1

https://wiki.pine64.org/wiki/Special:Export

[[User:Fxc/export]]

Cutoff: 16 April 2023

22 September 2023: PineTab-V, PineTab2

== Getting started ==

The Ox64 can be flashed using an UART connection or by connecting the device to the computer using USB-C.

=== Using UART ===

To flash the Ox64 using an UART connection, first connect your UART device as pictured below:

[[File:|360px]]

Then do the following steps:

* Do not connect the micro-USB cable or ''VBUS'' yet
* Press and hold the ''BOOT'' button
* Connect the micro-USB cable or connect ''VBUS''
* Wait for a few seconds
* Release the ''BOOT'' button

=== Using USB ===

To flash the Ox64 using a USB-C connection to a computer:

{{Info|This won't be possible on the first batch of Ox64 devices from October 2022, see [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff here].}}

* ...

== Chaos ==
* [[ROCKPro64 Software Releases#Android]]
* [[Special:ListFiles]]
* [[Pinebook Pro]]
* [[Getting started]]
* [[SOEDGE Software Releases]]
* [[PineBuds Pro]] -> stub sections, lacks user manual steps
* [[Special:UncategorizedPages]]
* [[Accessories_Step_by_Step_Guides]] -> Explanation for which devices this applies
* Rename Accessories_Step_by_Step_Guides section to Accessories everywhere
* [[PineTime#Community]] redundant information. Might be solved with a template per article
* [[SOQuartz Software Releases]]

== ChatGPT: Flashing with dd ==
Flashing a disk image to a microSD card using the dd command involves writing the disk image file to the microSD card. This process is performed through the terminal on Linux or macOS. Here are the steps to flash a disk image to a microSD card using <code>dd</code>:

1. Determine the device name of the microSD card: On Linux or macOS, you can use the <code>lsblk</code> or <code>diskutil list</code> command to find the name of the microSD card (e.g., ''/dev/sdb''). Make sure to properly identify the microSD card, as using the wrong device name can result in data loss.

2. Unmount the microSD card: If the microSD card is already mounted, you need to unmount it before flashing the disk image. On Linux, you can use the <code>umount</code> command. On macOS, you can use the <code>diskutil unmount</code> command.

3. On Linux or macOS, open a terminal window.

4. Flash the disk image to the microSD card: Use the following command to flash the disk image to the microSD card:

sudo dd if='''path_to_disk_image.img''' of='''/dev/sdX''' bs=4M conv=fsync

* Replace '''path_to_disk_image.img''' with the path to the disk image file.
* Replace '''/dev/sdX''' with the device name of the microSD card you determined in step 1.

5. Wait for the process to complete: The ''dd'' command will not provide any output until it has completed the process. This may take several minutes, depending on the size of the disk image and the speed of your computer and microSD card.

6. Eject the microSD card: Once the ''dd'' command has completed, eject the microSD card. On Linux, you can use the <code>eject</code> command. On macOS, you can use the <code>diskutil eject</code> command.

Note: Before flashing the disk image, make sure to backup any important data on the microSD card, as this process will erase all existing data on the card.

== ChatGPT: Flashing with Etcher ==
Here are the steps to flash a disk image to a microSD card:

# Download and install a disk image writing tool: A commonly used tool for this purpose is Etcher, which is available for Windows, Mac, and Linux.
# Insert the microSD card into your computer: Make sure that you have an SD card reader, or an adapter to connect the microSD card to your computer.
# Open the disk image writing tool: Launch Etcher and select the disk image file you want to flash to the microSD card.
# Select the target device: In Etcher, select the microSD card from the list of available drives.
# Start the flashing process: Click the "Flash" button to start the process of writing the disk image to the microSD card. This process may take a few minutes, depending on the size of the disk image and the speed of your computer.
# Verify the flash: After the flash is complete, Etcher will verify the integrity of the image to make sure it was written correctly.
# Eject the microSD card: Once the flash is complete and verified, safely eject the microSD card from your computer. You can now use the microSD card with the device it was intended for.

Note: Before flashing the disk image, make sure to backup any important data on the microSD card, as this process will erase all existing data on the card.

== Main example ==

=== Devices ===

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

Phones:
* [[PinePhone]]
* [[PinePhone Pro]]

Phone accessories:
* [[PinePhone (Pro) Add-ons]]
* [[PinePhone (Pro) Keyboard]]

Tablets:
* [[PineNote]]
* [[PineTab]]

Wearable:
* [[PineBuds Pro]]
* [[PineTime]]

Laptops:
* [[Pinebook]], [[1080P Pinebook]], [[Pinebook Pro]] and [[Pinebook Pro Dock|Pinebook Pro Docking station]]

Single-board computers:
* [[Ox64]], [[STAR64]], [[Quartz64]], [[QuartzPro64_Development|QuartzPro64]], [[ROCKPro64]], [[ROCK64]], [[PINE A64]], [[PINE A64-LTS/SOPine|PINE A64-LTS]] and [[PINE H64]]

Set-top box:
* [[RockBox]]

Clusters and modules:
* [[Clusterboard]]
* [[SOPINE]] and [[SOPINE Baseboard]]
* [[SOEDGE]] and [[SOEDGE Baseboard]]
* [[SOQuartz]]

IP camera:
* [[PineCube]]

Makerspace:
* [[Pinecil]], [[PinePower]], [[PineCone]] and [[Pinedio]]

== Pinebook notes ==
Merge https://wiki.pine64.org/wiki/1080P_Pinebook_Software_Releases into https://wiki.pine64.org/wiki/Pinebook_Software_Releases

{| class="wikitable" style="text-align: center;"
|+ Compatibility
|-
! Pinebook 11.6″ !! Pinebook 11.6" 1080p !! Pinebook 14″
|-
| ✅ || ❓ || ❌
|-
|}

== Collapsible test ==

{| role="presentation" class="mw-collapsible mw-collapsed wikitable" style="max-width: 60%"
| Notes
|-
| Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.
|}

User:Thomzane/Woodpecker

2023-09-22T21:03:17Z

Fxc: Fxc moved page Woodpecker to User:Thomzane/Woodpecker: Draft

{{Under construction}}

The '''Woodpecker''' Edition Serial Console is powered by the CH340G chipset enabled simple USB to Serial communication for PINE64 related project development.

The S1 jumper can be set to 5V or 3.3V.

[https://pine64.com/product/serial-console-woodpecker-edition/ PINE64 store page]

PineTab2

2023-09-18T20:36:35Z

Fxc: typo

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. A similarly packaged RISC-V tablet is the [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first box includes:

* the PineTab2,
* a short user guide,
* a power cable and
* the UART adapter. Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden.

The second box has the keyboard in it.

=== First start ===

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

=== Keyboard cover ===

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.
The external keyboard has 5 connection pins (the golden pins). four are standard USB connectors and one is used to detect that the keyboard is connected.

The backlight can be changed with the key combination ''Pinekey + Ctrl (right)''.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The releases for the PineTab2 can be found under [[PineTab2 Releases]].

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. '''In some cases''' it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings. 

To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device in the box also containing the charging cable. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|thumb|400px|right|Tablet's side ports: USB-C (with PD), MicroSD, USB-C 3.0, volume rocker, power button]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi: BES2600
*** Driver under development, use a USB wifi dongle for now
** Bluetooth: BES2600
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 + PD (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Sensors:'''
** Accelerometer: Silan SC7A20
** Ambient Light & Proximity Sensor
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Weight:''' 538g
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[PineTab2_FAQ#Performing_USB_Tethering_with_an_Android_Phone|USB tether a phone]] or [[PineTab2_FAQ#Selecting_a_USB_WIFI_Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_top-20230417.pdf PineTab2 PCB Component Reference location v2.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_bottom-20230417.pdf PineTab2 PCB Component Reference location v2.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab2 certifications:
* [https://files.pine64.org/doc/cert/Pinetab2%20FCC-SDOC%20Certificate-LCSA040323223E.pdf PineTab2 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab2%20CE%20RED%20Certificate-LCSA040323224E.pdf PineTab2 CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20CE%20EMC%20Certificate-LCSA040323225E.pdf PineTab2 CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20ROHS%20Report-LCSA040323221R.pdf PineTab2 ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMMC Certificate]

PineTab2 disassembly guide:
* [[file:PineTab2_display_panel_disassembly_guide.pdf]]
* Note: this is a very delicate operation esp. around the corners of the screen. Several (even experienced) users ended up damaging the screen.

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:

* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

== Tutorials and Frequently Asked Questions ==
Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:40:16Z

Fxc: /* Follow-Up Comments */ fix

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images:

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up cmments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:39:50Z

Fxc: /* Partition the microSD Card */ fix

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images:

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-Up Comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:39:31Z

Fxc: /* Build Mobian Partition */ fix

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD Card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images:

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-Up Comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:39:15Z

Fxc: /* Build PostmarketOS Partition */ fix

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD Card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images:

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian Partition ====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-Up Comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:39:08Z

Fxc: /* Flash rk2Aw Loader to SPI */ fix

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD Card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images:

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian Partition ====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS Partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-Up Comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:38:26Z

Fxc: /* Multi-Distro on MicroSD Card */ Fixes

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD Card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images:

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian Partition ====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS Partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw Loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-Up Comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:36:42Z

Fxc: /* Get Image Files for the Distros */ Fixes

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-Distro on MicroSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash Rk2Aw Loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build Multi-Distro on SD Card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary erase SD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the MicroSD Card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distros.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images:

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian Partition ====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS Partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw Loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-Up Comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:36:03Z

Fxc: /* Multi-Distro on eMMC */ Fixes

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-Distro on MicroSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash Rk2Aw Loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build Multi-Distro on SD Card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary erase SD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the MicroSD Card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distros.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get Image Files for the Distros ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian Partition ====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS Partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw Loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

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.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-Up Comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:34:47Z

Fxc: /* Multi-Distro on MicroSD Card */ Fixes

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-Distro on MicroSD Card ==

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

=== Flash Rk2Aw Loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

=== Build Multi-Distro on SD Card ===

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary erase SD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the MicroSD Card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distros.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get Image Files for the Distros ====

Change the directory to the ''Downloads'' folder:

cd ~/Downloads

Download your chosen image from [[PinePhone Pro Software Releases]]. Example releases (update the syntax to newer releases):

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the images

sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check mounted images:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

==== Build Arch Linux partition ====

Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Manjaro partition ====

As for previous step proceed for next partition:

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Mobian Partition ====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS Partition ====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build Ubuntu Touch partition ====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

=== Multi-Distro on eMMC ===

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

==== Flash Rk2Aw Loader to SPI ====

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

==== Build Multi-Distro eMMC ====

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.

===== Mount the Images =====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Prepare eMMC =====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Build Phosh Partition =====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build SXMO Partition =====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Follow-Up Comments ====
# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:30:44Z

Fxc: fix

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

=== Multi-Distro on MicroSD Card ===

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

==== Flash Rk2Aw Loader to SPI ====

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

==== Build Multi-Distro on SD Card ====

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary erase SD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

===== Partition the MicroSD Card =====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distros.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

===== Get Image Files for the Distros =====
Enter to Directory
cd ~/Downloads

Download your chosen image from wiki.pine64.org/wiki/PinePhone_Pro_Software_Releases
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the Compressed Files
xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the Images
sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check Mounted Images
lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

===== Build Archlinux Partition =====
Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build Manjaro Partition =====

As for previous step proceed for next partition.

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build Mobian Partition =====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

===== Build PostmarketOS Partition =====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build UbuntuTouch Partition =====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

=== Multi-Distro on eMMC ===

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

==== Flash Rk2Aw Loader to SPI ====

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

==== Build Multi-Distro eMMC ====

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.

===== Mount the Images =====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Prepare eMMC =====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Build Phosh Partition =====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build SXMO Partition =====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Follow-Up Comments ====
# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:30:12Z

Fxc: Added wiki-specifics

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using '''rk2aw'''.

=== Multi-Distro on MicroSD Card ===

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

==== Flash Rk2Aw Loader to SPI ====

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

==== Build Multi-Distro on SD Card ====

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary erase SD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

===== Partition the MicroSD Card =====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distros.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

===== Get Image Files for the Distros =====
Enter to Directory
cd ~/Downloads

Download your chosen image from wiki.pine64.org/wiki/PinePhone_Pro_Software_Releases
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the Compressed Files
xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the Images
sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check Mounted Images
lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

===== Build Archlinux Partition =====
Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build Manjaro Partition =====

As for previous step proceed for next partition.

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build Mobian Partition =====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

===== Build PostmarketOS Partition =====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build UbuntuTouch Partition =====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

=== Multi-Distro on eMMC ===

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

==== Flash Rk2Aw Loader to SPI ====

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

==== Build Multi-Distro eMMC ====

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.

===== Mount the Images =====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Prepare eMMC =====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Build Phosh Partition =====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build SXMO Partition =====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Follow-Up Comments ====
# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

[[Category:PinePhone Pro]]

User:Giorez/Rk2Aw draft

2023-09-09T20:28:46Z

Fxc: Fxc moved page User:Giorez/Rk2Aw draft to PinePhone Pro/Create a multi-distribution image using rk2aw: As discussed in the chat

#REDIRECT [[PinePhone Pro/Create a multi-distribution image using rk2aw]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-09-09T20:28:46Z

Fxc: Fxc moved page User:Giorez/Rk2Aw draft to PinePhone Pro/Create a multi-distribution image using rk2aw: As discussed in the chat

=== Multi-Distro on MicroSD Card ===

This section explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

==== Flash Rk2Aw Loader to SPI ====

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh

==== Build Multi-Distro on SD Card ====

Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

lsblk ''# show /loop, /sd references''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
blkid ''# show UUID for the partition''

If necessary erase SD card

sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

===== Partition the MicroSD Card =====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distros.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

===== Get Image Files for the Distros =====
Enter to Directory
cd ~/Downloads

Download your chosen image from wiki.pine64.org/wiki/PinePhone_Pro_Software_Releases
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230203/archlinux-pinephone-pro-sxmo-20230203.img.xz
wget https://github.com/manjaro-pinephone/plasma-mobile/releases/download/beta15-rc4/Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20230903.img.xz
wget https://images.postmarketos.org/bpo/v23.06/pine64-pinephonepro/phosh/20230904-0846/20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
# to do (postmarketOS-edge-phosh via BootStrap)
wget https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/4961858606/artifacts/file/ubuntu-touch-pinephone-unified.img.xz

Extract the Compressed Files
xz -v -d -k archlinux-pinephone-pro-sxmo-20230203.img.xz
xz -v -d -k Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20230903.img.xz
xz -v -d -k 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img.xz
xz -v -d -k ubuntu-touch-pinephone-unified.img.xz

Mount the Images
sudo su # login with your psw
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img && losetup -P /dev/loop2 Manjaro-ARM-plasma-mobile-pinephonepro-beta15-rc4.img && losetup -P /dev/loop3 mobian-pinephonepro-phosh-20230903.img && losetup -P /dev/loop4 20230904-0846-postmarketOS-v23.06-phosh-22.2-pine64-pinephonepro.img && losetup -P /dev/loop5 ubuntu-touch-pinephone-unified.img

ls -l /mnt/

mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root && mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root && mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root && mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root && mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root

mkdir /mnt/archlinuxsd && mkdir /mnt/manjarosd && mkdir /mnt/mobiansd && mkdir /mnt/postmarketossd && mkdir /mnt/ubuntutouchsd

mount /dev/loop1p1 /mnt/archlinux/boot/ && mount /dev/loop1p2 /mnt/archlinux/root/ && mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/ && mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/ && mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/ && mount /dev/loop5p1 /mnt/ubuntutouch/boot/ && mount /dev/loop5p2 /mnt/ubuntutouch/root/

Check Mounted Images
lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:0 0 122M 0 part /mnt/archlinux/boot
└─loop1p2 259:1 0 3.4G 0 part /mnt/archlinux/root
loop2 7:2 0 6.3G 0 loop
├─loop2p1 259:2 0 457.8M 0 part /mnt/manjaro/boot
└─loop2p2 259:3 0 5.8G 0 part /mnt/manjaro/root
loop3 7:3 0 5.6G 0 loop
├─loop3p1 259:4 0 511M 0 part /mnt/mobian/boot
└─loop3p2 259:5 0 5.1G 0 part /mnt/mobian/root
loop4 7:4 0 2.3G 0 loop
├─loop4p1 259:6 0 243M 0 part /mnt/postmarketos/boot
└─loop4p2 259:7 0 2.1G 0 part /mnt/postmarketos/root
loop5 7:5 0 3.7G 0 loop
├─loop5p1 259:10 0 380.5M 0 part /mnt/ubuntutouch/boot
└─loop5p2 259:11 0 3.4G 0 part /mnt/ubuntutouch/root
sdb 8:16 1 58.3G 0 disk
├─sdb1 8:17 1 16M 0 part
├─sdb2 8:18 1 11G 0 part
├─sdb3 8:19 1 11G 0 part
├─sdb4 8:20 1 11G 0 part
├─sdb5 8:21 1 11G 0 part
├─sdb6 8:22 1 11G 0 part
└─sdb7 8:23 1 3.2G 0 part

===== Build Archlinux Partition =====
Login as root, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/archlinuxsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=fd049b8e-615f-4efd-bc96-622c4d40e6cb / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

mkdir /mnt/archlinuxsd/boot/extlinux

sudo su
cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build Manjaro Partition =====

As for previous step proceed for next partition.

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG

sudo su
cat << EOF > /mnt/manjarosd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# PARTUUID=362866dc-95cf-4069-9bb8-623aa3cdcb5d / ext4 defaults 0 1
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

mkdir /mnt/manjarosd/boot/extlinux

sudo su
cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build Mobian Partition =====

As for previous step proceed for next partition.

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo su
cat << EOF > /mnt/mobiansd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=31e45541-2b52-413a-9217-060082ce2ce8 / ext4 defaults,x-systemd.growfs 0 1
# UUID=05106761-0b87-4729-a7f5-5a5a055c5e69 /boot ext4 defaults,x-systemd.growfs 0 2
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

===== Build PostmarketOS Partition =====

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot

sudo su
cat << EOF > /mnt/postmarketossd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# <file system> <mount point> <type> <options> <dump> <pass>
#UUID=11f02090-b971-4739-a68d-c6e633b371f9 / ext4 defaults 0 0
#UUID=A84E-596C /boot fat32 defaults 0 0
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
## /boot/extlinux/extlinux.conf
## IMPORTANT WARNING
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initrdfs
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build UbuntuTouch Partition =====

sudo dd if=/dev/loop5p2 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo su
cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
#UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 / ext4 defaults 0 1
#UUID=657dc3ea-dcfa-498b-a231-dbc29f6e1bfb /boot ext4 defaults 0 2
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo su
cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
##
## IMPORTANT WARNING
##
## The configuration of this file is generated automatically.
## Do not edit this file manually, use: u-boot-update
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine
initrd /boot/initrd.img-6.5.0-okpine
fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

#label l0r
# menu label UT rescue
# linux /boot/vmlinuz-6.5.0-okpine
# initrd /boot/initrd.img-6.5.0-okpine
# fdtdir /boot/dtb-6.5.0-okpine/
# append root=UUID=dec2be75-3594-4078-b8c9-f3b215e6eac3 console=ttyS2,115200n8 consoleblank=0 loglevel=7 rw spl>
EOF

Unmount all /dev
sudo umount /mnt/archlinuxsd /mnt/manjarosd /mnt/mobiansd /mnt/postmarketossd /mnt/ubuntutouchsd /mnt/*/boot /mnt/*/root

=== Multi-Distro on eMMC ===

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

==== Flash Rk2Aw Loader to SPI ====

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

==== Build Multi-Distro eMMC ====

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.

===== Mount the Images =====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Prepare eMMC =====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

===== Build Phosh Partition =====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

===== Build SXMO Partition =====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Follow-Up Comments ====
# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

PinePhone Pro

2023-09-09T20:23:23Z

Fxc: Reverted edits by Giorez (talk) to last revision by Fxc

[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]

The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

The PinePhone Pro is PINE64’s second smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a open system stack. Achieving this goal will, however, take time as the software and overall smartphone software ecosystem needs to mature.

=== State of the software ===
([[PinePhone Pro Software State|view separately]])

{{:PinePhone Pro Software State}}

=== Editions and revisions ===
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.

* [[PinePhone Pro Developer Edition]]
* PinePhone Pro Explorer Edition

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this Wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time setup ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Devices shipped after the end of July 2022 do only accept a nano-SIM, the SIM is inserted into a carriage released by slightly pulling on the handle in the lower slot (for information regarding devices shipped prior to end of July 2022 see below).

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the SIM card in the lower slot.]]

{{Info|Information regarding devices shipped prior to end of July 2022: The PinePhone Pros shipped prior to the end of July 2022 come with a micro-SIM slot instead of a nano-SIM slot. Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

== Software ==

The software section explains how to install the available software releases for the PinePhone Pro to the internal eMMC or a microSD card, how to boot them and how to solve common booting issues.

=== Software releases ===

The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.

{{Info|Images of the regular PinePhone are not compatible with the PinePhone Pro.}}

=== Boot order ===

The RK3399S processor in the PinePhone Pro searches for the bootloader (such as ''U-Boot'' or ''Tow-Boot'') in the following order:

# SPI flash
# eMMC (the internal memory)
# MicroSD card

==== Boot from microSD card temporarily ====

To temporarily boot from an inserted '''microSD card''' do the following:

* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while powering on the device. The batches bought after July 2022 come with ''Tow-Boot'' flashed to the SPI, which offers additional functionality over ''U-Boot'' as bootloader.

* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the cover for a few seconds, while powering on the device. If the button is labeled ''RESET'' instead of ''RE'' please verify if the device is a regular [[PinePhone]] (or the Developer Edition). This is required because older batches don't ship with ''Tow-Boot'' on the SPI. Flashing ''Tow-Boot'' can be caught up by following [https://tow-boot.org/devices/pine64-pinephonePro.html this] instruction. Note: If ''Tow-Boot'' is flashed later, the microSD card can be selected at boot with the volume down key as well.

* On the '''Developer Edition (sold to selected developers only)''' the SPI and the eMMC can be bypassed by shorting the bypass test points while booting. The process is explained in the article [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation|PinePhone Pro Developer Edition]]. Please join the community chat for any questions regarding the process.

The RE button disables the SPI and the eMMC at the hardware level while the button is held and the PinePhone Pro will try to boot from the next available boot medium, which is the microSD card. Note: When holding the ''RE'' button (or when shorting the contact points in case of the ''Developer Edition'') for a longer time at boot the operating system will not initialize the SPI and eMMC and it will not be possible to write to these storage mediums until the next reboot.

{{Template:Info|The bootloader uses its own boot order for loading the kernel and other core operating system components at boot, which for example may result in the boot loader residing on the eMMC loading and booting the kernel from a microSD card.}}

==== Boot from microSD card permanently ====

The bootloader (such as ''U-Boot'') resides in the free space in front of the first partition. Wiping the bootloader from the eMMC to make the PinePhone Pro boot from microSD card can be done using <code>sudo dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=400 conv=fsync</code>. Formatting the drive or deleting the partition table is not sufficient to wipe the bootloader.

==== Notes ====

If you received your device after July of 2022, the bootloader (''Tow-Boot'') resides on the SPI. To boot to an SD card, place the SD card in your PinePhone Pro and turn it on. The phone will vibrate once. At this point, hold down the volume down button until you feel the device vibrate again then release the button. The LED color should change to blue and your display should remain black for a few seconds. In a few seconds you should see the SD card booting, the indications of which are dependent on what image you chose. If the LED is flashing instead, the boot from SD failed. Erasing the SPI can be achieved via the Tow-Boot installer image. Instructions are available here [https://tow-boot.org/devices/pine64-pinephonePro.html Tow-Boot PinePhone Pro Instructions].

See [[RK3399 boot sequence]] for further details regarding the boot sequence.

=== Installation instructions ===

The software releases can be installed (the process is being referred to as ''flashing'') to the eMMC or to an microSD card.

==== Flashing to microSD card ====
To install an image to the microSD card:

# Download a compatible image from [[PinePhone Pro Software Releases]].
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Write the image to your microSD card using your favorite method, examples:
#* Using ''dd'': On the device you're flashing the microSD card from, find the correct device under <code>lsblk</code> and then flash the image to the microSD card using <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>. Make sure the target is the whole microSD card and not its first partition (''sdc1'' or ''mmcblk0p1'' are wrong!).
#* Using ''bmaptool'': Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device: Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 GB file.
#* Using ''a graphical tool'': A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
# Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore, see [[:File:Pinephone_slots.png|here]].
# Boot the device using the following method:
#* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while booting.
#* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the back cover while booting (or use the ''volume down key'' if you flashed ''Tow-Boot'').
#* On the '''Developer Edition (sold to selected developers only)''' apply the bypass by shorting the testing pads while booting according to the datasheet (or use the ''volume down key'' if you flashed ''Tow-Boot'').

Details regarding the boot order can be found in the [[PinePhone Pro#Boot order|Boot order]] section.

==== Flashing to the eMMC ====
Flashing to the eMMC (the internal memory of the PinePhone Pro) can either be done using ''Tow-Boot'''s USB Mass Storage mode (see [[#Boot order]] if you are unsure if the device comes with Tow-Bot pre-installed) or by booting an operating system from the microSD card (see the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]) and by writing to the eMMC directly from there:

By using Tow-Boot:

# Power off the device
# Power on the device and hold the ''volume up'' key before and during the second vibration
# The LED will turn blue if done successfully. This will only work if Tow-Boot is installed
# When connecting the device to a computer via USB it will behave like an USB drive now
# Check if the eMMC appears under <code>lsblk</code>, the output might look like the following:
#: '''''mmcblk2''' 179:0 0 115.2G 0 disk''
#: ''├─mmcblk2p1 179:1 0 122M 0 part /boot''
#: ''└─mmcblk2p2 179:2 0 115.1G 0 part /''
#: {{Info|In this example, '''/dev/mmcblk2''' is the device, while ''mmcblk2p1'' and ''mmcblk2p2'' are partitions of the device. The downloaded images are images from full devices, which means that the full device (''mmcblk2'' in this example) needs to be flashed. Ignore the partitions!}}
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/'''DEVICE''' bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'' and replace ''DEVICE'' with the correct device from the ''lsblk'' command)
# Reboot the PinePhone Pro

By booting a microSD card:

# Boot an operating system [[PinePhone Pro#Flashing to microSD card|from the microSD card]]. If there is already a bootloader on the eMMC installed see the section [[PinePhone Pro#Boot order|Boot order]] to bypass it.
# Download or copy the desired image to the microSD card as file
# Check if the eMMC appears under <code>lsblk</code>. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/mmcblk2 bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'').
# Reboot the PinePhone Pro

=== Troubleshooting ===

If the PinePhone Pro is not booting (either booting incompletely into a boot splash or tty or if the PinePhone Pro is showing no signs of life) this will typically have the following two reasons:

==== The battery is fully drained ====

If the battery is drained then the board can reset during boot causing a boot loop because of undervoltage condition. It can happen on all stages of the boot including ''U-Boot'' bootloader, display initialization and USB (re-)configuration. In that case it is not possible to charge the phone. The battery can be charged by interrupting the boot loop by booting the PinePhone Pro into ''Maskrom mode'' or by charging the battery externally. It is possible to follow these instructions without a computer by using a wall charger, however it would not be possible to determine if Maskrom mode was started successfully. To boot the PinePhone Pro into ''Maskrom mode'':

* Remove any microSD card from the phone and keep it removed for the below procedure
* Remove the battery, any USB cable and any serial cable
* Reinsert the battery
* Hold the ''RE'' button underneath the back cover of your ''Explorer Edition'' (or short the bypass contact points on the ''Developer Edition'')
{{Info|Confirm that the label of the button says ''RE'' and not ''RESET''! If the button label says ''RESET'' instead you probably have a regular PinePhone and you're reading the wrong page.}}
* Connect the phone to an USB port of a computer, while still holding the button for some time
* Confirm if the phone was booted in Maskrom mode:
** On ''Linux'' check if the Maskrom mode appears as device in the output of the terminal command <code>lsusb</code> on the computer, the expected ''VID:PID'' of the device is ''2207:330c''.
** On ''Windows'' this can be checked using the ''Device Manager'' and checking the VID "2207" and PID "330c" of an ''Unknown device'' appears.
** On ''macOS'' this can be checked in ''/Applications/Utilities/System Information.app'' under ''USB'' and by checking if the VID "2207" and PID "330c" is appearing for a ''Composite Device''.
* Let the phone charge for multiple hours

{{Info|If the device doesn't appear under ''lsusb'' please try again with a different known good USB-C cable and make sure that there is no microSD card in the phone inserted.}}

The device should now be able to boot from the boot medium again. If that is not the case the installation got corrupted, as explained below.

==== The installation is corrupted ====
The PinePhone Pro won't be able to boot if the installation on the SPI flash, the eMMC or the microSD card got corrupted. To boot a working operating system:

* Prepare a microSD card as explained in the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]
* Remove any USB-C cable or device or add-on case from the PinePhone Pro
* Make sure the device is powered off by shortly removing the battery for a second
* Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore.
* Power on the device while bypassing the SPI and eMMC as explained under [[PinePhone Pro#Boot order|Boot order]]

The device should now boot from the microSD card. If the phone does not boot from the microSD card the microSD card was flashed with an incompatible image or the battery got drained as explained above.

=== Bootloaders ===
The following section contains notes regarding compatible bootloaders with the PinePhone Pro.

==== U-Boot ====
The pre-installed operating system on the PinePhone Pro Explorer Edition, if sold prior to the end of July of 2022, is using [[U-Boot]] as default bootloader. Batches sold after July of 2022 are using ''Tow-Boot''

==== Tow-Boot ====
Current batches of the PinePhone Pro ship with ''Tow-Boot'' pre-installed to the SPI flash, which is an opinionated distribution of ''U-Boot'' and brings numerous advantages over stock ''U-Boot'', such as the possibility to choose from booting the eMMC or microSD card using the volume buttons during boot, as well as a ''USB Mass Storage mode'', where the device can be written to by connecting the device to a computer via USB.

The user can flash Tow-Boot to the PinePhone Pro using the [https://tow-boot.org/devices/pine64-pinephonePro.html instructions on the Tow-Boot website].

==== levinboot ====
The levinboot bootloader is another option for the PinePhone Pro. The project repository can be found [https://gitlab.com/DeltaGem/levinboot/-/tree/master/ here]. (Pinephone Pro supporting fork is [https://xff.cz/git/levinboot/ here].)

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

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.

{| class="wikitable"
|-
! Number
! Name
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART¹ mode.
|}

¹ Note: The baud rate may be 1500000 instead of 115200.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

''atinout'' example:

echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -

''minicom'' example:

minicom -D /dev/ttyUSB2

=== VoLTE ===

The PinePhone and PinePhone Pro modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

AT+QMBNCFG="select","ROW_Generic_3GPP"

Then enable Voice over LTE using:

AT+QCFG="ims",1

And reboot the modem to apply the settings:

AT+CFUN=1,1

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to power off the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone Pro. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone and PinePhone Pro modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===

The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the documentation section.

As with most smartphones, the PinePhone Pro has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone Pro may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Nano-SIM (Micro-SIM before 07/2022)
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''NOR Flash:''' Listed as [GigaDevices] GD25LQ128EWIGR, but physical inspection found a SiliconKaiser SK25LP128.
* '''Back Camera:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' Wi-Fi 802.11AC, hotspot capable + Bluetooth V5.0
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery; unglue bottom black plastic with your nail from Samsung battery before installation in order to match the dimensions)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Modifications and repairs ==

Most parts are available from the [https://pine64.com/product-category/pinephonepro-spare-parts/ Pine store]. Take care to use this link to avoid unintentionally ordering parts for the original PinePhone instead.

=== Replacing the mainboard ===

The mainboard can be replaced if it is faulty. The replacement board does not have an operating system pre-installed, to test if everything is working after swapping the mainboard a flashed SD card is required.

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an operating system from a microSD card.}}

Prior to replacing your PinePhone Pro’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the mainboard.
# Remove the phone's back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone, including the screw under the warranty sticker.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio and UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam for the regular PinePhone can be found [https://www.youtube.com/watch?v=5GbMoZ_zuZs here] or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here].

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Replacing the mainboard|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.
* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.
* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.
* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a silver-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the Pine Store ===

The following parts are not available on the Pine Store for the '''regular PinePhone'''. The replacements are listed below and have not been validated for the PinePhone Pro.

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| LCD
| Himax HX8394 compatible
|-
| Rear camera
| IMX258
|-
| Front camera
| OV8858
|-
| Camera flash
| AW3641EDNR
|-
| WiFi + Bluetooth
| [https://www.azurewave.com/img/wireless-modules/AW_CM256SM_DS_Rev15_CYW.pdf AzureWave AW-CM256SM]
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| <s>3 Axis Magnetometer</s>
| <s>[https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL]</s> '''''Note:''''' The ''AF8133J'' is used instead.
|-
| Geo Magnetic Sensor
| [http://www.voltafield.com/products01.html Voltafield AF8133J]
|-
| Ambient light / Proximity
| STK3311-A
|-
| Accelerometer / Gyroscope
| [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6500/ TDK MPU-6500]
|-
| Vibration motor
|
|-
| Notification LED
| LED0603RGB
|-
| Audio Codec
| ALC5616 and ALC5640
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| [https://rockchip.fr/RK818%20datasheet%20V1.0.pdf RK818]
|}

== Datasheets, schematics and certifications ==

PinePhone Pro mainboard schematic:
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf PinePhone Pro mainboard Explorer Edition Released Schematic ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-top.pdf PinePhone Pro mainboard Explorer Edition component top placement ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-bottom.pdf PinePhone Pro mainboard Explorer Edition component bottom placement ver 1.0 20211127]

PinePhone Pro USB-C small board schematic:
* TBD

Certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20FCC%20Certificate-S21101902805001.pdf PinePhone Pro FCC Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20SAR%20Evaluation%20Report-S21101902806001.pdf PinePhone Pro SAR Evaluation Report]
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20CE%20RED%20Certificate-S21101902802-R1.pdf PinePhone Pro CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20RoHS%20Test%20Report.pdf PinePhone Pro ROHS Test Report]

== Factory Test Build for Hardware Checking ==
[[File:PPP_Abdroid_Test_Utility-5.jpg|400px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by the support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, take out the PinePhone Pro Explorer Edition, then insert it into microSD slot (upper slot).
* Insert battery, press the RE button (bypass SPI and eMMC boot) underneath the back cover while plugging in the USB-C power. After 3 seconds release the RE button.
* When powering up, a battery icon screen will show up blow, press power key for two seconds, then the Rockchip logo screen shows up.


* Wait for the home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that the SD test is disabled due in this is SD boot build.
* After running a particular test function, please snapshot the test result and pass it back to support team

Notes:
* Please insert a functional SIM card when performing the SIM test
* When perform GPS test, the first result may fail and please ignore this false message.
* For light sensing test, please have a light shine to the PinePhone Pro when performing the test.


== Using Factory Test Build for Battery charging ==
[[File:PPP_Abdroid_Test_Utility-1.jpg|300px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and battery will start charging.
* The battery icon display for few seconds and then LCD panel turn off while charging. To check charging status, just quick press power button (about 0.5 second) and battery icon will display progress.

== Press ==

For an overview about media of the PinePhone Pro you can use for the news, blogs, or similar see [[PinePhone Press]].

== External links ==
* [https://www.pine64.org/pinephonepro/ Product Page]
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement

[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]

User:Thomzane/Woodpecker

2023-09-05T20:35:04Z

Fxc: +templ

Main Page

2023-09-05T20:34:05Z

Fxc: Undo revision 20608 by Thomzane (talk). Draft article. Link once ready. Please let the mods edit the main page instead

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the [[PINE64 brand and logo|article about our brand and logo]].

== Devices ==

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Phone accessories: '''[[PinePhone (Pro) Add-ons]]''' and '''[[PinePhone (Pro) Keyboard]]'''
* Tablets: '''[[PineTab]]''', '''[[PineTab2]]''', '''[[PineTab-V]]''' and '''[[PineNote]]'''
* Wearable: '''[[PineBuds Pro]]''', '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''' and '''[[Pinebook Pro]]'''
* Laptop accessories: '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Ox64]]''', '''[[STAR64]]''', '''[[Quartz64]]''', '''[[QuartzPro64_Development|QuartzPro64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS]]''', '''[[PINE H64 Model A]]''' and '''[[PINE H64|PINE H64 Model B]]'''
* Set-top box: '''[[RockBox]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPINE]]''', '''[[SOPINE Baseboard]]''', '''[[SOEDGE]]''', '''[[SOEDGE Baseboard]]''', and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Power adapter: '''[[PinePower]]'''
* Soldering iron: '''[[Pinecil]]'''
* Makerspace: '''[[PineCone]]''' and '''[[Pinedio]]'''

== Community and Support ==

Community collaboration and support is focused around the chat platforms and forums described below. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

=== Chat Platforms ===

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

{{hint|PINE64 community is not some always responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently.
* The activity of community members varies depending on the time of day and the number of active users.
* Whether your questions will be answered & whether the answers are right and definitive, depends on the information you provide, and, after all, difficulty of your questions & community members' ability.
* Read [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] to learn more.
* Please read [[PINE64 Community Rules and Code of Conduct]].

'''Note:'''
* PINE64 uses a bridge bot (''[https://github.com/42wim/matterbridge matterbridge]'' with some modifications), which allows Discord, IRC, Matrix, and Telegram users to see and participate in the community chat.
* The bot name is "Pine64 Protocol Droid" and if you see this, look in the message to see the actual author of the message.
* When the bot relays messages it will show the platform the user is using: ''[D]'' for ''Discord'', ''[I]'' for ''IRC'', ''[M]'' for ''Matrix'' and ''[T]'' for ''Telegram''.
}}

The community chat platforms are the following:

* '''Discord''': use this '''[https://discord.gg/pine64 Invite Link]'''. All PINE64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below.
* '''IRC''': the server is irc.pine64.org. Use <code>/list</code> command or the table below to see the full list of channels.
* '''Matrix and Telegram''': See the table below.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://matrix.to/#/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://matrix.to/#/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://matrix.to/#/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://matrix.to/#/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://matrix.to/#/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://matrix.to/#/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz-dev
|-
| Star64
| [https://matrix.to/#/#star64:matrix.org #star64:matrix.org]
| [https://t.me/star64_sbc @star64-sbc]
| Unavailable
|-
| Pinebook and Pinebook Pro
| [https://matrix.to/#/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://matrix.to/#/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://matrix.to/#/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://matrix.to/#/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://matrix.to/#/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #Pinetime
|-
| PineTime Development
| [https://matrix.to/#/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| PineBuds Pro
| [https://matrix.to/#/#pinebuds:matrix.org #pinebuds:matrix.org]
| [https://t.me/+nJVhM0mZ9KhlYmZl @pinebuds]
| Unavailable
|-
| Pinecil
| [https://matrix.to/#/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinecil Development
| [https://matrix.to/#/#pinecil-dev:matrix.org #pinecil-dev:matrix.org]
| [https://t.me/+8_pdKqXrVuQ4OTk1 Pinecil-dev]
| Unavailable
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| PineCube
| [https://matrix.to/#/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker, Ox64
| [https://matrix.to/#/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://matrix.to/#/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://matrix.to/#/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

There is also an unofficial Matrix Space at [https://matrix.to/#/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.

=== Forums ===

PINE64 runs an official forum powered by the open-source forum server software ''MyBB''. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

== Helpful Information for Beginners ==

* '''[[Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[How to Contribute]]''': Information about how to contribute to different partner projects
* '''[[Where to Report Bugs]]''': Information about how to report bugs
* '''[[Project]]''': A variety of well documented PINE64 projects to serve as inspiration

PinePhone (Pro) Keyboard

2023-08-31T14:50:16Z

Fxc: /* Safety */ Added sentence

PinePhone (Pro) Keyboard

2023-08-31T14:49:19Z

Fxc: /* Getting started */ Clarified wording

[[File:PP_KB_Front-1024x576.jpg|400px|thumb|right|Picture of the PinePhone (Pro) Keyboard]]

The '''PinePhone (Pro) Keyboard Case''' is a case compatible with the [[PinePhone]] and [[PinePhone Pro]], adding a keyboard functionality to the phone. It features a clam-shell design and uses the pogo pins located on the smartphone’s midsection and attaches by replacing the default back cover. This add-on effectively turns the PinePhone (Pro) into a PDA with an in-built LTE modem.

== Getting started ==
[[File:Ppkb_description.png|thumb|upright=1.2|
① Contact pads 
② Battery switch 
③ USB-C connector]]

The keyboard case works with both the PinePhone and PinePhone Pro and features a clam-shell design. It uses pogo pins located on the phone’s midsection and attaches by replacing the default back cover. When folded, the phone’s screen and the keyboard rest securely against each other. The hinge features a 180° design, which not only allows for two-hand typing on a surface but also for comfortable thumb-typing when fully extended. The etched keycaps can be easily relocated for alternate layouts such as AZERTY or QWERTZ. The keyboard case runs an [https://xff.cz/git/pinephone-keyboard/ open firmware], which means that anyone with the know-how can alter existing functions or add new ones. The bottom (keyboard) and top (phone) sections of the assembly are well-balanced thanks to the large, 6000mAh, internal battery capable of charging the PinePhone (Pro) during operation. The internal battery effectively triples the phone’s battery life. The internal keyboard battery can be manually toggled on/off and the keyboard’s battery charge level can be read in the supported operating systems; the keyboard remains functional with the battery fully depleted.

You do not lose access to the PinePhone (Pro)’s USB-C port, speaker, microphone, or any external features, such as volume and lock buttons, with the keyboard attached. There is also a cut-out for the camera, torch, and headphone jack. The USB-C port on the keyboard is capable of powering both the keyboard and PinePhone (Pro) simultaneously. This means that you can plug in a USB-C charger into the keyboard to charge the keyboard's internal battery, while the PinePhone (Pro) is charging via the internal connection between phone and keyboard.

{{warning|Do not plug in a charger into the keyboard and the phone at the same time. Using the USB-C port of the PinePhone (Pro) while a charger to is connected to the USB-C port of the keyboard is also discouraged for the same reason. Technical details regarding the issue can be found in the blog post of the developer ''megi'' [http://xnux.eu/log/072.html here], in [https://www.pine64.org/2022/05/31/may-update-worth-the-wait/ this] blog post and the [[PinePhone (Pro) Keyboard#Safety|safety]] section.}}

Please keep in mind that the keyboard case transforms the PinePhone (Pro) into a PDA, which means that taking calls will likely prove awkward without a wired or wireless headset connected (try speakerphone button if available).

=== Mounting the keyboard ===
Power off your PinePhone and remove the back case. To remove the back case of the PinePhone use your fingernail or another soft object to pry up the back case. A notch to easily remove the cover is located at the bottom left of the PinePhone with the backcover facing the user.

Open and place the keyboard flat on a hard surface with the hinge fully extended. Proceed to insert the PinePhone into the keyboard at an angle of approx. 15 degrees. Make sure that the PinePhone’s pogo pins and the corresponding pads ① on the keyboard are aligned. The leading edge with volume and power buttons should make contact first. Firmly press the PinePhone into place. Multiple clicks should be heard as the two snap into place. Pay special attention to the plastic pin below the camera hole. Firmly push from the rear, below the camera hole, to click it into position. Failing to do so may cause an insufficient pin contact and prevent the case from charging the phone.

The PinePhone can be removed from the keyboard easily using a notch similar to the one found on the back case. The notch is located at the bottom of the leading edge with the power and volume buttons.

=== Operation ===
The keyboard will function automatically once a PinePhone running a compatible operating system is mounted. For alterations to physical layout and firmware see the relevant sections respectively.

The keyboard features an in-built 6000mAh battery. The battery can be turned ON/OFF using the button on the right leading edge of the keyboard ②. A short button press activates the internal battery while a long (15 seconds) press or double press deactivates it. Compatible operating systems display both the PinePhone’s and keyboard’s battery status together.

You should charge the PinePhone and the keyboard only using the USB-C ③ port on the keyboard. The keyboard’s USB-C port cannot be used for peripherals. The PinePhone’s USB-C port remains operational when mounted in the keyboard and can be used for data and peripherals.

=== Troubleshooting ===
There are multiple possible hardware issues users could face. It is recommend to check the following most common hardware issues and their solutions and workarounds.

==== Pogo pins not making proper contact ====
Under certain scenarios the keyboard's contacts are not making proper contact with the pogo pins of the phone. To address the issue:

* Power down the phone!
* Apply '''slight''' pressure in the upper mid of the PinePhone's backside until the plastic holder pin towards the upper middle of the keyboard cover, until an audible click can be heard.
* Make sure the contacts and pogo pins are clean and the pogo pins can be slightly pressed individually.
* If the above does not work, a shim under the keyboard's contacts might be required, as explained [https://xnux.eu/pinephone-keyboard/faq.html#ts FAQ troubleshooting section]. See also this [https://freiburg.social/system/media_attachments/files/107/684/243/421/870/279/original/a5e9c68ff3510ec8.jpeg photo of where to place the shim], or [https://www.youtube.com/watch?v=4ixPjz6SPIA this video].

==== Top row is less responsive ====
The keys of the top row may be less responsive. The issue can be worked around by adding inserts to the underside of the top row key caps to decrease the travel distance. More details regarding the workaround can be found in the corresponding section of the FAQ page of the developer megi: https://xnux.eu/pinephone-keyboard/faq.html#ts

==== Software issues ====
For any software issue please see the [[PinePhone (Pro) Keyboard#Software support|Software support section]] and the [[PinePhone (Pro) Keyboard#Frequently asked questions|FAQ section]].

== Safety ==

Do not plug in a charger into the keyboard and the phone at the same time. Doing so may result in damage or loss of the keyboard charging functionality. Technical details regarding the issue can be found in the blog post of the developer ''megi'' [http://xnux.eu/log/072.html here] and [https://www.pine64.org/2022/05/31/may-update-worth-the-wait/ this] blog post.

Please note: Only use mild isopropyl alcohol when wiping down the clamshell of the device. Stronger solutions may partially strip the coatings. Do not lube the keyboard with GPL 205G0 switch grease, it can cause problems with the key responsiveness and tactility.

== Software support ==

=== Kernel-space driver ===

Kernel driver implementation from Samuel Holland: CONFIG_IP5XXX_POWER (module ip5xxx_power) and CONFIG_KEYBOARD_PINEPHONE (module pinephone_keyboard) https://github.com/smaeul/linux/commits/wip/pp-keyboard

Note: If you've upgraded to >=5.18, don't forget to upgrade the dtb as kb151 now appears to be a stub.

=== User-space driver ===
The user-space driver is available [https://xff.cz/git/pinephone-keyboard/ here]. Use git to clone the repository. You're going to need sdcc 4.1+ installed to build it, so use your package manager to install that first. Next you'll cd into the directory you cloned pinephone-keyboard and use the command "make" to build. After the build is completed, cd into the build directory and you'll notice several new files starting with ppkb-. To use your keyboard case, you'll want to run the following command: <code>sudo ./ppkb-i2c-inputd</code>  Open something you can type into like a new terminal window or text editor and you should now be able to use the keyboard case!

=== Notes ===
Virtual keyboards such as squeekboard are opening whenever a text field is selected.

To disable this behavior under Linux running '''Phosh''' you can change the corresponding settings under ''Settings'' > ''Accessibility'' > ''Screen Keyboard'' (see [https://forum.pine64.org/showthread.php?tid=15789&pid=105152 here]). The virtual keyboard can also be disabled temporarily for one session using:

* To temporarily disable the virtual keyboard: <code>gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled false</code>

* To temporarily enable the virtual keyboard: <code>gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true</code>

The virtual keyboard needs to be activated before removing the keyboard case again.

Under '''Plasma Mobile''' the keyboard can be disabled via a widget, see [https://forum.pine64.org/showthread.php?tid=14789&pid=105077#pid105077 here].

In '''Sxmo''' disabling the keyboard is not required, as the keyboard will only shown when the corresponding hotkey button is pressed.

== Keyboard layout ==
The keyboard features a default layout (pictured below) created and agreed upon by the community. The keyboard layout can be altered using software as well as by physically repositioning keycaps. All keycaps, with the exception of space and return keys, can be easily and safely relocated for alternative layouts corresponding to software settings.

<gallery mode="nolines" widths="500px" heights="400px">
Image:Ppkb_layout2.png|The keyboard layout how the keys were originally intended
</gallery>

== Keyboard firmware ==
PinePhone’s keyboard firmware was developed independently by Ondřej Jirman as a free-of-charge contribution to PINE64. The firmware source code is freely and publicly available and you can modify it, and the supporting utilities, using common FOSS tools.

=== Firmware and supporting utilities ===
The design of the firmware allows the keys, modifier keys, and their combinations to be handled in virtually unlimited ways, without a need to flash a customized version of the firmware. Mapping of keys is defined at runtime, using the supporting utilities, and is not hardcoded in the firmware. Different keyboard layouts can be loaded dynamically to support various use cases.

The repository that contains the source code of the firmware, supporting utilities and associated documentation is located at https://xnux.eu/pinephone-keyboard/.

You are welcome to contribute patches and improvements to the firmware and the supporting utilities. A summary of firmware development history is available at https://xnux.eu/log/ alongside other development updates from the firmware author.

Much time and effort went into the development of this firmware. If you wish to send a token of appreciation or support the development efforts in any way, please consider making a donation to the author via one of the methods listed at the bottom of this web page: https://xnux.eu/contribute.html.

=== Firmware License ===

<blockquote>Copyright (C) 2021 Ondřej Jirman <megi@xff.cz>

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, with either version 3 of the License or
(at your discretion) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See GNU General Public License for more details.

GNU General Public License http://www.gnu.org/licenses/</blockquote>

== Hardware ==
Key hardware specifications:
* Dimensions (closed): 161 x 95 x 25mm
* Weights (without / with PinePhone mounted): ~ 191 / ~391 grams
* Number of keys: 54
* Number of rows: 5
** Keyboard IC: Keyboard IC: EM85F684A 8-bit microcontroller with 256 bytes RAM, 2048/ bytes XRAM; 16kB for user’s own firmware
* Battery capacity: 6000mAh (22.2Wh 3.7V)
* Charger input: 5V, 3A (15W)
** Charging and battery IC chip: IP5209 power management IC with charge indicate controller and boost converter

== Frequently asked questions ==
{{Under construction}}

''' What is the keyboard driver situation? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#drivers

''' Are keyboard drivers included in my distribution? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#distros

''' What's the status of the existing software for the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#sw-status

''' My keyboard doesn't work (well)! ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#faq-ts

''' How does charging work? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#charging

''' What charger is best for the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#chargers

''' How safe is the charger circuit in the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#safety

''' Keyboard doesn't react to any key presses ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Keyboard works but top row of keys is less responsive ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Phone is not charging from the keyboard ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Phone is charging slowly from the keyboard battery ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts
and https://forum.pine64.org/showthread.php?tid=16979&pid=111414#pid111414#ts

''' Can you open the keyboard and add extra functionality? ''' 
It is possible to do so, however the production units can be extremely difficult to open. Do not attempt to open the keyboard if you do not want to risk cosmetic damage (scaring and scratching of the plastic).

''' How can I rotate the screen display in tty ? ''' 
Under Linux this can be done using the command <code>echo 1 | sudo tee /sys/class/graphics/fbcon/rotate</code>

''' Top row stopped displaying symbols! (kernel > 5.17) ''' 
* For Phosh (at the example of Mobian) see: https://wiki.mobian-project.org/doku.php?id=ppaccessories
* For TTY and SWMO see: https://codeberg.org/HazardChem/PinePhone_Keyboard
* For Plasma Mobile, one of either ''/etc/xdg/kxkbrc'' or ''~/.config/kxkbrc'' is necessary, with contents as described in https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3438

== Documents ==

* [https://files.pine64.org/doc/PinePhone/USER%20MANUAL-KEYBOARD-V2-EN-DE-FR-ES.pdf PinePhone Keyboard 4 language user manual ver 2.0 in PDF format]
* [https://files.pine64.org/doc/PinePhone/USER%20MANUAL-KEYBOARD-V2-EN-DE-FR-ES.odt PinePhone Keyboard 4 language user manual ver 2.0 in ODT format]

== Schematics, Datasheet and certifications ==

* Schematic:
** [https://files.pine64.org/doc/PinePhone/PinePhone%20Keyboard%20Schematic%20V1.0-20211009.pdf PinePhone Keyboard Schematic ver 1.0 20211009]

* Datasheet:
** [https://files.pine64.org/doc/datasheet/pinephone/EM85F684A.pdf PEM85F684A USB Microcontroller Datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/IP5209.pdf IP5209 Power Bank SOC Datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/txs0104e.pdf TXS0104E 4-Bit Bidirectional Voltage-Level Translator Datasheet]

* Certifications:
** [https://files.pine64.org/doc/cert/PinePhone%20Keyboard%20FCC%20Certificate-S21111804102001.pdf PinePhone Keyboard FCC Certificate]
** [https://files.pine64.org/doc/cert/PinePhone%20Keyboard%20CE%20Certificate-S21111804101001.pdf PinePhone Keyboard CE RED Certificate]

== External links ==
* [https://www.pine64.org/2022/01/11/pinephone-pro-explorer-edition-pre-orders-open-january-11/ Pre-order announcement]
* FAQ of the developer megous: https://xnux.eu/pinephone-keyboard/faq.html

[[Category:PinePhone]]
[[Category:PinePhone Pro]]
[[Category:PinePhone (Pro) Add-Ons]]

PINE A64

2023-08-27T08:43:21Z

Fxc: /* Software releases */ Specified the section, removed old mentions

[[File:PINEA64_sideimg.jpg|400px|thumb|right|The PINE A64]]

The '''PINE A64''' and the '''PINE A64+''' is ''PINE64's'' first Single Board Computer powered by Allwinner’s A64 quad-core ARM Cortex A53 64-Bit SoC. There are many Operating Systems available for the PINE A64 created by the open source community and various partner projects. Currently the majority of Linux distributions for the PINE A64 are using mainline Linux but there are a number of BSP-based distribution and / or legacy systems that can be downloaded too.

== Software releases ==

Under [[PINE A64 Software Releases]] you will find a complete list of currently supported operating system images, which work with the PINE A64 and PINE A64+, as well as other related software.

== Accessories Step-by-Step Guides ==

Under [[Accessories Step by Step Guides]] you can find instructions and guides pertaining to:
* Enclosures
* Bluetooth and WiFi module
* Real Time Clock (RTC) battery
* Real Time Clock (RTC) battery holder
* First and third party cases
* Featured 3D printed cases (and more).

== SoC and Memory Specification ==
* Based on Allwinner A64
[[File:Allwinner_A64.jpg|right]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]
* A power-efficient ARM v8 architecture
* 64 and 32bit execution states for scalable high performance
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* 512KB L2 cache

=== GPU Architecture ===
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]
* Support OpenGL ES 2.0 and OpenVG 1.1 standard

=== System Memory ===
* RAM Memory Variants: 512MB, 1GB and 2GB DDR3.
* Storage Memory: PINE A64 boards ''do not'' have built-in Flash memory but use '''bootable microSD Cards''' or USB attached storage.

== Board Features ==
=== Video ===
* Digital Video Port (Type A - full)

=== Audio ===
* 3.5mm stereo earphone/microphone plug

=== Network ===
* 10/100/1000Mbps Ethernet (PINE A64+ version), 10/100Mbps Ethernet (PINE A64 version)
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 USB2.0 Host port

=== Expansion Ports ===
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
* CSI - CMOS Camera Interface up to 5 mega pixel
* TP - Touch Panel Port, SPI with interrupt
* RTC - Real Time Clock Battery Connector
* VBAT - Lithium Battery Connector with temperature sensor input
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header
* 2x17 pins "Euler" GPIO Header
* 2x5 pins "EXP" Console Header

== Information, Schematics and Certifications ==

Board Dimensions: 133mm x 80mm x 19mm

Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, microUSB connector, Euler connector

Schematics and general files:
* [https://wiki.pine64.org/images/1/1d/Power_Consumption.jpg Power Consumption: 2.5W]
* [https://wiki.pine64.org/images/7/7d/Pine64_Board_Connector.png PINE A64 Connector Layout @courtesy of norm24]
* [https://wiki.pine64.org/images/2/2e/Pine64_Board_Connector_heatsink.png PINE A64 Heat Sink Location @courtesy of norm24]
* [https://wiki.pine64.org/images/d/da/Pine64_Connector.JPG PINE A64 Connector List]
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160215.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]
* [https://synfare.com/599N105E/hwdocs/pine64/index.html Good documentation about PINE A64, A64+, and A64-LTS GPIO pins article]
* [https://wiki.pine64.org/images/b/be/Pine64_Model_Spec.JPG Board Model Comparison]

Board schematics:
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20512MB%20rev%20B-2015121601_Release.pdf PINE A64 512MB Rev B Board Schematic]
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/a64-db-rev%20b-20151217-Plus-Release.pdf PINE A64+ 1GB Rev B Board Schematic]
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64plus%202GB%20Rev%20C-20160113_Release.pdf PINE A64+ 2GB Rev C Board Schematic]
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]

Stereo audio DAC schematics:
* [https://forum.pine64.org/attachment.php?aid=697 PINE A64 Stereo audio DAC schematics]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certifications and obtain the certificates to prove that the SBC board can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
* [https://files.pine64.org/doc/cert/Pine%20A64%20Board%20FCC%20certification%20CCF20160624.jpg PINE A64 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pine%20A64%20Board%20CE%20Certification%20CCF20160624.jpg PINE A64 CE Certificate]
* [https://files.pine64.org/doc/cert/CCF20160627_00000.jpg PINE A64 RoHS Certificate]

== Datasheets for Components and Peripherals ==
Allwinner A64 SoC information:
* [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
* [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
* [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

X-Powers AXP803 PMU (Power Management Unit) information:
* [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]

'''PINE A64, PINE A64+ and SOPINE Related:'''
* 5MPixel CMOS Camera module information:
** [https://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)]
** [https://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/S5K4ECGX_EVT1_DataSheet_R005_20100816.pdf S5K4EC 5MP CMOS Image Sensor SoC Chip Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/s5k4ec.c S5K4EC 5MP CMOS Image Sensor Driver Source Code in C language]
** Early version Camera module information:
*** [https://files.pine64.org/doc/datasheet/pine64/D116-A64_Bonsen_cmos_camera.pdf Bonsen Kexin V118-A64-GC2145-HM5065 CMOS Image Sensor Module]
*** [https://files.pine64.org/doc/datasheet/pine64/HM5065-DS-V03.pdf HiMax 5MP CMOS Image Sensor SoC]
* LCD Touch Screen Panel information:
** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]
** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]
** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]
* Lithium Battery information:
** [https://files.pine64.org/doc/datasheet/pine64/9070120P%203.7V%208000MAH.pdf 8000mAH Lithium Battery Specification]
* Ethernet PHY information:
** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE A64+ Board]
** [https://files.pine64.org/doc/datasheet/pine64/rtl8201cp.pdf Realtek RTL8201 10/100M Ethernet Transceiver for PINE A64 Board]
* Wifi/BT module information:
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
* Enclosure information:
** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]
** [https://files.pine64.org/doc/datasheet/case/ABS_enclosure_20160426.stp ABS Enclosure 3D file]
** [https://files.pine64.org/doc/datasheet/case/pine64%20Die%20Cast%20casing-final.jpg Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]
* Connector information:
** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]
* Remote control button mapping
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]

== Pine A64 POT ==
* [[POT|PINE A64 Peripheral On Top (POT) and Related Devices]]
* [[Wifi_Remote_I2c|WiFi Remote I2c Quick Start Guide]]

== Other Resources ==
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]
* [https://github.com/longsleep/build-pine64-image PINE A64 Linux build scripts, tools and instructions by Longsleep]
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE A64 Linux image by Longsleep]
* [https://github.com/ayufan-pine64/linux-build/releases PINE A64 Linux Github by ayufan]
* [https://github.com/ayufan-pine64/android-7.1/releases PINE A64 Android Github by ayufan]
* [https://www.armbian.com/pine64 Armbian's PINE A64 Page]
* [https://github.com/umiddelb/z2d/tree/master/pine64 Collection of scripts to set up a minimal Xenial 14.04.3 / Debian 8 Jessie root filesystem Contributed By Uli Middelberg]
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]
* [https://blog.hypriot.com/post/the-pine-a64-is-about-to-become=the-cheapest-ARM-64-bit-platform-to-run-Docker/ PINE A64 with HypriotOS by Dieter and Govinda]
* [https://sosfakeflash.wordpress.com/2008/09/02/h2testw-14-gold-standard-in-detecting-usb-counterfeit-drives/comment-page-3/#comment-9861 H2testw 1.4 – Gold Standard In Detecting USB Counterfeit Drives]
* [https://oss.digirati.com.br/f3/ F3 - an alternative to h2testw]
* [https://www.phoronix.com/scan.php?page=article&item=pine-64-benchmark&num=1 Benchmarking The Low-Cost PINE 64+ ARM Single Board Computer by Michael Larabel]
* [https://www.youtube.com/playlist?list=PLgj96wTPcMKffRm_Sk6673Nfy_I6b5UJW A series of Youtube video on PINE A64 Developers Board by Michael Larson]
* [https://rayhightower.com/blog/2016/04/04/pine64-quick-start-guide-using-mac-os-x/ PINE64 Quick Start Guide (with Gotchas)]
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]
* [https://github.com/avafinger/ffmpeg-3.3.4_cedrus264 FFmpeg Hardware encoder Cedrus264 on Linux by avafinger ]

[[Category:PINE A64]] [[Category:Allwinner A64]]

PINE A64 Software Releases

2023-08-27T08:41:20Z

Fxc: Changed style

This page contains a list of all available releases for the [[PINE A64|PINE A64 and PINE A64+]], as well as links to other resources.

{{Info|The images for the PINE A64 and PINE A64+ are '''not compatible with the PINE A64-LTS''' due to LPDDR3 memory configuration. For PINE A64-LTS, please use the [[SOPINE Software Releases]].}}

== Linux ==

'''Special thanks to Sunxi community and longsleep for their contributions'''

Below you will find useful links to various resources and forum threads:
* [https://linux-sunxi.org/Pine64 Sunxi PINE64 Page]
* [https://www.stdin.xyz/downloads/people/longsleep/tmp/pine64-images Longsleep BSP Linux Builds Download Page]
* [https://forum.pine64.org/showthread.php?tid=293 Longsleep BSP Linux Kernel Thread on PINE64 Forum]
* [https://forum.pine64.org/showthread.php?tid=376 Longsleep BSP Xenial Thread on PINE64 Forum]
* [https://forum.pine64.org/showthread.php?tid=343 Longsleep BSP Arch Linux Thread on PINE64 Forum]

=== AOSC ===
[[File:aosc.png|right|100px]]

'''AOSC OS''' is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website].

Download:
* https://aosc.io/downloads/ (supports the microSD card and eMMC, 8GB or more)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>aosc/anthon</code>
|}

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|right|100px]]

'''Arch Linux ARM''' is a distribution of Linux for ARM computers.

Installation:
* https://archlinuxarm.org/platforms/armv8/allwinner/pine64

=== Armbian ===
[[File:armbian.png|right|100px]]

'''Armbian''' is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored.

Download:
* https://www.armbian.com/pine64/

=== Debian ===
[[File:Debian-logo.png|right|100px]]

'''Debian''' is an operating system and a distribution of free software. See the forum thread [https://forum.pine64.org/showthread.php?tid=9744 here].

Download:
* [https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 11 Bullseye] (recommended)
* [https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 12 Bookworm]
* [https://d-i.debian.org/daily-images/arm64/ Daily netboot images]

Instructions:
* Download: <code>firmware.pine64_plus.img.gz</code>
* Download: <code>partition.img.gz</code>
* Create the disk image:
** For Linux: <code>zcat firmware.pine64_plus.img.gz partition.img.gz > complete_image.img</code>
** For Mac: <code>gzcat firmware.pine64_plus.img.gz partition.img.gz > complete_image.img</code>
* Write the image to your boot device:
** For Linux: <code>dd if=complete_image.img of=your_chosen_boot_device bs=4M</code>
** For Mac: see [[Getting started]]

Notes:
* An Ethernet connection is required for the above installer

=== DietPi ===
[[File:dietpi.png|right|100px]]

'''DietPi''' is a lightweight yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation]. Discuss the PINE A64 build on the [https://forum.pine64.org/showthread.php?tid=12513 PINE64 forum thread].

Download:
* [https://dietpi.com/downloads/images/DietPi_PINEA64-ARMv8-Bullseye.7z Debian 11 Bullseye] (supports the microSD card and eMMC, 4GB or more)
* [https://dietpi.com/downloads/images/DietPi_PINEA64-ARMv8-Bookworm.7z Debian 12 Bookworm] (supports the microSD card and eMMC, 4GB or more)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>root/dietpi</code>
|}

=== FreedomBox ===
[[File:FreedomBox.jpg|right|100px]]

'''FreedomBox''' is a private server for non-experts: it lets you install and configure server applications with only a few clicks. For more information about FreedomBox, please visit http://www.freedombox.org.

{{Outdated release}}

Download:
* [https://ftp.freedombox.org/pub/freedombox/hardware/pine64-plus/stable/freedombox-stable-free_buster_pine64-plus-arm64.img.xz Direct download from FreedomBox site]

Notes:
* This is a headless build, not HDMI output.
* Please plug-in Ethernet cable first before initial power up. After power up for 10 minutes, using browser and type in https://fredombox.local to setup. Browser may warms for unsecure site and please proceed with exception.
* Freedom Manual: https://wiki.debian.org/FreedomBox/Manual

=== LibreELEC ===
[[File:libreelec.jpg|right|100px]]

'''LibreELEC''' is a "Just enough OS" Linux distribution combining the Kodi media center with an operating system.

Download:
* 512MB PINE A64: [https://test.libreelec.tv/ direct download] from Libreelec nightly build site (look for ''LibreELEC-A64.arm-...-nightly-xxxxxxxx-xxxxxxx-pine64.img.gz'')
* 1GB/2GB PINE A64+ Board: [https://test.libreelec.tv/ direct download] from Libreelec nightly build site (look for ''LibreELEC-A64.arm-...-nightly-xxxxxxxx-xxxxxxx-pine64-plus.img.gz'')

Notes:
* Nightly build for microSD boot

=== motionEyeOS ===
[[File:motioneyeos.png|right|100px]]

'''motionEyeOS''' is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend. Visit the [https://github.com/ccrisan/motioneyeos/releases/ motionEyeOS GitHub] and its [https://github.com/ccrisan/motioneyeos/wiki GitHub Wiki] for more information

Download:
* 1GB/2GB PINE A64(+): [https://github.com/ccrisan/motioneyeos/releases/latest Direct download from GitHub] (look for ''motioneyeos-pine64-xxxxxxxx.img.xz'')

Notes:
* Suitable for 1GB/2GB PINE A64(+) variants
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname MEYE-* and go to the admin web interface https://[PINE A64(+) motionEyeOS IP Address] and after login, you should able to see the output of the CAMERA MODULE on the web interface
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>admin/-</code>
|}

=== NEMS Linux ===
[[File:nems.jpg|right|100px]]

'''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. To find out more on NEMS Linux, please visit their [https://nemslinux.com/ site].

{{Outdated release}}

Download:
* [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux] (2.66GB, MD5 of the xz file is ''ac508549a829021491cfa23aeb18a063'')
* [https://files.pine64.org/os/pine-a64/nems/NEMS_v1.5-Pine64-Build1.zip Direct download from pine64.org] (2.66GB, MD5 of the xz file is ''ac508549a829021491cfa23aeb18a063'')

Notes:
* Suitable for all 512MB/1GB/2GB PINE A64(+) variants

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>nemsadmin/nemsadmin</code>
|}

=== openSUSE ===
[[File:Opensuse-distribution.png|right|100px]]

'''openSUSE''' is a free and open source RPM-based Linux distribution developed by the openSUSE project. More details can be found under https://en.opensuse.org/HCL:Pine64.

Download:
* [http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pine64/images/ Images]
* Headless build: [http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pine64/images/openSUSE-Tumbleweed-ARM-JeOS-pine64.aarch64.raw.xz Direct download]

=== OpenWRT ===
[[File:Openwrt logo square.png|right|100px]]

The '''OpenWrt''' Project is a Linux operating system targeting embedded devices.

Download:
* [https://downloads.lede-project.org/snapshots/targets/sunxi/cortexa53/ Direct download] (look for ''pine64_pine64-baseboard-ext4-sdcard.img.gz'' and ''pine64_pine64-baseboard-squashfs-sdcard.img.gz'')

Notes:
* OpenWRT community build for microSD boot.
* This is headless build, please use serial console to configure

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>-/passwd</code>
|}

== BSD ==

=== NetBSD ===
[[File:netbsd.png|right|100px]]

'''NetBSD''' is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page].

Download:
* [https://www.invisible.ca/arm/ Direct download] (345MB, select ''PINE A64 / PINE A64+'')

Notes:
* NetBSD community build for microSD boot
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Root user and SSH
| <code>root/[none]</code>
|}

== Windows 10 IoT ==
[[File:win10iot.png|right|100px]]

Download:
* [https://files.pine64.org/os/pine-a64/win10-iot/PINE64_Win10IoT_TestOS_build_10.0.15063.0_20170602.ffu Windows IoT direct download] from ''pine64.org'' (957MB, MD5 of FFU file ''ACA617C0C9CEDA705DD510BF041E79B4'')

Notes:
* PINE64 Win10 IoT build already passed the [https://catalog.azureiotsuite.com/details?title=Allwinner_Technology_Pine64 Microsoft Azure certification]
* For step by step installation process, please follow this [https://github.com/Leeway213/Win10-IoT-for-A64-Release-Notes/blob/master/doc/How%20to%20flash%20ffu.md github link]
* For release note, please follow this [https://github.com/Leeway213/Win10-IoT-for-A64-Release-Notes/blob/master/20160809/Pine64/ReleaseNotes.md github link]
* For Microsoft Azure IoT SDKs, please follow this [https://github.com/Azure/azure-iot-sdks/ github link]

Changelog for Win10 IoT 10.0.15063.0_20170602:
* 10.0.15063.0_20170602
** Update Notes since 10.0.15063.0_20170524:
*** Fix the failure of default application installation caused by a app certification issue
*** Fix that the default application cannot start automatically after installation
*** Fix Ethernet initialization problem and now the Ethernet will start successfully every time
*** Enable the usermode access for all unusable GPIO pins in Pi-2 bus( later provide a UWP sample to show how to control these pins )
** Extra Notes:
*** If you want to connect a USB peripheral for extension, please connect a USB hub to the lower USB interface as the medium
*** Please refer to [https://github.com/Leeway213/BSP-aw1689/blob/master/doc/Dev%20Guide.md Part 2 of chapter 3: Debug with a virtual net over USB] on how to use the upper USB interface

* 10.0.15063.0_20170524
** Some Updates:
*** Update the OS version to build v.10.0.15063.0 (Creators Update)
*** New page style of Device Portal, visit https://deviceipaddr:8080 to check it
*** Built-in Cortana assistant, need to be enabled in settings page in default app and Device Portal
*** Support on-screen keyboard, need to be enabled in Device Portal
*** Enable 100M Ethernet and fix some bugs
*** Support built-in UART bus in A64 SoC(not built in the ffu, later provide driver binary and deployment helper)
*** Support built-in IR module in A64 SoC(not built in the ffu, later provide source code and dev doc for developers in community)
** Known Issues:
*** Kernel debug is enabled by default. This will slow the bring-up process. If a kernel debug is not necessary for you, visit Device Portal and navigate to Processes->Run Command page, run this command to disable:
**** Bcdedit /store C:\EFIESP\EFI\Microsoft\boot\BCD /set {default} debug off
*** An PnP bug in audio device may cause a blue screen when acting software shutdown
*** Ethernet device may not start with problem code 12 at the first time to bring up

== Linux BSP SDK ==

Linux BSP Kernel 4.9
* [https://files.pine64.org/SDK/PINE-A64/PINE-A64_lichee_BSP4.9.tar.xz Direct Download] from ''pine64.org'' (5.4GB, MD5 of the TAR-GZip file ''7736e3c4d50c021144d125cc4ee047a4'')

== Android SDK ==

Android Oreo (v8.1)

* [https://files.pine64.org/SDK/PINE-A64/PINE-A64_SDK_android8.1.tar.xz Direct Download] from ''pine64.org'' (24.94GB, MD5 of the TAR-GZip file ''b0394af324c70ce28067e52cd7bc0c87'')

== Other resources ==

* [[Mali Driver]]
* [https://files.pine64.org/tools/allwinner/PhoenixCard4_1_3.zip Allwinner PhoenixCard Bootable SD-Card Creator]
* [https://files.pine64.org/tools/allwinner/DragonFace.zip Allwinner DragonFace software that will let you edit and modify A64 Stock Android Build PhoenixCard image]

[[Category:PINE A64]]

PINE A64 Software Releases

2023-08-27T08:39:17Z

Fxc: added release

This page contains a list of all available releases for the [[PINE A64|PINE A64(+)]], as well as links to other resources.

Note that the PINE A64(+) images are '''not compatible with the PINE A64-LTS''' due to LPDDR3 memory configuration. For PINE A64-LTS, please use the [[SOPINE Software Releases]].

== Linux ==

'''Special thanks to Sunxi community and longsleep for their contributions'''

Below you will find useful links to various resources and forum threads:
* [https://linux-sunxi.org/Pine64 Sunxi PINE64 Page]
* [https://www.stdin.xyz/downloads/people/longsleep/tmp/pine64-images Longsleep BSP Linux Builds Download Page]
* [https://forum.pine64.org/showthread.php?tid=293 Longsleep BSP Linux Kernel Thread on PINE64 Forum]
* [https://forum.pine64.org/showthread.php?tid=376 Longsleep BSP Xenial Thread on PINE64 Forum]
* [https://forum.pine64.org/showthread.php?tid=343 Longsleep BSP Arch Linux Thread on PINE64 Forum]

=== AOSC ===
[[File:aosc.png|right|100px]]

'''AOSC OS''' is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website].

Download:
* https://aosc.io/downloads/ (supports the microSD card and eMMC, 8GB or more)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>aosc/anthon</code>
|}

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|right|100px]]

'''Arch Linux ARM''' is a distribution of Linux for ARM computers.

Installation:
* https://archlinuxarm.org/platforms/armv8/allwinner/pine64

=== Armbian ===
[[File:armbian.png|right|100px]]

'''Armbian''' is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored.

Download:
* https://www.armbian.com/pine64/

=== Debian ===
[[File:Debian-logo.png|right|100px]]

'''Debian''' is an operating system and a distribution of free software. See the forum thread [https://forum.pine64.org/showthread.php?tid=9744 here].

Download:
* [https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 11 Bullseye] (recommended)
* [https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 12 Bookworm]
* [https://d-i.debian.org/daily-images/arm64/ Daily netboot images]

Instructions:
* Download: <code>firmware.pine64_plus.img.gz</code>
* Download: <code>partition.img.gz</code>
* Create the disk image:
** For Linux: <code>zcat firmware.pine64_plus.img.gz partition.img.gz > complete_image.img</code>
** For Mac: <code>gzcat firmware.pine64_plus.img.gz partition.img.gz > complete_image.img</code>
* Write the image to your boot device:
** For Linux: <code>dd if=complete_image.img of=your_chosen_boot_device bs=4M</code>
** For Mac: see [[Getting started]]

Notes:
* An Ethernet connection is required for the above installer

=== DietPi ===
[[File:dietpi.png|right|100px]]

'''DietPi''' is a lightweight yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation]. Discuss the PINE A64 build on the [https://forum.pine64.org/showthread.php?tid=12513 PINE64 forum thread].

Download:
* [https://dietpi.com/downloads/images/DietPi_PINEA64-ARMv8-Bullseye.7z Debian 11 Bullseye] (supports the microSD card and eMMC, 4GB or more)
* [https://dietpi.com/downloads/images/DietPi_PINEA64-ARMv8-Bookworm.7z Debian 12 Bookworm] (supports the microSD card and eMMC, 4GB or more)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>root/dietpi</code>
|}

=== FreedomBox ===
[[File:FreedomBox.jpg|right|100px]]

'''FreedomBox''' is a private server for non-experts: it lets you install and configure server applications with only a few clicks. For more information about FreedomBox, please visit http://www.freedombox.org.

{{Outdated release}}

Download:
* [https://ftp.freedombox.org/pub/freedombox/hardware/pine64-plus/stable/freedombox-stable-free_buster_pine64-plus-arm64.img.xz Direct download from FreedomBox site]

Notes:
* This is a headless build, not HDMI output.
* Please plug-in Ethernet cable first before initial power up. After power up for 10 minutes, using browser and type in https://fredombox.local to setup. Browser may warms for unsecure site and please proceed with exception.
* Freedom Manual: https://wiki.debian.org/FreedomBox/Manual

=== LibreELEC ===
[[File:libreelec.jpg|right|100px]]

'''LibreELEC''' is a "Just enough OS" Linux distribution combining the Kodi media center with an operating system.

Download:
* 512MB PINE A64: [https://test.libreelec.tv/ direct download] from Libreelec nightly build site (look for ''LibreELEC-A64.arm-...-nightly-xxxxxxxx-xxxxxxx-pine64.img.gz'')
* 1GB/2GB PINE A64+ Board: [https://test.libreelec.tv/ direct download] from Libreelec nightly build site (look for ''LibreELEC-A64.arm-...-nightly-xxxxxxxx-xxxxxxx-pine64-plus.img.gz'')

Notes:
* Nightly build for microSD boot

=== motionEyeOS ===
[[File:motioneyeos.png|right|100px]]

'''motionEyeOS''' is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend. Visit the [https://github.com/ccrisan/motioneyeos/releases/ motionEyeOS GitHub] and its [https://github.com/ccrisan/motioneyeos/wiki GitHub Wiki] for more information

Download:
* 1GB/2GB PINE A64(+): [https://github.com/ccrisan/motioneyeos/releases/latest Direct download from GitHub] (look for ''motioneyeos-pine64-xxxxxxxx.img.xz'')

Notes:
* Suitable for 1GB/2GB PINE A64(+) variants
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname MEYE-* and go to the admin web interface https://[PINE A64(+) motionEyeOS IP Address] and after login, you should able to see the output of the CAMERA MODULE on the web interface
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>admin/-</code>
|}

=== NEMS Linux ===
[[File:nems.jpg|right|100px]]

'''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. To find out more on NEMS Linux, please visit their [https://nemslinux.com/ site].

{{Outdated release}}

Download:
* [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux] (2.66GB, MD5 of the xz file is ''ac508549a829021491cfa23aeb18a063'')
* [https://files.pine64.org/os/pine-a64/nems/NEMS_v1.5-Pine64-Build1.zip Direct download from pine64.org] (2.66GB, MD5 of the xz file is ''ac508549a829021491cfa23aeb18a063'')

Notes:
* Suitable for all 512MB/1GB/2GB PINE A64(+) variants

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>nemsadmin/nemsadmin</code>
|}

=== openSUSE ===
[[File:Opensuse-distribution.png|right|100px]]

'''openSUSE''' is a free and open source RPM-based Linux distribution developed by the openSUSE project. More details can be found under https://en.opensuse.org/HCL:Pine64.

Download:
* [http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pine64/images/ Images]
* Headless build: [http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pine64/images/openSUSE-Tumbleweed-ARM-JeOS-pine64.aarch64.raw.xz Direct download]

=== OpenWRT ===
[[File:Openwrt logo square.png|right|100px]]

The '''OpenWrt''' Project is a Linux operating system targeting embedded devices.

Download:
* [https://downloads.lede-project.org/snapshots/targets/sunxi/cortexa53/ Direct download] (look for ''pine64_pine64-baseboard-ext4-sdcard.img.gz'' and ''pine64_pine64-baseboard-squashfs-sdcard.img.gz'')

Notes:
* OpenWRT community build for microSD boot.
* This is headless build, please use serial console to configure

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>-/passwd</code>
|}

== BSD ==

=== NetBSD ===
[[File:netbsd.png|right|100px]]

'''NetBSD''' is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page].

Download:
* [https://www.invisible.ca/arm/ Direct download] (345MB, select ''PINE A64 / PINE A64+'')

Notes:
* NetBSD community build for microSD boot
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Root user and SSH
| <code>root/[none]</code>
|}

== Windows 10 IoT ==
[[File:win10iot.png|right|100px]]

Download:
* [https://files.pine64.org/os/pine-a64/win10-iot/PINE64_Win10IoT_TestOS_build_10.0.15063.0_20170602.ffu Windows IoT direct download] from ''pine64.org'' (957MB, MD5 of FFU file ''ACA617C0C9CEDA705DD510BF041E79B4'')

Notes:
* PINE64 Win10 IoT build already passed the [https://catalog.azureiotsuite.com/details?title=Allwinner_Technology_Pine64 Microsoft Azure certification]
* For step by step installation process, please follow this [https://github.com/Leeway213/Win10-IoT-for-A64-Release-Notes/blob/master/doc/How%20to%20flash%20ffu.md github link]
* For release note, please follow this [https://github.com/Leeway213/Win10-IoT-for-A64-Release-Notes/blob/master/20160809/Pine64/ReleaseNotes.md github link]
* For Microsoft Azure IoT SDKs, please follow this [https://github.com/Azure/azure-iot-sdks/ github link]

Changelog for Win10 IoT 10.0.15063.0_20170602:
* 10.0.15063.0_20170602
** Update Notes since 10.0.15063.0_20170524:
*** Fix the failure of default application installation caused by a app certification issue
*** Fix that the default application cannot start automatically after installation
*** Fix Ethernet initialization problem and now the Ethernet will start successfully every time
*** Enable the usermode access for all unusable GPIO pins in Pi-2 bus( later provide a UWP sample to show how to control these pins )
** Extra Notes:
*** If you want to connect a USB peripheral for extension, please connect a USB hub to the lower USB interface as the medium
*** Please refer to [https://github.com/Leeway213/BSP-aw1689/blob/master/doc/Dev%20Guide.md Part 2 of chapter 3: Debug with a virtual net over USB] on how to use the upper USB interface

* 10.0.15063.0_20170524
** Some Updates:
*** Update the OS version to build v.10.0.15063.0 (Creators Update)
*** New page style of Device Portal, visit https://deviceipaddr:8080 to check it
*** Built-in Cortana assistant, need to be enabled in settings page in default app and Device Portal
*** Support on-screen keyboard, need to be enabled in Device Portal
*** Enable 100M Ethernet and fix some bugs
*** Support built-in UART bus in A64 SoC(not built in the ffu, later provide driver binary and deployment helper)
*** Support built-in IR module in A64 SoC(not built in the ffu, later provide source code and dev doc for developers in community)
** Known Issues:
*** Kernel debug is enabled by default. This will slow the bring-up process. If a kernel debug is not necessary for you, visit Device Portal and navigate to Processes->Run Command page, run this command to disable:
**** Bcdedit /store C:\EFIESP\EFI\Microsoft\boot\BCD /set {default} debug off
*** An PnP bug in audio device may cause a blue screen when acting software shutdown
*** Ethernet device may not start with problem code 12 at the first time to bring up

== Linux BSP SDK ==

Linux BSP Kernel 4.9
* [https://files.pine64.org/SDK/PINE-A64/PINE-A64_lichee_BSP4.9.tar.xz Direct Download] from ''pine64.org'' (5.4GB, MD5 of the TAR-GZip file ''7736e3c4d50c021144d125cc4ee047a4'')

== Android SDK ==

Android Oreo (v8.1)

* [https://files.pine64.org/SDK/PINE-A64/PINE-A64_SDK_android8.1.tar.xz Direct Download] from ''pine64.org'' (24.94GB, MD5 of the TAR-GZip file ''b0394af324c70ce28067e52cd7bc0c87'')

== Other resources ==

* [[Mali Driver]]
* [https://files.pine64.org/tools/allwinner/PhoenixCard4_1_3.zip Allwinner PhoenixCard Bootable SD-Card Creator]
* [https://files.pine64.org/tools/allwinner/DragonFace.zip Allwinner DragonFace software that will let you edit and modify A64 Stock Android Build PhoenixCard image]

[[Category:PINE A64]]

PineTab2 FAQ

2023-08-16T18:11:37Z

Fxc: /* Performing USB Tethering with a KaiOS phone */ removed side comment

This is a collection of tutorials and frequently asked questions for the [[PineTab2]].

== Tutorials ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, plug the included debug adapter into the charging USB-C port and switch the white switch to its "ON" position to bypass eMMC/SPI boot. This tries to boot from SD, and if no SD is inserted, enters Maskrom mode.

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (or the USB-C to USB-C cable)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

Make sure to open the iPhone once you reconnect.

==== Performing USB Tethering with a KaiOS phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use a KaiOS phone for mobile Internet use with your PineTab2.

You'll need:

* A KaiOS phone
* A USB OTG adapter
* Your device’s charging cable
* Some knowledge of your KaiOS phone

Do the following in order:

* Plug the device into the PineTab2 using the USB cable and a USB OTG adapter
* On your KaiOS phone, open settings (specifics from here may vary on version)
* Navigate to "Network & Connectivity"
* Navigate to "Internet Sharing"
* Select "USB" and select On under USB tethering (Note: This option will be greyed out unless connected to the PineTab2)

You should now see a new network interface on the PineTab2 and it should show a wired connection icon.

=== Screen Rotation ===
==== Auto-rotating the Screen ====
Auto-rotation is handled by your operating system. However, the following general steps should work on distributions that support iio-sensor-proxy:

* To enable auto-rotation, install the iio-sensor-proxy package: <code>sudo pacman -S iio-sensor-proxy</code> and reboot.
* Some desktop environments, such as KDE, default to only allowing screen rotation while in tablet mode (detached from the case.) To enable it with the keyboard attached, go to System Settings-->Display and Monitor -> Display Configuration -> Uncheck "Only when in tablet mode" and click "Apply."

==== Rotating the Login Screen ====
Login screen orientation is handled by your operating system. Below are the instructions for the SDDM login screen that ships with the factory image:

By default, the login screen is set to display in portrait mode. If you wish to change it to landscape mode to match the keyboard while in the case, use the following steps ([https://forum.pine64.org/showthread.php?tid=18313 Credit to chzbacon]) :

* Install necessary software: <code>sudo pacman -S xorg-xrandr xorg-xinput</code>
* Edit /usr/share/sddm/scripts/Xsetup. For example, using nano: <code>sudo nano /usr/share/sddm/scripts/Xsetup</code> and add the following two lines to the end of file:
** <code>xrandr --output DSI-1 --mode 800x1280 --rate 60.00 --rotate right</code>
** <code>xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1</code>
* Now edit /etc/sddm.conf.d/sddm.conf, for example: <code>sudo nano /etc/sddm.conf.d/sddm.conf</code> and add the following two lines (case sensitive):
** <code>[X11]</code>
** <code>DisplayCommand=/usr/share/sddm/scripts/Xsetup</code>
* Reboot, and your login screen should now display in landscape mode.

== Frequently Asked Questions ==

=== General ===

==== How does the PineTab2 compare to the Pinebook Pro? ====
It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

==== What is the Performance of the PineTab2 compared to the PineTab-V? ====
The PineTab2 is notably faster than the PineTab-V. You can see this by [https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md comparing the Quartz64 sbc-bench results to the Star64 ones]. Performance should not be a factor of consideration when purchasing a PineTab-V.

==== I am a casual user with minimal Linux experience. Is this device for me? ====
The PineTab 2 is considered early release at this point, and the community is expected to develop support for it over time. For example, the [[PineTab2#Known_Issues]] page details several features that are not yet fully working. You may at times need to troubleshoot this device and some development experience is ideal if you want to realize the tablet's full potential at this stage.

For these reasons, the PineTab2 may not be the ideal device for casual users. However, if you feel up to the challenge and want to learn while joining a great community, you are more than welcome! Please join one of our [[Main_Page#Chat_Platforms|chat platforms]]: the community is always happy to help!

==== What works, what doesn't? ====

Please see [[PineTab2#Known_Issues]].

==== I only know Python, can I help with drivers? ====
Drivers are (at least typically) written in the C programming language. Unfortunately, there is no way to "code drivers in Python" because usually drivers need to access and process memory allocation directly. If you feel like this is interesting to you, we suggest you to spend some time learning the C programming language, maybe with an emphasis in device driver development. The good news is that, since you already know a programming language, you already know part of the skill.

In short, you can only help with drivers development if you learn the C programming language first.

=== Hardware ===

==== Does the Tablet support a Pen? ====
No, adding a digitiser for pen inputs would make the price too high.

==== Is there SPI Flash? ====
Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== Software ===
==== What operating systems are currently available? ====
The PineTab2 uses ARM operating systems. Please see [[PineTab2 Releases]] for a current list of software releases.

==== How can I install an operating system on the SD card / eMMC? ====

See the article [[PineTab2]].

==== Can I run Android on it? ====

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, and you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====

The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. Please see the [[PineTab2]] for more detailed information.

==== Can I install a different OS on my PineTab2? ====

Yes! While all PineTab2 come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card. See [[PineTab2]] and [[PineTab2 Releases]] for how to install them.

=== Bluetooth ===

==== The Bluetooth isn't working ====

The BES2600 Bluetooth driver still needs to be implemented. Please see the [[#Networking Using USB]] section above for a workaround.

=== Wi-Fi ===

==== The Wi-Fi isn't working ====
The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing: at the moment it causes system crashes. Please see the [[#Networking Using USB]] section above for a workaround.

=== Video ===

==== Can PineTab2 play back DRM content such as Netflix? ====

Yes, though the specific implementation depends on your installed operating system.

On the default Arch Linux Arm: Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

[[Category:Rockchip RK3566]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-08-14T14:16:09Z

Fxc: Fix

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]].

Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL.

== MicroSD card ==

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

Requirements: SSH connection from Linux machine to PinePhone Pro, internet connection.

{{Info|Loader and userspace utility to flash it are free, but not open-source.}}

=== Flash rk2aw loader to SPI ===

Connect PinePhone Pro to a Linux machine

ssh <user>@<phoneip>'' # start ssh connection''
cd ~/Downloads'' # enter to directory''
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz'' # download installer''
tar -xvzf ppp.tar.gz -C ~/Downloads'' # extract''
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh'' # flash SPI''

=== Flash Multi-Distro SD Card ===

Get the compressed distribution images and decompress them (i.e. Manjaro Phosh beta 34, Mobian, Arch Linux)

Mount distribution images both partitions "/boot", "/root" for each distribution.

lsblk ''# show /loop, /sd references''
blkid ''# show UUID for the partition''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
or sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD card ====

{{Info|A minimum capacity of 32 GB for the microSD card is recommended.}}

sudo sfdisk /dev/sdb/ <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

lsblk'' # list partitions on sd and mounted distro images''
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 16809983 16777216 8G Linux filesystem
/dev/sdb3 16809984 33587199 16777216 8G Linux filesystem
/dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem

==== Copy Files for Arch Linux ARM ====

sudo su'' # login with your psw''
dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync'' # copy rootfs to sd part2''
mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot'' # copy bootfs to to part2/boot''
mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG'' # hide auto-menu item''
nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/etc/fstab'' # add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''
mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALarm
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Manjaro ====

dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync'' # copy rootfs to sd part3''
mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/
scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot'' # copy bootfs to to part3/boot''
nano /media/xxx/ROOT_MNJRO1/etc/fstab'' # change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''
mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG'' # hide auto-menu item''
mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL Manjaro
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Mobian ====

dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync'' # copy rootfs to microSD card partition 4''
mount /dev/sdb4 /media/xxx/rootfs1/
scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot'' # copy bootfs to to part4/boot''
nano /media/xxx/rootfs1/etc/fstab'' # replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''

cat << EOF > /media/xxx/rootfs1/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title Pinephone Pro Boot Menu
prompt 0
timeout 10
label l0
menu label Mobian 63
linux '''/boot'''/vmlinuz-6.3-rockchip
initrd '''/boot'''/initrd.img-6.3-rockchip
fdtdir '''/usr/lib'''/linux-image-6.3-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
label l1
menu label Mobian 61
linux '''/boot'''/vmlinuz-6.1-rockchip
initrd '''/boot'''/initrd.img-6.1-rockchip
fdtdir '''/usr/lib'''/linux-image-6.1-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build Multi-Distro eMMC ===

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.

==== Mount the Images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh Partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO Partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

=== Follow-Up Comments ===
# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-08-14T14:10:21Z

Fxc: Fixes

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]].

== MicroSD card ==

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL, https://xnux.eu/rk2aw/ and https://xff.cz/git/u-boot/log/?h=ppp-2023.07

Requirements: SSH connection from Linux machine to PinePhone Pro, internet connection.

{{Info|Loader and userspace utility to flash it are free, but not open-source.}}

=== Flash rk2aw loader to SPI ===

Connect PinePhone Pro to a Linux machine

ssh <user>@<phoneip>'' # start ssh connection''
cd ~/Downloads'' # enter to directory''
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz'' # download installer''
tar -xvzf ppp.tar.gz -C ~/Downloads'' # extract''
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh'' # flash SPI''

=== Flash Multi-Distro SD Card ===

Get the compressed distribution images and decompress them (i.e. Manjaro Phosh beta 34, Mobian, Arch Linux)

Mount distribution images both partitions "/boot", "/root" for each distribution.

lsblk ''# show /loop, /sd references''
blkid ''# show UUID for the partition''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
or sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD card ====

{{Info|A minimum capacity of 32 GB for the microSD card is recommended.}}

sudo sfdisk /dev/sdb/ <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

lsblk'' # list partitions on sd and mounted distro images''
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 16809983 16777216 8G Linux filesystem
/dev/sdb3 16809984 33587199 16777216 8G Linux filesystem
/dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem

==== Copy Files for Arch Linux ARM ====

sudo su'' # login with your psw''
dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync'' # copy rootfs to sd part2''
mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot'' # copy bootfs to to part2/boot''
mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG'' # hide auto-menu item''
nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/etc/fstab'' # add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''
mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALarm
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Manjaro ====

dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync'' # copy rootfs to sd part3''
mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/
scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot'' # copy bootfs to to part3/boot''
nano /media/xxx/ROOT_MNJRO1/etc/fstab'' # change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''
mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG'' # hide auto-menu item''
mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL Manjaro
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Mobian ====

dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync'' # copy rootfs to microSD card partition 4''
mount /dev/sdb4 /media/xxx/rootfs1/
scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot'' # copy bootfs to to part4/boot''
nano /media/xxx/rootfs1/etc/fstab'' # replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''

cat << EOF > /media/xxx/rootfs1/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title Pinephone Pro Boot Menu
prompt 0
timeout 10
label l0
menu label Mobian 63
linux '''/boot'''/vmlinuz-6.3-rockchip
initrd '''/boot'''/initrd.img-6.3-rockchip
fdtdir '''/usr/lib'''/linux-image-6.3-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
label l1
menu label Mobian 61
linux '''/boot'''/vmlinuz-6.1-rockchip
initrd '''/boot'''/initrd.img-6.1-rockchip
fdtdir '''/usr/lib'''/linux-image-6.1-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build Multi-Distro eMMC ===

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.

==== Mount the Images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh Partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO Partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

=== Follow-Up Comments ===
# On first boot neither Phosh nor sxmo resized their partition - '''sudo resize2fs''' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-08-14T14:09:01Z

Fxc: /* Flash Multi-Distro SD Card */ style

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]].

== MicroSD card ==

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL, https://xnux.eu/rk2aw/ and https://xff.cz/git/u-boot/log/?h=ppp-2023.07

Requirements: SSH connection from Linux machine to PinePhone Pro, internet connection.

{{Info|Loader and userspace utility to flash it are free, but not open-source.}}

=== Flash Rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine

ssh <user>@<phoneip>'' # start ssh connection''
cd ~/Downloads'' # enter to directory''
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz'' # download installer''
tar -xvzf ppp.tar.gz -C ~/Downloads'' # extract''
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh'' # flash SPI''

=== Flash Multi-Distro SD Card ===

Get the compressed distribution images and decompress them (i.e. Manjaro Phosh beta 34, Mobian, Arch Linux)

Mount distribution images both partitions "/boot", "/root" for each distribution.

lsblk ''# show /loop, /sd references''
blkid ''# show UUID for the partition''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk ''(after each dd command you'll see the partition id name to adjust into scripts.)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
or sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition the microSD card ====

{{Info|A minimum capacity of 32 GB for the microSD card is recommended.}}

sudo sfdisk /dev/sdb/ <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

lsblk'' # list partitions on sd and mounted distro images''
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 16809983 16777216 8G Linux filesystem
/dev/sdb3 16809984 33587199 16777216 8G Linux filesystem
/dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem

==== Copy Files for Arch Linux ARM ====

sudo su'' # login with your psw''
dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync'' # copy rootfs to sd part2''
mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot'' # copy bootfs to to part2/boot''
mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG'' # hide auto-menu item''
nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/etc/fstab'' # add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''
mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALarm
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Manjaro ====

dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync'' # copy rootfs to sd part3''
mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/
scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot'' # copy bootfs to to part3/boot''
nano /media/xxx/ROOT_MNJRO1/etc/fstab'' # change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''
mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG'' # hide auto-menu item''
mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL Manjaro
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Mobian ====

dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync'' # copy rootfs to microSD card partition 4''
mount /dev/sdb4 /media/xxx/rootfs1/
scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot'' # copy bootfs to to part4/boot''
nano /media/xxx/rootfs1/etc/fstab'' # replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''

cat << EOF > /media/xxx/rootfs1/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title Pinephone Pro Boot Menu
prompt 0
timeout 10
label l0
menu label Mobian 63
linux '''/boot'''/vmlinuz-6.3-rockchip
initrd '''/boot'''/initrd.img-6.3-rockchip
fdtdir '''/usr/lib'''/linux-image-6.3-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
label l1
menu label Mobian 61
linux '''/boot'''/vmlinuz-6.1-rockchip
initrd '''/boot'''/initrd.img-6.1-rockchip
fdtdir '''/usr/lib'''/linux-image-6.1-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash Rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build Multi-Distro eMMC ===

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.

==== Mount the Images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh Partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO Partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

=== Follow-Up Comments ===
# On first boot neither Phosh nor sxmo resized their partition - '''sudo resize2fs''' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-08-14T14:06:56Z

Fxc: Wiki style fixes

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot and a multi-distribution image to the microSD card and eMMC of the [[PinePhone Pro]].

== MicroSD card ==

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL, https://xnux.eu/rk2aw/ and https://xff.cz/git/u-boot/log/?h=ppp-2023.07

Requirements: SSH connection from Linux machine to PinePhone Pro, internet connection.

{{Info|Loader and userspace utility to flash it are free, but not open-source.}}

=== Flash Rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine

ssh <user>@<phoneip>'' # start ssh connection''
cd ~/Downloads'' # enter to directory''
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz'' # download installer''
tar -xvzf ppp.tar.gz -C ~/Downloads'' # extract''
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh'' # flash SPI''

=== Flash Multi-Distro SD Card ===

Get the compressed distribution images and decompress them (i.e. Manjaro Phosh beta 34, Mobian, Arch Linux)

Mount distribution images both partitions "/boot", "/root" for each distro

lsblk'' # show /loop, /sd references''
blkid'' show UUID for the partition''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
or sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition SD Card (min 32GB) ====
sudo sfdisk /dev/sdb/ <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

lsblk'' # list partitions on sd and mounted distro images''
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 16809983 16777216 8G Linux filesystem
/dev/sdb3 16809984 33587199 16777216 8G Linux filesystem
/dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem

==== Copy Files for Arch Linux ARM ====

sudo su'' # login with your psw''
dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync'' # copy rootfs to sd part2''
mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot'' # copy bootfs to to part2/boot''
mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG'' # hide auto-menu item''
nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/etc/fstab'' # add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''
mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALarm
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Manjaro ====

dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync'' # copy rootfs to sd part3''
mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/
scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot'' # copy bootfs to to part3/boot''
nano /media/xxx/ROOT_MNJRO1/etc/fstab'' # change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''
mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG'' # hide auto-menu item''
mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL Manjaro
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Mobian ====

dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync'' # copy rootfs to microSD card partition 4''
mount /dev/sdb4 /media/xxx/rootfs1/
scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot'' # copy bootfs to to part4/boot''
nano /media/xxx/rootfs1/etc/fstab'' # replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''

cat << EOF > /media/xxx/rootfs1/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title Pinephone Pro Boot Menu
prompt 0
timeout 10
label l0
menu label Mobian 63
linux '''/boot'''/vmlinuz-6.3-rockchip
initrd '''/boot'''/initrd.img-6.3-rockchip
fdtdir '''/usr/lib'''/linux-image-6.3-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
label l1
menu label Mobian 61
linux '''/boot'''/vmlinuz-6.1-rockchip
initrd '''/boot'''/initrd.img-6.1-rockchip
fdtdir '''/usr/lib'''/linux-image-6.1-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash Rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build Multi-Distro eMMC ===

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.

==== Mount the Images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh Partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO Partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

=== Follow-Up Comments ===
# On first boot neither Phosh nor sxmo resized their partition - '''sudo resize2fs''' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-08-14T14:00:02Z

Fxc: /* Rk2Aw PreLoader, U-Boot & Multi-Distro on eMMC for PinePhonePro */ Moved image up

== Rk2Aw PreLoader, U-Boot & Multi-Distro on SD Card for PinePhonePro ==

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL, https://xnux.eu/rk2aw/ and https://xff.cz/git/u-boot/log/?h=ppp-2023.07

Requirements: SSH connection from linux machine to PinePhonePro, internet connection.

Note: Preloader and userspace utility to flash it are free, but not open-source.

Thanks: Megi at https://xnux.eu/log/ for the PreLoader and U-Boot, and Chris Norris for improving this guide.

=== Flash Rk2Aw PreLoader to SPI ===

Connect PinePhonePro to a Linux machine

ssh <user>@<phoneip>'' # start ssh connection''
cd ~/Downloads'' # enter to directory''
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz'' # download installer''
tar -xvzf ppp.tar.gz -C ~/Downloads'' # extract''
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh'' # flash SPI''

=== Flash Multi-Distro SD Card ===

Get the compressed distribution images and decompress them (i.e. Manjaro Phosh beta 34, Mobian, Arch Linux)

Mount distribution images both partitions "/boot", "/root" for each distro

lsblk'' # show /loop, /sd references''
blkid'' show UUID for the partition''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
or sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition SD Card (min 32GB) ====
sudo sfdisk /dev/sdb/ <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

lsblk'' # list partitions on sd and mounted distro images''
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 16809983 16777216 8G Linux filesystem
/dev/sdb3 16809984 33587199 16777216 8G Linux filesystem
/dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem

==== Copy Files for Arch Linux ARM ====

sudo su'' # login with your psw''
dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync'' # copy rootfs to sd part2''
mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot'' # copy bootfs to to part2/boot''
mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG'' # hide auto-menu item''
nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/etc/fstab'' # add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''
mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALarm
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Manjaro ====

dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync'' # copy rootfs to sd part3''
mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/
scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot'' # copy bootfs to to part3/boot''
nano /media/xxx/ROOT_MNJRO1/etc/fstab'' # change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''
mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG'' # hide auto-menu item''
mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL Manjaro
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Mobian ====

dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync'' # copy rootfs to microSD card partition 4''
mount /dev/sdb4 /media/xxx/rootfs1/
scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot'' # copy bootfs to to part4/boot''
nano /media/xxx/rootfs1/etc/fstab'' # replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''

cat << EOF > /media/xxx/rootfs1/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title Pinephone Pro Boot Menu
prompt 0
timeout 10
label l0
menu label Mobian 63
linux '''/boot'''/vmlinuz-6.3-rockchip
initrd '''/boot'''/initrd.img-6.3-rockchip
fdtdir '''/usr/lib'''/linux-image-6.3-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
label l1
menu label Mobian 61
linux '''/boot'''/vmlinuz-6.1-rockchip
initrd '''/boot'''/initrd.img-6.1-rockchip
fdtdir '''/usr/lib'''/linux-image-6.1-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Rk2Aw PreLoader, U-Boot & Multi-Distro on eMMC for PinePhonePro ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to be building the eMMC. Note that below, arch is booted from the microSD card and the microSD card shows as /dev/mmcblk1

=== Flash Rk2Aw PreLoader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build Multi-Distro eMMC ===

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.

==== Mount the Images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh Partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO Partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

=== Follow-Up Comments ===
# On first boot neither Phosh nor sxmo resized their partition - '''sudo resize2fs''' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.

PinePhone Pro/Create a multi-distribution image using rk2aw

2023-08-14T13:58:50Z

Fxc: Moved image up, line fix

== Rk2Aw PreLoader, U-Boot & Multi-Distro on SD Card for PinePhonePro ==

[[File:multi_distro_sd.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro and Mobian (kernel 6.1 and 6.3)]]

References: https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL, https://xnux.eu/rk2aw/ and https://xff.cz/git/u-boot/log/?h=ppp-2023.07

Requirements: SSH connection from linux machine to PinePhonePro, internet connection.

Note: Preloader and userspace utility to flash it are free, but not open-source.

Thanks: Megi at https://xnux.eu/log/ for the PreLoader and U-Boot, and Chris Norris for improving this guide.

=== Flash Rk2Aw PreLoader to SPI ===

Connect PinePhonePro to a Linux machine

ssh <user>@<phoneip>'' # start ssh connection''
cd ~/Downloads'' # enter to directory''
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz'' # download installer''
tar -xvzf ppp.tar.gz -C ~/Downloads'' # extract''
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
sudo ./spinor-flash-initial-setup.sh'' # flash SPI''

=== Flash Multi-Distro SD Card ===

Get the compressed distribution images and decompress them (i.e. Manjaro Phosh beta 34, Mobian, Arch Linux)

Mount distribution images both partitions "/boot", "/root" for each distro

lsblk'' # show /loop, /sd references''
blkid'' show UUID for the partition''
├─loop0p1 /media/xxx/BOOT_MNJRO
└─loop0p2 /media/xxx/ROOT_MNJRO
├─loop1p1 /media/xxx/boot
└─loop1p2 /media/xxx/rootfs
├─loop2p1 /media/xxx/52CA-6165
└─loop2p2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
└─sdb disk '' (after each dd command you'll see the partition id name to adjust into scripts.)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # quick erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
or sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # slow erase sd card. i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''

==== Partition SD Card (min 32GB) ====
sudo sfdisk /dev/sdb/ <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=10G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=10G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

lsblk'' # list partitions on sd and mounted distro images''
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 16809983 16777216 8G Linux filesystem
/dev/sdb3 16809984 33587199 16777216 8G Linux filesystem
/dev/sdb4 33587200 60524543 26937344 12.8G Linux filesystem

==== Copy Files for Arch Linux ARM ====

sudo su'' # login with your psw''
dd if=/dev/loop2p2 of=/dev/sdb2 bs=1M status=progress conv=fsync'' # copy rootfs to sd part2''
mount /dev/sdb2 /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441
scp -r /media/xxx/52CA-6165/* /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot'' # copy bootfs to to part2/boot''
mv /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/boot.scr /media/xxx/3d99072c-9fd6-4316-8526-9192e192c441<del>1</del>/boot/boot.scrORIG'' # hide auto-menu item''
nano /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/etc/fstab'' # add PARTLABEL=ALARM and delete UUID=xxx from second line, delete /boot entry''
mkdir /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALarm
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Manjaro ====

dd if=/dev/loop0p2 of=/dev/sdb3 bs=1M status=progress conv=fsync'' # copy rootfs to sd part3''
mount /dev/sdb3 /media/xxx/ROOT_MNJRO1/
scp -r /media/xxx/BOOT_MNJRO/* /media/xxx/ROOT_MNJRO1/boot'' # copy bootfs to to part3/boot''
nano /media/xxx/ROOT_MNJRO1/etc/fstab'' # change UUID=xxx to PARTLABEL=MANJARO, delete /boot line''
mv /media/xxx/ROOT_MNJRO1/boot/boot.scr /media/xxx/ROOT_MNJRO1/boot/boot.scrORIG'' # hide auto-menu item''
mkdir /media/xxx/ROOT_MNJRO1/boot/extlinux'' # add directory''

cat << EOF > /media/xxx/3d99072c-9fd6-4316-8526-9192e192c4411/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL Manjaro
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Copy Files for Mobian ====

dd if=/dev/loop1p2 of=/dev/sdb4 bs=1M status=progress conv=fsync'' # copy rootfs to microSD card partition 4''
mount /dev/sdb4 /media/xxx/rootfs1/
scp -r /media/xxx/boot/* /media/xxx/rootfs1/boot'' # copy bootfs to to part4/boot''
nano /media/xxx/rootfs1/etc/fstab'' # replace UUID=xxx with PARTLABEL=MOBIAN and delete UUID=xxx from second line. Delete /boot line''

cat << EOF > /media/xxx/rootfs1/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title Pinephone Pro Boot Menu
prompt 0
timeout 10
label l0
menu label Mobian 63
linux '''/boot'''/vmlinuz-6.3-rockchip
initrd '''/boot'''/initrd.img-6.3-rockchip
fdtdir '''/usr/lib'''/linux-image-6.3-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
label l1
menu label Mobian 61
linux '''/boot'''/vmlinuz-6.1-rockchip
initrd '''/boot'''/initrd.img-6.1-rockchip
fdtdir '''/usr/lib'''/linux-image-6.1-rockchip/
append root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Rk2Aw PreLoader, U-Boot & Multi-Distro on eMMC for PinePhonePro ==

Make sure you boot from the microSD card in your PinePhone Pro as we are going to be building the eMMC. Note that below, arch is booted from the microSD card and the microSD card shows as /dev/mmcblk1

=== Flash Rk2Aw PreLoader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follows:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build Multi-Distro eMMC ===

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.

==== Mount the Images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====
dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh Partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO Partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

=== Follow-Up Comments ===
# On first boot neither Phosh nor sxmo resized their partition - '''sudo resize2fs''' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# The end result is a boot screen as follows:

[[File:P1090461.JPG|200px|thumb|left|Options to boot Phosh or sxmo]]