Gigablue Trio UHD - recovery using HiTool

MihaiP

Member
Recovery Gigablue Trio 4K

Problem details:

- defective Gigablue Trio 4K receiver + a functional one!
- the defective one, when powered, went directly into ... UPDT
- @Sosozah brought a serial-jack cable ... functional! but not the remote control!
- I even assumed that we had a blocked "recovery" microswitch
- the serial showed us that Trio starts in Boot ... launches the Kernel and that's it!!!

I concluded that a "smart guy" made an image installation ...outlaw! one that wrote
an exotic Kernel ... I would even say foreign! I turned on the functional receiver to
find out how the system partitions were allocated! and I used the buttons on the
front panel to browse through Enigma2!here Linux/Enigma2 gave me a helping hand
( cat /proc/partitions )

179 1 1024 mmcblk0p1 - fastboot
179 2 1024 mmcblk0p2 - bootargs
179 3 1024 mmcblk0p3 - bootoptions
179 4 3072 mmcblk0p4 - baseparams
179 5 4096 mmcblk0p5 - pqparam
179 6 4096 mmcblk0p6 - logo
179 7 4096 mmcblk0p7 - deviceinfo
259 0 4096 mmcblk0p8
259 1 4096 mmcblk0p9
259 2 32768 mmcblk0p10 - loader
259 3 8192 mmcblk0p11 - kernel
259 4 16384 mmcblk0p12
259 5 16384 mmcblk0p13
259 6 16384 mmcblk0p14
259 7 16384 mmcblk0p15
259 8 7501824 mmcblk0p16
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0

By wandering around and making analogies with Dinobot I made the above allocation !!!I
created a Gigablue Trio 4K folder which I populated with what I found in the OpenATV
Recovery image !!! and the Kernel from the Normal image !

2.png


- I switched to the faulty receiver with network and serial connected!!!
- I deduced the IP it got, search on the router
- I started TFTPD, the FTP server and gave it the parameters
- I started HiTool and gave it the parameters

1.png


And now, brave one! I said ... Burn! Said and done! at the end I saved the configuration
file (XML) for eternity!!!yippee ... Reboot !!!

Screenshot-2024-12-12-13-58-44.png


Screenshot-2024-12-12-13-59-14.png


Screenshot-2024-12-12-13-59-29.png


Screenshot-2024-12-12-13-59-40.png


Gigablue has a strange recovery system! uses the Kernel existing inEMMC and not the
one delivered in the recovery image on the USB stick! soif the Kernel was stupidly rewritten
... in EMMC he launches it andit remains cracked!
 
@Liquid ... a 100 points question for you !!!

What is the content of the "Programmer file" ... can be read from SPi ?
can be write back ? witch is his role ?

I ask this because I feel that simple restoring "system" partitions is not enough !
that can explain my case ... restoring first 64 Mb of EMMC of a Viper 4K V30 ...
give a perfect functional STB except ... no Live Video and Audio ! but ... Live can
be streamed and ... works perfect under VLC on PC !!!
 
Last edited:
Back
Top