Hqnicolas

Generating files again.... Result Update.img V4 execute step 1 with V4 update.img execute step 2 with root.img (from tutorial) set Address on 0x0000A000 set Name on root Update.img V5 execute step 1 with V5 update.img execute step 2 with root.img (from tutorial) set Address will be different value "0x00xxxx??????", you will need to seach for partition named root Please share this value if this image works For update.img V5 i used a different pattern for Linux Pack Firmware

Did it works? My files get corrupted

i did this with the imgutil on windows Download imgutil /x boot.img dtb Please test the V5 and V4 Before another different approach

just to bloat the file inside, it works on my 4gb device absolutly NOT, it's basically the same original android img file

Result: update.img V4 execute step 1 with V4 update.img execute step 2 with root.img (from tutorial) set Address on 0x0000A000 set Name on root update.img V5 execute step 1 with V5 update.img execute step 2 with root.img (from tutorial) set Address will be different value "0x00xxxx??????", you will need to seach for partition named root Please share this value if this image works For update.img V5 i used a different pattern for Linux Pack Firmware

ah it's to prevent Kernel panic on 4.19 it's my old kernel 😁 we are still at the ground point in this project for 8gb device...... waiting for your patch i will delete my 8gb update images since your test got an error on uboot I'll try again a desperate adaptation

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