gersones

@Energokom Unfortunately, I didn't find any and forcing a "apt full-upgrade" will break the box from booting. I just gave up. If it has only 4GB of RAM and was sold in a deceptive way, considering the performance as a desktop (watching Youtube videos in the browser), I wouldn't disagree that both CPU/GPU are made the same way and present low performance (for a box "capable" to play "8k" content). I'd just use it for playing (server lab/testing) and things like that.

wtf...why? that's a lesson: never buy unknown chinese products again. thanks, @hotnikq

thanks, @hotnikq Unfortunately, again, only 4gb were recognized. I think I'll just give up for now. Maybe I'll try to build from zero someday but I just can't deal with the learning process right now. When done, I'll post the results here. Thank you

@ufsm Thanks so much Unfortunately, none recognized 8gb of ram BUT they'd worked* (updates included, except for the linux-headers-* and/or linux-image-*, because it says there's no space left in the disk (partition I believe)). Xfce worked almost perfectly (only superficial tests) while in Gnome there are micro stuttering (only tested these) but I think it's because the box's hardware is weak. *no sound while station-m3 have sound @hotnikq Thanks for complementary instructions. I'll try to do the tutorials asap. One more thing guys: using the tool I mentioned to extract the .dtb files from boot.img is okay or do I have to use the imgRePackerRK_107 once more on boot.img (because I did it and it generated a "dtb" (no extension) and "dtb.cfg".

if none of the .dtb files make the system recognize 8gb, that means the kernel or its architecture is the limitation? the 01.dtb crashed at boot (kernel panic) the 02 and 03.dtb booted recognizing 4gb only but everything else (wifi, lan, audio and even usb 2.0 - didn't test bluetooth) seems to work. though I did a nand-sata-install (don't remember exactly if this was the command) to the emmc but it didn't boot. I reiterate that these were all tested on a armbian station-m3 (not station-p2, which booted with the rk3566-firefly-roc-pc.dtb but didn't allow me to update the packages in the system). so are you sure I'll have to make the images with station-p2? (sorry but just want to make sure before I begin). thanks for the instructions @hotnikq this might take many weeks before I post again, okay? have other work during week days and sometimes even during weekends. this is just my "playing" time (still don't know if I'm enjoying it or just had nothing else to do lol)

dts files 01_rk3566-box-demo-v10.dts 02_rk3566-box-demo-v10.dts 03_rk3566-box-demo-v10.dts running the dtc command returned many warning messages like the one below, so I'm not sure if it worked...

posted: Efforts to develop firmware for Vontar KK Max 8gb/128gb

Vontar KK Max 8gb/128gb: Original Android 11 ROM image Which tag do I put (required field) since there's no rk3566 available and the Armbian image that worked for me is the station-m3 ones? DTB files: 01_dtbdump_rockchip,rk3566-box-demo-v10.dtb (can't attach: "Sorry, an unknown server error occurred when uploading this file. (Error code: -200)" message) ok 02_dtbdump_rockchip,rk3566-box-demo-v10.dtb ok 03_dtbdump_rockchip,rk3566-box-demo-v10.dtb *obtained using the extract-dtb tool I don't know how to join these into a single .dtb to point at into the working Armbian /boot/extlinux/extlinux.conf file. the only .dtb file that worked for me with the station-p2 (not posted here because it crashes and won't boot anymore if I made run "apt upgrade" which would be desirable) station-m3 image but only recognizes 4gb RAM: rk3566-firefly-roc-pc.dtb (idk if this is due a kernel's limitation or the hardware information contained in this .dtb file) if somebody could tell me... Loader file: ok MiniLoaderAll.bin uBoot file: uboot.img (can't attach: "Sorry, an unknown server error occurred when uploading this file. (Error code: -200)" message)

About the new topic: Which tag do I put (required field) since there's no rk3566 available and the Armbian which worked for me is a "station-m3"? About my attempts: I was able to extract multiple .dtb files from the boot.img (unpacked from the original Vontar KK Max firmware) but I have no idea how can I join these 01-first.dtb 02-second.dtb 03-third.dtb files into a single .dtb that I'll try to put into the working Armbian and point it in extlinux.conf to see if the 8gb RAM are recognized or if it's the kernel's limitation.

Understood. Lastly, do you know any method to extract the original .dtb (as Android systems "are" Linux, they also work with .dtb binaries?). If so, I'd need to extract mine because the only .dtb that worked with my device so far only sees 4GB RAM instead of the 8GB. But I don't really know if this limitation is the image limitation (kernel used) or if is a .dtb that specifies only 4GB RAM. Anyway, I'll stop posting here about Vontar KK Max and will create a new topic. Thanks @hotnikq

@hotnikq Now the update flashes but when it's done it goes to Maskrom mode no matter how many times I disconnect/reconnect while pressing the back button with a toothpick. But I think my male usb to male usb isn't reliable since it fails many times to connect into both loader or maskrom while pressing the back button (now I think this was the problem I faced earlier). I have no idea why a reboots "fix" it but I'm able to flash only once then I start to get these issues. Sorry. I'll try to buy another cable asap.

@hotnikq Okay, now I understand absolutely nothing. Excepted the fact that I was able to boot Armbian as I told, everything (PC, electronics) went wrong "today" (now is "tomorrow" already in here). After solving my computer BIOS little problem, I tried to flash the stock firmware (Android 11) with the RkDevTool and it did (I tried about thirty times or more for real). I'm coming to the conclusion that I'll never understand anything about "computers" (gadgets and related thing in TIC) and how it works nor how it doesn't work. I'll try again (Armbian that had worked) and give an update. Regards

Sorry @hotnikq but you don't have to bother anymore (about Vontar KK Max). I think I just bricked the device though I read somewhere Rockchip devices were unbrickable. I was so close to make it because I finally was successful in booting into Armbian (bookworm - kernel 5.10.x) and I f**ked it when, in an attempt to write it to the eMMC, I accidentaly erased all the partitions instead of letting the bootloader partition alone. Now my box doesn't get out of Maskmode anymore, no matter what I do. I tried different versions of RkDevTool but I think I have no idea of what I'm doing anymore. But thank you anyway.

Thanks, @hotnikq! @mvpwar But I'm having the same issue! I tried on RkDevTool v2.95 and v2.86. Unfortunately, I still know nothing about how to build an image from scratch so I'm looking like crazy for one that will work on my Vontar KK Max (yeah, I know this is for H96 Max but, as I said, I'm desperately already because it was not so cheap). I really hated the Android 11 UI of this box (tried another launchers but none is better than the stock). So I think Armbian would be a much more useful for it.