Zitat

---

I can't help with the BIOS files, unless you have a programmer to program in the PRR unlocked BIOS region. I'll grab the file at PM though, and see if I can find the lock, go ahead and order yourself a CH341A + SOIC8 test clip with cable, let me know if you need links.

---

I need to learn and study about this new technique which is exiting. Hope I will get it.By the way I have very less time to physically presents at that PC, as it is not available at my home location.

Zitat

---

* edit - sorry, I didn't mention before, maybe because I didn't have your BIOS? If I did already, then I forgot to look. Aside from PRR lock, this BIOS also have BIOS Lock enabled, which you can disable following this guide (Start at step 5-6, I'll give you variable to use below)
[GUIDE] Grub Fix Intel FPT Error 368 - BIOS Lock Asus/Other Mod BIOS Flash
Alt boot to grub when no boot to EFI on exit page - [Help needed] Hidden Advanced menu Bios HP Z1 J52_0274.BIN (2)
BIOS Lock variable for you to use >> 0xA53
Rename .efi file to >> Shell.efi (Or if you do not see the "Launch EFI Shell from USB drives" inside "Boot" menu section, then follow second link above method instead)
At grub prompt >> setup_var 0xA53 0x0

---

I keep focusing in to it. I will keep update more posts if need more help

Zitat

---

This is Asus BIOS, strange to see PRR lock enabled! Did you try the sleep mod test method I mentioned? If not, or if you did already, unlock BIOS lock first and then try again (This change will stick until you reflash some other BIOS)

---

I did not but that will be my next test about bios modding.

Zitat

---

I checked the BIOS, Flash Protection Range Registers (FPRR) is disabled at both modes (Fail safe and optimal), as suspected for Asus.
So I think the issue may be caused by not disabling BIOS Lock first. Also, make sure you are using the correct and latest FPT from the ME System Tools package that matches your ME FW Version.

---

Ran hwinfo and got that result

Intel ME Version:12.0, Build 1062
Intel ME FITC Version:12.0, Build 1063
 

by following this result, I using "Intel CSME System Tools v12 r14" its that correct for this motherboard?

hello can i run this command "At grub prompt >> setup_var 0xA53 0x0" with in windows without need to boot from USB efi? maybe not or is there any other way to do this remotly?

due to job purpose, I am currently away from this pc :(

Yes, that is correct ME System tools package for your ME FW Type

No, to the grub stuff you have to be in the presence of the board, like doing stuff in DOS or within the BIOS, you have to be at the computer

alright getting back to Dell bios model : XPS 8930
After successfully flashed and verified the modded file in to -Bios regios only for this model, it looks ok, BUT when I rebooting the PC, All modded option resetting back to its previous way :(
So looks like it successfully modding the bios region but not saving the settings in the bios for permanently.
Do i need to apply special fpt command for save the settings permanently?

that what showing when i using fpt -i command

Reading HSFSTS register... Flash Descriptor: Valid
 
    --- Flash Devices Found ---
    GD25B128C    ID:0xC84018    Size: 16384KB (131072Kb)
 
        --- Flash Image Information --
        Signature: VALID
        Number of Flash Components: 1
                Component 1 - 16384KB (131072Kb)
        Regions:
                DESC     - Base: 0x00000000, Limit: 0x00000FFF
                BIOS     - Base: 0x00800000, Limit: 0x00FFFFFF
                CSME     - Base: 0x00001000, Limit: 0x007FFFFF
                GbE      - Not present
                PDR      - Not present
                EC       - Not present
        Master Region Access:
                CPU/BIOS - ID: 0x00, Read: 0x00F, Write: 0x00A
                ME       - ID: 0x00, Read: 0x00D, Write: 0x004
                GbE      - ID: 0x00, Read: 0x009, Write: 0x008
                EC       - ID: 0x00, Read: 0x101, Write: 0x100
 
Total Accessible SPI Memory: 16384KB, Total Installed SPI Memory: 16384KB
 
FPT Operation Successful.
 

@superb123 - I am not sure what you are writing to the BIOS, using what command, and what options are your referring to and how/with what are you changing them from/to?
It sounds like a failed BIOS mod, meaning your not changing things in a way that works, but I'm not sure what your changing, or how etc.

The FPT info you show above has nothing to do with BIOS settings/anything you can flash into the BIOS region and expect a change made either, so that adds to my confusion here (That only shows FD Flash Descriptor info, unless you meant to show me that for some reason)
If you write BIOS region using FPT, and it allows it, then write is made 100% as the file you gave it, if your blocked from writing to the BIOS region FPT operation will fail and give you error. Please dump your FD and send to me, in case I need to clarify anything on next reply >> FPTw.exe -desc -d fd.bin

once again pc rebooted and it restoring back to its default bios settings after successfully flashed modded bios and verified.
I can see flashing the DESC region and ME region not possible because those are write protected. it can Only flash(luckily) BIOS region only BUT unluckily Bios flashing not saving permanently, bios all modify change values automatically restoring back to default after PC reboot.
maybe NVRAM reset needed but i don't know how.

I going to PM those files.

EDIt*
another interesting thing i found
When just dumping bios using fpt -d bios.bin and verifying it with current bios setting using fpt -verify bios.bin ,it shows "RESULT: The data is identical"

But again after few minutes later when I verifying the bios.bin with fpt -verify bios.bin , it shows "Error 381: Data verify mismatch found"

Yes, especially FD cannot be written via software unless you first pinmod the board or your board has FD/FDO/ME/Service 2pin jumper somewhere on the board, check everywhere and don't forget to look all around the memory slots too.
BIOS region is generally unlocked for writing in the FD controls, but sometimes other BIOS Locks can prevent flashing in a BIOS region until those are circumvented too (BIOS Lock, FPRR lock etc)

Every time you dump BIOS will be changed due to checksums, NVRAM Data changes, time/date stamps etc.

You are correct, some changes may be needed to be done in NVRAM instead of setup, but I'm still not sure what changes you are making and or how you are seeing they are not being applied.
Do you see what I mean? You're not explaining your attempted BIOS mods, so I still cannot check anything to see if what your doing is correct way to do it, or you need to use some other method.
I'll grab your files in PM, thanks. But nothing I can do until you give more details on what your trying to do, how you're doing it, and how your confirming it's not applying etc.

Once you do all that, I will move all this discussion to it's own thread, since none of this has anything to do with extracting BIOS from Dell EXE I'll tag you so you can find it easily once I do that @superb123

Finally I had a chance to physically present at AMI Apto V (which I left due to job purpose) and used usb grub boot technique and followed this command "setup_var 0xA53 0x0" and ITS WORKS!!!
Now I can flash only the bios region which was locked.
Well do you have 32 bit version of bootx64.efi ? I tried to use another pc which is 32 bit pc but this bootx64.efi is not working. as far as i know, need bootia32.efi for 32bit machine.do you have bootia32.efi bios unlocker version script?

for /GAN technique,I used it to another pc(test pc), after /gan applied, bios runs ok when pc restart BUT when I shutting it down and turning on, a blank screen showing on screen and hang.Do you know how to prevent it and what is the issue of it?

how is it "not working" on the x64 system? you may simply need to rename it to another name, not all systems use same name
And some systems without exit to shell on exit page you need to use different method to get to grub, which I outline messily here Alt boot to grub when no boot to EFI on exit page - [Help needed] Hidden Advanced menu Bios HP Z1 J52_0274.BIN (2)

/GAN is only for certain systems, and certainly not APTIO V systems (mainly V3 and some V4 BIOS) - best to never use it when there is other update methods that will work instead. Sounds like it's bricked, hopefully you can recover it, once you do don't use /GAN on it anymore.
Or, could also be you flashed in a broken BIOS? Hard to know without seeing the stock and mod BIOS, but /GAN is very risky and should only be used on old BIOS

Zitat

---

how is it "not working" on the x64 system?

---

no no I am talking about "not working" on the x86 system. that bootx64.efi file is for x64 system, I have another pc which is x86(32 bit) and that file bootx64.efi is not running there.
Do you have x86 compile version of that bios unlocker efi file?

for problem about /GAN, it actually erase everything from first to last and /GAN won't allow us to write particular region only. i don't know if anyone knows good method about safely use /GAN
anybody?

I understood you meant that, but I mean how is it "not working" What do you see, some error, nothing happens, how are you trying to boot to it? Try the way I linked above instead.
BIOS is generally not x64 or x86, but to answer you, no, I don't have any 32bit shell that will boot to grub that has a setup_var usage in it, I've never seen anyone have to use or request such a thing.
Bootx64 is just the name "That other BIOS" wants so I told you to rename it to that, some boards want it named Shell.efi instead (works fine in all manners I've ever seen), rename it and use the method I linked above, you should be fine.

I found you this in Google - https://github.com/holoto/efi_shell_flas...er/README_en.md
The described downloads are on this page - https://github.com/holoto/efi_shell_flash_bios (Sounds like you'll want A32.efi afu latest 32-bit version of EFI or A32.4.efi afu 32-bit EFI version (v4))
You will still need to follow the method I linked above, where I have image example of how I setup a USB when BIOS did not have "exit to shell" or similar on the exit page

I know how /GAN works, and it's not meant for your BIOS, as mentioned. /GAN can be safely used on V3 BIOS (AMIBIOS8) or some Aptio IV BIOS< but it's far from ideal there because there is other safer methods from Aptio IV onward
Such as this method, download the package to get the AFU, then follow last spoiler for method to flash - https://linustechtips.com/main/topic/592...r-motherboards/
Or, better than that, if it's Intel based, FPT dump, then edit, then reflash (BIOS region only)

help me. i want to extract dell 8MB bios .i have use a few ways but can not

@TranNamComputer - Link to BIOS or name of model would really help. I've moved your post to the main Dell extract BIOS thread, in this thread, there is several tools and methods linked/outlined, to help you extract BIOS.
If this is to recover motherboard with flash programmer, normally you cannot extract BIOS from EXE and write to chip, it need to be built from other dump and or extraction from HDR

Additionally, be sure to double check the motherboard, many Dell's have two BIOS chips and this is not simply a backup copy on the second chip, but it's a split file not at an even place so you must write both chips at same time from a split file.
Often, this is 2MB+4MB (So 6MB BIOS), or 8MB+4MB (So 12MB BIOS)

Finally I managed to boot efi after correction to EFI/BOOT/bootx64.efi.Thanks for clarification about it.
I will update more result about dell bios progress. thanks once again

Nevermind.