I can only tell you try my file above, it should be working too. Sniffnet 1.1.1 UEFITool A65 / 0.28.0 Light Switch 2.3 Comment Rules & Etiquette - We welcome all comments from our readers, but any comment section requires some moderation. He put image in same exact location, so not sure what he meant by moving things, or whatever that Dell comment meant? Unsure, he’d have to give you specifics. * Edit - I checked his file, looks similar to my edit, padding file remains so should be bootable as I expect mine is above too, but he’s changed some NRAM (So probably used some of stock BIOS instead of your dump, or reset some of the NVRAM for some reason?) I will look at his edit, but if you want to know what he meant by that you’ll have to ask him for more specific detail as it’s written I don’t understand what he meant there Needs to Dell the service code? Is that translation issues, or what Doesn’t make sense to me. Try my file above, I probably did a bunch of edits while you were already here reading/replying.
#UEFITOOL REPLACE BODY MOD#
Might as well pass it over Nothing done here except replace body with your mod image using UEFITool V25 instead of V26, should be OK now unless Bootguard is causing the problems If you can’t get it to remain let me know, I will rebuild BIOS for you (I redid already in UEFITool V25, it’s OK)
#UEFITOOL REPLACE BODY UPDATE#
***** Edit 99 - This padding file issue is probably the main problem, I see this brick BIOS often for users when they update microcodes. What’s going on there, why did you send it to me named PNG? So you renamed a PNG to BMP, or what? That’s going to fail no matter what - Ohh, I see, I renamed it to BMP and it opens properly, and I checked it in hex and it’s actual BMP and looks OK in GIMP too. This file can’t be opened or parsed in photoshop because of the file contents and file format do not match. Issue! Checking the images 1.bmp vs mod.bmp, my first comment above is as suspected. If it does, then test the BIOS, it may be fine! If not, and padding message is still there after edit, then maybe other issues we’ll have to figure out. So, try the edit again, but use UEFITool ver 25, and see if that padding remains. This displays as Non-UEFI Data found in Pad file message in UEFITool NE Notice in the image 0 you linked, see bottom of UEFITool where is says padding will be destroyed after modifications, when you see this you want it to remain. *** Ohh! I see the issue possibly right away, without looking at any of your files. I’ll check all this out and get back to you soon! Do you happen to have a 80h PCI debug card? If yes, what debug error does it stall on, or show last before rebooting? Or, copy all contents from the Flash Programming Tool \ DOS folder to the root of a USB Bootable disk and do the dump from DOS (FPT.exe -bios -d biosreg.bin) If you are stuck on Win10 and cannot easily get command prompt, and method I mentioned above does not work for you, here is some links that should help If both are disabled then Bootguard cannot be active currently, if both are enabled and the rest of the BIOS/ME FW are setup properly then bootguard is enabled and you can’t edit BIOS You’re welcome!! What does this mean > 1.m.png(1.m.bmp) > MEInfoWin.exe -verboseĬheck the end of this report, we’re looking at Measured & Verified Boot, on the left/FPF side.
0 kommentar(er)
