Here.
ME.rar (1.8 MB)
-
Your me.bin is an update binary! You have to use an ME region for flashing it via fpt! Writing an update binary as a region would brick your machine.
-
The command you used would write the file me.bin as a complete firmware, not a ME region thus beginning at 0x0 and overwriting the Descriptor region. This would brick your machine second time.
The correct command for flashing a ME region (if you had had one) with fptw64 would be fptw64 -ME -f me_region.bin -
The manual says your board has USB flashback:
I’m sorry, but you don’t understand what you’re doing and you’re trying really hard to brick your machine.
Take very good care of the dump you got via fptw64 -d spi.bin since you’re gonna need it for recovery if you continue this way.
Big thanks for answer.
“The command you used would write the file me.bin as a complete firmware, not a ME region thus beginning at 0x0 and overwriting the Descriptor region. This would brick your machine second time.”
But i don’t understand anyway how do i downgrade ME to the old one then? If i simply take old ME(which is not ME just an update) for my system and go to the FPT for downgrade “make my system bricked”
Asus Crashfree Bios 3 as i understand runs when your system can’t load and it activating automaticaly
Can i use this ME which provided and flash it with programmer?
You can flash a ME region with the correct syntax and binary. You can for example extract as is a ME region from an Asus update file as shown:
Save this file as ME_region.bin and use the command fptw64 -ME -f ME_region.bin
But this will possibly give you an error since ME region is still write protected at least in Flash Descriptor.
No, can be used anytime afaik.
No! As written and shown in HxD it has another structure and is an update binary, not a region. In addition wrong size!
Be careful - the only warnig fpt gives is a size warning! Otherwise it writes everything you give to it at any place you command it to!
@molando , how did you update your ME, and why do you now want to downgrade it?
This board has an easy to use ME firmware UpdateTool. If you have a good stitched ME firmware, you could do essentially the same thing (manually) in CSME System Tools v15.0 r15 > FWUpdate > WIN64 > FWUpdLcl64 -f stichedfirmware.bin
IOW, you wouldn’t mess with FPT; you’d use the FWUpdate tool. There should be no Protected Range Registers at play.
@lfb6 , is there any reason that the FWUpdate tool wouldn’t allow for a downgrade?
As written long ago…
(The TO didn’t tell us why he thinks he needs to downgrade and from which version to which version)
OK. I’ve never considered downgrading.
This shows when i try to flash me_region
How would I answer that?
I don’t know if you extracted the ME region properly and if you have a proper backup / dump.
Extracted As is from Uefitool
If you want me to check you can attach it. Theoretically it should be OK if done properly from the correct firmware.
Check that you have a good dump done with fptw64 -d spi.bin
If you have a fTPM enabled it’s reset. For a bitlocker encrypted drive you’d need to suspend ecnryption first or otherwise have the recovery key accessible!
And if you flash you should cold restart the ME with fptw64 -greset
No write access…
As written, haven’t seen your bios dump, but ME-region is write protected in Flash Descriptor for almost every machine.
So this time you probably had the right commands and files but still no write access to this region…
I’d try Asus Crashfree Bios 3, won’t hurt much, but might need some fiddling with USB sticks and formatting, correct renaming of the file and correct USB port, and it might update the bios region but forget to write the ME region, too.
sorry, attached
spi.rar (8.6 MB)
on asus crashfree, i renamed and copied bios to flashdrive but system just loads to windows i think this thing works only if you have errors with bios otherwise idk how to run it
So what’s my next step? I’m thinking to buy a programmer and flash modified bios with unlocked FD and try again flashing Me_region.
I tried several times to do this in afudos and afuwin but getting error “ME Data Size Checking … Fail**c8 - Error: Invalid ROM image file, ROM image file may be corrupted.”
The reason i’m doing this because after updating firmware everything works but something happened to the monitor image, it started looking bad, it kinda lost it’s brightness or something.
Sir… being ME FW as cause of that is very VERY unlikely, please stay put with this.
A monitor is an independent peripherical and only dependent on the output signal of a video source.
Your issue lies on the monitor itself or graphics card definitions.
EDIT: Then you’re unlucky as the issue turn out exaclty when you updated the bios from Asus and/or new fw??? Is that it???
Besides some power managment theres really nothing in Intel ME Firmware that concerns image output settings/quality, take this out of your ideia please.
If you had mention that this is the cause of downgrading the ME FW, already everyone else had told you the same and spare you and users all this writting… look for the cause of issue some where else but not the ME FW as main cause of a “bad image from monitor”…
i haven’t had this problem before
You literally saying that it is controlling power management and then you say problem is in something else…
As far as i know this “ME” is a part of chipset and chipset controls all peripherals. The image looking really “dead” after i updated firmware…
Go read and decompose an ME FW image, learn and then you can give lecture “lessons” and dont “put” words in my mouth, understood?
Wrong… learn and then you can comment and correct users.
If the image is corrupted, theres a guide on the forum for cleaning/reinitialize the the FW engine image of the system.
And with that i can say that we are all out of this… when a user issue is “a bad monitor image”.
Good luck and all the best, a merry christmas, over_n_out, of here.
You started this, i don’t want to argue with you i came here for help, my main target is to downgrade ME that’s all i need