[ROM] Beelink GT1 / Alfawise S92 TVStock Nexus ROM (Android TV 7.1)

[doiscavalos]

I have tried the chromecast feature included from my PocoF1 and didn't succeed. What am I doing wrong?
Can you please some suggestions?

Without this i guess that having and android tv box is some kind of useless.

[jit_mr]

Thanks for your efforts and great work but I am facing issue in flashing my box.
I have GT1 Ultimate box with sr no. 710N1, purchased on sept. 2018.

I am getting stuck at either 4% or 7% while using USB burning tools, I have tried following ROM so far each one giving the same error :

• http://freaktab.org/9252bfa15b83727c

[paddy67]

Hi,

Is this rom compatible with GT1 ultimate 3/32 Gb S/N AX12 ?

Is it possible to flash with SD Card (Burn_Card_Maker), USB Burning Toll does not recognized my box ?

Thanks

Thanks, but be sure to read the "Important Note" in red. That ROM is for the LPN1 hardware only.

[mercurio07100]

thanks for your work Guest

I have not tried it yet and I want to do it soon, but how can I read it is excellent, just a question that is not clear to me, the latest update (Nexus_GT1_710N1_TVStock-20190223) works with Beelink GT1 standard A912? Or is it better to try the penultimate update?

[n1gh7man]

Hi Folks,
i have a GT1 with serial A912, current ROM is the stock from Beelink 708N0_AP6255.
When i try to burn one of the images from here (tried with usb burning tool 2.0.8 and 2.1.2) i am getting an error right at the beginning of the process after "Download DDR".
Burning the stock from Beelink goes just fine.
What could be the possible reason for this?

...
[11:41:13 667][HUB5-1][Err]--[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error

I had the same problem. I inserted USB into another PC connector and it all worked. I don't know if it matters, the cable and PC connector (with which it worked) were USB 3.0 .

PS: When the burning tool wrote [HUB4-1] there was the same error. When I changed the connector, burning tool showed [HUB1-1] and it worked.

[n1gh7man]

Is there a way to make 5.1 dolby surround sound work ?

In my case MX Player (hw) work's only with DTS (not AC3). On Kodi AC3 and DTS works perfectly!
GT1 connected to Onkyo TX-NR414.

[n1gh7man]

Hello! Sorry for noob question .). How to update Chrome on this firmware?

[Sonyroc]

Hello, in France in my city, the deployment of fiber has arrived. So i noticed a bad debit in wired. How can i check this slowness ? My bit rate does not exceed 180 Mo/s. Do you have any commands to send me to test the ethernet card ? Is the network card flanged by hardware or android tv ? Thanks in advance.

Beelink GT1 s/n A912 + amlogic q201:7.1.2/NHG47L/20171221

Hello, thank you for your answer. Your rom is perfect and functional. Before answering you, I wanted to understand how the RGMII mode works (TS stream input10/100/1000M MAC+10/100 PHY). But this is beyond my level of competence. To conclude, the GT1 box is simply limited in bandwidth.

Same here. I didn't mess with Ethernet. Whatever works with the underlying OEM firmware should also work for this custom ROM.

Audio options are unchanged from the underlying OEM firmware.

[Sonyroc]

Hello, in France in my city, the deployment of fiber has arrived. So i noticed a bad debit in wired. How can i check this slowness ? My bit rate does not exceed 180 Mo/s. Do you have any commands to send me to test the ethernet card ? Is the network card flanged by hardware or android tv ? Thanks in advance.

Beelink GT1 s/n A912 + amlogic q201:7.1.2/NHG47L/20171221

[mrdigit420]

Is there a way to make 5.1 dolby surround sound work ?

[beo59]

Hi Folks,
i have a GT1 with serial A912, current ROM is the stock from Beelink 708N0_AP6255.
When i try to burn one of the images from here (tried with usb burning tool 2.0.8 and 2.1.2) i am getting an error right at the beginning of the process after "Download DDR".
Burning the stock from Beelink goes just fine.
What could be the possible reason for this?

[11:41:11 272][HUB5-1][Inf]-------------Download DDR.USB-----------
[11:41:11 272][HUB5-1][Inf]--2-2-0-0
[11:41:11 272][HUB5-1][Inf]--Control write pll reg1 0xd9000000:0x000000b1
[11:41:11 773][HUB5-1][Inf]--Control write pll reg1 0xd9000000:0x00005183
[11:41:12 274][HUB5-1][Inf]--Write initial succeed
[11:41:12 274][HUB5-1][Inf]--Upload encrypt at 0xc8100228
[11:41:12 274][HUB5-1][Inf]--ulValue = 0xadfc318c
[11:41:12 274][HUB5-1][Inf]--Read encrypt value succeed
[11:41:12 281][HUB5-1][Inf]--Transfer complete
[11:41:12 281][HUB5-1][Inf]--Run at address 0xd9000000
[11:41:12 282][HUB5-1][Inf]--RunInRam succeed
[11:41:12 658][HUB5-1][Inf]--IOCTL_IDENTIFY_HOST_Handler ret=-5 error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.


[11:41:12 658][HUB5-1][Err]--CheckFileRunState failed
[11:41:12 658][HUB5-1][Inf]--Failure : 1, FailureMax : 3
[11:41:12 660][Global][Inf]--Catch DBT_DEVICEREMOVECOMPLETE
[11:41:12 661][Global][Inf]--Scan usb device
[11:41:12 661][Global][Inf]--Aml scan WorldCup Device
[11:41:12 663][Global][Inf]--Host: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
[11:41:12 663][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_16e810cf&rev_04#3&11583659&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[11:41:12 664][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&2278ac73&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[11:41:12 664][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&a287287&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[11:41:12 664][Global][Inf]---------->[Port0]NoDeviceConnected
[11:41:12 664][Global][Inf]---------->[Port1]NoDeviceConnected
[11:41:12 665][Global][Inf]---------->[Port2]Other device
[11:41:12 665][Global][Inf]---------->[Port3]NoDeviceConnected
[11:41:12 665][Global][Inf]---------->[Port4]NoDeviceConnected
[11:41:12 665][Global][Inf]---------->[Port5]NoDeviceConnected
[11:41:12 665][Global][Inf]-------->[Port1]NoDeviceConnected
[11:41:12 665][Global][Inf]-------->[Port2]NoDeviceConnected
[11:41:12 667][Global][Inf]--Host: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26
[11:41:12 667][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_16e810cf&rev_04#3&11583659&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[11:41:12 667][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&1e2e9ada&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[11:41:12 771][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&339a2dae&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[11:41:12 771][Global][Inf]---------->[Port0]NoDeviceConnected
[11:41:12 771][Global][Inf]---------->[Port1]NoDeviceConnected
[11:41:12 771][Global][Inf]---------->[Port2]NoDeviceConnected
[11:41:12 772][Global][Inf]---------->[Port3]Other device
[11:41:12 772][Global][Inf]---------->[Port4]NoDeviceConnected
[11:41:12 773][Global][Inf]---------->[Port5]Other device
[11:41:12 773][Global][Inf]---------->[Port6]NoDeviceConnected
[11:41:12 773][Global][Inf]---------->[Port7]NoDeviceConnected
[11:41:12 773][Global][Inf]-------->[Port1]NoDeviceConnected
[11:41:12 773][Global][Inf]-------->[Port2]NoDeviceConnected
[11:41:12 775][Global][Inf]--Host: USB xHCI Compliant Host Controller
[11:41:12 775][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e31&subsys_16ee10cf&rev_04#3&11583659&0&a0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[11:41:12 775][Global][Inf]---->Roothub:USB#ROOT_HUB30#4&332fa869&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[11:41:12 775][Global][Inf]-------->[Port0]NoDeviceConnected
[11:41:12 775][Global][Inf]-------->[Port1]Other device
[11:41:12 775][Global][Inf]-------->[Port2]NoDeviceConnected
[11:41:12 776][Global][Inf]-------->[Port3]NoDeviceConnected
[11:41:12 776][Global][Inf]-------->[Port4]NoDeviceConnected
[11:41:12 776][Global][Inf]-------->[Port5]NoDeviceConnected
[11:41:12 776][Global][Inf]-------->[Port6]NoDeviceConnected
[11:41:12 776][Global][Inf]-------->[Port7]NoDeviceConnected
[11:41:12 776][Global][Inf]--Scan USB host controller complete
[11:41:12 776][Global][Inf]--Update data center with HubMap
[11:41:12 776][Global][Inf]--Update hub5 device data
[11:41:12 776][Global][Inf]--Update HUB5-1 
[11:41:12 776][HUB5-1][Inf]--Update device path
[11:41:12 776][Global][Inf]--Update HUB5-2 
[11:41:12 776][HUB5-2][Inf]--Update device path
[11:41:12 776][Global][Inf]--Update HUB5-3 
[11:41:12 776][HUB5-3][Inf]--Update device path
[11:41:12 776][Global][Inf]--Update HUB5-4 
[11:41:12 776][HUB5-4][Inf]--Update device path
[11:41:12 776][Global][Inf]--Update HUB5-5 
[11:41:12 776][HUB5-5][Inf]--Update device path
[11:41:12 776][Global][Inf]--Update HUB5-6 
[11:41:12 776][HUB5-6][Inf]--Update device path
[11:41:12 776][Global][Inf]--Update HUB5-7 
[11:41:12 776][HUB5-7][Inf]--Update device path
[11:41:12 776][Global][Inf]--Update HUB5-8 
[11:41:12 776][HUB5-8][Inf]--Update device path
[11:41:13 159][HUB5-1][Err]--[11:41:13 159][HUB5-1][Inf]--Failure : 2, FailureMax : 3
[11:41:13 660][HUB5-1][Err]--[11:41:13 660][HUB5-1][Inf]--Failure : 3, FailureMax : 3
[11:41:13 667][HUB5-1][Err]--[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error
[11:41:13 667][HUB5-1][Inf]--Close device handle 0x0000072c

I don't know that there'd be much value added. It would just be updating to the latest OpenGApps build, right?