PINE64 - PinePhone Hardware

PinePhone 16 GB – Free to a Good Home

Mon, 12 Jan 2026 14:37:16 +0000

PinePhone 16 GB – Free to a Good Home

I’m giving away a PinePhone (16 GB) that I no longer need.

If you can pick it up in Bonn, Germany, or send me 20 euros via PayPal (assuming that’s enough to cover shipping to your location), it’s yours.

Included:

a cracked but still sort of functional screen
an extra replacement screen for repairing the phone
no battery
a cracked back cover (still usable, though a piece between the buttons is missing) with a Debian logo
a yellowed & unsightly, transparent rubber protective case
no warranty of any kind

I don't know how to post picture here, but I guess you know what a Pinephone looks like.

Best,
A

PinePhone, PinePhone Pro, Keyboard/Accessories for sale

Thu, 20 Nov 2025 22:15:25 +0000

I have a PinePhone, PinePhone Pro, Keyboard, wireless charging back cover, cases, and spare batteries for sale. PM me.

Recycling pinephone as home server

Tue, 11 Nov 2025 16:12:14 +0000

Hi!

I have an old pinephone that I stopped using (due to broken battery pins).

I'm trying to recycle it as a home server, without a battery (I don't want it to catch fire) but:

- Either I plug it using an USB-C charger, it boots, but does not gets Wi-Fi (known behavior), so I'm stuck.
- Either I use the Pinephone convergence dock to use RJ45, but it looks like it lacks power or something as the phone bootloops.

I though about using a voltage regulator to fake the battery BUT I fear the moment the phone tries to "charge" it, lol.

Can someone try to boot its pinephone without a battery and with a convergence dock to see if there's any chance this way?

Or is there another way I missed?

My Phone stopped making and recieving Calls

Sun, 14 Sep 2025 21:30:39 +0000

My pine phone stopped making and receiving phone call.

I have full Internet and connection sharing, SMS works fine, both sending and receiving, but I am unable to make or receive phone calls.

I am in Australia, connecting through Telstra.

When attempting to make a call, it immediately goes to call ended, and when anyone calls me I get no indication that a call is coming through, at their end it goes to voice mail, and I receive an sms telling me I missed a call..

For an lshw list of my hardware .. please see attachment

The issue is not related to the recent upgrade, as it occurred prior to upgrading. I was hoping the upgrade would fix the issue..

lshw.txt (Size: 7.36 KB / Downloads: 4178)

PinePhone USB-C port and audio jack failure

Sun, 06 Jul 2025 23:08:53 +0000

I am at my second PinePhone, the first one having had a hardware failure that made the modem, among other things, inoperable (and the outer parts: screen, case, buttons having been damaged enough to make a mainboard replacement not worthwhile).

So I bought this PinePhone in March 2023 from the EU Store. Sadly, this means that the compulsory EU warranty (2 years) has expired 3-4 months ago. So far, I was happy with it (and the outside is in good condition), but…

I have noticed 2 failures this week – I cannot prove that they happened simultaneously, but the coincidence seems odd:

The USB-C port works for charging only. The data lines appear to be completely dead. I first noticed this (a few hours ago) trying to boot into JumpDrive, to connect the PinePhone to my computer (because I wanted to back up and then replace the installed OS through USB, trying to switch from Manjaro ARM stable, last updated over a year ago, to postmarketOS 25.06). There was no way I could get the computer to detect the PinePhone. I tried 2 different cables, 3 different USB-A ports on the computer, rebooting the PinePhone several times and the computer twice, nothing helped. Then I took out the JumpDrive microSD card, booted back into the installed OS, and tried using the "convergence package" dock stick to plug in my (USB-A) notebook mouse. Nothing, no way I could get the PinePhone to see the mouse at all, either. Charging works even through the dock (using its USB-C power input), but nothing else works. One would think that this is clearly a failure of the USB-C daughter board, but…
The audio jack on the other end of the phone also stopped working. I first noticed that this Thursday. When I try to connect the PinePhone to a hardware audio mixer, or to my small home stereo, it fails to detect that there is anything plugged in and does not produce any audio output. Tried 2 different cables, 2 different ports on the audio mixer, and even another output device (my stereo), nothing worked. This time, at least, there is some output in the journal, but it sounds like a typical "bad contact" on-and-off scenario: Within 1 second, I get around 20 times:

Code:
Jul 07 00:11:26 plasma-mobile kernel: jack: irq plug-in Jul 07 00:11:26 plasma-mobile kernel: jack: irq plug-out
So, while the PinePhone did detect that something was plugged in, it comes and goes (and comes back and goes again), around 20 times per second.

There is also other bizarre behavior I have noticed lately (since around 2-3 weeks), involving the WiFi/Bluetooth chip:

The WiFi has become much worse at keeping connections alive. Running ping commands (doing a ping every second) either from the PinePhone to somewhere else or from the computer to the PinePhone makes it better, but the WiFi used to work much better even without that workaround.
Bluetooth stopped pairing successfully with one particular audio device (the same hardware audio mixer that I first tried using the audio jack with), but the PinePhone pairs successfully with other Bluetooth devices (at least a small Bluetooth receiver and my computer), and other smartphones pair successfully with the audio device that the PinePhone has trouble with. In the particular pairing that stopped working, I always get the same "br-connection-unknown" error. It used to work fine for months, then suddenly started failing around 2 weeks ago.

This somehow reminds me of the old PinePhone's failure, though this time the internal USB modem stays on USB just fine, it is just the external port (and some apparently unrelated hardware, for some reason) that is not working.

The only thing I can tell for sure is that it is not a battery issue, because I have tried with the spare battery I had around and that did not solve the issue. Would have surprised me anyway, but replacing the one easily replaceable part (and with a spare ready to be tried) was worth a try. (And no, the spare I tried is not the battery from the old 2021 PinePhone, but a barely used Samsung EB-BJ700CBE I had lying around in the fridge in a waterproof freezer bag.)

Does anyone know which testpoint is for Fel boot?

Wed, 26 Mar 2025 10:22:38 +0000

Hi all,

I'd like to be able to boot my Pinephone using FEL boot without using the SD card. I've had success doing this for a Banana Pi, and a Pine64, so I would like to maybe make this an option for the pinephone as well.

Has anyone figured out which testpoint is the FEL boot pin on the 1.2 board? Did we ever get a proper layout for the 1.2 board?

Thanks!

Pinephone not booting sd card...

Tue, 25 Mar 2025 02:18:35 +0000

I am on pinephone and am trying to install pmOS to the emmc but when I try to boot to jumpdrive (on a sd card) the led flashes green and doesn't go to jumpdrive.

Battery connector dead

Sat, 01 Mar 2025 17:07:53 +0000

Just to see if it happened to someone else: I just broke one of the 4 small golden battery connectors ☹

My battery was a Samsung one, it was a tad too big so it was a bit hard to set and remove, maybe it helped weaken the connectors...

I'm not sure there's an easy fix, that's why I'm asking if it happend to someone else.

If it's dead I'll recycle it as a small home server maybe to try Home Assistant or something

Third-party cheap touchscreen/LCD for the Pinephone - lost knowledge?

Wed, 05 Feb 2025 19:39:42 +0000

Somewhere (not on this forum) there was a pretty detailed article that described how to replace a touch panel of the Pinephone - or perhaps the whole LCD assembly - with a third-party one from AliExpress instead of from Pine64. AliExpress alternative was much cheaper, had more shipping options and didn't have any availability problems (i.e. at the moment a Pine64's Pinephone LCD replacement - is "out of stock" for a pretty long time).

I had this article saved somewhere in my bookmarks, but now I can't find it anywhere - and extensive googling does not help yet. Two things that I remember:

it turned out that Pine64 changed the pinout of touch to make it more "proprietary" (maybe so that everyone is forced to buy this replacement part from Pine64), two pins were switched - but I don't remember which ones
this article was a couple of years old

If you have stumbled upon this article and have it saved somewhere, maybe in web archive (I don't know if this website is still alive), please let me know.
Alternatively, this knowledge may be re-obtained because we know it is possible and where to "dig" (i.e. check how the alternative panel's pins are routed)

EDIT: some keywords may involve "Goodix" "GT917S" "I2C" (Goodix GT917S touch panel's controller talks with a Pinephone over the internal I2C),
of course the replacement touch panel should be based on the same controller in order for it to work without any software/firmware modifications;
a similar-enough Goodix from the same "GT9xx" family - like GT911 or GT915 - may also work as a substitute

EDIT 2: there also may be some way to fix an existing touch panel, like using a gas lighter's quartz igniter - it works for some people, but may be dangerous:

Quote:Buy a two dollar lighter that uses a piece of quartz as an ignition source... Electrical discharge... Not the type with a piece of flint inside. The main difference and clue you have the right one is, the flint one has the rollers on top you run your thumb across as you press down on the button/trigger to release its gas for ignition. The lighter you want has just one button/ trigger. First vent or empty butane gas... Release valve on bottom. Then remove the quartz igniter from the lighters housing and place on you phones dead screen click/ press it a couple of times..for me three times. Dead zone/dead bar fixed.. no more ghost touches either. Fixed... 2.00 dollars... but keep igniter around in case screen goes dead again but after a couple of clicks screen permanent fix for me. For a detailed youtube video of the process, search keywords screen fix quartz iginiter.... the error is a digitizer fault, often due to your phone overheating for long periods at a time. The quartz igniter generates around 350 to 400 volts to the lcd screen and attached digitizer ..harmless to your phone and you... this electrical discharge that awakens the dead zone like magic. No costly repairs of digitizer and LCD screen

FOSS fw problem - PinePhonePro, EG25 modem

Fri, 31 Jan 2025 13:24:48 +0000

OK, so I have had an older PinePhonePro (mini SIM rather than micro SIM) for a while. I had flashed Biktorg's fw to it and used to be able to chat to the modem fine. A while back I had a problem 1 night setting a wakeup call (can't remember, power fail, think trying to flash 0.8.0) and since then I cant SMS the modem. I have tried everything I can think of, flashing back to stock, trying fwupd to flash, pmOS, arch, mobian, 30.006, 01.003 ADSP firmware, ...

So as I write this I have my PPP which has a "Frankenstein" firmware (it seems half FOSS but with stock artefacts) and my old PP in front of me which is FOSS and behaves like I expect.

The basic problem that is the subject of this thread - I can't send SMS to the modem:

Code:
$ cat sms.txt | sxmo_modemsendsms.sh +223344556677 -

12:41:25 sxmo_modemsendsms.sh: Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Connected: No AT port available to run command')

Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Connected: No AT port available to run command')

The system log during boot - note the serial number is "community_fw":

Code:
[   34.237819] usb 1-1: new high-speed USB device number 3 using ehci-platform

[   34.368702] usb 1-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18

[   34.368737] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[   34.368747] usb 1-1: Product: LTE Module

[   34.368755] usb 1-1: Manufacturer: Quectel, Incorporated

[   34.368764] usb 1-1: SerialNumber: community_fw

[   34.441830] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0

[   34.442645] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1

[   34.443151] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2

[   34.443494] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3

For cross reference on my PP the system log has the same info:

Code:
[   52.475036] usb 2-1: new high-speed USB device number 3 using ehci-platform

[   52.636611] usb 2-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18

[   52.640986] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[   52.641138] usb 2-1: Product: LTE Module

[   52.641198] usb 2-1: Manufacturer: Quectel, Incorporated

[   52.641232] usb 2-1: SerialNumber: community_fw

[   52.717965] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0

[   52.723460] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1

[   52.737674] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2

[   52.742115] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3

The reason for my "Frankenstein" use is that the differences start showing in the journal - my PPP has

Code:
[Jan 31 12:27:05] daemon eg25-manager: ** Message: 12:27:05.087: Successfully sent command: AT+QGMR

...

[Jan 31 12:27:05] daemon eg25-manager: ** Message: 12:27:05.113: Response: [EG25GGBR07A08M2G_01.003.00.000\r\n\r\nOK]

Whereas the PP has

Code:
[Jan 01 01:01:30] daemon eg25-manager: ** Message: 01:01:30.626: Successfully sent command: AT+QGMR

...

[Jan 01 01:01:30] daemon eg25-manager: ** Message: 01:01:30.645: Response: [0.7.4\r\n\r\nOK]

So it appears my most recent attempt to flash the modem failed, but the log is (flashing 0.7.4 FWIW):

Code:
# ./flashall 

Sending AT+QFASTBOOT...

OKAY [  0.002s]

Finished. Total time: 0.002s

Warning: skip copying aboot image avb footer (aboot partition size: 0, aboot image size: 286476).

Sending 'aboot' (279 KB)                           OKAY [  0.013s]

Writing 'aboot'                                    OKAY [  0.131s]

Finished. Total time: 0.166s

Rebooting                                          OKAY [  0.004s]

Finished. Total time: 0.055s

< waiting for any device >

OKAY [  0.002s]

Finished. Total time: 0.002s

Sending 'boot' (4600 KB)                           OKAY [  0.149s]

Writing 'boot'                                     OKAY [  1.793s]

Finished. Total time: 1.955s

Sending 'recovery' (4600 KB)                       OKAY [  0.148s]

Writing 'recovery'                                 OKAY [  1.795s]

Finished. Total time: 1.963s

Warning: skip copying system image avb footer (system partition size: 0, system image size: 28311552).

Sending 'system' (27648 KB)                        OKAY [  0.879s]

Writing 'system'                                   OKAY [ 11.942s]

Finished. Total time: 12.844s

Warning: skip copying recoveryfs image avb footer (recoveryfs partition size: 0, recoveryfs image size: 13369344).

Sending 'recoveryfs' (13056 KB)                    OKAY [  0.417s]

Writing 'recoveryfs'                               OKAY [  4.949s]

Finished. Total time: 5.391s

Rebooting                                          OKAY [  0.004s]

Finished. Total time: 0.055s

Done!

Any thoughts welcome - my only hope is to keep trying to flash 0.7.4 and hope it works!

Impossible to login, bottom right corner of the touchscreen not responding

Tue, 14 Jan 2025 14:56:33 +0000

Hello

The bottom right corner of the touchscreen doesn't respond, I cannot enter the password. I highly suspect an hardware defect, I had the same trouble on my very first Pinephone.

Could it be caused by a software problem?

Is there a workaround in the meantime so that I can login? For example, can I force the Pinephone to enable the screen rotation very early? Can I use the dock?

Does someone have some experience on replacing the touchscreen? I will probably do that and if it works on my current Pinephone, I will do the same on my previous Pinephone.

P.S: I can login by using the dock but half of the user interface doesn't appear on the screen and the keyboard starts working correctly only after entering the password. Note that I use full disk encryption.

Modem Issues with the Pinephone

Wed, 16 Oct 2024 03:19:59 +0000

Now part of this was probably my fault, but I'm having some odd issues with the modem.

I got my Pinephone used from a friend, and when I tried to use my SIM card, it could recognize the SIM card was inserted and the towers it could connect to, but it would never be able to connect. So I thought "Okay it's a driver issue" so I went and used the script available at https://github.com/the-modem-distro/pinephone_modem_sdk but I was tired and didn't think to check the current firmware on the modem and that also didn't work. So then I thought to try to load all the old firmwares until it was fully updated, but now the modem still exists and TRIES to function (it'll show me the settings, the lack of bars, and that there's no SIM inserted or that there is inserted) but I can't see it with

Code:
lsusb

Code:
adb

and I'm wondering if it's irrecoverable or not?

I did try connecting the two plates on the back of the board to each other, but perhaps that didn't short them out. When I did that, the modem just disappeared and still didn't exist with any command.

Kill switches for Wifi/Bluetooth does not work

Mon, 14 Oct 2024 21:34:13 +0000

Hi everyone,

When I flip the second kill switch on the pinephone I cannot get the WiFi or the bluetooth to turn off. Is this normal behaviour? Am I missing something?

Thanks a lot

Jumpdrive boots Computer(s) don't recognize PinPhone

Fri, 11 Oct 2024 11:47:42 +0000

As descriebed in the headline.

I own a pinephone. Mobian is installed in some outdeated version. I want to flash a new version of mobian but none of my computers recognizes the phone when booted with jumpdrive. tow boot seems to be installed. Booting while pressing the volume up button also does not show the devoce as mass storage. Any idea is appreciated.

(10-11-2024, 05:47 AM)sfb Wrote: As descriebed in the headline.

I own a pinephone. Mobian is installed in some outdeated version. I want to flash a new version of mobian but none of my computers recognizes the phone when booted with jumpdrive. tow boot seems to be installed. Booting while pressing the volume up button also does not show the devoce as mass storage. Any idea is appreciated.

edit: I put the image on SD and installed from there. But still I wonder why the pp isn't recognized as mass storage?

Pinephone + Keyboard for sale, little use

Thu, 10 Oct 2024 15:50:01 +0000

Bought a pinephone and the keyboard a few years ago, havent really used it in the past year and would like to get some money for it. UK Based and am probably going to list on ebay for auction soon but thought id post here first if anyone is looking for one. Thanks!