gerotmf

Change usb cable first. Had similar problems with one of my pi4s .. and it was new cheap chinese cable. Also check dmesg and see if there is something with usb logged there lile recconect or disconnect msgs. Sent from my SM-S901B using Tapatalk

Yes, that's why i think it's gone. It was finicky from the box. The other one - i have 2- is ok. So far. Sent from my SM-S901B using Tapatalk

@jock well tv box was acting up from the start (had to reflash original android rom from the start) , i've also tried 333Mhz idbloaders from the link you posted (sd boot into clean armbian, backed up original, dd to sd card, erased flash beforehand so that it will boot it).. but that killed the box .. like completely, now it doesn't even go into maskrom mode (av port button and usb a/a cable in usb2 port). I guess i can close this case it is weird though, the second box i bought for a friend, works ok.. although i must recheck that now, maybe under load it will also crap on me.

@jock Thanks for the answer, i did catch this at some point, but it's not the same every time

Hi, I have a rk3318_v.14 box, which has kingston emmc and some micron ddr memory which should be brand new but looks tired ... well i've installed armbian (minimal/cli, 23.02) on it (emmc), it boots up and i have wifi, eth, usb, hdmi working, i can even apt install amrbian-config, configure it and everything seems to work ok, until there is some serious load, like f.e. apt install gcc-arm-none-eabi .. that will start gunziping and just freezes, i can log into other ssh session, but any command i issue is blocked. I'm trying to find uart on this board but no luck so far. I've also extracted dtb/dts from original android firmware, under which it looks like box is working ok (tried copying 4GB files to emmc and such, no problems) which is located here https://drive.google.com/drive/folders/1a_lbHo4umDN56KeOWw0elDGhz6VE1LGF?usp=share_link but since my dtc guru is nonexistent i really can't make anything out of it. I've tried diffing with armbian's rk318-box.dtb but like i wrote, can't figure out what to look for... my first suspect was emmc so i also tried running from sd card with similar results. second guess is cpu power supply, where there are some diffs in dtb, Anyone has any suggestions, or can check that dtb if there is something obvious Tnx,