HD51 4K Multiboot image

Willo3092 · Jan 3, 2019

Multiboot is rubbish on ATV compared to ViX. They don't even label what OS is on which partition.
I would try and do an image backup of your ATV setup to a spare partition using the yellow button in Image Manager and see if you can boot to it.
You shouldn't have to rename startup files for it to work correctly.
If that works then flash ViX to the first partition and use a decent multiboot manager.

pdw · Jan 3, 2019

Thanks Willo, I'll try that tomorrow .

pdw · Jan 4, 2019

Im afraid it wouldnt backup my ATV image - only option was the current image. I then decided to flash slot 1 with VIX - no problem. I then tried to flash ATV using grog's script you mentioned earlier but its failing:
root@mutant51:~# wget --no-check-certificate -O installatv.sh https://www.dropbox.com/s/nqbo698rxconave/installatv.sh?dl=1 && bash
stallatv.sh
--2019-01-04 13:29:12-- https://www.dropbox.com/s/nqbo698rxconave/installatv.sh?dl=1
Resolving www.dropbox.com... 2620:100:6020:1::a27d:4001, 162.125.64.1
Connecting to www.dropbox.com|2620:100:6020:1::a27d:4001|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: /s/dl/nqbo698rxconave/installatv.sh [following]
--2019-01-04 13:29:12-- https://www.dropbox.com/s/dl/nqbo698rxconave/installatv.sh
Reusing existing connection to [www.dropbox.com]:443.
HTTP request sent, awaiting response... 302 Found
Location: https://uca0d69d318df279dc2bc472884...OqcMbk4Z3F7G4OUNFwD8NTKYAm2-OE5Pd_rKFUpzagXO_
ch2Qs78g2vG0SaqCKDYDlrrsXe_BLp-Hrn5YKgZamlKicumBv1s7VtOShxopRjS-EBsgZI32ZNZ91iERByuTkPczE-rf85fsDPBX5fyub9FV1Wcg9dvMN3B9WVBIjkzt6b
f9m_5wNAmjitHvLXY/file?dl=1 [following]
--2019-01-04 13:29:13-- https://uca0d69d318df279dc2bc472884...om/cd/0/get/AYxOqcMbk4Z3F7G4OUNFwD8NTKYAm2-OE
5Pd_rKFUpzagXO_ch2Qs78g2vG0SaqCKDYDlrrsXe_BLp-Hrn5YKgZamlKicumBv1s7VtOShxopRjS-EBsgZI32ZNZ91iERByuTkPczE-rf85fsDPBX5fyub9FV1Wcg9dv
MN3B9WVBIjkzt6bf9m_5wNAmjitHvLXY/file?dl=1
Resolving uca0d69d318df279dc2bc472884a.dl.dropboxusercontent.com... 2620:100:6020:6::a27d:4006, 162.125.64.6
Connecting to uca0d69d318df279dc2bc472884a.dl.dropboxusercontent.com|2620:100:6020:6::a27d:4006|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 896 [application/binary]
Saving to: ‘installatv.sh’

installatv.sh 100%[========================================================>] 896 --.-KB/s in 0s

2019-01-04 13:29:13 (10.7 MB/s) - ‘installatv.sh’ saved [896/896]

bash: installatv.shwget: No such file or directory
root@mutant51:~# ofgwrite

ofgwrite Utility v4.2.1
Author: Betacentauri
Based upon: mtd-utils-native-1.5.1 and busybox 1.24.1
Use at your own risk! Make always a backup before use!
Don't use it if you use multiple ubi volumes in ubi layer!

Usage: ofgwrite <parameter> <image_directory>
Options:
-k --kernel flash kernel with automatic device recognition(default)
-kmtdx --kernel=mtdx use mtdx device for kernel flashing
-kmmcblkxpx --kernel=mmcblkxpx use mmcblkxpx device for kernel flashing
-r --rootfs flash rootfs with automatic device recognition(default)
-rmtdy --rootfs=mtdy use mtdy device for rootfs flashing
-rmmcblkxpx --rootfs=mmcblkxpx use mmcblkxpx device for rootfs flashing
-mx --multi=x flash multiboot partition x (x= 1, 2, 3,...). Only supported by some boxes.
-n --nowrite show only found image and mtd partitions (no write)
-f --force force kill e2
-q --quiet show less output
-h --help show help
root@mutant51:~# opkg install --force-reinstall ofgwrite
Downloading http://www.openvix.co.uk/feeds/open...vfpv4/ofgwrite_4.x+git147+3899e86-r0_cortexa1
5hf-neon-vfpv4.ipk.
Upgrading ofgwrite from 4.x+git145+9cc3f09-r0 to 4.x+git147+3899e86-r0 on root.
Installing ofgwrite (4.x+git147+3899e86) on root.
Configuring ofgwrite.
root@mutant51:~# wget --no-check-certificate -O installatv.sh https://www.dropbox.com/s/nqbo698rxconave/installatv.sh?dl=1 && bash
installatv.sh
--2019-01-04 13:33:53-- https://www.dropbox.com/s/nqbo698rxconave/installatv.sh?dl=1
Resolving www.dropbox.com... 2620:100:6020:1::a27d:4001, 162.125.64.1
Connecting to www.dropbox.com|2620:100:6020:1::a27d:4001|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: /s/dl/nqbo698rxconave/installatv.sh [following]
--2019-01-04 13:33:54-- https://www.dropbox.com/s/dl/nqbo698rxconave/installatv.sh
Reusing existing connection to [www.dropbox.com]:443.
HTTP request sent, awaiting response... 302 Found
Location: https://uca0d69d318df279dc2bc472884...OqcMbk4Z3F7G4OUNFwD8NTKYAm2-OE5Pd_rKFUpzagXO_
ch2Qs78g2vG0SaqCKDYDlrrsXe_BLp-Hrn5YKgZamlKicumBv1s7VtOShxopRjS-EBsgZI32ZNZ91iERByuTkPczE-rf85fsDPBX5fyub9FV1Wcg9dvMN3B9WVBIjkzt6b
f9m_5wNAmjitHvLXY/file?dl=1 [following]
--2019-01-04 13:33:54-- https://uca0d69d318df279dc2bc472884...om/cd/0/get/AYxOqcMbk4Z3F7G4OUNFwD8NTKYAm2-OE
5Pd_rKFUpzagXO_ch2Qs78g2vG0SaqCKDYDlrrsXe_BLp-Hrn5YKgZamlKicumBv1s7VtOShxopRjS-EBsgZI32ZNZ91iERByuTkPczE-rf85fsDPBX5fyub9FV1Wcg9dv
MN3B9WVBIjkzt6bf9m_5wNAmjitHvLXY/file?dl=1
Resolving uca0d69d318df279dc2bc472884a.dl.dropboxusercontent.com... 2620:100:6020:6::a27d:4006, 162.125.64.6
Connecting to uca0d69d318df279dc2bc472884a.dl.dropboxusercontent.com|2620:100:6020:6::a27d:4006|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 896 [application/binary]
Saving to: ‘installatv.sh’

installatv.sh 100%[========================================================>] 896 --.-KB/s in 0s

2019-01-04 13:33:54 (27.8 MB/s) - ‘installatv.sh’ saved [896/896]

python: can't open file '/usr/lib/enigma2/python/BoxBrandingTest.py': [Errno 2] No such file or directory
You are about to flash your box with the latest stable image of ATV
If using multiboot box please enter partition to flash: 2
BusyBox v1.27.2 (2018-11-23 14:42:21 GMT) multi-call binary.

Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f FILE [FILE]...

Search for PATTERN in FILEs (or stdin)

-H Add 'filename:' prefix
-h Do not add 'filename:' prefix
-n Add 'line_no:' prefix
-l Show only names of files that match
-L Show only names of files that don't match
-c Show only count of matching lines
-o Show only the matching part of line
-q Quiet. Return 0 if PATTERN is found, 1 otherwise
-v Select non-matching lines
-s Suppress open and read errors
-r Recurse
-i Ignore case
-w Match whole words only
-x Match whole lines only
-F PATTERN is a literal (not regexp)
-E PATTERN is an extended regexp
-m N Match up to N times per file
-A N Print N lines of trailing context
-B N Print N lines of leading context
-C N Same as '-A N -B N'
-e PTRN Pattern to match
-f FILE Read pattern from file
mv: can't rename 'latestatv': No such file or directory

It didnt ask me which box or model like it did with Vix. Any ideas?

Willo3092 · Jan 4, 2019

I don't install ATV but I think it should pick up which image to flash from boxbranding.
Best way to do it is to download the zip file from the ATV site and copy it to /media/hdd/imagebackups/ and flash using the ViX image manager. Flash to partition 2.

pdw · Jan 4, 2019

Doh! Its because there is no ATV image installed. How do I force an ATV flash to slot2?

pdw · Jan 4, 2019

Willo3092 said:
I don't install ATV but I think it should pick up which image to flash from boxbranding.
Best way to do it is to download the zip file from the ATV site and copy it to /media/hdd/imagebackups/ and flash using the ViX image manager. Flash to partition 2.

Good idea! I'll try that.

pdw · Jan 4, 2019

Thanks a lot Willo. Your idea worked a treat. I now have Vix on slot 1 and ATV on slot 2. Perfect!

pdw · Jan 4, 2019

Alas, I spoke too soon. After rebooting from ATV it boots back into ATV even though the image is in slot2 and VIX in slot1 - all I can think is that ATV is set up to reboot into its own image no matter where it is. Think Ive had enough now :)

Abu Baniaz · Jan 4, 2019

Maybe you could report the issue to openatv?

pdw · Jan 4, 2019

Abu Baniaz said:
Maybe you could report the issue to openatv?

Thats a very good idea. I think I will.

pdw · Jan 4, 2019

OK an update. It doesnt look like its an ATV problem, the problem lies with Wooshbuild Infinity. As an experiment, I renamed the files to force a boot into VIX - flashed another ATV in slot3 without Wooshbuild Infinity which I have on the ATV in slot2. I then used the multiboot option and selected slot1 to go back to Vix - it worked no problem.

Willo3092 · Jan 4, 2019

I can't see how Infinity would affect which partition to boot to...

If you don't have any success I'll try it on mine but I don't think I'll get time tonight.

pdw · Jan 4, 2019

Thanks Willo - with Infinity, if you select multiboot in order to boot to another image, the box just crashes (the same occurs if you try and backup image). With ATV same version without Infinity there's no problem. It'll be interesting to see how you get on.

Willo3092 · Jan 4, 2019

Have you looked at the crash logs? Use Notepad++ to open them, not standard notepad.
This will usually point you in the right direction.

/home/root/logs

If there are lots, just delete them and invoke a crash to generate a new log.

pdw · Jan 4, 2019

Willo3092 said:
Have you looked at the crash logs? Use Notepad++ to open them, not standard notepad.
This will usually point you in the right direction.

/home/root/logs

If there are lots, just delete them and invoke a crash to generate a new log.

This is the latest log just created by selecting multiboot in the menu.

Willo3092 · Jan 4, 2019

Try copying /usr/lib/enigma2/python/Screens/MultiBootStartup.py from the vanilla ATV image to the Infinity image and reboot.

There's also a bit of grumbling about the skin having missing elements, try using a native skin like Metrix (might be worth trying that first actually)

pdw · Jan 4, 2019

Thanks Willo - Ill try this tomorrow.

pdw · Jan 4, 2019

Managed to try tonight - there was no MultiBootStartup.py file but a MultiBootStartup.pyo file which I copied and overwrote to the Infinity image. This didnt help. Also tried using the Metrix skin as well (did this before copying the file and after ) but still the box crashes selecting multiboot. When I restart from Infinity it still boots straight into Infinity again.
Ive double checked the images Slot1=Vix (Willobuild), Slot2=ATV (Infinity), Slot3=Vanilla ATV. Looking also from Vanilla ATV, Startup_1=Vix (Willobuild), Startup_2=ATV (Infinity), Startup_3=Vanilla ATV

pdw · Jan 5, 2019

The fact that multiboot works fine in the VIX and Vanilla ATV images and it does not work in Infinity; in fact it crashes the box, must surely point to an Infinity issue or am I mkssing something?

Willo3092 · Jan 5, 2019

Certainly looks like it. Possibly there are changed python files in WB? Have you asked about it in the support thread?

http://www.techkings.org/threads/wooshbuild-infinity-support-thread.140703/

HD51 4K Multiboot image

VIP Member

Member

Member

VIP Member

Member

Member

Member

Member

TK Veteran

Member

Member

VIP Member

Member

VIP Member

Member

Attachments

VIP Member

Member

Member

Member

VIP Member

Similar threads