corna / me_cleaner

Tool for partial deblobbing of Intel ME/TXE firmware images
GNU General Public License v3.0
4.51k stars 279 forks source link

Works on: #270

Open 0181505050 opened 5 years ago

0181505050 commented 5 years ago

hi peterwankman, do you think your method will work on a MAXIMUS VIII HERO motherboard with the same processor?

Id really like to give this a go. im new to programming with the universal programmer. but im quick at learning. and can follow instructions. if your keen to help give me a shout, thanks, tom.

Works on:

I used a cheap USB programmer I had used for earlier projects. It automatically detected the flash chip and read from and wrote to it perfectly. The original BIOS was the latest release from ASUS (3085 from 25.05.2018) with the latest ME Patch (11.8.55.3510 from 27.08.2018) BIOS now reports ME Version 0.0.0.0; Windows Device Manager reports the ME as not connected. No issues so far.

_Originally posted by @peterwankman in https://github.com/corna/me_cleaner/issues/3#issuecomment-449930625_

peterwankman commented 5 years ago

How would I know? It doesn't depend on the processor, but the flash chip. Have a look at the chip and see if it's listed in the programmer's software. Mine is a Winbond 25Q128FV in a DIP8 package, which is supported. I can't say anything about any other chip, other than to get a spare one first, in case it doesn't work.

0181505050 commented 5 years ago

Ok mate. Theres more to it than I thaught. I have a Winbond 25Q128FVIQ 1552. I think i need to do more research. As from what you just said, Ill need quite a bit of instruction. cheers.

peterwankman commented 5 years ago

https://www.winbond.com/resource-files/w25q128fv%20rev.m%2005132016%20kms.pdf The -IQ at the end stands for the variant of the chip (Industrial and Quad Enable). It's the same as mine. 1552 is probably a date code (52nd week of 2015)

0181505050 commented 5 years ago

thanks peter. thats given me the confidence to do it. I need to research every step on the way. ( buy this tool you have) and learning how to backup, modify and reflash. I only want to do it once and do it right :) sadley no youtube videos or step by step guides for fools. ill get there eventually.

dartraiden commented 5 years ago

step by step guides for fools

https://github.com/corna/me_cleaner/issues/98

steps 3&4 (dump current bios) → step 2 (me_cleaner) → step 5 (flash bios)

please note, some overclocking features (for example, bus speed overclocking) will be unavailable without ME, so ALWAYS CREATE BACKUP OF CURRENT BIOS before flashing new bios.

0181505050 commented 5 years ago

i am one grateful fool :)

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, 11 May 2019 17:54, Alexander notifications@github.com wrote:

step by step guides for fools

#98

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

0181505050 commented 5 years ago

I assume the process is identical if you are doing it to a asus maximius viii?

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, 11 May 2019 18:36, tommo@protonmail.com wrote:

i am one grateful fool :)

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, 11 May 2019 17:54, Alexander notifications@github.com wrote:

step by step guides for fools

#98

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

dartraiden commented 5 years ago

Yes, I did it with Z170-P... but it is identical for any motherboard with a removable chip All Z170 ASUS mobos should work well with -S me_cleaner's switch

0181505050 commented 5 years ago

I ordered the parts. i hope this works. really appreciate the effort thanks.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, 11 May 2019 18:51, Alexander notifications@github.com wrote:

Yes, I did it with Z170-P... but it is identical for any motherboard with a removable chip

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.