[ROM] Mecool M8S Pro TVStock Nexus ROM (Android TV 7.1)

[Novato]

Finally my m8s pro arrived !!! LOL .. after months of wait, I now have him in hands! the question which is now is then maybe this ROM is compatible with my model? So...Guest my device is a m8s pro 2gb of Ram and 16gb storage, he is compatible? has not updated for latest version, I can just install as update OTA playing your firmware for card memory?

Yep. If you use the OTA update, just make sure to check the box to Wipe Data.

[Novato]

Thanks, Magendanz , I did update OTA and it went well. I loved ROM, congratulations! Just had a few problems that made me a little sad, for example, when I click on the Power button, instead of just turning the screen off, the device turns off, for example, the device deletes the screen as it should, but when I press the button to light I realize that it is being initiated. Holding the Back button shows "Google Stoped" message, but the Google button on the screen returns. However the worst is that my GameSir control does not work the buttons after connected via Bluetooth, it is working fine, but via Bluetooth it is impossible to use it, it only works with Dogle Wi-Fi or USB cable.

Yes, the standby recovery issue is listed in the Known Issues of the release notes. I'm hoping that VideoStrong will fix it with their next release. The long press on the back button is because I set config_longPressOnBackBehavior to 1, which should bring up voice assist. I understand now that option is only available for watches, and so that's why the Google app crashes. I'll remove that "feature" with the next release.

[Novato]

There is excuse my bad English, my native language is Portuguese, I am using Google translator to help translate it.

[Novato]

Hi, I'm here again, I wonder if it's possible to go back to the original ROM by putting the .IMG file (available for download) on the memory card and flashing through TWRP, or just passing through the PC with the flash tool? I would also like to know if I would have an OTA update to return to stock.

No, the single .img files distributed for these devices are Amlogic's proprietary burn packages, not the standard Android partition images contained in the Google factory images or OTA updates. They need to be flashed with Amlogic USB Burning Tool or BootcardMaker.

[Roman8d5]

Good evening, M8S Pro TVStock Nexus ROM (Android TV 7.1) does not work Bluetooth ?, does not find Rapoo A3020

[Novato]

Thanks Guest, I loved this ROM, I love Android TV OS, but unfortunately I need to go back to a stock version of Amlogic for being a little more stable, but I'll wait for your next builds to be able to go back to Android TV, keep doing this great job.

[Novato]

Good evening, M8S Pro TVStock Nexus ROM (Android TV 7.1) does not work Bluetooth ?, does not find Rapoo A3020

The Bluetooth works for me, connects my device, receives files from my cell and etc. The problem was only with my control gamesir, I believe that has more relationship with the mapping key itself that with Bluetooth.

[Guest]

Changelog (20171103):

• Updated to latest M8S Pro OEM firmware (20171030.162112.V0619)
• Removed attempt to launch voice assist on Back button long press. (only valid for watches)
• Latest build from Open GApps (20171103)

Download:

• TVStock Variant: BURN PACKAGE (999MB IMG file), OTA UPDATE (526MB ZIP file)
• Flash burn package with Amlogic USB Burning Tool v2.0.8 or BootcardMaker v2.0.0.2

[Novato]

Thanks Guest, I'll install the update later. I'm hoping my bluetooth gamepad will work fine in this version.

I did update the kernel modules from the latest GT1 OEM firmware release, so give it a try.

[clarkss12]

I keep getting an error when I try to do the zip update using TWRP. Downloaded twice, tried with USB memory stick, both ports, also tried with microSD card.... *** Unable to Mount Storage ****

[Novato]

Unfortunately, the update also failed for me ... I updated and gave aborted update.

[Novato]

Unfortunately, the update also failed for me ... I updated and gave aborted update.

OTA Update Aborted

[Guest]

When the 20171005 build was first released, it had the wrong device code. This error was quickly corrected in a subsequent rolling update, but you'll need to make the correction yourself. (The check is critical so that you don't install the update on the M8S Pro L, which will brick the box.)

Just install a root file explorer like EFS File Explorer and modify the build.prop value for "ro.product.device" from "M8S_Pro" to "M8SPro". After that, the update should pass environment checks.

Alternatively, you can just flash the burn package (or comment out the check in the updater-script).

[clarkss12]

I used the burn package, so all is good now.

[Novato]

I used the burn package, so all is good now.

Thanks for the feedback, can you tell if the Bluetooth Gamepad is working well?