[help me] Rom M8S CS_812M8_V1.3 2015/09/21

[nguyenminhchi]

help me brick M8S CS_812M8_V1.3 2015/09/21

not connect usb buring tool

[iRickUK]

Hey guys, I have the same bricked device. All attempts to install replacement firmware have failed. I never get past 4%: formatting before it errors out. Any ideas? I can connect the M8s via the 2nd USB port but not the first even if I short the pins on the board.

[iRickUK]

[muncheno]

Hey guys, I have the same bricked device. All attempts to install replacement firmware have failed. I never get past 4%: formatting before it errors out. Any ideas? I can connect the M8s via the 2nd USB port but not the first even if I short the pins on the board.

I have the same M8S too with PCB label CS_812M8_V1.3 dated 20150921.

I managed to upgrade to become M8S+ running 5.1.1 with wifi working but AC is slow and ethernet not working.

What I did was:-

1) Using USB Burning tools, USB male to male cable and a tooth pick.

2) Have USB Burning tools running and import the required ROM.

3)holding reset button while connecting PC with the USB cable. There are 2 USB ports here.
Connect to the one next to HDMI port.

4) once detected start flashing and continue holding the reset button until it pass 4%. Normally it reboot once before reaching 3%.
if you fail here, maybe you didn't get the correct ROM.

Currently, I'm still try to determine which is the correct ROM to used and still testing.
The ROM to unbrick now which I still experimenting as follows,

5) KII-LMY47V-20160429.img this from Acemax KII.
https://mega.nz/#!04sVXJib!TgVPuZlDKgrPseXoxnOKh7xD-ZTj-bswaeOCNh7d67g

Flashing with Erase(Normal) & Erase Bootloader.
With this you can turn the led from red to blue. Problem after restart having boot loop at the boot logo.

6) Next I'm flashing with other ROM to try fixing the boot loop. The rom is M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package.rar .
The file is inside Post #2 you will see this link:- https://mega.nz/#F!IkQSgYAI!AUhqqesALCeH-7VPAOPaAw
If you fail to flash complete with file, then you step (5) again and this time step(6) untick the Erase bootloader, that you let you complete the flash.

To highlight again, the rom still not perfect. Wifi working on 2.4G and ethernet not working.
Will keep update here, if I got further progress.

Cheers.

[iRickUK]

Thanks I'll try that tomorrow, I previously did all you did except hold the reset with a toothpick up to 4%. It connected immediately in the burning tool when I plugged in the male to male in the 2nd USB slot. Maybe it's the lack of holding the reset is the cause not letting it format. I'll update my progress tomorrow

[JustMe]

can you post log of the error from usb burning tool if it getting t 4% then it sound like incorrect firmware also try using Amlogic Tool setup v2.0.5.15 build9 2.0.7 is buggy

[muncheno]

Another things I found tonight, you can also skip step (5).
This is directly flash M8S(n200c).. but also using erase option "Force erase". Normal erase will work too, but I found it depending what ROM that you flash before. Thus it must effective to use force erase options.

For most ROM I tested, it will either fail before 3% or after 94-96℅.

Purely my hunt here, if you fail before 3% could wrong rom, which the ROM intended for NAND memory instead of EMMC. Then after 94%, could be wrong bootloader, I noticed last item in the flashing is the boatloader.

Make it simple to understand, if you found a ROM fail after 94%, you try flash with M8S(n200C).. ROM then flash again the intended ROM with untick on erase bootloader and erase option, the ROM will like to boot up also.
I did manage some other ROM running with this approach.

So far I found only a custom ROM that get LAN and wi-fi working perfectly is from here

https://forums.matricom.net/viewforum.php?f=54&sid=9f1bcdc43d2fc72c90ce26612861aa43

After step(6) and flashing with twrp , any firmware 2.1 and above will boot up. However it will slowly hang and restart make device brick. I'm hoping there have never ROM coming out soon.

Just my 2-cents here, still experimenting to get it running perfect.

[JustMe]

matricom would have to be one the worse firmware's just my opinon anyway

[iRickUK]

can you post log of the error from usb burning tool if it getting t 4% then it sound like incorrect firmware also try using Amlogic Tool setup v2.0.5.15 build9 2.0.7 is buggy

I have tried many ROMs for my M8s all failed with varying issues the best i got was Progress: 4%- Formatting as seen in my attached text log, Initially I tried to get Android 5+ installed so i could run Kodi 17 but that bricked it, at this point I'm happy just getting it back to stock so its at least usable again on Kodi 16.1. Any advice given would be gladly received

Thanks!

[10:05:59 597][Global][Inf]--Scan USB host controller complete
[10:05:59 598][Global][Inf]--Update data center with HubMap
[10:05:59 598][Global][Inf]--Update hub3 device data
[10:05:59 598][Global][Inf]--Update HUB3-1 \\?\usb#vid_1b8e&pid_c003#5&20bc27f7&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
[10:05:59 598][HUB3-1][Inf]--Update device path
[10:05:59 598][Global][Inf]--Update HUB3-2
[10:05:59 598][HUB3-2][Inf]--Update device path
[10:05:59 598][Global][Inf]--Update HUB3-3
[10:05:59 598][HUB3-3][Inf]--Update device path
[10:05:59 598][Global][Inf]--Update HUB3-4
[10:05:59 598][HUB3-4][Inf]--Update device path
[10:05:59 598][Global][Inf]--Update HUB3-5
[10:05:59 598][HUB3-5][Inf]--Update device path
[10:05:59 598][Global][Inf]--Update HUB3-6
[10:05:59 598][HUB3-6][Inf]--Update device path
[10:05:59 598][Global][Inf]--Update HUB3-7
[10:05:59 598][HUB3-7][Inf]--Update device path
[10:05:59 598][Global][Inf]--Update HUB3-8
[10:05:59 598][HUB3-8][Inf]--Update device path
[10:05:59 627][HUB3-1][Inf]--------------ERASE BOOTLOADER------------
[10:05:59 629][HUB3-1][Inf]--0-7-0-16
[10:05:59 629][HUB3-1][Inf]--Identify status success
[10:05:59 629][HUB3-1][Inf]-- low_power
[10:05:59 634][HUB3-1][Inf]--Low power command success
[10:05:59 637][HUB3-1][Inf]--Read low power success
[10:05:59 638][HUB3-1][Inf]--bootloader_is_old
[10:05:59 638][HUB3-1][Inf]--Bootloader command success
[10:05:59 643][HUB3-1][Err]--failed: bootloader is new
[10:05:59 644][HUB3-1][Inf]--Bootloader is new
[10:05:59 644][HUB3-1][Inf]-------------Download DDR.USB-----------
[10:06:02 650][HUB3-1][Inf]--Close device handle 0x00000288
[10:06:02 701][HUB3-1][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&20bc27f7&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x0000079c
[10:06:02 759][HUB3-1][Inf]--0-7-0-16
[10:06:02 759][HUB3-1][Inf]--No need download
[10:06:02 759][HUB3-1][Inf]-------------Download UBOOT_COMP.USB-----------
[10:06:02 760][HUB3-1][Inf]--0-7-0-16
[10:06:02 760][HUB3-1][Inf]--No need download
[10:06:02 761][HUB3-1][Inf]-- low_power
[10:06:02 766][HUB3-1][Inf]--Send command success
[10:06:02 769][HUB3-1][Inf]--Read command status success
[10:06:02 769][HUB3-1][Inf]-------------ERASE FLASH-----------
[10:06:02 769][HUB3-1][Inf]--disk_initial 1
[10:06:02 770][HUB3-1][Inf]--Send command success
[10:06:17 031][HUB3-1][Err]--failed:[10:06:17 031][HUB3-1][Err]--Check command return failed
[10:06:17 126][HUB3-1][Err]--[0x30201004]UBOOT/Disk initialize/Send command/Error result
[10:06:17 126][HUB3-1][Inf]--Close device handle 0x0000079c
[10:06:22 834][Global][War]--User click stop button
[10:06:22 836][Global][Inf]--Enable burning 0

[JustMe]

you have ap6330 chipset your rom maybe incorrect, have you tried shorting pin ? or even flashing back to original working rom and untick boot loader flash

also my next question is is this mainly ott for kodi if so then just go straight to LibreELEC

the firmware you trying to flash is either AML8726 or bcm4335 chipset

I would need to back track since I'm on holidays for another week or so I would not be able to confirm till then

[muncheno]

I have tried many ROMs for my M8s all failed with varying issues the best i got was Progress: 4%- Formatting as seen in my attached text log, Initially I tried to get Android 5+ installed so i could run Kodi 17 but that bricked it, at this point I'm happy just getting it back to stock so its at least usable again on Kodi 16.1. Any advice given would be gladly received

Any update here?

I manage to get this aml-m8s + -5.1-20151022-mac.img to flash successful to flash with overwrite key (mac_ether.Ini) with intention to fix also ethernet.
The firmware will flash nicely and boot up without problem. Only that ethernet still not working.

So far ethernet will work if I flash matricom Q 2.1.1 firmware. However my box brick again once I power off or remote the power supply.