hi all after lots of reading and help from people on here i managed to dump bios with pi and soci clip i have no problem getting my fd unlocked or any other locks off now i have modded the mb to make the service pins usable.
my issue is every time i flash bios back even with minimal changes - remove microcode for the Haswell, enable overclocking feature/overclock lock, i tried to enable a few bios features but that never works even after changing to user,
i cant get past dell recovery logo just hanges and crashes but i can get into bios and f12 boot menu
the procedure i use is
power off pc
2.unplug pc attach soci clip
3.conect soci to pi
4.power pi up
5.flash chip now errors
6.turn pi off before removing soci clip
8.plug pc back in
am i missing something in my procedures.
i reverted to the latest dell bios A34 and want to try again.
i few places i have read the smbios version 2.8 has been leaving user with the same boot loop problem can anyone shed some light on this if possible.
How are you “touching” those features? AMIBCP tool?
Are you modding an original dell bios update file, a full spi backup or a bios region?
AMIBCP wont work on all modern Aptio V bioses as it was in Aptio IV, thats why you can see a lot of users that must use RU/IFR extract tool and hex edit the variables/strings.
This is due NVRAM DEFAULTS and other modelas besides the SETUP, this must be done with RU/IFR extract tool and edited. The strange part is only modding the mcodes, your issue still persists…
Its better to work on a bios region and use the FPT tool to flash only the bios region, not touching other regions.
EDIT: I said Bios_region only, not the full spi dump. This dump has ACM/RSA…this is not welcome in modding.
Try just the mcodes with AMI MMtool or UEFItool besides UBU, on the region.
According to the ME of your system:
Dumping: FPT -bios -d biosreg.bin
Flashing: FPT -bios -f biosreg_mod.bin
This is not an easy bios to mod…too much Dell in it, in structure/modules/NVRams…
EDIT: Ok then you understood it… but here it gives 8 388 kb not 8 192…
HEX edit was not ment to mcodes, that was used in older 1/2/4Mb bioses.
I opened the file with MMTool and UEFI…too much of Dell DXE/PEI in it, not a bios to touch myself, sry.
yes full spidump of orignal dell bios read advise to always use orignal bios before flash
yes i was enabling features in AMIBCP thanks for the info it wont work on Aptio V wont use anymore
i have tried the RU and Setup_var
RU changes vales but found i get maybe 5 mins in the program before it crashes and pc restarts
modgrub it changes the values but some wont change
Setup_Var_CV IntelSetup 0xEB is my bios lock varible set it 0x0 to disable but doesn’t seam to work.
this is the bios dump it got from fptw if i editor this bios and flash this back either with fptw or spi flasher?
not very good with hex editiing will read more about it now 7810-bios.rar (3.7 MB)
Im confused what you mean bios region when i do full dump the file is 16384kb the dump i did was fptw -d 7810-bios.bin -bios
and it game me the 8192kb bios file.
I have the mcodes extracted but been looking into what you said about hex editing.
this is what im trying to read up on today as im lost so far
So I took the bios region extracted the mcodes with mmtool shut down Pc
Service mode jumped on
Fptw -f biosregion -bios
It worked all verified I flashed it first with rewrite
Cleared cmos load default bios
Still stuck on preparing dell automatic recovery and then reboots
Are you still fighting with that Dell 7810? If so why new posts… users will see it (The origianl post) when updated or edited and this way a new user can get a clear picture of the initial issue else is gonna ask you again the background of it…
the reason asking is because i dumped the bios from fresh dell via flashrom on my pi with
–wp-disable got the bios only removed the microcode checked on me analiser all looked good reflashed back it then
Verifying flash… FAILED at 0x0001cd81! Expected=0x4e, Found=0x6e, failed byte count from 0x00000000-0x00ffffff: 0x1af Your flash chip is in an unknown state…
so erase reflash this time all verfied no errors
power off unclip.
MESPILOCK failed ME FW VERSION downgrade failed
Error sending End of Post message to ME
i tried to run dell bios flash update from F12 menu it deosnt load
so i did the clean dumped intel engine guide reflashed via flashrom but still errors on boot cant get into bios flash upgrade.
that’s why i was asking was trying to figure it out on my own but i cant seam to do it.
So I managed to get dos bootable usb flashed dell original bios back checked the me same FW but still didn’t clear errors and take ages to boot what would your suggestions be now
ok so is F12 back to normal again or you have this again?: MESPILOCK failed ME FW VERSION downgrade failed
Error sending End of Post message to ME
The “ages to boot” usually is an issue in the ME FW image of the system and most users get it solved by the procedure you did before, cleaning the ME following the guide on this forum.
There could be issues of NVRAM and/or Dell specific system ids/tags/security chip…these systems/motherboards are not easy to work with…
Gonna be honest with you, my in depth knowledge in this recovers of this kind of motherboards is limited.
EDIT: I dont want to point out to the SPI chip but… ive seen a bit of all.
There are 2 methods to clean, using full spi dump or just ME dump…try both cleaning methods.
I found that ME issue on many 100 series motherboards when they came out, cleaning the ME always fixed.
Hey buddy can you give your opinion in this user issue, thank you.
hi sorry about different threads can i merge them all to one
this was a full spi read in windows fptw tonight after dell fw bios flash it didnt flash correctly
not sure what i should try.
and thank you im learning as i go fullspi.rar (6.5 MB)
what im trying to do is remove the microcode and unlock over clocking i can only ever seam to get one or the other and when i try to go for both i end up messing up.
EDIT: If cant see nothing in the device manager the driver fails to install as there no device present, the ME is disable, did you?
You need to put the machine back on normal, NOT in Service mode, i guess, i cant remember all those peculiar details/methods for every fxxxxx machines around the world…
And users in order to help could enjoy some capture screens running the tools/errors/device manager etc…helps a lot and saves time and brains you know…
When a user says oh can see this or that, we really dont know if he knows what to search for or his
knowledge of it…
EDIT: humm i guess that… better no comments. Good luck.