Leaderboard

So, basically you're best to start by using DDU to remove any traces of old drivers. Then download and run the Nvidia installer for the 474.11. Let it fail but do not close it down. Go to your C: drive and find the NVIDIA folder. Copy and paste this in the same C: drive. It will auto-name itself NVIDIA - Copy Close down the failed installer and the NVIDIA folder should disappear and you're left with the NVIDIA - Copy folder The original NVIDIA folder is protected and you can't save any changes. The Copy is not. Navigate into the Display.Driver folder. Scroll down and find and open the nvdmi.inf Scroll down to find the first list of hardware ID's. Note: There are multiples of these list for different operating systems Copy and paste this line anywhere in the list. The Section# doesn't matter %NVIDIA_DEV.1BA1.0550.1028% = Section001, PCI\VEN_10DE&DEV_1BA1&SUBSYS_05501028 Scroll down further and there will be a small break and the list will start again. Paste the above line in this list as well. Scroll down to the end of this list and see if another list of ID's starts again and do the same. Drivers around this era had support for Windows 7, 8 and 10 so that's why there could be 3 lists of ID's so it's best to put your modded line in each of them just to be sure. Then quick scroll almost right down to the bottom and find the list of Strings. Copy and Paste this line in there. NVIDIA_DEV.1BA1.0550.1028 = "NVIDIA GeForce GTX 1070" Save and exit the inf and folder. Restart the laptop with Disable Driver Signature Enforcement. For Windows 7, I believe you just hit restart and then spam F8 to get into the hidden Advanced Menu. Select the option for Driver Signature Enforcement. Once the system starts up you just go to the NVIDIA - Copy folder and into the International folder and double click on the Setup.exe at the bottom of the list. If you've done things right then it should pass the compatibility test and start installing. Then a red/white warning will pop up and you just have to accept it to complete the installation.

https://allstone.lt/ideafan/

This is continuation of this thread (http://forum.techinferno.com/lenovo-ibm/2690-lenovo-y500-unlocked-bios.html) with all the necessary information in the first post in order to make it easier to find all the stuff. Lenovo Y400 / Y500 - 'unlocked' BIOS / wwan-wlan whitelist removal + modified VBIOS for higher overclocking The Lenovo Y500 comes with a pretty locked down BIOS, and in addition to this with a whitelist which prevents the user from getting 3rd-party wwan/wlan cards to work properly. The modified BIOS versions here will take care of this. Keep in mind that not necessarily all options available in the modified bios will work. Some might not do anything at all, others could possibly leave your system in a state which will prevent it from booting. Use care when changing stuff in the modified bios, don't touch things you're not familiar with. Use all the mods and software posted here on your own risk. Read the instructions carefully. NOTE: This will only flash the bios region. It won't reset the nvars set in the bios. *************** ONLY FLASH A MOD OF THE SAME VERSION AS YOUR CURRENT BIOS VERSION!!! If you're on 2.02 or 2.03 you can safely use the 2.04 update, *************** Attached you'll find modified versions of the Y400 / Y500 BIOS v1.03 and v1.05. Removed as they're outdated. Better updated to v2.02. The bios contains your Windows 8 license, therefore you can't just flash any file, else you'll have issue with your Windows activation. Furthermore the serial numbers, service tags etc. are stored there as well. You don't want to loose them. I wrote a little program that will take care of this issue and personalize the modified bios for you, so that you won't end up with an invalid Windows or no service tags. *************** Preparation to get to BIOS v2.02 (coming from any earlier version): Generally it's a good idea to keep the BIOS up to date. We're luck to have an official BIOS update to v2.02 apparently thanks to a leak on the net. (Lenovo is really bad when it comes to providing firmware updates and fixing issues). The leaked version must be genuine, else it wouldn't flash by using the regular method. If you want to update your system to v2.02 then grab the update here, extract it and flash the bios by executing the included InsydeFlash utility. Once the update is completed you can continue with the instructions below to get a modified version on your system. *************** Instructions for flashing a modified version: As a reminder - the modified BIOS needs to be the same version as you have on your system (2.02 to 2.04 is ok). Prepare an USB stick which can boot DOS. If you don't know how to do this, follow this short guide: Download the flash tool, for flashing you'll need the DOS version, but for creating the backup of your current BIOS the Win64 version will do as well, and it is faster. Get the prr tool as well. Grab the modified BIOS you want to flash, it comes as a tool which will patch the bios for you. Make sure you grab the version that corresponds with your BIOS version. Create a backup of your current BIOS using the flash tool you downloaded (first step) by runing the included backup.bat, or by using the Win or Dos version flash tool with this command: If the .bat doesn't work then open an administrator command prompt in your working directory and run the .bat per command line or type the command written above. In case you get an 'error 104' replace the parts file with the one that can be found in the 'error 104 fix' attachment at the end of the post. And if you still have issues after doing all of the steps above then please leave a reply in the thread and describe your problem. Open the downloaded tool and execute it. Drag and drop your BIOS backup file on it, it will create the mod for you. It will look like this: Put the modified BIOS, the prr.exe tool and the fpt.exe (along with the fparts.txt file) on the root of your prepared DOS bootable USB drive, restart your system and boot from that drive. Execute the prr.exe, if you don't get an error message continue by pressing enter. Then flash the bios by using this command (filename.bin obviously needs to be replaced with the name of the file you want to flash). If you can't remember the name of your file, use the command dir to display all the files on your drive. Flash with this: fpt.exe -f filename.bin -bios NOTE: The name of the BIOS file mustn't exceed eight characters (not counting the extension)! That's a DOS limit, so make sure the name of your file isn't too long. Wait until the process is done. After flashing it will verify the data, in case there's something wrong with the flashed data it will tell you. In that case don't reboot, just flash again. *************** Flashing the ultra bay 650m - only for SLI users with BIOS v2.02: The modified BIOS v2.02 also contains a vbios which will allow you to overclock your 650m past the 135MHz limit. As the ultra bay GPU has it's own vbios module you need to flash it separately. You'll need an USB drive which can boot DOS (just as the one you used for flashing the BIOS). *************** It might look a bit complicated at first, but that's the easiest way I could think of. Let me know if anything is unclear. >> Here's the 'buy me a beer' link in case you like this << Use at your own risk, you are responsible for your system and the changes you make on it. My programs come with absolutely no warranty to the extent permitted by applicable law. Grab file archive here:

Sorry I've been absent from Tech|Inferno everyone, life has kept me busy but I'm glad to see the forums humming along. We're always in the background ensuring things are running smoothly. To that end, I'd like to introduce my newest watercooled build that I think you'll like it. For a list of parts used and specs: https://pcpartpicker.com/b/HdHzK8 For comparison, here's the older version 2 that I had built in 2020:

Hello The motherboard and heatsink would work yes the heatsink is a easy DIY job to get the P775DM3 heatsink to fit RTX20** GPU's i can upload pictures tomorrow of how i went about doing it . The Motherbord can be worked around if you are into BIOS flashing

Hi! Try to read this threads:

so first up sorry for the thread necro not sure whats up with the thread most of the links are broken but I managed to piece enough together to make this work I am not the happy owner of a E6430 with i7-3740QM now running at 4.0Ghz fresh links to the tools since there appears to been some drama that resulted in breakage (why can't people just get along ffs) UEFI Tool https://github.com/LongSoft/UEFITool/releases I used NA A56 IFR Extractor https://github.com/LongSoft/Universal-IFR-Extractor/releases and to anybody that needs it here is the pre extracted IRF for a Dell Latitude E6430 BIOS A23 the latest and probly last bios as of this posting DELL 6430 BIOS REV A23 IRF_.zip as well as a minimal efi shell efi shell a minimal grub based cli with the setupvars tool efishell.zip dell.zip contains the python script for extracting uefi images from dells updater .exe (YOU MUST USE PYTHON27 To execute this script! dell.zip but in case you didn't want todo what i had to and spend 3 hours trying to navigate flamewars and broken links it boils down to this get the IRF table for your laptop boot to a efi shell config your desired vars remember you need to make sure the following are disabled TDP lock disabled config lock disabled TDP config up ENABLED then you can set your desired TDP and multis remember things are in hexadecimal so you need to remember to convert for example setup_var 0x25 0x28 will set the one core turbo multi to 40x here is a handy converter to make it easy https://www.rapidtables.com/convert/number/hex-to-binary.html?x=0x28 Same goes for tdp and other things you need to set be prepared to open your device and disconnect the cmos battery should you mess up and cause a no boot

Hi there, Just in case, i solved my issue, very easily in fact. i opened an hexa editor (HEXEDIT for example), opened the 8Mb and 6Mb files, did copy the 6Mb part to clipboard, went to 8Mb file, went to adress 80000h-60000h=20000h, and selected from there to end and pasted the data. save, exit, burn the file into a chip, soldered it and VOILA. if anyone needs the bios dump file of this modded G75VW with GTX 670MX (and lots of menus in BIOS no more hidden), just pm me.

Hi! Ok. Your unlocked bios done. Check PM.

Hi! Yes.

There you go. https://ibb.co/WxJXFNR Bis zum Sommer war ich regelmäßig in Würzburg. Mittlerweile leider nicht mehr... I am not entirely sure, but i think that juandante is right, my 3820QM has not been throttled down so far, even when loaded up to the maximum. But i will keep an eye on it. BTW i have upgraded to a Samsung 2TB SSD, the old one was too slow and already too small. Maybe i am going to get some new RAM, the one mounted is of questionable quality (no labels or anything)...

Lenovo Y500 - 'unlocked' BIOS / wwan-wlan whitelist removal The Lenovo Y580 / Y480 comes with a pretty locked down BIOS, and in addition to this with a whitelist which prevents the user from getting 3rd-party wwan/wlan cards to work properly. The modified BIOS versions here will take care of this. Keep in mind that not necessarily all options available in the modified bios will work. Some might not do anything at all, others could possibly leave your system in a state which will prevent it from booting. Use care when changing stuff in the modified bios, don't touch things you're not familiar with. Use all the mods and software posted here on your own risk. NOTE: This will only flash the bios region. It won't reset the nvars set in the bios. While it is technically possible to update from v2.0x to v8.01 by using the method described below, I can't really recommend it since the EC of your system won't get updated. While it might work (possibly even without any issues) I can't recommend it. Therefore if you're on v2.0x and want to update, the better option is to wait until Lenovo provides an official 8.xx firmware update with EC and BIOS. You can then still flash the modified version as described below, once you're on a proper v8.xx firmware. Attached you'll find a modified version of the Y580 / Y480 BIOS v8.01 (5DCN90WW). ----------------------------------------- >> For users with a v2.0x BIOS: << Download links Old version: Current 2.0x version: Lenovo Y580 / Y480 BIOS v2.07 (5DCN40WW) -> unlocked, whitelist removed, Nvidia 660m @ 1GHz default 3d clocks Flash with the included InsydeFlash utility. ----------------------------------------- >> Instructions for v8.0x BIOS users: << The attached BIOS ("Lenovo Y580 - Y480 BIOS v8.01 (5DCN90WW) - Mod") is unlocked, whitelist stuff removed and the 660m is tweaked to 1GHz default 3d core clock. The only way I know of which allows you to flash the modified BIOS for v8.01 users does unfortunately also describe certain information which you don't want to loose (serials, Windows licencse etc.). Don't worry, I got it all sorted out, but due to this the flashing procedure is a bit more complicated than usual. Make sure you follow the instructions carefully. Download the flash tool, for flashing you'll need the DOS version, but for creating the backup of your current BIOS the Win64 version will do as well, and it is faster. Get the prr tool as well. Grab the modified BIOS you want to flash and the Y580-Y480_BiosFix tool. Create a backup of your current BIOS using the flash tool you downloaded (first step) by runing the included backup.bat, or by using the Win or Dos version flash tool with this command: -d BackupBiosY500.bin -bios If you get and 'Error 104', grab 'Error 104' fix and replace the original fparts file with it. . Make sure you have the modified bios which you want to flash, the bios backup you just created and the "Y580-Y480_BiosFix" tool in the same folder. Run the Y580-Y480_BiosFix tool, follow the instructions on the screen. Enter the name of the files correctly, else you'll get an error. It will create a new file for you and will be named after the modified bios file you specified, with 'Fix' appended to it. Here's a screenshot of the tool in use (Y580 version looks the same). In the case shown here it will create a file called "modifiedBiosFix.bin" which you can find in the folder where you run the tool. Use that one for flashing. Put the fixed BIOS, the prr.exe tool and the fpt.exe (along with the fparts.txt file) on the root of your prepared DOS bootable USB drive, restart your system and boot from that drive. Execut the prr.exe, if you don't get an error message continue by pressing enter. Then flash the bios by using this command (filename.bin obviously needs to be replaced with the name of the file you want to flash). If you can't remember the name of your file, use the command dir to display all the files on your drive. Flash with this: fpt.exe -f filename.bin -bios NOTE: The name of the BIOS file mustn't exceed eight characters (not counting the extension)! That's a DOS limit, so make sure the name of your file isn't too long. Wait until the process is done. After flashing it will verify the data, in case there's something wrong with the flashed data it will tell you. In that case don't reboot, just flash again. It might look a bit complicated at first, but that's the easiest way I could think of. Let me know if anything is unclear. The attached v8.0x modified versions include: - unlocked menus - whitelist removed (wwan / wlan) - Nvidia 660m 'GHz edition' - 1000MHz default 3d clocks >> Here's the 'buy me a beer' link in case you like this. Modding makes me thirsty << Use at your own risk, you are responsible for your system and the changes you make on it. My programs come with absolutely no warranty to the extend permitted by applicable law. Thanks @X0pas1 for testing, and for some pics - see below: I'd appreciate it if someone could also post some pictures of the more interesting sub-menus, e.g. advanced CPU control, video settings and similar. UPDATE 1/17/16 DOWNLOAD LINK FOR FILES REFERENCED IN THIS POST:

Hi. I had this setup when I had the adapter... Yes, in spite of being a very decent processor, the 4700MQ will bottleneck the rx580. I think having a better GPU would not improved much the fps, being bottlenecked by the processor and adapter itself. I played warzone (all minimum) and were around 70 fps, very decent for a very outdated setup

The ROG Strix lineup, along with many other ROG laptops, is user-upgradeable, meaning you can add in more RAM or storage with nothing more than a screwdriver. Here's how.

Hi, the parts list is right here: https://pcpartpicker.com/b/HdHzK8

Hi! Try to download MSI Afterburner utility or ASUS GPU Tweak utility, or Nvidia Inspector utility, and then try to overclock your card.

Hi! Ok. Your bios with unlocked whitelist done. Check PM.

Hi! Alienware M17xR4 does not have any whitelists, so you don't need unlocked bios to replace the Wi-Fi card. I think you have to fiddle around with different drivers to find the correct driver for you.

I can't give you concrete answers to the video problem, but I do know that the Vbios of the video card is matched to the particular configuration of the system BIOS's of the laptop model they are put in. I believe this has to do with the ME monitoring temperatures and running fan speeds, The BIOS for which display to put video to by default and what the correct display modes are, as well as coordinating the Backlight power with the GPU and power delivery. That's mostly my speculation based on behaviors I've seen in the past. As far as the memory goes, I believe that model has four slots for RAM, two on the bottom, two under the keyboard. Try different slots to see if some work better than others, and run Memtest86+ on each stick individually to see if one of the sticks of ram is less optimal than the other. Sometimes the sticks of ram test good, but don't play well with each other, and one, or both need replaced. Sometimes that model takes a good two minutes before it finally resolves an acceptable RAM timing solution, reboots and posts normally, so be patient with it. (this is usually only when there are issues with ram sticks agreeing with each other.)

Howdy! Found the forums here questing to snag a replacement BIOS for my P775TM1, I thought I still had a copy from back in the day (alongside a Prema backup) but apparently I do not. So I'm here to be helpful, and await download approval. Might show off some of my mod projects.

Hi! Ok. Check PM.

Ok. Your unlocked bios done. Check PM.

Hi! Ok. Your unlocked bios done. Check PM.

Hi! Ok. Your unlocked bios done. Check PM.

No.

Hi! In your laptop model, any modified bios can be flash using hardware SPI programmer only, exactly the same as described in the first post of this thread: So, for creating backup (dump) of bios you need to use hardware SPI programmer only.

Hi! Ok. Your bios with unlocked whitelist done. Check PM.

Hi! Ok. Check PM.

Hi! Ok. Your bios with unlocked whitelist done. Check PM.

Hi! Restrictions on the type of battery are located in the EC firmware (not in bios). But I don't work with EC firmware.

Hi! Ok. Your bios with unlocked whitelist done. Check PM.

In case you own a Lenovo Y410p or Y510p laptop, you might be interested in upgrading its performance by installing an external graphics card. Ultrabay eGPU adapter designed by @gerald was proven to be a convenient plug-and-play option to do exactly that. However, for a long time only an AMD-branded GPUs could be used due to limitations in the Lenovo's stock BIOS. The purpose of the modified firmware presented here is to expand the range of available GPUs by enabling Nvidia support on Gerald's Ultrabay eGPU adapter. Huge thanks to: @MWichni - For efficiently assisting me during the development of this mod. By flashing dozens of BIOS builds over the course of several weeks and thoroughly describing the effects observed (or the lack thereof), he enabled me to fully understand necessary parts in BIOS structure and come up with a final solution. @svl7 - Whose unlocked BIOS / Whitelist mod has served as a basis for this modification. His discovery of a security hole in V2.07 BIOS has provided us with a convenient BIOS flashing method that does not require a physical programmer. The Unlocked BIOS and WLAN whitelist mods originally designed by him are also implemented in this BIOS mod. @gerald - For designing the aforementioned adapter. Without it, all this work would make very little sense. Key features: Resolves the "40-second reboot" issue normally encountered while using Nvidia graphics cards with Ultrabay eGPU adapter, thus allowing all Nvidia cards to be used. Based on the latest V3.08 BIOS. Includes Svl7's WLAN whitelist removal mod - for the convenience of aftermarket WLAN card users. Includes Svl7's BIOS debug menu mod - for the ease of experimentation with newly available features, e.g. attempting to use Nvidia Optimus to pass eGPU video back to laptop's display. NB! Svl7's Debug Menu is not a toy! It contains a lot of options that are either not supported or partially supported by the hardware platform and/or can disturb its normal operation or prevent the PC from booting up at all. Any of the entries not originally present in the stock BIOS should be modified at your own risk! DISCLAIMER: ANY MODIFICATIONS YOU ARE APPLYING TO YOUR HARDWARE ARE PERFORMED AT YOUR OWN RISK! AUTHOR OF THIS MOD DOES NOT HOLD ANY LIABILITY FOR LOSS OR DAMAGE RELATED TO USING THIS SOFTWARE. Screenshots: Installation instructions: If things don't go right: Error 43: If you intend using the GTX10XX-series Nvidia card as the eGPU (which you probably do), you are very likely to encounter the infamous Error 43 in Windows Device Manager. This is a widely known issue in the eGPU community and is not related to this particular mod in any way. Following this guide thoroughly will in most cases resolve the Error 43 issue. Download: Get your copy here! P.S.: Version of this mod for Lenovo Y400/Y500 models is coming soon!

Ok. Check PM.

Hi there ! I'm creating this thread because I've got a problem : My old Medion Erazer x7817 just lost his poor gtx 560 gpu.. and I could get my hands on a rx 480 mobile 4Go supposedly manufactured by ZRT (Unknowned to me). My problem is that i can't manage to use it properly. I'm dual booting windows 10 an Kubuntu 20.04 with a gpt hardrive (UEFI) and got different outputs with the OSs : - Windows : fans start spinning crazy just before getting to Desktop, and in devide manager I can see the rx 480 but disabled (with the yellow exclamation mark). Same problem when installing the last Adrenalin drivers, and I can't open the GUI (It says that i don't got a properly functional amd gpu). GPU-Z only shows the specs of the integrated GPU (HD 4000). - Linux : No crazy fan spinning. the command "lspci | grep VGA" shows me that the gpu is properly detected, and can run basic 3D objects using "DRI_PRIME=1 glxheads" but crash whithin seconds with heaven benchmarks, it seems that It can't handle "harder work". I searched a lot (maybe badly, but I really tried..) over distinctive forums and know these informations : - rx 480m might not work with legacy bios, but I use UEFI (and tried also with legacy) - I'm unable to find the link where if read this - - rx 480m can't output on LVDS screens (which I got) if the motherboard doesn't support OPTIMUS/ENDURO (Ok with the gt 60) -> http://forum.notebookreview.com/threads/hp-elitebook-8760w-compatible-with-an-rx-480-4gb-mobile.834335/page-2 Do you think that could be some bios or vbios problem ? I also read somewhere that optimus laptop include the vbios inside bios. I'm also thinking about power, maybe the 480 draw too much for my psu ? Or the fact that I changed from Nvidia to AMD gpu ? If somebody got a clue about what is happening, it would be wonderfull to explain it to me here ! Laptop Specs : - Medion Erazer x7817 with ms1761 motherboard (compatible with MS-16f3 bioses) - GPU : rx 480 mobile 4Go - CPU : i7 3610 qm - OSs : Windows 10/Kubuntu 20.04

Got some good news ! I could made it work ! I'll copy what I wrote in the netbookreview forum, and hope it'll serve to somebody here Hi there !More news here : With the "Rx 480M 4GB vBIOS - 015.050.000.001.000000 Samsung & Hynix TDP70W.rom" vBIOS, the problem seems to come from vulkan/DirectX API.OpenGL games works great (Portal 2 and Hades via wined3d) without crashed under linux.It seems so that this bios doesn't permit me to use the vulkan api (under linux) o directX under windows (the crash with heaven benchmark using directX11).I tried to search a bit but couldn't find any information : Does anybody have a link about vBios modding or want to play with me at the "Will your computer burn if you install that" game ? Anyway I might speak alone, but at least if somebody pass through the same problems, he/she'll have here a bit of information. Even more news ! I flashed another BIOS from here --> https://linustechtips.com/topic/126...esartifacting-problems-when-its-underclocked/which seems to work a bit better, but I steal got the same problems with vulkan (I used the one named 700).So I thought, why don't I give a try with this poor Windows that I everytime forget and then tadaaa : Directx 11 and Vulkan work there.Weird thing, this bios seems to be from a rx 580.I tried with the same game "Hades" which can run with both api.So we could say that a rx 480 mxm can work within a Gt60 Ol' Laptop, wich is great IMO, I'll upload here the vBIOS I got from Internet in case of somebody might need them.ANYWAY, if somebody want to help me with the linux problem (still searching for a solution), I'll be honored . Oh, and a last detail, but of importance : My motherboard BIOS is flashed.I remember doing it a long time ago (years), seeing a thread about putting 980m inside my mobo. I flashed it in case of, but i can't remember where i found the file.Anyway, the bios name is E16F31MS.51X (yes, it's from another motherboard, but it's compatible) and the EC is 1762EM71 ver 4.05. Here's the link with the vBIOS I've found :https://drive.google.com/file/d/1q9K0j7zgLCMHvHXzaoZIDzJyjk4V29LX/view?usp=sharingIt's a zip archive, hope it'll serve to somebody

Update: Moral Hazard used MESET.EXE on his clevo to force a dump and flash, but did not gain BCLK control. Update 2: SUCCESS by kasar on a Dell xps 15 (L502X) here! Unfortunately he needed to disable the ME region lock by desoldering and flashing the BIOS chip though. Update 3: SUCCESS by me on Clevo P150EM here! Mod relied on Clevo-only program to unlock ME region. Update 4: SUCCESS by Rhadamanthis on MSI gt780 dxr Update 5: SUCCESS by Akimox on HP 2570p here! At the hardware level, all 6 and likely 7 series laptops support overclocking. The problem is OEMs disable this ability except on laptops like the m18x. Clock configuration is NOT controlled by the BIOS. It is controlled by the Intel ME FW (management engine firmware), a BIOS extension. Only a few bits must be changed from a overclocking disabled ME FW to make it an overclocking enabled ME FW. Gigabyte accidentally leaked an intel utility that can read the ME FW, edit it, and write the new version back to the flash ROM, along with all the necessary documentation to make the correct changes. This flash ROM contains not only the ME FW, but the BIOS, flash descriptor, and 2 other regions called the GbE and PDR. There is one problem, which is that all laptop manufacturers (except ASUS) disable read/write access to the flash ROM. The read/write locks are contained in the flash descriptor. The security settings in the flash descriptor can be ignored by setting a special flag on BIOS startup known as the flash descriptor override, which enables read/write access to all regions. This override is used when you run a BIOS update. At this time there are methods to enable the flash descriptor override for HP and Clevo systems only. After setting the override and rebooting you can dump your whole flash image, edit the ME FW, rebuild the image, and flash. It is possible to flash either the ME FW region only, or the whole image. Obviously flashing the whole image is risky since you will also be flashing your BIOS, so I suggest just flashing the ME region. 6 series are more tolerable of corrupting the ME FW than 7 series. 7 series cannot run without a functional ME FW. 6 series can run without one as long as the BIOS detects that the ME FW is corrupt, and thus refuses to run its settings, however, the laptop can sill be bricked anyway if the BIOS thinks the ME FW is functional while it really is not, and attempts to run the inoperable clocking settings. Some of you may be aware of fwupdlcl.exe which can update the ME FW without enabling the flash descriptor override. This does not work for our purposes since it does not perform a full flash. It does not overwrite the hardware config portion of the ME FW, which is where clock configuration is done. However, if someone could figure out what this program does to write its partial image, it may be possible to use that knowledge to flash a full image. So here's the Intel Utilities and docs: 6 series chipset Link removed since the leaked FITC builds invalid images. Use the ME8 FPT and documentation for now. 7 series chipset: http://www.mediafire.com/?iwscmnadf5icnxq (thanks to kasar) MESET.exe to unlock Clevos: http://www.mediafire.com/?465pknsgc2z83s8 ME_Port by svet to unlock MSIs: https://www.dropbox.com/s/spmvxmz9pal1j6l/ME_Port.com BE CAREFUL WHEN USING FPTW64! It will happily overwrite your BIOS without any warning if you enter the wrong command. Even if you do things properly, still be prepared to have a dead ME FW and whatever the consequences of that may be. Although it is unlikely, trying to enable overclocking through my suggestions can kill your motherboard. There are a few combinations of mistakes that can be made which will most certainly do so. You have been warned, so don't blame me if you do. Also if you do, do NOT go RMA your laptop and make your manufacturer pay for what you caused. You took the risk, so you pay for the necessary repairs even if under warranty. If things go wrong I will do everything I can to help you recover, but please accept responsibility for trying this. Ok now that all that is out of the way so people can't justifiably yell at me. Back to how to try this. 1. Enable your flash descriptor override. Clevo users can use MESET.exe. MSI users can use ME_Port. HP users can use the keyboard sequence "WIN+left_arrow+right_arrow" during POST (got this info from Tech Inferno Fan). ASUS users don't have to do anything since they don't have the lock engaged. The rest of you guys are at this time out of luck. 2. So you'll first need to dump your ME FW image. This is done by running fptw64 in windows or fpt in DOS. It needs to be run in a cmd window with admin rights. The command to do so is "fptw64 -d imagename", where imagename is whatever name you want for your flash image dump. Prema found out that at least on Clevos, attempting to dump only the ME FW leaves out the clock control segment, so you need to dump the whole flash image. Note that you're also getting the flash descriptor when you dump everything, so you can edit it to not require the flash descriptor override to do any flash image reads and writes. 3. Now you need to change some bits to enable overclocking. By some, I mean you probably have to change quite a lot. The good news is that the settings on 6 and 7 series systems seem to be identical. When I edited my image, I followed the intel docs in the ME8 download. I've linked my original overclocked MW FW for comparison. You only need to make changes in the "ICC" section and subsections in FTIC. You can edit the ME FW as part of an entire flash image, or by itself. I edited it by itself, but have since then done several BIOS mods and flashing the whole image worked out fine. My modded P150/170EM ME FW: meoc.bin This image is just for reference to make sure you didn't miss anything. Don't just flash this ME FW. It might work, but there has been issues with flashing someone else's ME FW on HP and Dell systems and others may be affected. Dump and edit your own, or ask me to and I will if I have the time. Some manufacturers have additional changes. When it doubt read the manual or ask me if something should be changed or not. The Utility for editing the images is FTIC. This program has a GUI so it does not have to be run from cmd. Open your image and open the overclocking enabled image. Settings that are different from FTIC's generic 6 and 7 series file will be highlighted in yellow. What you need to edit is the ICC profiles under ICC Data. You can have up to 8 profiles. I think active profile changes depending on if you are say plugged in, on battery, on standby, temps are too high, etc. I don't really know how you identify which profile(s) much be changed, so I think you should just change all of them to make sure that if the flash works and you don't get overclocking, that you know you didn't miss something and that overclocking is impossible, so you don't waste time thinking about it and trying things. The number 1 thing to check that I found to make sure things don't go bad is your "clock source select" under "FCIM/BTM specific ICC registers". If it is 0x00011A33, then your laptop uses the PLL built into the PCH and you can keep going through trying this mod. It will be 0x00011A34 for enabling overclocking. If it is something else besides these 2, STOP NOW. This means that your PCH's PLL is not being used, and that instead an external PLL is feeding the PCH clocks to distribute. If you set your laptop to use the PCH's PLL, I think the PCH will get both clocks and you'll get a laptop with unintelligible clock signals. That would be bad. After making the changes you need to rebuild the ME FW image. You will then have a full image, and if you reopen this new image in FITC, FITC will create a new folder with the MW FW all by itself. You can use the full image or the MW FW image to flash. 4. Now the fun exciting part where we do the flash. I recommend doing it in DOS. The command to flash the ME FW only is "fpt -me -f filename", where filename is the name of your flash image. Don't forget the .bin extension. If you are flashing the entire ROM then you do need to leave out the "-me". If flashing the ME FW only and used the "build compact image" option in FITC, you should get a warning that the flash image is smaller than the total ME Region area that the flash descriptor says you can use, so the area after the file length will not be changed. This is OK and flash anyway. The image FTIC creates is not padded at the end, which causes the warning to occur. If you built a full image it is padded, so you don't get this warning. 5. You can now use Intel XTU to overclock. If you already installed it, you may have to reinstall it. BCLK can be changed in windows and takes effect immediately. Remember guys, this is risky stuff, especially if you have a 7 series laptop. If you're careful though everything should turn out fine.

Hi! Each bios mod prepared individually and based on your personal file backup of bios. Just read the first post of this tread.

Hi! Ok. Check your PM box.

Hi! Ok. Your bios mod done. Check PM.

OK, people have been asking for this for a while so I thought since I can tear this down in about 10min, I should do a quick write-up. Like the title said, I did this quick so pictures wont be the best but you will get a better understanding on how to teardown the system enough to at least repaste etc.. Here we go 1 - Shot of the underside 2 - Remove battery and the 4 screws in red to remove bottom cover 3 - Bottom Cover Off: Remove Screws Labeled I (5 of them in Red), P ( 5 in Blue), and HD Bay screws (4 in Green) 4 - Remove Hard Drives 5 - Remove Screws In Empty Hard Drive Bay (4 in blue) 6 - Remove the LCD Hinge Screws ( 4 in Red) and disconnect the wireless antennae (circled and traced in Red) 7 - Flip System over and open screen 8 - Pop off the media control panel by lifting the back right and left corners until it "pops" off. I find using my guitar pick helps with this 9 - Once the back corners have popped loose, run the guitar pick around the edges to loosen the rest (around the keyboard) 10 - Picture of the media panel loose but still connected with the ribbon cable (disconnect this now) 11 - Remove the Keyboard and macro keyboard screws ( 6 in Red) 12 - Disconnect all cables from the motherboard and graphic cards ( 11 in total) and 2 more lcd screws ( 2 in blue) This includes: 2 ribbon cables for the macro keyboard 2 ribbon cables for the keyboard 3 for the handrest/trackpad (2 on bottom, 1 near the right crossfire cable connector) 2 for the screen (one toward the bottom left, one at the top left) 2 for the crossfire cable (labeled L and R on the cable) 13 - Remove 3 more screws securing the cover ( 3 in Red). You will need to pop off this cover starting at the back... just lift until it pops off. If it is being difficult, make sure all screws labeled "P" on both the top and bottom are removed. 14 - Once the cover is off, remove the screws (going from #1-4) on your heatsinks.... clean and repaste. If anyone wants pics of the heatsinks removed just let me know (I took a couple but not really necessary for this guide). Once again, I did this all very fast so I know it is not as polished as it could have been.... but I wanted this out sooner than later for everyone to use. Let me know if anything is unclear etc... D.

In everyones name i just would like to thank you guys

i can go down to 9-11-11-X, but it performs rorse somewhy than 10-11-11-X, the memory copy is down from 30.5k to 27k. , anything lower for tRCD and tRP than 11 doesn't boot, and , and tRAS wise i can kind of set anything (tried even 13) and it does run memtest without errors, but the setting affect the performance and latency a little bit. Latency wise 28 is the sweet spot, RW speed wise is 27. The difference is very small, but consistent across multiple benchmarks.

Yes, of course. As i already answered you in email.