Posts by cayoenrique

  • Help porting Enigma2 to new device

    Long day for me, could not do much.


    As I expect the UARTs" voltage is 3.3V .

    The UART baud rate is 11520 8N1.


    I need to figure out how to keep MXQ info apart from GTCOMBO. Something like leaving this thread as Informal chat. And creating two extra threads just for each one of the Boxes. So no confusion is produce.


    So if you are following me. PLEASE keep in mind that in general you do not want to mix MXQ with GTCOMBO. You been warned.


    As I said latter we may have two new threads with separate info. For now let me post some of the Linux console output from GTCOMBO. I will post just some of the output for now.



    Then after that nothing else is printed. And it is unresponsive to Keyboards commands.


    I may have a bad PC board Rx solder joint. A bad USB to Serial Adapter or just there may be a boot command to disable console after 19 seconds. I do not know.


    I see you guys latter

    enrique.

  • Help porting Enigma2 to new device

    I almost have to quit. As the threaded connector of the DVS tune module broke!! I was lucky that electrical connections did not short or broke. I repaired by installing the outside flat watcher in the inside to prevent it from going out again to the outside. Mechanical force of the PC board against the back side of the plastic housing was good enough to make the ground connection.


    Now I need to know if anyone has good luck with establishing UART connection to create a Linux boot console. See following images:


    GTCOMBO Botom Reset Button

    Click to Enlarge


    GTCOMBO top UART

    Click to Enlarge


    If you look the RED Square I highlight at the extreme LEFT LOWER corner, you cans see an empty 4 pin holes. They should be label like

    V TX-Transmit

    R RX-Receive

    T Transmit

    G Ground


    Need to measure G to V.

    UART operates with standard 3.3V or 5V logic levels.

    I will expect this one is , TTL UARTs" outputting a 3.3V high signal.


    So the question is Voltage level and Port settings. Hopefully my family will allow me to play with GTCombo tonight, as they used it as Satellite TV Source during the day. This important for the second phase after I play with MXQPRO4K. We need to monitor UBOOT and the rest of the boot process to know it boots as intended or do troubleshoot if not.

  • Help porting Enigma2 to new device

    Who I am? What I know?:

    I have knowledge of Linux and controllers.

    But no experience on Enigma 2 other that to expect it should run better than Android with its support for many extras.

    I am been learning about Amlogic in particular S905 CPU. Now I mentioning this because the Fail-Safe boot process of Amlogic, is what should allow us to boot what ever we want on the device with very limited risk.


    And I am the type of person willing to take small risk to learn from mistakes.


    Now I will assume followers only want to do beta test. So unless some one ask for details I will not post procedures for creation for working files. But PLEASE feel free to ask. In the other hand be aware that I am learning too and that I can say things that may not be the correct procedure. All files are provided as is, you try them at your own risk. Soo, ask all you what before trying.


    OBJECTIVE:

    To boot from external sdcard a new Enigma 2 OS. Without touching Android from internal Flash of the GTCOMBO..


    PROBLEM:

    We have no Kernel Sources. This mean that a generic Kernel most likely find missing drivers. NO Tuner or even Wifi or Bluetooth, etc?

    Solution:

    1) To overcome this problem I intent to test if we can boot with Original Official Kernel os any of the GTMedia firmware. Then after all drivers are initialized we chroot to a Enigma 2 kernel/OS.

    2) Now as mention earlier I did some test using another Android TV with same S905 CPU.



    ENIGMA 2:


    If you read post #10 & #11 you will see that most of the work was done . See ==> RE: Help porting Enigma2 to new device


    The Thread RE: Enigma2 for KI, KII & KIII


    Is a MOST See to understand. See their Android Sat Box is a Mercool KI, K2 or KIII. And a user with nick "vidmod" proposed to use Enigma 2 solution. K1 & KII are base on S905. That is why I did copy the enigma partition from vitmod 6 backupV3.


    buc61b did ask for an "openatv 7.6". I have no time to learn enigma nor to build my self. Best I found here in the

    forum thread RE: Vitmod ATV 5 release for K3 pro


    Witch may or not be same as previous one. I will test next.


    Now lets resume, I will re do my previous steps to make a working MXQPRO4K image and test. Then I will start with the mod on the GTCOMBO witch require an additional step that is booting from official android kernel. If you like the steps I did to build just ask .

  • GTMEDIA GT COMBO (Android+DVB-S/S2/S2X+T/T2/Cable/ISDBT)

    OK guys to prevent prolonged Hijacking of this old thread lets continue where I started years ago. See next Link


    Post
    RE: Help porting Enigma2 to new device
    I know I had not been seen for years. I am so sorry. I was sick , OLD.... and too busy.

    But I intent to play a little more now that GTMEDIA seems to be gone. AHHHH.. I been ask to do some shopping. Bad luck.. But when I return I will try to post what I had on hand.

    See you guys very soon.
    enrique
    cayoenrique


    enrique

  • Help porting Enigma2 to new device

    I know I had not been seen for years. I am so sorry. I was sick , OLD.... and too busy.


    But I intent to play a little more now that GTMEDIA seems to be gone. AHHHH.. I been ask to do some shopping. Bad luck.. But when I return I will try to post what I had on hand.


    See you guys very soon.

    enrique

  • GTMEDIA GT COMBO (Android+DVB-S/S2/S2X+T/T2/Cable/ISDBT)

    @buc61b


    FACTS:

    1-The OP - Original Poster is GTMedia Linuxsat VIP. His last Last Activity: Nov 27th 2023. Never to be seen again.

    2-That I know there has never been posted an Official Firmware for GTCombo on this thread and I bet you there is none in the whole forum area: Linux Satellite Support Community>Android TV Boxes>GTMEDIA

    3-Since January 2026 Official GTMEDIA Forum removed ALL threads focused on Sat TV Boxes without giving reasons. This include GTCOMBO.


    Quote from buc61b

    ...I am waiting new sw for gt combo...

    I hope I am wrong but from what I see you will have a long waiting if you looking for a new official sw release.

    Quote from buc61b

    ...Why are u posting here such scam post..

    What seems to you "scam post", is our attempt to get an Enigma 2 firmware for GTCOMBO from us Linux Satellite Support Community users.


    I do not want to risk my $80-$100USD GTCOMBO box. So I do test on a cheap easy to find clone Amologic Android Streaming Box $15USD, in this case I had around a MXQPRO4K, but I suggest any one of you use what ever cheap Amlogic streaming box you hand on hand if you plan to find your self testing.


    enrique

  • GTMEDIA GT COMBO (Android+DVB-S/S2/S2X+T/T2/Cable/ISDBT)

    All the info in this post is NOT ABOUT GTCOMBO. PLEASE do not try to upload anything from this post to a GTMEDIA GTCOMBO.


    @frankviana

    Quick answer is a modification of disk image base on ==> v3.vitmod.k3pro.img the link is below.


    But 1rst lets say that old MXQ, MXQPRO, MXQPRO4K or MXQPRO+ is one of the most cloned Chinese TV Box . So expect anything. So my 1rst point is that due to so many clones you can expect that what works for me not necessary work for you.


    But in the good side, mostly this old boxes comes bootloader unlock and are easy to root.


    Now my clone is type MXQPRO4K with


    1) Hardware PCB: green pcb labeled "mxq_s905_v2_2 20160428"

    CPU Amlogic S905 Cortex A53 Processor 2.0GHz

    GPU Penta-Core ARM Mali-450

    RAM 1GB DDR3

    ROM 8GB NAND FLASH


    2) Original OS: Android 5.1.1 Build Number MXQ-Pro-201606131132

    Android ID: a23263b052e52827

    Build ID: MXQ-Pro-201606131132

    Codename: REL

    Fingerprint: Android/p201/p201:5.1.1/MXQ-Pro/20160613:userdebug/test-keys


    3) My E2 modification was build using:

    A) For bootloader image partition: Modified boot.img that comes from: LibreELEC-S905.arm-8.2-8.2.3.1.img

    Downloaded from: https://libreelec.dtech.hu/mis…05.arm-8.2-8.2.3.1.img.gz

    B) For Enigma 2 partition I base it on: v3.vitmod.k3pro.img

    Download v3.vitmod.k3pro.img.gz from: https://www.mediafire.com/file….vitmod.k3pro.img.gz/file


    Listen I am no expert, but if any one is interested we could open a new thread some where else to talk more about MXQ. As this thread is for GTMEDIA.


    Edit NOTE:

    All

    Linux on Android: If you intent to modify any BOX the MOST important step is to try to backup as much as you can from the original Linux/Android BOX. In particular having the original working dtb file is a MOST HAVE. See modenr kernels need the dtb file to Identify all the devices on your Linux BOX. Without the correct dtb you will not get the drivers of the new kernel mod to work.

  • GTMEDIA GT COMBO (Android+DVB-S/S2/S2X+T/T2/Cable/ISDBT)

    Quote from rozpruwacz

    GTMedia is it possible that You share the source code for the m88tc6800 tuner used in gt combo ? I'm running linux distro on this box and this tuner is the only part missing.

    @rozpruwacz


    I am interested in your work, and even in join search for m88tc6800 driver.


    Let me start by saying what I have done.

    My GTCOMBO is with original firmware. I had never allow it to take an update. But I did rooted and disabled a few of the original offered apps, including "firmware update". My original intention was to run some sort of Enigma 2 firmware. Now to be honest I never try to run anything else but the original Android OS on the GTCombo.


    But I did used a MXQPRO TV box as a test bed to execute Enigma 2, with success. Clearly TV box did not had any DVB-S tuner.


    I was same place you find yourself now . I did not found GTCombo tuner drivers. And also to be honest had little time to experiment.



    Now there is a possible last resort solution to overcome missing drivers.

    The solution involves starting boot on original Android Kernel, then chroot or proot to the new Linux Kernel / OS .


    I hope to hear from you soon.

    enrique

  • GTMEDIA GT COMBO (Android+DVB-S/S2/S2X+T/T2/Cable/ISDBT)

    GTMedia I guess are working a little. What they do wrong is not having a permanent voice at freesat. That provocate some users to feel ignored.


    A recent purchase came 2GB RAM 32GB EMMC ( 28 GB available ).


    I think I saw the originals with 1GB RAM 16GB EMMC.


    Now for the price, and sensitive tuner I am personally happy wit the receiver. Is like half the price of other receivers, so what you want or expect.


    Some of the complains have no real foundation. Like complains on turning on when powered. Guess what? That has nothing to do with GTMEDIA, Turning up on powered, is AMLogic way to go into bootloading/recovery. You can NOT change that.


    I personally have a complain on another receiver V9prime. In particular, special services M A R s global 7 0 W west SA beam. I got it working only 3 days of the last 18 days.

  • GTMEDIA GT COMBO (Android+DVB-S/S2/S2X+T/T2/Cable/ISDBT)

    Your answer does not convince me. Sorry. Why?


    Because freesat clearly caution people not to download and used that "T".


    Why would they do not want users to use "T" if they build it and was the answer for all problems!!


    Something do not add up....


    As a note:

    The comment I am mentioning was posted at "GTCOMBO Firmware Version" for V24 & V27.


    Now for V28 reads more nicely:

    Quote

    3. The software version with T is not the official version,
    It's an experience version for enthusiasts. Does not support OTA upgrade, need USB to download ZIP package to upgrade

  • Help porting Enigma2 to new device

    Update.


    I want to notify, that I am still working on the project. In general I am learning on boot/recovery process of Amlogic Devices. I will continue because what I learn should apply not only to GTCOMBO, but to most E2 Arm devices. So I am learning anyway.


    Now my GTCOMBO purchase is in trouble. So I do not know when I will be receiving it.


    There are a few obstacles that are making this project hard or destine to fail.


    The SAT Hack community has been for long here. But to survive, hackers need to have as much freedom to modify their stuff so that it finally can obtain positives results. So Lock bootloaders or Force updated on devices are the enemy of a hacker. If a hacker find that a new firmware not longer work, he then try to rollback to the previous. But if a Lock bootloader prevent rollback, it is then endgame. There is more to it but lets try to make it short. Now USA intelligence N S A, long intervening in Phone OS development to ensure that commerce on phones is safe. And Android/Iphone user got custom to force updates. Now an Android Satellite receiver can NOT be like phones. As I explain your TV viewing gets on jeopardy.


    It seems at the moment that GTMEDIA is treating its Android Satellite receivers like Phones with force updates. I do not own GTMEDIA to be sure that possible the phone bootloader may be lock too. If we can not install what we want as hackers on the Receiver, then this device looses quickly its potential as a platform.

  • Help porting Enigma2 to new device

    I did download to have a quick look:

    GTMEDIA_GTCOMBO_V2.0_C20.A9.1.11_19102021.rar

    GTCOMBO_v2.0_C20.A9.1.24_20230717.img

    GTCOMBO_v2.0_C20.A9.1.24_20230717.zip


    I did not found any reference to "aml_autoscript". This not necessary means we can not auto boot without Reset. There should be always the long way option to use the Update&Backup APK to force running the script from Android Menu.


    There was a uboot multiboot. Sadly all links I found for the original uboot multiboot where removed from Internet!! Weird.

    New custom uboot can also do the trick in the even we need a simple USB auto boot method.


    Tomorow if I have spare time I may try to unpack Working Libreelect boot.img, and see if I can modify "init" to auto chroot into Enigma 2 partition.

    Then I guess see if I can reuse working remote control config from libreeelect and substituye it on old Enigma. See if I got ETH0 and WLAN working.


    Again, I do not need a working MXQPRO4K with E2. I am doing it as a practice experience.


    This MXQPRO4K future may be to stay in Libreelect or with my own custom copy of Debian.

  • Help porting Enigma2 to new device

    PLEASE I am not asking you to do anything.


    Before you do anything it is important to backup your Android, I normally used TWRP.

    Now to be honest the very 1rst time, i get to a Linux promt. Then I get a BIG USB or SDCARD. and copy ALL hiden partitions.


    To get all partitions names I do

    Code
    # cat /proc/partitions
# ls -la /dev/block


    Then I prepare a bash script. Here the one I use with MXQPRO4K


    You need a USB bigger that your flash memory.

    Then in a PC I format this USB ( Empty). I normally use Linux ext4 partitions. As Android do not like to execute bash on FAT32.

    And I place the last bash script on it.


    Boot Android, open a terminal, Yes you need a Terminal APK.

    manually mount the ext4 partition, then execute batch script. Depending on the size of your FLASH it may take long time.

    If you want you can always comment /dev/block/data & /dev/block/cache. As this are not critical. They get empty when you do Factory WIPE/Reset.


    Again, this is for reference. As you seems interested. I am NOT asking you to do anything. dd is a POWERFULL command, just as dangerous!!

    Windows users call "dd" Linux "Disk Destroyer" command!!

  • Help porting Enigma2 to new device

    UPss I just realize I miss a step where I mount SDA2. Just in case SDA2 is USB secon partition that holds Enigma 2. So complete it should be like this


    Code
    CHRDIR=/storage/sda2
mkdir -p $CHRDIR
mount -t=ext4 /dev/block/sda2 $CHRDIR
mount --bind /dev $CHRDIR/dev
mount --bind /proc $CHRDIR/proc
mount --bind /sys $CHRDIR/sys
chroot $CHRDIR
./linuxrc

  • Help porting Enigma2 to new device

    It may sound strange, but kernel work so good that I do all using HDMI as monitor. But to make it easy I have a usb mouse and a usb keyboard.


    Now PLEASE do not forget I have no GTCOMBO. My test subject is just another Chinese Android TB Box called MXQPRO4K.


    IMPORTANT:

    For GTCOMBO, the stopping problem could be the DVB Tunner. So we need one of three thing to happen.

    * GT Media get nice with us and place at github working Kernel Sources

    * We try to build one of the latest Generic Amlogic Kernel, with the hope that drivers are already up.

    * At a last minute resource, we can try to use GTCOMBO's current Kernel (boot.img). Then we unpack the kernel, make any necessary changes to initramfs, init or even any /etc/init.d files. Then repack. In the hope that Androids own kernel is enough to chroot into Enigma 2.


    What kernel version your GTCOMBO has? In terminal do uname -a.


    Now, I am a Linux guy. In reality at the end I do not need Enigma2. See Enigma 2 is just in fact another Linux Distribution just like Ubuntu. Simple solution for me is using one of the already Linux versions for AMlogic, like: LibreElect, OpenElect, Armbian. But I most likely install at the end my own minimalist build of Debian using bootstrap. On top I will install "tvheadend" and "oscam". In this way I can watch Sat / Terrestrial TV from any of my Android devices or PC in my local LAN.


    I used to do this with a PC and a USB PCSAT. But GTCOMBO will be better as less power consumption will be require.

  • Does GTMEDIA devices update EMM`s for TVSat card automatically

    Please ignore or even delete my post if you feel like.


    But Title is "Does GTMEDIA devices update EMM`s for TVSat card automatically"


    And I was responding to a question.

    Then some one posted "You're definitely joking, do you know what you're saying?"


    I was force to clarify that I am not crazy.


    But as I say if moderators feel it out of place, please delete my responds to a request.

  • Help porting Enigma2 to new device

    1) I installed “backup v3.vitmod.k3pro.img” in a 8GB old USB I had using, “LibreELEC.USB-SD.Creator.Win32”

    2) I replaced original “dtb.img”, because I have a different platform, NOT K3PRO, instead MXQPRO4K. So I use a generic “gxbb_p201.dtb” and renamed “dtb.img”.

    3) I try to boot but failed to get in to Enigma2. I assume it is wrong kernel ( Boot image ). But I also assume ENIGMA 2 partition should be ok/useful.


    4) knowing that kernel from LibreELEC-S905.arm-8.2-8.2.3.1 works, I then proceeded to get it. From LibreELEC-S905.arm-8.2-8.2.3.1 partition 2, I copied kernel.img and renamed boot.img. Again, as I know this kernel works.

    5) I mounted in PC the USB with v3.vitmod.k3pro, This time I replace boot.img with my librelect one, that I prepare in step 2.


    6) I place the USB in my MXQPRO4K and proceeded to plugin the power. Please notice that we do not need to press Reset button as it uses “aml_autoscript” that takes care of it. NICE.

    7) As expected kernel start booting. But as I have not modified the “init” file it gets to a point where it fail to find “Libreelect” image. Sure the v3.vitmod.k3pro have no “Libreelect” image to mount. So as init fail, it drops me to a #promt. NICE I have a working promt.


    8) I then proceeded to mount (USB second partition) SDA2 and to “chroot” to it, just to finaly execute ENIGMA 2 real Init.


    Code
    CHRDIR=/storage/sda2
mkdir -p $CHRDIR
mount --bind /dev $CHRDIR/dev
mount --bind /proc $CHRDIR/proc
mount --bind /sys $CHRDIR/sys
chroot $CHRDIR
./linuxrc


    9) SUCCESS, I did run old v3.vitmod.k3pro Enigma2 in my MXQBOX4K. I was force to use a keyboard as my remote control is not for what it was build. Clearly I have no DVB-S reception. My box have no sat tuner.


    Please notice I have spent lotss of time reading here an there. And that in fact I have not change or compile a single line of code. This 1rst step only serve to feel relax knowing that some how, there should be a way to compile E2 for one of this Chinese TV boxes.

  • Does GTMEDIA devices update EMM`s for TVSat card automatically

    Quote from gobi2000

    You're definitely joking, do you know what you're saying?

    SKS is not something new. It was used in South America where there is a lot of land faraway from civilithaction where there was no terrestrial Internet.


    Here a definition:

    Quote from https://www.computerlanguage.com/results.php?definition=satellite+key+sharing

    Redirected from: satellite key sharing, Definition: card sharing


    The illegal access to pay TV, which occurs primarily in Europe and South America. Card sharing sends the decryption codes (code words) from the smart card in the receiver of a legitimate pay TV subscriber to an illegal server on the Internet. Using a modified set-top box (receiver), non-paying users acquire the codes from the server. Card sharing is also known as Internet key sharing (IKS), satellite key sharing (SKS) and control word (CW) sharing.


    I guess GTMEDIA M7X is the latest. But it is ONLY for Brazil footprint.


    Sorry if it sound weird for the Top North part of the World. I witch if was my Idea or invention.

  • Help porting Enigma2 to new device

    Learning every day.


    I have to remember to post links of github inside code. If not link is lost and instead we see those images.. Strange for me!!



    PD


    This is weird, 1rst images no link. After my post Images have links.... what a day.