[SOLVED] Trouble flashing mobian to pinephone

binkyd · 08-29-2020, 10:06 AM

Alas and alack!

'Nother Pinephone stumbling block - finally got time to try to flash the phone, and the process won't start.

From the Mobian wiki:

Quote:

Installation to eMMC
You can install the image to eMMC by using JumpDrive.

1. Download the Jumpdrive image and flash the Jumpdrive image to a micro SD card
2. Boot the PinePhone from the Jumpdrive micro SD card
3. Connect the PinePhone to your computer using a USB cable
4. The sdcard and the emmc will become available as block devices on your computer (in the form of /dev/sdX block devices).
5. Flash the exposed (mounted) PinePhone drive with the Mobian image using one of the methods below.
6. Disconnect the PinePhone from your computer and remove the Jumpdrive SD card
7. Power in the PinePhone and boot Mobian from eMMC

Step 4 doesn't happen.

Phone tells me "Jumpdrive" is running, but the PC can't see it. It makes system-sounds like something's trying to connect but is failing.

So what essential step am I missing here? Is there a log that might say what? Do I need another utility or piece of software? Does anybody know?

binkyd · 08-29-2020, 10:26 AM

Figured out that issue - one of those times the front USB ports are inadequate - it worked from a back port.

Which brings the next question:

Which partition is the one to flash it to?

Code:

sde       8:64   1  14.7G  0 disk 
├─sde1    8:65   1   1.9M  0 part 
├─sde2    8:66   1     1M  0 part /run/media/binky/b93cc654-5b81-4149-b3d2-b37e
├─sde3    8:67   1     8M  0 part /run/media/binky/62f503f8-03ae-477c-9ca1-908c
├─sde4    8:68   1    64M  0 part /run/media/binky/ceb00a06-e590-4426-8072-71cf
├─sde5    8:69   1  64.3M  0 part 
├─sde6    8:70   1  63.9M  0 part /run/media/binky/6c7b502b-e5af-4ede-8b76-8dcb
├─sde7    8:71   1  63.9M  0 part 
├─sde8    8:72   1   2.4G  0 part /run/media/binky/cache
├─sde9    8:73   1   2.4G  0 part /run/media/binky/db17074a-eb35-43cc-b22d-bce9
└─sde10   8:74   1   8.6G  0 part /run/media/binky/userdata
sdf       8:80   1  29.5G  0 disk 
└─sdf1    8:81   1    49M  0 part /run/media/binky/B410-EB02

Would I be correct with flashing to

Code:

sde9    8:73   1   2.4G  0 part /run/media/binky/db17074a-eb35-43cc-b22d-bce9

as in:

Code:

sudo bmaptool copy mobian-pinephone-20200805.img.gz dev/sde9

Really don't want to screw this up...

linmob · 08-29-2020, 11:52 AM

Hi,

in order to run Mobian from eMMC you will need to flash it to /dev/sde:

Code:

sudo bmaptool copy mobian-pinephone-20200805.img.gz /dev/sde

Otherwise you will just end up with a broken Ubuntu Touch install.

binkyd · 08-29-2020, 11:57 AM

Thank you - that's what I wasn't getting.

binkyd · 08-29-2020, 12:18 PM

That gets me an error that
"sde is listed under /dev but it's a regular file"

and nothing goes to the phone.

So what's wrong with the command?

Which directory do I need to be in to run it?

binkyd · 08-29-2020, 12:47 PM

New error - (the last one was probably me)

Code:

bmaptool: info: discovered bmap file 'mobian-pinephone-20200805.img.bmap'
bmaptool: ERROR: An error occurred, here is the traceback:
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/bmaptools/CLI.py", line 116, in open_block_device
    descriptor = os.open(path, os.O_WRONLY | os.O_EXCL)

bmaptool: ERROR: cannot open block device '/dev/sde' in exclusive mode: [Errno 16] Device or resource busy: '/dev/sde'

What is that telling me, exactly?

boughtonp · 08-29-2020, 02:26 PM

It means you need to unmount the device first.

binkyd · 08-29-2020, 03:10 PM

ok, thanks.

(I used the same search, but without the quotes, and got nothing... so please be patient with me.)

After looking at that, and at the man pages, I find that I don't understand how to unmount 10 partitions... or is there one in particular?

binkyd · 08-29-2020, 04:19 PM

I've tried every possibility I could come up with here to unmount; no matter, whatever I try to "umount" I'm told it's not mounted.

But I still get that error.

Please, need some help here.

boughtonp · 08-29-2020, 04:23 PM

Quote:

Originally Posted by binkyd

I used the same search, but without the quotes, and got nothing...

Yeah, I find I need to put quotes around almost everything I search for these days, or the stupid search engine gives me results that don't actually match.

Even with quotes it's common to have several results not contain the actual text searched for. :/

Quote:

I find that I don't understand how to unmount 10 partitions... or is there one in particular?

My understand is that if you unmount the device it'll do all the partitions that belong to it, i.e. "umount /dev/sde" (as root/sudo)

Quote:

Originally Posted by binkyd

I've tried every possibility I could come up with here to unmount; no matter, whatever I try to "umount" I'm told it's not mounted.

Does "lsblk" still show the same as before?

If you have inxi installed, what does "inxi -p" and "inxi -o" output?

binkyd · 08-29-2020, 04:40 PM

Thanks!

Code:

sudo umount /dev/sdd

also gets the message "not mounted"

these:

Code:

inxi -p
Partition:
  ID-1: / size: 50.31 GiB used: 18.15 GiB (36.1%) fs: ext4 dev: /dev/sdb4 
  ID-2: /boot/efi size: 511.0 MiB used: 6.8 MiB (1.3%) fs: vfat 
  dev: /dev/sdb1 
  ID-3: /home size: 627.52 GiB used: 100.19 GiB (16.0%) fs: ext4 
  dev: /dev/sdc1 
  ID-4: /run/media/binky/62f503f8-03ae-477c-9ca1-908cc39ee168 size: 476 KiB 
  used: 24 KiB (5.0%) fs: ext2 dev: /dev/sdd3 
  ID-5: /run/media/binky/6c7b502b-e5af-4ede-8b76-8dcb41e41dfd 
  size: 34.7 MiB used: 14.1 MiB (40.5%) fs: ext4 dev: /dev/sdd6 
  ID-6: /run/media/binky/B410-EB02 size: 39.4 MiB used: 4.9 MiB (12.4%) 
  fs: vfat dev: /dev/sde1 
  ID-7: /run/media/binky/b93cc654-5b81-4149-b3d2-b37e38634e07 size: 476 KiB 
  used: 32 KiB (6.7%) fs: ext4 dev: /dev/sdd2 
  ID-8: /run/media/binky/cache size: 2.35 GiB used: 3.6 MiB (0.1%) fs: ext2 
  dev: /dev/sdd8 
  ID-9: /run/media/binky/ceb00a06-e590-4426-8072-71cf37cfe078 
  size: 44.4 MiB used: 38.6 MiB (87.0%) fs: ext4 dev: /dev/sdd4 
  ID-10: /run/media/binky/db17074a-eb35-43cc-b22d-bce998a1cd18 
  size: 2.28 GiB used: 1.58 GiB (69.2%) fs: ext4 dev: /dev/sdd9 
  ID-11: /run/media/binky/userdata size: 8.37 GiB used: 827.6 MiB (9.7%) 
  fs: ext4 dev: /dev/sdd10 
  ID-12: /run/timeshift/backup size: 287.37 GiB used: 69.27 GiB (24.1%) 
  fs: ext4 dev: /dev/sdc2 
  ID-13: swap-1 size: 16.00 GiB used: 768 KiB (0.0%) fs: swap dev: /dev/sdb2
 
$ inxi -o
Unmounted: ID-1: /dev/sda1 size: 631.51 GiB fs: ext4 label: N/A uuid: 1d01a246-a1b4-4b1d-a04f-b9f75ad59d1b 
           ID-2: /dev/sda2 size: 300.00 GiB fs: ext4 label: Timeshift--1 uuid: 9fb8ee1f-14b4-4c7d-85c9-42f24f5f5ced 
           ID-3: /dev/sdb3 size: 51.37 GiB fs: ext4 label: N/A uuid: f1533673-2b52-4139-a759-063c5e565d12 
           ID-4: /dev/sdd1 size: 1.9 MiB fs: <superuser/root required> label: N/A uuid: N/A 
           ID-5: /dev/sdd5 size: 64.3 MiB fs: <superuser/root required> label: N/A uuid: N/A 
           ID-6: /dev/sdd7 size: 63.9 MiB fs: <superuser/root required> label: N/A uuid: N/A

I hope you can get something out of it

boughtonp · 08-29-2020, 04:52 PM

Hrm, that inxi output appears to be is saying /dev/sde1 is mounted at /run/media/binky/B410-EB02
But your previous lsblk output showed that as sdf1 (which doesn't appear in the inxi output), so I'm confused.

I think I would restart the machine and boot into command line (so there's no desktop environment doing any auto-mounting stuff), then check again to make sure /dev/sde is the correct device, because maybe it's /dev/sdd now, and you want to be certain before you accidentally wipe the wrong drive.

binkyd · 08-29-2020, 05:15 PM

If I look in gnome-disks,

/run/media/binky/B410-EB02

is the SD-card with Jumpdrive on it.

binkyd · 08-30-2020, 06:50 AM

Tried to do this on another machine, and getting the same error about unmounting:

Code:

cannot open block device '/dev/sde' in exclusive mode: [Errno 16] Device or resource busy: '/dev/sde'

When I run "df", I get this result:

Code:

]$ sudo df
Filesystem      1K-blocks       Used  Available Use% Mounted on
dev              8134848         0   8134848   0% /dev
run              8176080      1712   8174368   1% /run
/dev/sdb4       52758920  19032020  31017192  39% /
tmpfs            8176080    277132   7898948   4% /dev/shm
tmpfs               4096         0      4096   0% /sys/fs/cgroup
tmpfs            8176080     47040   8129040   1% /tmp
/dev/sdb1         523248      6924    516324   2% /boot/efi
/dev/sdc1      658003344 147206520 477302348  24% /home
tmpfs            1635216       148   1635068   1% /run/user/1000
/dev/sdc2      301329856  72645752 213307772  26% /run/timeshift/backup
/dev/sdg1          40314      4993     35322  13% /run/media/devlin/B410-EB02
/dev/sdf2            476        32       412   8% /run/media/devlin/b93cc654-5b81-4149-b3d2-b37e38634e07
/dev/sdf6          35567     14400     18300  45% /run/media/devlin/6c7b502b-e5af-4ede-8b76-8dcb41e41dfd
/dev/sdf4          45488     39560      2344  95% /run/media/devlin/ceb00a06-e590-4426-8072-71cf37cfe078
/dev/sdf3            476        24       428   6% /run/media/devlin/62f503f8-03ae-477c-9ca1-908cc39ee168
/dev/sdf10       8777676    847428   7464648  11% /run/media/devlin/userdata
/dev/sdf8        2460672      3680   2331992   1% /run/media/devlin/cache
/dev/sdf9        2387816   1652908    593524  74% /run/media/devlin/db17074a-eb35-43cc-b22d-bce998a1cd18

Can anybody see from this exactly which one I need to unmount? I thought maybe the "tmpfs" on line 9, but that gives me this error:

Code:

$ sudo umount tmpfs
[sudo] password for binkyd: 
umount: /run/user/1000: target is busy.
$ sudo umount -f tmpfs
umount: /run/user/1000: target is busy.

How do I "unbusy" the damn thing? (this is the Jumpdrive: /dev/sdg1 /run/media/devlin/B410-EB02)

binkyd · 08-30-2020, 09:08 AM

Tried to register on the mobianproject site, but their stuff doesn't like me - can't get registered at all.

And at the same time, the pine64 site seems to be broken.

Fed up again.

I guess it's time to put the phone away, write it off.