@lfb6 , @Lost_N_BIOS , I only disconnected the CMOS battery and the main battery, didn't disconnect anything else before the first read. I don't touch the whole setup while reading. Before reading, system was booting, all was good. After reconnecting the battery and CMOS, I got the brick. DELL is supposedly sending me a final response tomorrow whether the warranty will be valid, so fingers crossed.

using the software suggested by Lost, 25 SPI FLASH. Using this version, the verification step doesn't fail indeed, says chip and dump are the same. I checked the MD5 hash of the new files and they are different from the first reads I got with ASProgrammer, so I'm attaching the new dumps here

72F chip ID is detected as C2201817, used 16 MByte dump
https://drive.google.com/file/d/1SCyRLJM...iew?usp=sharing

XMC chip ID is 20701716, used 8 MByte dump
https://drive.google.com/file/d/1V8QREHa...iew?usp=sharing

I disconnected the CH341 from my computer while swapping the clip from one chip to the other, so I don't think it could have shorted anything on the board except if the 5V indeed fried the chips cause I didn't check if they were hot during the read. This is what concerns me the most right now since this programmer came from China for 6 dollars, so... I'm afraid what was supposed to be cheap became a very expensive problem.

Regarding Lost's links, that's not same computer, there's something called DELL Latitude Precision 3510 which was a workstation using 7th generation processors, mine is called the NEW Latitude 3510, which uses a U processor, it's an i5 10210U.

Now I don't know anything about this ME firmware, but I checked another identical computer for that using hwinfo (my whole team got the same computer), shows as

ME Version: build 1165, hotfix 37
Recovery Version: build 1165, hotfix 37
FITC Version: build 1205, hotfix 11

I just cannot guarantee the bios version is the same, unfortunately.

@lfb6 so this ME firmware not being configured could stop the computer from booting? Considering the 5V ordeal didn't fry the chips, is there any way of reconfiguring this if needed?

Thank you both for your help

@jacoghi - What is second chip full ID, so I can tell you what software/version is best to use for this, it may not be the v1.31(1.4) (CH341AFree) one I mentioned for the 72F chip.

5V would not fry the chip, I've used $3 programmer like that all the time on 100's of boards. The chips do not get hot under normal usages here, when I mentioned that it was in regards to/only happens if something is backwards (ie hard short)
Indeed, the files I linked may all be incorrect, I was only looking with Latitude 3510 as model, it would be best if you gave me the motherboard name/ID printed on the PCB

If you have another identical computer, dump it's ME FW and then lfb6 can use it here to make you a fixed BIOS to program back to both chips on the messed up board.
This can be done with software, so no programmer concerns, if this system has a ME/FDo/Management/Service jumper, look over the entire PCB for 2-3 pin jumper with label like that near it.
If you find one, then put jumper on, reboot to windows three times, then download ME System tools 14.0.20+ from section C.2 in this thread - Intel Management Engine: Drivers, Firmware & System Tools

Then from ADMIN CMD Prompt, run the following and send lfb6 that file >> FPTw.exe -me -d me.bin (Fixed!)
If you do not know how to run Admin CMD Prompt, here, merge this to registry, reboot, and then you can right click anywhere in the folder that contains the FPTw.exe and choose "Open CMD Prompt here as Admin"
http://s000.tinyupload.com/index.php?fil...134606820377175

Also, for lfb6, run these commands with FPT on the other system as well, and send him above + these files
FPTw.exe -ec -d ec.bin
FPTw.exe -desc -d fd.bin
FPTw.exe -bios -d biosreg.bin

ME FW drivers must be installed first as well, or you can do all this from UEFI Shell if you know how, using the EFI Shell version (no driver needed there, nor Admin CMD prompt

Once those two dumps you linked are appended, except for "Unconfigured" the only ME FW error MEA gives is >>
Skipped MFS partition at 0x107000, unrecognizable format!

Usually ME FW can be 100% corrupt, or missing, and system will still boot, but not always, so it's hard to say if this is the cause of the issue here, or if BIOS is messed up some too.
Is this the BIOS exe name from Dell you would use for this model >> Latitude_3410_3510_1.3.0.exe >> If not, please link me to your BIOS download page

You're welcome, hopefully lfb6 can help you get this sorted out!!

@jacoghi Dont run this command on any other computer

Zitat von Lost_N_BIOS im Beitrag #17

---

....Then from ADMIN CMD Prompt, run the following and send lfb6 that file >> FPTw.exe -me -f me.bin....

---

@lfb6 - Fixing, thanks for the catch! No file there as source for me.bin, so no mistake could be made, only file not found error would appear as you mentioned.
But yes, lucky catch just in case write would be allowed - locked FD for ME anyway though so nothing could happen

@jacoghi - What is model name printed on the motherboard PCB, thanks!

@jacoghi Regarding your new dump:

There's just one chunk in the region of the EC firmware that's not read:


But it's not EC firmware itself, that's identical with the EC firmware of the Dell update package.

EC fw block fro 1000- 101000
EC fw 1.03 at 1000
EC fw 1.01 at 41000
EC fw 1.03 at 81000
C1000: Something I can't identify, see ubo zip, the part not read is the last block of this area.

The dump of the ME region is identical and the bios region is identical, too.

That leaves us at:
- There's an uncertainity regarding your EC firmware, but I assume that a missing block when reading first time and it's OK
- Your ME is corrupted and that needs to be fixed anyway. That could be the reason for system not starting, especially if BootGuard is configured.

So I'd like you to read the bios of an identical machine as written by Lost_N_BIOS. I don't repeat the complete description here, just the commands:

Dump the complete firmware
fptw??.exe -d bios.bin

This will give an error if you didn't find a jumper as described by Lost_N_Bios, so if you don't success continue with the single regions:

FPTw.exe -desc -d fd.bin
FPTw.exe -ec -d ec.bin
FPTw.exe -bios -d biosreg.bin

and let's see what we get.

@Lost_N_BIOS the complete chip ID is XMC QH64AHIG (XM25QH64AHIG), the motherboard has the inscription:

MOCKINGBIRD-L 19746-1 YJCJD$CA

https://www.dell.com/support/home/en-ca/...-laptop/drivers

That's the DELL webpage containing everything for the laptop.

@lfb6, I unfortunately cannot open the other machine, since it's not mine. Can I do those steps without having to plug the programmer?

@jacoghi Yes, but you have to execute the commands as an administrator.

@lfb6, I'll get it done tomorrow for sure. I'll also look for the aforementioned jumper but I don't remember seeing anything like it anywhere on the board, I'm attaching a picture of the MB for reference.

For XMC QH64AHIG / XM25QH64AHIG try using ID GD25Q64 and Colibri or ASprogrammer - Make dump using this, if it matches what you used before, then read is OK, but for write back, I would use one of these as this is confirmed working.
Thanks for the board ID, I asked because I am talking to a guy at badcaps forum, maybe he can find us a good dump to use for comparison, fixing etc.
Thanks, that is the BIOS page I downloaded from, but I grabbed an older version is all (1.3.0)

Yes, FPT stuff is all software
FPTw.exe -me -d me.bin << needs added to the list above
EC dump will fail, I just noticed FD has read/write = NO on EC

llfb6 >> ME FW not covered by boot guard, only 8C8CE578-8A3D-4F1C-9935-896185C32DD3 + Last BIOS volume (8C8CE578-8A3D-4F1C-9935-896185C32DD3)

* Edit - @lfb6
foulou0238 over at badcaps forum said he will send dump from working system in a few days

Zitat von Lost_N_BIOS im Beitrag #24

---

... llfb6 >> ME FW not covered by boot guard, only 8C8CE578-8A3D-4F1C-9935-896185C32DD3 + Last BIOS volume (8C8CE578-8A3D-4F1C-9935-896185C32DD3)

* Edit - @lfb6
foulou0238 over at badcaps forum said he will send dump from working system in a few days

---

Yes, but ME Settings do not matter/apply, measured or verified boot would be set at the chipset level in the FPF fuses. Yes >> FVME = Verified + Measured Boot enabled, if violated = immediate shut down. This is set at chipset level
You could set No boot guard in ME FW and it would still be enabled due to key burned into chipset, so really, in systems where it's active like these Dells or HP etc, it's a waste if time for anything to be set in the ME FW
I would wait to do anything here, until you have a working ME FW dump, to clean/UPD/transfer over, then you only have to sort BIOS after that. ME FW from this dump cannot be used or fixed, ignore it as if it does not exist

I'll post the dump once he send it over

@lfb6 , @Lost_N_BIOS , I executed the commands:

-d fails,
Reading HSFSTS register... Flash Descriptor: Valid

--- Flash Devices Found ---
ID:0x207017 Size: 8192KB (65536Kb)
ID:0xEF4018 Size: 16384KB (131072Kb)


- Reading Flash [0x0000040] 0KB of 24576KB - 0 percent complete.
Error 185: FCERR is set. Hardware sequencing failed. Make sure that you have access to target flash area.

FPT Operation Failed.

-fd works
-ec fails with same error as above (Error 185: FCERR is set. Hardware sequencing failed. Make sure that you have access to target flash area.
)
-biosreg works
-me works

Files are here
https://drive.google.com/file/d/1Ct0jHS8...iew?usp=sharing

@jacoghi ME did work? That's great! Where are the dumped files FD, ME and bios?

@lfb6 , it succeeded, I understand. At least the command didn't result in any immediate errors. These are all coming from the fully working system, exact same specs.

Files are here:
https://drive.google.com/file/d/1Ct0jHS8...iew?usp=sharing

@jacoghi Easiest fix will be replacing the ME region with the working one from your colleagues system and try. Since the dumprd bios from the working system is identical except for NVRAM (expected) we continue with your old bios. Flash descriptor is identical, too, and EC firmware we don't have, but in your good read are 3 copies of Dell EC firmware in perfect order, so there's a good chance that the last piece in this area is OK, too.

Flash the file in 8MB.zip into the 8 MB chip. You can use the verify option of the flash- program, but in any case do in addition a separate read, store the file under a different name and compare it to the orginal file, they should be bitwise identical.

Since I left the bios unchanged I don't add the 16MB file.

If this does work, fine.

If not there's
- a slight chance for something in your EC firmware being wrong (we can't be 100% sure that it's OK at least) or
- maybe something in the NVRAM filesystem of the bios region being corrupted or
- there's a fault that's completely independant of the UEFI firmware....

(Even if Dell warranty will accept your case later this flash won't possibly damage the machine any further, if you work carefully. You opened it already and had the clip on that chips several times anyway.)