I don't know the answer to your question. ME dumps are different because of the DATA (MFS/EFFS) section it has. That section is pre-configured by the OEM but is also adjusted by the ME during normal operation. It gets removed by me_cleaner and thus stock clocks and configuration are used until the ME is repaired.
Thank you but it's not needed. PDM is PCH-LP specific and only relevant to ME 11.0 firmware, not 11.6.
You already know you have 9.1 so get the latest of that branch. As for SKU, you can run FWUpdate tool with command "FWUpdLcl -save me.bin" and drop me.bin to MEA. You can find your SKU that way quickly.
Download the latest BIOS/SPI image from ASUS. Open the .CAP file with UEFITool and remove the AMI Capsule Header by extracting the Intel Image "as is". You should end up with an 8MB (0x800000) SPI image which can now be used with CH341A. Use FD44Editor on that image first and then flash it with CH341A. I don't now how FD44Editor works exactly, meaning what it expects as an input (full SPI or BIOS-only image) but if it works with a full SPI then use the previously mentioned 8MB one, otherwise extract the BIOS section of the 8MB image via UEFIStrip, add the info to it via FD44Editor and reinsert it at the 8MB image which should then be fed to CH341A.
What are you talking about? Since when we have been talking about "LSI" cards? There is no utility of "mine" mentioned anywhere above. We were neither discussing raid protocols or external card microcodes. You posted at the wrong thread...
Obviously you must not mess with it now that it is sold. However, you should not ask for help if you don't plan to test the outcome or even reply. It takes hours to do things like the above and it's not cool if it ends up being in vain. Some human understanding is proper, especially when the help is unconditionally free.
"the laptop not working data" makes no sense and lacks every bit of information we might need to help. Explain in detail what you did, why did you want to clear the ME in the first place and what is the problem. In detail.
So did memtest86 show errors? If you miss-configure the ME then it is very possible to see such weird things. Make sure you have the BIOS from ASRock and update the ME using FWUpdate, not by yourself. A properly updated ME won't cause any such issues, bad hardware can.
So you have a new board but the old RAM. Update the new board to the latest stock ASRock BIOS without any mods or alterations/updates. That excludes any issues at the BIOS and/or ME firmware. If you still see problems, the memory DIMMs are almost certainly bad. To test you can use memtest86.
No, you can post here. Enable the "SERVICE MODE" jumper on the board to be able to dump/reflash the SPI firmware. Use Flash Programming Tool with command "fptw -d me.bin -me", compress and attach the resulting me.bin fie here.
There are two steps for such Dell executables (no icon). First, you need to extract the HDR from the EXE using this Python2 script or alternatively PhoenixTool. Lately some newer EXE have appeared which require that move twice, meaning exe to compressed HDR and then again from compressed HDR to uncompressed HDR. Then the HDR needs to be extracted to its components. Use Lordkag's Extractor which can be found here. Just drag & drop the output HDR to Z.version.bat and enter "dellhdr" command. It requires Python3 installed and its installation directory must be inserted to the batch file first.