no boot after VTI V2.0 flash

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Original von scorillo
      i have tried this new multiboot 6......last ting flashed was original 5.01..no meoboot or barryallen

      You don't need to sent your box back, you can fix it yourself.
      I do read you tried the multiboot_cfe v6.
      That's why your box isn't booting.
      If you still got a telenet connection, then start at point 4.

      You must do this:

      1) boot your VU+ in the bootconsole (with serial cable, press Ctrl+c to stop the bootsequence)
      2) copy this command to the console and press enter:

      Quellcode

      1. boot -z -elf flash0.kernel: 'rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3`

      3) your box should boot from flash
      4) open a telnet session and enter this command:

      Quellcode

      1. flash_eraseall /dev/mtd5

      5) reboot your box with this command:

      Quellcode

      1. reboot -f


      That's all. I hope you get your box back running.

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von Black_64 ()

    • Original von Black_64
      Original von scorillo
      i have tried this new multiboot 6......last ting flashed was original 5.01..no meoboot or barryallen

      You don't need to sent your box back, you can fix it yourself.
      I do read you tried the multiboot_cfe v6.
      That's why your box isn't booting.
      If you still got a telenet connection, then start at point 4.

      You must do this:

      1) boot your VU+ in the bootconsole (with serial cable, press Ctrl+c to stop the bootsequence)
      2) copy this command to the console and press enter:

      Quellcode

      1. boot -z -elf flash0.kernel: 'rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3`

      3) you box should boot from flash
      4) open a telnet session and enter this command:

      Quellcode

      1. flash_eraseall /dev/mtd5

      5) reboot your box with this command:

      Quellcode

      1. reboot -f


      That's all. I hope you get your box back running.


      thanks for helping...i start now your solution but i dont know how to start vu+ on bootconsole..
    • You must use a nullmodem cable on comport. Then start hyperterm or putty select comport. Settings are 115200,8,n,1 i guess. Then youll se output like in telnet.
      Pustekuchen ist keine Blume.

      Vu+ DUO - 500GB HDD (Samsung EcoGreen F2) - Vu+ DUO - 500GB HDD (Samsung EcoGreen F3)
      Vu+ SOLO - 500GB HDD (WD Mybook Essential 2,5") - Samsung USB DVD Brenner
      DM800 - Abcom IPBox 910 - Opticum HD TS 9600
      Zotac Mag Mini als Medialplayer - Buffalo Drive Station Pro als NAS
    • The solution was part of black64, not my part ;)
      Pustekuchen ist keine Blume.

      Vu+ DUO - 500GB HDD (Samsung EcoGreen F2) - Vu+ DUO - 500GB HDD (Samsung EcoGreen F3)
      Vu+ SOLO - 500GB HDD (WD Mybook Essential 2,5") - Samsung USB DVD Brenner
      DM800 - Abcom IPBox 910 - Opticum HD TS 9600
      Zotac Mag Mini als Medialplayer - Buffalo Drive Station Pro als NAS
    • We had last week a betatester with the same problem.
      Then (i think) the author of Multiboot_cfe did told how to recover.

      So i only posted this info here to help.
      Nice to see your box is back running.

      Don't forget the "flash_eraseall /dev/mtd5" in telnet when your box is booted.
      Otherwise next reboot it will again not boot.
    • Black_64

      thanks friend, I have all afternoon thinking it was the giant image.

      but the error is this and it is solved, my VU is alive thanks to you, a big hug for your help.

      others did not want to listen, when the error was obvious and was in front of your eyes.

      thank you very much, your solution works perfectly, I am eternally grateful.