Read carefully the first post.
http://valid.x86.fr/538krk
i know that i’m a lucky guy 
it works
what will happen when i insert a new ROM (from an other mobo that supports Ivy) into this mobo ?
If you replace the module processor support, there may be two options:
1) You are very lucky if it will work.
2) Get a brick, which is more likely.
To begin, I advise you to contact our Customer Support Asus that they clarified the reason why this motherboard is not supported by the Ivy Bridge.
Not a fact. Link shows a model in which Asus P8H61-M PLUS V2 has some sort of support for processors Ivy Bridge. Since there microcode for 6A9 (6A9 - Ivy Bridge). In your case, this is no microcode for 6A9. And there is no garanitii that adding microcode processor IVI score on your motherboard is.
EDIT by Fernando: Parts of the fully quoted text deleted (to save space within this thread)
i insert v2 ROM into v1 h61
i am going to flash source code from v2 rom into v1 rom tomorrow
EDIT by Fernando: Parts of the fully quoted text deleted (to save space within this thread)
AMD RAID ROMS ver. 3.3.1540.19 for controllers 4392 , 4393 , 7802 , 7803
AMD UEFI RAID DRIVER ver. 1.0.0.49 for UEFI Bios
Please include these roms and the driver in UBU Tool.
Thank you for your help.
EDIT by Fernando: Post moved and Title customized
AMD_RAID ROMS+UEFI RAID Driver.rar (882 KB)
@ kgbab:
Thanks for your contribution!
Since your request goes in line with the topic "UBU", I have moved it into the related thread.
This way we have a better chance, that SoniX, the developer of the UBU tool, will notice the new BIOS module files you have offered and may fulfill your request.
Regards
Fernando
@kgbab
@Fernando
I have said many times that there are some difficulties with the addition of AMD. I have no motherboard is for testing. A motherboard is the risk strangers I will not.
I see, of course, once again, what can be done, but I will not promise anything. So please forgive me in advance.
Added:
At this point, I have an idea. Make 2 packages UBU. The first package for Intel, for example UBU_I and one for AMD, for example UBU_A.
And as I said, I have no motherboard is for testing. So I’m not sure compatibility OROM AMD, even within the same chipset with different revisions.
If someone is willing to risk his motherboard is, then send me the file BIOS that point I had started.
That is a good idea.
Unfortunately I don’t have an AMD chipset mainboard myself. So I cannot do any tests regarding the AMD OROM/EFI modules.
And I have not. Thus, if someone is going to be interested, 
@lordkag
How do you determine the version in files MISC_SIG? If you are not hard, please explain on an example of version 3.2.1540. Thank you.
MISC.rar (34.1 KB)
Hello Sonix
Here is the latest bios from my motherboard.
Probably I will test the UBU Tool for the AMD and I will tell you the results.
Good luck to me and you…
ASRock 990FX Extreme4 Bios ver. 2.70.rar (2.63 MB)
@kgbab
Thank you for your feedback. As soon as I have prepared an option, I shall write to you immediately. 
Hi soniX
I have the asrock 990FX Professional
The last original bios P2.00
The my mod bios for the comparation mdclab
good job 
Ok. I will try this weekend to release the first beta of UBU supporting AMD SATA AHCI/RAID.
@SoniX
It is not possible to do that, since this is just a helper module. The only way is to pair it with the main AMD RAID OROM. But this is where the tricky part starts:
- usually BIOS has 1002-4391 (AHCI) + 1002-4392 (RAID) + 1002-4393 (RAID) | OR | 1022-7801 (AHCI) + 1022-7802 (RAID) + 1022-7803 (RAID). I have not seen mixed 43xx and 78xx so far.
- the rule is to have lower ID (4392 or 7802) in 9BD5C81D-…FC and higher ID (4393 or 7803) in 9BD5C81D-…FD.
- but some boards have them backwards, so extra check is needed.
- older 1002-4392 from 3.2.xxxx.xx series are uncompressed and have all this in hex: 81FA0210, 81430210, 91430210, 92430210, 93430210.
- all others are usually compressed so you need 7z.exe in UBU. They don’t have the ID in hex.
- run “7z.exe e temp\miscFC.ffs -otemp misc.bin -r >nul && ren temp\misc.bin miscFC.bin” and “7z.exe e temp\miscFD.ffs -otemp misc.bin -r >nul && ren temp\misc.bin miscFD.bin”
- run “hexfind 64000057568B5E048B473A8946FC662BC0668946C4B910008D7EC81607F3AB66 temp\miscFD.bin >nul”. If true, it is 4393 or 7803, otherwise check with miscFC.bin, otherwise dead end.
- I have only a few misc.bin from each ID, so this is only an assumption. Maybe kgbab can share other modules (even if not AMD), since he seems to have some high access.
So do something like this:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
2
3
4
5
6
7
8
9
10
11
12
13
14
set miscFClow=0
set miscFDlow=0
hexfind 92430210 temp\miscFC.ffs >nul && hexfind 93430210 temp\miscFC.ffs >nul && set miscFClow=1
hexfind 92430210 temp\miscFD.ffs >nul && hexfind 93430210 temp\miscFD.ffs >nul && set miscFDlow=1
if %miscFClow%==1 if %miscFDlow%==0 ------> then FC is 4392/7802 + FD is 4393/7803 and go to ...
if %miscFClow%==0 if %miscFDlow%==1 ------> then FD is 4392/7802 + FC is 4393/7803 and go to ...
rem Both are either compressed or uncompressed
7z.exe e temp\miscFC.ffs -otemp misc.bin -r >nul && ren temp\misc.bin miscFC.bin
7z.exe e temp\miscFD.ffs -otemp misc.bin -r >nul && ren temp\misc.bin miscFD.bin
rem Search this string. It is only found in 4393/7803.
if exist temp\miscFC.bin hexfind 64000057568B5E048B473A8946FC662BC0668946C4B910008D7EC81607F3AB66 temp\miscFC.bin >nul && set miscFDlow=1
if exist temp\miscFD.bin hexfind 64000057568B5E048B473A8946FC662BC0668946C4B910008D7EC81607F3AB66 temp\miscFD.bin >nul && set miscFClow=1
if %miscFClow%==1 if %miscFDlow%==0 ------> then FC is 4392/7802 + FD is 4393/7803 and go to ...
if %miscFClow%==0 if %miscFDlow%==1 ------> then FD is 4392/7802 + FC is 4393/7803 and go to ... else Dead end.
It also needs to account for one or none being compressed, so more polishing is needed. But this AMD is going to be a beast, since it has 4-5 (!!!) AMD RAID EFI files, then there are 2 more for FM2+, then there are 2-4 OROM+MISC, then there are VBIOS files.
@lordkag
It turns out that there is a direct dependence on versions? That is, if for example 4002-4392 is version 3.0.0.000, then MISC (for 4392) will be the same version 3.0.0.0000?
Added:
I see that there is a compression LH5 (LHARC), I wonder whether all will understand the motherboard is compressed MISC? Or have to do even unpacked?
Yes, they are linked with the main module. The problem is to determine with which one. The rule 4392/7802 in …FC and 4393/7803 in …FD is not always followed. Some of them are bugged with reversed order.
MISC.BIN for 1002-4392 up until 3.2.xxxx.xx is uncompressed, only after 3.3.xxxx.xx is compressed. You should leave them as they are found, since they have a checksum check in byte 0x0A.
It confuses me. If in the MISC.BIN was at least a hint to what Device ID refers.
In general, while I come from the rule OROM 4392/7802 -> MISC for 4392/7802 = …FC and OROM 4393/7803 -> MISC for 4393/7803 = …FD.
For AHCI (4391/7801) has its own MISC?
No, the AMD AHCI ROM doesn’t have and doesn’t need a MISC.BIN module.
The first beta version with support AMD.
While only display versions for OROM 4391-4393 and EFI AMD RAID / Utility.
https://www.sendspace.com/file/ebf16p
I do not have a BIOS for 7801-7803. 
Added:
@asrlab
@kgbab
@All
If there are problems in displaying versions then send screenshots.