43 43
balbes150

Armbian for Amlogic S9xxx kernel 4.1x (>= ver 5.55)

Recommended Posts

On 6/10/2019 at 9:04 AM, amirul said:

I have this one. After few hours stopped working, but furtunately due to faulty power supply. However, I mentioned previous page, I could not get it dual boot using standard methods. Balbes150 asked me to give UART output, but could not do it as UART. As per spec, WiFI/BT chip is AP6212

Share this post


Link to post
Share on other sites
38 minutes ago, sekarpdkt said:

I have this one. After few hours stopped working, but furtunately due to faulty power supply. However, I mentioned previous page, I would not get it dual boot using standard methods. Balbes150 asked me to give UART output, but could not do it as UART. As per spec, WiFI/BT chip is AP6212

Can you give output of atmbianmonitor -z for comparison?

Share this post


Link to post
Share on other sites
On 6/12/2019 at 7:34 PM, KrishIsola said:

I’m developing a (video) content display solution to run device in kiosk mode with Chrome browser starting in fullscreen. It is supposed to display video being received. Now, I’m looking at Amlogic S905x base board to run my solution. Ordered sample S905x based Android TV box from sztomata (OneNuts).

For S905X without HW support, the browser can play full screen YouTube video with 720p desktop resolution.

 

On 6/12/2019 at 7:34 PM, KrishIsola said:

- Reference, Docs, Scripts to remove Android and load Linux image onto S905x board (eMMC)

This information is in this topic (description of system startup and installation in eMMC).

 

On 6/12/2019 at 7:34 PM, KrishIsola said:

- Any recommendations on which OS and build to load?

For use with video, you can use Armbian with the optional HW acceleration script. Information about this version of there is in this topic previously (version of DEV with mali).

 

On 6/12/2019 at 7:34 PM, KrishIsola said:

- Can I use Khadas or corelec images directly on sztomato S905x hardware? 

- Must work: LAN, Wifi, BLE, USB, HDMI, Video Codecs (H.264, VP8, H.265, VP9)

I don't have that kind of equipment. I don't know if it will work or not with Armbian and Libreelec. I'm not dev Coreelec have no idea how well it works or not.

 

On 6/12/2019 at 7:34 PM, KrishIsola said:

- I might need to display say max 4 simultaneous video playback in same browser window

I have not tested such modes of operation.

 

Share this post


Link to post
Share on other sites

Hello, first a very thank you to all those who work on this forum and who offer us great tools!
I would like to ask a question to reassure me.
I have a VONTAR X96 Mini (2Gb, 16Gb) and I got it to start easily under ARMBIAN.

I used the image "Armbian_5.76_Aml-s905_Debian_stretch_default_4.20.5_20190224.img" because I need the Stretch version of Debian.
Here is my question: can I flash the EMMC card without worry, knowing that I do not use the latest version of ARMBIAN images?
In advance, thank you for your cooperation.
Ricardo

Share this post


Link to post
Share on other sites

Hi all,

 

Thanks balbes150 for your great work.

 

I installed the 5.88 version on my S905X 1g/8g tv box and did a samba, xrdp and ssh server.

Do you have any idea why the services only work if I'm logged in?

 

If the tvbox restarts I loose all services until I'm next to it and login with keyboard.

What should I verify and apply to make it work headless?

 

Thanks in advance.

Share this post


Link to post
Share on other sites
15 minutes ago, baku1413 said:

What are the differences between these images?

The one with "desktop" means the image is already including a X11 desktop, that is why image size is bigger ...

Share this post


Link to post
Share on other sites

Trying newest firmware Ubuntu Disco Desktop on a S912 3Gb Gb NIC TVBox.

 

All looks to be OK except that the NIC card doesn't start.  Wireless works fine.

 

Jun 18 01:31:35 HS-ATL kernel: Linux version 5.1.0-aml-s905 (root@vbox) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f
Jun 18 01:31:35 HS-ATL kernel: Machine model: Khadas VIM2 2x VTV

 

Jun 18 01:31:35 HS-ATL kernel: dwc3 c9000000.dwc3: Failed to get clk 'ref': -2

 

Jun 18 01:31:35 HS-ATL kernel: meson-gx-mmc d0074000.mmc: no support for card's volts
Jun 18 01:31:35 HS-ATL kernel: mmc1: error -22 whilst initialising MMC card

 

Jun 18 01:31:35 HS-ATL kernel: mdio_bus 0.2009087f: MDIO device at address 0 is missing.
Jun 18 01:31:35 HS-ATL kernel: phy phy-d0078080.phy.3: unsupported PHY mode 5

 

Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: PTP uses main clock
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: no reset control found
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet:         DWMAC1000
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: COE Type 2
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Normal descriptors
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Ring mode enabled
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet (unnamed net_device) (uninitialized): device MAC address c4:2a:fe:36:11:32

 

Jun 18 01:31:36 HS-ATL kernel: brcmfmac: F1 signature read @0x18000000=0x15264345
Jun 18 01:31:36 HS-ATL kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Jun 18 01:31:36 HS-ATL kernel: usbcore: registered new interface driver brcmfmac
Jun 18 01:31:36 HS-ATL kernel: Bluetooth: Generic Bluetooth SDIO driver ver 0.1
Jun 18 01:31:36 HS-ATL kernel: brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.khadas,vim2.txt failed with error -2

Jun 18 01:31:37 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
Jun 18 01:31:37 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)


Jun 18 01:31:37 HS-ATL kernel: Adding 1048572k swap on /dev/zram1.  Priority:5 extents:1 across:1048572k SSFS
Jun 18 01:31:37 HS-ATL kernel: zram0: detected capacity change from 0 to 52428800
Jun 18 01:31:37 HS-ATL kernel: EXT4-fs (zram0): mounted filesystem without journal. Opts: discard
Jun 18 01:31:38 HS-ATL kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Jun 18 01:31:38 HS-ATL kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4f

 

Jun 18 01:36:38 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
Jun 18 01:36:38 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
Jun 18 01:40:49 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY
Jun 18 01:40:50 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)


Jun 18 01:31:41 HS-ATL kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3

 

root@HS-ATL:/sys/class/net/eth0# sudo lshw -c network
  *-network:0               
       description: Wireless interface
       physical id: 3
       logical name: wlan0
       serial: 6c:21:a2:4e:68:d8
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=brcmfmac driverversion=7.45.154 firmware=01-4fbe0b04 ip=192.168.244.250 multicast=yes wireless=IEEE 802.11
  *-network:1 DISABLED
       description: Ethernet interface
       physical id: 4
       logical name: eth0
       serial: c4:2a:fe:36:11:32
       capabilities: ethernet physical
       configuration: broadcast=yes multicast=yes

 

This is going to be an automation server and will remove desktop once it is working.

 

Any suggestions?

 

 

 

Share this post


Link to post
Share on other sites

The new version of 5.89.

 

 

Pay attention to the Odroid N2 in these images there is a new u-boot-2019. When running from SD card in u-boot "mmc" switch mode, the "boot.ini" script will no longer work. All settings are made only through the standard file "extlinux.conf". Current file "boot.ini" is used only when the system is started using a modified u-boot in SPI.

 

 

Share this post


Link to post
Share on other sites

Hi, 

Im running newest build of Armbian on my TV box MECOOL M8S PRO WIFI 5.1 kernel

But in current kernel į dont see ssv6051 firmware. Would it be possible to add it to The build? Ar maybe some One could assist on building it on my system? 

Thanks

Share this post


Link to post
Share on other sites

For anyone getting stuck with their box:

 

- Setup and Imaging

- Booting

- What are DTB files about

- uEnv.ini and extlinux.conf

- Bricked your box etc

- Installing to emmc/NAND

 

Ive written this general guide.

 

 

I dont expect to answer every question/solve every problem, but it perhaps centralizes a lot of questions/answers people seem to keep asking on the forum.

 

Share this post


Link to post
Share on other sites

Tinkering a bit with changing DTB file I can get a mac address but no IP right now....T95Z Max S912 - 3Gb - Gb NIC

Share this post


Link to post
Share on other sites

@erew

Saw your guide, and you state there that WiFi iš nor working for you :) otherwise its good guide

So still looking for options to get WiFi working on mecool m8s pro w

Share this post


Link to post
Share on other sites
3 minutes ago, Laurynas said:

@erew

Saw your guide, and you state there that WiFi iš nor working for you :) otherwise its good guide

So still looking for options to get WiFi working on mecool m8s pro w

 

Yes, sorry I dont know of any way to get it working on that box. Id like it working too. I tried all the different DTB files just over 1 year ago and none of them got the WiFi working.

 

If you do find any solution (either an updated DTB file on the latest Armbian, or a manual driver install somehow) please let me know!

 

Thanks!

Share this post


Link to post
Share on other sites

Hi i am traying to install armbian in my new tv box (Mecool km3). i have used the image: "Armbian_5.89_Aml-s905_Ubuntu_bionic_default_5.1.0_desktop_20190617" but my tv box only show the initial screen "Tv box" and never follow there.

 

The step to step that i have used is:

1. Burn the image "5.89_Aml-s905_Ubuntu_bionic_default_5.1.0_desktop_20190617" in an usb pen using etcher.

2. I have activated the multiboot mode  ( Pushing internal button while a power the tv box for 5 seconds).

4. I have setup "meson-g12a-x96-max.dtb" like as dbt file in uEnv.ini file.

3. The tv box shows in its screen "Tv box" and it does not continue.

 

Can you help me??

Share this post


Link to post
Share on other sites
38 minutes ago, Jorge Bolanos said:

4. I have setup "meson-g12a-x96-max.dtb" like as dbt file in uEnv.ini file.

 

I don't know if there is a compatible dtb file for mecool device running 905X2 actually. I will try on my km9 tomorrow.

 

Maybe you have to chose from your android update the aml zip file. Did you try that way ? 

Share this post


Link to post
Share on other sites
1 hour ago, Peyton said:

I don't know if there is a compatible dtb file for mecool device running 905X2 actually. I will try on my km9 tomorrow.

 

Maybe you have to chose from your android update the aml zip file. Did you try that way ? 

My firts step was from android TV to execute the process of updating with USB stick in Mecool km3..i choose local update and also choose aml_autoscript.zip from USB Stick. After the tv box to do automatic reboot and when it up to generate an error in screen and after again to boot in Android TV.

 

It is very important for me that you try it your mecool km9 as km3 and km9 are very similar models.

 

I remain pending for your test in km9 I'm glad you share what you find with me.

Share this post


Link to post
Share on other sites

I did the test on my km9

 

- prepared the sdcard with Armbian_5.88_Aml-s905_Debian_buster_default_5.1.0_20190611

- select meson-g12a-x96-max.dtb in both uEnv.ini and extlinux.conf

- I boot android as usual

- select aml .zip from update

- It boots but i have no eth interface

Share this post


Link to post
Share on other sites
1 hour ago, Peyton said:

I did the test on my km9

 

- prepared the sdcard with Armbian_5.88_Aml-s905_Debian_buster_default_5.1.0_20190611

- select meson-g12a-x96-max.dtb in both uEnv.ini and extlinux.conf

- I boot android as usual

- select aml .zip from update

- It boots but i have no eth interface

Hi i have the following question:

1. My km3 has operating system "Android TV 9"...What does operating system has your km9??

2. what difference will have between to do the processs with usb stick that i use and sdcard how you do it??

3. the file aml.zip that you say is the file "aml_autoscript.zip" that is in the image??

 

Basicly i do the same process but in my case when km3 boot up it shows an error in screen!!

 

I believe that the trouble with eth interface is because the X96 max has a eth interface to Gigaethernet while km9 and km3 have a eth interface to 100 MB. We must find a dtb file for km9 and km3.

 

Tonight i am going to test with the same image that you used.

Share this post


Link to post
Share on other sites

1. I downgrade to android 8.1 as i wanted AOSP version. It may help. On my km8p i had to downgrade to android 6 to make armbian boot. Can't confirm it on km9.

2. sdcard is always better than usb stick on tv boxes. I can't find the source but it is.

edit

Quote

Attention !!!! On models with S802 S805 S812. Activation multi-boot is possible ONLY with SD card (activation of the USB stick is NOT WORKING). After a one-time activation procedure is multi-boot, run a variety of systems is possible from ANY storage media (SD cards and USB storage devices).

" first post.

3. Yes. I didn't had the exact name.. :)

 

I will test with this version Armbian_5.88_Aml-g12_Debian_buster_default_5.1.0-rc1_20190609.img tonight

Share this post


Link to post
Share on other sites
11 minutes ago, Peyton said:

1. I downgrade to android 8.1 as i wanted AOSP version. It may help. On my km8 i had to downgrade to android 6 to make armbian boot. Can't confirm it on km9.

2. sdcard is always better than usb stick on tv boxes. I can't find the source but it is.

edit

" first post.

3. Yes. I didn't had the exact name.. :)

 

Peyton, I appreciate your quick response very much.

 

Other question: Where can i find an image with android 8.1 for my Mecool km3? I would like to try putting this operating system in km3 before to try again to make armbian boot.

Share this post


Link to post
Share on other sites

Don't know. I saw ppl with km9 flashing km3 but it could brick your device. If you have usb/usb cable you can flash it with USB_Burning_Tool

 

km9 aosp : https://drive.google.com/file/d/1uMkgYrIHXbPDnrFnThWraEBpk5GHN5RR/view

 

original km3 : https://androidpctv.com/firmware-mecool-km3-rom/

 

For your info i've just tried with Armbian_5.88_Aml-g12_Debian_buster_default_5.1.0-rc1_20190609.img and it's the same..

 

Boot without any network interface except lo. :(

Share this post


Link to post
Share on other sites
On 6/18/2019 at 4:19 PM, Laurynas said:

As i understand, on kernel 3.14 there were module for ssv6051, thats The chip that should be used on this mecool m8s pro w box. But in current build there is No module for ssv6051 (5.44_3.14 still have it) and i had No success in compiling a driver for it. As i have never compiled anything on linux before :)

Share this post


Link to post
Share on other sites

OK got ethernet sort of working on the T95 Z Max TV Box (S912 - 3Gb - 1Gb NIC) using meson-gxm-q201.dtb.

 

/boot# uname -a
Linux HS3-ATL 5.1.0-aml-s905 #5.89 SMP PREEMPT Mon Jun 17 13:01:39 MSK 2019 aarch64 aarch64 aarch64 GNU/Linux


 

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c4:2a:fe:36:11:32  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  

eth0:avahi: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 169.254.5.7  netmask 255.255.0.0  broadcast 169.254.255.255
        ether c4:2a:fe:36:11:32  txqueuelen 1000  (Ethernet)
        device interrupt 20  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 551  bytes 50590 (50.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 551  bytes 50590 (50.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.244.252  netmask 255.255.255.128  broadcast 192.168.244.255
        inet6 2601:244:4000:dc3:55cc:f13:e04e:f6a8  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::944c:1fa5:37b0:bab2  prefixlen 64  scopeid 0x20<link>
        inet6 2601:244:4000:dc3:b85c:6eb8:c6a2:531f  prefixlen 64  scopeid 0x0<global>
        ether 6c:21:a2:4e:68:d8  txqueuelen 1000  (Ethernet)
        RX packets 13082  bytes 2254470 (2.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1727  bytes 296907 (296.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

No DHCP address comes up for eth0...but I can ssh into the eth0:avahi port which doesn't make sense to me.

 

I have read that there is an issue with eee and if I disable it that may fix my problem here.

ethtool --show-eee eth0
EEE Settings for eth0:
    EEE status: enabled - active
    Tx LPI: disabled
    Supported EEE link modes:  100baseT/Full
                               1000baseT/Full
                               1000baseKX/Full
                               10000baseT/Full
                               10000baseKX4/Full
                               10000baseKR/Full
    Advertised EEE link modes:  100baseT/Full
                                1000baseT/Full
                                1000baseKX/Full
                                10000baseT/Full
                                10000baseKX4/Full
                                10000baseKR/Full
    Link partner advertised EEE link modes:  100baseT/Full
                                             1000baseT/Full
                                             1000baseKX/Full
                                             10000baseT/Full
                                             10000baseKX4/Full
                                             10000baseKR/Full

 

Share this post


Link to post
Share on other sites
4 hours ago, Petee said:

OK got ethernet sort of working on the T95 Z Max TV Box (S912 - 3Gb - 1Gb NIC) using meson-gxm-q201.dtb.

Have you tried meson-gxm-q200.dtb?

Share this post


Link to post
Share on other sites
(edited)

Question about a T95Q - can it boot @balbes150 armbian? Which version?

 

Hello,

I have an S905X and a S912 running Debian Stretch, thanks to @balbes150.

 

Now I've bought a S905X2, T95Q model (4 GB RAM, USB 2 & USB 3,  Android 8.1, and so on).

I've tried to boot Debian:

1- Armbian_5.89_Aml-s905_Debian_buster_default_5.1.0_20190617

2- Armbian_5.84_Aml-s905_Debian_stretch_default_5.1.0-rc1_20190507

 

I've installed aml_autoscript.zip using "Update & Backup" app.

 

Tried to boot from USBs and microSD.

 

It doesn't boot, all I get is the "T95Q" logo.

 

What can I do to? Maybe the best is to return it to the seller?

 

Thank you very much,

EDIT: I've found its original firmware here: https://androidpc.es/firmware-t95q-box/

EDIT 2: The contents of this firmware:

-rwxr-xr-x@ 1 Apple  staff         621 Jan 10 18:39 aml_sdc_burn.ini
-rwxr-xr-x@ 1 Apple  staff  1416070328 Jan 10 18:44 aml_upgrade_package.img
-rwxr-xr-x@ 1 Apple  staff    24683008 Jan 10 18:39 aml_upgrade_package_
-rwxr-xr-x@ 1 Apple  staff     1176432 Jan 10 18:42 u-boot.bin.sd.bin

Is there something useful here?

Edited by skyfly555
Update info

Share this post


Link to post
Share on other sites

Thank you amirul will give meson-gxm-q200.dtb a try.

 

Odd thing is that for server mode on all of the other S912 boxes (3Gb, Gb NIC) the meson-gxm-khadas-vim2.dtb works great.

IE:

TicTid X9T Pro - S912 - 3Gb - Gb NIC

TX9 Pro Amlogic S912 - 3Gb - Gb NIC

 

It is only on this box (T95Z Max)  that I cannot get the network ethernet running.

 

I prefer to connect these boxes used as servers via their ethernet connection over their wireless connection.  BTW Wireless is working perfectly.


 

ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c4:2a:fe:36:11:32  txqueuelen 1000  (Ethernet)
        RX packets 579  bytes 79088 (79.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  

eth0:avahi: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 169.254.5.7  netmask 255.255.0.0  broadcast 169.254.255.255
        ether c4:2a:fe:36:11:32  txqueuelen 1000  (Ethernet)
        device interrupt 20  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 880  bytes 65120 (65.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 880  bytes 65120 (65.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.244.252  netmask 255.255.255.128  broadcast 192.168.244.255
        inet6 2601:244:4000:dc3:55cc:f13:e04e:f6a8  prefixlen 64  scopeid 0x0<global>
        inet6 2601:244:4000:dc3:3553:1ac8:be38:3e25  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::944c:1fa5:37b0:bab2  prefixlen 64  scopeid 0x20<link>
        ether 6c:21:a2:4e:68:d8  txqueuelen 1000  (Ethernet)
        RX packets 3273  bytes 4687586 (4.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1123  bytes 110440 (110.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Seeing the same with meson-gxm-q200.dtb file.

Share this post


Link to post
Share on other sites
On 6/19/2019 at 10:01 AM, Peyton said:

Don't know. I saw ppl with km9 flashing km3 but it could brick your device. If you have usb/usb cable you can flash it with USB_Burning_Tool

 

km9 aosp : https://drive.google.com/file/d/1uMkgYrIHXbPDnrFnThWraEBpk5GHN5RR/view

 

original km3 : https://androidpctv.com/firmware-mecool-km3-rom/

 

For your info i've just tried with Armbian_5.88_Aml-g12_Debian_buster_default_5.1.0-rc1_20190609.img and it's the same..

 

Boot without any network interface except lo. :(

Hi, Someone knows If Android TV 9 has locked the boot process that to prevents the already documented process to start Armbian by doing the update process from android?

 

@balbes150...What is your opinion of my question? I very much appreciate what you can tell us about this topic.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
43 43