[HOW TO RECOVER] So you bricked your box

[ClarkKent]

It appears it is the file "bootloader.img" inside the p212 zip file. You can prep the sdcard in the manner mentioned in the other thread.

Hello. calc
I need your help to straighten out an endless Circle.

Backstory... 3 week old GT1, I flashed one of Guest Nexus Nano ROMs to it. I tried several the only one I could get to take was 8. 25. 17
it worked well.
Then I loaded an incompatible APK or I threw the wrong TWRP at it. After deleting the APK, which was never used, I soft Rebooted.

I now have the Nexus static boot screen, followed by the animated boot screen, and that's it.

. It will not go recovery, reset, or take anything via SD card.I have appropriate img./ Zips on SD, in the proper hierarchy. Files search as boots, recovery, updating ROMs....Nada!
I Have tried a USB, and judging from the activity it skips external drives and goes boot loop.
I understand bootloader on this device is a little tricky, I may be wrong.

My question is if I short the pins on this device, will it Force addressing to the SD card?
And if so, what should I run on the SD for a booting file?

i'd be relieved just to get recovery.
Anything to move forward towards a reflash.
Can you shed some light on my dilemma, or point me in a New Direction?
I would really appreciate some charity/ clarity,
as I am lost. Many thanks! CK

[Scenz]

READ:0;0.0;CHK:0;
TE: 102658

BL2 Built : 13:38:48, Mar 8 2017.
gxl g8e12692 - xiaobo.gu@droid05

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 768MHz - FAIL
DDR3 chl: Rank0 @ 768MHz - PASS
Rank0: 2048MB(auto)-2T-11
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
aml log : SIG CHK : 230 for address 0x01700000
reset...
GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EM MC:0;READ:0;0.0;CHK:0;
TE: 102678

BL2 Built : 13:38:48, Mar 8 2017.
gxl g8e12692 - xiaobo.gu@droid05

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 768MHz - FAIL
DDR3 chl: Rank0 @ 768MHz - PASS
Rank0: 2048MB(auto)-2T-11
DataBus test pass!
AddrBus test pass!
-f
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
aml log : SIG CHK : 230 for address 0x01700000
reset...

Hi, this is the output i get out of my Mecool M8S Pro+. How can i repair it? The USB Burningtool as well as the BurnCardMaker do not work.... Thanks!

[hcardoso483]

Okay i bricked aml s912 cpu with m12n board the thing happened when i was updateing but i made this mistake and loadded the wrong firmware on the usb burning tool i only realized when i booted back the box coz it when non responsive, so i open it and try to short the emmc pins out to get it recognized in windows but it faild some how i know that there is a way to get it back working so i need to make this burn card but i belive thet the bootloader is corrupted so is there any chance of success?

Sent from my SM-N9300 using Tapatalk

[Fly]

HI, guys!
I bricked my BeeLink GT1
This is log form serial interface:
Every time is the same exept TE

GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0; EMMC:0;READ:0;0.0;CHK:0;
TE: 128499

BL2 Built : 13:18:48, Dec 21 2016.
gxl g4fc4d4e - xiaobo.gu@droid05

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR4 chl: Rank0+1 @ 636MHz
Rank0: 2048MB-2T-18
Rank1: 1024MB-2T-18

I did see - PASS mark at the end of memory DDR4 string

Interesting thing:
According to manufacturer's sticker box I have 2Gb DDR3 memory, in the log I see two banks Rank0: 2048MB-2T-18 + Rank1: 1024MB-2T-18 of DDR4 ????

I tried to create SD card as it described above but nothing work's for me. And anything I did - the serial looping is every time the same.
Now do you think is this the end?
Best Reragds.

[calc]

It appears it is the file "bootloader.img" inside the p212 zip file. You can prep the sdcard in the manner mentioned in the other thread.

[BLeaCHeR]

Are you sure you are using the u-boot from the package as the log appears to show it is the same version you were booting before.

form the zip package?
i 'm quite lost form here D:

[calc]

Are you sure you are using the u-boot from the package as the log appears to show it is the same version you were booting before.

BL2 Built : 13:48:56, Sep 23 2016.
gxl g7459bd4 - jianxin.pan@droid06

[BLeaCHeR]

i downloaded the firmware from here, but, it's not a img pure file...

anyway i try to boot using the recovery.img that comes with it, and there is the log.

GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:800;NAND:82;SD:0;READ:0;0.0;CHK:0;
no sdio debug board detected
TE: 196275

BL2 Built : 13:48:56, Sep 23 2016.
gxl g7459bd4 - jianxin.pan@droid06

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 2
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 720MHz - PASS
Rank0: 512MB-2T-11
Rank1: 512MB-2T-11
DataBus test pass!
  ADDR-W[0x00004000]:0xaaaaaaaa,R:0x28a921f9
  ADDR3-W[0x00000004]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000008]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000010]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000020]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000040]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000080]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000100]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000200]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000400]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00000800]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00001000]:0x55555555,R:0xa11889ca
  ADDR3-W[0x00002000]:0x55555555,R:0xa11889ca
  ADDR2-W[0x00008000]:0x55555555,R:0x5e5d761c
  ADDR3-W[0x00008000]:0x55555555,R:0x55555555
  ADDR2-W[0x00010000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00010000]:0x55555555,R:0x55555555
  ADDR2-W[0x00020000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00020000]:0x55555555,R:0x55555555
  ADDR2-W[0x00040000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00040000]:0x55555555,R:0x55555555
  ADDR2-W[0x00080000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00080000]:0x55555555,R:0x55555555
  ADDR2-W[0x00100000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00100000]:0x55555555,R:0x55555555
  ADDR2-W[0x00200000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00200000]:0x55555555,R:0x55555555
  ADDR2-W[0x00400000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00400000]:0x55555555,R:0x55555555
  ADDR2-W[0x00800000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x00800000]:0x55555555,R:0x55555555
  ADDR2-W[0x01000000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x01000000]:0x55555555,R:0x55555555
  ADDR2-W[0x02000000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x02000000]:0x55555555,R:0x55555555
  ADDR2-W[0x04000000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x04000000]:0x55555555,R:0x55555555
  ADDR2-W[0x08000000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x08000000]:0x55555555,R:0x55555555
  ADDR2-W[0x10000000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x10000000]:0x55555555,R:0x55555555
  ADDR2-W[0x20000000]:0x55555555,R:0x5ee77635
  ADDR3-W[0x20000000]:0x55555555,R:0x55555555
AddrBus test failed!!!
GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:800;NAND:82;SD:0;READ:0;0.0;CHK:0;
no sdio debug board detected
TE: 196276

[calc]

It looks like it is probably this one:

[BLeaCHeR]

sorry for the delay, i'm reinstalling the SO on my computer and i have some troubles with the HDD :C

http://imgur.com/a/kXXLp

there is a set of photos, hope that can be usefull

[calc]

That looks like its now not even seeing the BL2 on the sd card anymore, heh.

Which box do you have? If you aren't sure then a high resolution photo of the board will probably help.

BTW - Using a firmware that is not for your board will most likely brick it. The kernel (and I think uboot) needs to have the proper device tree file for the board it is running on.

This gives a brief overview of what that is:

https://events.linuxfoundation.org/s...ee-dummies.pdf

[BLeaCHeR]

not really, i can't find the exact firmware for this board

first i use the files from this firmware

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905x/606635-firmware-for-mxq-pro-4k-ver-s905x-android-6-0-marshmallow

now i use the files to try to boot a linux with the multiboot uboot

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files

i use the file "S905X_Linux_console_2GB_20161010.img" and i get the following output

GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:800;NAND:82;SD:0;READ:0;CHK:AA;USB:8;LOOP:1;EMMC:800;NAND:82;SD:0;READ:0;CHK:AA;USB:8;LOOP:2;EMMC:800;NAND:82;SD:0;READ:0;CHK:AA;USB:8;LOOP:3;EMMC:800;NAND:82;SD:0;READ:0;CHK:AA;USB:8;

i guess that is a advance... not?

[calc]

Do you have the stock firmware and u-boot on the sd card? As described in the first comment on the thread.

[BLeaCHeR]

i tried to flash a custom rom via recovery (not twrp)

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905x/others-aml-s905x/firmware-roms-tools-bx/614237-rom-xannytech-custom-mod-rom-twrp-recovey-built-in-for-minim8sii-and-other-devices-see-first-post

so, i have to change the bl2?

[calc]

So it looks like it is booting off the sd card but that it has the same build version of BL2 and is giving the same error.

What happened to cause the bricking?