Nick A

@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

@Ducdanh Nguyen H313 is basically the same chip as H616.

@Ducdanh Nguyen you should be able to see it on the board https://linux-sunxi.org/AXP_PMICs

@Ducdanh Nguyenthe secure boot patch is safe it doesn’t burn any fuses on your SOC. you still haven’t answered the axp chip question. If it doesn’t have one then it’s not a h313. The newer allwinner SOC’s use a axp chip for power management. If I don’t have that information then I don’t know which image to recommend.

@Ducdanh Nguyen can you see your axp chip? never heard of bigfish. Is that a heat sink on your SOC? Not sure why it has no writing on it. Install this android app it should give you more information https://play.google.com/store/apps/details?id=com.finalwire.aida64&hl=en_CA&pli=1 Did you apply the secure boot patch?

@Ducdanh Nguyen do you know which axp chip you have on your board? It’s a very small chip with axp written on it. I don’t see the H313 markings on your SOC chip. Are you sure you have a H313? If you don’t see an axp chip you might not even have a allwinner SOC. If your android is rooted then it probably has one installed.

@Ducdanh Nguyen on the other side of the board it has two capacitors. I don’t think that’s it.