Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

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

Collapse
This is a sticky topic.
X
X
Collapse
 
  • Page of 23
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 19 23 template Next
    #121
    I've been using the 20171005 TVstock ROM for a couple of weeks... very nice, thanks Magendanz. One issue: I use an air mouse rather than the provided remote, and when the device goes to sleep after 30 minutes it can't be woken up with the airmouse. Keeping the other remote around just for this is a pain. Enabling Developer options and setting Stay Awake When Charging doesn't stop the box from going to sleep. No need for the box to go to sleep, i'd rather it was just awake all the time. Any ideas how this can be done?
    Thx!

    Comment

      #122
      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:

      Comment

        #123
        amigo magendanz, una pregunta en esta nueva actualizacion se soluciono el tema del Bluetooth y del internet por medio de cable, gracias de todas forma por esta actualizacion

        Comment

        • Guest's Avatar
          #123.1
          Guest commented
          04 November 2017, 18:50
          Editing a comment
          I wasn't aware of any Bluetooth or wireless issues with this ROM. I believe that's specific to the Shiningworth All-in-One ROM (a.k.a. Precious), which uses a bad QCA9377 driver.
        #124
        Magendanz, your new 20171103 version won't install on top of 20171005 version using update zip from recovery... complains "Found Nexus M8S Pro... this package is intended only for M8S Pro". I guess you need to add another case to your device model check...

        Comment

        • Guest's Avatar
          #124.1
          Guest commented
          04 November 2017, 18:57
          Editing a comment
          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).
        #125
        after the update, the status bar is missing and it wont turned on..

        Comment

          #126
          I also have the status bar issue.
          Another bug: after the update, double-tapping Home key on my airmouse no longer brings up Recents, instead a dialog saying "System UI crashed".

          Comment

            #127
            Guest ...your comment 124.1 is advised for all confirmed m8spro/20q boxes?
            I've had issues with trying to flash 100517 via twrp. Box defaults to: "found" 091817 nano (incremental?).
            Status bar works like a champ. Once ticked in settings, appears as desired provided not viewing full screen Video... dropping mouse to screen bottom retrieves it- No swipe needed.
            Will this feature wain if ROM is update to latest build? ALL must be wiped ,Except for Internal data, correct?
            Kris....don't forget my boxes! Okay?

            Comment

              #128

              Well, it seems that System UI is broken in this build, and reverting SystemUI.apk to the previous release didn't fix the problem. The issue is probably in the framework services, so it will take a bit of time to troubleshoot. Please be patient.

              In the interim, you can revert to the previous release (20171005). I haven't removed them from the share yet. https://1drv.ms/f/s!AoqocX31ecnXgZ00eUEfqUI7zwHZpA

              Comment

                #129
                Okay, I found and fixed the SystemUI problem causing the missing the navigation bar, status bar and crashing recent apps view on these non-ATV builds. It's a rolling update, and so you'll need to refresh your downloads using the same links and reinstall. If updating with the OTA update, no data wipe is necessary.

                I apologize for not catching this during release testing. The error was mine, not one from VideoStrong.

                Comment

                  #130
                  Originally posted by Magendanz View Post
                  Well, it seems that System UI is broken in this build, and reverting SystemUI.apk to the previous release didn't fix the problem. The issue is probably in the framework services, so it will take a bit of time to troubleshoot. Please be patient.

                  In the interim, you can revert to the previous release (20171005). I haven't removed them from the share yet. https://1drv.ms/f/s!AoqocX31ecnXgZ00eUEfqUI7zwHZpA
                  In an effort to set a new soft brick record ...
                  I''ve been successful. I was running nano I20170918.111557.V0619... do not find that ROM in your file repository.

                  I'm assuming anything predating that is for q201, so not recognized. Everything after that in zip form, is an update... So rejected.

                  your October build img. ROMs, need to be flashed to which partition? Recovery? TWRP will not provide any choices, or allow me to edit the partition line.

                  So, I am both stuck and at a loss. Judging from my files I can find, and space available, Etc...
                  I believe most of my apps and data are still intact. Hopefully my build prop data, for flashing to use as a reference point, is still present but I can't find it's backup files.

                  where do I go from here? I am confined to TW RP, as I have no PC platforms. Can you throw me a lifeline?
                  I promise I'll be more careful in the future. Thanks * 10

                  ps where to find your GT1 ultimate ROMs, I have one of those coming later this week. Do I understand correctly it can be used on this m8s Pro also?
                  Kris....don't forget my boxes! Okay?

                  Comment

                  • Guest's Avatar
                    #130.1
                    Guest commented
                    09 November 2017, 00:36
                    Editing a comment
                    Yes, as I've tried to emphasize repeatedly, the Amlogic burn package isn't the same as a partition image file, despite the fact that they have the same .img file extension. So you can't flash Amlogic burn packages in TWRP; it must be done in USB Burning Tool (or with BootcardMaker).

                    From TWRP, you should be able to install this update (.zip file): https://1drv.ms/u/s!AoqocX31ecnXgachPc5OcV7q0bCeDA

                    It's based on the 20171030.162112.V0619 OEM firmware, which is newer. Your apps and data should also be preserved.
                  #131
                  Well thank you. We will give it a try, fingers crossed. To be clear then all image files found on freak tab, as well as most others found on the net for these devices, will NOT be image partition files. Correct?
                  I must have found one for my M18, as I'm pretty sure I flashed an image through TWRP.
                  nubes are dangerous things...
                  Kris....don't forget my boxes! Okay?

                  Comment

                  • Guest's Avatar
                    #131.1
                    Guest commented
                    09 November 2017, 00:55
                    Editing a comment
                    Correct. We usually post Amlogic (or Rockchip) burn packages, which contain the partition map and images for all the needed partitions in one file. If you find a raw partition image, it's usually for a custom recovery like TWRP.
                  #132
                  Guest
                  I pretty sure in build.prop I had removed the underscore between m8s and Pro... do I need to do the same to this file before trying it? Danke
                  Kris....don't forget my boxes! Okay?

                  Comment

                  • Guest's Avatar
                    #132.1
                    Guest commented
                    09 November 2017, 01:02
                    Editing a comment
                    Yes, the update script is looking for ro.product.device == "M8SPRO".

                    Alternatively, you can just unpack the .zip file and remove that check from the updater-script, then repack as a .zip. At that point it will be unsigned, but TWRP signature verification is off by default.
                  #133
                  I have a problem with my tv box. I want to use it to stream games using Nvidia Shield and Moonlight. Because I have a big latency (250ms) I have seen that I have low bandwidth. Application "Speedtest.net" show me 8-10 mbps bandwidth. I tested through wifi and lan. My Router is: TP-LINK M5R (1gbit lan, or 600mbit wifi 5Ghz). Testing on my computer the connection shows me 119mbit. What's wrong?

                  Comment

                    #134
                    @magendanz.
                    pretty sure .zp repacked properly...learning is fun !
                    i got an error4 with one, error7 with another repack,
                    though I thought both were edited identically. Whatever?

                    Does E#7 mean, i may have to delete the 'build prop verify' command line completely from script?
                    - i can't find build prop file/ bk.up within my data still accessible. ...Where to look?
                    - If intact, BP was last edited to 'M8SPRO'...so, your suggested edit is both necessary and critical!

                    btw...I wouldn't/ didn't attempt a burnpkg. You were received well on that point early on....just ota's

                    -But, Any updates are just that? They must be added to the base version, and are Not stand alone?
                    ....or complete Roms up thru latest tweak.
                    ________________

                    pls, another couple questions...

                    ~ m8sPRO L 's widevine means yt Red will automatically stream fhd (predominantly) ?
                    ~ Have you finished your gt1 ultimate? Where to find when?
                    ~ Submariner, or Sub Mariner... ?
                    Last edited by ClarkKent; 10 November 2017, 06:32.
                    Kris....don't forget my boxes! Okay?

                    Comment

                    • Guest's Avatar
                      #134.1
                      Guest commented
                      10 November 2017, 09:15
                      Editing a comment
                      I release full block-based OTA updates, which include full images for all the partitions included in a burn package. They don't need to be installed over a known base release like incremental updates.

                      I think you figured out what was going on with your .zip archive, right? You must have the same file hierarchy as the original.

                      I know that Widevine L1 is needed for Netflix, but I don't know for sure about YouTube Red. I can confirm that it's necessary for YouTube TV.

                      The GT1 release for standard & ultimate was done over the weekend, but I'd hold off for an update that I'm going to do tomorrow. I just received an update for the underlying All-in-One ROM from Shiningworth.

                      ...and it's pronounced, "Bubblehead". ;-)
                    #135
                    Hi magendaz.
                    I use the nexus Nano rom (non atv) 18/9/17 v0619 on my mecool m8s pro. Its working very good. Can i update using this nano OTA rom (#122) or it is another type of rom? I dont wanna burn this rom. I wanna use the OTA option
                    thank you very much

                    Comment

                    • Guest's Avatar
                      #135.1
                      Guest commented
                      10 November 2017, 20:23
                      Editing a comment
                      Most definitely! Just install it in TWRP.
                  Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 19 23 template Next

                  What's Going On

                  Collapse

                  There are currently 1775 users online. 0 members and 1775 guests.

                  Most users ever online was 63,956 at 18:56 on 20 March 2025.

                  Working...
                  X

                  We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                  By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                  I Agree