[ROM] Mecool M8S PRO+ Stock & Nano Nexus ROMs (Android 7.1)

[m4w]

Looks like mine is borked too. I can't get it to show in the burning tool.

Edit: I opened up the box and I have the v1.0 hardware revision.

Guest yelp! How do I short pins for Mask ROM mode? And what comes next? Is there a guide anywhere?

Seriously? What makes you think it might work on a Mi Box? In the title, I say it's for the Mecool M8S Pro+.

[ZeRoZeRoRaZ]

Guest will it work on Mi Box (MDZ-16-AB)?

[P.X]

#46.1
Magendanz commented
09-28-2017, 11:44
This would be the first case I've ever heard where flashing a ROM permanently damaged the hardware. Sure, you can corrupt your bootloader so that you can't flash anything else, but it's just writing code to the eMMC storage. What seems more likely is that some devices were built with a bad NAND batch that just didn't show issues until you did an extended block write.

Like you say probably faulty batch. My box had serious issues before the flash.

Would it be possible to make a version of the FW that works from USB or SD like people do with LibreElec (or so I gather) so that the eMMC is bypassed ?

Any other ideas welcomed ...
Pete

This would be the first case I've ever heard where flashing a ROM permanently damaged the hardware. Sure, you can corrupt your bootloader so that you can't flash anything else, but it's just writing code to the eMMC storage. What seems more likely is that some devices were built with a bad NAND batch that just didn't show issues until you did an extended block write.

[P.X]

WARNING

WARNING : FW 20170829.121614.V0321

New HW boxes arriving with this 2017.08.29 dated FW

Do NOT flash any earlier dated ROM if you have a box with 20170829.121614.V0321

As far as I can tell if you flash any earlier FW, Custom or OEM, onto the boxes with 20170829.121614.V0321 - Boxes with SEC and D/W hardware - The box will be in a state where it freezes rapidly after power-on and is useless.

An Update to the latest V0619 FW did not restore functionality to my box.

Until there is an extracted 20170829.121614.V0321 we do not know if these boxes will work again when restored to Original FW.

My box, HW-Date 17.08.11 SEC & D/W chips, had freezing problems from the start but it seems all those who flashed an earlier dated ROM have similarly borked boxes afterwards.

[DEcosse]

You might want to know that two weeks apart and the hardware is different. You can photo from other forum chain.
i guess we will have to not assume because the manufacturers or sales companies aren't exactly ISO certified.

Please read my posts carefully - I was actually the first to suggest there MIGHT be a hardware change (but I'm not convinced that the memory chips constitute that) - and what I was suggesting was simply that IF the hardware configuration WAS the same, then installing an older OEM ROM image SHOULD not be a problem.

[grimmie]

I have already updated to the Nexus ROM so the OEM firmware version is moot
However my order shipped from Geekbuying on 8/22 which clearly pre-dates 8/29 - and I had no OTA update that it found. I certainly did not execute an update.


If we assume for a moment that 8/29 is merely a later revision based on same hardware, there is no reason why you could not flash 08/15 version - it should not HAVE to be same you started with


You might still go ahead and try to flash in the OEM 8/15 ROM (as per the link) - if there is no hardware change, then it should install and you can see where you are from there.
If that won't take, then indeed something may have changed

You might want to know that two weeks apart and the hardware is different. You can photo from other forum chain.
i guess we will have to not assume because the manufacturers or sales companies aren't exactly ISO certified.

[gmikulski]

Hi!!
Thanks for this awesome ROM! I have one issue though:

• Recovery from sleep/standby seems to result in a full boot. This seems to be a bug in the underlying OEM firmware.

I am using dual boot with LibreElec starting from SD Card. Every time I click power off button on remote, box shuts down and then recovers with full boot. As a result I get "file system corruption detected" every time when LibreElec is booting. Need to wait 120 seconds and then repair runs, and LibreElec finally boots.

SD card is brand new, 16gb Sandisk Ultra Class 10... So I don't think it is card issue. Rather issue is caused by box not going to sleep mode well, filesystem gets corrupt.

Anybody encountered same issue? Can I avoid it somehow? The full boot is rather painful... Any chance to fix this?

[DEcosse]

I have already updated to the Nexus ROM so the OEM firmware version is moot
However my order shipped from Geekbuying on 8/22 which clearly pre-dates 8/29 - and I had no OTA update that it found. I certainly did not execute an update.

For that to work you will need the original OEM ROM. If like me, it's something that I dont have because the original oem rom version 20170829 is not available..

If we assume for a moment that 8/29 is merely a later revision based on same hardware, there is no reason why you could not flash 08/15 version - it should not HAVE to be same you started with


You might still go ahead and try to flash in the OEM 8/15 ROM (as per the link) - if there is no hardware change, then it should install and you can see where you are from there.
If that won't take, then indeed something may have changed

[grimmie]

I know that there was "no update available" for my box (i.e. it was not offering update to take it to the 20170829) - therefor I wonder if there has been a hardware change and that is why the OEM ROM is different (and why the custom ROM is not working?)

What's your box' current firmware version?

[DEcosse]

I know that there was "no update available" for my box (i.e. it was not offering update to take it to the 20170829) - therefor I wonder if there has been a hardware change and that is why the OEM ROM is different (and why the custom ROM is not working?)

[grimmie]

FYI - See this response from Guest - http://freaktab.com/forum/tv-player-...563#post662563

Maybe restore back to OEM and try again

For that to work you will need the original OEM ROM. If like me, it's something that I dont have because the original oem rom version 20170829 is not available..

[grimmie]

I have the same problems as many others had. After installing the OTA package, my device got stuck and it won't do anything. I have ordered a male to male USB cable so I will be able to try the USB burn method. Just a question, should the sd option be also a good choice for me? And, where's the reset button in our device? Because if I use a toothpick I can't find any button, meaning I can even put it into the device. Thanks!

I used male to male USB cable from the start. And the device just hang after update. Dont think the problem is the way you update but what was updated.

[grimmie]

Doesn't work on my box. All with the same result.. hung.