I believe you still don't get my point. Changing resolution or video output is essentially just overwriting a few KBs at the beginning of the SD card as you already outlined in https://github.com/BPI-SINOVOIP/BPI-M2-Configuration
You force users (that power their board using the USB OTG port and suffer from being able to use half of the USB ports since they don't know better and search for script.bin since they don't know better) to download stuff from github and do a risky dd operation themselves? While there are already images based on kernel 4.x in the wild where everything works totally different?
Why don't you ship a small self-containing tool that
a) checks boundary conditions (which u-boot version and kernel is the user in question running? Is this a sun6i board or does someone try to trash his M1/M1+/M3 installation?)
b) does the right thing (overwriting SD card blocks when U-Boot 2011 and kernel 3.3 is used and otherwise adjusting the .dtb file)
With this approach you would also help users to use GPIO pins and GBit Ethernet with an older OS image and don't want to start over again with a totally fresh image.
Whether script.bin works or not (and therefore exists or not) is not a question of the board but of the software used. And SinoVoip uses a totally outdated U-Boot version for their kernel 3.3 based OS images so there simply is no script.bin that you as the user could easily adopt to your needs using the sunxi tools bin2fex/fex2bin.