@maks - I put in microcode with the version H2OEZE you mentioned, via "Other > Microcode" in the menu (496C2 and 406C4 codes are also in there by default).
I updated them all, by first download all three updated microcodes, create empty ncpucode.bin, combine all three to that, then delete code in stock BIOS, replace with new combined microcode file.
If you need better explanation on that let me know, I assumed you knew about that since you've dug this deep already so I kept it short

https://www.sendspace.com/file/361qw1

Cherryview GOP 8.0.1040 here, in case you need later including BSF's for both, but still can't find the 1005 you need Other modules there may be of use to you as well.
RE:CherryView BIOS Mod Help

LAN can be modified w/ UEFITool, or with the H2OEZ2 app. All modules can be replaced with that version it looks like, via components > module > Replace.
I see what looks like at least 100+ shown as replaceable, and I see Intel GOP at the very end of the list whenever you find proper one for that.
via Binary-Rom > OpRom you can replace same as extract likeyou did, oprom one is vBIOS 2 is Intel Undi/Realtek PXE GBE, 3-5 is NVidia roms.

As for UEFITool errors like that, when I see them in a stock known working BIOS I assume that's normal and do not try to mess with them or correct it. Sometimes I avoid using UEFITool then, in case it automatically corrects them and breaks something.
OK to test if you have a programmer, then it's not a problem, but if not I'd try MMTool instead, then take back to UEFITool and if errors are fixed, be worried again.
Once you have a programmer you can right click, rebuild all those errors after double clicking on them and it takes you to each section at the top, and see if it's OK to use after that.

When messing with BIOS editing, especially when there is so many unknowns, get a CH341A flasher, they're very cheap (Get two!) usually only $2.50-$4
https://www.ebay.com/itm/263458010112 - Choose "Blue" model, and if $$ is no issue, get black one below too, it's cheaper than ordering same one from this seller. Or get both from same seller, add blue to cart, go back and add black from same seller, then checkout.
https://www.ebay.com/itm/223021931206

I suggest both types, because often people have issue with one or the other in various situations, and they're so cheap everyone might as well get both.
If your BIOS is soldered to the board, grab one of these too
https://www.ebay.com/itm/263708580560

@Lost_N_BIOS
Thanks fof your help.

As you can see in H2OEZE cpu microcode section is shown as:

So is that combined microcode file you mentioned? Could you describe how can I create new one? AFAIU I need to create empty file ncpucode.bin and put all three microcode files inside one by one right? Should I add some header or other stuff there?

If I remember correctly there is GOP 8.0.1038 inside. So I need to find GOP 8.0.1040 somewhere... Maybe from another Acer model.
Within H2OEZE there are 2 modules:
FF0C8745-3270-4439-B74F-3E45F8C77064 so called IntelGopDriver
and
878AC2CC-5343-46F2-B563-51F89DAF56BA so called IntelGopVbt
I think that the first one is UEFI GOP driver and second one is legacy VBT driver. Is that right? How can I find if GOP driver is 32 or 64 bits?

And finally - I don't know how to find and replace AHCI driver. There are plenty of modules named ahci/sata/*something*. For example:
3ACC966D-8E33-45C6-B4FE-62724BCD15A9 - AhciBusDxe
BB65942B-521F-4EC3-BAF9-A92540CF60D2 - SataController
69FD8E47-A161-4550-B01A-5594CEB2B2B2 - IdebusDxe
As I mentioned in my earlier post I would like to update EFI (and OROM maybe) modules for AHCI but which one should I replace?

I tried to compare modules (network) taken from my bios with @SoniX one but they have different structure. So first I need to know is it safe to replace it.

P.S. I already have CH341A flasher. I fried "black" model and now I've got "green" one or I can use my Rapsberry Pi to flash bios.

Later when I have time (heading to sleep now), I'll write out detail on how to create combined microcode file.
GOP file 8.0.1040, I linked above. I will look at all of those for AHCI rom for you tonight and let you know more.

And, while you wait for my next reply, specify for me which network module exactly you are replacing, and which you compared with that you thought isn't right one.
I'll try to help best I can, but as you notice already not many people modify these BIOS so there's not a whole lot of info out there. It's good you have a flash programmer already, no worries about failed BIOS testing now!

Please go ahead while you wait on us to figure out the other stuff and program in the BIOS I posted above, so I can know if the replaced the microcode safely or not. If it fails to boot, then I can try few other ways to update the microcode.
This can all be done manually, via hex or other non-tool type methods, but best to use tools when we can. The H2OEZ2 tool is made for this, so probably best to use for all, but I may need to do the microcode differently (ie remove all, then insert one by one instead of single file containing all)

*Edit -
To create single microcode file from several microcodes, put all microcodes into one folder on desktop for easy processing.
1. Open command prompt at that folder run this command to create empty microcode file (Ignore any warnings) >> Nul > NCPUcode.bin
2. Combine all microcodes to that new empty microcode file with this command, editing in your full microcode file names in the middle area (leave ncpucode.bin at start and end) >> copy /b ncpucode.bin + microcode1.bin + microcode2.bin + microcode3.bin ncpucode.bin
3. Right click newly compiled ncpucode.bin and go to properties, check "Read Only" and apply.
4. Done! You now have a compiled new multi-entry microcode file.

VBT CHERRYVIEW 1005 Intel(R) CHV Mobile/Desktop PCI Accelerated SVGA BIOS Build Number: 1005 PC 14.34
OptionRom1 64KB

FF0C8745-3270-4439-B74F-3E45F8C77064 = GOP Driver 1038 70KB

VBT CHERRYVIEW 1215 Intel(R) CHV Mobile/Desktop PCI Accelerated SVGA BIOS Build Number: 1215 PC 14.34
IntelGOPVBT 6KB
878AC2CC-5343-46F2-B563-51F89DAF56BA 6KB

Watch extraction with UEIFTool or Intel tol etc, different headers via different methods, applies to all

So, I think due to version numbers and size that is three different things for vBIOS related files.

I'm still looking about AHCI and LAN. I don't think either of those AHCI (AHCIBus or SATAController) are what you want to update (Like AHCI Option rom I mean)

Option Rom 2 is Intel UNDI/Realtek PXE (Boot from network, not LAN)

@maks
There is one problem. After updating the files in this BIOS, you can get a brick.

@Lost_N_BIOS
I'll try to merge 3 microcode files (I think that I need only one for 406C3) in HxD to be sure. Then I use H2OEZE to replace it.

I checked InsydeH2O Setup and there is definitely Intel(R) GOP Driver [8.0.1038]. So what should I do next with GOP driver? Maybe it will be better to leave VBT module as is because I don't use it.

@SoniX
Why do you think so? I've got CH341A or RasPi to "unbrick" this laptop - I hope so :/

@maks
Ok. Try it. I updated only the GOP Driver to version 8.0.1040.
If your device works, then you can try to update further.

@SoniX

I tried to update your modded bios with no luck. FPT said

Error 286: Unable to write data to flash with SPI lock enabled.
 

So first I need to unlock SPI. Maybe it will be possible with IFR Extractor method.

Did the BIOS I posted with the microcode update give you the same error?

There is 3 graphics components to the BIOS, that's what I was mentioning, GOP Driver, legacy option Rom, and Intel VBT. I assume all need/can be updated, but finding updates I don't know, especially the Intel vBIOS due to no BSF's

Do you have a backup made from the BIOS chip with your programmer? If yes, please upload there here, instead of the FPT dump you posted in first link. Then we may be able to unlock the FD for you within the BIOS, or yes IFR method could be used.

No jumper on the board for servicing/FDO/ME etc as mentioned in E2 section of the guide you linked above?

@Lost_N_BIOS
Yes. It gives me the same error.

I've done more research and found two interesting VarOffsets inside "Setup" DXE:
TXE HMRFPO at 0x166 with default value set to 0 - disable
and another
BIOS Lock at 0x208 with default value set to 1 - enable
But with setup_var command I was able to change only the first one (TXE HMRFPO). When I was trying to change BIOS Lock value I've got error. Something about "efi cannot change value".

Tomorrow I will try to backup BIOS chip with RaspberryPi and upload it here.

If you have ability to backup with your raspberryPI, make sure it verifies correctly, then once you're sure you can go ahead and modify then write any BIOS you want to it, no need to try and find a way to flash with programs.

My notebook model is toshiba u840w (Taiwan version)，CPU: i5-3317U
I tried to modify the cpu microcode, but I will encounter the following situation:

1. Unable to update microcode with ubu
2. When using hex replacement, the file size of the new microcode and the old microcode are different and cannot be directly replaced.
3. If you use the official Insyde tool "H2OEZE", the microcode will be added to the me firmware, not the original location.






Another tricky question:

I tried to update vbios, but the original vibos file version number is 2130.
The file in the compressed package provided by SoniX does not have a corresponding version number, and the word file prompt (ONLY FOR DESKTOP)
but the folder in the compressed package does have "Mobile"，How can I change vbios to the latest version?



Finally, my English is very bad.
All of the above are translated using google. If there is a place where the meaning is not smooth, please forgive me :)

Images are too small to view, please attach full size (System will shrink), or upload to image host and post link for full size image
I will see if I can update microcodes for you. Do you just need all microcode update to latest versions?

Sometimes, desktop will still say mobile too., and sometimes manufacturers put both or leave one by mistake. I am not sure what package or file you mean that does not have version numbers?
All the vBIOS I know of posted in packages here have version names/numbers, in many folders for various versions. * Sorry, I was confused what you meant, I understand now, you need mobile and package has only desktop versions, correct?
I will update that for you too, if I can. Please link or attach larger images, thanks

Hello, I have re-uploaded the image.
Regarding the issue of updating VBIOS, because SoniX has published an article:

[Guide] Transfer of specific Intel VBIOS settings by using Intels BMP tool

In the downloaded archive file, the world file mentioned that SNB and IVB only have "ONLY FOR DESKTOP"
But the zip file also contains the Mobile folder, I am not sure if it can be used :(

Thank you again for your help, thank you very much.

You're welcome, and thank you for larger images! And on vBIOS, yes I assume for mobile too now, since included, maybe @SoniX forgot to update word doc after later adding in mobile folder?

I see what you mean about microcode at ME now in your image, yes that's not good!

On your vBIOS image, bottom section "No 2130" in word doc, you would use 2124-2132, but yes again (ONLY Mobile) there is confusing, hope he will clarify here, if not ask in the vBIOS BMP thread you linked. I bet it's just outdated file, not updated since adding in the Mobile section.
I will wait to do anything for a reply from him about this vBIOS.
For his reference, your stock BIOS has
EFI GOP Driver SandyBridge - 2.0.1024
EFI GOP Driver IvyBridge - 3.0.1030
FFS-OROM VBIOS SNB/IVB-MOBILE Version 2130

The BIOS file provided at the top is the version I have modified with UBU and H2OEZE, except cpu microcdoe and VBIOS.

This is the official original BIOS update page:
https://support.toshiba.com/support/view...ntentId=4004823

Can you trouble me first to teach me how to update the cpu microcode in the BIOS file? Thank you :)

As for vBIOS, it seems that I can only wait for @SoniX to illustrate

PS: I think I only have one chance to update the BIOS. If it fails, it won't boot up. x(