Zitat von Lost_N_BIOS im Beitrag #30

---

@cemara - Great you could find a programmer locally. Did you get cables? you need either SOIC8 Test clip with cables, or SPI Cables for your BIOS since it's not socketed.

That is not same MD5 checksum as file I uploaded, so something must have happened to it during the VPN download possibly?
I re-downloaded from the link I gave you again just now to confirm the MD5 from file I had in storage that I gave you previously, it's a match


MD5 = 9d3303cf4a9d0b6d04f126e41c40249d

Even though MD5 does not match, you did remove the jumper after flashing now correct? I assume this wont help, since MD5 does not match who knows how bad the file is you flashed in? Very sorry this happened, but looks like it's due to how you had to download.
Upload that file you have and I will check it, maybe I can find what the issue is, but you wont be able to fix it without a programmer, unless you can boot to DOS?

If you have not tried yet, put jumper back on and see if you can boot to DOS or BIOS like that, this will disable the ME region if ME region is what got messed up during the flash you may be able to reflash again.
If you do get lucky and that gets it started again, redownload the file and make sure you get that MD5 above before you flash it. And if needed, please give me a free file host other than google you want the file uploaded to and I can re-upload for you.

---

Yes, interesting! So now I go to the site you linked, and get same MD5 from there too, definitely something to do with uploading a file to their site?

Very sorry this happened, it could either be a bad flash generally, or something wrong with the method I modified the BIOS (It can be done a few ways).
Once you have your programmer, do not write anything until you have reached goal #1 >> first and only goal until you get a valid verified backup is that, do not try to recover the board until you have a verified backup (read, verify then save) and then open that BIOS in hex editor and make sure it's not all zero's or FF's
Once you have a good backup, then you can try to recover (erase, blank check, then open file and write/verify) The BIOS downloads are .bin/rom file, so you can use that, but you'll later have to correct BIOS using your backup from above, to put back LAN MAC ID, serial, UUID etc.

Zitat von Lost_N_BIOS im Beitrag #30

---

@cemara - Great you could find a programmer locally. Did you get cables? you need either SOIC8 Test clip with cables, or SPI Cables for your BIOS since it's not socketed.

That is not same MD5 checksum as file I uploaded, so something must have happened to it during the VPN download possibly?
I re-downloaded from the link I gave you again just now to confirm the MD5 from file I had in storage that I gave you previously, it's a match


MD5 = 9d3303cf4a9d0b6d04f126e41c40249d

Even though MD5 does not match, you did remove the jumper after flashing now correct? I assume this wont help, since MD5 does not match who knows how bad the file is you flashed in? Very sorry this happened, but looks like it's due to how you had to download.
Upload that file you have and I will check it, maybe I can find what the issue is, but you wont be able to fix it without a programmer, unless you can boot to DOS?

If you have not tried yet, put jumper back on and see if you can boot to DOS or BIOS like that, this will disable the ME region if ME region is what got messed up during the flash you may be able to reflash again.
If you do get lucky and that gets it started again, redownload the file and make sure you get that MD5 above before you flash it. And if needed, please give me a free file host other than google you want the file uploaded to and I can re-upload for you.

---

What is "SOC motherboard"? Yes, that guide you linked applies, and here is one with lots of images to show you how to correctly use everything
https://www.bios-mods.com/forum/Thread-G...341A-programmer

That is correct programmer, but you also need SOIC8 test clip cable, or SPI Cables

Zitat von Lost_N_BIOS im Beitrag #34

---

What is "SOC motherboard"? Yes, that guide you linked applies, and here is one with lots of images to show you how to correctly use everything
https://www.bios-mods.com/forum/Thread-G...341A-programmer

That is correct programmer, but you also need SOIC8 test clip cable, or SPI Cables

---

@cemara - Yes, cables are needed unless you have a drop-in/spring loaded SOIC8 adapter or PCB based DIP8 adapter to desolder the chip from the board and then put into the programmer. Which I assume not, that's why I mentioned you will need cable too when said to pickup a CH341A
Thanks, I gotcha now, SOC does not matter, processor is not used for this process, so additionally no heatsink removal is required either. BIOS chip is right above the CMOS battery, that is all you will be connecting to in order to reprogram the BIOS.

I've setup everything but i got 1 issue, during PART2 of that post, the "Detect" button remains greyed out, am i supposed to pick other than W25Q64BV?

Edit : its finally detected with W25Q128FW :)

Do you have jumper in correct position on the programmer itself, should be on 1-2 (End of block, nearest middle of programmer, on lever side)
Are you sure you have all cables connected correctly? To programmer side and to the BIOS chip itself? If yes, then you may need to leave power supply connected if you have it disconnected now, or you may need to disconnect it.

If you still cannot get it, show me images of your BIOS chip on the board with nothing connected to it (So can see it's orientation), and then show me image of cable connected to the BIOS chip, and then cable connected to the programmer.

It could also be software bug, maybe detect button doesn't work on some versions, not sure? What version software are you using? If not already, try 1.30, I know that one works correctly for W25Q64BV/FV when clicking detect it will show both and choose W25Q64FV if BV is not working
Does it show "Device Connected" in bottom right corner? If not, use a different USB Slot.

You can't use 128 if chip size if 64, please try W25Q64FV instead, or just W25Q64 without any letters

I looked directly into the chip in the motherboard and it has "128" in it, so i chose W25Q128FW, and its finally detected..
then i tried read, verify, but during verify i got " chip main memory with the contents are in disagreements"
what should i do then?

OK, well then that makes more sense! Yes, then you would use W25Q128xxx The error you mentioned is normal, that means it failed try again.

What is the actual chip ID? Try choosing that, if not, try another similar. "Detect" button should work at first, without selecting any ID.
What software version are you using? You just have to keep trying until you find the right software that works with that chip, and then right ID that works too.

Ok i tried it 4 times now but it still gives same result, ive also tried other "128" but they all now throw the same error.. im using 2.9 just like instructed in that page

For the 10th time what software version are you using? *Edit, just saw your edit. I've never heard of any version 2.9?
Here, download new package and try 1.30 / 1.31 (don't like layout) / 1.34 - http://s000.tinyupload.com/index.php?fil...257455007472602
I've used 1.30 and 1.34 on 128MB Winbond chips without issue. Let me get in my pile and see if I have your exact chip, if I do I will find what works and make a test for you - I have W25Q128FVSG chips, testing now!

Also, now still waiting for actual CHIP ID, I thought you mentioned it once but now I don't see it?

My bad, i mean 1.29
sorry i had to find a magnifying glass because its so tiny, its winbond 25Q128FWSQ,
ok gonna try newer version now

Well bad news, both 1.34 and 1.31 gave me same error...
But the strange thing now is when i press "verify" it immediately throws that error instead of loading first..
btw, i dont see 25Q128FWSQ, in any versions, could it be too recent ?

Drats! I do not have that same chip to test/compare with, only W25Q128FVSG
So far, no luck on writes with W25Q128FV or BV using 1.30 or 1.34, so I assume reads will be same, but am unable to get that far yet since I want to verify in proper order to verify all functions work with xxx version and xxx chip ID

1.34 is brand new version, but W25Q128SW is the issue, I see now thanks for giving chip ID Finally https://www.winbond.com/resource-files/w...v_g_feb1714.pdf
This is 1.8V chip, you need 1.8V adapter to use in the programmer, 3.3v is too high and will never read or write properly
https://www.ebay.com/itm/253208845481

Ok i bought that type already, but i was wondering if its even technically even possible to enable legacy? Other gemini based boards also have this no legacy issue and there doesnt seem to be a fix yet
https://forum.odroid.com/viewtopic.php?f=168&t=33097