Thanks Thanks:  2
Ergebnis 1 bis 2 von 2
  1. #1
    Senior Mitglied Avatar von gorski
    Registriert seit
    07.05.2013
    Beiträge
    101
    Total Downloaded
    393,8 KB
    Total Downloaded
    393,8 KB
    ReceiverDankeAktivitäten

    How to recover PrismCube Ruby after a failed flash...

    Manual Prismcube Ruby: How To Recover PrismCube Ruby after a failed flash

    mysatbox.tv


    How To Recover PrismCube Ruby after a failed flash | PrismCube Community

    Forum Gateway - Powered by DnP Firewall

    How to Recover PrismCube Ruby after a failed flash

    Manual Prismcube Ruby: How To Recover PrismCube Ruby after a failed flash

    October 26, 2013 Manual Prismcube Ruby
    How To Recover PrismCube Ruby after a failed flash

    With this how to you can recover your PrismCube Ruby box if the flash process of an Image is corrupted and the fan is on and the led is red.


    First of all, you should get ready the items you will need to make a recovery:
    - a jumper like the one in the the following photo:




    - a null modem cable (9 PIN) to connect your PC and PrismCube Ruby and a USB-to-serial converter if your PC doesn't have a serial port
    - terminal software: Tera Term (attached in this thread)
    - necessary loaders and files (attached in this thread)


    Preliminary Step: get all the necessary software and files:

    - download Tera Term from this thread and install it on Windows PC: you should unzip it and it's ready to be used
    - download UART Loader (uldr.bin.zip) and unzip it into a temporary folder
    - download U-Boot (u-boot.zip) and unzip it into a temporary folder
    - download LATEST Emergency Update from official Marusys server (404 Not Found) and unzip into a temporary folder



    First step: open the box

    - Disconnect the power supply from the box
    - Open the box with care and remove the cover. You should see the mainboard






    - locate the jumper JP9 (UART_BOOT) and insert the jumper on the pins. Here is the photo of the mainboard with the JP9 located into a green circle (thanks to Paolino for the photo):







    - connect your null modem cable between the box and the PC

    Second step: use Tera Term
    - open Tera Term and you will see the "Tera Term New connection" panel:



    - Put "Serial" and select the COM port you are used to connect the null modem cable and press OK
    - The Tera Term main program window appears:




    - now it's time to setup serial port speed: click on Setup -> Serial Port and the corresponding setup panel appear:




    Select into "Baud Rate" the value 115200 and confirm with OK.

    - Download from 404 Not Found the LATEST official Emergency Update image, unzip it and place the "update_ruby" folder into a USB pendrive FAT32 formatted
    - Connect the USB stick on your box
    - Connect the power cable to your box: you will see something appear on the Tera Term window:




    You can see the "C" letters continue to be printed on the console screen: it's a very good sign, and means that the box is waiting for something.

    - Now select File -> Transfer -> YMODEM -> Send and select uldr.bin.uartboot_img extracted from uldr.bin.zip
    This will transfer the file to your box ...




    - Now there is more info on the console screen:




    Now the box it's waiting for U-Boot file to proceed.

    - AGAIN select File -> Transfer -> YMODEM -> Send and select u-boot.bin extracted from u-boot.zip
    This will transfer the file to your box ...




    - after uploading U-Boot, the console screen changes and the box will start to AUTOMATICALLY flash the Emergency Image:




    TAKE CARE ON THE LINE "scanning bus for storage devices..." because not all USB disks are recognised as valid and in this line it will be reported how many USB stick are detected and automatically used. If you see something different than "1 Storage Device(s) found" you MUST repeat all the steps above with another USB stick.

    The box now continues it's internal operations as if you had flashed it the usual way with the Emergency Update.
    At the end of this step, the display shows the usual "Remove USB".

    Now power off the box and remove the jumper on JP9.

    Now you can power on your box as usual and refit the cover, after you have checked that the box is working correctly.

  2. Thanks rantanplan bedankten sich
    •   Alt Advertising

       

  3. #2
    Senior Mitglied Avatar von gorski
    Registriert seit
    07.05.2013
    Beiträge
    101
    Themenstarter
    Total Downloaded
    393,8 KB
    Total Downloaded
    393,8 KB
    ReceiverDankeAktivitäten
    Thanx to Bogdan:

    HowTo fix your box when your Prismcube is in a reboot loop.

    First you need to see where your addon or skin was installed that caused the problem.

    1} If it was installed in box memory

    1.1} First you need to find the folder with addons, plugins, skins. It is in "/usr/share/xbmc/addons/*.* "

    1.1.1} In this folder you will see your files, now please find the addon or skin that created the problem [metadata.tvdb.com ] and skin [ skin.droid ]

    1.1.2} Now delete this file and reboot your box (Power off)
    1.1.3} If you deleted the correct files, your box will now boot because xbmc creates a new list of available addons and skins.


    2} If was installed on hdd

    2.1} Now this is a bigger problem because if the skin or addon was installed on the hdd you have no access to the folder because it is hidden

    2.1.1 } The only way to prevent this is to enable the see hidden folders in the xbmc menu option

    once this option is enabled, a normal ftp program will see the folders.
    2.1.2} But if this option is disable you must use Filezilla . You can download from
    Code:
    https://filezilla-project.org/
    2.2.1} Now you need to setup this program, setup IP your box; user [ root ], password [ leave empty ] and port [21] . You must enable "Force showing hidden files "

    2.2.2} Next go to "/mnt/hdd0/program/.xbmc/addons" because in this folder you will find the skin that is causing the problems

    2.2.3} When you find the skin [ in this example problem skin is called neon] or addon that caused the problem and delete it

    2.2.4} Now reboot box (Power Off) if after rebooting you still see the old skin name on your menu change to standard Confluence skin


    3} Now you are better off installing your image again from scratch, as this will give you a fresh image and everything will work as normal again.

    All this changes are you doing on your own risk.
    Please first backup your file and made careful changes in files.


    BIG Thanks EVO for coreckt my english.

  4. Thanks rantanplan bedankten sich

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Diese Website benutzt Cookies
Wir benutzen Cookies um Sitzungsinformationen zu speichern. Dies erleichtert es uns z.B. Dich an Deine Login zu erinnern, Einstellungen der Webseite zu speichern, Inhalte und Werbung zu personalisieren, Social Media Funktionen anzubieten und unser Datenaufkommen zu analysieren. Wir teilen diese Informationen ebenfalls mit unseren Social Media-, Werbe- und Analysepartnern.
     
Alle Zeitangaben in WEZ +1. Es ist jetzt 20:16 Uhr.
Powered by vBulletin® Version 4.2.3 (Deutsch)
Copyright ©2017 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,56%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com