Hqnicolas

From my experience with TV boxes, If you keep USB3.0 on max speed for a time longer the 30 seconds, probably you will experience a data loss somewhere.

https://youtu.be/1vpepaQ-VQQ?si=zDM2XXD7xPOaP-JK

I bought 4, and have 4, never have any trouble with this Chinese crap, it's very powerful, but I recognize trash when I see trash, don't let your files on emmc without backup, and don't trust a full time service on that RAM, also don't trust external SSD devices on that power supply Sent from my 22021211RC using Tapatalk

You can throw it on trash easyer than a umbrel device or raspiblitz.

Stop saying the truth. [emoji28] Sent from my 22021211RC using Tapatalk

F

send the device to armbian, they will use it to something.

Please, dont, some children have worked on it. Step 1: You Just need to short the clk and gnd from MMC while connect the device on USB - Male to Male use linux! flash the loader with rkdeveloptool

@Evgeny Radchenko to work with RK3566 @hzdm images you need to use the v2.86 RkdevTool

the USB 2.0 is chainloaded from HDMI, the server image won't start the display HDMI GPU, if you want a USB 2.0 enabled device, use HotnikQ Desktop images

SELECT THE BOOTLOADER CHECKCBOX! to flash EMMC you need to pass the bootloader to enable EMMC write. Dear @Evgeny Radchenko to work with RK3566 devices you need to use the v2.86 RkdevTool

Dear @BrunoMerz it happends because you don't follow the first boot fix, "step 3" Now you need to setup all again. do the Step 1 and 2 again... Step 3: Do the First boot fix: When you boot, set the admin password, and after that, go to terminal and do the Device FIX: ################################ 8GB devices Fix ############################## 8GB device First Boot Comand: fdisk /dev/mmcblk1 t 4 1 w # this GPT file was generated from a 4gb device. # in 8gb device you will need to trick the gpt after instalation # First boot comand: What you will see on prompt: 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 you can safe reboot and use your armbian device.

Try v1.0 image update H96 MAX V56 RK3566 8gb EMMC Chainloader to mainline HotnikQ images: Tutorial EMMC Version v1.0 ARMBIAN Armbian 23.11.0 Server Minimal V1.0 The Latest Armbian 23.11.0 Desktop Gnome V1.0 The Latest Debian 12 BookWorm Server Minimal v1.0 The Latest Debian 12 BookWorm Desktop Gnome v1.0 The Latest

You need to short the clk and gnd from MMC to connect the device before flash the loader on Linux rkdeveloptool Sent from my 22021211RC using Tapatalk

You describe my everyday so, did you try to flash the original Android image with RkDevTools? https://drive.google.com/file/d/14HWcHYHDrgUBFWholrDCKUWDPHw1r4F1/view

H96 Max With USB 2.0 rk3566-firefly-roc-pc.dtbrk3566-firefly-roc-pc.dts

H96 Max Without USB 2.0 rk3566-firefly-roc-pc.dtsrk3566-firefly-roc-pc.dtb

Stop thinking Rockchip devices are unbrickable I think you put a incompatible bootloader, please clean the emmc with this method Learn More on this document https://roc-rk3328-cc.readthedocs.io/en/latest/flash_emmc.html#maskrom-mode

This is a H96 MAX board with SSD attach! Great product! the difference are on Sata Port, wifi chip or power control. did you try H96 DTS DTB or image?

use an x86 computer with ubuntu 22.04 Build Armbian ./compile.sh KERNEL_CONFIGURE=yes

take the rootfs http://ca.us.mirror.archlinuxarm.org/os/rockchip/ drop on rootfs if you dont know how to drop it, follow the T95 gui's @maka @Darren Williams @tmm1 now, the easy step, refactor all armbian software.

@ning can you please provide here the DTS | DTB | product name | photo from this device?

did you test v0.7 v0.9 v1.0 or custom build? send a picture from the board of your box sometimes the factory changes board and pinout Need to be something like this. https://forum.armbian.com/uploads/monthly_2023_07/114.thumb.jpg.43ae8bbca4209c02c38c0db29e30c28e.jpg https://forum.armbian.com/uploads/monthly_2023_07/h96maxF.jpg.1046202b427bb0797a20a2e6e5f6a2f9.jpg

Broadcom VideoCore VII GPU Pi 5 launch day saw 3 patches for the V3D kernel driver to enable the Raspberry Pi 5 support. These changes by Igalia amount to just around 200 lines of changed code for enabling the kernel driver support. Linux 6.1-derived kernel and Mesa 23.2-rc3 with the extra patches for driver support. The V3D DRM kernel driver changes will be picked-up for the Linux 6.7 cycle but that stable kernel release won't appear until early 2024.

Use a Linux Ubuntu 22.04 to build And Windows 10 machine to burn images Follow this instructions And to build a mainline image. Follow this instructions Since i don't have this machine, I can't.