Check id MD5 of the original downloaded file (v1.2.3_img,zip) is ea64a0c7085710dfbc47e724eb000445 (as mine is, unluckily Zidoo forgot to post zip CRC) Will be good if Zidoo will confirm this CRC and better also contained img file CRC.
ea64a0c7085710dfbc47e724eb000445 is the md5 hash, have you tried to flash the box? Has anyone successed to flash it?
http://ota-cloudfront.zidoo.tv/X9S/image/v1.2.6/v1.2.6_img.zip The zip file MD5:c4437c6b3565c844b4e25aa1e3a4e402 The img file MD5:f0b3af3fbd846c403bf1365e6bd8451e
What is the difference between img.zip and OTA? Is one a full flash whilst the other is differential?
More or less, yes. But OTA may be installed starting from any prevoius FW release (if is not a specific version update), img erases all, and don't depends on presence of FW, usually is flashable also in "soft bricked" devices. Not perfectly accurate, but enough to understand a rough difference.
The IMG method only requires the Bootloader to be intact. The Bootloader is a very small and simple piece of Flash Rom code which only reads the IMG file as a straight memory image from SD-Card or USB-Stick. After loading/validating it, it will start running that image. The Bootloader is activated if the RESTORE button is detected as being pressed (using a pin) during the power-on boot. Using this process will implicitly erase the total player: OS, Data, APP's and Settings. A bootloader restore will work as long as that specific small piece of code is still intact. It does not require the player to have a working/bootable/stable OS. It does not even matter whether a picture is produced or not. So players which crashed and or corrupted the running OS can be fully recovered with it. Cross flashing (putting in an alien FW) with the FW of even the closest type of player (having the same or similar SOC) probably will have a slightly different bootloader and might brick your player. Never try this, always come across people who do with mostly a very nasty surprise at the end after doing so.
I have tried. "restore factory setting" doesn't sometimes fully clear/erase the settings by the user. After reboot, some of the user's settings are still there. So flashing does it.