EVERYONE UPDATE TO V4 FIRMWARE IF YOU CAN!! NEW AMA MODE!!!!

[SlvrDragon50]

So I'm having issues now (very minor). My LG 34" monitor flashes occasionally and videos in my FB feed start out with the colors all weird (blacked out silhouettes) which take a few seconds to return to normal.

Is this due to poor CRU settings or my GPU just struggling? I only have a 7950 so I wouldn't be all to surprised if it was the latter.

[Hell-storm]

I have trouble updating the my benq 2720z and are getting these error messages (see attachment error msg)

I 've tried using different laptops
And there is no light and function to touch buttons on side of the screen.

[Falkentyne]

Question:
In your gif you posted, you're writing the backup.bin file. Were you trying to restore the backup? If so, why? Where is the command above that?

Try unplugging the monitor from the wall for 15 minutes.
Then plug it back in and flash the backup file you created. Since the backup file is already there, you wont need any of those rename and merge commands.

That should flash successfully.
Once that's done, then redo all the steps.

Also make 100% sure that you didn't mess up or make a typo in any of the commands.
What I found helpful was, saving that full command list I wrote back (several pages ago) into a text file.
Linux can see and open the text file locally, so you can have it open.

Then just use the right mouse button to copy/paste/highlight the commands and paste them directly into the command line editor, only substituting the bus ID that needs to be changed for your hardware.

[Hell-storm]

Tried to updating through DVI instead of VGA.
And it still failed .
I am not sure if the backup.bin I have from the before the screen bricked is working.
Do i have to update first with backup.bin and then a newer firmware if the screen is bricked ?
Here is a copy of my terminal commands.

ubuntu@ubuntu:~/flashrom$
ubuntu@ubuntu:~/flashrom$ sudo modprobe i2c-dev
ubuntu@ubuntu:~/flashrom$ sudo i2cdetect -l
i2c-0 i2c i915 gmbus ssc I2C adapter
i2c-1 i2c i915 gmbus vga I2C adapter
i2c-2 i2c i915 gmbus panel I2C adapter
i2c-3 i2c i915 gmbus dpc I2C adapter
i2c-4 i2c i915 gmbus dpb I2C adapter
i2c-5 i2c i915 gmbus dpd I2C adapter
i2c-6 i2c SDVO DDC proxy I2C adapter
ubuntu@ubuntu:~/flashrom$ sudo i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
ubuntu@ubuntu:~/flashrom$ sudo i2cdetect 6
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-6.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- 38 -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- 49 -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- 59 -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
ubuntu@ubuntu:~/flashrom$ sudo i2cdump -r 0-127 6 0x50
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-6, address 0x50, mode byte
Probe range limited to 0x00-0x7f.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 ff ff ff ff ff ff 00 09 d1 29 7f 45 54 00 00 ........??)?ET..
10: 10 18 01 03 80 3c 22 78 2e 14 d1 a5 58 52 a2 26 ?????<"x.???XR?&
20: 0c 50 54 a5 6b 80 d1 c0 45 7c 61 7c 81 80 81 bc ?PT?k???E|a|????
30: 95 3c 31 7c 01 01 02 3a 80 18 71 38 2d 40 58 2c ?<1|???:??q8-@X,
40: 45 00 55 50 21 00 00 1e 00 00 00 ff 00 41 34 45 E.UP!..?.....A4E
50: 30 30 39 39 39 53 4c 30 0a 20 00 00 00 fd 00 38 00999SL0? ...?.8
60: 90 1e a0 21 00 0a 20 20 20 20 20 20 00 00 00 fc ???!.? ...?
70: 00 42 65 6e 51 20 58 4c 32 37 32 30 5a 0a 01 fa .BenQ XL2720Z???
ubuntu@ubuntu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-6:49
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-6 and address 0x49.
Info: WILL reset the device at the end.
Found Macronix flash chip "MX25L1605" (2048 kB, SPI) on mstarddc_spi.
Found Macronix flash chip "MX25L1605A/MX25L1606E" (2048 kB, SPI) on mstarddc_spi.
Found Macronix flash chip "MX25L1605D/MX25L1608D/MX25L1673E" (2048 kB, SPI) on mstarddc_spi.
Multiple flash chip definitions match the detected chip(s): "MX25L1605", "MX25L1605A/MX25L1606E", "MX25L1605D/MX25L1608D/MX25L1673E"
Please specify which chip definition to use with the -c <chipname> option.
ubuntu@ubuntu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-1:49 -c "MX25L1605A/MX25L1606E" -r backup.bin
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-1 and address 0x49.
Info: WILL reset the device at the end.
Error enabling ISP mode: errno 6 & 6.
Please check that device (/dev/i2c-1) and address (0x49) are correct.
Error: Programmer initialization failed.
ubuntu@ubuntu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-6:49 -c "MX25L1605A/MX25L1606E" -r backup.bin
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-6 and address 0x49.
Info: WILL reset the device at the end.
Found Macronix flash chip "MX25L1605A/MX25L1606E" (2048 kB, SPI) on mstarddc_spi.
Reading flash... Error sending write command: errno 6.
Read operation failed!
FAILED.
Info: Reset command was not sent. Either the noreset=1 option was used, or an error occured.
ubuntu@ubuntu:~/flashrom$ tr '\000' '\377' < /dev/zero | dd of=firmware.bin bs=1k count=2k
2048+0 records in
2048+0 records out
2097152 bytes (2.1 MB) copied, 0.0142798 s, 147 MB/s
ubuntu@ubuntu:~/flashrom$ dd if=XL2720Z_V005.BIN of=firmware.bin conv=notrunc1664+0 records in
1664+0 records out
851968 bytes (852 kB) copied, 0.00591695 s, 144 MB/s
ubuntu@ubuntu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-6:49 -c "MX25L1605A/MX25L1606E" -w firmware.bin
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-6 and address 0x49.
Info: WILL reset the device at the end.
Found Macronix flash chip "MX25L1605A/MX25L1606E" (2048 kB, SPI) on mstarddc_spi.
Reading old flash chip contents... Error sending write command: errno 6.
FAILED.
Info: Reset command was not sent. Either the noreset=1 option was used, or an error occured.
ubuntu@ubuntu:~/flashrom$

Is there a link to 2720z backup.bin i can use to update my screen.

[Falkentyne]

How do I upload my backup file?
I flashed to V5 but I have a v4 backup 2 mb already available.

I think your problem originally was you used an incorrect bus when trying the first flashrom command.
that error message was mentioned way back as being some strange undocumented error/unhandled exception, including the mis-spellings. You tried to backup on bus 1 originally, then switched to bus 6. This may have caused any sort of problem.

*edit* posted here. unrar it first then try.
it's 2 MB And already merged with the v4 832k firmware so don't use the merge commands.
Just flash it right away with the -w command.
Remember your bus is 6, not 1.

[Hell-storm]

I 've tried updateing but are getting these error codes (se buttom of the post) .
I think i must buy a MSTAR to make this work.
Can you even unbrick the pc screen with a MSTAR?
i will try with older computer and then possibly buy a MSTAR if it doest work.

hans@ubutu:~/flashrom$ sudo modprobe i2c-dev
hans@ubutu:~/flashrom$ sudo i2cdetect -l
i2c-0 i2c i915 gmbus ssc I2C adapter
i2c-1 i2c i915 gmbus vga I2C adapter
i2c-2 i2c i915 gmbus panel I2C adapter
i2c-3 i2c i915 gmbus dpc I2C adapter
i2c-4 i2c i915 gmbus dpb I2C adapter
i2c-5 i2c i915 gmbus dpd I2C adapter
hans@ubutu:~/flashrom$ sudo i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- 49 -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- 59 -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
hans@ubutu:~/flashrom$ sudo i2cdump -r 0-127 1 0x50
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1, address 0x50, mode byte
Probe range limited to 0x00-0x7f.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 ff ff ff ff ff ff 00 09 d1 28 7f 45 54 00 00 ........??(?ET..
10: 10 18 01 03 0e 3c 22 78 2e 14 d1 a5 58 52 a2 26 ?????<"x.???XR?&
20: 0c 50 54 a5 6b 80 d1 c0 45 7c 61 7c 81 80 81 bc ?PT?k???E|a|????
30: 95 3c 31 7c 01 01 02 3a 80 18 71 38 2d 40 58 2c ?<1|???:??q8-@X,
40: 45 00 55 50 21 00 00 1e 00 00 00 ff 00 41 34 45 E.UP!..?.....A4E
50: 30 30 39 39 39 53 4c 30 0a 20 00 00 00 fd 00 18 00999SL0? ...?.?
60: 78 0f 87 15 00 0a 20 20 20 20 20 20 00 00 00 fc x???.? ...?
70: 00 42 65 6e 51 20 58 4c 32 37 32 30 5a 0a 00 da .BenQ XL2720Z?.?
hans@ubutu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-1:49
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-1 and address 0x49.
Info: WILL reset the device at the end.
Found Macronix flash chip "MX25L1605" (2048 kB, SPI) on mstarddc_spi.
Found Macronix flash chip "MX25L1605A/MX25L1606E" (2048 kB, SPI) on mstarddc_spi.
Found Macronix flash chip "MX25L1605D/MX25L1608D/MX25L1673E" (2048 kB, SPI) on mstarddc_spi.
Multiple flash chip definitions match the detected chip(s): "MX25L1605", "MX25L1605A/MX25L1606E", "MX25L1605D/MX25L1608D/MX25L1673E"
Please specify which chip definition to use with the -c <chipname> option.
hans@ubutu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-1:49 -c "MX25L1605A/MX25L1606E" -w backup.bin
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-1 and address 0x49.
Info: WILL reset the device at the end.
Found Macronix flash chip "MX25L1605A/MX25L1606E" (2048 kB, SPI) on mstarddc_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Error sending write command: errno 6.
spi_nbyte_program failed during command execution at address 0x0
Reading current flash chip contents... done. Looking for another erase function.
Error sending write command: errno 6.
spi_nbyte_program failed during command execution at address 0x0
Reading current flash chip contents... done. Looking for another erase function.
Error sending write command: errno 6.
spi_nbyte_program failed during command execution at address 0x0
Reading current flash chip contents... done. Looking for another erase function.
Error sending write command: errno 6.
spi_nbyte_program failed during command execution at address 0x0
Reading current flash chip contents... done. Looking for another erase function.
Error sending write command: errno 6.
spi_nbyte_program failed during command execution at address 0x0
Looking for another erase function.
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Good, writing to the flash chip apparently didn't do anything.
Please check the connections (especially those to write protection pins) between
the programmer and the flash chip. If you think the error is caused by flashrom
please report this on IRC at chat.freenode.net (channel #flashrom) or
mail [email protected], thanks!
Info: Reset command was not sent. Either the noreset=1 option was used, or an error occured.

[Falkentyne]

A Mstar unit should always work. I actually ordered one so I don't have to deal with 10 minute flashes anymore.

It also can flash within seconds, instead of taking 10-15 minutes.
Hell you can even use it to cross flash other firmwares if the unit accepts the flash type (one of the mstar units can flash realtek units).

If I may ask, on all the computers you tried flashing on, are you using a "UEFI" Bios or a "traditional" Bios? that includes the laptop.

[Hell-storm]

Just received my mstar unit and when I followed the instructions on blurbuster site but now i am getting an error message (program file not ready !!!) 2 times and then finally (cant find device type !!!)
Some advice?

[Falkentyne]

Program file not ready means that you didn't load the firmware into the mstar unit. "Program file" is the file name of the firmware you will flash.

Cant find device type--Are you using your Mstar unit through DVI or VGA?
If you are using it through DVI, you may need to enable DVI HPD (hot plug detect) in the service menu.

http://forums.blurbusters.com/viewtopic.php?f=2&t=2467

After you click "read" and select the firmware, you won't get the program file not ready error ever again, since it remembers the last file you loaded into it.

[Hell-storm]

I am updateing with vga and my 2720z is bricked non functioning because of a failed firmware update through linux.
But i can still se the screen is alive because i can find the screen through linux commands you use to update it, but it fail updating it.