Originally posted by X92-2GB
View Post
Do you know how to test if that part of power is working?
-
From what it looks on your boot loader, it should see the SD card without reset. Just insert the card and power on the box. The display should show progress.
It is also possible you have a hardware issue. Could have blown one of the power sections to drive memory, or USB data bus.Leave a comment:
-
Thanks for your reply.
I've got two firmwares I'd like to try, but can't get it to recognise the micro sd card or a computer.
With the sd card, I formatted as FAT32, and loaded the Uboot and firmware file plus ini file with USB burn tool (various versions). Holding the reset button in the av port and then putting power onto the unit, but nothing...
Alternatively, I tried shorting each pin that are beside each other on the NAND while power is on and the computer didn't connect. I used this same usb-usb cable to flash it the first time.
Do I need to short the nand and then apply power? I can't figure out which two pins are correct. There are about 3 pairs that when shorted cause the blue led to turn off... Does the correct pair cause the led to turn off?
Leave a comment:
-
Looks good to me... nothing wrong with your bootloader. You need to find an LPDDR3 firmware for your box.Originally posted by MrJCub View Post
I assume you need to mask rom reset to start with USB burn tool. You prolly can use the ST Card burn tool to flash without opening your box.Leave a comment:
-
Hello,
I'm looking for some help with a T95Z Plus that seems bricked.
I loaded firmware with USB Burn Tool but in the issues of trying to load it, I unclicked erase bootloader and when it finished loading, the device only shows the blue led, no display on tv.
I've tried booting from microSD with and without reset button pressed, but nothing.
Tried connecting to computer, but doesn't find it.
Tried shorting pins on nand chip, but couldn't find the right pins. Chip has THGBMFG8C4LBAIR on it and can't find datasheet.
Board is Green, with XJH-V99-V00 2018-03-31.
Here is the Boot log from Serial monitor:
Code:GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0 ;EMMC:0;READ:0;0.0;CHK:0; TE: 86276 BL2 Built : 18:50:13, Sep 22 2017. gxl g4786fda-dirty - jiaxing.ye@droid12 set vdd cpu_a to 1120 mv set vdd cpu_b to 1050 mv set vddee to 1000 mv Board ID = 3 CPU clk: 1200MHz DQS-corr enabled DDR scramble disabled STICKY_REG0: 0x00000000 STICKY_REG8: 0x00000000 STICKY_REG9: 0x00000000 LPDDR3 chl: Rank0+1 @ 720MHz ddr_lpddr3_only_up_odt_enable: 0x00000001.... Training PGSR0: 0x80001fbf.... ddr_training_inf: rank: 0 org_wr0 w0_l w0_r org_r0 r0_l r0_r org_wr1 w1_l w1_r org_r1 r1_l r1_r org_wr2 w2_l w2_r org_r2 r2_l r2_r org_wr3 w3_l w3_r org_r3 r3_l r3_r af_vrefddr_training_win: rank: 0 21 00 45 3d 18 63 17 00 31 44 1c 6e 20 00 41 3c 15 65 1f 00 40 3b 13 64 674 rank: 1 22 00 45 3d 18 63 17 00 31 45 1c 6e 20 00 41 3d 15 65 1f 00 40 3b 13 64 674 bist_test rank: 0 20 12 2f 40 2c 54 19 03 2f 42 2c 59 24 10 39 3d 2a 50 20 0a 37 3a 23 52 674 rank: 1 1f 10 2f 3e 2b 52 19 03 2f 43 2e 59 22 0d 37 3c 2a 4f 21 0a 39 3a 23 51 674 bist_size0x 000007e0 bist_cost_time 350986 us bist test no threshold setting: ddr_refi_counter37 DDR1_ADDRMAP_0== 0x14941cc5 DDR1_ADDRMAP_1== 0x230783ab DDR1_ADDRMAP_2== 0x2f6ad272 DDR1_ADDRMAP_3== 0x3bcdeb38 DDR1_ADDRMAP_4== 0x0007359e Rank0: 2048MB-2T-3 Rank1: 1024MB-2T-3 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x0002c600 Load bl33 from eMMC, src: 0x00050200, des: 0x01000000, size: 0x00065a00 NOTICE: BL3-1: v1.0(release):a625749 NOTICE: BL3-1: Built : 11:25:15, Aug 25 2017 NOTICE: BL31: BL33 decompress pass mpu_config_enable:ok [Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07] OPS=0x82 wdt: reset registers! 89 d9 d8 0 ce 6f af 8e 21 97 61 76 [0.734996 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast U-Boot 2015.01 (Dec 26 2017 - 15:03:06) DRAM: 3 GiB Relocation Offset is: b6eb4000 12345678 10112281101! initcall sequence 00000000b7f5b818 failed at call 0000000001009120 (err=-1) ### ERROR ### Please RESET the board ###
Leave a comment:
-
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.Leave a 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.Leave a 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?Leave a comment:
-
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?Leave a 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 PostLeave a 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.
Leave a comment:
-
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.Leave a 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 youLeave a comment:
Leave a comment: