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.

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.

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

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 .

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.

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.

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 123986

BL2 Built : 20:29:41, Jun 18 2019. g12a ga659aac - luan.yuan@droid15-sz

***


U-Boot 2015.01-g691d522b66 (Sep 21 2022 - 10:24:29)

***

parts: 17
00:      logo    0000000000800000 1
01:  recovery    0000000001800000 1
02:      misc    0000000000800000 1
03:      dtbo    0000000000800000 1
04:  cri_data    0000000000800000 2
05:     param    0000000001000000 2
06:      boot    0000000001000000 1
set has_boot_slot = 0
07:       rsv    0000000001000000 1
08:  metadata    0000000001000000 1
09:    vbmeta    0000000000200000 1
10:       tee    0000000002000000 1
11:    vendor    0000000014000000 1
12:       odm    0000000008000000 1
13:    system    0000000060000000 1
14:   product    0000000008000000 1
15:     cache    0000000020000000 2
16:      data    ffffffffffffffff 4

***


Starting kernel ...

uboot time: 5689269 us
[    0.000000@0] Booting Linux on physical CPU 0x0
[    0.000000@0] Linux version 4.9.113-03131-g1dc2ef7073ba-dirty (freesat@winsat-PowerEdge-R710) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #1 SMP PREEMPT Thu Oct 27 13:37:48 CST 2022
[    0.000000@0] CPU: ARMv7 Processor [411fd050] revision 0 (ARMv7), cr=10c5383d

***

[   19.650436@0] file system registered
[   19.655767@0] assign_ffs_buffer FFS_BUFFER_MAX=100!!!

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.