so i must return the cpu then. it will never work with hm65.. then it is no go. but yes i would take the modded bios and give it a go.

First, you must be fully aware that this mod might brick your board. Think twice about what you are going to do and the risks involved. I will not be held responsible for what it will happen. There is nothing safe about modding, even flashing the official BIOS could go wrong sometimes. If big companies have failed or refused, if Intel itself has declined support for mobile 6 series, how optimistic are you about one guy doing it in one shot?

1. Make sure you have the latest official BIOS installed. You must backup your current BIOS, just in case something goes wrong and you don't want to lose your SN and other ID's embedded in your system. Use Universal BIOS Backup ToolKit, or Intel fpt (fptw64 -d backup.bin -bios), or FPT_AFU_Insyde_BACKUP attached (downloaded from MDL, unpack and check .bat for yourself, if you are worried about its content).

2. You must be prepaired for a recovery, in case of disaster: read here and here (Insyde method !!!) how it is done with a flash drive. But you must put 2 copies of the backup/official bios with names AMIBIOS.rom and NAR0003A.rom. Check key combinations like Fn+Esc, Fn+B, Win+B, Ctrl+Home, Fn+F.
!!! Do this only when flashing went wrong !!!

3. Load setup defaults in BIOS before and after flashing. Have your power cord connected the hole time. Fully shutdown the machine after flashing, let it 5 minutes in that state. You can also use EC reset. If the flashing works, test with your current CPU first for any sign of corruption. Test with Intel ME Info to see if the firmware is ok (you must have the ME drivers installed first).

4. If you get an error about "project ID check fail" when flashing, it is the original BIOS+flasher that it is causing
this. You must decide if you want to use amiflash or ask Toshiba Support for a proper BIOS.

5. Only then you can swap your new CPU and test if it is accepted.

Credits to VirtualFred for ME replacing.

this bios should work fine with sandy cpu thats in the lappy now.. i will take a dessision this weekend.

Think this through, then think it again. I strongly advise to NOT flash this, unless you are a hardcore tester and have soldering skills + programmer. You can read here about a similar attempt.

There could be problems in ME not being recognized, there could be problems with the VBIOS. You should check your current VBIOS, which should be replaced by 2158. You now have a very old one, probably older than 2098, which is Sandy only. The 2158 will be Sandy/Ivy, but I haven't added any settings from the previous one, as to not change the BIOS too much. If you will have brightness or resolution issues, I will look into fixing them, but only after you will settle what CPU to keep.

My final and best advice is to only update for your current CPU, like microcodes, ME 7.1.52.1176, VBIOS 2158, Lan PXE. The risk is smaller and you can actually used it, not just hoping that it will work.

yepp, i will keep the sandy then. so do the updates you mention : microcodes, ME 7.1.52.1176, VBIOS 2158, Lan PXE. I look for a new laptop later and pas this on to my youngest one..

Yes, but be careful. You can use UBU for microcodes update, since your CPUID is in the list. You can use the ME 7.1.60.1193 posted here, but it didn't properly install on my brother's laptop, so it would be better to use 7.1.52.1176.
You can NOT use UBU for VBIOS, because it is only for desktop CPU, so you need mobile 2158/2170 and you need to take the settings from the current one.
You can use UBU for Lan PXE, but it only updates the Gbe controller, leaving the FE controller (probably mobile) as is. So use MMTOOL with "link present" instead.