Karthik T

@radzki While not an allwinner H3 box, I had an Amlogic box that I used libreelec on, and after that booting from Armbian kept failing. You could try a factory reset from the "current image" presumably android and see if that changes your experience. Bit more detail at

Thanks for your confidence and company @Nick A I am glad i took another deeper dive..

Err... I have no idea what happened.. In all this resets I check `ip addr` and I see wlan0 thr.. I could swear I checked it and it wasnt before.. I installed `network-manager` and was able to get the wifi connected and working..

I did a symlink to a clm_blob that was present and the dmesg changed a bit. [ 7.548281] r8152 2-1.3:1.0: Falling back to sysfs fallback for: rtl_nic/rtl8153a-4.fw [ 7.608116] systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... [ 7.633616] systemd[1]: Reached target bluetooth.target - Bluetooth Support. [ 7.653242] systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status. [ 7.678063] zram0: detected capacity change from 0 to 1020768 [ 7.679530] ieee80211 phy0: brcmf_c_download_blob: clmload (4733 byte file) failed (-52) [ 7.680437] ieee80211 phy0: brcmf_c_download_blob: get clmload_status failed (-52) [ 7.680473] ieee80211 phy0: brcmf_c_preinit_dcmds: download CLM blob file failed, -5 [ 7.680486] ieee80211 phy0: brcmf_bus_started: failed: -5 [ 7.680513] ieee80211 phy0: brcmf_attach: dongle is not responding: err=-5 [ 7.707369] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed [ 7.711698] Adding 510380k swap on /dev/zram0. Priority:5 extents:1 across:510380k SS [ 7.947193] zram1: detected capacity change from 0 to 102400

I see it is trying to load `brcm/brcmfmac43430a0-sdio.clm_blob` but the device only has `brcm/brcmfmac43430a0-sdio.bin`, and .txt, should it have clm_blob?

Hey, @Nick A here is the dmesg https://pastebin.com/AKP6tdKX The relevant bit is likely [ 7.668535] r8152 2-1.3:1.0: Direct firmware load for rtl_nic/rtl8153a-4.fw failed with error -2 [ 7.668569] r8152 2-1.3:1.0: Falling back to sysfs fallback for: rtl_nic/rtl8153a-4.fw [ 7.679766] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.clm_blob failed with error -2 [ 7.679798] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430a0-sdio.clm_blob [ 7.736675] systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... [ 7.768622] systemd[1]: Reached target bluetooth.target - Bluetooth Support. [ 7.780124] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 7.780153] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 7.780892] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/0 wl0: Jul 1 2016 18:02:40 version 7.10.1 (A0 Station/P2P feature) FWID 01-bae8afee [ 7.784507] systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status. [ 7.816592] zram0: detected capacity change from 0 to 1020768 [ 7.828732] Bluetooth: hci0: BCM: chip id 94 [ 7.829421] Bluetooth: hci0: BCM: features 0x2e [ 7.831802] Bluetooth: hci0: 4343A0 [ 7.831843] Bluetooth: hci0: BCM4343A0 (001.001.034) build 0000 [ 7.837654] Bluetooth: hci0: BCM4343A0 'brcm/BCM4343A0.hcd' Patch [ 7.852062] Adding 510380k swap on /dev/zram0. Priority:5 extents:1 across:510380k SS [ 8.092132] zram1: detected capacity change from 0 to 102400 [ 8.143675] systemd[1]: Finished armbian-zram-config.service - Armbian ZRAM config. [ 8.173101] systemd[1]: Starting armbian-ramlog.service - Armbian memory supported logging... [ 8.258237] EXT4-fs (zram1): mounted filesystem a960efb7-2ddb-4b74-b890-02db439f3633 r/w without journal. Quota mode: none. [ 8.617334] Bluetooth: hci0: BCM: features 0x2e [ 8.620034] Bluetooth: hci0: BCM4343A0 26MHz AP6212_CL1 OTP_BD-0061 [ 8.620075] Bluetooth: hci0: BCM4343A0 (001.001.034) build 0245 [ 8.729100] systemd[1]: Finished armbian-ramlog.service - Armbian memory supported logging. [ 8.756443] systemd[1]: Starting systemd-journald.service - Journal Service... [ 12.827907] systemd[1]: systemd-rfkill.service: Deactivated successfully. [ 68.599453] r8152 2-1.3:1.0: unable to load firmware patch rtl_nic/rtl8153a-4.fw (-110) [ 68.634262] r8152 2-1.3:1.0 eth0: v1.12.13 [ 68.634675] usbcore: registered new interface driver r8152 [ 68.647431] usbcore: registered new interface driver cdc_ether [ 68.650104] usbcore: registered new interface driver r8153_ecm [ 68.708140] systemd[1]: Started systemd-journald.service - Journal Service. [ 68.768773] systemd-journald[388]: Received client request to flush runtime journal. [ 68.771384] r8152 2-1.3:1.0 enxa0cec873285e: renamed from eth0 [ 70.227164] r8152 2-1.3:1.0 enxa0cec873285e: carrier on

@Nick A I am going based purely on the fact that the 2 sunxi links I posted above both reference `Ampak AP6212`. I am quite new to this level of armbian/linux, and am not sure if 1. The wiki is accurate. For the draco, I havent opened the case yet because it seems quite fiddly and might be destructive to open. 2. If there are differences between revisions/versions of the boards which means there is a difference from the build to my tv stick. 3. If Ampak AP6212 means the same firmware or if there are revisions within this chipset itself. I will check and post the dmesg tonight.

Thank you so much for the response. >Maybe you are missing the drivers for your wifi. I assumed that, wouldnt Banana Pi M2 +, having the same chipset as mine, use the same driver? Is it just a matter of turning it on somewhr? > You can find the firmware in your original Android backup. I really wish I hadnt written to emmc.. or had taken a backup before that 😐 let me try to do more research and see if I can find firmware for this thing.

Thank you! and Thanks for your work with Amlogic boxes, that was my previous rescue from ewaste.

Apologies this isnt about Orange Pi Zero 2, but about a TV stick called Tronsmart Draco H3 which I have and am trying to repurpose into a light weight server with armbian. It obviously isnt well known, but I have tried a few H3 based builds, all of them boot fine, but I cant seem to get Wifi running. I tried Orange Pi PC and Orange Pi but they dont have Wifi at all I believe, so it didnt ask to setup wifi. I tried Orange Pi Zero 2+H3, but for some odd reason my keyboard didnt work on it, so I couldnt setup the users to be able to get further. I tried Nano Pi R1, but that didnt have HDMI, so my hdmi didnt work and I had no idea how to view the output at that point. I tried Orange Pi + as that had wifi as well, but the wifi wasnt able to be configured. I then figured that I need to get a board with the same wifi chipset as mine, and settled on Banana Pi M2+ which matched on RAM, SOC and Wifi chipset, but it still had the same problem as Orange Pi+ in that it asked to setup wifi, but then fails immediately with unable to configure. Any tips on how I can proceed? I understand that recovering esoteric TV boxes isnt looked on fondly here, but I am curious to see if I can make this work. p.s. Ethernet does work with this box and the banana pi m2 + build, but I would need an ethernet to USB dongle, and ofc the cable.

To add my own reason to the above list of reasons to use the TV boxes, It is a simple use case, and I get to keep a TV box out of the electronic heaven in the sky for a little longer, and save a new purchase. It also turns out my TV box was a little bit faster than my main "server" the PineA64 board.

I was able to perform a Factory reset from the android side, and that let me boot from my armbian usb stick. Factory reset from the recovery menu did not work though.

@Vito Dgb I am trying to follow this guide on an old TV Box. I have also tried CoreElec on it via USB, but not installed to emmc, that worked fine. However with Armbian, if I do the toothpick method, I go to the android recovery menu with some error about /misc partition not found. Is this what you mean? Can you elabourate more on how you got it to boot?