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.
-
-
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.Last edited by Fly; 05-22-2017, 18:52.Comment
-
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
Comment
-
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!Comment
-
Hello. calcOriginally posted by calc View Post
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! CKLast edited by ClarkKent; 11-28-2017, 19:31.Kris....don't forget my boxes! Okay?Comment
-
Hi guys,
what about the settings of the serial port? I've tried with putty, Tera term and hyperterminal using different baud rates, data bit and stop bit settings with no luck. Something appear but it's just some strange geroglifics.
Can you give me some more indications?
Thank youComment
-
Frustrating...
keeps blinking the startup image every couple seconds.
usb_burning_tool no longer sees the box (usb from OTG to computer, push recovery pin, plug in usb... now nothing).
I've tried burning an image that had worked using sdcard. First Bootcard maker, then realizing Burn_card does all the work.
Tried booting both with pin and without.
Does not recognize this, still blinking the start up screen.
I've even tried to boot with twrp, which has worked in the past, but also nothing.
Matricom GBox Q3
S209x
Any help would be appreciated.Comment
-
Hello!
If anyone still reading this thread I need help. I have a GT1 ultimate wiht the S/N G912GSIG50016 32G. I tried to flash firmware on this box several months ago and bricked the device. I tried to get help from support, but failed. At the end I put it aside for a while. Now I had a look again on the problem to see if there is any progress. I checked my boot messages, and here is what I got:
Code:GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 122981 BL2 Built : 19:58:22, Aug 31 2016. gxl g54c8aee - 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 @ 912MHz Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... Error PGSR0: 0x840047ff.Retry... DX0GSR0: 0x009f27a0.... DX1GSR0: 0x009e27a0.... DX2GSR0: 0x009f27a0.... DX3GSR0: 0x009e27a0.... DX0GSR2: 0x27800018.... DX1GSR2: 0x27800018.... DX2GSR2: 0x27800018.... DX3GSR2: 0x27800018.... DX0GSR3: 0x00000000.... DX1GSR3: 0x00000000.... DX2GSR3: 0x00000000.... DX3GSR3: 0x00000000.... DDR init fail, reset...
It is obvious that the problem is in the DDR init. Is this a software error or is it the hardware that is broken. How can this be fixed? Any help is appreciated.
Comment
-
In 2016 I had the prototype board for that box this is how you need to do, get the 6.0.1 marshmallow firmware for your box, in an sdcard with fat32 file system make the flash firmware version using the amlogic sdburning card tool i can't remember exactly witch versuon of the tool is compatible with the firmware just search one that be. Then insertithe card to your box connect HDMI cable press and hold reset button inside av port and apply power, you will see a green Android and a progress bar updating on TV screen it is possible that it fails on the 1st attempt on the 2nd do the same thing but this time do not press the reset button you will see same thing on screen this time the tip of the progress bar will be green wait for it to do its thing it may take some 10 to 15 minuts also unless you see an Android with an red Cross don't stop the process, some times it may look like it's doing nothing but it is. That's it hope it helpsOriginally posted by sarkanyz View PostComment
-
Thank you. I will definitely try to revive the box with this method.Originally posted by hcardoso483 View PostComment
-
I am trying to find the right 6.0.1 firmware file, but i found only one location where it could still be downloaded:Originally posted by sarkanyz View Post
The downloaded archive however contains only a recovery.img, a factory_update_param.aml and an OTA update package q201_9377-ota-20170227.zip. There is no image I could burn with an amlogic burn_card_maker.
If I try to select the recovery.img i get the error message "L(1005)aml_sdc_burn.UBOOT, and bootloader.PARTITION al not in pkg"
How shall I proceed?Comment
-
Try here https://chinagadgetsreviews.com/?s=Beelink+gt1 what version is yours 2gb or 3gb ram? Don't forget your ram is ddr4 you can flash any s912 ddr4 firmware now you need to check wifi 9377 is for the new models of the GT1 Ultimate I Believe the GT1 has a 6255 chipset but don't listen to me on the wifi thing coz I am not sure I hope that page has what you need, let me now...good luckOriginally posted by sarkanyz View Post
I am trying to find the right 6.0.1 firmware file, but i found only one location where it could still be downloaded:
The downloaded archive however contains only a recovery.img, a factory_update_param.aml and an OTA update package q201_9377-ota-20170227.zip. There is no image I could burn with an amlogic burn_card_maker.
If I try to select the recovery.img i get the error message "L(1005)aml_sdc_burn.UBOOT, and bootloader.PARTITION al not in pkg"
How shall I proceed?Comment
-
Thank you for trying to help.Originally posted by hcardoso483 View Post
I have a GT1 ultimate 32G/3G version with wifi chip LTM8830 which according to forums compatible with 9377 version. My problem is that all packages from chinagadgetsreviews contain:
"Inside archive: firmware + factory_update_param.aml + recovery.img"
I have no idea what to do with these files. The burn_card_maker doesnt accept any of them to flash on the sd card as I written in my previous post.Comment
-
Format à 4GB or larger SD Card as Fat32. Do a full format not a quick one. Copy the contents of the downloaded file from chinagadget into the SD Card. Then do the steps.Originally posted by sarkanyz View PostComment
-
I tried every combination of the firmware versions, and tried to boot from sd card by pushing the button when powering up and without it also, but there was absolutely no change in the serial debug port messages. The only change I could achieve is not to receive any messages through the serial port. The firmware update did not start at all.Originally posted by X92-2GB View Post
I also tried to use the USB burning tool, but was unable to make windows recognize the board. I even tried to short the those pins of the storage chip also... no luck.Comment
There are currently 9439 users online. 2 members and 9437 guests.
Most users ever online was 16,134 at 08:28 on 08-11-2023.
Comment