Beelink GT1 bricked, please help

Phant0m``

Chomee replied at 2017-06-12 07:20
Did anyone manage to solve
[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control se ...

If I remember correctly, this has to-do with not booting your box up into Recovery Mode via RESET button, holding it down and carefully plugging in the USB cable that is already plugged into the PC. :D

jgf78

one more device bricked, ligth on and no more :(

Djuganight

minonano replied at 2017-05-10 03:39
Miles
I have managed to get mine working again, pm me for info.

Hello,
I seen your post where you say you manage to unbrick the beelink.
Can you please share the info and I have a paper wight ATM and theres nothing I do that make this box work.
Thanks

minonano

Follow this post and make sure you have same board, you are still taking a risk, good luck.
http://www.bee-link.com/Beelink-2978-4-1.html
All the credit to Chomee.

shlomi_tz

Chomee replied at 2017-03-13 19:50
Ok, since Beelink didn't allow my last 2 posts with photos. If someone is interested, I've found out ...

Hi friend. Can you send me the procedure how to reset the emmc? My gt1 ultimate a912 had 709n0 and i tried to upgrade to 710n1 and after the file was uploaded, the gt1 become a brick. No way to get to it by sd nor by usb cable. Only the gray light is one. Please - need your assistance
. My email is : shlomi.tzur@gmail.com

longo213

I have a similar problem - my GT1 (A912 S/N, 16GB) seems bricked too - no output to HDMI, but the white icon is on. So far no luck installing from SD card. I tried to connect it with A male/male cable - it was visible in USB burning tool, but the flash stops at 9% with error

[0x30405004]UBOOT/Partition _aml_dtb/Verify partition/Error result

longo213

1. [19:06:54 801][HUB1-1][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&d027aa&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}  0x000004f4
   
2. [19:06:54 852][HUB1-1][Inf]--CloneImageProxy
   
3. [19:06:54 852][HUB1-1][Inf]--Connect path=USB xHCI Compliant Host Controller/P0/P0
   
4. [19:06:54 852][HUB1-1][Inf]--Start burning...
   
5. [19:06:54 903][HUB1-1][Inf]--------------ERASE BOOTLOADER------------
   
6. [19:06:54 905][HUB1-1][Inf]--0-7-0-16
   
7. [19:06:54 905][HUB1-1][Inf]--Identify status success
   
8. [19:06:54 905][HUB1-1][Inf]--    low_power
   
9. [19:06:54 910][HUB1-1][Inf]--Low power command success
   
10. [19:06:54 914][HUB1-1][Inf]--Read low power success
    
11. [19:06:54 914][HUB1-1][Inf]--bootloader_is_old
    
12. [19:06:54 914][HUB1-1][Inf]--Bootloader command success
    
13. [19:06:54 920][HUB1-1][Err]--failed: bootloader is new
    
14. [19:06:54 920][HUB1-1][Inf]--Bootloader is new
    
15. [19:06:54 920][HUB1-1][Inf]-------------Download DDR.USB-----------
    
16. [19:06:54 921][HUB1-1][Inf]--0-7-0-16
    
17. [19:06:54 921][HUB1-1][Inf]--No need download
    
18. [19:06:54 921][HUB1-1][Inf]-------------Download UBOOT.USB-----------
    
19. [19:06:54 922][HUB1-1][Inf]--0-7-0-16
    
20. [19:06:54 922][HUB1-1][Inf]--No need download
    
21. [19:06:54 923][HUB1-1][Inf]--    low_power
    
22. [19:06:54 928][HUB1-1][Inf]--Send command success
    
23. [19:06:54 931][HUB1-1][Inf]--Read command status success
    
24. [19:06:54 932][HUB1-1][Inf]-------------Download meson1.dtb-----------
    
25. [19:06:54 933][HUB1-1][Inf]--0-7-0-16
    
26. [19:06:54 933][HUB1-1][Inf]--Enc(0x00000000)
    
27. [19:06:54 934][HUB1-1][Inf]--    download mem dtb normal 141312
    
28. [19:06:54 934][HUB1-1][Inf]--Send download command success
    
29. [19:06:54 948][HUB1-1][Inf]--Read command status success
    
30. [19:06:54 964][HUB1-1][Inf]--Transfer complete
    
31. [19:06:54 964][HUB1-1][Inf]--Send download get_status command succeed
    
32. [19:06:54 968][HUB1-1][Inf]--get_status success
    
33. [19:06:55 468][HUB1-1][Inf]-------------ERASE FLASH-----------
    
34. [19:06:55 468][HUB1-1][Inf]--disk_initial 1
    
35. [19:06:55 468][HUB1-1][Inf]--Send command success
    
36. [19:06:55 475][HUB1-1][Inf]--Read command status success
    
37. [19:06:55 475][HUB1-1][Inf]-------------Download _aml_dtb.PARTITION-----------
    
38. [19:06:55 476][HUB1-1][Inf]--0-7-0-16
    
39. [19:06:55 476][HUB1-1][Inf]--download store _aml_dtb normal 141312
    
40. [19:06:55 476][HUB1-1][Inf]--Send download command success
    
41. [19:06:55 490][HUB1-1][Inf]--Read command status success
    
42. [19:06:55 705][HUB1-1][Inf]--Transfer complete
    
43. [19:06:55 706][HUB1-1][Inf]--Send download get_status command succeed
    
44. [19:06:55 711][HUB1-1][Inf]--get_status success
    
45. [19:06:55 711][HUB1-1][Inf]--verify sha1sum a513b27cd9fd9560420b9bdf437600a3fd10b6cb
    
46. [19:06:55 711][HUB1-1][Inf]--Send verify cmd succeed
    
47. [19:06:55 771][HUB1-1][Err]--failed:Verify Failed with sha1sum, origin sum "a513b27cd9fd9560420b9bdf437600a3fd10b6cb" != gen sum "15dee1f40d8d0a16994da6353ff20b187902b7d5"
    
48. 
    
49. [19:06:55 804][HUB1-1][Err]--[0x30405004]UBOOT/Partition _aml_dtb/Verify patition/Error result
    
50. [19:06:55 804][HUB1-1][Inf]--Close device handle 0x000004f4

Copy the Code

uzunogluosman

longo213 replied at 2019-10-21 01:08

I have same problem. My device is bricked . So if you can  solve problem, could you please share how did you manage it ?