Posts by frankviana

Quote from urie

Quote from frankviana

No more Android tests (back again to enigma2 files)... Now, we need wait Zgemma give us "gitf" with Android system.

if we are lucky we may get it if they ever release the 10 combo but even then it is still out dated 10/100 Mbit Ethernet and 300Mhz Speed WIFI

you nearly got there with your tests probably driver issues also and there are not available to you and zgemma not great in answering emails i have tried before.

No luck to solve any Zgemma devices...

Post months, until today no solve blindscan C

https://github.com/zgemma-star/meta-zgemma/issues/85

Bad support...

Quote from frankviana

We need found other Android firmwares when appear this image to try new tests (1 GB DDR3 and 8GB emmc):

Post here if someone find this kind of firmware.

Quote from evlasenko

Android boots up, displays the initial splash screen and then goes to this screen, where the network address (ethernet) is correctly determined and remains on this splash screen without responding to any buttons.

682f62d4f4ac52f.jpg

Click right button after MULTIBOX screen and before start this screen (no stop "RIGHT button" click after MULTIBOX)

For "exit" DTV, click right button too... for all back options... Maybe work too press "esc" keyboard, but no did tests this option.

No more Android tests (back again to enigma2 files)... Now, we need wait Zgemma give us "gitf" with Android system.

New good video (app tests)

https://gofile.io/d/cow97h

Zgemma need solve this dual boot and send us good Android firmware working DTV, RC and ethernet. I'm using usb mouse/keyboard. Remote control don't work.

:)

We need found other Android firmwares when appear this image to try new tests (1 GB DDR3 and 8GB emmc):

Quote from arion75

Quote from abparacha

Quote from frankviana

Now, new video using other image, then, wifi working...

:)

But need some (a lot of) steps to back to recovery enigma2...

https://gofile.io/d/aO0gTl

Display More

great work man, you can share firmware if it working,

Display More

You need to rename the folder multibox on h9combo. Put it back in the zip archive. And it can be installed via recovery. But we will get an unmanaged android.

Display More

Try tests replacing recovery.bin and bootoptions.img

Tests to boot for enigma2

for enigma 2.zip

Tests to boot for Android

Android.zip

After running Android, DTV don't found channels (different tuners) and ethernet don't work too, only wifi...

Android firmware to test (560 MB):

https://mega.nz/file/ZiQFhCiA#CeNlGUuv7HxDhNQt67B-hq8WxVFZnoGWc9oKAN_pBq8

Quote from piocarro

sorry if you buy an android box you don't do before

Sorry, but I did not understand what you said. :derpthink:

I need to sleep.

Here, 02:19 AM

:)

Now, new video using other image, then, wifi working...

:)

But need some (a lot of) steps to back to recovery enigma2...

https://gofile.io/d/aO0gTl

3 new videos... android running, but no network to download apk

https://gofile.io/d/W7LEer

Very fast, but I see some options, lol

https://www.mediafire.com/file…/200920086935_42.mp4/file

I think the problem is "skin", but I don't know how to change. This problem appear too when change my apk file for other HiScilicon dvb device.

Quote from urie

Quote from frankviana

New video:

https://www.mediafire.com/file…/200920086438_03.mp4/file

*OpenATV don't reboot to recovery (stop and need replace recovery again);

*When start to Android too, need replace recovery again.

We need a way to contact xda develpers to install other android images.

Here a log when starting Android:

H9_TWIN_ANDROID_2021-03-17_15-32-46.log

Display More

well done you are making good progress you can go to xda-developers and register.

Display More

I have account past more years, but some people don't answer... and... I don't have good english.

Mouse working...

https://www.mediafire.com/file…/200920086920_02.mp4/file

...but we need a way to do factory reset or install other android

New video:

https://www.mediafire.com/file…/200920086438_03.mp4/file

*OpenATV don't reboot to recovery (stop and need replace recovery again);

*When start to Android too, need replace recovery again.

We need a way to contact xda develpers to install other android images.

Here a log when starting Android:

H9_TWIN_ANDROID_2021-03-17_15-32-46.log

Wow!!!!

Sucess to install andoid on my Zgemma h9 twin, but rebooting after appear first screen (same first video Unsuccessful try to install android on zgemmah9twin).

Here the video:

https://www.mediafire.com/file…_20210317_130350.mp4/file

:)

After send only kernel, appear display Andr, but restarting... I need send kernel again.

ANDROID KERNEL.txt

We need a way to write only android partition, but I don't know why. I tried only "system" partition, because may to damage all systems.

Here 2 folders ".xml" for andoid boxes.

dceaf0614c4fbb3.png

Log for uart partition:

When try to load android:

Fastboot 3.3.0 (h9combo@builder) (Jul 24 2019 - 23:00:41)


Fastboot:      Version 3.3.0
Build Date:    Jul 24 2019, 23:03:26
CPU:           Hi3798Mv200
Boot Media:    eMMC
DDR Size:      1GB


Found flash memory controller hifmc100.
no found nand device.


MMC/SD controller initialization.
scan edges:3 p2f:5 f2p:8
mix set temp-phase 2
scan elemnts: startp:132 endp:111
Tuning SampleClock. mix set phase:[03/07] ele:[02/17]
MMC/SD Card:
MID:         0x15
Read Block:  512 Bytes
Write Block: 512 Bytes
Chip Size:   7456M Bytes (High Capacity)
Name:        "8GTF4R"
Chip Type:   MMC
Version:     5.1
Speed:       100000000Hz
Mode:        HS400
Voltage:     1.8V
Bus Width:   8bit
Boot Addr:   0 Bytes






*******************************


serial:
mac:


*******************************


Net:   eth0 phymdio(31) invalid, use default:0
upWarning: failed to set MAC address
, downWarning: failed to set MAC address
, gmac0Warning: failed to set MAC address




Boot Env on eMMC
Env Offset:          0x00100000
Env Size:            0x00010000
Env Range:           0x00010000




SDK Version: h9combo


Reserve Memory
Start Addr:          0x3A8FE000
Bound Addr:          0x8EA9000
Free  Addr:          0x391F7000
Alloc Block:  Addr         Size
0x3A4FD000   0x400000
0x3A1FC000   0x300000
0x3A1F9000   0x2000
0x3A178000   0x80000
0x39B88000   0x5EF000
0x3939E000   0x7E9000
0x3939A000   0x3000
0x39204000   0x195000
0x391FA000   0x9000
0x391F7000   0x2000


reading STARTUP_ONCE


0 bytes read
Total of 1 byte were the same
Total of 1 byte were the same
reading STARTUP


189 bytes read
byte at 0x01000000 (0x62) != byte at 0x04000000 (0x00)
Total of 0 bytes were the same
Press Ctrl+C to stop autoboot


MMC read: dev # 0, block # 196608, count 16384 ... 16384 blocks read: OK


176053727 Bytes/s
Check Hisilicon_ADVCA ...
Not hisilicon ADVCA image ...
Check Hisilicon_ADVCA ...
Not hisilicon ADVCA image ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!

MMC read: dev # 0, block # 155648, count 40960 ... 40960 blocks read: OK

176251008 Bytes/s
Check Hisilicon_ADVCA ...
Not hisilicon ADVCA image ...
Check Hisilicon_ADVCA ...
Not hisilicon ADVCA image ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Now, trying to get kernel from recovery again to boot other multiboot images:

MMC read: dev # 0, block # 4096, count 36864 ... 36864 blocks read: OK


176049348 Bytes/s
Check Hisilicon_ADVCA ...
Not hisilicon ADVCA image ...
Check Hisilicon_ADVCA ...
Not hisilicon ADVCA image ...
## Booting kernel from Legacy Image at 01000000 ...
Image Name:   Linux-4.4.35
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    15766387 Bytes = 15 MiB
Load Address: 02000000
Entry Point:  02000000
Loading Kernel Image from 0x16777280 to 0x33554432 ... OK
OK
ATAGS [0x00000100 - 0x000004E4], 996Bytes


Starting kernel ...

I tried only "system", but no sucess to boot android...

cbc57cea7bd7b904d32dc.png

cafcd8.png

27adda32b43.png

LOG HERE:

LOG2_H9_TWIN.txt