MattWestB

If you have one backup of the original firmware or log from it then booting perhaps @jock can helping digging what is needed for getting the WiFi card being powered on but this boxes is little trashy how they have implementing the hardware.

The Linux kernel is not detecting the WiFi card then its need the power being enabled by one GPIO from the system. Try other LED / board config in rk3318-config and also look in the head of it if its showing if the system have detecting some card (your screenshot its written: Wifi device: Not available) after doing the change and rebooting the device (some config can making the device not booting at all !!).

If you have selecting one working (LED)configure in rk3318-config you shall have somthing like "brcmfmac" then the chip is initiating and then more then the system is loading the firmware in it in the log and i have not seen it then looking. In your log i see: [ 2.987024] mmc3: Failed to initialize a non-removable card [ 3.032919] mmc1: Failed to initialize a non-removable card and mmc0 is not conected and mmc1 is the eMMC

With RKs tools its possible erasing the eMMC and the chip shall trying boot from SD-card (then eMMC is empty / no bootloader on it) with boot loader on it like Multitool (not USB devices). If you is good on counting you can flashing all with the tools but must putting all in the right place for getting it working at all so not recommended.

WAN (Wide Aria Network) = your external internet connection routed to your ISP (so the ISPs IP adrress) from your home network and not WiFi interface of the box.

Some board have no standard HDMI config and is not being activated on standard boot with Multitool and other Armbian images. Best is trying one current multitool on SD-card and booting and look on the LED if its continuous lighting or start flashing slowly after some minutes (first boot takes longtime then resizing the SD-card). If getting blink = system have booting OK. Then connect with SSH to the device (thru Ethernet or the comport on the PCB) and making the mulltitool things. After installed do the same on the installed Armbian.

RK322Xs is 32 bit ARM CPUs and can only running 32 bit OS so not possible installing aarch64 OS on the hardware. Also it have not enough RAM (normally 1 or 2 G) for running very large docker containers.

@ToShuk Look in the log if the eMMC is in read only mode or if other error code. I was having one RK2328 in read only mode but was unbricking it with RK factory tool but it was not easy. And i have 2 RK3318 boxes with bad eMMC so using SC-Card then cant recover the chip (looks like ODRID have getting there external eMMC unbricked with the same chip but was doing it in very early kernel boot with script).

@Asriel Nguyen The board looks very not RK3228 like but your lsusb is saying it one in maskrom mode so shall being one but no initial booltloader in the eMMC = shall booting Multitool / Armbian OK from SD-Card (but not direct from USB sticks). Only PM is if the card reader is on the standard address or being on other then its not working. Do you have some high res picture of top and bottom of the PCB then cant see the small components and printing ?

Armbian Noble V24.11.X base-files broken _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v24.8.4 for rk322x-box running Armbian Linux 6.6.63-current-rockchip Packages: Ubuntu stable (noble) Support: DIY (community maintained) Its up to date and the kernel and system is the 24.11.1 armbian-bsp-cli-rk322x-box-current is hold back then its depending on armbian-bsp-cli-rk322x-box-current : Depends: base-files (>= 24.11.1) but 24.8.4-13ubuntu10-noble is to be installed That is not existing for all 32 bits arm. apt list -a base-files Listing... Done base-files/noble,now 24.8.4-13ubuntu10-noble armhf [installed] base-files/noble 24.5.5-13ubuntu10-noble armhf base-files/noble 24.5.1-13ubuntu10-noble armhf base-files/noble 24.2.1-13ubuntu7-noble armhf base-files/noble-updates 13ubuntu10.1 armhf base-files/noble 13ubuntu10 armhf Technical its Ubuntu Noble V24.11.1 only the base-files is failing so the the welcome screen is writing wrong information and other programs that is reading it from the system

@wanton beis Your device is having eMMC and no nand flash. If flashing factors Android on the bootloader in the eMMC can only booting eMMC or old bootloaders from the sd-card like Multitool. If eMMC is empty the SOC is looking for one sc-card for bootloader and if you have written one new arbian image on it it shall finding it and booting OK and also can booting USB-flash from the sd-card (jump starting). Then writing Android or one old Linux on the eMMC it can only booinng from eMMC system or sd-card all with old system so need updating the bootloadre in the eMMC or erasing the eMMC for booting newer systems from the sd-card and gettig jump loading of USB-flash.

Thanks @haven for the replay then im not alone with this issue. Was looking on the PCB and its one Toshiba THGBM9G9T8KBAIG but cant finding datasheet of it only some summery on AIX and i think the PCB is using wrong voltage for the flash and after some mouths its being fired and cant being recovered.

2 of my "new" H96 Max RK3318 V11 with display was stop using the MMC (around one week between and first running Armbian and the other Android 11). The booting SD-Card i finding this in the log: [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: IDMAC supports 32-bit address mode. [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: Using internal DMA controller. [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: Version ID is 270a [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: DW MMC controller at irq 37,32 bit host data width,256 deep fifo [Wed Nov 27 16:08:54 2024] mmc_host mmc2: card is non-removable. [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:55 2024] mmc2: Failed to initialize a non-removable card Was looking for the android firmware and using factory tool and the device is going in maskrom mode then pressing the "pin button" and connecting it to the PC. Flashing the Android firmware and its still showing Maskrom. Re connecting it and its not starting. Putting in Armbian SD-Card and its booting Armbian OK. Doing the same test with the second box and the same result. Conclusion: MMCA Version 6 = hard bricked MMC. So now need baying some A2 SD-Card for running Armbian and no Android TV with IPTV. If some have experience of recover not working MMC pleas share it and you thinking.

@ExUser 44 From the first post download and flash multitool on one SD-Card (USB is not supported by factory android bootloader) and put it in the box and power on. Make one backup of the eMMCand then shutdown the box and copy the backup to one safe place. Download one Armbian from links in the first post (stable Ubuntu or debian server or desktop). Copy the tar file to the (multitool) sd-card image folder and puting it in the box and power it up. The safest and brutal is erase eMMC and write the Arbian image to ti but can being one brick. The more safe is only erase the eMMC then the SOC is not finding boot-loader on it its trying booting from sc-card . If only erasing eMMC you can burning Armbian on one SD-Card and the system shall booting from it and cant being bricked. Then getting it working try writing the eMMC with multitol and hope its working well (then you also getting USB boot support).

Thanks for great work @Jean-Francois Lessard !!! I think the trigger was not loaded OK with my manual install. My 2 boxes is for the moment HA in production and the second one is updated Android V11 (from V10) then it was having problems running large IPTV (corrupting the files system) that looks working OK now. Then i have getting all stable and also can getting HyperHDR also running (USB problems . . . with V1.4 hardware but one other box looks doing better but not the USB3) i can doing one rockade and doing more testing.