Pinephone won't boot.

[spha]

Pinephone screen stopped working. The system starts but the screen is black. When starting the jumpdrive, the screen is bright gray, but after an hour of charging, nothing has changed. The battery voltage is 3.76 volts. I have tried different operating systems and chargers. The last time it worked, I turned it off by holding the power button and put it on the table.

[fxc]

Pinephone screen stopped working. The system starts but the screen is black. When starting the jumpdrive, the screen is bright gray, but after an hour of charging, nothing has changed. The battery voltage is 3.76 volts. I have tried different operating systems and chargers. The last time it worked, I turned it off by holding the power button and put it on the table.

Which Jumpdrive image did you flash? Jumpdrive is not supposed to show a gray screen, instead it should show this screen: https://wiki.pine64.org/images/1/1a/Jumpdrive.jpg

The rest of the symptoms describe a drained battery, maybe beyond the point of saving. Mind that in this state, charging it for only one hour in Jumpdrive is not sufficient, at this state it will charge very slowly and it is required to charge it multiple hours until the drained battery takes some charge again.

[Kevin Kofler]

The rest of the symptoms describe a drained battery

Do they really? The user reports a battery voltage of 3.76V. According to the battery data sheet, the "nominal voltage" is 3.8V, the "end of discharge voltage" is 3.0±0.05V. Considering those numbers, 3.76V does not sound like a badly discharged battery to me.

[spha]

Pinephone screen stopped working. The system starts but the screen is black. When starting the jumpdrive, the screen is bright gray, but after an hour of charging, nothing has changed. The battery voltage is 3.76 volts. I have tried different operating systems and chargers. The last time it worked, I turned it off by holding the power button and put it on the table.

Which Jumpdrive image did you flash? Jumpdrive is not supposed to show a gray screen, instead it should show this screen: https://wiki.pine64.org/images/1/1a/Jumpdrive.jpg

The rest of the symptoms describe a drained battery, maybe beyond the point of saving. Mind that in this state, charging it for only one hour in Jumpdrive is not sufficient, at this state it will charge very slowly and it is required to charge it multiple hours until the drained battery takes some charge again.

I used both jumpdrive images. pine64-pinephone-charging.img.xz and pine64-pinephone.img.xz.

/home/spha/Загрузки/pine64-pinephone.img.xz

[fxc]

Pinephone screen stopped working. The system starts but the screen is black. When starting the jumpdrive, the screen is bright gray, but after an hour of charging, nothing has changed. The battery voltage is 3.76 volts. I have tried different operating systems and chargers. The last time it worked, I turned it off by holding the power button and put it on the table.

Which Jumpdrive image did you flash? Jumpdrive is not supposed to show a gray screen, instead it should show this screen: https://wiki.pine64.org/images/1/1a/Jumpdrive.jpg

The rest of the symptoms describe a drained battery, maybe beyond the point of saving. Mind that in this state, charging it for only one hour in Jumpdrive is not sufficient, at this state it will charge very slowly and it is required to charge it multiple hours until the drained battery takes some charge again.

I used both jumpdrive images. pine64-pinephone-charging.img.xz and pine64-pinephone.img.xz.

/home/spha/Загрузки/pine64-pinephone.img.xz

Please don't use the charging image, it disables the screen and it would match what you described (no screen output, possibly only backlight). I would suggest that you redownload https://github.com/dreemurrs-embedded/Ju...one.img.xz and check if you get a screen output with that.

---

The rest of the symptoms describe a drained battery

Do they really? The user reports a battery voltage of 3.76V. According to the battery data sheet, the "nominal voltage" is 3.8V, the "end of discharge voltage" is 3.0±0.05V. Considering those numbers, 3.76V does not sound like a badly discharged battery to me.

4.20 V when it is full. After an hour of charging it should be more than that, 3.76 V is in the bottom 0-10 %. I don't trust these measurements and am not considering them in my reply.

[spha]

Pinephone screen stopped working. The system starts but the screen is black. When starting the jumpdrive, the screen is bright gray, but after an hour of charging, nothing has changed. The battery voltage is 3.76 volts. I have tried different operating systems and chargers. The last time it worked, I turned it off by holding the power button and put it on the table.

Which Jumpdrive image did you flash? Jumpdrive is not supposed to show a gray screen, instead it should show this screen: https://wiki.pine64.org/images/1/1a/Jumpdrive.jpg

The rest of the symptoms describe a drained battery, maybe beyond the point of saving. Mind that in this state, charging it for only one hour in Jumpdrive is not sufficient, at this state it will charge very slowly and it is required to charge it multiple hours until the drained battery takes some charge again.

I used both jumpdrive images. pine64-pinephone-charging.img.xz and pine64-pinephone.img.xz.

/home/spha/Загрузки/pine64-pinephone.img.xz

Please don't use the charging image, it disables the screen and it would match what you described (no screen output, possibly only backlight). I would suggest that you redownload https://github.com/dreemurrs-embedded/Ju...one.img.xz and check if you get a screen output with that.

---

The rest of the symptoms describe a drained battery

Do they really? The user reports a battery voltage of 3.76V. According to the battery data sheet, the "nominal voltage" is 3.8V, the "end of discharge voltage" is 3.0±0.05V. Considering those numbers, 3.76V does not sound like a badly discharged battery to me.

4.20 V when it is full. After an hour of charging it should be more than that, 3.76 V is in the bottom 0-10 %. I don't trust these measurements and am not considering them in my reply.

I tried to use both images. When using pine64-pinephone.img.xz, the screen is bright gray, but the Jumpdrive itself was working. After some time of charging the battery, the battery voltage is 3.80 volts.

[fxc]

Pinephone screen stopped working. The system starts but the screen is black. When starting the jumpdrive, the screen is bright gray, but after an hour of charging, nothing has changed. The battery voltage is 3.76 volts. I have tried different operating systems and chargers. The last time it worked, I turned it off by holding the power button and put it on the table.

Which Jumpdrive image did you flash? Jumpdrive is not supposed to show a gray screen, instead it should show this screen: https://wiki.pine64.org/images/1/1a/Jumpdrive.jpg

The rest of the symptoms describe a drained battery, maybe beyond the point of saving. Mind that in this state, charging it for only one hour in Jumpdrive is not sufficient, at this state it will charge very slowly and it is required to charge it multiple hours until the drained battery takes some charge again.

I used both jumpdrive images. pine64-pinephone-charging.img.xz and pine64-pinephone.img.xz.

/home/spha/Загрузки/pine64-pinephone.img.xz

Please don't use the charging image, it disables the screen and it would match what you described (no screen output, possibly only backlight). I would suggest that you redownload https://github.com/dreemurrs-embedded/Ju...one.img.xz and check if you get a screen output with that.

---

The rest of the symptoms describe a drained battery

Do they really? The user reports a battery voltage of 3.76V. According to the battery data sheet, the "nominal voltage" is 3.8V, the "end of discharge voltage" is 3.0±0.05V. Considering those numbers, 3.76V does not sound like a badly discharged battery to me.

4.20 V when it is full. After an hour of charging it should be more than that, 3.76 V is in the bottom 0-10 %. I don't trust these measurements and am not considering them in my reply.

I tried to use both images. When using pine64-pinephone.img.xz, the screen is bright gray, but the Jumpdrive itself was working. After some time of charging the battery, the battery voltage is 3.80 volts.

If the USB functionality of Jumpdrive works it is not a drained battery. Sounds like the phone is functional but the display unit stopped working. 

It's a bit tricky to diagnose from this point of view because it would require further tools. I can give some general hints without saying which one the right or best way is:

• You can also open the phone and try to readjust the screen connector and see if that makes a difference (the one left to the microSD connector, see https://www.pine64.org/wp-content/upload...Phone1.png)
  
• With an USB UART adapter connected to the headphone jack (and the switch inside the PinePhone toggled to UART output) it would be possible to check if the OS is functional
  
• Screen can be replaced, however at this point it is unclear if there is an issue on the screen or the mainboard or other kind of issues
  
• Additionally, the battery behavior is currently also unclear, 3.8V is also not much change either
  

[spha]

Which Jumpdrive image did you flash? Jumpdrive is not supposed to show a gray screen, instead it should show this screen: https://wiki.pine64.org/images/1/1a/Jumpdrive.jpg

The rest of the symptoms describe a drained battery, maybe beyond the point of saving. Mind that in this state, charging it for only one hour in Jumpdrive is not sufficient, at this state it will charge very slowly and it is required to charge it multiple hours until the drained battery takes some charge again.

I used both jumpdrive images. pine64-pinephone-charging.img.xz and pine64-pinephone.img.xz.

/home/spha/Загрузки/pine64-pinephone.img.xz

Please don't use the charging image, it disables the screen and it would match what you described (no screen output, possibly only backlight). I would suggest that you redownload https://github.com/dreemurrs-embedded/Ju...one.img.xz and check if you get a screen output with that.

---

The rest of the symptoms describe a drained battery

Do they really? The user reports a battery voltage of 3.76V. According to the battery data sheet, the "nominal voltage" is 3.8V, the "end of discharge voltage" is 3.0±0.05V. Considering those numbers, 3.76V does not sound like a badly discharged battery to me.

4.20 V when it is full. After an hour of charging it should be more than that, 3.76 V is in the bottom 0-10 %. I don't trust these measurements and am not considering them in my reply.

I tried to use both images. When using pine64-pinephone.img.xz, the screen is bright gray, but the Jumpdrive itself was working. After some time of charging the battery, the battery voltage is 3.80 volts.

If the USB functionality of Jumpdrive works it is not a drained battery. Sounds like the phone is functional but the display unit stopped working. 

It's a bit tricky to diagnose from this point of view because it would require further tools. I can give some general hints without saying which one the right or best way is:

• You can also open the phone and try to readjust the screen connector and see if that makes a difference (the one left to the microSD connector, see https://www.pine64.org/wp-content/upload...Phone1.png)
  
• With an USB UART adapter connected to the headphone jack (and the switch inside the PinePhone toggled to UART output) it would be possible to check if the OS is functional
  
• Screen can be replaced, however at this point it is unclear if there is an issue on the screen or the mainboard or other kind of issues
  
• Additionally, the battery behavior is currently also unclear, 3.8V is also not much change either
  

I tried to reconnect the screen cable, it did not help. I'm sure the OS is working. The screen is not damaged, the cable is also in good condition. When I left the phone overnight without a battery and then booted up the OS, the screen was bright gray, and after a subsequent reboot, the screen was black again.

[spha]

Which Jumpdrive image did you flash? Jumpdrive is not supposed to show a gray screen, instead it should show this screen: https://wiki.pine64.org/images/1/1a/Jumpdrive.jpg

The rest of the symptoms describe a drained battery, maybe beyond the point of saving. Mind that in this state, charging it for only one hour in Jumpdrive is not sufficient, at this state it will charge very slowly and it is required to charge it multiple hours until the drained battery takes some charge again.

I used both jumpdrive images. pine64-pinephone-charging.img.xz and pine64-pinephone.img.xz.

/home/spha/Загрузки/pine64-pinephone.img.xz

Please don't use the charging image, it disables the screen and it would match what you described (no screen output, possibly only backlight). I would suggest that you redownload https://github.com/dreemurrs-embedded/Ju...one.img.xz and check if you get a screen output with that.

---

The rest of the symptoms describe a drained battery

Do they really? The user reports a battery voltage of 3.76V. According to the battery data sheet, the "nominal voltage" is 3.8V, the "end of discharge voltage" is 3.0±0.05V. Considering those numbers, 3.76V does not sound like a badly discharged battery to me.

4.20 V when it is full. After an hour of charging it should be more than that, 3.76 V is in the bottom 0-10 %. I don't trust these measurements and am not considering them in my reply.

I tried to use both images. When using pine64-pinephone.img.xz, the screen is bright gray, but the Jumpdrive itself was working. After some time of charging the battery, the battery voltage is 3.80 volts.

If the USB functionality of Jumpdrive works it is not a drained battery. Sounds like the phone is functional but the display unit stopped working. 

It's a bit tricky to diagnose from this point of view because it would require further tools. I can give some general hints without saying which one the right or best way is:

• You can also open the phone and try to readjust the screen connector and see if that makes a difference (the one left to the microSD connector, see https://www.pine64.org/wp-content/upload...Phone1.png)
  
• With an USB UART adapter connected to the headphone jack (and the switch inside the PinePhone toggled to UART output) it would be possible to check if the OS is functional
  
• Screen can be replaced, however at this point it is unclear if there is an issue on the screen or the mainboard or other kind of issues
  
• Additionally, the battery behavior is currently also unclear, 3.8V is also not much change either
  

Connecting the phone via UART, I saw the following:
1. Warning: HDMI PHY init timeout!
2. * WARNING: clock skew detected!
3. * Starting kill-pbsplash ...killall: pbsplash: no process killed
* start-stop-daemon: failed to start `/usr/bin/killall'
* Failed to start kill-pbsplash
[ !! ]
* ERROR: kill-pbsplash failed to start
4. Sxmo is not running
5. ERROR: /dev/fb0 did not appear!
1tfb_acquire_fb() failed with error code: 1


xinit: Fatal server error:
(EE) no screens found(EE)

Code:

pine64-pinephone:~$ ls /dev autofs loop4       ptyp8 tty17 tty43  ttyp0     vcs7 binder loop5       ptyp9 tty18 tty44  ttyp1     vcsa block loop6       ptypa tty19 tty45  ttyp2     vcsa1 bus loop7       ptypb tty2 tty46  ttyp3     vcsa2 char mapper        ptypc tty20 tty47  ttyp4     vcsa3 console media0        ptypd tty21 tty48  ttyp5     vcsa4 cpu_dma_latency  media1        ptype tty22 tty49  ttyp6     vcsa5 disk mem       ptypf tty23 tty5  ttyp7     vcsa6 dri mmcblk0      random tty24 tty50  ttyp8     vcsa7 fd mmcblk0p1    rfkill tty25 tty51  ttyp9     vcsu full mmcblk0p2    root tty26 tty52  ttypa     vcsu1 fuse mmcblk2      rtc tty27 tty53  ttypb     vcsu2 gpiochip0 mmcblk2boot0  rtc0 tty28 tty54  ttypc     vcsu3 gpiochip1 mmcblk2boot1  shm tty29 tty55  ttypd     vcsu4 hwbinder mmcblk2p1    snapshot  tty3 tty56  ttype     vcsu5 i2c-0 mmcblk2p2    snd tty30 tty57  ttypf     vcsu6 i2c-1 mqueue        stderr tty31 tty58  uhid     vcsu7 i2c-2 net       stdin tty32 tty59  urandom     vfio i2c-3 null       stdout tty33 tty6  v4l     video0 i2c-4 ptmx       tty tty34 tty60  v4l-subdev0  video1 iio:device3 pts       tty0 tty35 tty61  v4l-subdev1  video2 input ptyp0       tty1 tty36 tty62  v4l-subdev2  video3 kmsg ptyp1       tty10 tty37 tty63  vcs     vndbinder log ptyp2       tty11 tty38 tty7  vcs1     zero loop-control ptyp3       tty12 tty39 tty8  vcs2     zram0 loop0 ptyp4       tty13 tty4 tty9  vcs3 loop1 ptyp5       tty14 tty40 ttyS0  vcs4 loop2 ptyp6       tty15 tty41 ttyS2  vcs5 loop3 ptyp7       tty16 tty42 ttyS3  vcs6

Code:

pine64-pinephone:~$ ls /dev/*/ /dev/block/: 179:0  179:2  179:33  179:64  253:0  7:1  7:3 7:5  7:7 179:1  179:32  179:34  179:96  7:0    7:2  7:4 7:6 /dev/bus/: usb /dev/char/: 10:124 13:64 226:128  2:4 3:5  4:2  4:35  4:50 4:67  7:2  81:3 10:125 13:65 250:3   2:5 3:6  4:20  4:36  4:51 4:7    7:3  81:4 10:126 13:66 251:0   2:6 3:7  4:21  4:37  4:52 4:8    7:4  81:5 10:127 13:67 251:1   2:7 3:8  4:22  4:38  4:53 4:9    7:5  81:6 10:196 13:68 252:0   2:8 3:9  4:23  4:39  4:54 5:0    7:6  89:0 10:200 189:0 254:0   2:9 4:0  4:24  4:4  4:55 5:1    7:64  89:1 10:229 189:128  254:1   3:0 4:1  4:25  4:40  4:56 5:2    7:65  89:2 10:231 189:256  2:0   3:1 4:10  4:26  4:41  4:57 7:0    7:66  89:3 10:235 189:384  2:1   3:10 4:11  4:27  4:42  4:58 7:1    7:67  89:4 10:236 1:1 2:10   3:11 4:12  4:28  4:43  4:59 7:128  7:68 10:237 1:11 2:11   3:12 4:13  4:29  4:44  4:6 7:129  7:69 10:239 1:3 2:12   3:13 4:14  4:3  4:45  4:60 7:130  7:7 10:242 1:5 2:13   3:14 4:15  4:30  4:46  4:61 7:131  7:70 116:0 1:7 2:14   3:15 4:16  4:31  4:47  4:62 7:132  7:71 116:16 1:8 2:15   3:2 4:17  4:32  4:48  4:63 7:133  81:0 116:24 1:9 2:2   3:3 4:18  4:33  4:49  4:64 7:134  81:1 116:33 226:0 2:3   3:4 4:19  4:34  4:5  4:66 7:135  81:2 /dev/disk/: by-id  by-label  by-partuuid  by-path  by-uuid /dev/dri/: by-path  card0 renderD128 /dev/fd/: 0  1  2  3 /dev/input/: by-path  event0  event1  event2  event3  event4 /dev/mapper/: control /dev/mqueue/: /dev/net/: tun /dev/pts/: ptmx /dev/shm/: user /dev/snd/: by-path  controlC0  pcmC0D0c  pcmC0D0p timer /dev/v4l/: by-path /dev/vfio/: vfio

Warning: HDMI PHY init timeout!

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 6.3.5 (pmos@build) (aarch64-alpine-linux-musl-gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, GNU ld (GNU Binutils) 2.40) #1-postmarketos-allwinner SMP PREEMPT Tue Jun 20 07:12:4
9 UTC 20
[ 0.000000] Machine model: Pine64 PinePhone (1.2)
[ 0.000000] earlycon: uart0 at MMIO32 0x0000000001c28000 (options '')
[ 0.000000] printk: bootconsole [uart0] enabled
### postmarketOS initramfs ###
Configuring kernel firmware image search path
NOTE: Waiting 10 seconds for the framebuffer /dev/fb0.
If your device does not have a framebuffer, disable this with:
no_framebuffer=true in <https://postmarketos.org/deviceinfo>



Mobian:

Starting kernel ...

[ 5.484740] lima 1c40000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
[ 6.349158] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 6.375975] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 6.385433] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 6.395664] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 6.405325] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 6.503650] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 6.519130] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 6.530144] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 7.532097] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 7.622779] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 7.653545] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 7.685248] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
[ 7.749068] pinephone-keyboard 2-0015: Failed to read device ID: -6
[ 9.795201] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 9.801813] Goodix-TS 0-005d: Error reading 1 bytes from 0x8140: -110
[ 11.843196] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 11.849781] anx7688 0-0028: tcpc i2c read failed at 0x0 (-110)
[ 13.891198] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 13.897787] Goodix-TS 0-005d: Error reading 1 bytes from 0x8140: -110
[ 13.931198] Goodix-TS 0-005d: I2C communication failure: -110
[ 15.935191] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 15.941785] anx7688 0-0028: tcpc i2c read failed at 0x1 (-110)
[ 15.968606] panel-sitronix-st7703 1ca0000.dsi.0: mipi_dsi_attach failed (-517). Is host ready?
ERROR: SDL_Init failed: kmsdrm not available
ERROR: SDL_Init failed: kmsdrm not available
ERROR: SDL_Init failed: kmsdrm not available
ERROR: SDL_Init failed: kmsdrm not available
ERROR: SDL_Init failed: kmsdrm not available

[mikehenson]

I used both jumpdrive images. pine64-pinephone-charging.img.xz and pine64-pinephone.img.xz.

/home/spha/Загрузки/pine64-pinephone.img.xz

I made a video of loading jumpdrive, then I load an OS.
The steps for loading/installing any other an OS should be the same.

https://www.youtube.com/watch?v=XNF8zuIEGik

Devices:
PinePhone 16Gig
PinePhone Pro
Both running DanctNIX Arch with Phosh