[ROM] Mecool M8S PRO+ Stock & Nano Nexus ROMs (Android 7.1)

[rahzel]

Thanks for the update.

Is it possible to add an option to put the box to sleep from the power button on the navbar? ie long press the power button to give more options?

Changelog (20171210):

• Added local update and backup option from Settings->About->System update based on Amlogic stock OTAUpgrade app.
• Added additional options (Reboot & Sleep) to global action menu that displays when you press and hold the Power button.
• Latest build from Open GApps (20171210)

Known Bugs:

• Wake from sleep will usually result in a restart. This seems to be a bug in the underlying OEM firmware.
• Clicking on Vision Settings in the setup wizard will launch an unsupported activity in Settings.
• You can enable the nav bar in Settings->Display->Statusbar, but may need to toggle back and forth before it will show.

Download:

• Nano Variant: BURN PACKAGE (924MB), OTA UPDATE (478MB ZIP file)
• Stock Variant: BURN PACKAGE (1.42GB), OTA UPDATE (814MB ZIP file)

Yes, and it's really what the OEM does in SystemUI (and supporting framework services). I prefer the Shiningworth approach, where you can dismiss it with the chevrons but then drag it back up from the bottom edge.

I'm working on a Shiningworth release for Amlogic p212 reference board (S905X), which may also work for the M8S Pro+.

Yeah, I'm a heavy Bluetooth user (remote control and headphones), and so I've been looking for a way to enable this on the M8S Pro+. So far, however, I haven't been successful. I've not given up yet, though.

[plazomat]

Hi all,

The nano rom is perfect lite weight install only what ya like - not sure if this is a ROM or Noughat thing..

Is there any way to have a self hiding status bar at the bottom of the screen..I know my MX3 lollipop box has one..

I enable it from settings, not sure if it self hides, but if you reset box it disappears and has to be enabled again.

The nano rom is perfect lite weight install only what ya like - not sure if this is a ROM or Noughat thing..

Plaz

[bylderup]

Guest
I know this was asked somewhere, but can´t find it atm.
I have bought a standard csr4 bluetooth dongle.
Runs fine with libreelec booting from sd card.
Can you add bluetooth support in this android rom ?

Since I flashed your Rom I start the device moreoften with android. With bluetooth support it would be perfect and the SD card could be used to extend Memory.

Yep, that was one of those mix-n-match deals. It worked as a proof of concept, but I didn't have a kernel with the kernel modules to support the other wireless chipsets. There are more options for Nougat on S905X now, so I might give it another try after the holidays.

[noabody]

LOL, what a nightmare.

I realized my faux pas after the post. Here I'm trying to get the manufacturer's designation from a customized firmware that has already been mixed and matched in who knows what way.

Might work with a stock rom built right from the source. Pretty sure the hash on that u2+ fw matched the one from your proof of concept.

Your talents will be known far and wide, though credit may fray along the fringes.

When I first saw the q20x and p21x for ro.product.board, I thought that VideoStrong may have had special reference boards created by Amlogic, but I soon realized that wasn't actually the case. These are just standard Amlogic q201 and p212 reference boards, and there's really no reason that you shouldn't be able to migrate their firmware to any device based on that hardware. As you discovered, the bootloader is looking for a specific device tree ID (amlogic-dt-id) based on its DRAM config and a string template that the OEM hard codes in the bootloader. Most just leave the default ("{ro.board.platform}-{ro.product.board}-{1g/2g/3g}", e.g..gxl-p212-2g), but VideoStrong decided to use their own (gxl-p21x-2g) as did some Shiningworth OEMs (mxq-g9x-2g). Ultimately, it only matters that the bootloader finds a device tree by that ID, but you can mix and match the boot and system partitions pretty safely. (That's not to say that it will successfully boot, but you're not going to brick the box.)

Just to really throw a twist in the works, the S905W SoC reference board has been designated p281. However, VideoStrong's products (M8S Pro W, etc.) have ro.product.board=p21x like the M8S Pro+, which is really wrong. The device tree ids (gxl-p28x-2g) don't match the reference board designation.

[noabody]

Please forgive the question. I've been lurking the forums and finally have Nougat on my TX8 (GT1 ATV 7.1.2, q201-AP6255) and TX5pro (u2+ ATV 7.1.1, p212-qca9337).

I understand that this firmware is for p21x reference board and tried it on the TX5 but it boot-looped (USB burning tool is all I use). Took awhile to comprehend the u2+ stock is for p212 and that is okay. Found the links where Magendanz did the heavy lifting to do a proof of concept for the p212 and also why it isn't currently feasible to build a cfw for it (missing sources or different gfx chip).

Currently my TX5 on u2+ says: "M8S Pro+-userdebug 7.1.1 NMF26Q 20170715-093046.V0321"

It seems like there's a minefield of nougat firmwares with the designation M8S Pro+.


Is there an easier way to tell the difference between a p212 and p21x firmware before actually flashing it? Something in the version strings like V0321 or V0619 (NMF26Q and NHG47L are OS IIRC).

Do I need to try OTA updating from now on (would think it should check version compatibility)?

Thank you for your attention.

Edit:
Thanks Magendanz for being brilliant.

Using information you've provided I extracted some images to look at the vendor ids:

 amlxtract M8S_PRO+-NMF26Q-20170815.182813.V0321.img
 dtc -O dts -o meson1.dts -I dtb meson1.dtb
 cat meson1.dts |grep -i amlogic-dt-id
    amlogic-dt-id = "gxl_p21x_1g";

 amlxtract U2+p212_V0321_Nano-20170730.img
 dtc -O dts -o meson1.dts -I dtb meson1.dtb
 cat meson1.dts |grep -i amlogic-dt-id
    amlogic-dt-id = "mxq_g9x_1g";

 amlxtract MINIMXIII-II_V0321_TVStock-20170730.img
 dtc -O dts -o meson1.dts -I dtb meson1.dtb
 cat meson1.dts |grep -i amlogic-dt-id
    amlogic-dt-id = "mxq_g9x_1g";

Still kinda clear as mud as to why the g9x_1g is p212 compatible while the p21x_1g appears to be p21x. Fun to play with, though.

[ClarkKent]

Nano Version

btw idle temp as seen in Kodi for Android : 44 Degrees C. Device vertical on Wall

Venting up, or down and to r.h. Side? ... Up would be most the effective thermal exodus. Yes?

[whiskandspoon]

Download links not working for me.

*** Update - Being very slow tonight and all is working fine. Can't wait to try.

Well, if you got the Mecool logo there was a problem with installing the update. If it was successful, you'd see a "nexus" logo. If you're not able to boot into system or recovery at this point, you're stuck flashing via USB Burning Tool. Do you have a reset button on your device (behind right front grill next to LED)?

http://freaktab.com/node/660688

[xxxarxas]

Hi again, i tried for flashing nano rom with zip file in sd card via update app. The box stuck it in mecool logo on screen. Unplug it and swich on normaly. After this i downloaded reboot app from aptoide, tried to enter to recovery but the box stuck again to mecool logo. Unplug it and turn on again. What i make wrong?

I received my box (2/16GB) from Gearbest and the firmware is (NHG47L 20170919.150557.V0619) and no reset button, is my box safe to flash the Nano variant ROM?

Yes, we haven't had any eMMC problems with the new units that don't have a reset button.

Which method is better, with amlogic burning tool or with local update? The zip file for flashing is better copied in sd card or to usb flash?

We devs prefer the burn package because there are fewer things that can go wrong. It automatically includes a data wipe and environment checks are done in the u-boot binaries, and so the burden isn't on us to do it in script. That said, if you don't have a reset switch, flashing via USB is a PITA (at least until VideoStrong fixes USB auto-detection). If you remember to check Data Wipe, using the Update app to do a local update with the .zip file is fine...and you can even do it without a USB keyboard or mouse.

Either an SD card or USB flash drive should be fine for local updates using the update app. Both should show in the list when it searches for .zip files.