Code: File: Tool_v8.0_Build_1.7z CRC-32: e5f25606 MD4: 64711a30ed0e439a3b16b4684e17b3a8 MD5: 55ca2a067a4d6a9f4e639bd17e37c685 SHA-1: e967cc45c5d9e961dacf176a90937ed6781403d6 File: Multi_OEM_Project_04.07.2016.7z CRC-32: d5590b2d MD4: 2a10632f841b98c841fcd63c11e978cf MD5: 3483045a89a55f9300b87abae68d798e SHA-1: 161f2295110d358cda37f24bf6253dbca2d2fc16 File: OEM_s_04-07-2016.rar CRC-32: 771bd0cb MD4: 8bd10bae7c763cbd99889b382dec36c5 MD5: e39d34db81faad3f5b1367f57ead7e56 SHA-1: 5a1b20c5066ac2003a7afc4909bc439c1301f555
Typo on my part that I forgot to change. If I change the post I have to get a hold of Tito again to hide pastebin url. I hate bugging him to hide it again. Its only a typo but will ask him in pm if he can hide it again. I really hate bugging him. lol I sent the pm to Tito.
Now to troubleshoot my other project. Seems I am back and forth today. Update: Guess Tito was reading the thread when I sent him the pm. Its done already. Looks like I forgot to change 2015 to 2016 in change log. Its just a typo, sorry. I am not going to edit the post again just to change it to 2016. The main heading is 2016 so users can put 2 and 2 together to realize its a typo in change log. Sorry again.
DATE FOR ITS NOT SERIOUS ABOUT DOWNLOAD LINK his noted 2016 thank you again for your really great work your software to reuperer the key microsoft official Licese course not hacking it really helps for activation
Not "ANY" word but for example, DELL, HP, etc. I give a list of all supported OEM Brands to choose from within the project. The project should auto find the OEM and apply the correct theme. The force theme txt file is a backup method just in case it doesnt auto find the OEM or bios are modded with another OEM (bios mod for example, HP modded with Dell bios).
The project by default auto detects oem branding by reading the bios. If you do use the force theme txt file then it will brand according to what oem you typed into it.
Code: File: Multi_OEM_Project_04.07.2016.7z CRC-32: f523f1d6 MD4: 74a34e644ef3367b4a0d565c3bb9bf71 MD5: 8a085c7bc1b5465d96707e442046269d SHA-1: a5147ddbe2ca155c0c886dbe2549523d12078b3f File: OEM_s_04-07-2016.rar CRC-32: 771bd0cb MD4: 8bd10bae7c763cbd99889b382dec36c5 MD5: e39d34db81faad3f5b1367f57ead7e56 SHA-1: 5a1b20c5066ac2003a7afc4909bc439c1301f555 File: Tool_v8.0_Build_1.7z CRC-32: e5f25606 MD4: 64711a30ed0e439a3b16b4684e17b3a8 MD5: 55ca2a067a4d6a9f4e639bd17e37c685 SHA-1: e967cc45c5d9e961dacf176a90937ed6781403d6 @The_Guardian could you provide the checksums on every update? thnx
I will add to to site this evening when home. I updated the project to include the new oem in the OEM's Used in Forced_Theme_[readme] File which I forgot to do when released officially. My bad.
Thank you The_Guardian for this project, I've been using it for quite some time now and had no problem with activation. The only problem I got was for brand recognition, so I now use the Force Theme feature everytime. One exemple : Surface Pro, whichever generation is recognised as ProLink (it's probably looking for "Pro" ?) instead of Surface. I had other brands with that kind of problem, I just wanted to ask if you needed that information ?