Hello @Nick A i did everything git cloned now im in setup,

heres what i choosed:

1. Do not change kernel configuration

And after that, i don't found any compactible for my h313

also note that mine firmware is based off d9 Pro 5g so i think it could use the same dram settings and wifi chip except for the cpu. Hope this helps!

I have identified the ram chip and nand, but don't know where wifi is, i think thats not very important since i have alot of usb wifi and ethernet

 

@Nick A heres the complete info : 

🧠 DRAM

Chip 1:

Marking: MPF694C4G-P

Maker: UniIC (UnilC)

Type: DDR3/DDR3L

Density: 4 Gb (512 MB)

Date code: 2021 (week 11)

Chip 2:

Marking: SBC13H4G150

Maker: UniIC (UnilC)

Type: DDR3/DDR3L

Density: 4 Gb (512 MB)

Date code: 2020 (week 11)

✅ Total RAM = 1 GB (2 × 512 MB)

💾 Storage (eMMC)

Chip:

Marking (line 1): NCEMAM60-08G

Maker: FORESEE

Type: eMMC Flash (not raw NAND)

Capacity: 8 GB

Marking (line 2): 000

Serial/Batch: Z1S1801147073

Date code: 1802 → Year 2018, Week 02

✅ Total storage = 8 GB eMMC (manufactured early 2018)

@Ducdanh Nguyen you forgot these steps 

choose "Show CSC/WIP/EOS/TVB"

choose "I understand and agree"
 

you should see a few x96q in the list.

@Nick A thank you.

hey @Nick A, i think i found the serial port

look at the yellow mark on the image

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

@Nick A Oh..

 

by the way i don't see any options with allwinner h313 and 1gb ram, can i just choose the 2gb x96q?

@Nick A i choosed x96q-lpddr3 (csc) Allwinner H313 TVB with 2gigs of ram and emmc (my box uses emmc)

debian 11

image with desktop enviroment

Edited August 30, 20251 yr by Ducdanh Nguyen

@Nick A 

full log (failed):

[💲|🌱] Starting main configuration
[💲|🌱] Using REVISION from [ main VERSION file: '25.05.0-trunk' ]
[💲|🌿] Enabling extension [ armbian-config ]
[💲|🌱] Sourcing family configuration [ /home/nguye/build/config/sources/families/sun50iw9.conf ]
[💲|🌿] Enabling extension [ sunxi-tools ]
[💲|✅] change-tracking: after sourcing family config [ KERNEL_MAJOR_MINOR='6.12' ]
[💲|✅] change-tracking: after sourcing family config [ KERNELBRANCH='tag:v6.12.11' ]
[💲|✅] change-tracking: after sourcing family config [ LINUXFAMILY='sunxi64'  # (was: 'sun50iw9') ]
[💲|✅] change-tracking: after sourcing family config [ KERNELPATCHDIR='archive/warpme-6.12' ]
[💲|✅] change-tracking: after sourcing family config [ BOOTBRANCH='tag:v2025.01' ]
[💲|✅] change-tracking: after sourcing family config [ BOOTPATCHDIR='u-boot-h616' ]
[💲|✅] change-tracking: after sourcing family config [ ATFBRANCH='tag:lts-v2.10.14' ]
[💲|✅] change-tracking: after sourcing family config [ NETWORKING_STACK='network-manager' ]
[💲|🌱] Sourcing arch configuration [ arm64.conf ]
[💲|✅] change-tracking: after sourcing arm64 arch [ ATFDIR='arm-trusted-firmware' ]
[💲|🌱] Using NETWORKING_STACK [ NETWORKING_STACK: network-manager ]
[💲|🌱] Adding networking extensions [ net-network-manager, net-chrony ]
[💲|🌿] Enabling extension [ net-network-manager ]
[💲|🌿] Enabling extension [ net-chrony ]
[💲|🌱] Extension manager [ processed 17 Extension Methods calls and 27 Extension Method implementations ]
[💲|🌱] x96q-lpddr3 [ Using allwinner/sun50i-h313-x96-q-lpddr3.dtb for edge ]
[💲|💥] Error  1 occurred in SUBSHELL [ SUBSHELL at /home/nguye/build/lib/functions/configuration/config-desktop.sh:48 ]
[💲|💥] Cleaning up [ please wait for cleanups to finish ]
[💲|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans ]
[💲|🌱] Share log manually: [ use one of the commands below (or add SHARE_LOG=yes next time!) ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.com/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.de/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.next.armbian.com/log ]
[💲|🌿] Share log manually: [ curl --data-binary @output/logs/log-build-5e1956f5-4bb3-4cdf-b026-7bcfa7d1794e.log.ans https://paste.armbian.eu/log ]
nguye@DESKTOP-IFEAUMD:~/build$

 

EDIT: it continued while i tried Debian 12

 

Next i choosed

xfce

config_base (onlyone)

internet

Edited August 30, 20251 yr by Ducdanh Nguyen

@Nick A success build

log : https://paste.armbian.eu/simirepihe

Edited August 30, 20251 yr by Ducdanh Nguyen

@Nick A i flashed it to my card and it's not booting to armbian...

Wait @Nick A when a device is rooted, do i need a root manager???

@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.

Edited August 30, 20251 yr by Nick A

@Nick A su binary installed, but not working correctly, i don't know why, the chip is def h313 because i used cat /proc/cpuinfo(and others) and with grok commands i can confirm it uses cortex-a53 (which includes in h313) and bigfish manufactor/ or codename idk but it's part of  allwinner, i mean enought to prove that mine is h313 

Edited August 30, 20251 yr by Ducdanh Nguyen

@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?

Edited August 30, 20251 yr by Nick A

@Nick A oh yea i used aida64 all the time (and with alot of command line commands), that's where i came up with h313 since it uses cortex-a53, the clock speed and the arch is 64bit armv8 (on 32bit mode)

and about the secure boot patch, i think it's too risky (since it is a fake box and diffrent dram settings, etc,....) and i think i will buy a cable and test the su command, if it works, i will dump the boot.img and extract it

@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.

Edited August 31, 20251 yr by Nick A

@Nick A sorry, i haven't got any information about the axp chip, i will do the reseacrch

@Ducdanh Nguyen you should be able to see it on the board 

 

https://linux-sunxi.org/AXP_PMICs

Edited August 31, 20251 yr by Nick A

@Nick Ai don't see any h313 on the page, maybe i will just tear it down again

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

@Ducdanh Nguyenyour axp chip should look similar to this

 

Thanks, i will tear it down and see what axp chip mine is using

i didn't found any axp chip in my device, but only a controller, it's very small and that's all i found. Is it ok to dump boot img with adb

 

Edited September 1, 20251 yr by Ducdanh Nguyen

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

I already ordered a usb to usb cable, bout 0.5 meters ( about 20 inches )

Already have adb too

@Nick A also there are some problem with root, when i try ‘su’ on terminal emulator, it showed /system/xbin/su : permission denied

is there any problem with root?

@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.