Hqnicolas

This is a problem? It's running kernel 6.2? Or the old kernel 4.2?

Welcome to Linux My god, you have that old image? It works on 8gb devices? Please Share it here with Google drive I have deleted it @Kenneth Hidalgo need your image to 8gb devices

First I add SD card to test the dtb files faster Then I create the internal flash 2 step Now I just flash the MMC when I need to clean install No SD SD card since v0.7 firmware remembering that you should change only the update.img file that initializes the device The root.img contains dtb file that works on both 4gb and 8gb devices

Create an Parameter.txt File like this FIRMWARE_VER: 12.0 MACHINE_MODEL: H96_Max_V56 MACHINE_ID: 007 MANUFACTURER: rockchip MAGIC: 0x5041524B ATAG: 0x00200800 MACHINE: rk3566_box CHECK_MASK: 0x80 PWR_HLD: 0,0,A,0,1 TYPE: EXT4 CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 root=UUID=c79ae8c4-0a9a-479b-b57f-ed7575bf5017 rw rootfstype=ext4 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles mtdparts=rk29xxnand:0x00002000@0x00004000(uboot),0x00002000@0x00006000(trust),0x00002000@0x00008000(misc),0x00002000@0x0000a000(dtbo),0x00000800@0x0000c000(vbmeta),-@0x0000d000(root:grow) uuid:root=c79ae8c4-0a9a-479b-b57f-ed7575bf5017 Extract from your android image uboot.img trust.img misc.img dtbo.img vbmeta.img and the "root,img" file you pickup from tutorial root image from this topic. put it all inside image folder on rockdev on rockdev folder edit the file package-file # NAME Relative path # #HWDEF HWDEF package-file package-file bootloader Image/MiniLoaderAll.bin parameter Image/parameter.txt trust Image/dtbo.img uboot Image/uboot.img security Image/parameter.txt #resource Image/resource.img #kernel Image/kernel.img root Image/root.img #recovery Image/recovery.img #rootfs Image/rootfs.img #oem Image/oem.img #userdata Image/userdata.img #backup RESERVED #update-script update-script #recover-script recover-script @mvpwar This is the 4gb/32gb device This is the 4gb/32gb device

You find it! Nice! Uboot for 8gb devices are newer So the loadder use address instead of name Just change the GPT address on parameter.txt I don't have this device to test, but it looks a great start

The GPT parameters you will find on Parameter.Txt

looks like the bootloader dont find the "root.img" partition inside EMMC............ ????did you try to flash both versions from root.img on 0x0000A000 ???

yes, you will need to work around the "update.img" file this is how i create the update.img https://drive.google.com/file/d/1k_VUDxwtc-ACayWx4PtAkef0jWk65-jK/view you can try to combine all MiniLoaderAll.bin with uboot.img files....

The bootloader is incompatible with you board, you will need to go back to android image. https://androidtvbox.eu/firmware-rk3566-h96-max-for-android-11-tv-box-update-20210810/ or try the linaro from @Kenneth Hidalgo https://drive.google.com/file/d/1FTOKB0pgqkLCJedyJrBq-qdONQ9KTM3-/view?usp=drive_link Since my Uboot + Miniloaderall.bin don't detect your board you will have to adapt uboot and miniloaderall.bin somehow if you can't flash this images you will need to short the CLK + GND with tweezers to enable maskrom mode these two pins are exactly opposite the emmc side of the board short it, conect the USB male to male USB release the short flash the regular ROM https://roc-rk3328-cc.readthedocs.io/en/latest/flash_emmc.html#maskrom-mode

I was on a trip, now that I could see all your posts. now i can see, you did all steps on other post. I see you have a debug TTL, and a board different from mine. I see you can run this method using this new box and parse the results @mvpwar publish the results of your board in this post here! since it's an 8gb/64gb

mmc0(part 0) is current device Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** You need to flash the part 2 tutorial Sent from my 22021211RC using Tapatalk

Check this pins. I have never tested this device but if you find the CLK and GND with a multimeter you can short it with tweezers https://roc-rk3328-cc.readthedocs.io/en/latest/flash_emmc.html#maskrom-mode

@Kenneth Hidalgo let's test another image how to install? https://forum.armbian.com/topic/24091-efforts-to-develop-firmware-for-h96-max-v56-rk3566-4g32g/?do=findComment&comment=166326 This is a new Update.img file for you to test

since this image works with your H96 MAX I create an update.img file based on your image....

today I will work in that image....

the armbian nand-sata-install just work on original device from your armbian build. To work in a TVbox you will need to follow this tutorial. or follow my tutorial to create an flash image, it's slow to create but faster to recovery the device.

Can you share a image that actually works on your device? Can be Android or Linux i think you already test this https://drive.google.com/file/d/1FTOKB0pgqkLCJedyJrBq-qdONQ9KTM3-/view?usp=sharing please confirm

@mvpwar and @Kenneth Hidalgo did you test the new version of this tutorial? it's flagged as untested until somebody came back here and reply this topic as "tested" just like you tested the first version

Sure, do it on the device that you trust to work, I've been tried at least 5 devices in my topic

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