Bootloader failed to update on March update

Had the following error message on a 4K+
I previous had some problems with a bricked device, @sam_nazarko helped me out with, due to the 4.9 testing, so i am sure it has something to do with that.

There is nothing in the logs due to several reboots after enabling debug logs and disable an VPN addon which spammed the logs.

Logs http://paste.osmc.io/ituqasokuq.vhdl

What to do from here?

Can you try to reinstall the bootloader:

sudo apt-get install --reinstall vero3-bootloader-osmc

Perhaps we’ll get a better idea of why it’s failing.

Sure, here it is

osmc@osmc_stue:~$ sudo apt-get install --reinstall vero3-bootloader-osmc
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for vero3-bootloader-osmc:armhf

Debug logs. https://paste.osmc.tv/nayuzatena

I can download it.

osmc@osmc-4k:~$ apt-get download vero3-bootloader-osmc
Get:1 http://ftp.fau.de/osmc/osmc/apt stretch/main armhf vero3-bootloader-osmc armhf 1.3.0-1 [1602 kB]
Fetched 1602 kB in 4s (363 kB/s)   

Try sudo apt-get update and, if no errors, retry the reinstall.

Already tried that, and it is the same.

osmc@osmc_stue:~$ sudo apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.debian.org/debian stretch InRelease
Hit:3 http://ftp.debian.org/debian stretch-updates InRelease
Hit:5 http://ftp.debian.org/debian stretch Release
Hit:4 http://ftp.fau.de/osmc/osmc/apt stretch InRelease
Reading package lists… Done
osmc@osmc_stue:~$ sudo apt-get install --reinstall vero3-bootloader-osmc
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for vero3-bootloader-osmc:armhf

The update step looks ok.

sudo apt-get clean
sudo apt-get install --reinstall vero3-bootloader-osmc

Same.

osmc@osmc_stue:~$ sudo apt-get clean
osmc@osmc_stue:~$ sudo apt-get install --reinstall vero3-bootloader-osmc
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for vero3-bootloader-osmc:armhf

I hate these “internal error” messages.

A quick search threw up some possible fixes, though the root cause is unclear and might require Sam’s input. Try this

sudo dpkg --configure --pending

It intentionally fails for a reason - there’s a sanity check to prevent it from installing. Otherwise his device will end up a brick. I’ll post some instructions shortly.

1 Like

Me to :slight_smile: I really suspect it has something to do with the 4.9 testing, which bricked the Vero 4k+, and had to force it in USB recovery mode, and use USB burning tool to flash it.

Here is the output.

osmc@osmc_stue:~$ sudo dpkg --configure --pending
Setting up vero3-bootloader-osmc (1.3.0-1) …
Bootloader and device mismatch
dpkg: error processing package vero3-bootloader-osmc (–configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of vero364-image-3.14.29-157-osmc:arm64:
vero364-image-3.14.29-157-osmc:arm64 depends on vero3-bootloader-osmc:armhf (>= 1.0.0); however:
Package vero3-bootloader-osmc is not configured yet.

dpkg: error processing package vero364-image-3.14.29-157-osmc:arm64 (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of vero3-device-osmc:
vero3-device-osmc depends on vero3-bootloader-osmc; however:
Package vero3-bootloader-osmc is not configured yet.

dpkg: error processing package vero3-device-osmc (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of vero364-kernel-osmc:arm64:
vero364-kernel-osmc:arm64 depends on vero364-image-3.14.29-157-osmc; however:
Package vero364-image-3.14.29-157-osmc:arm64 is not configured yet.

dpkg: error processing package vero364-kernel-osmc:arm64 (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
vero3-bootloader-osmc
vero364-image-3.14.29-157-osmc:arm64
vero3-device-osmc
vero364-kernel-osmc:arm64

That was appearing in the 4.9 testing, wasn’t it? Over to Sam, I think.

Yes it was. Thank you for taking the time :slight_smile:

1 Like

Please run:

sudo fw_setenv revmodel '4kplus'
sudo fw_setenv initargs 'initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 revision=4kplus'

Then reboot, and try update again.

Sam

@thansen_dk’s previous log doesn’t show it as being a plus.

rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive logo=osd1,loaded,0x3d800000,576cvbs maxcpus=4 vout=576cvbs,enable hdmimode=1080p60hz cvbsmode=576cvbs hdmitx= cvbsdrv=0 pq= androidboot.firstboot=1 jtag=apao androidboot.hardware=amlogic mac=c4:4e:ac:28:57:72 androidboot.mac=c4:4e:ac:28:57:72 androidboot.slot_suffix=_a root=/dev/vero-nand/root rootfstype=ext4 quiet console=tty0 osmcdev=vero3

Will this make a difference?

Yes – but he says it is a +.

The bootloader install deliberately bails for now, to prevent problems.

It is a 4K+

It’s my fault – we sent him a 4K unbrick image instead of 4K +.
There will be a few corner cases where users are affected like this.

Ran the above with no errors, but i am not sure it is fixed.

osmc@osmc_stue:~$ sudo apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.debian.org/debian stretch InRelease
Hit:4 http://ftp.debian.org/debian stretch-updates InRelease
Hit:5 http://ftp.debian.org/debian stretch Release
Hit:3 http://ftp.fau.de/osmc/osmc/apt stretch InRelease
Reading package lists… Done
osmc@osmc_stue:~$ sudo apt-get dist-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up vero3-bootloader-osmc (1.3.0-1) …
11+0 records in
11+0 records out
11 bytes copied, 0.00126052 s, 8.7 kB/s
1632+0 records in
1632+0 records out
835584 bytes (836 kB, 816 KiB) copied, 0.0356846 s, 23.4 MB/s
Setting up vero364-image-3.14.29-157-osmc:arm64 (157) …
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.14.29-157-osmc /b oot/vmlinuz-3.14.29-157-osmc
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal-osmc 3.14.29-157-os mc /boot/vmlinuz-3.14.29-157-osmc
run-parts: executing /etc/kernel/postinst.d/inform-updater 3.14.29-157-osmc /boo t/vmlinuz-3.14.29-157-osmc
run-parts: executing /etc/kernel/postinst.d/upload-to-emmc 3.14.29-157-osmc /boo t/vmlinuz-3.14.29-157-osmc
7+1 records in
7+1 records out
8318976 bytes (8.3 MB, 7.9 MiB) copied, 0.226447 s, 36.7 MB/s
0+1 records in
0+1 records out
83968 bytes (84 kB, 82 KiB) copied, 0.01054 s, 8.0 MB/s
Setting up vero364-kernel-osmc:arm64 (3.9.157) …
Setting up vero3-device-osmc (1.4.4) …
W: APT had planned for dpkg to do more than it reported back (9 vs 13).
Affected packages: vero3-bootloader-osmc:armhf

Run sudo apt-get -f install

It looks like it has worked as expected.

1 Like

Yes, everything seems to be fine now.

Was this caused by the problems i had with the 4.9 testing, which bricked the Vero?? and does that mean that there should be no problems with future updates regarding to the bootloader?

Thank you very much.