Zitat von SoniX im Beitrag #315

---

And UBU, at the very beginning of the work, what does the "Platform - " write?

---

@Gonzakpo

Oops Then your BIOS does not belong to Insyde H2O and UBU can update microcodes. But the package includes only microcodes for desktops. For notebooks, you need to add on your own or leave only 1 microcode.

Zitat von SoniX im Beitrag #305

---

@hoffer

For versions 1063-1065, there are no clean OROM and BSF files. Therefore, they are not uploaded to the archive.

---

Zitat von plutomaniac im Beitrag ASUS K93SM BIOS MOD

---

If you continue what you are doing you will brick your laptop.

Intel vBIOS has a mobile and a desktop firmware. UBU includes the desktop counterpart only and that's why it won't allow you to replace your current one. You need to find the mobile 2170 vBIOS and modify it with Intel BMP first (SoniX has a "repository" link somewhere for both firmware and BMP Tool) otherwise there will be issues with video/audio sources, outputs etc.

Don't use MMTool5 to modify an Aptio IV platform. Use MMTool4 instead. Don't use UBU for a laptop unless you know what to do and what not. In this case only RST, PXE and Microcode can be updated via this utility. Nothing else.

---

Zitat von SoniX im Beitrag #317

---

@Gonzakpo

Oops Then your BIOS does not belong to Insyde H2O and UBU can update microcodes. But the package includes only microcodes for desktops. For notebooks, you need to add on your own or leave only 1 microcode.

---

@hoffer amd @ALL

In general, I do not recommend updating OROM VBIOS and GOP Driver. If you have no problem displaying the image on the screen.
I had cases when the image did not fit on the screen, a problem with the resolution. In such situations, replacing the OROM VBIOS or GOP Driver helped a lot.
So better think again - do you need to change or not.
But if you really want, then at your own peril and risk. :))

@hoffer

If I understand you correctly, then do you want to spell OROM VBIOS 1037 to 1044?
No problems. The VBT for both versions are identical and the transfer of settings will be 1 in 1.
But just in case, send me your files, I will compare.

Oh yes. OROM VBIOS, starting with HSW, are universal, that is, suitable for desktops and mobile.

@Gonzakpo

Very simple. If it's Intel.

1) In the "Filea\Intel\mCode" folder, create your own folder. Exfmple - "My_mCode"
2) Put all your microcodes in it.
3) Open d TextEditor file "MCUpdate.txt" amd Redo
'CPUID' My_mCode\'name file

Example

;My_Mcode
706DC My_mCode\cpuid706DCblf-nla-bla
706DB My_mCode\cpuid706DBblf-nla-bla
.....

* It is advisable to write in descending order.


For AMD.
1) Open "Files\AMD\mCode" folsder
2) Remove old mCode from "Old" or "AM4" folder
3) Add new mCode.
Done.

Updating Intel and AMD microcodes is radically different for technical reasons. At AMD, microcodes are always one racer.

@SoniX
Thanks a lot for your advices!
Here are my files that I try to made for Kaby and Haswell to update orom VBios with some explanations in file пояснения.txt

@hoffer

Well. Will watch. Delete your archives, I have already taken them.

@SoniX:
Thank you. I succeeded updating the microcodes. Then I verified the Modded Rom against the original one, and I see that the padding after the microcodes was removed... Is this normal?

These are the links of the ROMS:
Original BIOS: https://mega.nz/#!XtkDQSTC!QqRSYR5Y_gkBp...O1pRXDxstpzxhqM
Modded BIOS (by UBU Tool): https://mega.nz/#!ipsFDSxK!2MBl0tBIGLrvK...M1sY19i4wuX8Lfg

EDIT by Fernando: Fully quoted post replaced by directly addressing (to save space)

@Gonzakpo

Hard to say, but usually not critical. Such filling is usually provided for adding new microcodes, but there may well be an alignment of subsequent volumes.

Zitat von SoniX im Beitrag #325

---

Hard to say, but usually not critical. Such filling is usually provided for adding new microcodes, but there may well be an alignment of subsequent volumes.

---

@Gonzakpo:
Insyde H2OEZE 100.00.02.13
https://www.sendspace.com/file/kv5j4z

Insyde H2OEZE 100.00.03.04
https://www.sendspace.com/file/rqnlla

EDIT by Fernando: Fully quoted post replaced by directly addressing (to save space)

@jordanpchome
Definitely is not an Insyde BIOS. It says "unsupported rom".

@SoniX
Thanks for all your support again. Do you think is safe to flash the UBU modified ROM? Regardless of the missing padding (after the microcodes)? If I edit the bios manually using a Hex Editor and replace the microcodes myself, it is the same?? I would prefer to preserve the original padding just in case...

@Gonzakpo

I can not give a 100% guarantee for your notebook.
Any change in BIOS firmware always has a risk.

I think that you can install VMWare Microcode Driver?
At least it will always be possible to change the microcode promptly and not patch the BIOS.

@SoniX:
Yeah, probably the smartest thing to do. Because my BIOS looks very strange. Your tool identifies it as AMI Aptio. Phoenix Tool identifies it as Insyde EFI. And H2OEZE tools say it's unsupported... THIS IS MADNESS

EDIT by Fernando: Fully quoted post replaced by directly addressing (to save space)