Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

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

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • suarez23
    replied
    Guest
    Thank you for the link, but what is the password?

    Leave a comment:


  • Guest
    Guest commented on 's reply
    It's all archived here: http://freaktab.org/27~f

  • sigdrak
    replied
    So, from my last experiments, I think at least on my box, I have random failure to get to recovery. Whether initiated by an app, or through the reset button, I sometimes end up with a blank screen after the nexus logo (ie no video signal), and a non-responsive box (power unplug required).

    As for my needs, no improvements, so I'm basically barred to use DRM-based applications. ctsProfile reamins false whatever I try with magisk, so maybe editing various fields in build.prop is needed...

    Leave a comment:


  • suarez23
    replied
    Guest
    Do you suggest that reinstall of the rom can help with the ATVRemoteservice.apk ? ---I've just tried using Burning Tool - it didn't help
    Could you send me active link to the previous ATV rom (Burn Package), please.
    Last edited by suarez23; 20 February 2019, 11:47.

    Leave a comment:


  • sigdrak
    replied
    So, managed to wriggle around the HDMI and flash the OTA package using the TWRP recovery. Couldn't get the default AMLogic using a SD card to work, and getting to the recovery is somewhat random. Tried 2 apps, the reboot to recovery does reboot, but after the Nexus logo, often the screen goes dark, and then no signal.

    Installed magisk (hardly ever used it, just wanted an alternate way of rooting with hiding possibilities). SafetyNet level of basic by default. Trying to hide, and using a module to work around liboemcrypto did not increase the level/ctsprofile thingie. Might need to completely remove the (Super)SU stuff, as I don't need it extensively, and can reinstall it in TWRP.

    EDIT: tried that, failed. It seems to behave differently, complaining about DRM issues.
    Last edited by sigdrak; 20 February 2019, 00:21.

    Leave a comment:


  • Guest
    Guest commented on 's reply
    I've had that happen to me with a couple of boxes. They just stopped working with no explanation. Sadly, the build quality on these things is pretty marginal.

  • sigdrak
    replied
    Sorry, don't know how to quote a reply on this forum.

    I wasn't clear. I haven't even flashed the ROM or anything else. I've just started the box as usual (well, last was 4 months ago...), but I had no video output. Tested on 2 TVs.

    So my issue is not related to the update, and is actually off topic..

    Leave a comment:


  • Guest
    Guest commented on 's reply
    Was it the burn package or the OTA update that you used? Is there any chance you've got one of the affected batch from last summer?

  • Guest
    Guest commented on 's reply
    The problem is that the AtvRemoteService.apk for Nougat crashes without Bluetooth support, which this box doesn't have. Until now, I've been able to get the Marshmallow build of AtvRemoteService working on it, but it's been pretty temperamental. My guess is that one of the static libs wasn't installed correctly. (The new version doesn't use static libs.)

  • Axe
    replied
    Originally posted by Davvid View Post
    Hello.

    Is anyone able to play anything in official HBO Go TV app https://play.google.com/store/apps/d...dtv.production (from the Play Store) ? L1 or L3?. I can't (error 5.1) with L3. App activates, I can browse all but it plays nothing. I thought it would run with forced L3 widevine.

    Fortunately it works very good in Kodi via addon (in 1080p) but I'd like to use native app.

    Thanks.
    Same here. Mine is L1, but i also got 5.1 error. I also hide root status to hbo apk with magisk, but still the same result .Error 5.1.

    Very complicated to watch service you already payed .

    Leave a comment:


  • sigdrak
    replied
    Originally posted by Magendanz View Post
    Changelog (20190213):
    • Wake from sleep will no longer result in a restart. This was fixed in the underlying OEM firmware.
    • Developer Options now visible by default in Settings.
    • Updated to latest M8S Pro+ OEM firmware (20180806.102424.V0213)
    • Updated to TWRP Recovery 3.2.3-0 using omni-twrp-8.1 branch and latest OEM kernel
    • Latest build from Open GApps (20190209)
    Known Bugs:
    • Google Cast service broadcasts and is discoverable from mobile devices, but quits unexpectedly unless connected through Chrome.
    Download:
    Thanks for the update! There seems to be a lot of happy people.

    No issue with the ROM, but I couldn't test it! I started up the bo, and discovered I no longer had any output on HDMI. The box still reacts to the remote controller and to pressing the reset button.

    Leave a comment:


  • suarez23
    replied
    I just wanted to ask if anybody has a problem with ATV Remote app in the newest ATV rom. I can find my M8S pro+ and pair it with the phone over WiFi but it disconnects after a second and goes back to the screen with ATV devices to choose. Doesn't metter if I'm using phone with Android 4.4 or 7.1 - always the same. It probably means that the problem is on Mecool (with ATV rom) side.
    I had no problem with android remote on the previous ATV rom. Has the remote service changed in the new rom comparing to the previous one ?

    Leave a comment:


  • Guest
    Guest commented on 's reply
    TWRP to the rescue! It has saved my bacon many times. ;-)

  • legnosecco
    replied
    • @ Magendanz commented 02-18-2019, 12:47


      If you replaced the file instead of editing it in place, make sure that the permissions are restored. Ideally, you'd restore the file context, but usually just running a chmod 644 will do the trick. Also, make sure you didn't the line endings or encoding on the text file.

      Long story short.... (see post #1999 above)
      I was stuck on colored circles after many reboots.
      I then rebooted pressing down on RESET button.....and got the green robot with a RED cross.
      Tried this several times...always the same.
      Then suddenly I get TWRP come up on screen.
      I reflashed the OTA update again and all is good...did not lose any apps or anything.

    Leave a comment:


  • Guest
    Guest commented on 's reply
    If you replaced the file instead of editing it in place, make sure that the permissions are restored. Ideally, you'd restore the file context, but usually just running a chmod 644 will do the trick. Also, make sure you didn't the line endings or encoding on the text file.
Working...
X