HowTo Vu+ Multiboot in OpenBh 5.2

Liquid said:
In the past I was able to get android running on vuuno4kse. But it was far to be a working android. Netflix and prime due to missing certificates runs at low resolution. Finally since the SDK for android was leaked from somewhere there could be license issue. Then getting the same working on the other box were time consuming, so I stopped the project.
I tried also other innovative approach but drivers stopped me.
Click to expand...
Thanks for sharing your experiences
Is there new since time of that project gives cause for optimism to be rethought?
How to get New combatable Android versions and how to build them to fit VU+ devices!
Is this from individual developers or what?
Do you think the is feasible and worth researching and developing?
It is with the same logic that the team followed in developing the internal partition on Vu devices, We hope that the dual boot (android/enigma2) will be available like other devices
Thanks again
 
biko said:
Thanks for sharing your experiences
Is there new since time of that project gives cause for optimism to be rethought?
How to get New combatable Android versions and how to build them to fit VU+ devices!
Is this from individual developers or what?
Do you think the is feasible and worth researching and developing?
It is with the same logic that the team followed in developing the internal partition on Vu devices, We hope that the dual boot (android/enigma2) will be available like other devices
Thanks again
Click to expand...
Forget it. Too complicated, too much hardware resource to build android images.
And the resulting image was too buggy. It was fun for me but can't be released.
 
I used a brand new USB 3.2 Stick, a SanDisk 32GB and initialized it in ext4
I re-flashed the entire VU+Ultimo4K .
I also initialized internal SSD in ext4.
It won't flash any image in fifth slot, no matter what I try.
So, three images are in the flash, the fourth is on a USB stick and the fifth won't fit in.
It gets halfway through and says errors and restarts. Any idea is welcome.

1697787473135.png
 
It seems recent sandisk usb sticks are not as good as they used to be.

I have had 4 fails on me recently (some boxes won't accept them at all, others will work for a while then the stick becomes corrupt).

I would suggest trying to format it again and give it another go, and if you still get the same issue try another stick.

In the meantime could you post a debug log, so we can take a look at what is going on.
 
Enigma2_crash is too big, but error is mentioned here:

OpenBh Enigma2 Crashlog

Crashdate = Fri Oct 20 09:34:34 2023

Creator = OpenBh
Version = 5.3
Build = 009
Type = release
Machine = vuultimo4k
URL = http://www.openbh.net
distro=openbh
compile-date=20231015
compile-datetime=20231015193206
Compiled = Oct 16 2023
Skin = MX_Slim-Line_NP/skin.xml
Component = Enigma2

Kernel CMDline = kexec=1 rootfstype=ext4 rootflags=data=journal rootwait rw coherent_pool=2M vmalloc=622m bmem=630m@394m bmem=383m@1665m bmem=443m@2625m kernel=/linuxrootfs1/zImage root=/dev/mmcblk0p4 rootsubdir=linuxrootfs1

...

< 177.4910> 09:34:34.6062 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/OBH/ImageManager.py", line 674, in ofgwriteResult
< 177.4917> 09:34:34.6069 AttributeError: 'OpenBhImageManager' object has no attribute 'session'
< 177.4918> 09:34:34.6070 [ePyObject] (CallObject(<bound method ConsoleItem.finishedCB of <Components.Console.ConsoleItem object at 0xaf367e30>>,(1,)) failed)


dmesg

<6>[ 0.000000] Booting Linux on physical CPU 0x0

...
 
No thats the end result, ofgwrite has an error condition so has returned non 0 return code........

Would be interesting to see the return code from just before this crash:-
print("[ImageManager] ofgwrite retval :", retval)
and the ofgwrite output which should be there in the log
 
< 79.7975> 09:32:56.9126 [eInputDeviceInit0] 0 0 (0) 0
< 79.7992> 09:32:56.9144 ImageManager 5
< 79.7995> 09:32:56.9146 [BackupManager] Device: /media/hdd/
< 79.7995> 09:32:56.9147 [BackupManager] Directory: /media/hdd/backup/
< 79.8034> 09:32:56.9185 [Skin] Processing screen 'JobView', position=(309, 149), size=(1302 x 782) for module 'JobView'.
< 79.8522> 09:32:56.9673 [Screen] Warning: Skin is missing element 'HelpWindow' in <class 'Screens.TaskView.JobView'>.
< 79.8596> 09:32:56.9748 [Skin] Processing screen 'JobView_summary' from list 'JobView_summary, SetupSummary, SimpleSummary', position=(0, 0), size=(800 x 480) for module 'SetupSummary'.
< 80.0281> 09:32:57.1432 [eInputDeviceInit0] 0 160 (352) 1
< 80.0281> 09:32:57.1433 [eRCDeviceInputDev] emit: 0
< 80.0284> 09:32:57.1436 [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 80.0285> 09:32:57.1437 [InfoBarGenerics] KEY: 352 OK
< 80.0286> 09:32:57.1438 [eInputDeviceInit0] 0 0 (0) 0
< 80.9457> 09:32:58.0609 [BackupManager] Listing installed plugins
< 80.9458> 09:32:58.0609 [Console] command: opkg status
< 80.9458> 09:32:58.0610 [eConsoleAppContainer] Starting /bin/sh
< 81.0086> 09:32:58.1237 [Console] finished: opkg status
< 81.0311> 09:32:58.1462 [BackupManager] Listing completed.
< 81.9507> 09:32:59.0659 [BackupManager] Finding kernel version:3.14.28
< 81.9512> 09:32:59.0664 [BackupManager] Finding image version:5.3
< 84.0740> 09:33:01.1892 [BackupManager] Backup running
< 84.0746> 09:33:01.1898 [Console] command: tar -T /tmp/_backup-files.list -czvf /media/hdd/backup/openbh-rel-IM-5.3.009-20231020-0933.tar.gz
< 84.0747> 09:33:01.1899 [eConsoleAppContainer] Starting /bin/sh
< 84.2341> 09:33:01.3493 [Console] finished: tar -T /tmp/_backup-files.list -czvf /media/hdd/backup/openbh-rel-IM-5.3.009-20231020-0933.tar.gz
< 84.2343> 09:33:01.3495 [BackupManager] Complete.
< 85.0816> 09:33:02.1968 [Task] job Components.Task.Job name=Backup manager #tasks=11 completed with [] in None
< 85.0878> 09:33:02.2030 [Skin] Processing screen 'MessageBox', position=(397, 535), size=(1125 x 10) for module 'MessageBox'.
< 85.0931> 09:33:02.2083 [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Please wait while the flash prepares.).
< 85.0933> 09:33:02.2084 [Skin] Attribute 'itemHeight' (with value of '40') in object of type 'eLabel' is not implemented!
< 85.0939> 09:33:02.2091 [Pixmap] setPixmapNum(1) failed! defined pixmaps: []
< 85.0942> 09:33:02.2094 [MessageBox] Timeout set to 240 seconds.
< 85.0950> 09:33:02.2101 [Skin] Processing screen 'MessageBox_summary' from list 'MessageBox_summary, SimpleSummary', position=(0, 0), size=(800 x 480) for module 'ScreenSummary'.
< 85.0966> 09:33:02.2118 [Console] command: unzip -o /media/hdd/imagebackups/openvix-6.4.008.release-vuultimo4k_usb.zip -d /media/hdd/imagebackups/imagerestore
< 85.0967> 09:33:02.2119 [eConsoleAppContainer] Starting /bin/sh
< 90.6254> 09:33:07.7406 [Console] finished: unzip -o /media/hdd/imagebackups/openvix-6.4.008.release-vuultimo4k_usb.zip -d /media/hdd/imagebackups/imagerestore
< 90.6274> 09:33:07.7426 [Skin] Processing screen 'MessageBox', position=(397, 535), size=(1125 x 10) for module 'MessageBox'.
< 90.6330> 09:33:07.7482 [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Flash image unzip successful.).
< 90.6332> 09:33:07.7484 [Skin] Attribute 'itemHeight' (with value of '40') in object of type 'eLabel' is not implemented!
< 90.6339> 09:33:07.7491 [Pixmap] setPixmapNum(1) failed! defined pixmaps: []
< 90.6343> 09:33:07.7494 [MessageBox] Timeout set to 4 seconds.
< 90.6351> 09:33:07.7503 [Skin] Processing screen 'MessageBox_summary' from list 'MessageBox_summary, SimpleSummary', position=(0, 0), size=(800 x 480) for module 'ScreenSummary'.
< 90.6367> 09:33:07.7519 [ImageManager] MAINDEST=/media/hdd/imagebackups/imagerestore
< 90.6372> 09:33:07.7524 [ImageManager] FIXED MAINDEST=/media/hdd/imagebackups/imagerestore/vuplus/ultimo4k
< 90.6373> 09:33:07.7525 [ImageManager] running commnd:/usr/bin/ofgwrite -rsdb1 -kzImage -s'ultimo4k/linuxrootfs' -m5 '/media/hdd/imagebackups/imagerestore/vuplus/ultimo4k' slot = 5
< 90.6374> 09:33:07.7525 [ImageManager] running commnd: /usr/bin/ofgwrite -rsdb1 -kzImage -s'ultimo4k/linuxrootfs' -m5 '/media/hdd/imagebackups/imagerestore/vuplus/ultimo4k'
< 90.6374> 09:33:07.7526 [Console] command: /usr/bin/ofgwrite -rsdb1 -kzImage -s'ultimo4k/linuxrootfs' -m5 '/media/hdd/imagebackups/imagerestore/vuplus/ultimo4k'
< 90.6375> 09:33:07.7526 [eConsoleAppContainer] Starting /bin/sh
< 94.6627> 09:33:11.7778 [MessageBox] Timeout!
< 158.6957> 09:34:15.8108 [eInputDeviceInit0] 1 ae (174) 1
< 158.6957> 09:34:15.8109 [eRCDeviceInputDev] emit: 1
< 158.6960> 09:34:15.8112 [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 158.6961> 09:34:15.8112 [InfoBarGenerics] KEY: 174 EXIT
< 158.6962> 09:34:15.8113 [ActionMap] Keymap 'OkCancelActions' -> Action = 'cancel'.
< 158.6972> 09:34:15.8124 [eInputDeviceInit0] 0 0 (0) 0
< 158.9270> 09:34:16.0422 [eInputDeviceInit0] 0 ae (174) 1
< 158.9270> 09:34:16.0422 [eRCDeviceInputDev] emit: 0
< 158.9273> 09:34:16.0425 [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 158.9274> 09:34:16.0426 [InfoBarGenerics] KEY: 174 EXIT
< 158.9275> 09:34:16.0426 [eInputDeviceInit0] 0 0 (0) 0
< 162.0643> 09:34:19.1795 [eInputDeviceInit0] 1 ae (174) 1
< 162.0643> 09:34:19.1795 [eRCDeviceInputDev] emit: 1
< 162.0646> 09:34:19.1798 [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 162.0647> 09:34:19.1799 [InfoBarGenerics] KEY: 174 EXIT
< 162.0648> 09:34:19.1799 [ActionMap] Keymap 'OkCancelActions' -> Action = 'cancel'.
< 162.0660> 09:34:19.1812 [eInputDeviceInit0] 0 0 (0) 0
< 162.4031> 09:34:19.5182 [eInputDeviceInit0] 0 ae (174) 1
< 162.4031> 09:34:19.5183 [eRCDeviceInputDev] emit: 0
< 162.4034> 09:34:19.5186 [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 162.4035> 09:34:19.5187 [InfoBarGenerics] KEY: 174 EXIT
< 162.4036> 09:34:19.5188 [eInputDeviceInit0] 0 0 (0) 0
< 177.4705> 09:34:34.5856 [Console] finished: /usr/bin/ofgwrite -rsdb1 -kzImage -s'ultimo4k/linuxrootfs' -m5 '/media/hdd/imagebackups/imagerestore/vuplus/ultimo4k'
< 177.4706> 09:34:34.5858 [fb] double buffering available!
< 177.4901> 09:34:34.6053 [ImageManager] ofgwrite retval : 1
< 177.4904> 09:34:34.6056 Traceback (most recent call last):
< 177.4905> 09:34:34.6056 File "/usr/lib/enigma2/python/Components/Console.py", line 49, in finishedCB
< 177.4910> 09:34:34.6062 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/OBH/ImageManager.py", line 674, in ofgwriteResult
< 177.4917> 09:34:34.6069 AttributeError: 'OpenBhImageManager' object has no attribute 'session'
< 177.4918> 09:34:34.6070 [ePyObject] (CallObject(<bound method ConsoleItem.finishedCB of <Components.Console.ConsoleItem object at 0xaf367e30>>,(1,)) failed)
 
So does slot 5 show an image installed in MultiBootSelector (long press power)? and if so what happens if you try to boot it???
 
Last edited:
So unzip & copy the attachment to /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX and reboot, if you use Putty init 4 before copy and init 3 afterwards
Post the debug, would like to see both returns in debug from ofgwrite ...... it should not crash as before.
 

Attachments

It had been a long, exhausting day :sick:
Flashing slot 1, 2, 3 but there was not slot 4,5,6 ...
Red button didn't create 4 more slots.
I changed several different USB sticks, of different types (USB 2.0, 3.0, 3.1, 3.2) and capacities (4GB, 16GB, 32GB)
Same problem with OBH 5.3.009.
Then I finaly try OBH 5.3.001. and everything was beautiful :) :)
I flashed also latest versions of PLI, ATV, VIX, Pure2, Vision and all of them works just fine.
So the OBH 5.3.009. is obviously not good, at least for VU+Ultimo4K
Finally I made new fatal error.
I flashed good old BlackHole 3.1.0. but I forget to replace kernel_auto.bin and of course stuck with Black Hole.
So I start flashing again from begining instead to use STARTUP_RECOVERY as described is post #1
I really do everything the hard way but
 
klofer said:
It had been a long, exhausting day :sick:
Flashing slot 1, 2, 3 but there was not slot 4,5,6 ...
Red button didn't create 4 more slots.
I changed several different USB sticks, of different types (USB 2.0, 3.0, 3.1, 3.2) and capacities (4GB, 16GB, 32GB)
Same problem with OBH 5.3.009.
Then I finaly try OBH 5.3.001. and everything was beautiful :) :)
I flashed also latest versions of PLI, ATV, VIX, Pure2, Vision and all of them works just fine.
So the OBH 5.3.009. is obviously not good, at least for VU+Ultimo4K
Finally I made new fatal error.
I flashed good old BlackHole 3.1.0. but I forget to replace kernel_auto.bin and of course stuck with Black Hole.
So I start flashing again from begining instead to use STARTUP_RECOVERY as described is post #1
I really do everything the hard way but
Click to expand...
If you want to install Blackhole 3.1.0 (or your BH 3.1.0 backup) on your Solo4K you need to repack the image with the file BH Solo4K kernel_auto.bin. Download it,, unzip the image, replace the original kernel_auto.bin. Zip it again and flash it from openbh image manager

follow this guide: https://board.openbh.net/threads/howto-vu-multiboot-in-openbh-5-2.3119/

and after this: https://board.openbh.net/threads/howto-vu-multiboot-in-openbh-5-2.3119/page-4
 
I finally succeeded, I made my big six :)
All of images work fine but first 3 (in flash) work much faster then others in USB 2.0 device.
Yesterday, during tests with many of them I noticed that USB 3.0 (3.2) is really faster.
Main image in slot 1 is OBH 5.3.001. and I won't do update/upgrade until 5.3.010 will shown cause 5.3.009 did not create 4 extra slots (red button) on my VU+Ultimo4K.
Can someone confirm which images (and versions) are also convenient for VU+multiboot, especially for VU+Ultimo4K?
Pic7.png
 
43 slot
but you can do whatever you want,
for knowledge
is to understand the various images,
to test and improve everything

1697974294325.png
 
klofer said:
Main image in slot 1 is OBH 5.3.001. and I won't do update/upgrade until 5.3.010 will shown cause 5.3.009 did not create 4 extra slots (red button) on my VU+Ultimo4K.
Click to expand...
Few days ago I made mistake and update OBH 5.3.001. to 5.3.009.
And lost all USB slots with installed images, they are all gone.
3 Images in eMMC still works fine.
Today was a new update in 5.3.009. but VU+Ultimo4K still cannot create new slots with red button.
I hope one of future updates will fix it.
 
klofer said:
Few days ago I made mistake and update OBH 5.3.001. to 5.3.009.
And lost all USB slots with installed images, they are all gone.
3 Images in eMMC still works fine.
Today was a new update in 5.3.009. but VU+Ultimo4K still cannot create new slots with red button.
I hope one of future updates will fix it.
Click to expand...
I just tested this on ultimo4k, it adds extra slots no problem.
 
You must log in or register to reply here.
Back
Top