Yes, but if you had it set as shown, it may only erased 128KB. I never said anything was empty, I said hopefully it's not empty, since you only dumped 128Kb and tried to write 128KB
Yes, read or write can take several minutes. If it is all lost, you will have to give me images off all the stickers on your board, then I will make you new UUID, add serial and LAN MAC ID from stickers

I checked that dump, all FF (Blank). When did you erase chip, before or after you dumped that 128KB?
If you erased before you dumped that 128KB file you sent, then current dump is invalid (ie not actual chip contents). Try 1.30 instead, and go ahead and also make a dump with ASProgrammer too.
If you erased chip after you made that 128KB dump, then it's possible all blank, but I'm not sure due to you had wrong ID and thus size selected. Go ahead and do both dumps mentioned above anyway so we can be sure.
Please put those in an archive (7zip, zip, rar)

Zitat von Lost_N_BIOS im Beitrag #436

---

Yes, but if you had it set as shown, it may only erased 128KB. I never said anything was empty, I said hopefully it's not empty, since you only dumped 128Kb and tried to write 128KB
Yes, read or write can take several minutes. If it is all lost, you will have to give me images off all the stickers on your board, then I will make you new UUID, add serial and LAN MAC ID from stickers

I checked that dump, all FF (Blank). When did you erase chip, before or after you dumped that 128KB?
If you erased before you dumped that 128KB file you sent, then current dump is invalid (ie not actual chip contents). Try 1.30 instead, and go ahead and also make a dump with ASProgrammer too.
If you erased chip after you made that 128KB dump, then it's possible all blank, but I'm not sure due to you had wrong ID and thus size selected. Go ahead and do both dumps mentioned above anyway so we can be sure.
Please put those in an archive (7zip, zip, rar)

---

@nicovon Yes!
Look at all plastic parts of your motherboard p.e. -> 24-pin power connector. There could be some combinations of letters and digits. At LAN / NIC or somewhere else there could be the MAC address. And take a look at the back side.

And please don't post your serial numbers here in forum. Sent it as an private message to Lost_N_BIOS.

Regards, MiMo

@nicovon - Yes, please send me images of all stickers on the board itself, be sure to check as mentioned above, on side of 24 pin, top/bottom sides of PCI/PCIE slots, and make sure to include the long white sticker on the board itself.
Sometimes, there is a sticker on the back of the board too, but that's getting rare now with more modern boards.

YOu didn't answer my questions?? Nor, provide the additional dumps I mentioned, please do that, in case it's as I mentioned

Yes, 128KB file may contain your LAN MAC ID, I'll have to check, but that would be the only thing it may contain. (I checked, it's not there due to GbE not used in this BIOS)
And yes, I can use fake info (Have to for GUID, at least partially). Serial can be made up, if you never plan to RMA, and if it doesn't mess with windows activation.
LAN MAC ID cannot be made up, but this will be on a sticker on the board. However, if you are lucky, since GbE not used, the LAN MAC may be stored in chip and still be OK

@Lost_N_BIOS Yes, I'm sorry I didn't send you dumps anymore. Saturday I send you everything. Thanks again for your valuable help. :)

Zitat von Lost_N_BIOS im Beitrag #439

---

@nicovon - Yes, please send me images of all stickers on the board itself, be sure to check as mentioned above, on side of 24 pin, top/bottom sides of PCI/PCIE slots, and make sure to include the long white sticker on the board itself.
Sometimes, there is a sticker on the back of the board too, but that's getting rare now with more modern boards.

YOu didn't answer my questions?? Nor, provide the additional dumps I mentioned, please do that, in case it's as I mentioned

Yes, 128KB file may contain your LAN MAC ID, I'll have to check, but that would be the only thing it may contain. (I checked, it's not there due to GbE not used in this BIOS)
And yes, I can use fake info (Have to for GUID, at least partially). Serial can be made up, if you never plan to RMA, and if it doesn't mess with windows activation.
LAN MAC ID cannot be made up, but this will be on a sticker on the board. However, if you are lucky, since GbE not used, the LAN MAC may be stored in chip and still be OK

---

Hello all,

Why on hell my CH341A is not able to detect any of my 2 BIOS chips? Ther is no way to detect them... I have 2 old MoBos:

- ACER Aspire 5920 - MXIC 25L8005 BIOS chip
- Samsung NP-RC530 - MXCI 25L3206E BIOS chip

I try to make tests with them, but it is imposuble. Ther is a very curious thing... There is one moment, I suppose when the CLIP is Ok connected, that the on power light in the MoBos gets on in both laptops (as you can see in the image.

In Samsung it blinks green-red, and in Acer it lights in blue. But neither in this situation the chips are detected. Even if I read the chips with the power light on, selecting both manually, all I get is FFFFFFFFFF....

I am a bit desperated in this situation. I am using both Programmer and ASProgrammer, with all versions of them, and even with a bootable Windows 7 x32 (I am stuck in Win 10 x64).

Some idea, please?

@Haplo you should not have the systems powered on, and in most cases you would want to remove the battery and main power cable too. Some systems may need main battery and or power connected, but never on.
I say this because you mentioned blinking green-red and or blue etc, none of those are programmer LED colors, so makes me think you have the systems you're trying to dump from powered on.

Have you used CH341A before, successfully, or is this yoru first attempt? It may just be bad connection, what LED's do you see on the programmer itself? One bright, one partially dim (While doing no read/write/detect) means bad connection.
There should only be one bright LED if you are doing nothing, then once read/write or detect the other will light up bright too. Anytime second is dimly lit it's not a good connection or there is a power related issue (not enough, or too much etc)

@nicovon - You can ignore that message with 1.30 and proceed. I guess you should have been able to tell from the 30kb dump package, all are blank I don't even have to unzip that
Got em

* Edit - give me some time, I have one of these boards, so I can dig it out and get the exact location and format of how these details are put into this series.
UUID and or possibly serial will have to be partially made up, since you lost originals.

Zitat von Lost_N_BIOS im Beitrag #443

---

you should not have the systems powered on, and in most cases you would want to remove the battery and main power cable too

---

Zitat von Lost_N_BIOS im Beitrag #443

---

I say this because you mentioned blinking green-red and or blue etc, none of those are programmer LED colors,

---

Zitat von Lost_N_BIOS im Beitrag #443

---

I say this because you mentioned blinking green-red and or blue etc, none of those are programmer LED colors,

---

Zitat von Lost_N_BIOS im Beitrag #443

---

Have you used CH341A before, successfully, or is this yoru first attempt?

---

All those quotes just to answer me?? So, try with power connected then, since you have not already, some systems need that, also try with battery and PSU too if no luck with PSU alone. Do not power on system though.

2 RED leds on flasher during read means good connection, usually. It may be possible for that to happen w/ a bad connection, but I've not seen it (never paid attention at bad connection though, so may be possible it happens)

Bad connection between chip and clip happens ALL THE TIME, sometimes it takes me 20+ times to get it perfect, sometimes I almost give up and get out my proper BIOS jumper tool instead.
So, since this is your first time, I assume this is a clip/connection problem and you just aren't getting it perfectly, that and or it also needs the PSU/battery for that board.
Trust me, looking connected perfect and actually being connected perfectly and securely are two very different things, and it's often a pain to get it just right. NEVER will it take only 1-2 clip attempts, at least not that I've ever seen.

[quote=Lost_N_BIOS]UUID and or possibly serial will have to be partially made up, since you lost originals.[/quote]
@Lost_N_BIOS I thought you had completely recovered them from the stickers I sent you.

Hello, I'm welcome to the club too, right? :D
Guess what, I tried to downgrade my BIOS to an older one using FPT(should've used AFUDOS instead) while on Windows. Reboot. It doesn't work anymore. Turns on for a fraction of second, turns off. Keeps this cycle for 1 or 2 minutes. Completely dead. I've bought the CH341A and flashed the older one again but again, it didn't work(what a surprise huh?).
There is only one remark, if I didn't had used FPT but AFUDOS instead, the downgrade would be successful because I have done it in the past.
My motherboard has the ME_UNLOCK pin which must be shorted if I need to flash a bios, it's a Z77H2-A3(I didn't found anything on internet about this obscure motherboard), plus the manufacturer released the latest bios in a format that is only flashable through Windows(it's a .exe). And I'm dumb like a knob because they stated on their website to not downgrade it, it would crash the system. However this time I commit the big mistake of making use of FPT.
I have the standard bios that came with the computer saven(how lucky am I, right?).
I was wondering what could be done in my case because when I try to flash through linux it says the .bin file is smaller around (6293kb) than the chip (8192kb) thus not able to be written.
ROM: MX25L6406E
Ah, here it goes, the standard bios.
https://mega.nz/#!WsUwzarL!qKDyM1MqYu7eu...ICJ_33vAmMM3Scc
gdrive:
https://drive.google.com/file/d/1fv_br9t...iew?usp=sharing
The latest bios file available on the manufacturer website is the: 30528_W_63EAh.zip
https://www.ecs.com.tw/ECSWebSite/Produc...155-LL-Intel-RR-
I read so many threads on this forum yet I'm not able to flash a working bios to this board, with the knowledge acquired here something makes me have the presumption that it is not possible to fix it, unfortunately :(

@nicovon - Yes, I have your sticker images, did you see my post/edit above at #443.
Original info cannot be recovered in full, due to GUID is often made of date of manufacture details, and sometimes serial has that info as well, this is why I mentioned what I did.
I will try to dig out the board I have like this tonight!

@c00lkid - FPT works great, when used properly, I suggest this 1000% of the time over AFU every time. Sounds like you possibly flashed something incorrectly with FPT.
Please clarify, the Mega/google link, what BIOS is this, a backup, and if yes, what did you make this backup with (What software)? Do you have FPT backup from before you flashed with FPT? If yes, send me that.

ME Flash pins only need shorted if you plan to reflash ME or FD region of BIOS, this is not required every time, only if BIOS has updated ME FW in it and you want to update it.
This probably why your BIOS said you can't downgrade after BIOS you used before, you need to downgrade ME FW too

Please also link me to your motherboard driver/BIOS download page, the above link is not valid. Or, confirm for me, which of these is the correct page to grab your BIOS from
https://www.ecs.com.tw/ECSWebSite/Produc...erview/0/1/1326 << I assume this one, but you know how assuming goes sometimes
https://www.ecs.com.tw/ECSWebSite/Produc...erview/0/1/1339

Also, hopefully you have not erased the chip or tried to write to it yet! Please dump the chip now, and send me that, with the above "Original backup" you made.

Not sure what you are talking about with "Some BIOS" being EXE or windows only? I don't see any exe BIOS here or on ECS website.
30528_W_63EAh.zip contains an encapsulated BIOS region of the same name, and then flashing tools that are exe. You can't program this BIOS region, nor should you ever try, even with capsule removed, you will loose your board specific details, serial, UUID, LAN MAC ID etc)
I assume that 30528_W_63EAh.CAP is what you programmed with FPT, correct? If yes, it warned you in bold red not to proceed, so you should have stopped right there!

Anyway, I need your original backup you made with software (Hopefully FPT, but if not AFU will do), and then I also need you to dump your current BIOS chips contents and include this as well.
Please archive these two things for me, and upload to http://tinyupload.com/ Or https://uploadfiles.io/
Or, some other free site is fine too, just not Mega or Dropbox.

@Lost_N_BIOS
The mega/gdrive link is a backup, one made with afudos while the me_unlock pins were in short. This file is named afuwin.rom.

I don't have the FPT backup but at the same time I created my account in this forum and was researching on internet, I contacted the manufacturer and they released me one file that is supposed to work on my motherboard(I begged for the bios file from the support and they were comprehensive). I guess it can help you because I don't have a backup from FPT but one file that contains the descriptor region was released by the manufacturer.
This is the file: 30528.BIN
https://ufile.io/k9f14hgy

My motherboard required to short the pins whenever a bios update was supposed to be done, but that doesn't come in case now since I can manually flash it with the programmer.
Yes, this is the correct link: https://www.ecs.com.tw/ECSWebSite/Produc...erview/0/1/1326
The .EXE file I'm talking about is available on this website, look at the bios update section.
https://i.imgur.com/DMyt1Gp.png
No, I did not flash 30528_W_63EAh.CAP with FPT. I flashed the afuwin.rom with FPT. Just shorted the me_unlock pins and surprisingly it did not warn me about anything while flashing the afuwin.rom.
I never did a backup before attempting to write afuwin.rom(it's a way old backup, but still one that worked, it's originated from the motherboard).
So we have things like this.
Old backup from bios: afuwin.rom
https://ufile.io/4k3b3lze
Current: bios.bin
https://ufile.io/f0yltfiu
Manufacturer: 30528.BIN
https://ufile.io/k9f14hgy
Hope it can helps. Thanks.

It's OK you don't have a FPT dump, I only hoped you did, but AFU one will work OK since you had jumper on there (hopefully, I've not looked at file yet)

As mentioned, pins only need shorted to update ME or FD, not all BIOS will update ME, so it's not always required.
However, they may have "coded" their flash programs to attempt to flash ME FW even if it's not going to, so if that is case then yes all might fail without jumper, but it should only be required with BIOS updates that plan to update the ME FW
Or, if you use FPT from the stock package to flash with instead of AFU, and do not specify BIOS region only, that would make it write FD/ME too (FPT should never be used in this manner with stock BIOS anyway, you would always loose serial, UUID, and MAC ID)

Your image is about ME FW / BIOS update, were you on old BIOS with ME FW V7, so you had to use EXE to update your BIOS? So, that leads to this EXE, is that what you tried to write with programmer? >> http://www.ecs.com.tw/extra/windows_8_su...829(CPUEVO).zip
That contains Full BIOS, but not one you would ideally use with a programmer, or you loose your serial, UUID, LAN MAC ID etc.

I'm more confused now, you're providing way too much information and files/links etc. I only need exactly what I asked for.
What is "Current BIOS"? What BIOS are you on now? I assumed system not working, so does current BIOS mean bricked BIOS that you dumped with programmer?
What BIOS do you want to be on?? I assume some older one, but which one (Just back to original?), and WHY would you want to do that?
Your backup BIOS (Afuwin.rom) is version 1.2, your messed up "Current" BIOS.bin is 1.27. 30528.BIN is also 1.27 version (Both 1.27 versions are BIOS after ME FW update to V8)

If you want to go back to original, I will have to find a proper full dump of your board that has ME FW V7 in it, since you do not have such a backup right now, so please wait while I try to find.

*Edit -OR, you can email them again and tell them you need the OLD ME V7 type BIOS (130103A) or whatever ME FW was before 8.1 BIOS (Maybe it was old Non-UEFI BIOS), not the new ME V8.1 BIOS they sent you.
I can only find latest BIOS in dump form, no where is the older BIOS type dumped, even on paid BIOS sites, so you will need to request this from them. I will try to downgrade ME manually for you and rebuild a BIOS, but I can't promise this will work
*Edit 2 - @c00lkid - do you remember or know, what your ME FW version was before all this? Was your old BIOS non-UEFI Type, and the new one was UEFI (graphical type BIOS vs old plain text type BIOS)?
Sorry, I initially thought this was a ME FW V7 >> Vs >> V8 issue, but now I think it's old BIOS style (Legacy, plain text) vs new BIOS style (UEFI, GUI type interface). Is that correct?

What is your BIOS Chip ID (look on chip, do not rely on software or detection)? And, what software and version did you use to dump BIOS with?