Spotted in the wild: x88 King x922

[greenstone]

Here is something I found on the forums that they were doing for the gt-king basically it explains how to make a recovery image backup then use that to boot magisk but it forces you to leave your box on all the time in that mode. Rather not do that.

https://forum.freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s922x/others-s922x/firmware-roms-tools-dq/785374-magisk-on-gt-king

[Juasser]

Here is something I found on the forums that they were doing for the gt-king basically it explains how to make a recovery image backup then use that to boot magisk but it forces you to leave your box on all the time in that mode. Rather not do that.

https://forum.freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s922x/others-s922x/firmware-roms-tools-dq/785374-magisk-on-gt-king

I was trying that metod at the same time you wrote. I had make magisk work from an external sd and install modules (yeah!!). I'd tried systemizer to make Glimpse Notifications dont ask for notification access, but lo luck, I'd tried MagiskHide Props Config to make play store show all apps without luck too. Im very tired to try and try (4 firmwares reinstalls in 2 days)..... im going to take a break.

[greenstone]

Looks like our only options are waiting for another firmware update and praying that they fix it or finding someone who can figure out how to install and spoof for this.

I contacted my device's vendor and she said that the manufacturer probably couldn't get google certified.so the problem would persist.
I am considering returning the device sadly.

[greenstone]

I am still trying to figure out how to install TWRP so if you know how please let me know.

Here is a link that explains the safetynet/uncertified device issue with google store apps, and why magisk can be used to fix it also they are claiming xposed framework and the the module EDxposed might be able to do so as well.

https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet

[Juasser]

I upload 2 recoverys, one for tpwr an other for magisk. Just copy what you want to an sd and rename to recovery.img. Start up the device with a clip in the hole, wait 10 seconds and relase the clip. If you select twrp then it would show in the screen, if select magisk the device make the full boot but with magisk enablet to use with magisk-manager and could install plugins.

https://drive.google.com/drive/mobile/folders/1-KQY0RQU9mqet1lXgqFOTxVVZ-kPbT95

[greenstone]

Just noticed a weird issue I was having with the box basically the Q and ENTER keys on my minikeyboard arent working right - had to actually change the keyboard input with something someone had on the playstore. Another issue I noticed is that the audio on the box with some movie apps fails unless you turn off and turn the audio back on. Disney+, HBO go and Showtime go seem to have that problem. The CW app doesn't run properly and neither does the CW seed or whatever its called. More time I spend with the box the more I see the issues with it. I have yet to find a game that wow's me, but I dont have a decent android game controller anyway.

[Porkie]

Just noticed a weird issue I was having with the box basically the Q and ENTER keys on my minikeyboard arent working right - had to actually change the keyboard input with something someone had on the playstore. Another issue I noticed is that the audio on the box with some movie apps fails unless you turn off and turn the audio back on. Disney+, HBO go and Showtime go seem to have that problem. The CW app doesn't run properly and neither does the CW seed or whatever its called. More time I spend with the box the more I see the issues with it. I have yet to find a game that wow's me, but I dont have a decent android game controller anyway.

For the keyboard the fix is super easy, go to Vendor/usr/keylayout and delete generic.kl. Then go to system/usr/keylayout and copy generic.kl to vendor/usr/keylayout, set permissions and reboot

[Juasser]

I was trying [ROM] Beelink GT-King ALVATECH Standard Android (9.0 Pie) S922X and seems that the only thing that dont works are the usb. I'd tried and Lan, wifi, bt, Ir... and all works, storage show 128Gb too. Would be wonderful if someone can make a patch to make usb works. I downladed an app from play store to see usb devices and seems that both are reconogised but no input or storage devices work. I post the log.


Device Info
Device Path: /sys/bus/usb/devices/usb1/
Device Class: USB Hub (0x9)
Vendor ID: 1d6b
Vendor Name (reported): Linux 4.9.113 xhci-hcd
Vendor Name (from DB): Linux Foundation
Product ID: 0002
Product Name (reported): xHCI Host Controller
Product Name (from DB): not found

Additional Info
USB Version: 2.00
Speed: 480
Protocol: 01
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto

---------------------------------------------------
Device Info
Device Path: /sys/bus/usb/devices/usb2/
Device Class: USB Hub (0x9)
Vendor ID: 1d6b
Vendor Name (reported): Linux 4.9.113 xhci-hcd
Vendor Name (from DB): Linux Foundation
Product ID: 0003
Product Name (reported): xHCI Host Controller
Product Name (from DB): not found

Additional Info
USB Version: 3.00
Speed: 5000
Protocol: 03
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto

Thanks in advance

[greenstone]

Porkie Thanks for the tip about the keyboard that worked. I renamed the old file in that area to bad-generic and copied over the new file with the proper permissions.


Juasser Was wondering if you can get me the build.props from that rom want to see if we can edit our build.props and "spoof" our box so its recognized as a gtbox for playstore. From what I remember reading on the thread about the gt-king rom there were two roms they made depending on the serial number of the board. I am wondering if we should get that info from our boxes for them.

[greenstone]

Juasser Was able to get a build.prop from alvatech rom:


# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.011
ro.build.display.id=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.version.incremental=20191017
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Thu Oct 17 15:41:30 CST 2019
ro.build.date.utc=1571298090
ro.build.type=userdebug
ro.build.user=alvatech
ro.build.host=AT
ro.build.tags=test-keys
ro.build.flavor=galilei-userdebug
ro.build.system_root_image=true
ro.product.model=GTKing_AT
ro.product.brand=Amlogic
ro.product.name=galilei
ro.product.device=galilei
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Xiaomi
ro.product.locale=en-US
ro.wifi.channels=13
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galilei
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.fingerprint=Amlogic/galilei/galilei:9/PPR1.180610.011/20191017:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.build.expect.bootloader=01.01.180822.152145
ro.expect.recovery_id=0x3bcc839a9ee7293976ba33f666 4930d935f56c02000000000000000000000000


Here is the build.prop from our boxes:


# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.011
ro.build.display.id=galilei-userdebug 9 PPR1.180610.011 20191207 test-keys
ro.build.version.incremental=20191207
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Sat Dec 7 09:43:48 CST 2019
ro.build.date.utc=1575683028
ro.build.type=userdebug
ro.build.user=foxluo
ro.build.host=hugsun
ro.build.tags=test-keys
ro.build.flavor=galilei-userdebug
ro.build.system_root_image=true
ro.product.model=X88King
ro.product.brand=Amlogic
ro.product.name=galilei
ro.product.device=galilei


# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Amlogic
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galilei
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=galilei-userdebug 9 PPR1.180610.011 20191207 test-keys
ro.build.fingerprint=Amlogic/galilei/galilei:9/PPR1.180610.011/20191207:userdebug/test-keys
ro.build.characteristics=mbx,nosdcard
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.build.expect.bootloader=01.01.180822.152145

# begin fota properties
ro.fota.platform=S922X
ro.fota.type=box
ro.fota.oem=x88king
ro.fota.device=x88king
ro.fota.version=X88King_20191207-1003
# end fota properties
ro.expect.recovery_id=0x811716e3d7287246acbcf21694 143e8212a9c5e0000000000000000000000000


Here are few areas that are different:

ro.product.model=GTKing_AT ---vs--- ro.product.model=X88King
ro.product.manufacturer=Xiaomi ---vs--- ro.product.manufacturer=Amlogic
ro.wifi.channels=13 ---vs--- ro.wifi.channels=
ro.build.characteristics=tablet ---vs--- ro.build.characteristics=mbx,nosdcard

[greenstone]

ro.product.model=GTKing_AT ---vs--- ro.product.model=X88King
ro.product.manufacturer=Xiaomi ---vs--- ro.product.manufacturer=Amlogic
ro.wifi.channels=13 ---vs--- ro.wifi.channels=
ro.build.characteristics=tablet ---vs--- ro.build.characteristics=mbx,nosdcard

Hmm replaced these values, cleared the app store cache/storage (including framework and so forth...)

No luck so far.

[raruba]

ro.product.model=GTKing_AT ---vs--- ro.product.model=X88King
ro.product.manufacturer=Xiaomi ---vs--- ro.product.manufacturer=Amlogic
ro.wifi.channels=13 ---vs--- ro.wifi.channels=
ro.build.characteristics=tablet ---vs--- ro.build.characteristics=mbx,nosdcard

Hmm replaced these values, cleared the app store cache/storage (including framework and so forth...)

No luck so far.

Greenstone: nice try....keep up the good work, it would be great if the beelink GT-KING firmware would work on the X88 King.

[Juasser]

Porkie Thanks for the tip about the keyboard that worked. I renamed the old file in that area to bad-generic and copied over the new file with the proper permissions.


Juasser Was wondering if you can get me the build.props from that rom want to see if we can edit our build.props and "spoof" our box so its recognized as a gtbox for playstore. From what I remember reading on the thread about the gt-king rom there were two roms they made depending on the serial number of the board. I am wondering if we should get that info from our boxes for them.

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.011
ro.build.display.id=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.version.incremental=20191017
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Thu Oct 17 17:20:09 CST 2019
ro.build.date.utc=1571304009
ro.build.type=userdebug
ro.build.user=alvatech
ro.build.host=AT
ro.build.tags=test-keys
ro.build.flavor=galilei-userdebug
ro.build.system_root_image=true
ro.product.model=GTKing_AT
ro.product.brand=Amlogic
ro.product.name=galilei
ro.product.device=galilei
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Xiaomi
ro.product.locale=en-US
ro.wifi.channels=13
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galilei
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.fingerprint=Amlogic/galilei/galilei:9/PPR1.180610.011/20191017:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.build.expect.bootloader=01.01.180822.152145
ro.expect.recovery_id=0x3b30004511e5d6ee48ed6d9c0a 8d29245154b555000000000000000000000000

[Juasser]

raruba, would be possible patch boot.img from original x88 to ALVATECH rom, or this is a crazy idea?

[raruba]

raruba, would be possible patch boot.img from original x88 to ALVATECH rom, or this is a crazy idea?

Yeah it shouldn't be that hard, if the only thing that don't work is USB's....should be fairly easy, for him that is....lol