• Discussion in the Admin room about nightly images, we dont really need or want these posting for the following reasons.

    1. We all know where to get them.
    2. Never have a change log.
    3. The changes if any are not worthy of anyone upgrading there boxes on a daily basis.
    4. They clutter the forum up.

    Posts will be removed.

    Ferret

hellobox gsky v7

slugworth

Registered
Messages
336
mainboard gd_s2+hd_k3_v1.1 20141223

uses the same remote control as the old coolsat 4000/5000/6000
 

slugworth

Registered
Messages
336
if you google dl_preset.bin you will find a chinese site that has a converter for the bin file to .xls and vice versa.
Since the receiver doesn't store /load the file it may come in handy.Also a commandline merge program to get the file back into a full firmware.
 

Ras Kush

Registered
Messages
7
mainboard gd_s2+hd_k3_v1.1 20141223

uses the same remote control as the old coolsat 4000/5000/6000

Hi Slugworth,
I have a GSKy v.6HD satellite receiver and the motherboard chassis number is exactly the same as you have you've posted above.
GSky v.7HD remote control will work on GSKy v.6HD and vice versa.

Processor & Memory:
NANYA 1538
NT5CB64M16FP-DH

CPU: K3 Dual Core
Flash Memory: 32MB
SDRAM: 1024MB

What is the Processor & Memory chip used in HelloBox GSky v.7HD
:confused: :confused: :confused:
 
Last edited:

Ras Kush

Registered
Messages
7
Hi Slugworth,
I have a GSKy v.6HD satellite receiver and the motherboard chassis number is exactly the same as you have you've posted above.
GSky v.7HD remote control will work on GSKy v.6HD and vice versa.

Processor & Memory:
NANYA 1538
NT5CB64M16FP-DH

CPU: K3 Dual Core
Flash Memory: 32MB
SDRAM: 1024MB

What is the Processor & Memory chip used in HelloBox GSky v.7HD
:confused: :confused: :confused:

Error clarification Flash Memory details as follows:
CPU: K3 Dual Core
Flash Memory: 32MB
SDRAM: 512MB

Although the above satellite receiver specifications are official, i tend to belief they are some what exaggerated !!!
 

slugworth

Registered
Messages
336
There are like 7 or 8 brands that use the same mainboard.
Most just have to be patched to bypass the hardware detection.
I track them down via the rs232 loader.
They use the tcom_upg_rs232 or k3_loader_tool.
Mostly russian models.
Basically anything with k3 in the name.
 

slugworth

Registered
Messages
336
The v7 has a 8Mb flash and the updates are a full 8meg.
If the v6 updates are the same size the firmware must have hardware detection.
 

slugworth

Registered
Messages
336
the v6 has an 8 byte difference in the hardware detect section starting @ hex 0x502c0 if you compare the 80 byte chunks taken from that address.You can mod v7 firmware and play with it.If you kill the receiver you can recover via rs232 loader.
 

satelitindonesia

Registered
Messages
336
the v6 has an 8 byte difference in the hardware detect section starting @ hex 0x502c0 if you compare the 80 byte chunks taken from that address.You can mod v7 firmware and play with it.If you kill the receiver you can recover via rs232 loader.

not only that , chip ID, i have edited but still mode on. :mecry:
 

Ras Kush

Registered
Messages
7
There are like 7 or 8 brands that use the same mainboard.
Most just have to be patched to bypass the hardware detection.
I track them down via the rs232 loader.
They use the tcom_upg_rs232 or k3_loader_tool.
Mostly russian models.
Basically anything with k3 in the name.

Now that you've mentioned it, i pumped the Russian software of Sat-Integral s-1226 HD k3 and to my surprise GSky v.6HD accepted software without any glitches.

Eeprom flash memory was identified without using the tcom_upg_rs232_loader_tool.
 
Last edited:

slugworth

Registered
Messages
336
sat-integral s-1226 has may 16th firmware I am using now.
Autorolls biss.I mod it to load on the v7
 

dl76

Registered
Messages
41
Works great here just scanned in ufc and its biss. Gsky v7 hd.
0721b47f5301c94a6954a1d4af235eac.jpg


Sent from my SM-G900V using Tapatalk
 

Ras Kush

Registered
Messages
7
sat-integral s-1226 has may 16th firmware I am using now.
Autorolls biss.I mod it to load on the v7

I actually downloaded the firmware: k3_single_classical_cstm_gd_20170516.zip

I didn't realise it auto-rolls Biss.

Unfortunately i'm in East Africa where most satellite channels don't use Biss Encryption, its card & sat.box pairing.

 

Ras Kush

Registered
Messages
7
the v6 has an 8 byte difference in the hardware detect section starting @ hex 0x502c0 if you compare the 80 byte chunks taken from that address.You can mod v7 firmware and play with it.If you kill the receiver you can recover via rs232 loader.

I have no knowledge of Software Programming; how do you "mod" software?
:hammer: :hammer: :hammer:
 

slugworth

Registered
Messages
336
I use an old version of hex workshop but for the smaller jobs I use ztree file manager hex edit mode.
Basically a copy/replace of hex byes from your favorite receiver firmware to the target firmware.
V6 firmware will run on the v7 after editing the 8 bytes but the v6 firmware is from jan 2017 so is lagging behind.
 

slugworth

Registered
Messages
336
The auto_burn function still works for the v7 but is never mentioned.A leftover from the old v5 days.
You rename a firmware dump file to auto_burn.fac and put it on the usb stick.When you plug the stick into the receiver it will automatically load that firmware.When the display reaches FFFF remove the stick and cycle power with the switch in the back.Rename the file on usb stick back to dump.bin or whatever or the process will start all over again with the stick inserted.
 
Top