Jump to content

x96q h313


Blaize

Recommended Posts

@svsruof

 

FEL is a low-level subroutine contained in the BootROM on Allwinner devices. It is used for initial programming and recovery of devices using USB.

 

In order to Enter to FEL mode you need a Male to Male USB cable.

 

1> Disconnect power supply from your TV-BOX.

2> connect the USB cable to your PC USB port.

3> with a tooth pick  PRESS continuously  the button inside AV port and connect the other end of USB cable to the USB (OTG ) of your TV-BOX

( Note: if you have 2 usb ports on your tv-box try the left first )

4> Release the the button you pressed with the tooth Pick (after 3 - 4 seconds)

 

Now you must be FEL mode. if your tv-box is booting to android then you an not in FEL mode. (repeat the procedure and/or change the USB port on TV-BOx )

 

When you successfully enter into FEL mode you will see nothing on Serial console output and your device will not boot to installed os.

 

 

To ensure that you are in FEL mode you (if you are using Windows)

go to Device Manager and examine the USB devices root tree

you must see a device with the bellow IDs

 

USB Device(VID_1f3a_PID_efe8)

 

if you are using linux open a terminal and give the lsusb command and exam the device IDs.

 

if you see above IDs then you are in FEL mode and you can use sunxi tools for further investigation.

 

 

 

 

 

 

 

 

 

 

 

Link to comment
Share on other sites

Armbian & Khadas are rewarding contributors

@svsruof

 

Yes entering to FEL mode and verify the IDs is a Safe method that indicates that your board is Allwinner and not a Fake board like RK322x or something else.

in FEL mode you can flash your device firmware with PhoenixSuit if your device is bricked,  or to investigate your board with sunxi-tools. Both operations  requires

knowledge of your hardware otherwise you may easily brick your device.

 

From your serial log you posted your device seems to have secure boot enabled by the manufacturer firmware. (SBOOT / [01.260]secure enable bit: 1)

this does not allow non trusted boot environmet and probably this is the reason that you can not boot from SD card.

I am still looking for a way to override this situation and unlock the boot process  (as i have also a similar bricked board) on some Chinese boxes and is very difficult

to find the original manufacturer firmware (for investigation)  because they don't publish it. 

I also have tried sunxi-fel in order to boot linux via USB but without success (usb_bulk_send() ERROR -7: Operation timed out on H616)

 

If someone knows a method to override this situation on Allwinner (H313 / H616)  is welcome to help.

Link to comment
Share on other sites

For Allwinner boxes you need to add this line to your u-boot defconfig.

CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y

 

To generate a TOC0 image from a binary, you will need an RSA key (pair) file. As most secure-boot enabled devices do not burn the VENDOR_ID eFUSE, you can use any RSA key, so just generate one, for instance with the openssl tool (would only need to be done once):

openssl genrsa -out root_key.pem

 

Your root_key.pem needs to be in the u-boot root directory. 

 

 

 

 

Edited by Nick A
Link to comment
Share on other sites

Bonjour, // Hi
vous savez si il y a un OS fonctionnel pour ce modèle ? //  Did you know if there is an OS that i can install on this model ?
il y a quelques  mois j'en ai testé plusieurs mais en vain aucun n'a daigné lancer quoi que ce soit. // Months ago, i've tried to install somes OS like Armbian but no one seems to work
Merci d'avance. // Thanks in advance !
20240919_151054.webp.8e9cca49764cac0177c98168deef461c.webp

Link to comment
Share on other sites

@Lancoly

Your board seems to be a x96Q Board v5.1

You can try to boot your board with  following image : "MiniArch-20240715-6.10.10-board-h313.x96_q_v5.1-SD-Image.img.xz" 

if your board is booting then you can install also Armbian by modify the extlinux.conf

 

 

 

 

Link to comment
Share on other sites

@Nick A

I have trouble with this bricked board is a x96q variant (new) (older version with differen emmc boot miniarch),  manufacturer firmware is not available but i am able to boot it with  (iATV Q5 Stock Firmware)

The board is booting from SD card (i used PhoenixCard.v4.2.4 to burn it as startup) and i am able to see the bootlogo but android does not start because on serial log i see that (rotpk is not written yet).

 

I also decompiled the  iATV Q5 Stock Firmware to fex files. firmware contains toc0.fex and toc1.fex

The problem is that the board requires secure boot in order  to boot.

I am able to produce Open SSL certificate via (openssl genrsa -out root_key.pem) .

 

How can I boot or compile Ambian for this secure boot device ?

 

 

PS: if anyone has a working firmware for this device please provide link.

 

Board Specifications are:

Processor: H313

Emmc: Kingston 16EMCP16  (2GB Ram - 16GB Rom)

pmic: AXP313a

wifi : SV6256P

BlueTooth: BR8052A01

 

 

IMG_20240919_153624.jpg

IMG_20240919_153649.jpg

IMG_20240919_153658.jpg

IMG_20240919_153709.jpg

IMG_20240919_153833.jpg

IMG_20240919_153901.jpg

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines