Author: Chomee

Beelink GT1 bricked, please help

[Copy link]

1

Threads

4

Posts

36

Credits

Newbie

Rank: 1

Credits
36
Post time 2017-03-19 06:58:59 | Show all posts
This are the steps I'm doing:

0º Everything is disconected from the computer and also from the GT1
1º Start USB Burning Tool v2.0.8, set language to English.
2º Load the .img file, that on my case is "GT1_311M0.img" since I have the GT1 Ultimate Board q201_9377.
3º Go to File->Import Image and select the "GT1_311M0.img" to load. I get the Image check popup box.
4º I have the configuration on the USB Burning Tool set to: Erase Flash "X" - Force erase all, all the other check boxes are unpicked.
5º I press the start button on the USB Burning Tool software.
6º I plug the USB Cable A to A, on the side USB port from the GT1 Ultimate, and the LED comes ON.
7º I connect the power cord to the wall plug and to the GT1 Ultimate.
8º I plug the USB Cable A to A, to the USB 3.0 from the computer.

It is supposed to ear the windows sound but nothing happens.

I have tested many variations that I can remenber:
- Pressing and hold the reset button on the bottom of GT1 Ultimate with a paper clip before plug the power and USB.
- Withou pressing any button.
- Pressing and hold the reset button on the bottom of GT1 Ultimate with a paper clip after plug the power and USB.
- I have also tested around 6 versions of USB Burning Tool
- I also have tested all the list above but press the start button on the USB Burning Tool only at the end after everything pluged.

I did get once the GT1 Ultimate, recognized by the windows and USB Burning Tool, but when flashing I did get one error, after unplug and didn't get the windows to recognise the GT1 Ultimate any more.

Any ideas?
Reply Support Not support

Use magic Report

16

Threads

197

Posts

1187

Credits

Gold Member

Rank: 6Rank: 6

Credits
1187
Post time 2017-03-19 08:31:14 | Show all posts
Yes, you should wait on hitting Start in the USB Burning Tool until after you've successfully connected the box in recovery mode and get the "Connect success" message.  And to get in recovery mode, you'll definitely need to hold in the reset button with a paper clip as you connect the USB cable.  It should only take a few seconds.

If you're still not connecting, it's possible you've got a bad bootloader and need to reset the NAND.  See above instructions on shorting pins, but the procedure resurrected another Amlogic box for me just this week.
Reply Support Not support

Use magic Report

1

Threads

4

Posts

36

Credits

Newbie

Rank: 1

Credits
36
Post time 2017-03-19 18:19:21 | Show all posts
Yes I have 100% sure that is a bad bootloader.

Can anyone send me message with the picture for GT1 Ultimate with the PINs to short?

I don't find it on the posts above.
Reply Support Not support

Use magic Report

1

Threads

24

Posts

116

Credits

Member

Rank: 2

Credits
116
 Author| Post time 2017-03-20 16:25:37 | Show all posts
Hi Jhonnie, I can show you which pins to short, but I cannot upload it here, dunno why. Contact me on skype (milan7483)
Reply Support Not support

Use magic Report

0

Threads

1

Posts

16

Credits

Newbie

Rank: 1

Credits
16
Post time 2017-03-22 04:10:14 | Show all posts
Chomee replied at 2017-03-20 16:25
Hi Jhonnie, I can show you which pins to short, but I cannot upload it here, dunno why. Contact me o ...

Hi! Please help me with my Beelink GT1 Ultimate. I think i bricked it. Please send me some instructions on shorting pins. Image and what should I do. My email zebberty@gmail.com
Reply Support Not support

Use magic Report

1

Threads

24

Posts

116

Credits

Member

Rank: 2

Credits
116
 Author| Post time 2017-03-24 15:36:38 | Show all posts
It stopped working again, but pc recognizes box. Now when I want to flash firmware with Usb Burning tool, it shows me after 2% of burning this error:
[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error
I tried 4 different firmwares, and the same happens every time. Can anyone suggest something? I can copy whole error if it can help determine the problem.
Reply Support Not support

Use magic Report

2

Threads

39

Posts

130

Credits

Member

Rank: 2

Credits
130
Post time 2017-03-24 15:53:20 | Show all posts
That was the exact same  error it gave me when I tried to flash the wrong firmware. Like yours, mine also stopped at 2% and returned me with that error...
Make sure that your firmware is correct! Go to freaktab dot com website and download the correct firmware. Also try to change different versions of the burning tool...
The procedure that worked for me was:
1) Connect the phone
2) Open the burning tool
3) connect the power cord

It didn't work the first 3 times. But in the end it worked. What really "opened" the phone for me was installing the android box tv rom for  AP6255 WiFi chipset. It is called Alfawise S92 TVStock Nexus ROM (Android TV) and it is on Freaktab dot com.
You also have to install the patch for the  AP6255 in order to make wifi work along with that ROM. If you manage to install this rom there is nothing working with your box.
Reply Support Not support

Use magic Report

2

Threads

39

Posts

130

Credits

Member

Rank: 2

Credits
130
Post time 2017-03-24 16:01:44 | Show all posts
I meant "Wrong" not working...sorry for the mistyped word...
Reply Support Not support

Use magic Report

1

Threads

24

Posts

116

Credits

Member

Rank: 2

Credits
116
 Author| Post time 2017-03-24 16:36:24 | Show all posts
Thank you Frank for quick answer! Actually firmware that I am trying to flash is GT1_109M0_AP6255, and was the one which I successfully burnt when I had previous problem. After I burnt it box was working great about a week, and then yesterday just stopped responding. I tried Alfawise S92 Nano Nexus ROM, it also stopped at 2%, now I am downloading Stock variant and we'll see if I'll be more lucky with that one.
Reply Support Not support

Use magic Report

4

Threads

62

Posts

671

Credits

Senior Member

Rank: 4

Credits
671
Post time 2017-03-24 17:47:11 | Show all posts
unbelievable
the serial says on the box begins with A912...
but on cpuz hardware is this
Reply Support Not support

Use magic Report

You have to log in before you can reply Login | Sign up

Points Rules

Quick Reply To Top Return to the list