after some research i decided to make transfer of all settings of me firmware to another me firmware(same version 8.1.52.1496)
the bios that i want to transfer the settings from is this:https://mega.nz/#!rQVVWbAJ!JoFjaZmy-2sQ8…fPycVvbWBQNM3Lw
but because of my poor knowledge im thinking that if i to this will my notebook got bricked ? (i will change all the settings except oem information settings)
Download the appropriate System Tools Package and run two instances of Flash Image Tool (FITC). One with the old bios loaded and another with the new one. Compare ME settings and adjust everything exactly as it is at the original. Then build the new SPI image.
i changed every settings except "Enable İntel (R) Standart Manageability;Disable İntel (R) AMT" option im not able to change it 
also what is SPI image ? i pressed build and 4 files have been created must not it be 1 file ? how to flash this files ?
edit:im transferring settings from qm77 mobile chipset firmware to hm77 chipset firmware does it matter ?
I don’t understand what you are trying to do. Don’t transfer settings from one machine to another, doesn’t work like that. Leave each machine’s firmware settings intact. What I said above is only relevant when you want to re-create your SPI image with a newer ME firmware for a given system. Not for cross-platform alterations.
The SPI is the chip itself which includes regions like Flash Descriptor, BIOS, ME, GbE, PDR etc. I don’t think you should be messing with such things if you don’t have such basic knowledge. As far as FITC is concerned, go to it’s settings and disable intermediate images to get one final SPI image.
if i transfer settings will my notebook got bricked ?
What do you want to do exactly? Explain your thought-process.
i want to transfer all the current options in this me firmware to my firmware:https://mega.nz/#!rQVVWbAJ!JoFjaZmy-2sQ8…fPycVvbWBQNM3Lw
this firmware is from prema so after transferring i cant overclock my cpu or disable turbo boost
First of all @Prema mods should not break any overclocking, his workings are always top-level. The only example would be upgrading ME 9.0 systems 9.1 firmware without first updating of the BIOS from the OEM with updated ME dependencies but this has nothing to do with ME8 firmware.
So I suppose you have a Clevo system? Which one? As I said, more information is needed to provide accurate help and not vague hints.
If I understand properly, you want to restore your ME firmware to how it was previously with just the version updated. Take the latest BIOS from Clevo for your specific model, download the 8.1.52.1496 region from here and do as I said above. Open two instances of FITC and adjust all settings of the 8.1.52 firmware to be exactly the same as the ones from the latest Clevo bios. Then build only the ME Region (Descriptor Region > Descriptor Map > Number of Flash Components > 0). You should end up with a 1.5MB ME Region of version 8.1.52.1496 but adjusted with the settings of your own model’s ME. Use Flash Programming Tool to replace the old ME region with the new one (fptw64 -f ME_Mod.bin -ME). Also, if your descriptor is locked (error 26 when trying to flash ME region with FPT) you will need the MESet.exe tool that Clevo sometimes provide to disable it and thus flash the ME region.
Do not take the ME settings of other models, only your own.
Do not take the ME settings of a stock or extracted ME region because they are not based on your system.
This is if you want the other adjustments Prema made in his mod apart from the modded ME firmware. Otherwise, if you don’t care about the modded bios at all, just restore to the latest stock Clevo BIOS and then use FWUpdate tool to update to the latest ME firmware without loosing any OEM specific settings. Again, in order for the protected ME region to be restored to Clevo default you might need to use MESet.exe first. Usually though Prema also provides his own scripts to restore to default Clevo bios if you want. If that’s the case, definitely use that package.
Is this the recommended way of transferring settings, with two instances of FITC? I see this not only as time-consuming from user point of view, but also prone to errors. Not to mention that the two FITC will use the same xml and not all settings are visible in FITC, some only in xml. The way I see it (and I remember testing this), is to open the firmware with needed settings, save the settings as [something].xml, open the new firmware and load the previous xml. At the end you can re-open the saved firmware with a clean xml and save its settings, then compare with original xml.
I highly doubt what I said it recommended. No OEM would ever go through so much trouble for every SPI image with an updated ME region. But if I remember properly this has worked for me in the past.
Since I have a Z77 with unlocked descriptor and dual BIOS, I will test both methods in the future to test the two methods further. Yes, the xml one seems a lot easier.