yes its reported as PCI\VEN_1002&DEV_4391&SUBSYS_84DD1043&REV_40 :)


https://dlcdnets.asus.com/pub/ASUS/mb/So...0-ASUS-2603.zip

the bios has AMD Raid Misc 4392 and 4393 included but i only use ahci mode on it

and that i could not see in UBU yet and my knowledge with hex editing is not really good

would be nice if you could help me out :)

@empilein

Try this.

the selected file is not an EFI bios File and also USB flashback is not working :(

I was half expecting this... Because i changed the Bios, the encapsulation has changed (.cap)

Try this one instead.

@empilein

I forgot to say that you must remember to rename the Bios for Flashback to work. For you motherboard, it should be renamed M5A97R20.CAP before trying to flash it.

Zitat von Phoenix48 im Beitrag #194

---

@fr0tch

You are not the first person to have this problem but you are the first person that i know of to have this problem with the Z version... I explain:

Usually, but rarelly, once in a while there are some people reporting having a 1042A chip in a Formula (non-Z) instead of the usual 1042 chip. Everyone always assumed that Asus run out at some point of 1042 and put some newer 1042A untill either the 1042 stock got up again or untill the production of the Formula was completed and replaced by the Formula-Z.

Anyway, all this to say that you are the first that i am aware of that it is the other way around with a Formula-Z instead of a Formula.

In any case, because the problem is more frequent and already well known with the Formula, i suggest you see the last part of the first post in the Formula (non-Z) thread instead. everything you need should be there.

---

Zitat von Phoenix48 im Beitrag #201

---

@empilein

I forgot to say that you must remember to rename the Bios for Flashback to work. For you motherboard, it should be renamed M5A97R20.CAP before trying to flash it.

---

@fr0tch

If your original dump file that was done before your first flash attempt shows 2104B, this means you have a 1042A firmware originally and, since it was working, it doesn't really matter what is written on the chipset. It is another well known fact among many peoples who got burned by flashing the wrong firmware in a 1042(A) chip by only trusting according what is written on it. Why? Because it was discovered that way that there are chips that are identified as 1042 who work with the 1042A firmware and vice versa. Not many. But it happened to some peoples. Just don't ask me why this happened and why some chips were made that way and not identified correctly... The point being that because of that, the original firmware in a chip is by far more trustworthy to say what a chip really is rather than what is written on it.

So since your dump of the original firmware says 2104B, it is a safe bet to say you probably have a 1042A chipset identified as 1042 written on it. So a 1042A firmware is the best bet to correct the problem since the original was the same.

Be warned that i say all this assuming that your dump file was made BEFORE your first flash attempt. If it was made after, then all bets are off and it is a guessing game now.

As for playing with the Bios to reset the chipset, i am sorry to say that nothing in the Bios will touch the firmware in the chipset even if you reflash it. And it is not related to flashback or the CMOS either. The chipset is completely independent and must be flash independently.

@Pheonix48

I wish I could say it was from the original fw, but it is not. That's the current state of the backup. But, you have helped save me a bunch of time by explaining the disassociation of the chipset from the bios, in that I at least can focus there. Any suggestions on what method might be more effective? The DOS flash or the Windows Asmedia FWUpdater? Both have said succeeded at attempting, but clearly neither has functionally. I never tried flashing 1042 at first, but it's fuzzy as to whether I noticed the issue under which condition. I did attempt to flash once before, but was rushed due to circumstances and was never able to check if it stuck. I DO know, that I didn't realize at that time there was a 1042 and 1042A firmware difference, because the drivers from Asmedia didn't differentiate or draw any attention to it. But I obviously didn't do enough research the first time. So I'm at a loss for how to attempt fixing the issue. Ultimately there may be nothing I can do but live with it, but you know I'm going to try to rectify the problem. But in the interest of being reasonable, I'll stop when the motherboard explodes in my face in a fiery hell or I throw it out the window.

And yes, after it hits the ground, I'd obviously still try booting one last time to see if that helped to fix the firmware issue.
Although, if the fiery hell thing happens, and my renters insurance covers the replacement of the motherboard... problem solved. At least where the motherboard is concerned.
Me... can't be fixed.

@fr0tch

When you have a choice between flashing something within DOS or within Windows, ALWAYS, really, always chose to go the DOS way. It is by far the safest and the more direct aproach because nothing is in the middle of the process (like Windows and anything installed in it) that can mess things up between the original command to the flash itself. Imagine flashing a USB chip that control the USB ports while something else on the PC decide to try to access those same USB ports... Or another software or program in Windows that decide to prioritise or use the ressources needed to do the flash... There is always the hope that Windows can manage all those situations well but it is often just that: Hope. Hope with often bad results. Those situations can not happen in DOS. It is just a few example of why Windows should never be used to flash anything unless there is absolutely no other choice available. More often than not, the only reason that a Windows option exist to the customers is because many can't do it in DOS, they just don't know how. So to those peoples, Windows is the easier way even if it is also the riskier way.

@Pheonix48

Oh I agree 100 percent. That is always my go to method. I love using DOS for flashing.
But being this is a somewhat unique instance, sometimes the less obvious approach works. And sometimes what seems less obvious to the limited of knowledge, is in fact the obvious choice to the more knowledgeable. If that makes sense.
I just want to have all the options to consider, at the very least, before narrowing it down to the path I choose to go down... fall down.. whichever.

Would the OptionROM offer any chances here at getting this right? Isn't legacy more direct, as long as you make sure you have the right one? Or is that just for telling it the type of device to call from, and not so much the actual chip condititions?

@fr0tch

I think you need to understand how and where each component is and what it is related to. So here are some definitions and explications to try to explain it:

BIOS: That word is 2 things the little program that controls the startup of the PC that everyone knows about, but it is also how you refer and name the chip on the motherboard that the Bios (the software/firmware) is flashed into.

EFI ROM/module: One of many module in a modern Bios that control something in a UEFI Bios. Like the NVMe module that enable a NVMe drive.

Option ROM/PCI ROM: The same as the last but not EFI, rather legacy like before UEFI was invented. It can go into an old non-EFI/legacy Bios or can be put in the CSMCORE section of a UEFI Bios which permit it to use the module even if it is not EFI.

Chip: Usually called "Something-that-say-what-is-my-function chip" like the USB chip or the sound chip. Each is an other chip, completely differrent than the BIOS chip and somewhere else on the motherboard.

Chipset: Same as a chip but there are at least 2 or more of them. For example, a USB chipset is at least 2 chips that are connected and control each differents USB ports and, because they do the same job (but with different ports), they are flashed at the same time with the same firmware when needed to.

Firmware: A little program going into a chip or chipset (like a USB chipset) or a hardware (like a HDD drive or a BlueRay/DVD/CD drive) to tell it how to behave at the core. Like a Bios in a Bios chip. But because the Bios is so much important to the PC and control so many things, no one call it that. But it is, in a way, just that: A little program in a chip.

So when a program or even the Bios speak with a chip or a hardware, it tells it what it wants and what to do, but never how to do it. It is managed by the firmware and the hardware that the firmware control. The system can tell "Read the CD in the drive and send the sound to the sound chip" But it will never manage the CD itself and tell him how to read it, or say "i have just decided that you can now read CDs written with X protocol and here is how to do it". It is the firmware that can and know how to do that, or it doesn't and will answer to the system "Sorry, i can't do it".

So a firmware update in a USB chip can correct some random USB ports disconnect issue and can sometimes increase speed but a Bios update won't. Unless the problem was an error in the way the Bios was giving the order but that is very rare.

It is a very oversimplified way to explain them all but enough for you to see and understand why a Bios change or a option rom, which is both the same because one is a part of the other, will unfortunately not fix your problem. Only a succesfull flash with the right firmware of your USB chipset can fix it.

The way i see it, you have a 50% chance of getting it right because it is either the firmware for the 1042A that you need to flash or the one for 1042.

Now a question: The first time you tried to flash it, did the flasher asked you if you wanted to "force" the flash anyway, or the question never appeared?

Honestly, my brain is frazzled after3 days of this. The first time I attempted to flash, was actually some time ago, so I don't actually recall what happened in any useful amount.
I do however remember doing a flash in the last couple days where I had to "force" it from the Windows environment.

Interestingly though, I just had a positive flash using the Asus USB 3.0 FW Update Tool v3.0
It flashed successfully and it shows 120816_02_02_6D now when viewed with the Asmedia Tool instead of 100803_00_00_0D, which shows some positive movement.
I think. But I'll reserve hope for later. SSID=8488 SVID=1043 though, is that right?
I need to take a break and get something to eat, and come back in a bit, sorry.

Sorry, can't help you there. I don't remember what it is it is supposed to show up and i am not near that PC now so i can't verify that. Find the thread about flashing the ASMedia USB chip in the forum around here, it is probably written somewhere in it.