Pinephone boot.
#1
So a good while back, I ordered a pinephone. Mostly to support the project but also because I wanted to use a Linux phone. Unfortunately, before I got to use it, AT&T did their whitelist thing then Verizon bought Tracfone et al which caused not a small amount of grief so the Pinephone sat in a drawer for a while.

Anyway, yesterday, I activated a t-mobile sim and put it in the (unupdated) pinephone. Things seemed to be going well. Sent some texts, did some test calls, things were good. So I left it charging. This morning, I came to use it and it appeared to be off. No biggie. Try to boot - red led, red&green led then just the backlight. Wonder if I didn't have things plugged in correctly so make sure charging is all good and leave it for 10 minutes. Same thing happens.

So now we're in troubleshooting mode. vol-up+power, same deal. vol-up+power, same deal. No apparent recovery mode. Time for research. Find the post at the top of this thread. Could be battery? Don't think so (see above) but pull battery and it's giving a good 4.13V so we appear to definitely be in good shape. Next to try jumpdrive. Download the image, flash to SD, insert and... LED is green (yay, something different) but then we're back to the backlight only. Nothing appeared on the screen at all. A couple of attempts to get to recovery mode again that lead to the same result and then a reboot and the phone's been sitting there for 10 minutes with the backlight on. The metal plate inside the phone is warm (but not hot).

So is there anywhere to go from here?
  Reply
#2
Do you have the serial cable? There may be console messages that would help figure out what's going on.

By the way, I've been using my Pinephone successfully on AT&T for a couple of years now. I simply changed the IMEI to that of the free flip phone they sent me when 3g service was shut down. (Since AT&T provided the phone it's on their whitelist. The flip phone is left unused in a drawer with the battery removed so I know I'm not using someone else's IMEI.)
  Reply
#3
(05-05-2024, 11:11 AM)Richy_T Wrote: So a good while back, I ordered a pinephone. Mostly to support the project but also because I wanted to use a Linux phone. Unfortunately, before I got to use it, AT&T did their whitelist thing then Verizon bought Tracfone et al which caused not a small amount of grief so the Pinephone sat in a drawer for a while.

Anyway, yesterday, I activated a t-mobile sim and put it in the (unupdated) pinephone. Things seemed to be going well. Sent some texts, did some test calls, things were good. So I left it charging. This morning, I came to use it and it appeared to be off. No biggie. Try to boot - red led, red&green led then just the backlight. Wonder if I didn't have things plugged in correctly so make sure charging is all good and leave it for 10 minutes. Same thing happens.

So now we're in troubleshooting mode. vol-up+power, same deal. vol-up+power, same deal. No apparent recovery mode. Time for research. Find the post at the top of this thread. Could be battery? Don't think so (see above) but pull battery and it's giving a good 4.13V so we appear to definitely be in good shape. Next to try jumpdrive. Download the image, flash to SD, insert and... LED is green (yay, something different) but then we're back to the backlight only. Nothing appeared on the screen at all. A couple of attempts to get to recovery mode again that lead to the same result and then a reboot and the phone's been sitting there for 10 minutes with the backlight on. The metal plate inside the phone is warm (but not hot).

So is there anywhere to go from here?

is it bad behaving suspend (sleep)?!

i noticed, that phosh does not immediately show suspend option. maybe something needs to be started in a background when suspend option is shown in power submenu.

you didn't tell your o.s.! mobian (and debian) trixie has t64 tansition going on in trixie, which causes headaches.

did you have automatic updates? which is bad idea for beta software.

tow-boot does not have recovery mode, at least not same as in android world. rough options are, normal boot, sdcard boot, and builtin usb jumpdrive mode.
  Reply
#4
(05-05-2024, 10:39 PM)Zebulon Walton Wrote: Do you have the serial cable? There may be console messages that would help figure out what's going on.

By the way, I've been using my Pinephone successfully on AT&T for a couple of years now. I simply changed the IMEI to that of the free flip phone they sent me when 3g service was shut down. (Since AT&T provided the phone it's on their whitelist. The flip phone is left unused in a drawer with the battery removed so I know I'm not using someone else's IMEI.)

Interesting. I did not know you could change the IMEI as I may have tried to go that way. I can't remember the exact order of events but I think I got the pinephone just before Tracphone/Verizon pushed everyone over.

I don't have the serial cable but I do have the parts to make one. I'll look into making one this week.
  Reply
#5
(05-05-2024, 11:52 PM)zetabeta Wrote: is it bad behaving suspend (sleep)?!

i noticed, that phosh does not immediately show suspend option. maybe something needs to be started in a background when suspend option is shown in power submenu.

you didn't tell your o.s.! mobian (and debian) trixie has t64 tansition going on in trixie, which causes headaches.

did you have automatic updates? which is bad idea for beta software.

tow-boot does not have recovery mode, at least not same as in android world. rough options are, normal boot, sdcard boot, and builtin usb jumpdrive mode.

I can't even get close to suspend/sleep. As far as I can tell, it was working fine the night before but now I can't even get anywhere through the boot process.
  Reply
#6
(05-05-2024, 11:52 PM)zetabeta Wrote: is it bad behaving suspend (sleep)?!

i noticed, that phosh does not immediately show suspend option. maybe something needs to be started in a background when suspend option is shown in power submenu.

you didn't tell your o.s.! mobian (and debian) trixie has t64 tansition going on in trixie, which causes headaches.

did you have automatic updates? which is bad idea for beta software.

tow-boot does not have recovery mode, at least not same as in android world. rough options are, normal boot, sdcard boot, and builtin usb jumpdrive mode.


It looks to me like the phone is alive. This is what I get booting normally:

Code:
U-Boot SPL 2020.07-rc4-11.2 (Jan 31 2021 - 14:19:48 +0000)
DRAM: 3072 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.3(debug):
NOTICE:  BL31: Built : 14:19:48, Jan 31 2021
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x4064908, model: Pine64 PinePhone (1.2)
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP803 on RSB
INFO:    PMIC: dcdc1 voltage: 3.300V
INFO:    PMIC: dcdc5 voltage: 1.200V
INFO:    PMIC: dcdc6 voltage: 1.100V
INFO:    PMIC: dldo1 voltage: 3.300V
INFO:    PMIC: dldo2 voltage: 1.800V
INFO:    PMIC: dldo3 voltage: 2.800V
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
NOTICE:  PSCI: System suspend is available via SCPI
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.07-rc4-11.2 (Jan 31 2021 - 14:19:48 +0000) Manjaro Linux ARM

CPU:   Allwinner A64 (SUN50I)
Model: Pine64 PinePhone (1.2)
DRAM:  3 GiB
MMC:   Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000'
mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
starting USB...
No working controllers found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
975 bytes read in 1 ms (952.1 KiB/s)
## Executing script at 4fc00000
gpio: pin 98 (gpio 98) value is 1
gpio: pin 114 (gpio 114) value is 1
19042312 bytes read in 816 ms (22.3 MiB/s)
gpio: pin 98 (gpio 98) value is 0
51342 bytes read in 5 ms (9.8 MiB/s)
7172119 bytes read in 308 ms (22.2 MiB/s)
gpio: pin 115 (gpio 115) value is 1
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 49928000, end 49fff017 ... OK
   Loading Device Tree to 0000000049918000, end 000000004992788d ... OK

Starting kernel ...

[    0.654863] SMCCC: SOC_ID: ARCH_SOC_ID(0) returned error: ffffffffffffffff
[    3.328194] i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
[    3.334783] Goodix-TS 1-005d: i2c test failed attempt 1: -110
[    5.408192] i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
[    5.414744] Goodix-TS 1-005d: i2c test failed attempt 2: -110
[    5.448189] Goodix-TS 1-005d: I2C communication failure: -110
Starting version 247.3-1-arch
ROOT_MNJRO: recovering journal
ROOT_MNJRO: clean, 173247/1880480 files, 1344654/7515099 blocks
[    9.003700] iio iio:device1: failed to read Who-Am-I register.
[   11.067969] i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   11.074678] anx7688 1-0028: tcpc i2c read failed at 0x0 (-110)
[   13.120226] i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   13.126902] anx7688 1-0028: tcpc i2c read failed at 0x1 (-110)

Manjaro Linux 5.11.3-1-MANJARO-ARM (ttyS0)

plasma-mobile login:

And with the SD inserted

Code:
DRAM: 3072 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.2(release):v2.2-904-gf9ea3a629
NOTICE:  BL31: Built : 15:32:12, Apr  9 2020
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x4064410, model: PinePhone
NOTICE:  PSCI: System suspend is unavailable


U-Boot 2020.07 (Nov 08 2020 - 00:15:12 +0100)

DRAM:  3 GiB
MMC:   Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000'
mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

starting USB...
No working controllers found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
653 bytes read in 2 ms (318.4 KiB/s)
## Executing script at 4fc00000
gpio: pin 114 (gpio 114) value is 1
4275261 bytes read in 188 ms (21.7 MiB/s)
Uncompressed size: 10170376 = 0x9B3008
36162 bytes read in 3 ms (11.5 MiB/s)
1078500 bytes read in 49 ms (21 MiB/s)
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 49ef8000, end 49fff4e4 ... OK
   Loading Device Tree to 0000000049eec000, end 0000000049ef7d41 ... OK

Starting kernel ...


/ #

But nothing on the screen but the backlight. Clearly there's something up but I'm not a hardware guy,
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Tow boot MTXP 1 220 06-01-2024, 05:08 AM
Last Post: shulamy
  Pinephone won't boot. spha 13 3,579 05-15-2024, 10:31 PM
Last Post: Richy_T
  eSIM on PinePhone just_a_q 4 2,975 05-14-2024, 01:35 PM
Last Post: Kevin Kofler
  PinePhone - boot from microSD laserpyramid 9 1,267 05-03-2024, 10:09 AM
Last Post: laserpyramid
  pinephone virtual keyboard aular 4 636 04-10-2024, 03:45 PM
Last Post: aular
  PinePhone Doesn't Boot LED Doesn't Show Any Signs When Charging dorkydev 1 439 04-02-2024, 11:50 AM
Last Post: Kevin Kofler
  Are you using the Pinephone as your daily driver? jro 157 115,102 02-18-2024, 11:33 PM
Last Post: aular
  2020 PinePhone Manjaro CE EU for sale, name your price astrojuanlu 7 2,239 02-14-2024, 04:51 PM
Last Post: astrojuanlu
  pinephone is not bootble for the box. ijij 1 832 01-19-2024, 01:29 PM
Last Post: fxc
  Multiple issues with the Pinephone MTXP 12 3,001 12-28-2023, 07:55 AM
Last Post: MTXP

Forum Jump:


Users browsing this thread: 1 Guest(s)