[b][/b]
[i][/i]
[u][/u]
[s][/s]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
smile
smile2
spook
alien
zunge
rose
shy
clown
devil
death
flash
sick
heart
idee
frage
blush
smokin
mad
sad
wink
frown
crazy
grin
hmm
laugh
mund
oh
rolling_eyes
lil
oh2
shocked
cool
[mail][/mail]
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
plutomaniac
Posts: 2424 | Points: -1 | Last online: 03.27.2017
Date registered
09.16.2014
Sex
not specified
    • plutomaniac has written a new post "Unknown ME Region" Yesterday

      FPT is Windows only. You can use flashrom under Linux.

    • plutomaniac has written a new post "Dell Precision M4400 bios modding. Bios mod AMT and Computrace?" Yesterday

      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.

    • plutomaniac has written a new post "Unknown ME Region" Yesterday

      Zitat von WinDrop im Beitrag #5
      On 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.

    • plutomaniac has written a new post "Dell Precision M4400 bios modding. Bios mod AMT and Computrace?" Yesterday

      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.

    • plutomaniac has written a new post "Dell Precision M4400 bios modding. Bios mod AMT and Computrace?" 03.26.2017

      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.

    • plutomaniac has written a new post "Unknown ME Region" 03.26.2017

      Try the software from this guide.

    • plutomaniac has written a new post "Dell Precision M4400 bios modding. Bios mod AMT and Computrace?" 03.26.2017

      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.

    • plutomaniac has written a new post "Unknown ME Region" 03.26.2017

      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.

    • plutomaniac has written a new post "HP Z420 Unable to upgrade ME Firmware to v8.1" 03.26.2017

      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.

    • plutomaniac has written a new post "HP Z420 Unable to upgrade ME Firmware to v8.1" 03.25.2017

      You cannot upgrade from ME7 to ME8 yourself. The latest BIOS from HP already has ME8. So first update the BIOS and only when you are at ME8 can you use FWUpdate to update ME8 to a newer version.

      [[File:Capture.PNG|none|fullsize]]

    • plutomaniac has written a new post "Reviving dead Dell Workstations with bricked BIOS" 03.23.2017

      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.

    • plutomaniac has written a new post "Reviving dead Dell Workstations with bricked BIOS" 03.23.2017

      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.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 03.22.2017
    • plutomaniac has written a new post "Reviving dead Dell Workstations with bricked BIOS" 03.22.2017

      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 #1
      The 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 #1
      Personal 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.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 03.21.2017

      Intel ME System Tools v11.6 r8

      @ ahzhi:

      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.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 03.21.2017

      @ yurikol:

      You cannot. Engine release notes are not public. Sometimes OEMs include some changelogs of their own but they list only some Intel fixes and others that are specific to their own firmware releases.

      @ atomota:

      Oh it is definitely BIOS. Things is, without a new ASUS BIOS, it can only be fixed (maybe temporarily if the BIOS is the problem, and yes I believe it is) by reflashing the SPI chip (ME+BIOS). That is not possible when the Flash Descriptor is locked and ASUS BIOS Flashback deals only with the BIOS region of the SPI chip. So either wait for a new BIOS which might solve the problem via BIOS Flashback or claim the warranty. I don't have anything else to add, everything else is up to ASUS. Thank you for keeping me updated though as to your support efforts.

      @ ahzhi:

      User acid96 already corrected you. Now read the first post to answer your questions, it's there for a reason.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 03.18.2017

      Intel ME 11.6 Corporate PCH-H Firmware v11.6.25.1229

      [[File:Capture.PNG|none|fullsize]]

      Intel ME System Tools v11.6 r7

      For PCH-LP 100/200-series users:

      It seems that PDM is possible at ME 11.6 firmware as well. There are 11.6 firmware which can be be YPDM and others which are NPDM. Intel has made things even more confusing at 11.6. If I had to guess, Intel releases each 11.6 kit (firmware, drivers, tools, documentation) twice, one for SPT (100-series) and one for KBP (200-series) systems. At SPT, the LP firmware are distinguished between PDM and non-PDM which is good. However, the same happens at KBP kits but the PDM firmware are just a direct copy of the non-PDM ones. So I cannot trust firmware filenames anymore without knowing the kit they came from because a random firmware marked as "PDM" can be either truly PDM (SPT) or a copy of the equivalent non-PDM (KBP). Based on user reports, we also know that the exact same 11.6 LP firmware, regardless of whether it's PDM or not, can show different status at the MEInfo's FWStatusRegister3, depending on whether that system is affected by the PDM erratum or not. On top of that, it's impossible to determine whether a LP firmware is PDM or not by looking at its data because of a proprietary Huffman compression used at the place where such info is stored. So to sum up, we cannot rely on MEA (binary analysis), MEInfo (FWStatusRegister3) and Stock filenames from Intel Kits (unreliable). Thus, we cannot do anything without knowledgeable researchers who can find a way to decompress Huffman modules. It was done in the past (anything before ME11) by UnHuffME but I don't see any movement towards doing the same for ME11, unfortunately. Which leaves me with one option:

      All 11.6 PCH-LP firmware are tagged as Unknown PDM (UPDM) by MEA, database and repository. If we have both PDM and non-PDM variants of the same version and SKU, they are marked as UPDM1 and UPDM2. I've left the previous YPDM and NPDM marks at 11.0 firmware as back then it was a little easier to figure out what they were. These changes will be applied at the next version of MEA.

      [[File:Capture2.PNG|none|auto]]

      Last and certainly least, I won't post these 11.7 drivers at the first post at this point. Intel has apparently decided that yet another ME11 branch is a good idea. Until we know more, I advise all users to use 11.6 drivers only.

      @ atomota:

      No matter their support, a new BIOS for such a new board is a given. It's a matter of time. Fingers crossed that ASUS has already seen that problem elsewhere and knows that needs to be fixed.

    • plutomaniac has written a new post "BIOS Modding: Introduction and Preparations" 03.17.2017

      That executable has nothing to do with what I was saying above. It has an icon and doesn't include a HDR file. Usually it's easier to just run these executables and take the BIOS from the temp folder or wherever it extracts. In this case just get a11.bin from BIOS.BIZ.gz extracted file.

Recipient
plutomaniac
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor