Nick A

@going Yes, git is a pain in ass. I think it's better to teach everyone the git commands. Maybe someone will learn from my instructions and contribute to the mainline Linux kernel and Armbian. Transpeed 8k618-t Tv box will always be supported because I learned how to use git commands and submit patches. I hope others will do the same. A lot of the patches are mainlined for h618. I don't think it will be too long before Armbian only needs a Transpeed 8k618 board config to build an image. But of course there's different variations of the same box. I hope this thread helps them because I won't be here forever.

@emor acid you could also edit the dts and compile a dtb. Then transfer it to your sdcard. https://stackoverflow.com/questions/21670967/how-to-compile-dts-linux-device-tree-source-files-to-dtb

@dale Sure, I'll upload what have so far. Need help debugging it.

@emor acid You could use the armbian build system to create patches https://docs.armbian.com/Developer-Guide_Build-Commands/#rewrite-uboot-patches. I like to use the git commands and make my own patches. git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "x98h" choose "edge" rest is up to you. Stop the build after the kernel patches are applied in the middle of the kernel build. Use "ctrl c" keys. ctrl c Patch your u-boot dts. cd cache/sources/u-boot-worktree/u-boot/v2025.01 sudo pico dts/upstream/src/arm64/allwinner/sun50i-h618-x98h.dts Delete this. ethernet0 = &emac1; &emac1 { pinctrl-names = "default"; pinctrl-0 = <&rmii_pins>; phy-mode = "rmii"; phy-handle = <&rmii_phy>; phy-supply = <&reg_aldo1>; allwinner,rx-delay-ps = <3100>; allwinner,tx-delay-ps = <700>; status = "okay"; }; &mdio1 { rmii_phy: ethernet-phy@16 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <16>; }; }; Add this ethernet0 = &emac0; ethernet1 = &emac1; &emac0 { compatible = "allwinner,sun50i-h616-emac"; pinctrl-names = "default"; pinctrl-0 = <&ext_rgmii_pins>; phy-mode = "rgmii"; phy-handle = <&ext_rgmii_phy>; phy-supply = <&reg_gmac_3v3>; phy-io-supply = <&reg_dldo1>; allwinner,rx-delay-ps = <3100>; allwinner,tx-delay-ps = <700>; status = "okay"; }; &mdio0 { ext_rgmii_phy: ethernet-phy@1 { /* rtl8211F compatible string for mdio and phy */ compatible = "ethernet-phy-id001c.c916"; reg = <1>; reset-assert-us = <20000>; reset-deassert-us = <100000>; reset-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ }; }; &emac1 { compatible = "allwinner,sunxi-gmac"; status = "disabled"; }; &mdio1 { rmii_phy: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <1>; }; }; sudo git add dts/upstream/src/arm64/allwinner/sun50i-h618-x98h.dts sudo git commit This opens up an editor. First line is your Title. The rest is your description. Remember to save when you are done. Title Description sudo git format-patch -1 Your new patch. 0001-Title.patch Rename 0001-Title.patch to 172-Title.patch Copy your patch into the build/patch/u-boot/u-boot-h616 directory. Patch your kernel dts. cd cache/sources/linux-kernel-worktree/6.12__sunxi64__arm64 sudo pico arch/arm64/boot/dts/allwinner/sun50i-h618-x98h.dts Same changes as above. sudo git add arch/arm64/boot/dts/allwinner/sun50i-h618-x98h.dts sudo git commit Title Description sudo git format-patch -1 Rename 0001-Title.patch to 2002-Title.patch. Copy your patch into the build/patch/kernel/archive/warpme-6.12 directory.

@NiTr0 I guess transferring the dtb to official armbian kernel 6.12.43 will work. Most of warpme’s collection of patches are already in the official armbian build. There might be some differences. the reason I use warpme patches is because he’s usually quick at porting his patches to the latest kernel versions. I made a 6.17 build but I haven’t had time to test it yet. Don’t worry about those wifi errors it will work fine.

@emor acid Here's some information on H616/H618 ethernet phy. This is the 100Mbit ethernet built inside the H618 SOC. https://lore.kernel.org/linux-sunxi/20250526002924.2567843-1-james.hilliard1@gmail.com/T/#t In your dmesg log it shows your box is loading a generic phy. It should be loading the Allwinner phy. For example @NiTr0 logs above. Your box might be using a 1000Mbit external ethernet chip. If that's the case your dts settings will be very different. You'll need check if your box supports Gigabit Ethernet and find the Ethernet chip on your board. @NiTr0 Just freeze the kernel updates using armbian-config. My armbian build is unofficial so you can't use the official armbian kernels. I'm using patches created by warpme and my own custom patches. So the kernel update feature will not work. https://www.google.com/search?q=armbian+config+freeze+kernel&oq=armbian+config+freeze+kernel&gs_lcrp=EgZjaHJvbWUyBggAEEUYOdIBCDY4MDJqMGo3qAIAsAIA&sourceid=chrome&ie=UTF-8 For wifi your box is looking for You need find the brcmfmac4334 bin file and rename it to brcmfmac4334-sdio.transpeed,8k618-t.bin. Also, the brcmfmac4334 txt to brcmfmac4334-sdio.txt. I think it's already in /lib/firmware/brcm under a different name.

@emor acid can you post your full dmesg.

@NiTr0 Armbian doesn't use $fdtfile because U-Boot carries the same DT already, in memory. If you want to use a different DT, add fdtfile=yourdt to the /boot/armbianEnv.txt. I haven't tried this method. I don’t remember if I tested orange pi 2w. It’s been awhile since I released the image. I think someone has. I have a board laying around somewhere. I'll try it when I'm not busy.

@emor acid This was discussed before in this thread. Here are the links. Hope they help. 1) https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/4/#findComment-187672 2) https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/21/#findComment-218004 @NiTr0 You need to freeze kernel updates in the armbian-config tool. The images I released use kernel version 6.12. Linux version 6.15.4-edge-sunxi64 (build@armbian)

@Tomi Skies try the x96q images https://github.com/NickAlilovic/build/releases/tag/20250306

@MeJune You can build your own Debian 13 Trixie version. git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "transpeed=8k618-t" choose "edge" choose "trixie" rest is up to you. Your image should be in output/images directory.

@rockamal maybe you’ll have better luck with x96q lpddr3 https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build pico patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch Change @@ -0,0 +1,191 @@ to @@ -0,0 +1,192 @@ add this to the bottom of the patch "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" Then you need to include the secure boot patch. pico patch/u-boot/u-boot-h616/secure-boot.patch create the secure boot patch. you can find it here.

@AHMEDLORI

@AHMEDLORI try these the transpeed or x98h image. https://github.com/NickAlilovic/build/releases/tag/20250306

@Luckyisnotcoolest try the x96q images here. https://github.com/NickAlilovic/build/releases/tag/20250306

@emor acid could be your gpio settings for mmc0. Try the x98h image. If that doesn’t work you need to extract your android dts or use the one from the working Ubuntu.

@Rodrigo Campos @kazekami_him I think @nitrolack and @afiftyp had the same Transpeed M98-8k board. It booted fine with my transpeed image. (other than wifi) They didn't have a board that had secure boot. Check if your board is the same. Maybe you could try my older images. It could be the newer u-boot and patches broke the ram detection? Maybe your board is using a different ram?

@Andre Ruiz that’s weird uboot loaded boot.scr Check if “/boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb” exists and path is correct. Make sure it’s not 0 bytes.

@Andre Ruiz I might already have those patches in my build. Try the x96q images here. Also, you should change the log level to 7 in armbianEnv.txt. https://github.com/NickAlilovic/build/releases/tag/20250306

@snow try the transpeed image https://github.com/NickAlilovic/build/releases/tag/20250306

@Ducdanh Nguyen Yes does it tell you in android Google Ai: To find your Android device's GPU, download a hardware info app like Dev Check from the Google Play Store, go to Settings > About Phone > Hardware Information (though this is less reliable on some Android versions), or use developer tools like Android GPU Inspector (AGI) for detailed profiling.

@Ducdanh Nguyen Can you find the gpu version?

@Ducdanh Nguyen without a axp chip I’m pretty sure you don’t have a h313. You’re going to have research your box on your own. Sorry but I’m too busy.

@Ducdanh Nguyen it should work. https://developer.android.com/tools/adb

@Ducdanh Nguyenyour axp chip should look similar to this