gorski

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

2 posts in this topic

http://www.mysatbox.tv/2013/10/manual-prismcube-ruby-how-to-recover.html

http://www.prismcube-community.net/board/threads/how-to-recover-prismcube-ruby-after-a-failed-flash.379/

http://www.world-satellite.net/104482-how-recover-prismcube-ruby-after-failed-flash.html

http://www.sat4fun.co.uk/showthread.php?149258-How-to-Recover-PrismCube-Ruby-after-a-failed-flash

Quote

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

how_to_logo.webp
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:
 
IMG_0844.JPG
 
 
- 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 (http://update.prismcube.com/Ruby/) and unzip into a temporary folder
 
                                                download.png
 
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
 
IMG_0842.JPG
 
 
- 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):
 
 
ponticello.JPG
 
 
- 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:
 
1_start_tera_term.png
 
 
- 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:
 
2_tera_term_main_window.png
 
 
- now it's time to setup serial port speed: click on Setup -> Serial Port and the corresponding setup panel appear:
 
3_serial_port_speed_setup.png
 
Select into "Baud Rate" the value 115200 and confirm with OK.
 
- Download from http://update.prismcube.com/Ruby/ 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:
 
1.png
 
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 ...
 
2.png
 
- Now there is more info on the console screen:
 
3.png
 
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 ...
 
4.png
 
- after uploading U-Boot, the console screen changes and the box will start to AUTOMATICALLY flash the Emergency Image:
 
5.png
 
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.

 

Share this post


Link to post
Share on other sites

Thanx to Bogdan:

Quote
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.JPG
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 ]
2.PNG
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.
8.JPG

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
3.JPG
2.1.1 } The only way to prevent this is to enable the see hidden folders in the xbmc menu option
4.JPG
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 "
5.JPG
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
6.JPG
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
7.JPG
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
8.JPG

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.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now