+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: UBPorts on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=125)
+---- Thread: Pinephone UBport Edition no OS preinstalled (/showthread.php?tid=10129)
Pages:
1
2
Pinephone UBport Edition no OS preinstalled - Bouc - 06-08-2020
Hi, I just received the Ubuntu Edition pinophone, I removed the film on the battery and turned it on.
The phone is in "boot loop" showing the pinecone for a few seconds, then a black screen with the LEDs changing from red to white to blue and then the pinecone. Endlessly.
I think I need help. Shouldn't the Ubuntu touch OS be pre-installed?
Update: now on power-up it shows the pine cone only once, then black screen with steady red LED.
RE: Pinephone UBport Edition no OS preinstalled - --- - 06-08-2020
Yes, mine started first time.
RE: Pinephone UBport Edition no OS preinstalled - malditobastardo - 06-08-2020
Check the FAQ https://forum.pine64.org/showthread.php?tid=10130
RE: Pinephone UBport Edition no OS preinstalled - Bouc - 06-08-2020
(06-08-2020, 10:22 AM)malditobastardo Wrote: Check the FAQ https://forum.pine64.org/showthread.php?tid=10130
FAQ don't help. I've tryed shutdown and restart many times, but the result is the same.
Restart loop 3/4 times and then black screen and red led.
RE: Pinephone UBport Edition no OS preinstalled - idontcare - 06-08-2020
Have you tried charging the phone? Maybe the battery is nearly empty. I'd do that - completely remove the battery (hard power-off
), put it back in, put it on a charger overnight and try again.Oh, btw, did you see this thread?
RE: Pinephone UBport Edition no OS preinstalled - Bouc - 06-08-2020
(06-08-2020, 10:22 AM)malditobastardo Wrote: Check the FAQ https://forum.pine64.org/showthread.php?tid=10130
I've tryed the "telnet" thing, but doesn't work:
Code:
telnet 172.16.42.1
Trying 172.16.42.1...
Connected to 172.16.42.1.
Escape character is '^]'.
Welcome to Rescue SD Shell!
/ # umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync
umount: can't unmount /dev/mmcblk2p10: Invalid argument
e2fsck 1.46-WIP (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/mmcblk2p10
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
/ # sync && reboot -fRE: Pinephone UBport Edition no OS preinstalled - 33YN2 - 06-08-2020
(06-08-2020, 01:05 PM)Bouc Wrote:(06-08-2020, 10:22 AM)malditobastardo Wrote: Check the FAQ https://forum.pine64.org/showthread.php?tid=10130
FAQ don't help. I've tryed shutdown and restart many times, but the result is the same.
Restart loop 3/4 times and then black screen and red led.
Did you defragment the EMMC like it said?
Code:
umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && syncRE: Pinephone UBport Edition no OS preinstalled - Bouc - 06-08-2020
(06-08-2020, 02:42 PM)Aberts10 Wrote:(06-08-2020, 01:05 PM)Bouc Wrote:(06-08-2020, 10:22 AM)malditobastardo Wrote: Check the FAQ https://forum.pine64.org/showthread.php?tid=10130
FAQ don't help. I've tryed shutdown and restart many times, but the result is the same.
Restart loop 3/4 times and then black screen and red led.
Did you defragment the EMMC like it said?
Code:umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync
Code:
/ # umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync
umount: can't unmount /dev/mmcblk2p10: Invalid argument
e2fsck 1.46-WIP (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/mmcblk2p10
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>RE: Pinephone UBport Edition no OS preinstalled - 33YN2 - 06-08-2020
(06-08-2020, 03:03 PM)Bouc Wrote:(06-08-2020, 02:42 PM)Aberts10 Wrote:(06-08-2020, 01:05 PM)Bouc Wrote:(06-08-2020, 10:22 AM)malditobastardo Wrote: Check the FAQ https://forum.pine64.org/showthread.php?tid=10130
FAQ don't help. I've tryed shutdown and restart many times, but the result is the same.
Restart loop 3/4 times and then black screen and red led.
Did you defragment the EMMC like it said?
Code:umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync
Code:/ # umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync
umount: can't unmount /dev/mmcblk2p10: Invalid argument
e2fsck 1.46-WIP (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/mmcblk2p10
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
You followed the other steps before doing that? You have to be in jumpdrive mode (Recovery mode basically)
RE: Pinephone UBport Edition no OS preinstalled - Bouc - 06-09-2020
(06-08-2020, 08:52 PM)Aberts10 Wrote: You followed the other steps before doing that? You have to be in jumpdrive mode (Recovery mode basically)
I've followed every step. All was ok, I see the orange robot and i read the 'Welcome to Rescue SD Shell!'.
The first error is when I try to unmount /dev/mmcblk2p10.