VU+ 4K MULTIBOOT TUTORIAL [4 SLOTS PARTITION] ENGLISH VERSION

Antworten
esuo2
Registrierte Benutzer
Registrierte Benutzer
Beiträge: 1
Registriert: Sa 7. Mai 2022, 15:35
Hat sich bedankt: 3 Mal
Danksagung erhalten: 4 Mal

VU+ 4K MULTIBOOT TUTORIAL [4 SLOTS PARTITION] ENGLISH VERSION

#1

Beitrag von esuo2 »

Table of Contents
1.0 INTRODUCTION
2.0 MULTIBOOT
2.1 Hardware Multiboot
2.2 Openmultiboot
3.0 THE FILE STRUCTURE
3.1 Vu+ Standard Image Structure
3.2 BPanther Neutrino image structure
3.2.1 Neutrino image unpack
3.3 Vu+ Original Image File Format Explained
3.4 Bpanther Neutrino Image File Format Explained
4.0 THE INSTALLATION
5.0 BOOTING FOR THE FIRST TIME
5.1 Booting from VTi image
6.0 UPDATING ANY OF THE IMAGES (after installing four images for the first time)
7.0 GOING BACK TO THE SINGLE BOOT
8.0 ATTACHED FILES


1.0 INTRODUCTION
The VU+ receivers come with a single partition, unlike their hisilicon counterparts, with four (4) hardware partition slots. Until now, the only way to install multiple images on VU+ is to use third-party software for multiboot like NeoBoot, OpenMultiboot, NFR4XBoot and OPDBoot MultiBoot plugins, etc. There is also the phobia of the bootloader being destroyed and the box not being able to boot. That is not possible; again, whether it is possible to go back to the single boot of VU+, which will also be explained in subsequent chapters.
Additionally, online updates of enigma in this multiboot environment are always critical, and one cannot update from example, openATV 6.4 to 7.1

2.0 MULTIBOOT
2.1 Hardware Multiboot
There is no plugin involved in this. It is when a receiver's flash memory has been partitioned (as well as external memory on some images). The bootloader permits the selection of the boot partition. There is no mingling of kernels and the like. Not all receivers possess this capability.
Examples are the Gigablue Quad 4K, Zgemma H9, Octagon Sf8008, and Xtrend ET8500 receivers. On most images, the image selection is located in the restart menu (Abu Baniaz).

2.2 Openmultiboot
A piece of software that can be added to all receivers. The internal flash has an image put on it. The additional images are set on the storage device. The base image is partially loaded, and then you choose and load the image from the storage device. Most of the time, OpenPLI images on flash memory don't work well with this method (Abu Baniaz).

3.0 THE FILE STRUCTURE
Firstly, the multiboot in vu+ receivers is possible by installing BPanther Neutrino image, which allows you to install four different images in 4 slots, so let us begin;

1. let's compare the files of the standard VU+ image and BPanther neutrino image

3.1 Vu+ Standard Image Structure
table 1.PNG
3.2 BPanther Neutrino image structure
3.2.1 Neutrino image unpack
table 2c.PNG
All *.md5 files are not needed for the USB device, they are only for checking the files if flashing fails. Bpanther has added an essential file after rev20040 Neutrino image of the VU4K images. This is the startup.update file and a new version of the initrd_auto.bin file which makes it possible to rebuild a damaged STARTUP area. The STARTUP area is repaired by formatting and rebuilding the STARTUP files. Nothing else is done; all images remain as they are. Furthermore, you can also specify a start partition with the startup.update file. Quite helpful if a partition doesn't start, but you don't want to flash it completely immediately because you still need some of it or want to repair it manually using a different image. Or when E2 attempts a kernel update and thus corrupts the STARTUP area, which used to be the kernel area.
To switch to a particular slot, enter a number in the file (1, 2, 3 or 4), and the system will change to the specified partition instead of the first when you restart the box. Otherwise, the file can also be empty, i.e. a 0-byte dummy.

3.3 Vu+ Original Image File Format Explained
force.update
This is the file that forces the update, ONLY for VU+ ZERO 4K and VU+ UNO 4K, because they have no POWER button.
imageversion
This file contains the version of the image
initrd_auto.bin
This is the loader for flash or update. This is a very important file, it is either the one of the desired VU+ image or that from Bpanther image for "MultiBoot"
kernel_auto.bin
This is the kernel file, when creating a multiboot image, its just a dummy that aught to be present.
mkpart.update
This is the dummy for creating the partitions
rootfs.tar.bz2
this is the file that contains your image files, either from VU+ image or even from backup.
splash_auto.bin
This is the splash logo file, Bpanther has his own splash logo, but I prefer to use the original one for VU+ images, you change as you like
reboot.update
this is an optional file for other VU+ models, which auto reboots the box after update, it is not for VU+ ZERO 4K and VU+ UNO 4K


3.4 Bpanther Neutrino Image File Format Explained
force.update
This is the file that forces the update, ONLY for VU+ ZERO 4K and VU+ UNO 4K, because they have no POWER button.
imageversion
This file contains the version of the image
initrd_auto.bin
This is the loader for flash or update. This is a very important file. It is either one of the desired VU+ image or that from Bpanther image for "MultiBoot"
kernel_auto.bin
This is the kernel file; when creating a multiboot image, it is just a dummy that ought to be present. The kernel file has to be the same for all four images, so kindly leave it as it is. Further, because it is a multiboot kernel. Normal kernels do not find the partition because it is set incorrectly and permanently.
mkpart.update
This is the dummy for creating the partitions
rootfs.tar.bz2
This is the file that contains your image files, either from VU+ image or even from backup
splash_auto.bin
This is the splash logo file, Bpanther has his splash logo, but I prefer to use the original one for VU+ images; you change it as you like
reboot.update
this is an optional file for other VU+ models, which auto reboots the box after update, it is not for VU+ ZERO 4K and VU+ UNO 4K


rootfs1.tar.bz2 Image slot 1
rootfs2.tar.bz2 Image slot 2
rootfs3.tar.bz2 Image slot 3
rootfs4.tar.bz2 Image slot 4

The file structure is the same as that of VU+ image, as explained above. The MD5 files are just a checksum for the files and can be deleted or ignored.

However, very important to create the four partitions for your VU+; you need to install all four partitions at once; then you can change any of the desired slots after you have the four images in internal storage; otherwise, the box won't start, THIS IS A MUST. So it is important to replace rootfs2.tar.bz2, rootfs3.tar.bz2, rootfs4.tar.bz2 with your desired image. rootfs1.tar.bz2 is Bpanthers neutrino image. It is preferable to use the Bpanthers image in slot 1 [rootfs1] to create the perfect four slots. After, you can change to whatever image you prefer.
After installing all four slots, I changed slot 1 to VTi and slot 2 to Sat Dream Greek image (SDG), slot 3 to openATV 6.4, and slot 4 to openATV 7.1.

4.0 THE INSTALLATION
You can download Neutrino images from here >> Neutrino - v3.xx/4.xx - Download und Changelog
Copy to a FAT32 formatted USB stick, preferably 4gig or 8gig flash. I would also advise a flash drive with a flashing light so you know what's going on during the process of flashing
The flashing process is the same as you flash any VU+ box. In my case, I use Zero 4K after inserting the flash drive and putting on the box from the back;
The flash drive begins flashing: Stick is being read, and the first step is initrd_auto.bin is loaded.
1st flash afterwards: boot logo is flashed, thereafter, 2nd to 9th flash with a pause in between: kernel and root are being flashed (4x). So a maximum of 10x flashes on the stick with pauses, and everything should be ready.
It should not and must not flash constantly. file is read = flashing, file is flashed = no flashing on the stick

5.0 BOOTING FOR THE FIRST TIME
After you boot for the first time, the box boots into BPanther neutrino image, so you need to go to the boot menu to change to other boot images. The new images already recognise the boot partitions except for VTi, which is a problem. You need to install the multiboot plugin, VTi needs the old version 1.0.4 of the simple Stb-Startup plugin not as .ipk, but you need to unpack the .ipk and send the file to /usr/lib/enigma2/python/extensions/plugin/ and restart the box. Then you can move into other images. You also need to add the following lines in /etc/fstab:

VU+ UNO 4K / VU+ UNO 4K SE / VU+ ULTIMO 4K / VU+ SOLO 4K
/dev/mmcblk0p1 /boot auto defaults 1 1

VU+ ZERO 4K
/dev/mmcblk0p4 /boot auto defaults 1 1

VU+ DUO 4K / VU+ DUO 4K SE
/dev/mmcblk0p6 /boot auto defaults 1 1

Again, having VTi among the image slots will cause the other slots to crush when you try switching to other slots. Since VTi uses a "bad" /etc/issue, this will otherwise lead to a crash when multibooting under OATV 7.x. So you need to delete /etc/issue, and the multiboot works. The file changes after an update, so have to be replaced. Also, this line goes into the /etc/issue
Welcome to VTi \n \l
vti 15.0.0.1 \n \l
Otherwise, your multiboot image version shows us 0.0.0.0

It would be best if you also change the MultiBoot.py file based on OATV 7.x (newer GIT), which allows the multiboot function to work under the menu/reboot function. But the VU+ DUO 4K and VU+ DUO 4K SE need the MultiBoot.py to work properly not like the other models, and if you have also VTi installed (wrong /etc/issue).
1.jpg
2.jpg
5.1 Booting from VTi image
To boot from VTi image for the first time, it is assumed the enigma2 startup plugin .ipk has been unpacked and sent to the plugin folder; after reboot, the plugin appears in the plugin list. To switch to another image, you have to select the desired image slot, go to Menu, restart and after restarting, you will end up in the desired slot.
3.jpg
4.jpg
5.jpg
6.jpg
6.0 UPDATING ANY OF THE IMAGES (after installing four images for the first time)
To update any of the images after installing all four images at once is very simple. You must take all the files from Bpanther image and only retain the rootfs file you want to install.
For example, the Bpanther image comes with the following file's
force.update
image version
initrd_auto.bin
initrd_auto.bin.md5
kernel_auto.bin
kernel1_auto.bin
kernel1_auto.bin.md5
kernel2_auto.bin
kernel2_auto.bin.md5
kernel3_auto.bin
kerne3_auto.bin.md5
kernel4_auto.bin
kerne4_auto.bin.md5
mkpart.update
rootfs.tar.bz2
rootfs1.tar.bz2
rootfs2.tar.bz2
rootfs3.tar.bz2
rootfs4.tar.bz2
rootfs.tar.bz2.md5
splash_auto.bin
splash_auto.bin.md5
root.update

so let us say we would like to update image in slot 3. We delete rootfs1.tar.bz2, rootfs2.tar.bz2, rootfs4.tar.bz2 and leave only rootfs3.tar.bz2, but rootfs3.tar.bz2 should be the new image we want to install but renamed rootfs3.tar.bz2. Also, kernel3_auto.bin must be present among the files.

7.0 GOING BACK TO THE SINGLE BOOT
This is very simple, take all the files from a VU+ image, and replace only one file. Yes, one file, the initrd_auto.bin from neutrino image.

8.0 ATTACHED FILES
ENIGMA2-STB-STARTUP_1.04-20200904_ALL.IPK >>
enigma2-stb-startup_1.04-20200904_all.ipk
MULTIBOOT.ZIP >>
MultiBoot.zip
Du hast keine ausreichende Berechtigung, um die Dateianhänge dieses Beitrags anzusehen.
Folgende Benutzer bedankten sich beim Autor esuo2 für den Beitrag (Insgesamt 4):
fritz (Do 8. Dez 2022, 15:28) • thc09 (Do 8. Dez 2022, 19:35) • BPanther (Do 8. Dez 2022, 21:22) • jakub969 (Mi 17. Mai 2023, 20:00)
Bewertung: 30.77%
Antworten

Zurück zu „Allgemeines/Anleitungen/FAQ“