11/20/2022 0 Comments Ch341 programmer software![]() Modification 2: Add a 1000uF 16V elco capacitor to the USB power line, positive side of capacitor goes to the plus pole, and negative side of capacitor goes to the minus pole of USB power line. Now we have 5V power for our 95xxx eeproms.ģ. Now solder a short piece of wire from 5V pin to pin number one on the socket. ![]() Modification 1: 95xxx eeproms are read/write by inserting them to the 25xxx labeled socket and thats where we need to cut the 3.3V trace on the backside on the PCB. Luckly on the programmer there is 5VDC pin which we will be use to get this power from.Ģ. But to write and read to automotive 95xxx series eeproms we need to supply 5VDC. For reading and writing to those eeproms, 3.3 V power is supplied from the programmer its self. This programmer supports two types of eeprom, 24xxx (I2C) and 25xxx(ISP) series, so on the ZIF socket there are labels which indicate where to insert which type of EEPROM. Buy a cheap CH341A eerpom from Ebay or Aliexpress. I used this programmer with success to read and write to 95128 EEPROM.ġ. I must say, this is not my solution, I am just sharing it with you. Make sure it opens properly and looks correct in any BIOS editing tools you are familiar with too, then you'll know it's OK.I hope this will help someone, like it did for me. Then repeat that a time or two and compare those two verified files, if they're always good files and match then probably OK. Open that file in hex editor and make sure it's not all FF"s. Verify after reading it should tell you chip and buffer or memory match, then that is possibly a good verified file (not always). If it verified good, then you hit save BIOS. ![]() Once you've done that, hit read and when it's done hit verify. Sometimes you might need to choose less than full ID, or different than ID too, like BIOS ends in FV sometimes BV works better, but you'll figure that out later if it comes to that. Hit detect and if it detects your chip by ID OK, then select that one. Then open software of your choosing to try first, I already try newest version first. Lost_N_BIOS Wrote:Then install driver in above package. If it is all FF's, that's verified invalid blank and you need to use another software version or CHIP ID and try again until you get verified and valid backup). Lost_N_BIOS Wrote:Run read, then verify, once it says "Chip/Buffer match" then that is verified, click save and then open that file in hex editor and make sure it's valid BIOS and not all FF's. The contents of the files is not the same but it is very similar. Lenovo G710 BIOS Whitelist Rem.Įxtracting coa and other info from bin f. ![]() Request to add Ivy Bridge-E support to E. Dell Vostro 200 v1.0.16 Experimental Unl. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |