Help! I Bricked my MXQ Pro s905....

[Goudtik]

I was fiddling around with an other firmware and it seems my bootloader has gone corrupt...
It won't startup (no video, no respons to reset-button) only the blue led wil light.
I can't seem to get the device to connect with the computer through USB so this keeps me from flashing it again... Any thoughts on how to repair the bootloader?

When I hook it up to my serial port it reports:

BL2 Built : 13:55:05, Jan 28 2016.
gxb g3625dd5 - xiaobo.gu@droid05

Board ID = 2
set vcck to 1100 mv
set vddee to 1000 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;E MMC:0;READ:0;CHK:0;
TE: 44523
no sdio debug board detected

I don't know how to solve this! Can anyone help?


Before I started I made a backup of serveral folders on the device, so I have the following folders saved as *img:
DATA, SYSTEM, CACHE, BOOT, LOGO.
The output (before I changed anything) is in the txt file included.

MXQ Pro.txt

[Nofan Tasi]

I was fiddling around with an other firmware and it seems my bootloader has gone corrupt...
It won't startup (no video, no respons to reset-button) only the blue led wil light.
I can't seem to get the device to connect with the computer through USB so this keeps me from flashing it again... Any thoughts on how to repair the bootloader?

When I hook it up to my serial port it reports:

BL2 Built : 13:55:05, Jan 28 2016.
gxb g3625dd5 - xiaobo.gu@droid05

Board ID = 2
set vcck to 1100 mv
set vddee to 1000 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;E MMC:0;READ:0;CHK:0;
TE: 44523
no sdio debug board detected

I don't know how to solve this! Can anyone help?


Before I started I made a backup of serveral folders on the device, so I have the following folders saved as *img:
DATA, SYSTEM, CACHE, BOOT, LOGO.
The output (before I changed anything) is in the txt file included.

[ATTACH]n576652[/ATTACH]

I believe I had same board as you (see your other post).
If nothing helps:
Try to USB flash http://aml.technikexpert.com/amlogic...XQPRO-0315.zip

[balbes150]

See what the marking on the chip's internal memory. This marking looking for, what contacts need to close, to lock it. Burn Tools USB then will be able to see the device and re flash it. You downloaded u-boot from the model, where more RAM than your console. Without blocking the contacts Burn Tools USB will not turn on.

http://4pda.ru/forum/index.php?s=&showtopic=723156&view=findpost&p=49413899

[Goudtik]

thanks Balbes150, I did not know the correct pins to short. This worked to get windows to recognise the box again. The flashing keeps ending at 2%.... I hooked it up to mij UART device and I'm now trying to use the terminal to copy my settings back. I hope this works!

[balbes150]

If you pre-make a full backup of the internal memory (using the run Linux from an external card), you can quickly restore it without using a USB cable. If you do not get recover through the console UART, write me, I will explain how to restore using SD card or USB flash drive.

[seraser]

If you pre-make a full backup of the internal memory (using the run Linux from an external card), you can quickly restore it without using a USB cable. If you do not get recover through the console UART, write me, I will explain how to restore using SD card or USB flash drive.

Bello, can you explain me, bricked with blue les, nand erased an no uboot con it., uart atached.

[balbes150]

In this state you can connect via USB cable and flash from the program Burn Tools need firmware.