[ROM] Beelink Mini MX3 II / M8S II TVStock Nexus ROM (Android TV)

Still waiting for the VPN fix please.

From what I can tell, this VPN problem is just a generic issue with the app bar (a.k.a. action bar) running on Android TV. Several apps (including Settings and Terminal Emulator) are missing their toolbar icons on the right and the Up (<) button on the left isn't working.

[sweetnonso]

Changelog (20170606):

• Enabled multi-user support.
• Added kernel module for many USB Bluetooth dongles (btusb.ko).
• Reverted to AOSP keyboard, since Gboard just doesn't have the necessary D-pad navigation support. Leanback keyboard is still also available.
• Switched from spoofing the Xiaomi Mi Box to the Nexus Player.
• Removed several libraries that are no longer required.
• Updated for latest Beelink firmware OTA update (112M0) and Open GApps build (20170606).

IMPORTANT NOTE: This custom ROM is still based on the Beelink Mini MXIII II, but it's the version that contains the AMPAK wireless chipset drivers. These support most AMPAK chipsets, but not the Qualcomm QCA9377. An update for that will be forthcoming...basically as soon as Beelink posts the 112M0 update for QCA9377.

On the bright side, this means that the ROM will work AS IS on the Mini M8S II, which uses the AMPAK AP6255.

Nice update, thanks for your work as always. Still waiting for the VPN fix please.

[EagleEyeXZ]

Oh damm... maybe later?

Magendanz do you also start with android 7.1.1 sdk? SuperCeleron said he does not have time now to start with it but what i read nougat can have a lot new features for the s905x chipset like HD audio

Not on this hardware, but I've started a custom Nougat build on the M8S Pro...right now blocked because I'm lacking a functional TWRP build for that box. I could potentially also do it for the GT1, but they've only got a beta release at this point which is still pretty rough around the edges.

Surprisingly, I've gotten the farthest on the Z28, which uses a Rockchip RK3328. That chipset, however, has problems in that it seems to be natively running in 720p vs. 1080p.

[EagleEyeXZ]

Magendanz do you also start with android 7.1.1 sdk? SuperCeleron said he does not have time now to start with it but what i read nougat can have a lot new features for the s905x chipset like HD audio

[seikt]

Yes, and I ordered one myself last week.

Sweet.

[professeur83]

Changelog (20170606):

• Enabled multi-user support.
• Added kernel module for many USB Bluetooth dongles (btusb.ko).
• Reverted to AOSP keyboard, since Gboard just doesn't have the necessary D-pad navigation support. Leanback keyboard is still also available.
• Switched from spoofing the Xiaomi Mi Box to the Nexus Player.
• Removed several libraries that are no longer required.
• Updated for latest Beelink firmware OTA update (112M0) and Open GApps build (20170606).

IMPORTANT NOTE: This custom ROM is still based on the Beelink Mini MXIII II, but it's the version that contains the AMPAK wireless chipset drivers. These support most AMPAK chipsets, but not the Qualcomm QCA9377. An update for that will be forthcoming...basically as soon as Beelink posts the 112M0 update for QCA9377.

On the bright side, this means that the ROM will work AS IS on the Mini M8S II, which uses the AMPAK AP6255.

Hello and thank you ! You are a killer this firmware is on top

Bluetooth Xiaomi Mi Box remotes can be purchased cheaply on aliexpress. I was wondering if it would be possible to turn on/off these units using a xiaomi bluetooth remote. If not, would it be possible to support this functionality?

Yes, and I ordered one myself last week.

[seikt]

@Magendanz

Bluetooth Xiaomi Mi Box remotes can be purchased cheaply on aliexpress. I was wondering if it would be possible to turn on/off these units using a xiaomi bluetooth remote. If not, would it be possible to support this functionality?

Changelog (20170606):

• Enabled multi-user support.
• Added kernel module for many USB Bluetooth dongles (btusb.ko).
• Reverted to AOSP keyboard, since Gboard just doesn't have the necessary D-pad navigation support. Leanback keyboard is still also available.
• Switched from spoofing the Xiaomi Mi Box to the Nexus Player.
• Removed several libraries that are no longer required.
• Updated for latest Beelink firmware OTA update (112M0) and Open GApps build (20170606).

IMPORTANT NOTE: This custom ROM is still based on the Beelink Mini MXIII II, but it's the version that contains the AMPAK wireless chipset drivers. These support most AMPAK chipsets, but not the Qualcomm QCA9377. An update for that will be forthcoming...basically as soon as Beelink posts the 112M0 update for QCA9377.

On the bright side, this means that the ROM will work AS IS on the Mini M8S II, which uses the AMPAK AP6255.

[sweetnonso]

Thanks ever so much. Hopefully you will crack it soon..

Guest, Just sent you a private message on an entirely different topic, hence i cant write it on here. Thanks.

[techboy_xxi]

Just a reminder that the first flash from the OEM firmware should always be the full burn package using the USB Burning Tool or BootcardMaker. It's necessary to ensure partitions are correctly sized and it has more strict device tree checks than the OTA updater. You'll also get TWRP, which gives you more flexibility for recovery, should something go wrong.

I dont have a fully firmware image, so I asked a seller. He flashed a cook rom into my box using "USB burning tool" like I did. Magically, it works. Comehome, I try flash box using "USB burning tool" again but it cannot work. That's confused

same to me now i can not go to recovery mode and flash rom even with USB burning tool, please help!

Just a reminder that the first flash from the OEM firmware should always be the full burn package using the USB Burning Tool or BootcardMaker. It's necessary to ensure partitions are correctly sized and it has more strict device tree checks than the OTA updater. You'll also get TWRP, which gives you more flexibility for recovery, should something go wrong.

[techboy_xxi]

Just did this and got a success message. Power cycled the box and now it won't even turn on when its plugged in. Just get the red LED. Going to try to recover it with USB burn tool now.

same to me now i can not go to recovery mode and flash rom even with USB burning tool, please help!

[sweetnonso]

Okay, the problem seems to be specific to the TVStock (Android TV) variant, and it's also happening on the GT1/S92 TVStock ROM. I don't see an obvious cause, but I'm continuing to investigate.

Thanks ever so much. Hopefully you will crack it soon..