MeCool M8S Pro L (LB version) - Hung on Pairing Remote Screen

[Wanderer190]

@t23: I tried to find the correct TWRP for the box, not sure which one to use. Any help would be appreciated.

[t23]

See my previous post - hopefully a kind soul will help you with that bit. From then on i have a clue again.

[DrNicos]

There are 3 separate posts in this link (below) to forum post (page 16) that seem to be factory firmwares pulled from the LB version of the box.

By the way, I'm going off the topic of this thread, but since we're talking specifically about the LB hardware version, I'm having a strange problem with my new M8S (it's always been like this since I bought it 2 weeks ago):
1. If I power up the box with ethernet wire connected in the socket it won't connect.
2. I need to physically pull out the wire and re-insert it, and then the box becomes connected.
3. It stays connected until I power down. If I power down and on again, connection is lost, until I remove and re-insert the ethernet wire.

Anyone facing such a problem? Is it 100% faulty hardware, or it might be software/firmware/settings problems?
(by the way I tried this with many different ethernet wires)

[Wanderer190]

There are 3 separate posts in this link (below) to forum post (page 16) that seem to be factory firmwares pulled from the LB version of the box.

By the way, I'm going off the topic of this thread, but since we're talking specifically about the LB hardware version, I'm having a strange problem with my new M8S (it's always been like this since I bought it 2 weeks ago):
1. If I power up the box with ethernet wire connected in the socket it won't connect.
2. I need to physically pull out the wire and re-insert it, and then the box becomes connected.
3. It stays connected until I power down. If I power down and on again, connection is lost, until I remove and re-insert the ethernet wire.

Anyone facing such a problem? Is it 100% faulty hardware, or it might be software/firmware/settings problems?
(by the way I tried this with many different ethernet wires)

@DrNicos: I have already downloaded one of them. But no one seems to know which version of TWRP I am suppose to use on the box.

[t23]

@DrNicos: I have already downloaded one of them. But no one seems to know which version of TWRP I am suppose to use on the box.

I seriously don't know - flashed one of the Magendanz firmwares myself which came with it. But there's got to be a standalone q20x version you can install through the stock recovery.

[Wanderer190]

@t23: I finally found the actual image files for the LB version of the box and flashed the box via Burn Card Maker. They both had the same issue. It has to be a hardware failure. Now it is just a matter of seeing if I can get a replacemement/refund from vendor or if I just pi$$ed another $70 into China for nothing??

[t23]

If it was the backups pointed to above, you have to restore them with TWRP. Easy to check - if your download unpacks to seven or more files, it's a TWRP backup. Show me the link, please?

But if you figured out how to use Burn Card Maker, you can flash a Magendanz LQ image, then you get TWRP, and then you can do a restore of such backup. Burn Card Maker never worked for me, i spliced two USB cables together and used USB Burning Tool. Pin 1 to 1, 2 to 2 and so forth - cables from the same manufacturer are color coded the same way, but never hurts to double check with a multimeter.

And hey, you're lucky, paid $90 for one (that was, though, including 24 hour delivery across Europe), but at least it's working now except for a few quirks.

[Wanderer190]

If it was the backups pointed to above, you have to restore them with TWRP. Easy to check - if your download unpacks to seven or more files, it's a TWRP backup. Show me the link, please?

But if you figured out how to use Burn Card Maker, you can flash a Magendanz LQ image, then you get TWRP, and then you can do a restore of such backup. Burn Card Maker never worked for me, i spliced two USB cables together and used USB Burning Tool. Pin 1 to 1, 2 to 2 and so forth - cables from the same manufacturer are color coded the same way, but never hurts to double check with a multimeter.

And hey, you're lucky, paid $90 for one (that was, though, including 24 hour delivery across Europe), but at least it's working now except for a few quirks.

Links to the LB Image files on here:
1. M8S_PRO_L-NHG47L-20180316.143701.V0213.IMG - http://freaktab.org/a28c3f52268572bb
2. M8S_PRO_L-NHG47L-20180417.150752.V0213.IMG - http://freaktab.org/8e1ecd22568550f2

Burn Card Maker is simple. I use v2.0.2. Simply run it, use Burn Card Maker to burn the image to a SD card. Insert the SD card in the box, hold reset in (or short pins in this case) and plug in power. It does the rest.

[t23]

Assuming those are made from those backups posted here, then yeah, not much to do. If you know how to adb into it or have a terminal, one last thing you can try is this command:

dmesg | grep 4335

if it doesn't say "dhd_os_open_image" and "open success" twice in a row somewhere, it means it didn't bother to even try loading the firmware. And then i am really convinced you should get a replacement - and also out of ideas.

[supermal]

Links to the LB Image files on here:
1. M8S_PRO_L-NHG47L-20180316.143701.V0213.IMG - http://freaktab.org/a28c3f52268572bb
2. M8S_PRO_L-NHG47L-20180417.150752.V0213.IMG - http://freaktab.org/8e1ecd22568550f2

Burn Card Maker is simple. I use v2.0.2. Simply run it, use Burn Card Maker to burn the image to a SD card. Insert the SD card in the box, hold reset in (or short pins in this case) and plug in power. It does the rest.

Those images are not back up images for the LB version boxes they are full images for the box.use usb burning tool and you will get full stock firmware restored.i was the one who uploaded a twrp backup of my LB box to help people out.you don't need that now.just install one of those images from freaktab download forum.

[t23]

i was the one who uploaded a twrp backup of my LB box to help people out.

You saved my box. Thank you!

[Appys]

Damn same pinch, box doesn't show on scans and stuck on the screen after ota update and reset no bluetooth no WiFi no entry..

[rockinhc]

I have this same issue but it's not hung. I can connect a mouse/keyboard and move around. I can even use the remote to adjust the volume. Just can't bypass the screen.

[Wanderer190]

Here is what happened in my scenario: (SPOILER: my bad box has a bad wifi / bluetooth chip)

I found the correct version of TWRP for the box that worked for me (twrp.q20x-3.2.1-0_2.img). I renamed it to recovery.img and copied it over to a blank 32GB SD Micro. Placed it in my good box.

I then finagled and shaped a paper clip to short the pins on the box from the front vent holes (the 1st & 2nd slots on the right of the blue light), I found a picture of the board on here somewhere.

With a little patience I held the paper clip in place, you will feel the paper clip hitting the holes on the board if you are in the right spots, then I plugged in the power and booted it from the SD and used TWRP to do a full backup of the good box.

I then put the SD card in the bad box, booted it to the SD card, done a full restore. The box now boots right up and functions well, however it does NOT have bluetooth or WIFI. The original remote works, but the voice functions do NOT work. I bought a cheap voice remote ($15) off of Amazon that uses a USB dongle and it semi works (you have to activate the voice on-screen then use the dongle remote).

I will try to do a clean backup of the box after the Remote Pairing in the next day or two and then upload TWRP and the Backup files to Google drive or something so at least you can get the box functioning again. And if your hardware is good, everything should work correctly. You will have to manually pair your remote.

If your chip is bad, like mine, then you can at least still get some use out of the box. Mine went to a spare bedroom for grand kids and works great for kodi and such (wired network). I had a Microsoft 360 controller dongle and he even uses it to play game using a 360 controller.

Hope this helps

[Appys]

Like xda, this forum deserves a thank button for folks like yourself..