Well, I'm just another GT1 Ultimate owner, who, without intention, become member of "Bricked GT1" club.
Here are details:
GT1 Ultimate S/No: AX12..., with AP6255 WiFi, nad 32GB eMMC Toshiba (153 pin FBGA).
Box came with build 703NO, but I experienced some bugs (with portrait application display), so I updated it with build 704NO from the following link (http://freaktab.com/forum/tv-pla ... -3g-32g-a912-ap6255). Update was done by SD card method, and successfull.
However, although improved, issue with portrait application display was not fully solved, so I went further. I installed ATV package (http://freaktab.com/forum/tv-pla ... 7-standard-ultimate). Instalation went fine, but I didn't like limited choice of applications on Play Store, so I decided to try something else.
This time I selected Nano Nexus variant (http://freaktab.com/forum/tv-pla ... us-roms-android-7-1). I put SW on SD card, and tried to boot from it, while keeping reset button pushed. Since box booted from internal memory rather that from SD card, I restarted it several times, until one time box didn't boot.
When plugged in, only white LED is lit, but no any picture is shown on TV via HDMI.
I tried to recover device, both by booting it from bootable SD card, or via USB Burning Tool, but with no luck.
Using USB Burning Tool, I can burn just some of the IMG files from various sources. For example, I can burn this image (http://freak-tab.de/luis/Beelink ... TV-GT1_Ultimate.zip) as per instructions from http://freaktab.com/forum/tv-pla ... tv-android-tv-ddr4. But after burning is successfully finished, box again is not working.
Also, I can burn image Nexus_q201_Nano_NHG47L-20170825.img (from http://freaktab.com/forum/tv-pla ... us-roms-android-7-1), but box again is not working.
If I try to burn "official" images GT1_704NO_AP6255 or GT1_704NO_AP6255, I get error in USB Burning Tool, around 4%, which I can not overcome ([0x10303004]Romcode/Switch status/Identify/Error result).
Today I manage to get serial connection to the device, but now I'm even more confused, since I see no error in booting sequence - or am I missing something?
Looks like device is booting fine, but nothing is shown after last line (Relocation Offset is: b6ec9000):
TE: 54995
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
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: 0x10100000, size: 0x00015400
Load bl33 from eMMC, src: 0x00038200, des: 0x01000000, size: 0x000a9a00
NOTICE: BL3-1: v1.0(debug):2e39a99
NOTICE: BL3-1: Built : 16:36:21, Sep 20 2016
aml log : bl31 normal boot !
[Image: gxl_v1.1.3154-065f772 2016-09-29 14:08:54 yan.wang@droid05]
OPS=0x82
c8 af f 5d 3e cb c7 69 33 f8 5c bf [0.301803 Inits done]
secure task start!
high task start!
low task start!
INFO: BL3-1: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader
ERROR: Error initializing runtime service opteed_fast
INFO: BL3-1: Preparing for EL3 exit to normal world
INFO: BL3-1: Next image address = 0x1000000
INFO: BL3-1: Next image spsr = 0x3c9
U-Boot 2015.01-gf3cbd70 (Feb 24 2017 - 22:51:16)
DRAM: 3 GiB
Relocation Offset is: b6ec9000
Also, how long boot sequence is displayed on serial console? Can someone attach here example of full boot - just to compare it with my logs?
BR
Comment