ESLint v7.10.0 released We just pushed ESLint v7.10.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release. Add modern lights for your modern buildings. Ceiling and ground lights drop when their support blocks are broken. CMMC Model Version 1.0 Version 1.0 A-4 CAPABILITY PRACTICES Level 1 (L1) Level 2 (L2) Level 3 (L3) Level 4 (L4) Level 5 (L5) C002 Control internal system access AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. FAR Clause 52.204-21 b.1.ii.
[TOOLKIT] SKIPSOFT UNIFIED ANDROID TOOLKIT
The Unified Android Toolkit supports 37 Android devices: Galaxy Nexus, Nexus 4, Nexus 5, Nexus 6, Nexus 7 [2012], Nexus 7 [2013], Nexus 9, Nexus 10, Nexus Player, Nexus 5X, Nexus 6P, Google Pixel C, Google Pixel (2016), Google Pixel XL (2016), OnePlus 1, OnePlus 2, OnePlus X, OnePlus 3, OnePlus 3T, OnePlus 5, Samsung Galaxy S3, Samsung Galaxy S3 Mini, Samsung Galaxy S4, Samsung Galaxy S4 Mini, Samsung Galaxy S5, Samsung Galaxy S6, Samsung Galaxy S6 Edge, Samsung Galaxy Note 2, Samsung Galaxy Note 3, Samsung Galaxy Note 4, Samsung Galaxy Note 5, Samsung Galaxy Note 8.0 [2012], Samsung Galaxy Note 10.1 [2012], Samsung Galaxy Note 10.1 [2014], Samsung Galaxy TabS 8.4 and 10.5 models [2014], Samsung Galaxy Camera (smartcamera) and Samsung Galaxy Gear [smartwatch] on Android Only. The Galaxy Gear Toolkit module will not work if the watch is using the Tizen operating system. There is also a Basic Android Toolkit included which any Android device can use.
Devices to be added soon:
Samsung Galaxy S7, Samsung Galaxy S7Edge, Samsung Galaxy S8, Samsung Galaxy S8 Plus.
Samsung Galaxy S7, Samsung Galaxy S7Edge, Samsung Galaxy S8, Samsung Galaxy S8 Plus.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
Eset cyber security pro 6 8 3. * Install correct adb/fastboot drivers automatically
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X, 6, 6P, 9, Google Pixel C, Google Pixel, Google Pixel XL
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X, 6, 6P, 9, Google Pixel C, Google Pixel, Google Pixel XL
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google N-Nexus O-OnePlus S-Samsung
————————————————————–
————————————————————–
————————————————————–
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS*HERE*
————————————————————–
DOWNLOAD THE UNIFIED ANDROID TOOLKIT*HERE*
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: Grarak for TWRP custom recovery on OnePlus 3, ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
————————————————————–
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
————————————————————–
PLEASE READ THE HELP PAGE *HERE* IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
————————————————————–
1. INSTALLING DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION ‘1’ IN THE MAIN MENU OR OPTION ‘DR’ AT STARTUP.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select ‘browse my computer’ and then ‘Let me pick from a list’.
If no adb interface driver appears in the list then untick ‘Show compatible hardware’ and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select ‘browse my computer’ and then ‘Let me pick from a list’.
If no adb interface driver appears in the list then untick ‘Show compatible hardware’ and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick ‘Always allow’ then click ‘ok’.
————————————————————–
2. USING THE UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type ’00’ to enter your activation code and enable pro features, ‘i’ will take you to the Information and Help Section, ‘a’ will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the “any build” option to root any build (useful if your build is not listed).
————————————————————–
ChangeLog:
ToolKit v1.6.1 (15th May 2017)
+Added support for OnePlus 3T device up to latest build
ToolKit v1.6.1 (15th May 2017)
+Added support for OnePlus 3T device up to latest build
ToolKit v1.5.0 (30th June 2016)
+Fixed All OnePlus devices loading OnePlusOne module after AutoUpdate
+Added OnePlus USB driver pack installer to driver options
+Fixed All OnePlus devices loading OnePlusOne module after AutoUpdate
+Added OnePlus USB driver pack installer to driver options
ToolKit v1.4.9 (27th June 2016)
+Added support for OnePlus 1, 2, 3 and X devices up to latest build
+Made some improvements at startup and fixed some minor bugs
+Added support for OnePlus 1, 2, 3 and X devices up to latest build
+Made some improvements at startup and fixed some minor bugs
ToolKit v1.4.8 (16th June 2016)
+Added support for Samsung Galaxy Note 5 device
+Added support for Samsung Galaxy Note 5 device
ToolKit v1.4.7 (10th June 2016)
+ALL USERS PLEASE UPDATE TO THIS VERSION AS FUTURE UPDATES WILL BE BUILT ON THIS
+All Google,Nexus,Samsung device modules are updated to latest versions
+Fixed SuperSU downloading incorrect versions for Stable and Beta releases
+Toolkit checks for latest root zip files after device selection for ALL users
+Lots of bug fixes, improvements and additions for public users
+ALL USERS PLEASE UPDATE TO THIS VERSION AS FUTURE UPDATES WILL BE BUILT ON THIS
+All Google,Nexus,Samsung device modules are updated to latest versions
+Fixed SuperSU downloading incorrect versions for Stable and Beta releases
+Toolkit checks for latest root zip files after device selection for ALL users
+Lots of bug fixes, improvements and additions for public users
ToolKit v1.4.5 (23rd Dec 2015)
+Added support for GOOGLE PIXEL C TABLET [RYU]
+Added support for GOOGLE PIXEL C TABLET [RYU]
ToolKit v1.4.4 (09th Dec 2015)
+Updated base files to enable SuperSU Systemless root method on all devices
THIS VERSION IS REQUIRED FOR ALL NEW DEVICE MODULES TO WORK SO PLEASE UPDATE NOW
+Updated base files to enable SuperSU Systemless root method on all devices
THIS VERSION IS REQUIRED FOR ALL NEW DEVICE MODULES TO WORK SO PLEASE UPDATE NOW
ToolKit v1.4.3 (27th Oct 2015)
+Added support for HUAWEI NEXUS 6P [ANGLER]
+Added support for HUAWEI NEXUS 6P [ANGLER]
ToolKit v1.4.2 (21st Oct 2015)
+Added support for LG NEXUS 5X [BULLHEAD]
+Updated ToolkitClean.exe to update Toolkit.exe base file to latest version
+Updated Toolkit installable Apps to latest [busybox free, root checker, easy backup, efs backup]
+Toolkit will now check needed files at startup and download if needed
+Added support for LG NEXUS 5X [BULLHEAD]
+Updated ToolkitClean.exe to update Toolkit.exe base file to latest version
+Updated Toolkit installable Apps to latest [busybox free, root checker, easy backup, efs backup]
+Toolkit will now check needed files at startup and download if needed
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
ToolKit v1.4.0 (05th May 2015)
+Added support for Samsung Galaxy S6 [SUPPORTED VARIANTS BELOW]
SM-G920F, SM-G920P, SM-G920T, SM-G920R4, SM-G920W8, SM-G920I
+Added support for Samsung Galaxy S6 Edge [SUPPORTED VARIANTS BELOW]
SM-G925F, SM-G925P, SM-G925T, SM-G925R4, SM-G925W8, SM-G925I
+All Samsung device modules updated to latest versions
+A lot of fixes and updates to Samsung code
+Added ToolkitClean program to reset certain modules, hard reset, uninstall
+Added support for Samsung Galaxy S6 [SUPPORTED VARIANTS BELOW]
SM-G920F, SM-G920P, SM-G920T, SM-G920R4, SM-G920W8, SM-G920I
+Added support for Samsung Galaxy S6 Edge [SUPPORTED VARIANTS BELOW]
SM-G925F, SM-G925P, SM-G925T, SM-G925R4, SM-G925W8, SM-G925I
+All Samsung device modules updated to latest versions
+A lot of fixes and updates to Samsung code
+Added ToolkitClean program to reset certain modules, hard reset, uninstall
ToolKit v1.3.5 (14th Apr 2015)
+Added support for Asus Nexus Player device
+Added support for Asus Nexus Player device
ToolKit v1.3.4 (09th Jan 2015)
+Added support for Samsung Galaxy Note 4, Samsung Galaxy Note 10.1 [2014] and Samsung Galaxy TabS 8.4 and 10.5 [2014] devices
+Updated Toolkit installable apps (root checker, busybox installer, easy backup, efs backup) for ALL device modules
+Updated rooting procedure for above devices
+Updated procedure for renaming recovery restore files for above devices
+Added md5 check for in-toolkit public update download for future versions
+Added support for Samsung Galaxy Note 4, Samsung Galaxy Note 10.1 [2014] and Samsung Galaxy TabS 8.4 and 10.5 [2014] devices
+Updated Toolkit installable apps (root checker, busybox installer, easy backup, efs backup) for ALL device modules
+Updated rooting procedure for above devices
+Updated procedure for renaming recovery restore files for above devices
+Added md5 check for in-toolkit public update download for future versions
ToolKit v1.3.3 (08th Dec 2014)
+Added support for Nexus6 and Nexus9 devices
+Updated build support for all Toolkit devices [where builds available]
+Major updates to code and updated available apps
+Added support for Nexus6 and Nexus9 devices
+Updated build support for all Toolkit devices [where builds available]
+Major updates to code and updated available apps
ToolKit v1.2.8 (25th April 2014)
+Added support for Samsung Galaxy Camera (2012 model) device
+Added support for Samsung Galaxy Note 10.1 (2012 model) device
+Added fix for extSdCard write permissions from installed apps in Android 4.4+ (where device needs it)
+Added support for Samsung Galaxy Camera (2012 model) device
+Added support for Samsung Galaxy Note 10.1 (2012 model) device
+Added fix for extSdCard write permissions from installed apps in Android 4.4+ (where device needs it)
ToolKit v1.2.7 (16th April 2014)
+Added support for Samsung Galaxy S5 (SmartPhone) device
+Added support for Samsung Galaxy Note 8.0 (2012 model) device
+Updated some code in the Toolkit initialisation program
+Added Odin v3.0.9 (for new devices now, rest will be updated via auto update)
+Updated busybox free installer by stericson to latest version (v12)
+Added support for Samsung Galaxy S5 (SmartPhone) device
+Added support for Samsung Galaxy Note 8.0 (2012 model) device
+Updated some code in the Toolkit initialisation program
+Added Odin v3.0.9 (for new devices now, rest will be updated via auto update)
+Updated busybox free installer by stericson to latest version (v12)
ToolKit v1.2.6 (31st March 2014)
+Added support for Samsung Galaxy S4 Mini (SmartPhone) device
+Added support for Samsung Galaxy Gear (Smartwatch) device
+Added support for Samsung Galaxy S4 Mini (SmartPhone) device
+Added support for Samsung Galaxy Gear (Smartwatch) device
ToolKit v1.2.5 (21st March 2014)
+Added support for Samsung Galaxy Note 3 (see supported builds page for variants covered)
+Added ALLINONE procedure back for Samsung modules to root, flash recovery, install busybox and rename recovery restore files via TWRP openrecoveryscript
+Added fix for “Superuser/SuperSU has stopped” message after rooting and rebooting
+Added more text in the Information section
+Minor bug fixes
+Added support for Samsung Galaxy Note 3 (see supported builds page for variants covered)
+Added ALLINONE procedure back for Samsung modules to root, flash recovery, install busybox and rename recovery restore files via TWRP openrecoveryscript
+Added fix for “Superuser/SuperSU has stopped” message after rooting and rebooting
+Added more text in the Information section
+Minor bug fixes
ToolKit v1.2.4 (10th March 2014)
+Added support for Samsung Galaxy S3, Samsung Galaxy S3 Mini, Samsung Galaxy S4 and Samsung Galaxy Note 2
+Updated support for latest builds in all device modules
+Root options support insecure boot and custom recovery methods [all rewritten]
+Added KNOX notification disabler for Samsung modules
+Added Root Checker to check the status of your root/busybox
+Added philz_touch Advanced cwm recovery to Samsung modules [will be added to Nexus modules soon]
+Added more help screens to the Information section and added ability to save screen and send to default printer
+Added option in build selection screen to disable all adb root functions [custom recovery functions available]
+Toolkit will disable insecure boot functions if insecure boot image not available
+Re-wrote most of the code to Change the way lots of functions work [more efficient and more stable]
+Many more changes I can’t think of right now
+Added support for Samsung Galaxy S3, Samsung Galaxy S3 Mini, Samsung Galaxy S4 and Samsung Galaxy Note 2
+Updated support for latest builds in all device modules
+Root options support insecure boot and custom recovery methods [all rewritten]
+Added KNOX notification disabler for Samsung modules
+Added Root Checker to check the status of your root/busybox
+Added philz_touch Advanced cwm recovery to Samsung modules [will be added to Nexus modules soon]
+Added more help screens to the Information section and added ability to save screen and send to default printer
+Added option in build selection screen to disable all adb root functions [custom recovery functions available]
+Toolkit will disable insecure boot functions if insecure boot image not available
+Re-wrote most of the code to Change the way lots of functions work [more efficient and more stable]
+Many more changes I can’t think of right now
ToolKit v1.2.0 (04th December 2013)
+Added support for the latest builds for all devices
+Updated Superuser versions
+Updated CWM Recovery for the Nexus 5 to the official 6.0.4.5 version
+Added the Information/Help Section to the Model/Build Selection screen to view information easier
+Added more text throughout the Toolkit to clarify parts
+Minor bug fixes
+Added support for the latest builds for all devices
+Updated Superuser versions
+Updated CWM Recovery for the Nexus 5 to the official 6.0.4.5 version
+Added the Information/Help Section to the Model/Build Selection screen to view information easier
+Added more text throughout the Toolkit to clarify parts
+Minor bug fixes
ToolKit v1.0.0 (14th November 2013)
+Initial release
+Initial release
————————————————————–
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
Last updated: $Date: 2011-09-07 11:08:21 -0400 (Wed, 07 Sep 2011) $ by $Author: CloyceS $
(To check for possible updates to this document, pleasesee http://www.spec.org/cpu2006/Docs/ )
Contents
I. Introduction
II. Changes to system version requirements
A. Linux: a variety of toolsets
B. Unsupported toolsets: BSD dropped; Alpha updated.
III. Benchmark source code changes
IV. Run Rules Changed
V. New and Updated Features
A. New sysinfo
B. Changes to the runspec command
C. Changes to reports
D. Changes to config files
Clarify V1 2 0 Hdi
E. Changes to utility programs
F. Changes to log files
G. Changes to flags files
1. Summary of changes
2. Symptoms of old flags files
VI. Problems fixed by SPEC CPU2006 V1.2
Appendix: Open source updates
Note: links to SPEC CPU2006 documents on this web page assume that you are reading the page from a directory that also contains the other SPEC CPU2006 documents. If by some chance you are reading this web page from a location where the links do not work, try accessing the referenced documents at one of the following locations:
- The $SPEC/Docs/ (Unix) or %SPEC%Docs (Windows) directory on a system where SPEC CPU2006 has been installed.
- The Docs/ directory on your SPEC CPU2006 distribution DVD.
I. Introduction
SPEC CPU2006 V1.2 is an incremental update to SPEC CPU2006 V1.1. Results generated with SPEC CPU2006 V1.2 are comparableto results from other V1.x releases and vice versa. SPEC CPU2006 V1.2 is intended to improve compatibility, stability,documentation and ease of use.
If you have already used SPEC CPU2006 V1.0 or V1.1 andalready have configuration files, it is recommended that you read through this document.
Here are the top 3 changes to user-visible behavior that may cause surprises. You should be aware ofthese before using SPEC CPU2006 V1.2:
- There is a new example sysinfo program, which is enabled by default, and which fills out some of your system information/documentation for the results generated by a run. You may need to adjust your config file.
- The structure of flags files has changed. If you are doing reportable runs, this change *will* affect your preparation of final disclosures with all required information.
- specbzip2 has been removed. It is replaced by specxz
There are other changes, including bugfixes, better reporting of sponsors, more flexibility in config files, and much better environment logging. Please read on!
II. Changes to system version requirements
SPEC's toolset was updated and rebuilt for all supported operating systems. See the list of supported platforms in system-requirements.html.
For some (but not all) platforms, the tools rebuild has caused a change to the minimum required level of the OS:
Operating System Requirements for SPEC CPU2006 | ||
---|---|---|
OS | Former minimum | V1.2 minimum |
AIX PowerPC | AIX 5L V5.1 | AIX 5L V5.3 |
HP-UX IPF | HP-UX 11iv2 | HP-UX 11iv3 |
HP-UX PA-RISC | HP-UX 11iv2 | HP-UX 11iv31 |
MacOS X PowerPC | MacOS X 10.2.8+ | MacOS X 10.3 |
Please ensure that you meet the minimum required version prior to installing SPEC CPU2006 V1.2.
II.A. Linux: a variety of toolsets
There are many Linux distributions. SPEC has made an effort to support a wide variety of them. For details, please seethe Linux table in system-requirements.html.
II.B. Unsupported toolsets: BSD dropped; Alpha updated.
- SPEC CPU2006 V1.1 provided unsupported tools built on BSD. These toolsets are not present in SPEC CPU2006 V1.2.
- SPEC CPU2006 V1.1 provided tools built on Digital Unix V4.0F. For SPEC CPU2006 V1.2, the tools have been rebuilt on Tru64 Unix V5.1B.
Caution:
- Unsupported toolsets are provided as a courtesy, as a service to users who may have the listed platform(s).
- Unsupported toolsets have been tested much less extensively than other tool sets and might or might not work.
- More importantly, some of the benchmarks themselves have not been ported for the environments represented by the unsupported toolsets:
- Therefore, if you use an unsupported toolset, you will need to dedicate time to a porting effort.
- Please especially notice that it is impossible to do a reportable run on an unsupported system until such time as SPEC approves any source changes and/or portability flags needed for such system.
- For more information about obtaining SPEC approval for source changes, see techsupport.html.
III. Benchmark source code changes
The following benchmark changes were made in V1.2:
- 403.gcc: The input files were renamed to prevent them from being inadvertantly removed by the tools during multi-pass compilation. If you are studying the benchmarks with your own tools, or outside the SPEC tool harness, you may need to adjust your procedures.
- 447.dealII
- Enable compilation with compilers such as Microsoft Visual C++ 2010 that require even unreachable return values to have the correct type, or which require normally implicit casts to be explicit when '0' is an argument to a perfect forwarding function.
- Allow compilation with Windows C++ compilers using the EDG 4.0 or later front end (for example PGI 2010)
- Enable compilation with the Apache Standard C++ Library
- 483.xalancbmk
- Added portability changes for PGI on Mac OS X
- Enable compilation with Microsoft Visual C++ 2010, or with the Apache Standard C++ Library.
IV. Run Rules Changed
Publishable results must adhere to the SPEC CPU2006 Run Rules. In SPEC's opinion, the changes do not affect thecomparabilty of results between SPEC CPU2006 V1.0, V1.1, and V1.2, because the changes are primarily clarifications of theexisting rules.
Here is a list of the rules that have have been changed, excerpted from the change history in runrules.html. (Reminder: as noted above, linksgo to the copy in the same directory as the document you are reading now; the most recent copy is the one atwww.spec.org)
- At the top, clarify that the rules may be updated from time to time.
- In rule 4.2, note that system descriptions may be edited after a test.
- Add rule 4.2.1.1 about identifying equivalent systems.
- In rule 4.2.3, reference the updated mechanism for setting the auto parallel field.
- In rule 4.2.4(g), emphasize that all tuning must be documented.
- In rule 4.2.5 clarify which information belongs in flags files vs. other locations.
- Add rule 4.2.7 on how to document cross compiles, referencing it from 2.0.6.
- Replace rule 4.7 with a reference to the SPEC-wide Fair Use rule.
Regarding the last item above, please note that SPEC has centralized the Fair Use rules for all benchmarks to a singlelocation, for the convenience of those who use SPEC results. The Fair Use rules for all SPECbenchmarks are now posted at a location which is intended to be easily memorable:
V. New and Updated Features
These user-visible features are new, updated, or newly documented for SPEC CPU2006 V1.2:
V.A. New sysinfo
The example sysinfo program is substantially expanded. You can use it toautomatically capture various system configuration items on systems running Linux, Mac OS X, Solaris, and Windows.
Note that the example sysinfo program isenabled by default!
It is on by default because SPEC believes that its virtues outweigh its limitations, both of which are summarized in thissection.
By default, there will be more information in your platform notes. For example, by default Windows systems will includelines such as these:
Also by default, the example sysinfo program will try to parse the above information into system description fields,such as:
Virtues of the example sysinfo program
- The primary value of a sysinfo program is that it creates a contemporaneous record of the system under test.
- The record is created under the control of the SPEC toolset.
- Because system configuration information is automatically recorded, it is not subject to human transcription error.
- Therefore, the example sysinfo program can remove ambiguity such as 'I remember that I upgraded the version of theoperating system, but I can't quite recall whether that was before or after I did the re-run of the SPECfp2006 test.'
- The utility works with Windows, Mac OS X, Solaris, and Linux.
It is hoped that users will find it useful that the information is recorded and that some fields are automaticallypopulated, under program control, contemporaneously with your test.
Limitations of the example sysinfo program and likely surprises
- SPEC is aware that there are many dependencies and differences among hardware and software platforms, and that thesechange from time to time. Therefore, the example sysinfo program is only an 'example': you may need to modify the examplein order to use it on your system.
- For the same reason, SPEC may decide to update the utility fromtime to time.
- As of the release of V1.2, the example does not work with other operating systems, such as AIX, IRIX, and HP-UX.
- You may see WARNINGS when you use it, because the utility is likely towrite fields that are already in your config file:If you see warnings such as the above, you will need to decide what to do about them. There are four options suggested inconfig.html.
Details about the sysinfo utility may be found in the config.html section About sysinfo, including how to selectively enable output types, how to resolve conflicting field warnings, and how to write your own sysinfo utility.
V.B. Changes to the runspec command
The --speed option is effective now for runspec, in addition torawformat. A config file containing rate = 1 can therefore be overridden from the commandline, and used for a SPECspeed run by adding --speed to the runspec line. In general, the command line takes precedence over the config file, sothis change makes the switch more compatible with how other switches work.
V.C. Changes to reports
If the test sponsor is not the same as the hardware vendor, this fact is now noted more prominently in the generatedHTML, Postscript, and PDF reports.
V.D. Changes to config files
- The restrictions about placement of certain config file options have been slightly relaxed This change may be of especial interest to users who would like to create macros that write to both the header section and to other config file sections.
- You can now add tags to all notes, which may allow you to organize your system information in a manner that better suits your own categories for describing it.
- You can now use += (plus equals) for options that are sent to specmake, an option that increases flexibility. (This feature should be used with caution, as described in the config.html.)
- The example sysinfo program is called by default.
V.E. Changes to utility programs
- The program specbzip2 is no longer present. Instead, compression is done via specxz, from XZ Utils 5.0.0. Switching compression programs has reduced the size of SPEC distribution media. If you have written scripts that rely on specbzip2, it will be necessary to either retain a copy of specbzip2 from your V1.1 kit, or to change your scripts to specxz. If you make the change, you will also probably notice that specxz produces smaller files.Note that switches commonly used with specbzip2 are also supported by specxz.
- The specdiff utility now removes prior outputs, thereby eliminating a prior source of confusion.
- The port_progress utility now allows selective reporting by tuning for convenience during debugging.
- The printpath utility has been documented. It may help you avoid hard-to-diagose path surprises.
- The output of specinvoke -nn is expanded to include information about environment variables, which may be very useful when doing runs outside of the SPEC harness for debugging or for tuning.
- You can also, now, control whether specinvoke continues or exits after individual workload failures. This feature is primarily of interest only during debugging.
V.F. Changes to log files
- You may notice that the success message has changed to indicate power usage.The extra fields are present because the SPEC CPU toolset is used in multiple SPEC benchmarks; measurement of power is not a supported feature in SPEC CPU2006 V1.2. You may ignore these fields.
- If the preENV feature is used, runspec is restarted with the requested environment change. For SPEC CPU2006 V1.1, the top of the log file had the second, automatically-generated runspec command, and the environment settings were not recorded in the log. Now, with SPEC CPU2006 V1.2, it has the command that the user actually entered, and the settings are logged.It is expected that this change will remove a source of confusion, while adding very useful information to the log.Example: Consider this simple config file that runs the test workload of 401.bzip2 once, with an environment setting of 32 threads:Here is its behavior with SPEC CPU2006 V1.1:Here is its behavior with SPEC CPU2006 V1.2:Notice above that the runspec command matches what the user entered, and the environment setting is logged.
V.G. Changes to flags files
V.G.1. Summary of changes
| Element order, from flag-description.html: |
V.G.2. Symptoms of old flags files
You may realize that you are using an old-format flags file if you see a message similar to this:
The problem above is that although the named file (/cpu2006/V1.2/config/Oracle-Solaris-Studio12.2.xml) has useful information about the tested platform, the information needs to be updated and put into new locations. For SPEC CPU2006 V1.2, instead of using a platform element, you need to use a platform file. The message above is telling you that there is no element named 'platform_settings' (as of V1.2).
![Clarify Clarify](https://windows-cdn.softpedia.com/screenshots/Clarify_9.png)
An example of how the above error can be resolved is available in flag-description.html.
VI. Problems fixed by SPEC CPU2006 V1.2
Here is a list of the problems have been fixed, excerpted from the table of contents of errata.html. (Reminder: as noted above, links goto the copy in the same directory as the document you are reading now; the most recent copy is the one atwww.spec.org)
8. Your vendor has notdefined POSIX macro WEXITSTATUS with invalid flags file
9. Error: corrupt resultfile; unable to format after failed FDO build
10. WARNING: accessor'benchmark' not found during reportable run
12. Style settings may appear ineffective whenformatting results with multiple flags files
![Clarify Clarify](https://mac-cdn.softpedia.com/screenshots/Clarify_4.jpg)
14.WARNING: accessor'setup_error' not found with minimize_rundirs
15. Index utility prints Expected 17 fields; got 16 (base_copies, ..
16.Individual benchmarkselection is not allowed for a reportable run
18. Incorrect spelling: 'Evironment' when usingpreENV
19. The config file feature rate=1 is not recommended
20. During installation 'Error running runspec tests' due to time.t 'FAILED at test 2'
21. During installation 'Error running runspec tests' due to tie.t not ok 20 'unlocalisation of tiedhashes'
22. Some test or train failures may not beproperly reported.
Appendix: Open source updates
The SPEC CPU toolset includes components from many open source programs. Where required by licenses, you will find theoriginal sources, and SPEC's modifications, in this directory:
- $SPEC/redistributable_sources/ (Unix)
- %SPEC%redistributable_sources (Windows), or
- on your SPEC CPU2006 DVD in the directory redistributable_sources/.
Most users have little reason to care about the internal implementation of SPEC's toolset, and if that describes you,feel free to skip this section. It is here for two reasons: (1) If you encounter a problem while using a SPEC-providedtool, it may be useful to know where it came from, and the version thereof. (2) SPEC is thankful to the open sourcecommunity, and gratefully acknowledges the updates that have gone into SPEC CPU2006 V1.2.
Clarify V1 2 0 3
For SPEC CPU2006 V1.2, the sources of these tools have been updated:
Tool | Based on | Was | Now |
---|---|---|---|
specmake | GNU make | 3.81 | 3.82 |
specperl | Perl | 5.8.8 | 5.12.3 |
specpp | filepp | 1.7.1 | 1.8.0 |
spectar | GNU tar | 1.15.1 | 1.25 |
specrxp | RXP | 1.4.8 | 1.5.0 |
Clarify V1 2 0 1
Newly added are:
- specxz, from XZ Utils 5.0.0, replacing specbzip2
- specsum, extended from md5sum.c of coreutils 8.9 (plus portions of gnulib) replacing the former md5sum 1.1 from textutils.
These perl modules are updated:
Module | Was | Now |
---|---|---|
Algorithm::Diff | 1.15 | 1.1902 |
Font::AFM | 1.18 | 1.20 |
HTML::Parser | 3.45 | 3.68 |
HTML::Tagset | 3.04 | 3.20 |
IO::Stringy | 2.108 | 2.110 |
LWP (libwww-perl) | 5.803 | 5.837 |
MailTools | 1.58 | 2.04 |
MIME-tools | 5.417 | 5.428 |
PDF::API2 | 0.41 | 0.73 |
Text::CSV_XS | 0.23 | 0.79 |
TimeDate | 1.16 | 1.20 |
URI | 1.35 | 1.56 |
XML::NamespaceSupport | 1.08 | 1.11 |
XML::SAX | 0.12 | 0.96 |
XML::SAX::ExpatXS | 1.08 | 1.31 |
Note that any perl modules used in 400.perlbench are not affected. 1password 5 0 – powerful password manager. The benchmark has its own copies, set at the releaseof SPEC CPU2006 V1.0, and these modules have not been updated.
Clarify V1 2 0 2
These perl modules have been newly added in SPEC CPU2006 V1.2:
- String::ShellQuote 1.04
These (non-perl) modules have been updated:
Module | Was | Now |
---|---|---|
expat | 1.95.8 | 2.0.1 |
These open source modules are unchanged in SPEC CPU2006 V1.2:
- dmake 4.11
- File::NFSLock 1.20
- GD 1.19
- makedepf90 2.8.8
- ntzsh (an early version of what later became WinZsh)
Copyright 2011 Standard Performance Evaluation Corporation
All Rights Reserved
All Rights Reserved