[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: 2581 | Points: -1 | Last online: 05.24.2017
Date registered
09.16.2014
Sex
not specified
    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" Yesterday

      Intel MEI Driver v11.7.0.1013 MEI-Only Installer
      Intel MEI Driver v11.7.0.1011 (Windows 8.x & Windows 10) INF
      Intel MEI Driver v11.7.0.1011 (Windows XP & Windows 7) INF
      Intel MEI v11.7.0.1013 for Corporate systems Drivers & Software


      Intel ME 11.7 Corporate PCH-H Firmware v11.7.0.1261

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

      Intel ME 11.7 Corporate PCH-LP Firmware v11.7.0.1261

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

      Intel ME 11.0 Consumer PCH-LP Firmware v11.0.26.3000

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

      Intel ME 10.0 1.5MB Firmware v10.0.55.3000

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

      Intel ME System Tools v11.0 r6

      Added OEM advisory from Toshiba regarding INTEL-SA-00075/CVE-2017-5689

    • plutomaniac has written a new post "Yoga 2 Pro shutdowns every 30 minutes" 05.22.2017

      Make sure you have downloaded the System Tools v9.5 from the ME thread and that you haven't deleted any files from Flash Image Tool folder. Otherwise, try to do everything from a folder path which has no Russian characters, just in case the problem is caused by that. As for the .cap file that MS provides, it is a full SPI image with an AMI Capsule Header at the top. If you remove the capsule (0x1000 bytes) you'll end up with a proper 16MB SPI image which can also be properly parsed by UEFITool. Since the ME region is found at the BIOS, MS does not provide a separate ME folder for the Surface Pro 2 like they do for other Surface models.

      You have two options, either extract the ME region (assumed clean) from MS BIOS and flash it directly via "fptw -f me.bin -me" command or follow the cleanup guide on your own SPI 16MB dump and flash the output via "fptw -f output.bin" command. In the latter case, of course you can also extract the cleaned ME region only from the output SPI and flash it via "fptw -f me.bin -me" command. Make sure the size is the same though.

    • plutomaniac has written a new post "Yoga 2 Pro shutdowns every 30 minutes" 05.22.2017

      Try what Ferrous suggested as the guide should work, you must be doing something wrong. As for the 3 files, MS keeps the ME firmware at a ME or similar folder at those .zip or .msi updates from their website. I think it is EXTR but I don't remember. Either way, you must use your own full SPI dump at the guide.

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

      That whole problem is irrelevant to ME. It should be a matter of performing a clear CMOS or resetting the BIOS NVRAM somehow, MEManuf is thus irrelevant. Maybe HP has implemented a check while BIOS updating/downgrading to check if the ME firmware of their own update is older that the currently flashed one but that does not have to do with the MEManuf errors which is what has been troubling you.

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

      You have confused everything and went into trouble for no reason. The system has no problem, none at all. Not before the update and not after. The BIOS downgrade is controlled by HP and it is very normal to not be able to downgrade to older versions due to security improvements. Such restrictions are imposed by HP and I've seen the "downgrade to earlier BIOS not allowed" or "supersedes all previous releases" notices at their BIOS changelogs very often. That feature has nothing to do with the ME and it has nothing to do with the recent update of said firmware. There is nothing special in this case.

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

      @ ArtZ:

      1. The firmware you saved via "FWUpdate -save" command is not customized by HP. You created an Update (UPD) image which is only usable with FWUpdate and does not contain any ME DATA, only generic ME CODE.

      2. Correct, that is rare unfortunately so that's why I mentioned it.

      3. There are also MEA pre-built binaries which can be found at Github > Releases section. If you are interested in building it though, regardless of what I just said, you should provide some more details about the errors at the ME Analyzer forum thread. A quick note: You need to use the PyInstaller 3 develop version as the master branch (3.2.1) does not support Python 3.6 yet. That's probably why you get errors.

      As I said for MEManuf, that error must have been there from before. It is very possible that some ISHC tests are not supported by OEM design. Everything is working just fine after the update so you can ignore that error or just use -NOISH.

      @ shivam94:

      The problem is not ME related then. Hopefully you'll find a solution.

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

      @ ArtZ:

      Your system does use ISHC and it seems to work just fine as indicated at MEInfo. Try a ME reset via Flash Programming Tool's command "fptw -greset" and try MEManuf again after the reboot. Otherwise, that MEManuf error must have been there from before, possibly some ISHC tests are not supported by OEM design.

      @ shivam94:

      The ME looks fine. Just in case, try a ME reset via Flash Programming Tool's command "fptw -greset". Otherwise, the problem is not ME related. Maybe at the BIOS or OS. Also, please don't tag me at this thread, I monitor it regardless.

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

      @ shivam94:

      Run the ME health tools (MEInfo & MEManuf) as explained at the first post and show the results.

      @ ArtZ:

      You've done your research before asking, good work. Does MEInfo show any extra details at the bottom which are ISHC related? Otherwise, ignore the ISHC error at MEManuf, you need -NOISC parameter. As for downgrading, check Version Control Number (VCN) at the first post to know why it won't work.

    • plutomaniac has written a new post "[Discussion] UBU Tool related Questions, Reports and Suggestions" 05.17.2017

      Zitat von Fischer im Beitrag #2973
      strange, it was my working-backup since years.
      With new "fresh" download from producer site UBU is working fine

      SoniX is right. That dump is completely broken. There are sections partially or fully missing, zero padding all over the place etc. Don't ever flash that image. Download the one from MSI instead.

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

      A lot more info is needed. Explain what happened in detail. What system do you have? What firmware did you pick? What tool did you use and of what version? What do you mean by "it doesn't work"? How did the flash process fail?

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

      That guide is dangerously wrong on many levels. The ME is not static firmware, it needs to be configured first for each system by the OEM via Intel's Flash Image Tool before deployment. So we never replace a dumped SPI image with a stock (RGN as I call them) ME region, which is what is provided at the ME or Repositories threads, without prior configuration. Searching for the ME region via the string "KRID" is also wrong because a) it may not lead to the actual ME region (some OEMs implement a 2nd partial ME Flash Partition Table for recovery purposes) and b) not all firmware have that string based on their generation. Also, the size of the ME firmware is not always 0x17D000, which is especially wrong for recent versions, and the actual ME region of the SPI image is never at that size so leftover data may be left after that length which can cause a brick. For some older firmware like ME 6.x, even from Apple, replacing at that size will probably extend to the BIOS region and effectively brick the system. Generally, that guide is horrible and shouldn't be followed by anyone who wants a working system afterwards.

      I don't know what "post #129" is, you need to be more specific. As for the SKU: In the past, Apple had their own ME firmware SKU for mobile systems aside from the usual two from Intel for everyone else (1.5MB & 5MB). They had their own "1.5MB Apple Mac" as I called it. For ME 11.x (SKL/KBL) I am not able to verify if that still applies (maybe "Consumer Apple Mac") because Apple users tend to not be able to help in order to figure something like that out, with all due respect. I had explained at the three previously linked posts with the other Mac user exactly why it cannot be "cleaned" easily and in under which cases that is possible. So please read those three posts again first.

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

      Zitat von Jest im Beitrag #2942
      I successfully "downgraded" from v11.7.0.1229 to v11.6.29.3287 on my motherboard, Asrock Fatal1ty Z270 Gaming K6.

      Yeap, 11.7.0.1229 is based on 11.6.25.1229 and has a VCN of 178 whereas 11.6.27.3264 and 11.6.29.3287 have VCN of 192 and 193 respectively. Thus, 11.7.0.1229 is a downgrade compared to anything after 11.6.25.1229.

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

      Update to the latest 11.6 firmware, ignore 11.7 for now. Also, if you currently are at 11.6.27.3264 or 11.6.29.3287, you cannot update to 11.7.0.1229. There are no 11.7 tools posted, thus the "Placeholder" text.

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

      @ FM:

      Clearly a mistake, there is no such upgrade path

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

      Intel ME 11.6 Consumer PCH-H Firmware v11.6.29.3287

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

      Intel ME 11.0 Corporate PCH-LP Firmware v11.0.26.3000

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

      Intel ME System Tools v11.6 r12

      @ X7JAY7X:

      First of all read these three posts to understand why your case differs. As you can see, one thing we haven't out is if Apple is using a custom ME11 SKU for their laptops, in which case all the other firmware are not compatible. What guide are you following which says to "copy"? That is extremely wrong.

    • plutomaniac has written a new post "Intel Trusted Execution Engine: Drivers, Firmware & System Tools" 05.16.2017

      Intel TXE System Tools v3 r2

    • plutomaniac has written a new post "[Discussion] UBU Tool related Questions, Reports and Suggestions" 05.15.2017

      Generally, such modded versions cannot be posted at the non-discussion thread because SoniX may have different plans for his own 1.67 or at the very least such an action can confuse everyone when the official 1.67 is out. Maybe add a clear indication and don't change the minor version, if SoniX is ok with that. Meaning v1.66.1_evo or similar. For future reference, the mmtool.txt hash file is indeed a good idea.

    • plutomaniac has written a new post "Intel RST/RSTe Drivers (newest: v15.5.2.1054 WHQL/v4.6.0.1048 WHQL)" 05.15.2017

      I think 15.5.2.1054 drivers are new. The link is temporary.

Recipient
plutomaniac
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor