Hqnicolas

About RAM: the problem is the wrong miniloader.bin on internal MMC try flash a different image inside to miniloader.bin detect 8gb RAM Start with this file Convert to DTS Translate it to Linux using the station P2 or M3 base DTS Apply the example And test it this only works on original device from image since you´re messing with different device, it doesn´t work how can you do an internal MMC image: all the files on this tutorial came from my device, you will need to extract your own files from your own device Now you create an 2 step trick image for internal MMC use it like this tutorial:

I made the changes to work on your device see there in the topic I created for your device @Kenneth Hidalgo

@gersones @Werner Please move this topic to chinese gadgets more complicated than my ex girlfriend

Hints and tricks First MOD to do is: Disabling all USB to test the station-p2 DTS if the boot happens, enable only the ones you believe work how? on station-p2 DTS inside your armbian compilator folder arch/arm64/boot/dts/rockchip

these warnings are only for being an android dts instead of a linux dts, nothing to worry about now you have to work on these files, if your device has an sd card it is easier, because you will just put the dtb file inside the sd card and test it this is all you need to create this image, first step: Compile armbian on linux desktop station-p2 mainline https://docs.armbian.com/Developer-Guide_Build-Preparation/ dont forgot to do it with modified DTS file that you edit like the example How? SET the armbian compilator to build custom kernel build, When the compilator stop to modify your kernel: drop the DTS inside the arch/arm64/boot/dts/rockchip folder that contains the DTS files since the modified file is inside the folder you can acept the kernel modifications and Run the build for station-p2 and BOOOOOOM You will find it here https://github.com/armbian/linux-rockchip/tree/rk-5.10-rkr4/arch/arm64/boot/dts/rockchip or inside your armbian compilator folder arch/arm64/boot/dts/rockchip (better files) you will need a lot of calm and patience to carry out the translations How you can make this android DTS work on linux: Like i said: https://forum.armbian.com/topic/28841-efforts-to-develop-firmware-for-hk1-rbox-r2-4g64g/?do=findComment&comment=166788 Lets Start with an example: On Vontar KK max Android DTS you have: and on Linux Rockchip: So we can do an Vontar KK MAX compatible: do this again and again to adapt the devices in the station-p2 DTS FILE many times in mainline you can do some tricks like disabling all usb

@gersones you have 1 device, and your android ROM have 3 different DTB's so we conclude that your device has 3 different types, with variations that can be LAN or video, usb, some variations have. now you will need to decompile the DTB file onto DTS. On linux: dtc -I dtb -O dts -o 01-android.dts 01-android.dtb dtc -I dtb -O dts -o 02-android.dts 02-android.dtb dtc -I dtb -O dts -o 03-android.dts 03-android.dtb these 3 files will be necessary for the other users who will ask you for the armbian image and will not be able to run it, because their device is another one of these three. so let's do the total process for the 3 files. post here the 3 decompiled dts files from android

Click Here and do it. you will need to publish all of them in your topic since every DTB correspound to a device type, 4gb, 8gb, differente lan card... etc

The link to the method

This is the Vontar kk Max? That's happens because incompatible loader.Bin Your device uses different memory.

With the firmware working very well, I mean.... Can I flag this firmware as "working"? As I said, I don't have this 8gb cheap Chinese box I just have the cheapest cheap 4gb chip

Just flash the original Android firmware again. If it doesn't work you will need to: do the clk - gnd short on emmc And connect the device at the same time After connect, just release the short Probably you will find a tutorial on 4pda forum If you Post two side pictures from your board hardware here, I will show the clk and gnd pins It's unbreakable like a rock cheap

I need your help to solve the problem in USB 2.0 not working DTB

@gersones and @mvpwar Link updated to Update.img, can you test it again? I'm waiting for prince charming to solve the usb 2.0 problem

finally an adventurer to test this shit I made, now I'm going to redo it and publish it again when it is recompiled I will ask you to test again remembering that this is not my device it's just an adaptation for 8gb New Link Start from scratch! Create a new topic, and name it: "Efforts to develop firmware for Vontar KK Max 4gb/32gb" put pictures from your device and links to the android ROM images that already works on device apply this method to decompile android image share the DTB files, the uBoot files, the miniloader.bin all on your topic my case took more than 8 months to show any result but now we are on kernel 6 and things got faster, look this example

the topic H96MAX have an description how to create a MMC flashing image "legacy u-boot" ask on wrt forum and bring that to our topic can you edit the legacy uboot to the same config as the mainline for LAN? Found some Github posts Github is blocked on my work so i get it from google cache.... This problem also happends on N2 you will find a armbian solution.... @ewww

and about the fix the RGMII to keep the same legacy uboot? you're building entire uboot just because misconfig lan card?

this is the same legacy uboot you use before. mainline may look like this "u-boot.itb"

@maka please share the DTS and DTB files here to other users work around next steps did the wifi works?

@maka @ewww can you post this DTS file and a checklist? exemple: runs kernel 6 ✔️ Detect USB 2.0 port ✖️ ethernet gigabit ✖️ display video HDMi ✔️ detect internal MMC ✔️

Did you try to fix by RGMII side?

it is working with async timmings. it's an know issue To armbian, we use legacy uboot kernel. in your case, the RTL8211F dont accept to start with legacy uboot and switch to mainline armbian

the fix, their is a mismatch in " mainline " vs " downstream uboot " that causes its clock "fix up" based on the kernels DTB set the wrong clocks for (at least) GPLL and CPLL. Fixing this the RGMII interface now works as intended. You will need to create a mainline Uboot or fix the RGMII

welcome to armbian, TVBoxes isn't supported here. So, you will need to done all by your own. See My example before read this and follow this guis

Be carefull, This value coud be a phandle. the phandle is an redirect pointer. # when you sent redirect = <0x4f>; # the device redirect it to something like usb2phy2@483e8000 { compatible = "ti,am437x-usb2"; reg = <0x483e8000 0x8000>; ctrl-module = <0x4c>; clocks = <0x1a 0x4d>; clock-names = "wkupclk", "refclk"; #phy-cells = <0x0>; linux,phandle = <0x4f>; phandle = <0x4f>; };

Considere doar o seu hardware para a comunidade Armbian.