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

[ClarkKent]

Guest
I'm guessing Gina's update will Not run on this Rom? I suppose just placing her supplied bin files within the system is a useless attempt also? What do you suggest to regain said feature? Thnx

[ClarkKent]

Guest
Had a few issues at first...Gapps was inoperable, loaded but no data. Desktop wallpaper present, but that was all. .Possibly due to flashing via twrp?
Successfully flashed now. Nicely setup, very quickly boots with a full compliment of added apps. Smooth and perhaps even better rendering. Opted for 32g adopted storage, allowing better storage and addressing for vid library. Lots of other features to become familiar with. All network protocols working quickly as well...no problems encountered virtually anywhere. Only downside, Loss of L1 and corresponding hdcp 1.1. That is a drawback.
Also noting system does not recognize or address any USB drives. Is a fix available for this?
. Great work though! Many kudos

Yes, it's based on the same Shiningworth firmware release, so you won't see any changes in the About panel. Just has new OTA update script, new Mali driver, new Bluetooth libraries, and latest OpenGApps.

[zenix]

Here's another revision of our little experiment building Nexus Nano for the M8S PRO on the Shiningworth All-in-One firmware:

Burn Package: Nexus_M8S_Nano_NHG47L-20180202.img
OTA Update: update_Nexus_M8S_Nano_NHG47L-20180202.zip

This has the following fixes:

- Fixed OTA update script to accept a ro.product.board of "q201" or "q20x".
- New build of Mali driver that supports OpenGL 3.2 + AEP
- New Bluetooth libraries that seem to fix the audio stuttering problem on the Longsys LTM8830.

I'm still seeing intermittent wireless issues, but I think we're getting pretty close. Anyone spot any other problems?

I did flash succesfully. No visible changes and no version changed in system settings/"about this box".
Thank you

[ClarkKent]

My bad, typo.
**Edit: Third time's a charm. I'll blame it on peripherals.. .; )

Looks good!
Any tips on using new settings?
HDR and framerate switching, etc,?
** Will this update recognize and support a 64g SD card as adopted memory? 0r is it HW restricted?

What's "q20q"? No, it definitely won't accept that. And if the environment check fails, it won't change anything.

[ClarkKent]

"This has the following fixes:
-- Fixed OTA update script to accept a ro.product.board of "q201" or "q20x".
-------------------
CM... Is it possible the script still has a exclusion for q20?

ro.build.description")); ((file_getprop("/system/build.prop", "ro.product.board") == "q201") || (file_getprop("/system/build.prop", "ro.product.board") == "q20x")) || abort("E3004: This update package is intended only for the Amlogic q201 reference board.");

Not flashing yet

[rwdwg]

Here's another revision of our little experiment building Nexus Nano for the M8S PRO on the Shiningworth All-in-One firmware:

Burn Package: Nexus_M8S_Nano_NHG47L-20180202.img
OTA Update: update_Nexus_M8S_Nano_NHG47L-20180202.zip

This has the following fixes:

- Fixed OTA update script to accept a ro.product.board of "q201" or "q20x".
- New build of Mali driver that supports OpenGL 3.2 + AEP
- New Bluetooth libraries that seem to fix the audio stuttering problem on the Longsys LTM8830.

I'm still seeing intermittent wireless issues, but I think we're getting pretty close. Anyone spot any other problems?

[ClarkKent]

Recovery and TWRP continues to be missing or unaccessible... A new hiccup.

It is possible when re-flashing last rom and su zip, i mistakenly included a indentical local twrp zip.
Apparently the conflict killed any & ALL recovery access or options.
... A fresh .img from mag's uploads, and helped by pre-release of 'Amlogic TV box Tools' (@ playstore) did the job. I was seemingly stranded, now just a little amazed.

[zenix]

Congrats! Was gonna say pm me, but?.. Sometimes tinkering is best
Struggling with missing recovery here. I think is solved now. I tried flashing latest, with your same results.
So, I'll take your cue.. I think it's q201 vs. q20 board conflict. Gotta look at log data to confirm
You replaced entire update script from Mag's last (2017) 8sPro build? Yes?

** how are you getting 4k yt? They are thin on true hd source media, methinks

I unziped the last mags (2017) ota update, i took the updater script from meta inf file then i unziped the last (2018) ota update and replaced the new with the old updater script, zipped again and flashed in twrp.

About youtube:
i have a 4k hdr lg and when i search for a 4k video hdr, for example "chess hdr", in the resaults i take a lot videos and when i play one of them , youtube let me to choose the qaulity, 1080p hdr, 1440p hdr, 2160p hdr etc. The problem is that in 2160, yt buffering cause i dont have very fast internet. In 1440p its ok. Great picture
This happens from the first time i flash magendaz rom. Not only now.

Thank you and thank mag too

[ClarkKent]

Finally i did it. Just replaced the updater script with the old one included in the previews (16/11/17) ota update snd then flashed in twrp

After the update, in settings/info, i see "Netflix ESN". If you click it, does nothing. Anybody knows what is that?

Congrats! Was gonna say pm me, but?.. Sometimes tinkering is best
Struggling with missing recovery here. I think is solved now. I tried flashing latest, with your same results.
So, I'll take your cue.. I think it's q201 vs. q20 board conflict. Gotta look at log data to confirm
You replaced entire update script from Mag's last (2017) 8sPro build? Yes?

** how are you getting 4k yt? They are thin on true hd source media, methinks

[zenix]

After the ota update, widevine level is now 3, hdcp is unsuported but youtube is 4k

[zenix]

Finally i did it. Just replaced the updater script with the old one included in the previews (16/11/17) ota update snd then flashed in twrp

After the update, in settings/info, i see "Netflix ESN". If you click it, does nothing. Anybody knows what is that?

[zenix]

Once in TWRP, prefix file name is of lesser importance.
Copying of log data will show what happens just prior to the e7
Probably the roms target device is a mismatched name, as compared to your actual box's identity.
Compare the two... Open the zip in its own folder, open meta down thru android. Once at updater script, that will open in a script editor for matching the two targets.
Once done, reZip and move back to 1st level of sd.
It should go by reset recovery or ota via twrp in either case. METHOD 1: UPDATER SCRIPT HACK TO FIX ERROR 7

Note: Use this method only when you’re 100% sure that the ROM you’ve downloaded is for your device. What this does is to bypass assert checks in recovery so that you can install the ROM without any checks.

1. Open the Lineage OS ROM zip using any archiving software like 7zip, WinRAR, etc… You can also open it on your device.
2. Now, you need to navigate to this path: META-INF » com » google » android » updater-script.
3. Open the file updater-script in a text editor. You’ll see a bunch of lines with the command assert and the model name of the device next to it.
   
4. If there’s a mismatch with the codename of the device in the script, you’ll get Error 7 while flashing.
5. So, just either edit the code to match your device’s codename or delete all the lines having the code “assert & getprop”
6. Save the file.
7. Try to install the ROM now.

First of all, thank you for your interest.
i edited the updater script and there are no lines with "assets" e.t.c. I also edited the previews OTA update file (16\11\2017) that was downloaded in my box and i saw that there are no lines with "assets" too. It is only one line "getprop" with the name m8spro.
so i found the same line with getprop in the new OTA and i changed the name of the box from "q201" into "m8spro" and tried to flash again but i got the same error.
Next thing i ll do is to replace the new updater script with the old and try again.

P.s is it possible the new ota file to be corrupted OR not to be for m8spro?