|
Release Website : CracksNow.com
Multi OEM Project (Windows Vista, 7, 8x, 10) Build 27.07.2017 [CracksNow]
100+ OEM's:
• Acer • Advent • Action • Alienware • AOC • Aquarius • ASRock • Asus • ATcomputers • Bangho • Beko • BenQ • BGH-SA • ByteSpeed • Casper • CCE • chiliGREEN • Compaq • crea • CZC • Dell • Depo • digimix • ECS • eMachines • Epson • Equus • Everex • Excimer • EXO • Exper • Extra • Founder • FSC • Fujitsu • Gateway • Genuine • Gericom • Gigabyte • Greatwall • Haier • Hannspree • Hasee • HCL • Hedy • Higrade • HP • Hyrican • IBM • Impression • Infinity • Insys • Intelbras • iQon • Itautec • Jetway • JooyonTech • Kohjinsha • Kouziro • Kraftway • KSystems • Lanix • Lenovo • LG • M&A Technology • Maxdata • Mecer • Medion • Megaware • Mesh • Mitac • Mouse • MSI • NEC • Nokia • Olidata • Olivetti • Onkyo • OQO • Packard Bell • Panasonic • Paradigit • Paragon • Philco • Positivo • PowerSpec • Prolink • qbex • Quanmax • RMplc • Rover • Samsung • SCC • Semp Toshiba • Seneca • Sharp • Sony • Stone • Synnex • Systemax • Tangent • Targa • Tarox • TCL • TTL • Tongfang • Toshiba • Trigem • Twinhead • Velocity • Vestel • Viewsonic • viliv • WD Corporation • Wortmann • xplore • Zoostorm • ZT ~incl. (branding only): BioStar • Foxconn • Intel • M$ $urface • VirtualBox • VMware
FEATURES -
• OEM's = 118 ; Branding = 127
•BIOS Mode supported: Legacy and/or UEFI
• You can force install 'ANY' brand theme by reading and using the Force_Theme_[readme].txt
Editions for OEM Activation:
• Win10... • Home • Pro
• Win8.x... • Core • Pro
• Win7..... • Starter • Home Basic • Home Premium • Pro • Ultimate
• Vista..... • Starter • Home Basic • Home Premium • Business • Ultimate
• (Vista-Win10) If not known edition, branding only takes place.
Objective - add $oem$ folder to .iso /usb.
• $oem$ method can be used to apply activation & manufacturer brand to your Win10 • Win 8.x • Win 7 • Vista '.iso'/usb
• NOTE:- PC needs (Win8.x and Win10 'OEM-DM' • Win7 '2.1 slic' • Vista '2.0 slic') bios to apply genuine oem activation.
• Project includes optional Telemetry disabling for all supported OS's and adds domains to block through hosts file.
How To:
Win8.x|Win10
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and add custom 'ei.cfg' file to the same 'sources' folder and edit|save iso. Windows will install the edition identified from 'ei.cfg' file. (Project 'Options' folder includes 'ei.cfg' instructions). OOBE.cmd will call tool that will extract embedded 'OEM-DM' key from bios (if exists), and apply the serial during installation.
Win7
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'ei.cfg' file from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Win7' you want installed (ie. Starter • Home Basic • Home Premium • Pro • Ultimate)... if you don't delete 'ei.cfg' file, that's OK, just means Ultimate will install by default.
Vista
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'PID.txt' file (if exists) from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Vista' you want installed (ie. Starter • Home Basic • Home Premium • Business • Ultimate)... if you don't delete 'PID.txt' file, that's OK, just means serial used on that file will determine edition installed.
• Please read the 'readme' files included in the download folder, for additional information.
• "UltraISO" recommended to edit|save your .iso, preserving 'bootable' image.
Editions for OEM Activation:
• Win10.. • Technical Preview • Consumer Preview
• Win8.x... • Core • Pro
• Win7.... • Starter • Home Basic • Home Premium • Pro • Ultimate
• Vista.... • Starter • Home Basic • Home Premium • Business • Ultimate
• (Vista-Win10) If not known edition, branding only takes place.
Objective - add $oem$ folder to .iso /usb.
• $oem$ method can be used to apply activation & manufacturer brand to your Win10 • Win 8.x • Win 7 • Vista '.iso'/usb
• NOTE:- PC needs (Win8.x and Win10 'OEM-DM' • Win7 '2.1 slic' • Vista '2.0 slic') bios to apply genuine oem activation.
How To:
Win 10
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and edit|save iso. OOBE.cmd (Install.cmd) will extract embedded 'OEM-DM' serial from bios (if exists), and apply the serial during installation.
Win8.1
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and add custom 'ei.cfg' file to the same 'sources' folder and edit|save iso. Windows will install the edition identified from 'ei.cfg' file. (Project 'Options' folder includes 'ei.cfg' instructions). OOBE.cmd (Install.cmd) will extract embedded 'OEM-DM' serial from bios (if exists), and apply the serial during installation.
Win8.0
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and edit|save iso. Windows will install the edition that matches the embedded 'OEM-DM' serial in your bios (if exists).
Win7
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'ei.cfg' file from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Win7' you want installed (ie. Starter • Home Basic • Home Premium • Pro • Ultimate)... if you don't delete 'ei.cfg' file, that's OK, just means Ultimate will install by default.
Vista
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'PID.txt' file (if exists) from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Vista' you want installed (ie. Starter • Home Basic • Home Premium • Business • Ultimate)... if you don't delete 'PID.txt' file, that's OK, just means serial used on that file will determine edition installed.
• Please read the 'readme' files included in the download folder, for additional information
• UltraISO recommended to edit|save your .iso, preserving 'bootable' image
Included link for images to be used with System Brand Changer if users prefer using a desktop branding tool with a nice gui, created by Alphawaves.
VirusTotal Results:
OEM Query Tool v5.5: 2/57 (Due to WinRAR SFX file. False positive, it is safe) 3.5% False Positives
Multi OEM Project: 8/56 (Due to decryption method. False positive, it is safe) 14.0% False Positives
Whats New :
New look to the Project.log!
The OS and DMI/BIOS information now is displayed in a more structured format.
Re-worded some output lines which should make things a bit more easier to understand. Even
though the log is designed to help me find any problems, I wanted to make it more user friendly
in that it shows clearer progress of what MRP was doing during the installation process and not
be all technical jargon.
Adjusted some error checking areas.
Quite a bit of re-writing to the branding/theme script has been done, this is what takes the
time to get things ready for a release. If this script is altered in any way then testing takes
a lot longer due to its complex/sensitive structure.
DeCompile has been tweaked as well, more checks added to make sure that MRP will function
unless something happens it is not happy about.
If certain criteria is not met then as mentioned in another log entry below that the project
will still run but in Reduced Function Mode (RFM). In this mode certain sections may be
skipped, such as MSDM table checking, so for Win 8.x/10 your key will not be auto-inserted
or even checked.
This only happens if you have removed .Net framework 4.x, why you would want to do that is
not open for debate. Likewise for Vista/7 if .Net v2.x is removed certain sections will also
be skipped, but branding and activation should still take place providing there is any valid
DMI/SLIC information present.
Force_Theme routine has been revamped and with better error checking/parsing, it may not be 100%
foolproof, so check your spelling of the brand name if you use this feature!
Due to the changes in the Force_Theme section you will need to use the latest OEM's.7z file which is
provided within the main MRP archive. See Optional folder -> Force_Theme_[readme].txt for more details
on which brands are affected, not all brands are, only a select few that did not meet the new checking
routine was altered.
As a lot of work been done behind the scenes the version been bumped up instead of a being a minor
60.1 version.
|
