PINE64 - User contributions [en]

PineModems

2021-08-30T04:32:19Z

Biktorgj: Small updates to the partition table description

= Modems used in Pine64 boards and devices =

== Quectel EG25-G Modem ==

Quectel EG25-G is an LTE Cat 4 module optimized specially for M2M and IoT applications. It is used in the [[PinePhone]].

* Specifications: [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
* Hardware design: [[File:Quectel_EG25-G_Hardware_Design_V1.4.pdf]]
* AT Interface reference manual:
** 1.3 for EC25: [[File:Quectel_EC25&EC21_AT_Commands_Manual_V1.3.pdf]]
** 2.0 for EC25 and EG25-G: [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
* AT Interface file operations: [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]
* GNSS Application note: [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_GNSS_Application_Note_V1.3.pdf]]

=== Specifications ===

{| class="wikitable"
| Processor Family || Qualcomm MDM9607
|-
| CPU || Qualcomm MDM9207
|-
| Cores || 1 ACPU Core, Qualcomm Hexagon DSP
|-
| Total RAM || 256Mb
|-
| Total flash space || 256Mb
|-
| Available RAM for the ACPU || 160Mb
|}

=== NAND Partition table layout ===

{| class="wikitable"
! Index
! Name
! Description
|-
| MTD0 || <code>SBL</code>
| Secondary Bootloader, called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
|-
| MTD1 || <code>mibib</code>
| NAND Partition table
|-
| MTD2 || <code>EFS2</code>
| IMEI and settings used by the ADSP are stored here
|-
| MTD3 || <code>sys_rev</code>
| Unexplored
|-
| MTD4 || <code>rawdata</code>
| This is where FOTA update data exists before being commited to system or recoveryfs partitions
|-
| MTD5 || <code>tz</code>
| TrustZone kernel
|-
| MTD6 || <code>rpm</code>
| Resource / Power Manager
|-
| MTD7 || <code>cust_info</code>
| Unexplored
|-
| MTD8 || <code>aboot</code>
| Application Bootloader. Uses [https://github.com/littlekernel/lk LK] (LittleKernel, LK embedded kernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
|-
| MTD9 || <code>boot</code>
| [https://www.openembedded.org/wiki/Main_Page OpenEmbedded] boot kernel + DTB
|-
| MTD10 || <code>recovery</code>
| Recovery kernel (used for FOTA updates)
|-
| MTD11 || <code>modem</code>
| ADSP firmware blobs
|-
| MTD12 || <code>misc</code>
| Some settings are stored here, along with commands that need to be picked by LK on next boot (to reboot to fastboot or recovery mode)
|-
| MTD13 || <code>recoveryfs</code>
| Recovery filesystem image (FOTA updates)
|-
| MTD14 || <code>usr_data</code>
| User data partition (<code>/data</code> when mounted by OpenEmbedded)
|-
| MTD15 || <code>sec</code>
| Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools
|-
| MTD16 || <code>system</code>
| Linux OpenEmbedded root image, formatted in UBIFS (Unsorted Block Image File System, [https://en.wikipedia.org/wiki/UBIFS Wikipedia])
|}

=== Firmware Recovery ===

{{warning|1= The following instructions are directed towards expert-level users and developers!}}

The System partition is mounted as read-only mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.

[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]

The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might:
* not show anywhere (USB device missing)
* or malfunction (no radio but USB working)
* or enter EDL mode, if the entire flash is corrupt.

'''Boot the device in EDL mode'''

To check if the device is booted in EDL mode, run <code>lsusb</code> (a part of the <code>usbutils</code> package) in a terminal and inspect the output. You should see the following device listed:

Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins on the PinePhone motherboard.

# Power off the phone
# short the two test points
# boot the phone while keeping the test points shorted until fully booted up, at least until you hear the camera clicking twice (which is normally when the modem is powered).

'''Get the Firmware Recovery Package'''

The Firmware Recovery Package is at: https://github.com/Biktorgj/quectel_eg25_recovery

Either clone its repo with git, or download its archive & unzip it.

As you should have no access to the Internet on PinePhone when its modem need a Recovery, you can fetch it on other devices and copy it to the Pinephone.

'''Execute the Quectel QFirehose utility'''

Once in EDL mode, open a terminal, navigate to the root directory of the recovery package, and run:

* If you use an ARM64 distribution (most likely): <code>sudo ./qfirehose -f ./</code> or <code>sudo ./qfirehose_arm64 -f ./</code>
* If you use an ARMHF (32 bit) distribution: <code>sudo ./qfirehose_armhf -f ./</code>

It will reboot the modem after finished. After about 30 seconds, it will get back up and running. To check the firmware version after that, use an AT command <code>AT+QGMR</code> like at [[PinePhone#Firmware_update]].

=== Bootloader unlocking ===

{{warning|1= The following instructions are directed towards expert-level users and developers!}}

The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

Unlocked bootloader:
* Source code: https://github.com/Biktorgj/quectel_lk
* Prebuilt binary releases: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

{{warning|1= The following instructions are directed towards expert-level users and developers!}}

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable.

* The source code release for the kernel provided by the manufacturer is incomplete and won't build
* Common Android tools like mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTBs attached.
* Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a '''work in progress''' SDK to allow creating custom kernels and system images, which can be downloaded from the following repository: https://github.com/Biktorgj/pinephone_modem_sdk

See its readme for infomations and instructions. Once downloaded, you should run the <code>init.sh</code> script, which will create all the base directories and download all the different repositories required to build. After the initial setup is complete, run<code>make</code> without arguments to list the available options.

[[Category:PinePhone]]

PineModems

2020-10-10T05:12:32Z

Biktorgj: /* Firmware Recovery */

= Modems used in Pine64 boards and devices =

=== Quectel EG25-G Modem ===

* Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf
* Hardware design: https://www.quectel.com/UploadImage/Downlad/Quectel_EG25-G_Hardware_Design_V1.2.pdf
* AT Interface reference manual: https://www.quectel.com/UploadImage/Downlad/Quectel_EC25&EC21_AT_Commands_Manual_V1.3.pdf
* AT Interface file operations: https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf

=== Specifications ===
* Processor Family: Qualcomm MDM9607
* CPU: Qualcomm MDM9207
* Cores: 1 ACPU Core, Qualcomm Hexagon DSP
* Total RAM: 256Mb
* Total flash space: 256Mb
* Available RAM for the ACPU: 160Mb

=== NAND Partition table layout ===

* MTD0: SBL (Secondary Bootloader), called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
* MTD1: mibib (Unknown, used by the DSP)
* MTD2: EFS2 (Unexplored, probably NVRAM data, Used by the DSP)
* MTD3: sys_rev: Unexplored
* MTD4: rawdata: This is where FOTA update data exists before being commited to system or recoveryfs partitions
* MTD5: tz: TrustZone kernel
* MTD6: rpm: Resource / Power Manager
* MTD7: cust_info: Unexplored
* MTD8: aboot: Application Bootloader. Uses LK (LittleKernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
* MTD9: boot: OpenEmbedded boot kernel + DTB
* MTD10: recovery: Recovery kernel (normally unused)
* MTD11: modem: ADSP firmware blobs
* MTD12: misc: Unexplored
* MTD13: recoveryfs: Recovery filesystem image (FOTA updates)
* MTD14: usr_data: User data partition (/data when mounted by OpenEmbedded)
* MTD15: sec (Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools)
* MTD16: system (Linux OpenEmbedded root image, formatted in Ubifs filesystem)

=== Firmware Recovery ===
The System partition is mounted as readonly mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.
[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]
The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might not show anywhere (USB device missing), it might malfunction (no radio but USB working), or it might enter EDL mode if the entire flash is corrupt

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins in the PinePhone Motherboard. Power off the phone, short the two test points and start it again while keeping the pads shorted at least until you hear the camera clicking twice (which is normally when the modem is powered)

Download the Firmware Recovery Package and copy it to the Pinephone: https://github.com/Biktorgj/quectel_eg25_recovery/
To check if you're currently booted in EDL mode, run lsusb in a terminal and inspect the output.
You should see the following device listed: Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Once in EDL mode, open a terminal and go to the root directory of the recovery package, and run:

If you use an ARM64 distro (most likely) ./qfirehose_arm64 -f ./

If you use an ARMHF (32 bit) distro: ./qfirehose_armhf -f ./

After it finishes, it will reboot the modem and after about 30 seconds it will get back up and running

=== Bootloader unlocking ===
The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

The source code for the Bootloader is here: https://github.com/Biktorgj/quectel_lk
Prebuilt binary releases can be downloaded from here: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable. The source code release for the kernel provided by the manufacturer is incomplete and won't build, and common Android tools mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTB's attached. Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a _Work in progress_ SDK to allow creating custom kernels and system images, which can be downloaded from the following repo: https://github.com/Biktorgj/pinephone_modem_sdk

Once downloaded, you should run the 'init.sh' script, which will create all the base directories and download all the different repos required to build. After the initial setup is complete, run 'make' without arguments to list the available options

PineModems

2020-10-10T05:11:07Z

Biktorgj: /* Quectel EG25-G Modem */

= Modems used in Pine64 boards and devices =

=== Quectel EG25-G Modem ===

* Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf
* Hardware design: https://www.quectel.com/UploadImage/Downlad/Quectel_EG25-G_Hardware_Design_V1.2.pdf
* AT Interface reference manual: https://www.quectel.com/UploadImage/Downlad/Quectel_EC25&EC21_AT_Commands_Manual_V1.3.pdf
* AT Interface file operations: https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf

=== Specifications ===
* Processor Family: Qualcomm MDM9607
* CPU: Qualcomm MDM9207
* Cores: 1 ACPU Core, Qualcomm Hexagon DSP
* Total RAM: 256Mb
* Total flash space: 256Mb
* Available RAM for the ACPU: 160Mb

=== NAND Partition table layout ===

* MTD0: SBL (Secondary Bootloader), called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
* MTD1: mibib (Unknown, used by the DSP)
* MTD2: EFS2 (Unexplored, probably NVRAM data, Used by the DSP)
* MTD3: sys_rev: Unexplored
* MTD4: rawdata: This is where FOTA update data exists before being commited to system or recoveryfs partitions
* MTD5: tz: TrustZone kernel
* MTD6: rpm: Resource / Power Manager
* MTD7: cust_info: Unexplored
* MTD8: aboot: Application Bootloader. Uses LK (LittleKernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
* MTD9: boot: OpenEmbedded boot kernel + DTB
* MTD10: recovery: Recovery kernel (normally unused)
* MTD11: modem: ADSP firmware blobs
* MTD12: misc: Unexplored
* MTD13: recoveryfs: Recovery filesystem image (FOTA updates)
* MTD14: usr_data: User data partition (/data when mounted by OpenEmbedded)
* MTD15: sec (Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools)
* MTD16: system (Linux OpenEmbedded root image, formatted in Ubifs filesystem)

=== Firmware Recovery ===
The System partition is mounted as readonly mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.
[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]
The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might not show anywhere (USB device missing), it might malfunction (no radio but USB working), or it might enter EDL mode if the entire flash is corrupt

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins in the PinePhone Motherboard. Power off the phone, short the two test points and start it again while keeping the pads shorted at least until you hear the camera clicking twice (which is normally when the modem is powered)

Download the Firmware Recovery Package and copy it to the Pinephone: https://github.com/Biktorgj/quectel_eg25_recovery/archive/master.zip
To check if you're currently booted in EDL mode, run lsusb in a terminal and inspect the output.
You should see the following device listed: Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Once in EDL mode, open a terminal and go to the root directory of the recovery package, and run:

If you use an ARM64 distro (most likely) ./qfirehose_arm64 -f ./

If you use an ARMHF (32 bit) distro: ./qfirehose_armhf -f ./

After it finishes, it will reboot the modem and after about 30 seconds it will get back up and running

=== Bootloader unlocking ===
The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

The source code for the Bootloader is here: https://github.com/Biktorgj/quectel_lk
Prebuilt binary releases can be downloaded from here: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable. The source code release for the kernel provided by the manufacturer is incomplete and won't build, and common Android tools mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTB's attached. Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a _Work in progress_ SDK to allow creating custom kernels and system images, which can be downloaded from the following repo: https://github.com/Biktorgj/pinephone_modem_sdk

Once downloaded, you should run the 'init.sh' script, which will create all the base directories and download all the different repos required to build. After the initial setup is complete, run 'make' without arguments to list the available options

PineModems

2020-10-10T05:09:56Z

Biktorgj: /* NAND Partition table layout */

= Modems used in Pine64 boards and devices =

=== Quectel EG25-G Modem ===

* Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf
* Hardware design: https://www.quectel.com/UploadImage/Downlad/Quectel_EG25-G_Hardware_Design_V1.2.pdf
* AT Interface reference manual: https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf

=== Specifications ===
* Processor Family: Qualcomm MDM9607
* CPU: Qualcomm MDM9207
* Cores: 1 ACPU Core, Qualcomm Hexagon DSP
* Total RAM: 256Mb
* Total flash space: 256Mb
* Available RAM for the ACPU: 160Mb

=== NAND Partition table layout ===

* MTD0: SBL (Secondary Bootloader), called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
* MTD1: mibib (Unknown, used by the DSP)
* MTD2: EFS2 (Unexplored, probably NVRAM data, Used by the DSP)
* MTD3: sys_rev: Unexplored
* MTD4: rawdata: This is where FOTA update data exists before being commited to system or recoveryfs partitions
* MTD5: tz: TrustZone kernel
* MTD6: rpm: Resource / Power Manager
* MTD7: cust_info: Unexplored
* MTD8: aboot: Application Bootloader. Uses LK (LittleKernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
* MTD9: boot: OpenEmbedded boot kernel + DTB
* MTD10: recovery: Recovery kernel (normally unused)
* MTD11: modem: ADSP firmware blobs
* MTD12: misc: Unexplored
* MTD13: recoveryfs: Recovery filesystem image (FOTA updates)
* MTD14: usr_data: User data partition (/data when mounted by OpenEmbedded)
* MTD15: sec (Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools)
* MTD16: system (Linux OpenEmbedded root image, formatted in Ubifs filesystem)

=== Firmware Recovery ===
The System partition is mounted as readonly mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.
[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]
The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might not show anywhere (USB device missing), it might malfunction (no radio but USB working), or it might enter EDL mode if the entire flash is corrupt

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins in the PinePhone Motherboard. Power off the phone, short the two test points and start it again while keeping the pads shorted at least until you hear the camera clicking twice (which is normally when the modem is powered)

Download the Firmware Recovery Package and copy it to the Pinephone: https://github.com/Biktorgj/quectel_eg25_recovery/archive/master.zip
To check if you're currently booted in EDL mode, run lsusb in a terminal and inspect the output.
You should see the following device listed: Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Once in EDL mode, open a terminal and go to the root directory of the recovery package, and run:

If you use an ARM64 distro (most likely) ./qfirehose_arm64 -f ./

If you use an ARMHF (32 bit) distro: ./qfirehose_armhf -f ./

After it finishes, it will reboot the modem and after about 30 seconds it will get back up and running

=== Bootloader unlocking ===
The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

The source code for the Bootloader is here: https://github.com/Biktorgj/quectel_lk
Prebuilt binary releases can be downloaded from here: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable. The source code release for the kernel provided by the manufacturer is incomplete and won't build, and common Android tools mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTB's attached. Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a _Work in progress_ SDK to allow creating custom kernels and system images, which can be downloaded from the following repo: https://github.com/Biktorgj/pinephone_modem_sdk

Once downloaded, you should run the 'init.sh' script, which will create all the base directories and download all the different repos required to build. After the initial setup is complete, run 'make' without arguments to list the available options

PinePhone

2020-09-16T10:15:08Z

Biktorgj: /* Modem and carrier support */

The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. The BraveHeart Edition was the first publicly-available version of the phone, though it came without a fully functional OS (factory test image) and was geared specifically towards tinkerers and hackers. Its successor is the Community Edition, the first Community Edition started to ship in June 2020. The phone will be available for at least five years.

== First time installation ==

[[File:PinePhone-3.jpg|400px|thumb|right|PinePhone is capable of running a multitude of different Linux mobile OSes]]

[[File:PinePhoneSides.svg|400px|thumb|right|Backward and front of PinePhone UBPorts Edition]]

From the factory the battery has a sticker on it that isolates the battery from the phone. The battery '''will not''' charge until this is removed.

After unboxing remove the back panel using the notch in the corner of the back panel. Then remove the battery and peel off the clear plastic sticker below it that isolates the charging contact. Then replace the battery. See [[PinePhone#Battery|Battery]] for more information.

== 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 
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" 
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) 
'''Communication: G25-G'''
: '''LTE:''' B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41
: '''WCDMA:''' B1, B2, B4, B5, B6, B8, B19
: '''GSM:''' 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, gyro, proximity, ambient light, compass 
'''Killswitches:''' 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
| Quectel EG25-G
|-
| GNSS/GPS
| Quectel EG25-G
|-
| Magnetometer
| ST LIS3MDL
|-
| Ambient light / Proximity
| SensorTek STK3335
|-
| Sixaxis
| InvenSense MPU-6050
|-
| Vibration motor
| Yes, unknown model
|-
| Notification LED
| LED0603RGB
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| X-Powers AXP803
|}

== Hardware revisions ==

# [[Project Anakin]]
# [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]
# [[PinePhone v1.1 - Braveheart]]
# [[PinePhone v1.2‎]] - Community Edition

== Hardware accessory ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, HDMI port and Ethernet connection. The driver that would make this connection available is not supported at this time.

=== Pogo pins ===

The PinePhone has 6 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 input to charge the battery, power source and an I2C interface.

[[File:Pinephone pogo.png|none|400px]]

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| 5V / VBUS
| VBAT
| GND
|}

The VBUS pin is powered by USB and is 5V. The second power pin is VBAT, which connects to the battery voltage. 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 [http://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp here].

=== Serial console ===

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

[[File:PinePhone_Serial_Cable.png|none|400px]]

You can buy a serial debug cable from the [https://store.pine64.org/product/pinebook-serial-console/ Pine64 Store]. The store cable uses a 4 ring plug, as seen in the [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf 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.

== Killswitch configuration ==

[[File:PinePhone switches.jpeg|400px|thumb|right|Photo of BraveHeart switches from OSAKANA TARO on Twitter]]

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.5mm 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.5mm audio jack, "off" switches the jack to hardware UART mode.
|}

== Battery ==

{{Hint|The EG25 modem and RTL8723CS WiFi/bluetooth do not work without battery power, even if you are supplying enough power to the PinePhone with USB-C.}}

The [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf supplied battery] is [https://forum.pine64.org/showthread.php?tid=8120&pid=53307#pid53307 meant to be] compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone.
* The extended life aftermarket BBU do fit, however, somewhat firmly.
* There is [https://forum.pine64.org/showthread.php?tid=8563&pid=55053#pid55053 a report] that the EB-BJ700CBE isn't quite the same size, causing the back not to fit properly.

The battery terminals, in order from nearest the edge to nearest the middle, are:

# +ve
# thermistor
# -ve
# 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 [https://forum.pine64.org/showthread.php?tid=8563&pid=55377#pid55377 can be recharged] by connecting the phone to a charger. Once it has charged sufficiently you will be able to boot the phone.

If your battery is hard to remove from the phone, try loosening the screws around it. Possibly cutting up a piece of plastic and sliding it under the battery as a pull tab can work too.

{{Note|The phone ships with a plastic sticker between the battery and the phone. You need to open the back cover (gently), then remove the battery and finally remove the sticker and check that the pins aren't bent. This is to protect the device from turning on during shipping.}}

If using an aftermarket battery on the CE edition phones, removing the lower tabs is not necessary as there is space supplied in the compartment.

<gallery mode="packed", heights=300px>
Image:PinePhone battery1.png|Photo of Brave Heart case from OSAKANA TARO on Twitter
Image:PinePhone battery3.jpeg|Photo of Brave Heart battery sticker from OSAKANA TARO on Twitter
</gallery>

== Modem and carrier support ==
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 under the [[#Specifications|specifications]] section).

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.

=== Voice mail ===

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

=== APN settings ===

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 ===

There is a document about using the modem from January 18th 2020 by user ''megi'' [https://megous.com/dl/tmp/modem.txt here]. The script at the end to disable the modem before power off is pretty essential to avoid corrupting your modem's flash memory.

=== Firmware modifications ===

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

== 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.

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.

=== Installation instructions ===

For instructions on how to install the operating systems to the eMMC or SD card see [[PinePhone Installation Instructions]].

=== Flashing eMMC using Jumpdrive ===

[[File:jumpdrive.jpg|400px|thumb|right|Jumpdrive running on the PinePhone]]
The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS.
This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.
The process of flashing an OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a SD card. You can use the 'DD' command or a utility such as Etcher or Gnome Disks, etc.

Latest Jumpdrive can be found [https://github.com/dreemurrs-embedded/Jumpdrive/releases/ here].

==== Detailed usage instructions ====

# Download the Jumpdrive image
# Flash the Jumpdrive image to a micro SD card
# Boot the PinePhone from the Jumpdrive micro SD card
# Connect the PinePhone to your computer using USB-A -> USB-C cable
# Flash the exposed PinePhone drive (e.g. /dev/mm..., check for the right device in dmesg, GNOME disks, or similar, and make sure it's unmounted) with your chosen OS image
# Once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card
# The process is now finished, and you can boot from eMMC

Jumpdrive also acts as a rescue image in case if you messed up your installation. To do so, you can telnet to '''172.16.42.1''', mount rootfs and fix it!

==== Resize file system ====

If you flash a 4GB image distribution (such as phosh+debian) to your eMMC, your eMMC will only have a 3.7GB partition on it. To use the entire 14.7GB on the eMMC, run the following commands:

# sudo cfdisk /dev/sdX
# Change to [Resize] in the ncurses program, resize the 3.7GB partition to 14.7GB, and [Write]
# sudo resize2fs /dev/sdXY

Replace X with your drive's name. Replace Y with the partition you resized in cfdisk.

==== Feedback ====

If you've found an issue or want to improve the tool consider these sites:

* Issues: https://github.com/dreemurrs-embedded/Jumpdrive/issues
* Pull Requests: https://github.com/dreemurrs-embedded/Jumpdrive/pulls

== Frequently asked questions ==

For a list of frequently asked questions (including information regarding the shipping) see [[PinePhone FAQ]].

== PinePhone board information, schematics and certifications ==
* PinePhone mainboard schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
** [http://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]]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
* PinePhone USB-C small board schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]
** [http://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]
** [http://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:
** [http://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]
** [http://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinPhone CE RED Certificate]
** [http://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]
* [[PinePhone component list]]

== Datasheets for components and peripherals ==

* Allwinner A64 SoC information:
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [http://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:
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

* LPDDR3 (178 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

* eMMC information:
** [http://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC datasheet]

* CMOS camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel specification]
** [http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller datasheet]

* Lithium battery information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery specification]
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV curve chart]

* WiFi/BT module information:
** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

* LTE module information:
** [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Standard_Specification_V1.2.pdf Quectel EG25-G LTE Module specification]
** [[Media:Quectel EC25EC21 AT Commands Manual V1.2.pdf|EC25&EC21 AT Commands Manual]]

* Sensors:
** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]
** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS datasheet]
** [http://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:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone case exploded diagram]
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone back cover 3D file]

== Developer works ==
=== Megous ===

* [https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting start with PinePhone Hardware]
* [https://xnux.eu/devices/pine64-pinephone.html#toc-pine64-pinephone State of development progress]
* [https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]

== External links ==
* [https://store.pine64.org/?post_type=product Pine64 shop]

[[Category:PinePhone]]

PineModems

2020-09-16T09:36:37Z

Biktorgj: /* Firmware Recovery */

= Modems used in Pine64 boards and devices =

=== Quectel EG25-G Modem ===

* Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf
* Hardware design: https://www.quectel.com/UploadImage/Downlad/Quectel_EG25-G_Hardware_Design_V1.2.pdf
* AT Interface reference manual: https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf

=== Specifications ===
* Processor Family: Qualcomm MDM9607
* CPU: Qualcomm MDM9207
* Cores: 1 ACPU Core, Qualcomm Hexagon DSP
* Total RAM: 256Mb
* Total flash space: 256Mb
* Available RAM for the ACPU: 160Mb

=== NAND Partition table layout ===

* MTD0: SBL (Secondary Bootloader), called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
* MTD1: mibib (Unknown, used by the DSP)
* MTD2: EFS2 (Unexplored, probably NVRAM data, Used by the DSP)
* MTD3: sys_rev: Unexplored
* MTD4: rawdata: Unexplored
* MTD5: tz: TrustZone kernel
* MTD6: rpm: Resource / Power Manager
* MTD7: cust_info: Unexplored
* MTD8: aboot: Application Bootloader. Uses LK (LittleKernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
* MTD9: boot: OpenEmbedded boot kernel + DTB
* MTD10: recovery: Recovery kernel (normally unused)
* MTD11: modem: ADSP firmware blobs
* MTD12: misc: Unexplored
* MTD13: recoveryfs: Recovery filesystem image (FOTA updates)
* MTD14: usr_data: User data partition (/data when mounted by OpenEmbedded)
* MTD15: sec (Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools)
* MTD16: system (Linux OpenEmbedded root image, formatted in Ubifs filesystem)

=== Firmware Recovery ===
The System partition is mounted as readonly mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.
[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]
The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might not show anywhere (USB device missing), it might malfunction (no radio but USB working), or it might enter EDL mode if the entire flash is corrupt

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins in the PinePhone Motherboard. Power off the phone, short the two test points and start it again while keeping the pads shorted at least until you hear the camera clicking twice (which is normally when the modem is powered)

Download the Firmware Recovery Package and copy it to the Pinephone: https://github.com/Biktorgj/quectel_eg25_recovery/archive/master.zip
To check if you're currently booted in EDL mode, run lsusb in a terminal and inspect the output.
You should see the following device listed: Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Once in EDL mode, open a terminal and go to the root directory of the recovery package, and run:

If you use an ARM64 distro (most likely) ./qfirehose_arm64 -f ./

If you use an ARMHF (32 bit) distro: ./qfirehose_armhf -f ./

After it finishes, it will reboot the modem and after about 30 seconds it will get back up and running

=== Bootloader unlocking ===
The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

The source code for the Bootloader is here: https://github.com/Biktorgj/quectel_lk
Prebuilt binary releases can be downloaded from here: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable. The source code release for the kernel provided by the manufacturer is incomplete and won't build, and common Android tools mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTB's attached. Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a _Work in progress_ SDK to allow creating custom kernels and system images, which can be downloaded from the following repo: https://github.com/Biktorgj/pinephone_modem_sdk

Once downloaded, you should run the 'init.sh' script, which will create all the base directories and download all the different repos required to build. After the initial setup is complete, run 'make' without arguments to list the available options

PineModems

2020-09-16T09:36:02Z

Biktorgj:

= Modems used in Pine64 boards and devices =

=== Quectel EG25-G Modem ===

* Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf
* Hardware design: https://www.quectel.com/UploadImage/Downlad/Quectel_EG25-G_Hardware_Design_V1.2.pdf
* AT Interface reference manual: https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf

=== Specifications ===
* Processor Family: Qualcomm MDM9607
* CPU: Qualcomm MDM9207
* Cores: 1 ACPU Core, Qualcomm Hexagon DSP
* Total RAM: 256Mb
* Total flash space: 256Mb
* Available RAM for the ACPU: 160Mb

=== NAND Partition table layout ===

* MTD0: SBL (Secondary Bootloader), called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
* MTD1: mibib (Unknown, used by the DSP)
* MTD2: EFS2 (Unexplored, probably NVRAM data, Used by the DSP)
* MTD3: sys_rev: Unexplored
* MTD4: rawdata: Unexplored
* MTD5: tz: TrustZone kernel
* MTD6: rpm: Resource / Power Manager
* MTD7: cust_info: Unexplored
* MTD8: aboot: Application Bootloader. Uses LK (LittleKernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
* MTD9: boot: OpenEmbedded boot kernel + DTB
* MTD10: recovery: Recovery kernel (normally unused)
* MTD11: modem: ADSP firmware blobs
* MTD12: misc: Unexplored
* MTD13: recoveryfs: Recovery filesystem image (FOTA updates)
* MTD14: usr_data: User data partition (/data when mounted by OpenEmbedded)
* MTD15: sec (Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools)
* MTD16: system (Linux OpenEmbedded root image, formatted in Ubifs filesystem)

=== Firmware Recovery ===
The System partition is mounted as readonly mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.

The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might not show anywhere (USB device missing), it might malfunction (no radio but USB working), or it might enter EDL mode if the entire flash is corrupt

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins in the PinePhone Motherboard. Power off the phone, short the two test points and start it again while keeping the pads shorted at least until you hear the camera clicking twice (which is normally when the modem is powered)
[[File:Pinephone-EG25-Recovery.jpg|thumb|PinePhone USB_BOOT test points]]

Download the Firmware Recovery Package and copy it to the Pinephone: https://github.com/Biktorgj/quectel_eg25_recovery/archive/master.zip
To check if you're currently booted in EDL mode, run lsusb in a terminal and inspect the output.
You should see the following device listed: Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Once in EDL mode, open a terminal and go to the root directory of the recovery package, and run:

If you use an ARM64 distro (most likely) ./qfirehose_arm64 -f ./

If you use an ARMHF (32 bit) distro: ./qfirehose_armhf -f ./

After it finishes, it will reboot the modem and after about 30 seconds it will get back up and running

=== Bootloader unlocking ===
The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

The source code for the Bootloader is here: https://github.com/Biktorgj/quectel_lk
Prebuilt binary releases can be downloaded from here: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable. The source code release for the kernel provided by the manufacturer is incomplete and won't build, and common Android tools mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTB's attached. Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a _Work in progress_ SDK to allow creating custom kernels and system images, which can be downloaded from the following repo: https://github.com/Biktorgj/pinephone_modem_sdk

Once downloaded, you should run the 'init.sh' script, which will create all the base directories and download all the different repos required to build. After the initial setup is complete, run 'make' without arguments to list the available options

PineModems

2020-09-16T09:35:17Z

Biktorgj:

= Modems used in Pine64 boards and devices =

=== Quectel EG25-G Modem ===

* Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf
* Hardware design: https://www.quectel.com/UploadImage/Downlad/Quectel_EG25-G_Hardware_Design_V1.2.pdf
* AT Interface reference manual: https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf

=== Specifications ===
* Processor Family: Qualcomm MDM9607
* CPU: Qualcomm MDM9207
* Cores: 1 ACPU Core, Qualcomm Hexagon DSP
* Total RAM: 256Mb
* Total flash space: 256Mb
* Available RAM for the ACPU: 160Mb

=== NAND Partition table layout ===

* MTD0: SBL (Secondary Bootloader), called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
* MTD1: mibib (Unknown, used by the DSP)
* MTD2: EFS2 (Unexplored, probably NVRAM data, Used by the DSP)
* MTD3: sys_rev: Unexplored
* MTD4: rawdata: Unexplored
* MTD5: tz: TrustZone kernel
* MTD6: rpm: Resource / Power Manager
* MTD7: cust_info: Unexplored
* MTD8: aboot: Application Bootloader. Uses LK (LittleKernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
* MTD9: boot: OpenEmbedded boot kernel + DTB
* MTD10: recovery: Recovery kernel (normally unused)
* MTD11: modem: ADSP firmware blobs
* MTD12: misc: Unexplored
* MTD13: recoveryfs: Recovery filesystem image (FOTA updates)
* MTD14: usr_data: User data partition (/data when mounted by OpenEmbedded)
* MTD15: sec (Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools)
* MTD16: system (Linux OpenEmbedded root image, formatted in Ubifs filesystem)

=== Firmware Recovery ===
The System partition is mounted as readonly mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.

The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might not show anywhere (USB device missing), it might malfunction (no radio but USB working), or it might enter EDL mode if the entire flash is corrupt

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins in the PinePhone Motherboard. Power off the phone, short the two test points and start it again while keeping the pads shorted at least until you hear the camera clicking twice (which is normally when the modem is powered)
[[File:Pinephone-EG25-Recovery.jpg|400px|thumb|right|PinePhone USB_BOOT test points]]

Download the Firmware Recovery Package and copy it to the Pinephone: https://github.com/Biktorgj/quectel_eg25_recovery/archive/master.zip
To check if you're currently booted in EDL mode, run lsusb in a terminal and inspect the output.
You should see the following device listed: Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Once in EDL mode, open a terminal and go to the root directory of the recovery package, and run:

If you use an ARM64 distro (most likely) ./qfirehose_arm64 -f ./

If you use an ARMHF (32 bit) distro: ./qfirehose_armhf -f ./

After it finishes, it will reboot the modem and after about 30 seconds it will get back up and running

=== Bootloader unlocking ===
The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

The source code for the Bootloader is here: https://github.com/Biktorgj/quectel_lk
Prebuilt binary releases can be downloaded from here: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable. The source code release for the kernel provided by the manufacturer is incomplete and won't build, and common Android tools mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTB's attached. Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a _Work in progress_ SDK to allow creating custom kernels and system images, which can be downloaded from the following repo: https://github.com/Biktorgj/pinephone_modem_sdk

Once downloaded, you should run the 'init.sh' script, which will create all the base directories and download all the different repos required to build. After the initial setup is complete, run 'make' without arguments to list the available options

File:Pinephone-EG25-Recovery.jpg

2020-09-16T09:35:09Z

Biktorgj:

== Licensing ==
{{PD|PD}}

PineModems

2020-09-16T09:24:43Z

Biktorgj: Created page with "= Modems used in Pine64 boards and devices = == Quectel EG25-G Modem == * Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1...."

= Modems used in Pine64 boards and devices =

== Quectel EG25-G Modem ==

* Specifications: https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.pdf
* Hardware design: https://www.quectel.com/UploadImage/Downlad/Quectel_EG25-G_Hardware_Design_V1.2.pdf
* AT Interface reference manual: https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf

=== Specifications ===
* Processor Family: Qualcomm MDM9607
* CPU: Qualcomm MDM9207
* Cores: 1 ACPU Core, Qualcomm Hexagon DSP
* Total RAM: 256Mb
* Total flash space: 256Mb
* Available RAM for the ACPU: 160Mb

=== NAND Partition table layout ===

* MTD0: SBL (Secondary Bootloader), called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
* MTD1: mibib (Unknown, used by the DSP)
* MTD2: EFS2 (Unexplored, probably NVRAM data, Used by the DSP)
* MTD3: sys_rev: Unexplored
* MTD4: rawdata: Unexplored
* MTD5: tz: TrustZone kernel
* MTD6: rpm: Resource / Power Manager
* MTD7: cust_info: Unexplored
* MTD8: aboot: Application Bootloader. Uses LK (LittleKernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
* MTD9: boot: OpenEmbedded boot kernel + DTB
* MTD10: recovery: Recovery kernel (normally unused)
* MTD11: modem: ADSP firmware blobs
* MTD12: misc: Unexplored
* MTD13: recoveryfs: Recovery filesystem image (FOTA updates)
* MTD14: usr_data: User data partition (/data when mounted by OpenEmbedded)
* MTD15: sec (Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools)
* MTD16: system (Linux OpenEmbedded root image, formatted in Ubifs filesystem)

=== Firmware Recovery ===
The System partition is mounted as readonly mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.

The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might not show anywhere (USB device missing), it might malfunction (no radio but USB working), or it might enter EDL mode if the entire flash is corrupt

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins in the PinePhone Motherboard. Power off the phone, short the two test points and start it again while keeping the pads shorted at least until you hear the camera clicking twice (which is normally when the modem is powered)
[PHOTO]

Download the Firmware Recovery Package and copy it to the Pinephone: https://github.com/Biktorgj/quectel_eg25_recovery/archive/master.zip
To check if you're currently booted in EDL mode, run lsusb in a terminal and inspect the output.
You should see the following device listed: Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Once in EDL mode, open a terminal and go to the root directory of the recovery package, and run:

If you use an ARM64 distro (most likely) ./qfirehose_arm64 -f ./

If you use an ARMHF (32 bit) distro: ./qfirehose_armhf -f ./

After it finishes, it will reboot the modem and after about 30 seconds it will get back up and running

=== Bootloader unlocking ===
The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

The source code for the Bootloader is here: https://github.com/Biktorgj/quectel_lk
Prebuilt binary releases can be downloaded from here: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable. The source code release for the kernel provided by the manufacturer is incomplete and won't build, and common Android tools mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTB's attached. Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a _Work in progress_ SDK to allow creating custom kernels and system images, which can be downloaded from the following repo: https://github.com/Biktorgj/pinephone_modem_sdk

Once downloaded, you should run the 'init.sh' script, which will create all the base directories and download all the different repos required to build. After the initial setup is complete, run 'make' without arguments to list the available options