mxq pro 4k 5g allwinner h313 can't sd card boot

[Ducdanh Nguyen]

(sorry for bad english)

 

i'm looking to boot in an armbian bookworm by sicxnull on my mxq pro 4k 5g, i checked the aida64, it showed the allwinner h313, i tried the toothpick method to the recovery menu (which have a boot option?) i'm novice to android 😕

 

by the way here are the images of the tv box pcb:

 

[ccs1664]

Hi 

I think that a boot on this TV box it should  be not so hard, I never tested an Allwiner.
Please, start reading some advices from this post from 2023:

once that h313, probably follows at the same procedure of the H61X ...
I hope to help you

ccs
 

Edited August 10 by ccs1664

[Ducdanh Nguyen]

@ccs1664 thanks for the information, but i already have a image that works on my mxq pro 4k 5g allwinner h313, but im struggling how to boot in the sd card, and i cant enter recovery mode too (it showed an update screen but nithing updated) im glad you replied to my situation.

[Nick A]

@Ducdanh Nguyen @ccs1664 is correct.. there’s a lot of information on that thread and the x96q threads to get your box running. I have to post the same advice over and over again.

 

The last thread you posted in. I gave instructions to get your dram settings and dts. Have you extracted them?

 

it could be possible that you have secure boot.

[Ducdanh Nguyen]

6 hours ago, Nick A said:

 

@Ducdanh Nguyen @ccs1664 is correct.. there’s a lot of information on that thread and the x96q threads to get your box running. I have to post the same advice over and over again.

 

The last thread you posted in. I gave instructions to get your dram settings and dts. Have you extracted them?

 

it could be possible that you have secure boot.

 

Thanks for noticing me!!! I will check the last thread ive been in and the dram settings and dts, i havent checked also i cant edit/change dram and dts, i use windows but i will use a virtual machine to get the armbian doing its job.

 

and from the secure boot, it could be because when i do the “toothpick method”, it showed the updating screen but nothing updated

 

thanks you for replying to me

 

edit: is the text too blurry? I could take more 😃

Edited August 12 by Ducdanh Nguyen

[Ducdanh Nguyen]

@Nick A sorrry but i didn't found where you replied to me could you repost it to mine trhead?😁

[Ducdanh Nguyen]

.

Edited August 12 by Ducdanh Nguyen

[Nick A]

 Start reading here.. 

[Ducdanh Nguyen]

@Nick Aok, im working on it

Edited August 14 by Ducdanh Nguyen

[Ducdanh Nguyen]

@Nick AMay i ask you a question? If yes , why wont my boxtry and boot on that amrbian image? I plugged in and it should detetct and boot to the sd card right?

[Nick A]

@Ducdanh Nguyen hard to tell. I don’t see any markings for uart. It’s not going to be easy to debug your board. 

[Ducdanh Nguyen]

@Nick A To be honest i don't really think about debug my box, but i sure will do more research after getting all settings done.

[Ducdanh Nguyen]

@Nick A could you help me get the dram settings??? My box don't have root access, on aida64, it says my box has root, but the tv info (https://play.google.com/store/apps/details?id=com.saksham.developer.tvinfo&hl=en&pli=1) says it is not rooted?

[Nick A]

 

[Ducdanh Nguyen]

@Nick A 👍

[Ducdanh Nguyen]

hey @Nick A i have problem when connecting to the box throught adb connect, i have installed every dependencies before (i won't show ouput bc too long but it succesed)

here is what i tried:

Quote

passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.17:5555
* daemon not running; starting now at tcp:5037
* daemon started successfully
failed to connect to '192.168.1.17:5555': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.17:5555
failed to connect to '192.168.1.17:5555': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.17:8888
failed to connect to '192.168.1.17:8888': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$

i am using a virtual machine to do this work

my uncle tried reset the prop on the tv box(mxq pro 4k 5g) (he's an android expert):

 

Quote

setprop service.adb.tcp.port 5555

stop adbd

stop : must be root

 

[Ducdanh Nguyen]

hello @Nick A i did install everything including adb on my VM, but it has occured an error

Here is the whole ouput:

Quote

passisdanhdanhdanh123@vmlmdanh:~$ cd Android_boot_image_editor
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo apt install git device-tree-compiler lz4 xz-utils zlib1g-dev openjdk-17-jdk gcc g++ python3 python-is-python3 p7zip-full android-sdk-libsparse-utils erofs-utils
[sudo] password for passisdanhdanhdanh123:                
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
git is already the newest version (1:2.43.0-1ubuntu7.3).
device-tree-compiler is already the newest version (1.7.0-2build1).
lz4 is already the newest version (1.9.4-1build1.1).
xz-utils is already the newest version (5.6.1+really5.4.5-1ubuntu0.2).
zlib1g-dev is already the newest version (1:1.3.dfsg-3.1ubuntu2.1).
openjdk-17-jdk is already the newest version (17.0.16+8~us1-0ubuntu1~24.04.1).
gcc is already the newest version (4:13.2.0-7ubuntu1).
g++ is already the newest version (4:13.2.0-7ubuntu1).
python3 is already the newest version (3.12.3-0ubuntu2).
python-is-python3 is already the newest version (3.11.4-1).
p7zip-full is already the newest version (16.02+transitional.1).
android-sdk-libsparse-utils is already the newest version (1:34.0.4-1build3).
erofs-utils is already the newest version (1.7.1-1build2).
0 upgraded, 0 newly installed, 0 to remove and 430 not upgraded.
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.17:8888
* daemon not running; starting now at tcp:5037
* daemon started successfully
^C
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.15:8888
failed to connect to '192.168.1.15:8888': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.15:5555
failed to connect to '192.168.1.15:5555': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$

any advice? thank you.

Edited Sunday at 08:44 AM by Ducdanh Nguyen
trying more commands

[Ducdanh Nguyen]

Hello @Nick A, i'm on my linux virtual machine doing the following command, but i got some problem on it (i have installed every package needed):

Quote

passisdanhdanhdanh123@vmlmdanh:~$ cd Android_boot_image_editor
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.13:5555
[sudo] password for passisdanhdanhdanh123:                
* daemon not running; starting now at tcp:5037
* daemon started successfully
failed to connect to '192.168.1.13:5555': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.13:8000
failed to connect to '192.168.1.13:8000': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.13:8888
failed to connect to '192.168.1.13:8888': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$

yes, i got the ip from the ifconfig command on termux 32bit if you are wondering

glad you helped me

Edited Thursday at 02:21 AM by Ducdanh Nguyen
the host arch is x86 64 bit if you are wondering

[Nick A]

Connect using 5037

[Ducdanh Nguyen]

@Nick Aalright

[Ducdanh Nguyen]

here is the ouput : @Nick A

Quote

passisdanhdanhdanh123@vmlmdanh:~$ cd Android_boot_image_editor
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$ sudo adb connect 192.168.1.13:5037
[sudo] password for passisdanhdanhdanh123:                
* daemon not running; starting now at tcp:5037
* daemon started successfully
failed to connect to '192.168.1.13:5037': Connection refused
passisdanhdanhdanh123@vmlmdanh:~/Android_boot_image_editor$

 

Edited Thursday at 05:00 AM by Ducdanh Nguyen