I tried all the P212 1gb dtb images and none worked, my box displays the A905X boot logo then a black screen.
This box is finicky, as I cant get other roms to work either. I can only get the stock image and a stripped version of it to work.
I did a cat /proc/device-tree/amlogic-dt-id and the result was:
gxl_p212_1g
But the corresponding included dtb file doesnt work.
Update: I dumped my dtb.img using dd if=/dev/dtb | gzip > /storage/downloads/dtb.img.gz and tested the extracted dtb.img file, but it doesn’t work either. Now I don’t even get a black screen, it freezes on the A905X blue logo.
The resulting file has 256kb instead of the 40kb ish of the included ones, tho.
Update 2: I tried splitting the dtb with the script found here:
It resulted in 3 files, I tested all 3 and same result, it freezes on the A905X Screen.
I’ve already replied to your post in LE .
More info to identify your chip.
You’ve extracted the Android device tree. That will not work with CE or LE
Upload it here so as the DEVS MIGHT look at it.
Meanwhile look at ❓ Which DTB do I use?
If you can connect to the UART connector on the inner PCB (the “motherboard”) of your box, then you can connect it to a PC via a UART to USB adapter and get kernel output and diagnose what’s going wrong.
Yep, always replacing the dtb.img on the root partition.
Yes, 100% sure, it’s even printed on the motherboard its a S905X p212 device, the boot logo is S905X and a couple roms for S905X run on it like a slim versions etc.
Hard to say what is going on here without a log dump of the bootloader.
Try pressing down the reset button inside the AV port on the rear of the device as you insert the power cable, don’t release it until you see the S905X logo, if that still fails then try a different USB flash drive or memory card.
you have “crypt and tee” partitions, typical sign of “secure board”. As with a Xiaomi Mi box, the Armbian kernel starts with the original DTB.
Dtb.img files that you have tried are not loaded by the bootloader due to a lack of signature.
In your case, it’s just a guess.
Accurate secure information is provided by the SEC_AO_SEC_SD_CFG10 register where its value is extracted. Make a TTL log.
Yes.
This register value can be taken from the burn log. 1. Make a full backup copy of your Android system. 2. Try to install any suitable (in terms of RAM memory type) S905X Android FW on the box via AML-BT. If the board is encrypted, the burning process will fail. Post the log from the AML Burning Tool.
I did, multiple times. Restored the stock one multiple times, including doing the pin shorting on the nand chip to restore from hard bricks. Currently i’m using a modded one intended for the MXQ Pro. It burns ok.