Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Mini M8S II (S905X) bricked - Internal Memory 0Mb - Won't flash

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

    Mini M8S II (S905X) bricked - Internal Memory 0Mb - Won't flash

    Hello everyone,

    I have a situation that has around 3 months now, and I can't fix it even after reading every piece of information I could grab on this forum and google.

    I'm usually the guy that prefers to play safe and not flash any kind of Android device to avoid this kind of headaches, but out of the blue, my box wouldn't boot past the logo. It's a Mini M8S II (S905X). I contacted the support at Gearbest (where I bought it) and they said it could not be fixed and refunded half the money. So no luck there.

    After 3 months of research and testing and failing to unbrick this box, here are the conclusions I took:

    - When I try to flash any firmware with USB Burning Tool it recognizes easily, but always stops at 7% (U-Boot/Send Command Error or something like that). Tried 2 cables, 2,0 and 3.0 USB ports, and different versions of USB Burning Tool (had time to try many combinations)
    - When I try to flash any firmware with SD Card, it shows the cute and lovely android but ends up with a red cross on the end. (tried all kinds of combinations with the erasing flash option, all types of firmwares I could find for this box, etc)
    - When I try to access the recovery without SD Card using the toothpick, nothing happens.
    - I tried the "sd_MINIM8SII_rv102" extracted to the sd card, nothing happened.

    After some deeper research, I tried extracting the "update.zip" from "sd_MINIM8SII_rv102" to sd card and replacing the recovery.img with the one from TWRP for S905X v3.0.2. It boots successfully to TWRP asking if I want to keep the system read-only. (at this point I saw the light at the end of the tunnel) Tried right away to flash a firmware from it, failing with messages saying the are no mounting points for /data and no /system partition and what not. Then I noticed the internal memory says 0Mb, in the recovery.

    I've also seen stuff like dropping a u-boot.bin (tried botfap's u-boot.bin.sd.bin) and stopping u-boot to access u-boot shell. From there you can flash the recovery.img and dtb.img and stuff like that. Can't find much information on that and didn't had much luck with it either.

    What am I missing? what can I do? I'm up for anything other than using this Box as a tall beer coaster.
Working...
X