View Full Version : How to flash your GiaBlue HD800 QUAD?
Hello,
As per some devices who have special requirement regarding the order to upgrade or flash here the procedure is pretty simple.
1/ Download the latest Vix Image from this thread: http://www.world-of-satellite.com/forumdisplay.php?361-GiGaBlue-QUAD-Images
2/ Once you have download the usb.zip file, you need to copy the directory into a USB key (better formatted with FAT32)
3/ Then you shutdown your GigaBlue
4/ You plug your USB key
5/ And you boot your GigaBlue box
6/ then you should have a menu asking you to confirm that you want to flash your box.
As some Vu+ box you don't necessary need to upgrade your FGPA before upgrading the box image.
Of course you may need to upgrade the FGPA but there shouldn't be any damage not to do when flashing.
I hope it helps. Please add your comments if I need to add some notes on this "How To"
Thanks
XabiX
--------------------------------------------------------------------------------------------------------------------
To install a CAM, you can follow this thread: http://www.world-of-satellite.com/showthread.php?8704-How-to-Install-CCcam-MGCamd-amp-other-softcam-s-on-ALL-ViX-supported-Enigma-2-Receivers
To install picons, you can follow this thread: http://www.world-of-satellite.com/showthread.php?8712-How-to-setup-picons-onto-usb-stick-ViX
For LCD picons, you can follow this thread: http://www.world-of-satellite.com/showthread.php?22266-LCD-Picons-for-Gigablue-Quad
2/ Once you have download the usb.zip file, you need to copy the directory into a USB key
Might be a good idea to add "unzip" or "extract" ;) and put the gigablue directory to the root of the USB key.
Its unbelievable the amount of people who would try and literally copy the zipped file to the USB key and expect it to work while still in the compressed format :thumbsup:
:thumbsup:
i can't edit my post anymore but hopefully people get to read the 2nd post :D
When I unplug the box for 30s and boot (with the USB in front and the gigablue directory on it FAT32) I don't see any message on the screen and I boot directly under openMIIPS.
Did I miss something?
thanks
I don't know, I tried also with the rear USB port but no success.
I found a better post explaining the flash process.
http://www.world-of-satellite.com/showthread.php?22470-How-to-USB-flash-Upgrade-GiGaBlue-HD-800-UE-purchased-after-31-08-12-from-WoS&highlight=USB+reboot
I didn't find any bootloader for the quad so I directly try to flash.
I see the USB key mounted when it boots but I can't write on it so maybe the key is not supported. I tried to USB keys so far.
Jan 1 01:00:26 gbquad user.info kernel: usb 6-1: not running at top speed; connect to a high speed hub
Jan 1 01:00:26 gbquad user.info kernel: scsi2 : usb-storage 6-1:1.0
Jan 1 01:00:26 gbquad user.notice kernel: scsi 2:0:0:0: Direct-Access Generic USB Flash Drive 1.00 PQ: 0 ANSI: 2
Jan 1 01:00:26 gbquad user.notice kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
Jan 1 01:00:26 gbquad user.notice kernel: sd 2:0:0:0: [sda] 2086144 512-byte logical blocks: (1.06 GB/1018 MiB)
Jan 1 01:00:26 gbquad user.notice kernel: sd 2:0:0:0: [sda] Write Protect is off
Jan 1 01:00:26 gbquad user.debug kernel: sd 2:0:0:0: [sda] Mode Sense: 03 00 00 00
Jan 1 01:00:26 gbquad user.err kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Jan 1 01:00:26 gbquad user.err kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Jan 1 01:00:26 gbquad user.info kernel: sda: sda1
Jan 1 01:00:26 gbquad user.err kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Jan 1 01:00:26 gbquad user.notice kernel: sd 2:0:0:0: [sda] Attached SCSI removable disk
Jan 1 01:00:26 gbquad user.notice kernel: UBI: max. sequence number: 500
Jan 1 01:00:26 gbquad user.notice kernel: UBI: attached mtd0 to ubi0
Jan 1 01:00:26 gbquad user.notice kernel: UBI: MTD device name: "rootfs"
Jan 1 01:00:26 gbquad user.notice kernel: UBI: MTD device size: 504 MiB
Jan 1 01:00:26 gbquad user.notice kernel: UBI: number of good PEBs: 4022
Jan 1 01:00:26 gbquad user.notice kernel: UBI: number of bad PEBs: 10
Jan 1 01:00:26 gbquad user.notice kernel: UBI: number of corrupted PEBs: 0
Jan 1 01:00:26 gbquad user.notice kernel: UBI: max. allowed volumes: 128
Jan 1 01:00:26 gbquad user.notice kernel: UBI: wear-leveling threshold: 4096
Jan 1 01:00:26 gbquad user.notice kernel: UBI: number of internal volumes: 1
Jan 1 01:00:26 gbquad user.notice kernel: UBI: number of user volumes: 1
Jan 1 01:00:26 gbquad user.notice kernel: UBI: available PEBs: 0
Jan 1 01:00:26 gbquad user.notice kernel: UBI: total number of reserved PEBs: 4022
Jan 1 01:00:26 gbquad user.notice kernel: UBI: number of PEBs reserved for bad PEB handling: 40
Jan 1 01:00:26 gbquad user.notice kernel: UBI: max/mean erase counter: 2/0
Jan 1 01:00:26 gbquad user.notice kernel: UBI: image sequence number: 1363274720
Jan 1 01:00:26 gbquad user.notice kernel: UBI: background thread "ubi_bgt0d" started, PID 53
Jan 1 01:00:26 gbquad user.err kernel: UBI error: ubi_init: cannot attach mtd0
Jan 1 01:00:26 gbquad user.notice kernel: UBIFS: mounted UBI device 0, volume 0, name "rootfs"
Jan 1 01:00:26 gbquad user.notice kernel: UBIFS: file system size: 503713792 bytes (491908 KiB, 480 MiB, 3967 LEBs)
Jan 1 01:00:26 gbquad user.notice kernel: UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
Jan 1 01:00:26 gbquad user.notice kernel: UBIFS: media format: w4/r0 (latest is w4/r0)
Jan 1 01:00:26 gbquad user.notice kernel: UBIFS: default compressor: lzo
Jan 1 01:00:26 gbquad user.notice kernel: UBIFS: reserved for root: 0 bytes (0 KiB)
and
root@gbquad:/media/hdd# mv /tmp/easy-oscam.tgz .
mv: write error: No space left on device
thanks for any help
I solved the issu !!
I found out that the fstab was wrong so I remove the hdd line
root@gbquad:~# more /etc/fstab
rootfs / auto defaults 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
usbdevfs /proc/bus/usb usbdevfs noauto 0 0
tmpfs /var/volatile tmpfs defaults 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
UUID=00000000 /media/hdd auto defaults 1 1
root@gbquad:~# vi /etc/fstab
rootfs / auto defaults 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
usbdevfs /proc/bus/usb usbdevfs noauto 0 0
tmpfs /var/volatile tmpfs defaults 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
and now it works OK.
thanks
I'm glad to see you resolved your issue, and apologize if it seemed as if you received no or little help in doing so. As this box is so new very few users have one and because of that we cant offer the usual high level of hands on support that we would with some of the other receivers we support.
Thanks Pheonix, no worries we are all here to get up to speed :)
Actually it worked but it was with this package gigablue-quad-cfe-20120917
Anytime I try with the openvix one (openvix-3.0.394-gbquad_usb), I don't have any LCD screen menu asking for pressing OK as a new image has been found. So I still have the issue.
What is strange is that it looks like I am the only one with this issue.
(Besides I don't think that editing any file on the flash like fstab etc.. would change anything at the early boot level when the box looks for an image on a USB disk?)
I feel better now that I see that I am not the only one with this issue:
http://gigablue-support.com/index.php?page=Thread&postID=28954#post28954
Issue SOLVED, and I am now running OpenVIX image.
The issue was the USB key. Maybe too new and it looks like was recognized as sd (hd) instead of a usb stick.
On putting on 2 different Images last few days, the order was : gigablue folder with the quad folder inside that contain the files, onto a Fat 32 formatted suitable USB stick > Switch off box at the back and insert USB > Wait for a screen on the receiver to say whether you want to flash,
you have only a few seconds to decide, and press OK button on the receiver only. > The files should then start loading.
If you do not see the flash screen, and just reboots, it is usually a USB that will not work with this box.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.