RaptorSDS

@Mr-TNTplease can you send some picture of board , there are 2 boards with problem first wherer the right LED-Config has to been set with ssh after flash per LAN , the secound has a close bootloader which need a diffirent OPTEE area wich need to be flash seperatly overall normaly when sd-card boot work than later it should also boot from that , yyou can also flash armbian direct to sdcard and also try to boot from sdcard maybe as short term solution

thank you for more info in orginal post , please tell us wich LED config do you use ( LED config also determing wich Enable Pins used example wifi enable) also trl870+ also not common one did other ubuntu or debian are support rtl870+

understand but fake and cheap is always a topic , we have story about fake the fake , cpu --> like sell as amlogic , report as rockchip , label as motorola and inside it was a rk3229 memory micron chp id that even micron dont know wifi chips from iphone that was reused maybe you flash a rk322x bootloader and its old rk30xx chip or newer rk33xx chip ( maybe thats why uboot from 2024

and now ?? read the glasball maybe some information would be nice also rtl870+ is usb ? because normaly this box has cheap old wlan modules

there is no 4GB version of rk3228 you mean 4giB or 1GB Ram because of uboot from 2024 maybe still a closed bootloader , normally every bricked box still boot from usb or sdcard ( like on page one there is no real soft brick , only hard brick of memory chip fail)

why this , i thing most of usb wifi adapter ( WIFI N or AC at 2.4GHZ ) are realtek 81xx or some RTK88xx , that are good support and already inside this armbian ,also some Broadcom USB things . please be arware most of 5GHZ WIFI AC ( dual Mode) are not as good supported at linux

normally all are compatible but there are no 3228H , there is 3328A and 3228B and 3229 (all same ) but like we say always there are so many creepy box outside with so many variant hardware and HW quality there are always some issue . you can follow the tutorials

two methods , 1. boot image first than automatic resize to bigger size ( most of the drive) , than put your image on card 2. use the compressed image of armbian on the sd card , the multotool also can use zip and tar and tar.xz and tar.gz

wirte the armbian image to SD Card and than insert and start , than it should boot from SD card like the multitool i had nowadays 4 of this box, one old AMlogic s802 ( over 5 years in use with armbian scan and printserver) ) 1 xrk322x that work out of the box with armbian , one rk322x with resolder wifi from wired china chip to rtl8723ds , and now a rk3328 with android ( sadly sd card is on wrong sdio port)

BCM433x are normally good supported , do have rk322x-config and setup the right led config its help also with wifi enable signal

this looking not as rk322x , i thing thats another main chip like rk328x or newer , we see some box that boot multitool without rk322x

Please can you be more clear did armbian boot befor without hdmi but with wifi ? or only android had wifi ? did you have a bootlog or dmesg with dmesg | grep 8723 or dmesg | sdio ; maybe dmesg | grep - i 8723 if this is positiv than only a driver issue , else also DTS/DTB maybe dont activate the wifi sdio

please also show picture of boeard maybe board print name , some R29 boards have diffirent pin setting so ist maybe one of this creepy and non standart boards

When a script is possible than uENV.txt should be the best point , also in thinging of rk322x-config where a question for user can be implement my thought was more that we support Multitool with 2 small xz files extractet and from 24.xx image and 21.01.01 image ( maybe later get update in newer multitool version) , and when he has problem he can use a new item point where the bootloader get write like the script above #!/bin/bash set -e # Path UENV_FILE="/boot/uENV.txt" # read variable out of uENV UPGRADEBOOT=$(grep -Po '(?<=Upgradeboot=)\d' "$UENV_FILE" || true) #or this maybe better UPGRADEBOOT=$(grep -Po '(?<=Upgradeboot=)\d' "$UENV_FILE" || echo "1") # Proof, Upgradeboot=0 if [ "$UPGRADEBOOT" -eq 0 ]; then echo "Upgradeboot is deactive, Installation abort." >&2 exit 1 fi preinstall script

thats maybe a point which be can handle by multitool where the user has a option point (choose) , when have problem be more compatible (perfomance reduce) optee , when perfomance (with my incompatiple eg power-off ) flash TrustOS maybe with a hint that after a apt-Upgrade procedure has to renew