Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: ]NeoBoot by gutosie 6.41

  1. #1
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default ]NeoBoot by gutosie 6.41

    NeoBoot by gutosie 6.41




    972/5000
    Supported tuners: All VuPlus models - clones too, Octagon SF4008, MiracleBox Mini, Formuler (Tests - DM900)

    NeoBoot is not yet fully functional in the DM900 and OctagonSF4008 models - the improvement work is under way ...

    The first neoboot installation

    Run the following command in the supported tuner terminal:

    opkg update

    opkg install curl

    curl -kLs [Only Registered Users Can See Links. Click Here To Register]

    WARNING!!! Redistribution of the program version and making modifications IS PERMITTED subject to the observance of this copyright notice.

    The author DOES NOT bear ANY responsibility for the consequences of using this program and for the use of the information contained herein.

    You carry out the installation and modifications at your own risk !!! Before installing or updating Neoboot read carefully all information contained here and in the plugin. !

    Thank you to all my colleagues supporting the neoboot project.

    I also thank my colleagues supporting the project.

    gutosie




    :download:

    [Only Registered Users Can See Links. Click Here To Register]

  2. Thanks coco23 thanked for this post
    Likes kraibi liked this post
  3. #2
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    NeoBoot installation description by gutosie
    I decided to describe the correct process of installing the neoboot program on STB tuners

    ATTENTION !!! The description applies to the neo installation in image OpenPli, because this image works best with the NeoBoot (a) project

    1. We install the openpli system in our tuner
    2. Plug the USB stick into the USB port
    3. We do a complete reboot of the tuner
    4. Go from the remote control to Menu> Settings> System> Advanced Settings> Hard Disk> Initialize, here I select our disk by pressing OK and Initialize, I am waiting for it to finish formatting.
    5. We do a complete reboot of the tuner.
    6. We check with the command:
    Code:
    moun
    under which sd * 1 we have our drives, example:
    / dev / sda1 on / media / hdd type ext4
    / dev / sdb1 on / media / usb type ext4
    the mount command returns us from:
    sda1 is mounted under media / hdd and this is our HDD drive
    sdb1 is mounted under media / usb and this is our PENDRIVE drive
    7. Next, you should give a label for disks, we do it with a command for HDD
    Code:
    tune2fs -L hdd / dev / sda1
    for USB
    Code:
    tune2fs -L usb / dev / sdb1
    Important !!! if, for example, we have only a pendrive and there is no hard disk connected, then it should be given to the pena label hdd so that the pendrive would be recognized by the system as hdd, by the command:
    Code:
     tune2fs -L hdd / dev / sda1
    continue to create the movie directory with the command:
    Code:
    mkdir -p / media / hdd / movie
    we create the movie directory to be able to record

    after these treatments, it is good to give the tuner a deeply awake, by command:
    halt

    Warning!!! we do not do any other activities related to installing devices on our tuner if we want to install a neoboot. It is also important to have attached disks from the very beginning which will be permanently in our stb.

    After waking up the tuner, we go to the NeoBoot installation

    1. We are doing a packet upgrade with the command:
    opkg update
    2. Install the curl package with the command:
    opkg install curl
    3. We install the neoboot project in the system by command:
    curl -kLs [Only Registered Users Can See Links. Click Here To Register]
    The above command will install NeoBoot itself (a) and reboot the system

    4. Menu> NeoBoot and here press on the remote control successively, blue - Device Manager, ok, choose for example the cursor [i] Mount: / media / hdd Mount: / media / usb [/ i] and press green to save
    5. We return EXIT to the neoboot installation on a usb or hdd disk
    [Only Registered Users Can See Links. Click Here To Register]
    6. We choose on which medium we want to have neo and install -OK

    Recommended installation on a pendrive, because in the case if any image does not start up, simply unplug the pen and restart the tuner manually, it should start the system with flash, otherwise we will unscrew the HDD: wesołek:

    That's all
    [Only Registered Users Can See Links. Click Here To Register]
    recommended installation with command !!! because the installation command will give appropriate permissions to files, without this neoboot will not work properly or not at all: jolly:

    if the image does not start in neoboot and we have a telnet or shh (putty) connection then you can try to use the command:

    ln -sf "init.sysvinit" "/ sbin / init"
    echo "Flash"> /media/neoboot/ImageBoot/.neonextboot
    reboot -f
    Całkowite odinstalowanie neoboota z polecenia konsoli
    uruchamiamy image Flash i wydajemy polecenie:

    Code:
    rm -R /usr/lib/enigma2/python/Plugins/Extensions/NeoBoot
    rm -R /media/*/ImageBoot/.Flash
    rm -R /media/*/ImageBoot/.neonextboot
    rm -R /media/*/ImageBoot/.version
    rm -R /sbin/neoinit*
    ln -sfn /sbin/init.sysvinit /sbin/init  
    cp -rf /etc/fstab.org /etc/fstab 
    rm /etc/fstab.org 
    cp -rf /etc/init.d/volatile-media.sh.org /etc/init.d/volatile-media.sh
    rm /etc/init.d/volatile-media.sh.org 
    opkg install volatile-media
    sleep 2
    killall -9 enigma2
    jeśli proces się zatrzyma to klikamy Enter w okienku konsoli, E2 na koniec powinna się zrestartować
    Last edited by ZYGA; 08-01-2018 at 12:35.

  4. #3
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    NeoBoot by gutosie 6.43




    Supported tuners: All VuPlus models - clones too, Octagon SF4008, MiracleBox Mini, Formuler (Tests - DM900)

    NeoBoot is not yet fully functional in the DM900 and OctagonSF4008 models - the improvement work is under way ...

    The first neoboot installation

    Run the following command in the supported tuner terminal:



    Code:
    opkg update
    
    opkg install curl
    Code:
    curl -kLs [Only Registered Users Can See Links.  Click Here To Register]
    WARNING!!! Redistribution of the program version and making modifications IS PERMITTED subject to the observance of this copyright notice.

    The author DOES NOT bear ANY responsibility for the consequences of using this program and for the use of the information contained herein.

    You carry out the installation and modifications at your own risk !!! Before installing or updating Neoboot read carefully all information contained here and in the plugin. !

    Thank you to all my colleagues supporting the neoboot project.

    I also thank my colleagues supporting the project.
    Tłumacz Google dla Firm:Narzędzia dla tłumaczyTłumacz stron



    [Only Registered Users Can See Links. Click Here To Register]


    :download:

    [Only Registered Users Can See Links. Click Here To Register]
    Last edited by ZYGA; 02-01-2018 at 18:37.

  5. #4
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    NeoBoot by gutosie 6.45







    [/center]
    Supported tuners: All VuPlus models - clones too, Octagon SF4008, MiracleBox Mini, Formuler (Tests - DM900)

    NeoBoot is not yet fully functional in the DM900 and OctagonSF4008 models - the improvement work is under way ...

    The first neoboot installation

    Run the following command in the supported tuner terminal:



    Code:
    opkg update
    
    opkg install curl
    Code:
    curl -kLs [Only Registered Users Can See Links.  Click Here To Register]
    WARNING!!! Redistribution of the program version and making modifications IS PERMITTED subject to the observance of this copyright notice.

    The author DOES NOT bear ANY responsibility for the consequences of using this program and for the use of the information contained herein.

    You carry out the installation and modifications at your own risk !!! Before installing or updating Neoboot read carefully all information contained here and in the plugin. !

    Thank you to all my colleagues supporting the neoboot project.

    I also thank my colleagues supporting the project.
    WARNING!!!
    if the image does not start in neoboot and we have a telnet or shh (putty) connection then you can try to use the command:


    Code:
    ln -sf "init.sysvinit" "/ sbin / init"
    echo "Flash"> /media/neoboot/ImageBoot/.neonextboot
    reboot -f
    Neoboot in the current version is intended only for the image of OpenPLi 6.1 in flash.

    Please do not combine and do not put Neoboot on other image in flash, including even lower editions of OpenPLi.


    gutosie
    [Only Registered Users Can See Links. Click Here To Register]

    :download:

    [Only Registered Users Can See Links. Click Here To Register]
    Last edited by ZYGA; 05-01-2018 at 17:50.

  6. #5
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    NeoBoot 6.50 by gutosie






    [quote name='gutosie']
    WARNING!!! Redistribution of the program version and making modifications IS PERMITTED subject to the observance of this copyright notice.

    The author DOES NOT bear ANY responsibility for the consequences of using this program and for the use of the information contained herein.

    You carry out the installation and modifications at your own risk !!! Before installing or updating Neoboot read carefully all information contained here and in the plugin. !

    Thank you to all my colleagues supporting the neoboot project.

    I also thank my colleagues supporting the project.
    WARNING!!!
    if the image does not start in neoboot and we have a telnet or shh (putty) connection then you can try to use the command:


    [code]ln -sf "init.sysvinit" "/ sbin / init"
    echo "Flash"> /media/neoboot/ImageBoot/.neonextboot
    rebNeoboot in the current version is intended only for the image of OpenPLi 6.1 in flash.

    Please do not combine and do not put Neoboot on other image in flash, including even lower editions of OpenPLi.
    gutosie
    [Only Registered Users Can See Links. Click Here To Register]
    :download:

    [attachment=11655:NeoBoot-BY-gutosie_20180102-iNB.sh-packed.Lucek_all.ipk.zip]

    temat pod dyskusję :[Only Registered Users Can See Links. Click Here To Register]
    Download [Only Registered Users Can See Links. Click Here To Register]

  7. Thanks kraibi thanked for this post
  8. #6
    Join Date
    May 2012
    Posts
    1
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    good work.how does it differ from openmultiboot?

  9. #7
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    NeoBoot 6.50

    Dołączona grafika [Only Registered Users Can See Links. Click Here To Register]


    Spoiler

    Dołączona grafika [Only Registered Users Can See Links. Click Here To Register]
    Supported tuners: All VuPlus models - clones too, Octagon SF4008, MiracleBox Mini, Formuler (Tests - DM900)

    NeoBoot is not yet fully functional in the DM900 and OctagonSF4008 models - the improvement work is under way ...

    The first neoboot installation

    Run the following command in the supported tuner terminal:

    opkg update

    opkg install curl

    curl -kLs [Only Registered Users Can See Links. Click Here To Register]

    WARNING!!! Redistribution of the program version and making modifications IS PERMITTED subject to the observance of this copyright notice.

    The author DOES NOT bear ANY responsibility for the consequences of using this program and for the use of the information contained herein.

    You carry out the installation and modifications at your own risk !!! Before installing or updating Neoboot read carefully all information contained here and in the plugin. !

    Thank you to all my colleagues supporting the neoboot project.

    I also thank my colleagues supporting the project.

    gutosie
    NeoBoot-6.50 Download [Only Registered Users Can See Links. Click Here To Register]
    you can
    restore by installing

    NeoBoot-6.50-by.gutosie_packed.Lucek_all.ipk Download [Only Registered Users Can See Links. Click Here To Register]

  10. Thanks kraibi thanked for this post
  11. #8
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    VU + Description DJWeed "update in neoboot


    To make the soft with new drivers update in neoboot properly, before launching the given image (being on image in flash), download the latest version of the image file (eg ATV 6.2) which we want to update and replace in our image (in neo) kernel:

    We go to ftp to the catalog with our image installed in neo:

    / Media / USB / ImageBoot

    now we are entering the image that we want to update, for example ATV 6.2 for the Openatv-6.2-vuultimo4k catalog

    you can call it differently, just the name you gave when installing

    Now we are entering the / boot / directory in the image directory you want to run

    we have the zImage.ultimo4k file there, or with any other ending for your box.

    you rename the file zImage.ultimo4k to zImage.ultimo4k.bak

    now you download and copy from the downloaded soft file to the directory where the zImage.ultimo4k file was and now it is already fromImage.ultimo4k. as a file named kernel_auto.bin

    After copying, you change the name of the kernel_auto.bin file to zImage.ultimo4k (or any terminal for the decoder model you have).

    Finally, the attribute 755 should be given for the zImage.ultimo4k file

    After this procedure, we run our image in neo (for example ATV 6.2).

    We are updating the image
    Code:
    opkg update
    opkg upgrade
    and we enjoy the fresh version without having to re-upload the fresh version.

    edit:

    Note that for some image the operation should be "reversed", an example based on OpenSPA 7.2:

    1. We run the image on the old kernel
    2. Update the image from the console
    Code:
    opkg update
    opkg upgrade
    3. We do not run the box again, only with neo we choose to start with flash
    4. Replace the kernel with a new one, as described above
    5. We run the image after the update (on the example I am describing -> OpenSPA)
    6. We are happy with the updated image

    [color = red] Summary [/ color] (it will be topped up until it does not update all 18 images in neo):

    I. By the "basic" way, I updated the following image:
    1. OpenATV 6.2
    2. BlackHole 3.0.5

    II. With the "inverted" method, I updated the following image:
    1. OpenSPA 7.2
    2. OpenATV 6.1
    3. SatdreamGR 5
    4. PurE2 6.2
    5. OpenVIX 5.1
    6. OpenBH 4.1
    7. OpenPlus 2.3.1

    III. The image is updated without having to take any additional action or no online updates found at the time of writing this post:
    1. VTi 13.0.x update to -> 13.0.7
    2. OpenDROID 6.4 -> there is a newer file on the site, but no update is available online
    3. PurE2 6.1 (no update)
    4. POC Hyperion 5.8 (no update)
    5. OpenESI 5.0 (no update)
    6. OpenESI 5.5 (no update)
    7. BlackHole 3.0.4 (no update)
    8. SFTeam 6 (no update)
    9. Openten 0.3 update to -> 1.0

    On the occasion of spring cleaning, the tooth flew to the basket:

    1. PurE2 6.1 (no update)
    2. OpenESI 5.0 (no update)
    3. OpenESI 5.5 (no update)
    4. BlackHole 3.0.4 (no update)
    5. SFTeam 6 (no update)
    Download [Only Registered Users Can See Links. Click Here To Register]


    Pzdr.
    DJWeed
    Last edited by ZYGA; 23-03-2018 at 12:25.

  12. #9
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    NeoBoot by gutosie 6.52







    Wspierane tunery: Wszytkie modele VuPlus - klony też, Octagon SF4008, MiracleBox Mini, Formuler ( Testy- DM900)

    NeoBoot nie działa jeszcze w pełni sprawnie w modelach DM900 i OctagonSF4008 - prace nad ulepszeniem trwają..

    Pierwsza instalacja neoboot-a

    Uruchom poniższą komendę w terminalu wspieranego tunera:

    Code:
    opkg update
    
    opkg install curl
    
    curl -kLs https://raw.githubusercontent.com/gutosie/neoboot/master/iNB.sh|sh
    UWAGA!!! Redystrybucja wersji programu i dokonywania modyfikacji JEST DOZWOLONE, pod warunkiem zachowania niniejszej informacji o prawach autorskich.

    Autor NIE ponosi JAKIEJKOLWIEK odpowiedzialności za skutki użytkowania tego programu oraz za wykorzystanie zawartych tu informacji.

    Instalację i modyfikacje przeprowadzasz na wlasne ryzyko!!! Przed instalacją lub aktualizacją Neoboot przeczytaj uważnie wszystkie informacje zawarte tu i w wtyczce. !

    Dziękuję wszystkim kolegom wpierającym projekt neoboot.

    Dziękuję też kolegom wspierającym projekt.
    Download [Only Registered Users Can See Links. Click Here To Register]
    pozdrawiam gutosie


    :download:


    [Only Registered Users Can See Links. Click Here To Register]

  13. #10
    Join Date
    Aug 2010
    Posts
    15,682
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    72

    Default

    VU+soft with new drivers updated in neoboot correctly, by gutosie Um den Soft mit neuen Treibern in neoboot korrekt zu aktualisieren, laden Sie vor dem Start des gegebenen Images (im Flash-Image) die neueste Version der Image-Datei (zB ATV 6.2), die wir in unserem image (in neo) Kernel aktualisieren und ersetzen wollen:

    Wir gehen zum ftp zum Katalog mit unserem in neo installierten Bild:

    / Medien / USB / ImageBoot

    Jetzt geben wir das Bild ein, das wir aktualisieren möchten, zum Beispiel ATV 6.2 für den Openatv-6.2-vultimo4k-Katalog

    Sie können es anders nennen, nur den Namen, den Sie bei der Installation angegeben haben

    Jetzt betreten wir das Verzeichnis / boot / in dem Image-Verzeichnis, das Sie ausführen möchten

    Wir haben die zImage.ultimo4k-Datei dort oder mit einer anderen Endung für Ihre Box.

    Sie benennen die Datei zImage.ultimo4k in zImage.ultimo4k.bak um

    Jetzt laden Sie und kopieren Sie von der heruntergeladenen Soft-Datei in das Verzeichnis, in dem sich die zImage.ultimo4k-Datei befindet, und jetzt ist es bereits fromImage.ultimo4k.bak-Datei mit dem Namen kernel_auto.bin

    Nach dem Kopieren ändern Sie den Namen der Datei kernel_auto.bin in zImage.ultimo4k (oder ein beliebiges Terminal für das vorhandene Decodermodell).

    Schließlich sollte das Attribut 755 für die Datei zImage.ultimo4k angegeben werden

    Nach diesem Vorgang führen wir unser Image in neo (zum Beispiel ATV 6.2).

    Wir aktualisieren das Bild

    opkg Aktualisierung
    opkg Upgrade

    und wir genießen die neue Version, ohne die neue Version erneut hochladen zu müssen.

    edit:

    Beachten Sie, dass die Operation für einige Bilder "umgekehrt" sein sollte, ein Beispiel, das auf OpenSPA 7.2 basiert:

    1. Wir führen das Image auf dem alten Kernel aus
    2. Aktualisieren Sie das Bild von der Konsole

    opkg Aktualisierung
    opkg Upgrade


    3. Wir starten die Box nicht mehr, nur mit neo beginnen wir mit flash
    4. Ersetzen Sie den Kernel wie oben beschrieben durch einen neuen
    5. Wir führen das Image nach dem Update aus (im Beispiel beschreibe ich -> OpenSPA)
    6. Wir sind mit dem aktualisierten Bild zufrieden

    [color = red] Zusammenfassung [/ color] (es wird so lange aufgefüllt, bis es nicht alle 18 Bilder in neo aktualisiert):

    I. Auf die "grundlegende" Weise habe ich das folgende Bild aktualisiert:
    1. OpenATV 6.2
    2. BlackHole 3.0.5

    II. Mit der "invertierten" Methode habe ich das folgende Bild aktualisiert:
    1. OpenSPA 7.2
    2. OpenATV 6.1
    3. SatdreamGR 5
    4. PurE2 6.2
    5. OpenVIX 5.1
    6. OpenBH 4.1
    7. OpenPlus 2.3.1

    III. Das Bild wird aktualisiert, ohne dass zum Zeitpunkt des Verfassens dieses Posts zusätzliche Aktionen oder keine Online-Updates erforderlich sind:
    1. VTi 13.0.x Update auf -> 13.0.7
    2. OpenDROID 6.4 -> Es gibt eine neuere Datei auf der Website, aber kein Update ist online verfügbar
    3. PurE2 6.1 (kein Update)
    4. POC Hyperion 5.8 (kein Update)
    5. OpenESI 5.0 (kein Update)
    6. OpenESI 5.5 (kein Update)
    7. BlackHole 3.0.4 (kein Update)
    8. SFTeam 6 (kein Update)
    9. Openten 0.3 Update auf -> 1.0

    Bei der Frühjahrsputzung flog der Zahn in den Korb:

    1. PurE2 6.1 (kein Update)
    2. OpenESI 5.0 (kein Update)
    3. OpenESI 5.5 (kein Update)
    4. BlackHole 3.0.4 (kein Update)
    5. SFTeam 6 (kein Update)

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •