Since such invasive mods are rare, what I'm saying are only speculations. Keeping that in mind, I suggest you play around with Flash Image Tool (FITC) and its settings. Maybe the almost-same Toshiba model with HM76 has some small differences at the ME firmware which are FITC configurable. Generally, don't flash firmware which was configured with HM70 SKU profile selected at FITC as the latter is able to automatically grey out options which are not relevant to certain chipsets. If the model with HM76 is the same, take its ME firmware and clean that instead, then flash it at your modded HM76 system. If it's not the same (apart from chipset), then do it manually. Take the HM70 ME and compare with Toshiba's equivalent HM76 to spot any differences that might be relevant to your problem.
This problem is not ME related. Have you asked ASUS on how you can set these "the official way"? I'm curious as to what their answer will be. Other than that, you can use CodeRush's FD44Editor to edit those fields and reflash the BIOS via ASUS BIOS Flashback. Also, for future reference, don't attach directly .txt files as they cannot be opened due to a forum bug. Compress them first in a zip or rar file.
Zitat von atomota im Beitrag #2773Off the top of your head, whats the latest and best tool to open the bios and look at what versions of everything comes with it? Could you link or point me?
UEFI BIOS Updater (need to search elsewhere for the last version for now) but that's not relevant to this topic.
I don't think this is related to ME. Even your old chipset & bios caused the same issue. The cleanup guide has instructions at the last step to verify if all settings were properly transferred (xml comparison). If you see that all the settings are correct, I would try to check the settings of the almost-same Toshiba model which came with HM76 from the factory. Maybe you need to adjust some setting due to the different chipset. Apart from these, does that device work under a different operating system such as Linux? If none of these work, I assume the problem is hardware related.
Sometimes they can but only if the OEM has such tools and got leaked etc. For your Dell system you'll have to do it manually I guess. I see that GPIO33 is at the Audio chip (IDT 92HD71B7), which pin exactly not sure though.
Zitat von WinDrop im Beitrag #5On the post you linked me to it says that sometimes reading bios can fail if it hasn't been desoldered it can fail as the USB programmer will have to power up half of the motherboard. Could this be my case?
If you are reading while it's connected then maybe that's why. As you can see from the replies of that post, I had no luck while it was soldered as well. Have you tried to dump via software tools? For example via Flash Programming Tool (fptw -f spi.bin) etc.
The ME4 tools are old and may have problems running at newer Windows OS. The DOS version will always work though if you cannot get the former to work. If "FPT -d spi.bin" command shows CPU Access Error or similar then your FD is locked indeed. You have a pre 6-series system so you are not looking for SDA_HDO of the audio chip but rather for GPIO33.
Yes, Flash Programming Tool (FPT) v4 which can be found at the ME thread. Or flashrom under Linux if that's your thing. Try if you can dump with these but if the Flash Descriptor is locked and does not allow read/write access to the ME region, you'll need an external flasher, soldering and so on.
You need to work on your system's SPI dump and not deal with Dell's executable or HDR file. If you can dump the full contents of the SPI chip then you can easily do whatever you want, including disabling the ME via ich9deblob or similar.
If you cannot even read/write to the chip then this problem is beyond ME. Either the chip is dying or the programmer (hardware, maybe the software?) is not capable of reading it. Try different software versions just in case they can allow you to consistently read/write the same data. Otherwise, the programmer may not be able to work with that chip. If none of these help, you may need to replace the chip as you already said. Bottom line: you need to figure out how to read/write to the chip before dealing with firmware such as BIOS or ME.
HP should have instructions on how to properly set the ME_Disable jumper and what tool to use to upgrade. For HP I always suggest users to use their own tools because they can be very weird with motherboard provisioning, at least at their laptops. Since the ME_Disable jumper exists and HP provides a full SPI image at their BIOS releases, you can use a 3rd party (Intel) tool to quickly get the job done. Before that, try contacting their support to ask them how to transposition from ME7 to ME8 via their latest BIOS. If they do not care, we can use the 3rd party tool with the full SPI image from HP.
I'm glad this community could be of help and that the problem is solved. Now you can use again those two systems which were previously collecting dust. Thank you very much for your donation, we highly appreciate it. Enjoy.
Initially you were using Python 2.x at a Python 3.x script, plus you were missing the pypiwin32 dependency of Lordkag's Extractor (you can use the PyWin32 220 you installed manually instead). Afterwards, you run the wrong batch script. I have improved the instructions provided here, please follow them and you should successfully extract the HDR file.
Zitat von aletib im Beitrag #1- The BIOS region of the actual EPROM content is 6MB while T5600A12 is 10MB so nothing that can be simply swapped. And it doesn't even correspond to the total 12MB
File T5600A12 is a Dell HDR file which consists of various sections (BIOS, EC, ME etc). Once you extract it, as explained here, you can take file T5600A12_section1_A.12 which is the stock A12 Dell BIOS and it is exactly 6MB and thus can be used as a replacement at UEFITool and your dump. It can be swapped, you just need to first extract the ~10MB Dell HDR file to its components.
Zitat von aletib im Beitrag #1- If I open T5600A12 in UEFITOOL it contains only a BIOS region (no DESC, PDR, GbE or ME) which has 5 volumes (+2 padding regions)
Same as above, Dell HDR needs to be extracted first. Don't just input at at UEFITool without processing it first. You're supposed to extract it and then take the BIOS and replace at your own dump using UEFITool.
Zitat von aletib im Beitrag #1The only utility I've found able to build a split of 8+4MB is Intel's Flash Image Tool (and guess what? they're not sequential: the data is distribute like byte 1 and 2 on big eprom and byte 3 on small eprom).
What do you mean by that? The common structure at such dual chip implementations is always in order and the BIOS gets cut and continues to the 2nd smaller one. For example the first 8MB chip should have FD (4KB) + PDR (4KB) + GbE (16KB) + ME (5.97MB) + BIOS (first 2MB) and the second 4MB chip has the rest of the BIOS (last 4MB). The data are sequential with only BIOS getting cut between the two chips. If you have two dumps (8MB + 4MB) you can literally just merge them and create a new full 12MB SPI image and then use it at FITC or FPT. FPT is capable of automatically detecting the two chips and flash a full 12MB SPI image to both of them as I described above.
Zitat von aletib im Beitrag #1Personal assumptions (no proof in my findings to support it, it just make sense to me):
There is no free space at the two SPI chips as I explained above. The hot swap method wouldn't work unless you replaced both 8MB + 4MB chips since the BIOS is situated at both of them.
Yes there are differences which are mentioned at the first post briefly. Doesn't matter though, that decision is hardware and OEM, not user related. If you have Consumer you update to Consumer, same for whoever has Corporate. As for driver, I only keep the latest here. I don't know what guide you are referring to but if people want to keep older versions that's totally up to them.