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

Box has to be ...

"Restoration MECOOL M8S PRO (S912, version 3/32 GB) Firmware using a PC. Requires standard USB cable and Amlogic USB Burning Tool
1. Remove the cover of the attachment.
2. Download and install the Amlogic USB Burning Tool, launch the program, select the firmware via Import Image (M8S_PRO-NMF26Q-20171030.162112.V0619.img).
3. We decide on the contacts that should be closed (The third pair of contacts). (It is better to rehearse the entire firmware procedure several times).
4. We close the contacts and connect the PC to the set-top box. If all goes well, a beep sounds and Connected appears.
5. Connect the power supply and press the Start button.
6. After the end of the firmware, click Stop and close the program." [translation]

[Tyrannar]

Maybe not, let him try with mask rom method, flashing the original firmware back by shortening the pins on NAND flash !?



post #3300 on 4PDA.ru

Thanks for the heads up.
Box has to be plugged in power for that to work or I just disassemble it and short those pins without plugging anything?

.....Unfortunately, I had no luck. I am afraid your box is dead my friend

Maybe not, let him try with mask rom method, flashing the original firmware back by shortening the pins on NAND flash !?



post #3300 on 4PDA.ru

[thgiakit]

I had the same situation with another box. I tried myself to solve the problem and to revive the box. i spent countless hours researching the internet and several forums. Unfortunately, I had no luck. I am afraid your box is dead my friend

[Tyrannar]

Guys, please help

I'm getting the dreaded 0x10303004 romcode error result while trying to flash either nano or stock version of ROMs.
I also tried with the original MECOOL M8S PRO 20180412.img from but the problem persists, flashing starts once I connect the box and stops at 4%
Has anyone had any luck solving this?

[nunoedge]

I've used both Nano and Stock and Ethernet still doesn't work

Anyone with this problem?

[Androidboxlover]

What's the main difference between nano and stock variant? I installed one before for my M8s but don't remember which one

[lepa71]

How do I switch between mouse and arrows with the remote? Once I click on mouse button on the remote I get stock with mouse control.

[S0L0]

what did you install?

First, Stock Variant: OTA UPDATE (824MB ZIP file) and then ATV version.

[zenix]

Thank you for this topic Guest !

Very easy and fast to install !

what did you install?

[S0L0]

Thank you for this topic Guest !

Very easy and fast to install !

[billsboxt]

OK, I managed to reflash 20171030 using the TWRP recovery that was installed with the Nexus ROM (it was the fixed version from Magandanz), However this is still ATV.

I have "MECOOL M8S PRO SD 20170817.zip" which I now think is *normal* android, however I cant flash it through the standard recovery (giving a cant flash older ROM message), and I cant flash through TWRP (giving this ROM Is for M8SPRO and this device is a q20x message).


Can anyone advise how I can modify the 20170817 ROM to make it flashable and thus get back to a standard Android where I can use you tube?

thanks IA!

[billsboxt]

Guys, i'm a little stuck here:

I have a M8S Pro (actually bought on behalf of a colleague, I actually use a BB2 Pro myself).

I deliberately bought the Pro (as opposed to the 'L') because I wanted standard Android, not ATV.

Upon receiving the device I was disappointed to realise that youtube, playstore etc were ATV. I then started researching the options and eventually found this thread and downloaded the Nexus firmware and installed and everyting works fine EXCEPT for youtube, where I get terrible purple and green corruption on videos in 1080p. I also get options to set the resolution higher than 1080p, which I don't see on my BB2 (presumably because the box recognises the connected TV's 1080p maximum capabilities.)

I have found a mention of the same problem in this thread, but I do not understand the solution! I will post in this thread later on to see if I can get some clarification:

https://forum.freaktab.com/forum/tv-player-support/beelink-aa/beelink-android-tv-box/gt1-ultimate/firmware-roms-tools-ch/722668-rom-beelink-gt1-ultimate-android-7-1-2-alvatech-ddr4-newer-boxes/page15

The only other option I've got is to install the 20171030 firmware, which I THINK is standard Android and may therefore sort my problems...

any pointers appreciated. I'm kind of wishing i'd got another BB2 pro really!

[ClarkKent]

Guest
Please clarify for me:
The update between these two, Does Not require a factory reset?

The expected changes to the former "L" based rom are, solely listed in the Change log...
And, the Nano Variant?

• **Beyond the above description, No major UI changes are likely to be noticed?
• YOUR opinion / insight on aAlwinner SOC would be appreciated too

Changelog (20180310):
Updated to latest M8S Pro L OEM firmware (20180205.111652.V0928


Nano Nexus variant:

• Open GApps Nano Package
• Google Now Launcher (replaces OEM Launcher)
• Google Chrome Browser (replaces AOSP Browser)
• Google Legacy Camera (replaces AOSP Camera)
• Google Desk Clock (replaces AOSP Desk Clock)
• Google WebView (replaces AOSP WebView)
• Terminal app from LineageOS
• TWRP Recovery 3.2.3-0 by TeamWin

Changelog (20180829):
Updated to latest M8S Pro OEM firmware (20180412.194117.V0213)

• Updated to TWRP Recovery 3.2.3-0
• Preserves Miracast from OEM firmware
• Latest build from Open GApps (20180828)

[t23]

I've been running 20180310 on a KM8P for a while now (i don't need wifi anyway), and it has been running completely smoothly. Upgraded to 20180829 a few days ago, same thing, spins happily.

However, on both revisions, i have had the dreaded "black square" syndrome. When i reboot, the arrow cursor is replaced by a black square, and it remains that way until i hover over a text input field (like the "rename app/folder" options in the Apex or Nova launchers), then all is fine till reboot.

A Google search shows a lot of people asking the same question, but i cannot find an answer that makes sense.

Note, though, that switching to large cursor in Accessibility eliminates the problem, but yikes, i'd rather avoid that!

Any of you kind people out there know how i can fix it?