Mecool m8s pro+ not working on arrival

[wackybruce]

Hi freaktab friends!
I just recieved my first tv box today and I can't seem to get it to work. It's the MECOOL M8S Pro+ S905X 2G 16G DDR3 Model from Gearbest.

Plugged in the HDMI and power adaptor and switched everything on but I dont get anything on screen at all tried it with both my monitor and TV. The first thing I thought was using the remote, but no response from the screen or box itself which at all times shows a constant red light and a smaller purplish blue light to the right of it as shown in the photo.

Tried using another HDMI cable and different power adaptor but got no result.
Tried entering recovery but can't get there holding the menu on remote while plugging power and shorting inside the mobo as shown in other posts but nothing, no lights changed nothing happened.
Tried to get the device recognised by my PC with a male usb cable it doesn't show up at all as a device or within USB burning tool. tried other usb ports on my pc but nothing.

Just dissapointed really.

[wackybruce]

After trying several methods in trying to unbrick the mecool m8s pro+ I believe I have exhausted the most common options if not all. And I wanted to put the details here in order, incase anyone else experiences the same issues.
Board marked M8S PRO+_V1.0
emmc: samsung 628
KLMAG2GEAC -B031
ram: Mira P3P4GF3BLF
wifi: Scl S9082C

Lights shown are red and blue when powered on. no display or significant heat from anywhere to suggest it is working with faulty graphics.
Alternate HDMI or power adaptor doesn't work.
Holding 1 or menu or repeat pressing on remote when powering doesn't work.
No obvious damage anywhere on the pcb.
Doesn't have a reset switch and shorting the reset solder location when powering on doesn't work in bringing up recovery/display.

Using USB burning tool with male to male usb cable to pc I can get it recognised by shorting the nand flash pins on the back of the pcb but unable to get past 4% with the following errors constant:
[Inf]--Run at address 0xd9000000
[Err]--generatedAddSum:0x cc282e4;srcAddSum:0x9df075c4;runResult:0x e6;paraMagic:0x7856efab
[Inf]--ReadCheckPara failed
[Inf]--m_iFileIndex:0
[Err]--[0x11000902]Unknown

Tried with every version of the stock image.img (V0321,V0619,V0928) file but always these errors and fail at 4% not sure what the error is reffering to.

When having an sd card in with burn card maker image shorting nand doesn't get recognised by burning tool. With boot card maker image.zip and boot,recovery files it does get recognised.
There are several nand pins that allow usb burning tool to get recognised and some pins by itself.
Shorting the 2 reset holes with the closest led pin/solder resets the led light back to blue but has no effect on anything else.
I had 2 male cables so shortened one but no success.

The burning tool error is the biggest clue I have to figuring out the problem but if I had to guess it would be emmc or ram related (read para failed)

I probably just got really unlucky to get a doa on my first order so went and ordered an m8s pro l and fingers crossed I get a working device this time.

[yarahu]

Maybe this information help you, if not, sorry for garbage post:

**ID: USB_BURNNING_TOOL 2.0.8 or newest [SOLVED]**
Description: parse burning image fail
Solution: Unpack .img like zip!!!

**ID: ReadCheckPara failed with [0x11000902]Unknown [SOLVED]**
Description: Installation process stuck on 4% with message in log: ReadCheckPara failed; [0x11000902]Unknown; I didn't change temp in app.
Solution: Check motherboard by android system info. Compare model board with img file(some people add it to img name). This error mean that you img is not for your board(board is more important then device model). Manufacter build the same model with different motherboard. Problem isn't related with cabel or usb_burnning_tool verison.
My motheboard p212_9377; device MXQ PRO+ 4K; CPU S905x. I used img for tx7 from https://mega.nz/#!8VxwyDLK!swvvVOEe-...DBpJH64ky1f-Po. KODI, Netflix, eth, remote controller work
Person help resolved problem: pawel1234q from forum.android.com.pl (THX A LOT)