Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

MECOOL M8S Pro + TV Box Amlogic S905X Android 7.1 2/16GB Fast Lan, WiFi 802.11b/g/n

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • stelakis1914
    replied
    My advice is that if it works well do not teasing. After my entanglement, i would suggest that.

    Leave a comment:


  • cph666
    replied
    Originally posted by stelakis1914 View Post
    I am victim of cursed geekbying OTA update who destroyed my tv box. I have eMMC 5.1 chipset: SEC652 KLMAG1JENB B041 and the 20170829 stock firmware has work nice before. I extremely regret to take the decision to update. Now don't have many hopes to unbrick the TV Box.
    I also got this box delivered with the above SEC652 and it's with the 20170829 firmware from Gearbest.
    Any hint what to do now? I'd like to use Magendanz's firmware now or perhaps do "official" OTA updates.

    Leave a comment:


  • Matruchoti
    replied
    Hi, noob here, I have lots of experience flashing Android cellphones but no tvbox... I bought one of this boxes with the intention of dual boot Libreelec and AndroidTV custom ROM, my box is on its way, bought it in YUANDA America throw Amazon but I have no idea if it's one of the bad ones... What should I look at when it arrives and what do you guys recommend me to do if it is one of the bad ones...
    Thanks!

    Enviado desde mi Moto G (4) mediante Tapatalk

    Leave a comment:


  • stelakis1914
    replied
    When I rarely succesfully to connect the box with the USB Burning Tool, always the process stopped in 4% and take these faults on photos. Someone can help me to solve this? Thanks.
    You may only view thumbnails in this gallery. This gallery has 3 photos.

    Leave a comment:


  • P.X
    replied
    1 comment

    #584.1
    scooter2014 commented
    10-01-2017, 15:01
    I am sorry but Id consider this a manufactures defect and they should replace any affected. Mecool should offer replacements to units affected.
    They should if you can get them to agree with the consensus opinion of the defect.

    Leave a comment:


  • P.X
    replied

    Leave a comment:


  • stelakis1914
    replied
    I had try this image too. Thanks for your support!

    Leave a comment:


  • scooter2014
    commented on 's reply
    I am sorry but Id consider this a manufactures defect and they should replace any affected. Mecool should offer replacements to units affected.

  • P.X
    replied
    Originally posted by stelakis1914 View Post

    As i wrote i try with many firmwares with no luck. If you have some specific link for your suggested firmware please post it. Thanks.
    1 comment

    Leave a comment:


  • stelakis1914
    replied
    Originally posted by P.X View Post

    Have you specifically tried the recovered 08.29 IMG version that Magendanz made to get back to the starting point again?
    If you have, my commiserations.
    As i wrote i try with many firmwares with no luck. If you have some specific link for your suggested firmware please post it. Thanks.

    Leave a comment:


  • P.X
    replied
    Originally posted by stelakis1914 View Post

    I have many trials with various firmwares (stock and custom) and the things get worst.
    Have you specifically tried the recovered 08.29 IMG version that Magendanz made to get back to the starting point again?
    If you have, my commiserations.

    My totally bricked one has the same build date as yours, with an SEC 701 batch code.
    Luckily for me it had bad signs of an issue before any FW changes so I could complain to GearB early.
    Nothing helped it either.

    Leave a comment:


  • stelakis1914
    replied
    Originally posted by P.X View Post

    Have you tried reverting to the 08.29 OEM FW ?
    It has worked for a few ...
    Hope you are lucky

    I have many trials with various firmwares (stock and custom) and the things get worst.

    Leave a comment:


  • P.X
    replied
    Originally posted by stelakis1914 View Post
    I am victim of cursed geekbying OTA update who destroyed my tv box. I have eMMC 5.1 chipset: SEC652 KLMAG1JENB B041 and the 20170829 stock firmware has work nice before. I extremely regret to take the decision to update. Now don't have many hopes to unbrick the TV Box.
    Have you tried reverting to the 08.29 OEM FW ?
    It has worked for a few ...
    Hope you are lucky


    Leave a comment:


  • stelakis1914
    replied
    I am victim of cursed geekbying OTA update who destroyed my tv box. I have eMMC 5.1 chipset: SEC652 KLMAG1JENB B041 and the 20170829 stock firmware has work nice before. I extremely regret to take the decision to update. Now don't have many hopes to unbrick the TV Box.
    You may only view thumbnails in this gallery. This gallery has 2 photos.

    Leave a comment:


  • P.X
    replied
    Originally posted by trebor View Post
    WARNING: There's is a possible bad batch of M8S Pro+ boxes which are experiencing regular freezing and crashes. We've narrowed the source of the problem down to a Samsung eMMC 5.1 chipset (KLMAG1JENB - B041), batches SEC 701 to 713, and these usually shipped from the factory with version 20170829.121614.V0321 of the OEM firmware. If you have one of these, it's highly recommended that you not flash any ROM (custom or OEM), as the prolonged block writes seem to result in serious data corruption.

    By request this was posted.
    Thanks -

    Leave a comment:

Working...
X