Yes, check the Linux thread.
Whitestar dumped XL2411z V4 and it's available here.http://www.mediafire.com/download/m707c ... backup.bin
This backup is 2 mb, so it may not need the 'merge' commands that extend the raw files (the raw files were the 832 mb ones) into 2 mb ones.
So you can probably omit these two steps
1) tr '\000' '\377' < /dev/zero | dd of=firmware.bin bs=1k count=2k
2) dd if=XL2411Z_V2_20131209_8B72.BIN of=firmware.bin conv=notrunc
But you need those two steps for the 832k files (the firmware name above was based on flashing the original V2 btw)
Might want to save it because these links are the only known places they have been posted to.
I'll repost the instructions again.
First grab a USB flash drive. 8 GB+ works best, though I did use an empty 2 GB one.
Get the ISO for Linux (Ubuntu) http://releases.ubuntu.com/14.04/
I used the i386 one for my core i7.
Download the easy to use USB installer here:
Install it then boot to the flash drive and run the try Ubuntu mode.
When it finishes loading, open a terminal (Ctrl + Alt + T);
type "sudo gedit /etc/apt/sources.list" without the quotes to bring up the editor.
At the end of the second line, add "Universe Multiverse" so the line looks exactly iike this:
trusty main restricted universe multiverse"
Save and exit the sources.list file.
Then type "sudo apt-get update"
That should download some updates.
sudo apt-get install i2c-tools subversion libpci-dev
That should update and install some package lists.
You MIGHT also need this command too.
sudo apt-get install libusb-dev
If everything installs correctly, great.
But now things get tricky.
Using the instructions on this website, you need to find and backup the V4 firmware. The hard part is actually finding the i2c bus where it's located.
Type these commands: Remove any quotes I put, though, including the quotes in the wget command (trying to bypass link creation).
"svn co svn://flashrom.org/flashrom/trunk@1846
wget -O- "http://boeglin.org/static/benq/0001-Add-programmer-for-the-MSTAR-I2C-ISP-protocol.patch | patch -p1" (<---the | is the shifted \ key, aka the "Pipe" symbol). On this website, that link shows up truncated with "...." unless you mouse over it. The full link without truncation is on the main site: "http://boeglin.org/blog/index.php?entry=Flashing-a-BenQ-Z-series-for-free(dom)"
Remove the quote before http and after -p1.
make -j (<-this should make the flashrom patcher with the data for the mstar scaler)
sudo modprobe i2c-dev
sudo i2cdetect -l <--this lists all i2c buses
sudo i2cdetect 1 <---this lists al i2c buses on bus 1.
sudo i2cdump -r 0-127 1 0x50 <--- get EDID (0x50) from bus 1. You are looking for an EDID dump that shows the monitor name in it. You may have to change the 1 to a 0 ( 0 0x50 insteada of 1 0x50), or you may have to change 0x50 to 0x49 (probably not, though; most video hardware will always be on 0x50). Once you find the dump that says "XL2411Z" then you're good to go. In some cases your monitor may be on bus 0, thus the change from a 1 to a 0. On my R9 290x video card, on the DVI port, this was bus 5. So the command I had to use was "sudo i2cdump -r 0-127 5 0x50"
If you are using a laptop through VGA, you SHOULD be able to find the monitor i2c identifier name easily. If you are using a desktop through DVI and flashing through the desktop and you can not find the monitor bus or get random data where the monitor 'should' be located (or in the rare case that the laptop can't see it through VGA, reboot the host computer back to windows and install the monitor driver from the DVD (device manager or displays in control panel); this has been confirmed to have helped people who kept getting "Unknown" data on the i2c bus. (0x50 buses 0-4 usually). Not sure why this works; maybe Linux has access to installed inf data.
sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-1:49 <----# identify flash chip, on bus 1 (/dev/i2c-1) at address 0x49. Change the 1 to a 0 if you are on bus 0. My r9 290x dvi port was bus 5. Laptop VGA port was bus 0.
(dump current firmware)
sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-1:49 -c "MX25L1605A/MX25L1606E" -r backup.bin <--again change the 1 to a 0 if you are on bus 0. My r9 290x dvi port was bus 5. Laptop VGA port was bus 0.
This should take about 5 minutes to dump. Once that's done, copy backup.bin to a folder on the local hard drive (NOT the USB drive) so you can can upload it somewhere. The dumped file should be 2 mb in size. We can easily verify if you dumped the right thing by a hex editor.
Copy the EXTRACTED Version 4 firmware into the flashrom folder. If you renamed it in windows (I suggest this), copy the renamed file. I suggest renaming XL2411Z's V4 (if you downloaded whitestar's backup.bin dump) to XL2411Z_V4.BIN, XL2420Z to XL2420Z_V4.BIN and the XL2720Z file to XL2720Z_V4.BIN
DO NOT RENAME IT TO FIRMWARE.BIN !!!!!
# extend firmware to 2MB, to match the flash chip size
(this step is important; the flash chip is 2 MB, but the raw firmware is 800k'ish. In order to flash with this flashrom patcher (the MSTAR ISP unit does not have this limitation), the other 1.2 MB must be filled with "empty/dummy" bytes to make the file 2 MB in total size. This is a limitation of flashrom itself).
tr '\000' '\377' < /dev/zero | dd of=firmware.bin bs=1k count=2k
dd if=XL2411Z_V2_20131209_8B72.BIN of=firmware.bin conv=notrunc (# < important !--REPLACE XL2411Z_V2_20131209_8B72.BIN with your firmware you are flashing!! Example: XL2411Z_V4.BIN or XL2420Z_V4.BIN or XL2720Z_V4.bin (as I suggested above).
(What this did was, it created a DUMMY empty 2 MB file called firmware.bin.
Then it MERGED the V2 (for this example only, in your case it will be the V4 file) with the 2 MB dummy file, a new 2 MB V4 file, that will be called firmware.bin
# write firmware
sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-1:49 -c "MX25L1605A/MX25L1606E" -w firmware.bin
(this will take between 5-20 minutes).
*** IF FOR SOME REASON the flash fails halfway through with some sort of strange error about being unable to do something, and the monitor seems to be 'bricked', it's not really bricked. The DDC/CI bus is bricked, but the i2c bus is still available. If the flash fails partway through, it's probably due to the computer you are using preventing the flasher from running cleanly (For some reason certain computers can confuse or break the flasher). Unplug the monitor for 10 minutes, plug it into a different computer IN STANDBY MODE (don't power it on), preferably into a laptop with a VGA port, and try again. Everyone who has had flashes fail from incompatible dvi ports or laptops has been able to reflash on a more compatible computer successfully. One user even had the firmware update fail on his first computer, was able to reflash the backup file, then flashed the new firmware on a different computer**. People have had success with DVI ports on the main PC, but that's at your own risk.