Hqnicolas

@hzdm The result from your post ThankYou! Keep Pushing on Arm Devices!

####################### EMMC: V1.0 Release Version ####################### # Tested on 8gb device (16/11/2023) # Tested on 4gb device (03/11/2023) # Flash RkdevTool v2.86 Doesn't Work on Windows 11 Computers! How to build this images? V0.7 Root + Build Update What is that? Yes, it's a v0.7 update image, that you flash a little gpt file to repair partition on EMMC. So, you will use the same v0.7 Update images that you have. The Gpt file First Things First! Drop Config.cfg the RkDevTool config file on folder Righ click on white background from RKDevTool click on Load Config Select the Config.cfg Flash Update.img Restart device on loader mode Flash gpt.img The Gpt file Yes, you can Skip Root flash. But you can drop the v0.7 Root.img file on this device. Please Reflash GPT.img after new Root.img 🏆 help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. Since It will be the image that i use on my server, This is my Last Collaboration in this project, if you done something better, post it here. ################################ 8GB devices Fix ############################## 8GB device First Boot Comand: # this GPT file was generated from a 4gb device. # in 8gb device you will need to trick the gpt after instalation # First boot comand: fdisk /dev/mmcblk1 t 4 1 w On 8gb device Screen you will see: fdisk Welcome to fdisk (util-linux 2.37.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. This disk is currently in use - repartitioning is probably a bad idea. It's recommended to umount all file systems, and swapoff all swap partitions on this disk. Command (m for help): t Partition number (1-4, default 4): 4 Partition type or alias (type L to list all): 1 Changed type of partition 'Linux filesystem' to 'EFI System'. Command (m for help): w The partition table has been altered. Syncing disks. Now if you reboot the 8gb device, it will find the linux partition without no problem. gpt.img config.cfg

It's time for a new joint venture. using the @hzdm method, i create the single burn firmware. How to build this images? ######################## EMMC Server: v0.9 image Beta ######################## insert the gpt file to use the same image to burn different devices. First Things first: Read the RkDevTool config! For 8gb/64gb devices: Uncheck disable the GPT image file to flash. For 4gb/32gb devices: Check enable the GPT image file to flash. Lets flash! how? Follow the HZDM tutorial. 🏆 help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions.

Working in a solution for GPT over EMMC. Since this solution makes 8gb images work on 4gb devices I will try: https://opensource.rock-chips.com/wiki_Partitions this is the 4gb 32gb image GPT: Command (? for help): i Partition number (1-4): 1 Partition GUID code: DE110000-0000-4051-8000-460A00003284 (Unknown) Partition unique GUID: F51C0000-0000-455E-8000-20DF000015D9 First sector: 16384 (at 8.0 MiB) Last sector: 24575 (at 12.0 MiB) Partition size: 8192 sectors (4.0 MiB) Attribute flags: 0000000000000000 Partition name: 'security' Command (? for help): i Partition number (1-4): 2 Partition GUID code: 57090000-0000-4C1B-8000-2CC300006C3E (Unknown) Partition unique GUID: DC7B0000-0000-400E-8000-1A30000064FB First sector: 24576 (at 12.0 MiB) Last sector: 32767 (at 16.0 MiB) Partition size: 8192 sectors (4.0 MiB) Attribute flags: 0000000000000000 Partition name: 'uboot' Command (? for help): i Partition number (1-4): 3 Partition GUID code: 9E010000-0000-491F-8000-2EDD00003399 (Unknown) Partition unique GUID: F6680000-0000-4F67-8000-11C500006AE2 First sector: 32768 (at 16.0 MiB) Last sector: 40959 (at 20.0 MiB) Partition size: 8192 sectors (4.0 MiB) Attribute flags: 0000000000000000 Partition name: 'trust' Command (? for help): i Partition number (1-4): 4 Partition GUID code: 7D0B0000-0000-4D02-8000-2621000044DE (Unknown) Partition unique GUID: 5FA600DD-BFC2-4260-A3DA-562CB9D13F00 First sector: 40960 (at 20.0 MiB) Last sector: 61071326 (at 29.1 GiB) Partition size: 61030367 sectors (29.1 GiB) Attribute flags: 0000000000000000 Partition name: 'root'

@hzdm i create an Server image Based on your instructions. but my device is an 4gb 32gb device how can you change the GPT LBA from this files? there is a source of this start.img file? the initial error: Trying to boot from MMC1 GPT: last_usable_lba incorrect: X > 747bfde part_get_info_efi: *** ERROR: Invalid GPT *** part_get_info_efi: *** Using Backup GPT *** on device to repair the initial error, when "sudo gdisk /dev/mmcblk1:" it reveals the GPT partition is 57gb Disk /dev/mmcblk1: 61071360 sectors, 29.1 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EC944974-E823-4B58-AEB7-A94651D008F8 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 122142686 Partitions will be aligned on 2048-sector boundaries Total free space is 61407 sectors (30.0 MiB) Number Start (sector) End (sector) Size Code Name 1 61440 2158590 1024.0 MiB FFFF bootfs 2 2158592 122142686 57.2 GiB FFFF rootfs Command (? for help): i 2 Partition number (1-2): 2 Partition GUID code: 1124E418-9008-41F8-9E3D-8D872216C8A1 (Unknown) Partition unique GUID: 67AD7741-4638-47C6-A488-D396583E582A First sector: 2158592 (at 1.0 GiB) Last sector: 122142686 (at 58.2 GiB) Partition size: 119984095 sectors (57.2 GiB) Attribute flags: 0000000000000000 Partition name: 'rootfs' Command (? for help): i Partition number (1-2): 1 Partition GUID code: 8DCD1602-5214-43F9-FFEF-C49A4EE450B7 (Unknown) Partition unique GUID: 5A30833F-8C43-47B1-A41D-84D40883D0C6 First sector: 61440 (at 30.0 MiB) Last sector: 2158590 (at 1.0 GiB) Partition size: 2097151 sectors (1024.0 MiB) Attribute flags: 0000000000000000 Partition name: 'bootfs' How i fix this initial problem: boot from SD card..... and: root@station-m2:~# sudo gdisk /dev/mmcblk1 GPT fdisk (gdisk) version 1.0.8 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/mmcblk1: 61071360 sectors, 29.1 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EC944974-E823-4B58-AEB7-A94651D008F8 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 61071326 Partitions will be aligned on 2048-sector boundaries Total free space is 58974142 sectors (28.1 GiB) Number Start (sector) End (sector) Size Code Name 1 61440 2158590 1024.0 MiB FFFF bootfs Command (? for help): n Partition number (2-128, default 2): First sector (34-61071326, default = 2158592) or {+-}size{KMGTP}: Last sector (2158592-61071326, default = 61071326) or {+-}size{KMGTP}: Current type is 8300 (Linux filesystem) Hex code or GUID (L to show codes, Enter = 8300): 1124E418-9008-41F8-9E3D-8D872216C8A1 Changed type of partition to 'Unknown' Command (? for help): x Expert command (? for help): c Partition number (1-2): 2 Enter the partition's new unique GUID ('R' to randomize): 67AD7741-4638-47C6-A488-D396583E582A New GUID is 67AD7741-4638-47C6-A488-D396583E582A Expert command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): y After solution: root@station-m2:~# sudo gdisk /dev/mmcblk1 GPT fdisk (gdisk) version 1.0.8 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/mmcblk1: 61071360 sectors, 29.1 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EC944974-E823-4B58-AEB7-A94651D008F8 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 61071326 Partitions will be aligned on 2048-sector boundaries Total free space is 61407 sectors (30.0 MiB) Number Start (sector) End (sector) Size Code Name 1 61440 2158590 1024.0 MiB FFFF bootfs 2 2158592 61071326 28.1 GiB FFFF Unknown I will try soon: https://opensource.rock-chips.com/wiki_Partitions it works! to flash your method over 4gb 32gb devices Just flash the gpt.img inside the start.img located on 0x00000000 GPT 4gb to use in 8gb HZDM images gpt.img

Combine a ROOT image with an UPDATE image and BOOM = v0.7 build firmware i will finish this step in a week or two.... if you have an 8gb device, use the @hzdm method UPDATE: H96 MAX V56 RK3566 4gb and 8gb Ram SD-Card images: Release Version v0.5DEBIAN12 BETA Release Version v0.5ARMBIAN23 BETA UPDATE: H96 MAX V56 RK3566 4gb and 8gb EMMC images: Release Version V0.7DEBIAN12 BETA Release Version V0.7ARMBIAN23 BETA

Take your debian SD card image and: now you have an ROOT v0.7 IMAGE MADE BY YOURSELF!

!!!!!!!NOW YOU HAVE AN SD CARD v0.5 image!!!!!

@hzdm Dear friend, Your MOD on USB2.0 doesnt boot with SERVER version of armbian!!!! for server images Please use the OLD DTB file without USB2.0 it solves the boot problem on Server images!!! @Sunil sankar i'm building updated versions from the SD-card images based on v0.5 All that you need to compile armbian: https://drive.google.com/file/d/1G5KBVq1oR-QrIKG3FoHmUTwh8OSAG018/view?usp=sharing H96MAX_DTB_DTS_WIFI_NOVEMBER_2023.zip

Don't use it, I'm trying to rebuild it [emoji28] wait a week or two...

i will test the 4gb version too Please report your 8gb device by: armbianmonitor -u due to the high demand for 8gb devices I bought a unit to test the images here too, I'm going to put in a 1tb SSD with a sata adapter and create a bitcoin lightning node 1R$ = 0,20U$ 5R$ = 1U$ 54,12U$ = 271,37R$ with taxes 51,11U$ = 256,28R$ with taxes

@rossbcan dmesg | grep mmcblk0 cat /var/log/syslog | grep mmcblk0 armbianmonitor -u Result before SDcard insert: https://paste.armbian.com/qixunuqehi After Connect by insert SDcard: https://paste.armbian.com/rucaleyigi

Tested on 4gb / 32gb Old board version The factory can change layout without warning nobody. This is the bad side of TV boxes, and this is why Linux on this type of devices isn't supported by community

@Sunil sankar @hzdm @mvpwar Can you test this new 23.11 image? Please validade if it works

V0.5 = @armbian The Armbian SD card image "Compiled From Armbian Project" V0.8 = @hzdm Project with Mainline Bootloader "Boot the 64gb Emmc Armbian with Mainline Rockchip" V0.9 = @hzdm Mainline Bootloader "Boot the 32gb and 64gb Emmc Armbian with Mainline Rockchip" V1.0 = @hotnikq The Armbian SD card inside the Android Legacy Rockchip Image "Glued Image: Android boot for Linux"

based on @hzdm method i will make this image using Distro Boot with Boot.scr https://wiki.trenz-electronic.de/display/PD/Distro+Boot+with+Boot.scr mount the H96MAX update.img Files that will help 1. MiniLoaderAll.bin and U-boot are taken from Armbian image from Orange Pi 3B board. 2. The /boot directory was moved to a separate bootfs partition. 3. Rename file /boot/extlinux/extlinux.conf in extlinux.conf.bak 4. In /boot directory boot.cmd and boot.scr files were created with the following contents sudo apt-get update sudo apt install u-boot-tools This is the content of Boot.cmd and this is the content of boot.scr file too!! setenv docker_optimizations "on" setenv bootlogo "false" echo "Boot script loaded from ${devtype} ${devnum}" if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1"; fi if test "${bootlogo}" = "true"; then setenv consoleargs "splash plymouth.ignore-serial-consoles ${consoleargs}" else setenv consoleargs "splash=verbose ${consoleargs}" fi part uuid mmc 1:2 partuuid setenv bootargs androidboot.console=ttyFIQ0 root=PARTUUID=${partuuid} rootwait rw rootfstype=ext4 ${consoleargs} no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash p> load mmc 1:1 0x42000000 Image load mmc 1:1 0x44000000 dtb/rockchip/rk3566-firefly-roc-pc.dtb load mmc 1:1 0x46000000 uInitrd booti 0x42000000 0x46000000 0x44000000 # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr fdisk /dev/mmcblk1 N default default (lower this value to match the size of your root image) T 1 W create the boot disk drive content Create the root disk drive content Create the rootfs.img file Create the bootfs.img file

Attached, DTB and DTS Files that work with all USB ports Today I start the Recompile Session. Command: ./compile.sh build BOARD=station-m2 BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='3dsupport browsers desktop_tools internet office programming remote_desktop' DESKTOP_ENVIRONMENT=cinnamon DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=yes RELEASE=jammy Whats news? Detect USB 2.0 port ✔️ Works Wifi Broadcom ✔️ Updated Armbian 23.11 ✔️ runs kernel 6.2 DESKTOP ✔️ Boot on Linux Cinnamon Ambian✔️ display video HDMi ✔️ detect internal MMC ✔️ Detect SD-CARD ✔️ Detect USB 3.0 port ✔️ Please test this image and report it here. Use this tutorial to test this image use the same update.img and apply this new 23.11 rootfs insted of 23.08 also use the new 23.11 update image NEW ROOT FILE ARMBIAN 23.11 CINNAMON The changes are: Line 299 and Line 304 Amazing job @hzdm rk3566-firefly-roc-pc.dtb rk3566-firefly-roc-pc.dts

just disable and uninstall XFCE

Attached, DTB and DTS Files that work with all USB ports Today I start the Recompile Session. Command: ./compile.sh build BOARD=station-m2 BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='3dsupport browsers desktop_tools internet office programming remote_desktop' DESKTOP_ENVIRONMENT=cinnamon DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=yes RELEASE=jammy H96 Max RK3566 4gb and 8gb ✔️ boot from SD-CARD Soldered ✔️ runs kernel 6.2 DESKTOP ✔️ Boot on Linux XFCE Ambian✔️ display video HDMi ✔️ detect internal MMC ✔️ Detect SD-CARD ✔️ Detect USB 2.0 port ✔️ Detect USB 3.0 port ✔️ (nothing better than an usb hub) The changes are: Line 299 and Line 304 Amazing job @hzdm rk3566-firefly-roc-pc.dtb rk3566-firefly-roc-pc.dts

you will need to build it again, probably on 2024 I will have time for that.

this is Old! Your device is an 8gb RAM Please consider to use the HZDM 8GB version Follow the 8GB device topic This Topic is only for 4GB devices

in only in a 4gb device rk3566 i was using 2x 1TB SATA SSD on USB3.0 Docker with CasaOS: Web tunnel over cloudflare to enable access to nextcloud with HTTPs. Web Nextcloud application dockered to share things with windows over samba to local network. on MacOS and Linux devices i used to share files from Local Lan over Cifis agaist baremetal. this device as a NAS work at gigabit speeds, all over the place with wifi6

you can do it! I have a tip for you to do what you are imagining!!! Linux distros with ARC Manjaro architecture have GPU acceleration working perfectly on MALI GPU's. you can make a Manjaro ROOT compilation Based on Armbian, If you manage to compile it please come back here and share I start talking about it here and the conclusion is here my Rock 3a works fine as a media player device with Manjaro since 2022

It's time to compile a version and call it alpha. I'm going to install Linux on my new FCBGA1744 interposer ddr4 In a few weeks I will publish an image for 4gb H96 max device with USB2 working