@Doze - yes, thank you, but unfortunately in this case not worked. Maybe someone thought at DELL its not a good idea to give such tools to the users and they omitted this from the newer releases ... that was the first point made me upset
However, thanks to @Lost_N_BIOS the problem is solved.
I see, so the GUID itself is only important because it's easier to search the Setup part or I can use it in case the UEFItool cannot name the section correctly. And I assume it can vary in case of different types/vendors.

Yes, GUID search was easy way for you to find it, and for this particular extract you want to extract the entire GUID (Setup) GUID or name for each thing is not always same in different BIOS, so anything mentioned here is only for this BIOS.
Some BIOS show GUID where name is, others only where I showed you in the image, all depends on how they created the BIOS

Hello,
after successfully cloning a PC (GUID, service Tag, and don't know yet what else) , I'm back .
The mistake: I backed up the bios from one Optiplex 3020, and flashed back the modified (with the added nvme driver) one to another one. I'm trying to flash more PC-s of the same type.
Now I'm thinking about only flashing the neccessary part (volume) of the BIOS (fptw64.exe offers such possibility with the -a and -l options). In this case the area is 0x0f0000 and ends at 0x4fffff. Can it work? Or even to flash the inserted module only? I know it sounds as a precision surgery done by a mad doctor
I tried to back up the area of the whole volume, I get: Error 26: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region.
While I was able to back up the area of the inserted module only.
update:
I experienced that I can backup the rom from address 0x200000 without any problem. What does that descriptor settings in the error mean and how to modify it?
Ok I realized that the BIOS area starts at 0x200000.

An other approach can be to find the location for the unique IDs and insert them to the rom file or write them back after flashing. I assume that the flashing tool provided by the manufacturer does in some of that ways. Do someone has experince with these GUID's?

@Lost_N_BIOS - May I have a question : Did you only inserted the NVME driver to the .rom, or did something extra modifications?
I've compared the o3020a18.rom and o3020a18M.rom files and saw additional differences in the last volume approximately at File GUID: 221D6760-4AC0-4C12-BA96-9C63E4D9C1C8 (PeiHwmInit).
I made a fresh bios backup, inserted the nvme driver, and after comapring the two rom images, there was only one difference where I expected. So is it enough to insert the driver or do the rom file need extra modifications?

Ahhh, I see what you're doing now! Maybe should have mentioned first, we could have blanked out service tags. What tool are you using for Service tag anyway, can you send me link (In PM is fine if you want).
I have one and need this for another user here, but reading it's "Read Me" file tonight I see it seems to mainly be mentioning laptops. So I'm not sure if it works on desktops or not.
If this is something you need, then I can send you version I have, then you test and see if it works, if not I'll try to find us desktop version if you do not have already.

I am not sure about using FPT how you mention, where is the service tag stored in the BIOS? I know you can use FPT to flash -bios region only, but that's probably containing the service tag.
If you know where it is we can blank (FF), then test and see if that works properly. If you don't know where it is, send me the service tag value for the BIOS dump you sent and I'll find it in BIOS and then blank and send back and you can test.

On your Error 26, are you using a flash programmer? If yes, dump description (FD) with FPT using this command >> FPTw -desc -d FD.bin and edit that following this guide (second spoiler shows what to FF) - [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing
Then flash it back via FPTw -desc -f FD.bin

If you have programmer, best to do this edit on entire BIOS file before flashing any of them, it's (FD region) right at the top of the BIOS usually.

I only inserted the NVME, not same one you did remember, and not same location you did previously either. So any changes you see may be either due to one of those (Not same NVME, or location).
Any changes to PeiHwmInit would be done by UEFITool on rebuild (Maybe it's checksum or location value, usually in the header)

Yes, I know should have telled the whole story, but I didn't think the serial numbers located in the bios region ... it was a surprise

Now the problem is that I don't have (didn't find) a tool, and don't know the location of the Service tag (and the serial number of the mainboard is also affected :) I found https://www.dell.com/community/Desktops-...10/td-p/4643926 refers the ftp://ftp.dell.com/utility/asset_a209.com and contains the description of the hidden functions of the utility, but the system did not allow to change the service tag, only the asset tag. I also tried it with removed BIOS lock and SMI lock.

Regarding FPT and denied access for the region below 0x200000, I realized that its not relevant, I don't need it. Using the -BIOS option has the same effect as -a 0x200000 -l 0x600000. I checked the modified ROM image: the volume that contains the NVME driver starts at offset 0x0f0000 and has a length of 0x410000 (ends at 0x4fffff). I had a theory that the service tag and/or the asset tag is not on the same volume as the drivers, which is now successfully tested with the asset tag:
I've made a fresh extract of the original BIOS region then changed the asset tag with the utility mentioned above. I've added the NVME driver to the image and extracted asis only the volume containing the new NVME driver, and finally flashed it with fptw -a 0x2f0000 -l 0x410000 -f vol.bin (maybe -l can be omitted?). And it works and the asset tag remain unchanged.

So now I have to find the Service tag location and/or figure out how to modify it.

I have one package, but surely could find another, of Dell DST/DSCTD (asset and service tag) which says laptops, but I don't know if it's only working on laptops or not, you will have to try and see. If it doesn't work for your model let me know, surely I can find desktop package too

Yes, that is the situation, the nvme is working fine. If I can change the service tag, I can restore the "overcloned" PC, and can make a final test of the flashing method, and be sure that it doesnt't affect the service tag.

I've tried these tools: SVCTAG, ASSET /S already, they are not working. May I give a try to the others.

The asset tag was empty, but for that I already have a tool to change (ASSET.COM).

The service tag is 9D8Q212. First I tried to find it according the method you showed me in case of BIOS lock and I found an offset 0x3a1. I used the "grub" tool to verify the content, change it / fill it with 0xff -> no success. Then I made a unicode search, and found it too many times but only in the first two volume of the rom image.

Good your BIOS NVME mod is working!

Sometimes the tag is duplicated many times, often in NVRAM area of the BIOS. I would try all of the EE-ERASE, and read into the SVCTAG.INF to see all the options it mentions, maybe something will catch your eye. And notice #3 info about EE_Erase, it says -forcetype may be needed?
In the end, I may need to find desktop version, going to look now, since there is another user here too getting a bunch of shipments of Dell's in so we need to find anyway.

CCTK and DDC is an option too, but since I do not have Dell systems here I am not sure how easy this is to use
https://www.dell.com/support/article/us/...it-cctk?lang=en
https://www.dell.com/support/article/us/...systems?lang=en

Also, see this, it's old now but may still work on some systems, second download link works I grabbed the file. Then read down for steps to run the service tag utility
https://community.spiceworks.com/how_to/...nspirion-laptop

Zitat

---

You CAN use the asset utility to change the service tag. It is an undocumented switch. run asset /s SERVICETAG, where SERVICETAG = the service tag you want to enter.
Works like a charm on Optiplex & Latitude.

---

Here is ATAG_A209 (Asset is included in the previously linked package I uploaded DSTCD, unsure if same or same version) I think all same files in above link too, same CD ISO, but I see ATAG_209 and Asset in CD.ISO are different sizes, so probably different versoins too
https://www.dell.com/support/home/us/en/...?driverid=h3mvy

I also read this about the ISO I uploaded previously, for using ASSET
Usage:
ASSET new_asset_tag Specify new asset tag
ASSET /d Delete asset tag
ASSET /o new_owner_tag Specify new owner tag (if applicable)
ASSET /o /d Delete owner tag (if applicable)
See also, all the Dell belong to YOU open in firefox or FTP app
http://ftp.us.dell.com/utility/

Breaking news: i did it
I have enough adventures for a novel now ... but in short:

I went back to the roots and started to compare the rom image extracted from the original bios update and the one extracted from the PC. I found that the first 4 volumes of the original image are almost empty (0xff), and the last 3 sections are almost identical. After some searching I finally found that the padding section (offset: 0x40000, length: 0x50000, volume 3 and volume 4 in the original image) of the extracted rom contains both the service tag and the SN only one time. So I modified that volume with the original service tag and SN, flashed it back and voila, everything is back, even the GUID of the machine (I read somewhere that it is derived from service tag).

So here is a method to modify the service tag and SN of a Dell Optiplex 3020:

0. Doing that you might lose warranty!
1. Extract the bios region (fpt -bios -d bios.rom) from the PC you want to change!
2. Open the image with UEFItool, locate the padding region in the middle, calculate it's offset and write it down (it's: 0x40000 - an easy method for calculation is to add the lengths of each preceding section, it is shown upon clicking the section)!
3. Extract the padding section asis (padding.bin)!
4. Open it with a hex-editor (eg: xwvi32), locate the service tag you want to modify with text search, and change it!
5. You can repeat step 4 with the SN also.
6. Save, and flash it back with fpt -a 0x240000 -l 0x50000 -f padding.bin (the bios region starts at 0x200000, add the offset of padding section. You may also need to unlock the BIOS for flashing, see the description in post #10 of this topic)!
7. Restart and enjoy!
8. You might want to revert the BIOS lock, to avoid security issues.

Thanks for posting your method, and good you solved it outside of the box without software.
Another way to flash your mod, put padding back in same way and same location you removed it from, then >>> FPTw -bios -f bios.rom

Yes, you're right, the method is easier as you suggested: there is no need for UEFItool, just (maybe search and) edit only the correct location of the image.
This time I just wanted to be sure that I don't modify any other section, and wrote down the steps before I forget it.

Yes, that too, no need to extract if it's not in compressed section, you can probably direct hex edit at location you know is the one.
All the others toward beginning of BIOS, are what's stored I NVRAM I think, you can extract NVRAM section with UEFITool NE Alpha and see all the times they are stored in there, but most of that is like a "log" file so I think they can be ignored in there.
Or you could use hex and find/replace all in one action with a proper hex editor with this function

Just an info regarding the descriptor lock discussed in post #19: I found that for Dell Optiplex 3020 it can be easily unlocked with the service mode jumper on the mainboard (if you have physical access :). After installing and power cycling the 0x0-0x1fffff region is readable.

May I have another question? Do you have any deeper knowledge about UEFI variables? I understood in case of BIOS lock and SMI lock how to read/modify these variables with the setup_var command in the "grub" (i don't have better name for this) tool via memory offset. And I can list variables with lsefivar command. Are these the same things? And i saw that they have GUID too. Where are they stored (in flash)? Do you know any tool can be used to manipulate them directly from windows? Sorry for the many question, this whole UEFI topic is far more interesting than I thought, and I'm getting more and more thirsty ...

I always forget some boards have those jumpers!

I am not sure about lsefivar, if I need to find a setup_var to edit, I extract that module, or it's PE32 file, or it's Sub-GUID under PE32 with UEFITool, then get an IFR output with universal IFR extractor. From there, search for the setting you want to change and then you'll find it's variable to use.
They can't really be edited from windows that I know of, but you can edit them in the actual module and put back into the BIOS and flash it (Like change default disable to default enabled).
https://github.com/LongSoft/UEFITool
https://github.com/LongSoft/Universal-IFR-Extractor

Here's a guide I wrote not long ago about how to unlock BIOS/SMI lock for some boards, reading over that will give you a general / perfect example of how to do what I described above.
[GUIDE] Grub Fix Intel FPT Error 368 - BIOS Lock Asus/Other Mod BIOS Flash

So now that you guys made progress, how do we go about changing the Dell splash logo some something else?

I currently have a 7010 optiplex and from what i read i need to extract the HDR file then what?