Help with bios programmer (EZP2019+)

[jamaicaboy]

Re: Help with bios programmer (EZP2019+)

Hello I'm using the EZP2023, when I try to detect some chips the programmer shows me PLEASE MANUALLY SELECT THE CORRESPONDING TYPE BURN,. What does this mean?, and what should be the first thing to do whatever I come across this that message?. THANK YOU .

[ogre4273]

Re: Help with bios programmer (EZP2019+)

I dump two files of the same bios chip with different speed (3 mhz and 12 mhz) now why are there differences when i try to compare them using hxd? Does it matter or it will not affect the dump

[linh0983]

Re: Help with bios programmer (EZP2019+)

I have tried but without success

I want to read W25Q128FVPQ with EZP2019+ but canr read.

what can I use to read/write W25Q128FVPQ

This box can support all kinds of chips you can refer to .

http://www.xgecu.com/en/

[Bravetech]

Re: Help with bios programmer (EZP2019+)

Hello friends please I have problem with the new EZP 2023 programmer, after insering the chip into SOIC, when I read the bios is says chip empty. Anyone with the solutiaon

[samtron786]

Re: Help with bios programmer (EZP2019+)

NOT CONNECT
That's a driver problem.
Drivers are included with the software.
Go to Device Manager and look under USB
Install the driver for the EZP2019 programmer.
Problem solved.

Don't forget to deactivate the driver signature :-)

[aa10aa10]

Hi! Long story short - I wanted to remove supervisor password from BIOS (MX25L12873F chip). I have read BIOS using AFUWINGUI64 (8MB), edited and pressed write - AFU started erasing the chip and then it showed error. I didn't manage to write BIOS using AFU - not original, nor edited. Then I have rebooted - no post, only power light is on. I have disassembled notebook, connected EZP2010 programmer and read the chip (16MB) using EZP2011 v3.0 (chip was detected as MX25L12805D). I have replaced corrupted partly erased BIOS part from 16MB file to previously read 8MB BIOS. Still no post. EZP erases this chip, verification of erased chip passes, then EZP writes this chip and verification of written chip passes. I have afterwards read the chip and compared both files using VBinDiff - files are the same.

I have also tried another BIOS dumps found here from similar model - still no luck.

So the question is - I need another programmer for this chip? Could there be any problems with EZP taking into account that verification passes?