Hi, first of all let me introduce myself my name is Craig Roberts I am a coder for Roblox games but I am here primarily to get everything up to date and help the Unified Android Toolkit to grow again. Mark has been unwell for quite some time and is unable to use a keyboard or mouse and a lot of people who promised to answer emails and keep the site up to date for him (and for which he paid them) have let him down so I offered to step in and get everything back in working order again. This is his only source of income right now and I have known him for a long time so I wanted to help.
Email support and missing Toolkit codes: If you have sent an email and not been responded to then I apologise. I will start working through the backlog but missing codes will take priority so if you have purchased a code for a pro/ultimate version of the Toolkit and not had an answer please help me out, do not open a paypal dispute, email me at skipsoft.toolkit@gmail.com and I will send your code right away (during office hours). You can also go to http://skipsoft.net/donate/getcode.php and enter your paypal email to get your code. There seems to be a problem with paypal processing hotmail addresses which has caused a lot of unresponded payments and I assure you this has not been on purpose and will be sorted out.
Device Module Updates: I know a lot of modules are out of date and this is being recitifed right now. This morning I pushed AutoUpdates for current OnePlus devices (3, 3T, 5 and 5T) with support for all past and latest builds so they should all be up to date now. I am now starting on the Google/Nexus devices (Nexus5X, 6P, GooglePixelC, Pixel, PixelXL, Pixel2 and Pixel2XL) and AutoUpdates should/will be pushed today or tomorrow to bring them up to date. I will then start working on Samsung Device Updates and adding support for new devices, starting with the OnePlus6 which is an amazing device.
Please wish Mark well in his slow recovery, he is upset he cannot maintain the Toolkit but I have promised I will stick by it as it is a great kit he has developed over the years and has helped out many thousands of users. I reiterate this is his only source of income so please support him as best you can if the Toolkit has ever been a help to you (I know its saved my neck on more than 1 occasion which is why im here today). Any support and/or purchase of a code will help ease the worry of him looking after his family.
Feel free to retweet and share this post to get the message out that the Toolkit is not dead and we can make it great again (and help Mark out).
Thank you and stay tuned for more updates, Craig.
I apologise for my absence I have been back in hospital for a while but back and working now. Working on getting all updates done within next 2 days. Nexus/Pixel November images have been downloaded and support for October/November will be done today. SUHide flash option has been added to the root/unroot section if needed.
Also support for Pixel 2 and Pixel 2 XL will be added today. Root will not be added until stable custom recovery is available. Everything else should work (bootloader unlock, flashing stock image)
Support for the OnePlus 5 has now been added to the SkipSoft Unified Android Toolkit.
The device has only just been released so there is no custom recovery or firmware images available yet. This means no root but all basic functions should work fine and as soon as anything is released the device module will be updated.
XDA Support forum: OnePlus 5.
To add support for the new devices you can either download the Toolkit v1.6.4 from *HERE* or you can run ToolkitClean.exe (assuming you have already installed the Toolkit) and select option 62 to update the Toolkit.exe file to the latest version.
If anyone uses the OnePlus 5 device module please give feedback in the forum as to button combinations to get to fastboot mode and on the bootloader unlock option to make sure it works as expected.
Enjoy.
Most people probably think I have stopped development on the Toolkit as it has not been updated in a few months and emails have not been responded to. This is most definitely not the case and I would like to take a minute to explain and aplogise.
I was involved in an accident in January and had quite major injuries to my hands and arms. I have had multiple corrective surgery over the past few months but have not been able to use a computer at all. I asked a colleague to answer my emails but he has only answered about 10% and I have built up around 600 unanswered emails. The Toolkit makes nowhere near enough money to employ someone to help so its up to me to sort it out. My hands are well enough now to type and use a mouse but I have a huge backlog of emails and updates to get through so I am asking people to be patient with emails. I will start with the most recent and work my way backwards as there is no point in answering emails from 4 months ago, If you have written to me for an activation code then I would ask you and have not been answered I would ask you to send another email and I promise I will get back to you. A few people gave up waiting and asked for their money back through paypal and I have no problem with that but would like to say a big sorry to those people and hope they may come back to the Toolkit in the future. I will get back to everyone who has written to me, it may just take a while.
To make things even worse my hard drive crashed a few days ago and I have lost all my source files and configuration files. I am downloading files right now from my servers to rebuild the source files, reinstall programs and get back to a working position again.
On to updates and I uploaded new device files for all the Nexus and Google devices which cover up to March firmware and have download Nexus/Google May firmware images and will definitely be uploading AutoUpdates over the weekend. These AutoUpdates will be for Nexus6, Nexus 5X, Nexus 6P, Nexus 9, Nexus Player, Google Pixel C, Google Pixel and Google Pixel XL. Once they are done I will be adding support for the OnePlus 3T, Samsung 7 and Samsung 7 Edge and will try to add initial support for the Samsung S8 and S8 Plus. These will all be done in the next week. After that I will start updating all the Samsung devices (long overdue) and OnePlus devices. I want everything updated within the next 2-3 weeks to support the latest firmware.
Lastly (and I understand fully) support for the Toolkit has been hit hard due to my absence and lack of support and it needs a serious cash injection to keep going. If you use the Toolkit at all and it has helped you in any way I plead with you PLEASE consider donating to a Device module or buy the Ultimate mode to cover all devices present and future. Its well worth it and will be saving a very worthwhile project. Without your support I cannot with the Toolkit and will fight to keep it running to my last breathe.
To the people who do support the Toolkit I thank you from the bottom of my heart and pledge to keep building and growing the Toolkit into the future. I have some very exciting ideas how to improve it and would love to see them implemented.
If you made it this far without falling asleep, thank you again.
Mark (owner/operator of the Unified Android Toolkit project).
Changelog:
+The SuperSU Stable/SuperSU Beta version checker has been updated to detect sub versions [SR]. The toolkit catches the version from chainfires site but it only extracted the main version number (not any SR versions) so the latest SR4 to allow twrp and SuperSU to work together on the Gooel Pixel/XL would not be downloaded. This is now fixed and will update to ALL new versions.
+The Toolkit will now check for the latest adb/fastboot versions after device selection. If a newer version is found it will automatically be installed in the Toolkit folder so the latest support will be available for newer devices (especially the Google Pixel/XL).
+A Hidden option at device selection has been added [dp] which will disable/enable server pings before downloading files. This is only important for a few people that have problems when the Toolkit pings the server and then errors out, but can download files fine. This toggle should fix the problem. Only the Pro updates have support added to the config files to disable server pings before downloading model files but public support for the config files will be added as I release new public versions of the device config files.
These are some Important additions and I would strongly advise anyone using the Toolkit update. You can update the base version via any of the following 3 ways:
1. Make sure the Toolkit is closed. Run ToolKitClean from the Toolkit folder and select option 62 to update just the Toolkit.exe file
2. When the Toolkit starts it will check for the latest version. Accept this update to 1.5.6, make sure the installation folder is the same as your existing installation when prompted and choose update so you do not lose any model files, settings and Pro/Ultimate activation.
3. Download the full Toolkit installation from http://www.skipsoft.net/?p=1660 and install.
Mark.
Support for googles new Nexus replacements, the Pixel and Pixel XL Android SmartPhones have been added to the SkipSoft Unified Android Toolkit.
As there is no stock firmware or custom recovery images available yet the Toolkit is limited to its basic (yet still ample) functions. Disabled functions are flashing stock firmware images, which will be added as soon as they are available, and functions that require the use of a custom recovery image such as rooting. Drivers can be installed where needed, the bootloader unlocked where allowed (I do not know whether any carriers such as verizon have locked the bootloader but I assume the majority will be unlockable) and lots of other functions performed.
XDA Support forums: Google Pixel, Google Pixel XL.
To add support for the new devices you can either download the Toolkit v1.5.4 from *HERE* or you can run ToolkitClean.exe (assuming you have already installed the Toolkit) and select option 62 to update the Toolkit.exe file to the latest version.
If anyone uses the Google Pixel or Pixel XL device modules please give feedback in the forum as to button combinations to get to fastboot mode and on the bootloader unlock option to make sure it works as expected.
Enjoy, Mark.
!THIS IS A RECOMMENDED UPDATE TO FIX POSSIBLE PROBLEMS WITH TOOLKIT!
WHAT’S NEW [V1.5.3] 03RD SEP 2016
+Added much improved Drivers section in Device Selection Screen [DR] with new automated google drivers installer
+Improved Root file checker/downloader at device module startup where version numbers would not be updated under certain situations
+Bug fixes
I have spent about a week with these updates to fix problems with the Toolkit and also to improve the driver installer section. I will be carrying on with device module updates from saturday starting with the rest of the Android 7 support updates for Google/Nexus devices.
Mark.
Announcing the SkipSoft ULTIMATE drivers and adb Installer to make the task of getting your Android device connected that much simpler.
Yes I know there are loads of these about but they don’t tend to have any help or information about what you are doing or how to fix existing problems. THIS DOES.
This is a standalone version of the new drivers installer in The SkipSoft Unified Android Toolkit 1.5.3. You may not want to use the Toolkit and want to do things yourself so this is for you.
If you are having problems with getting your Android device communicating with your PC give the ULTIMATE drivers and adb Installer a go.
Link to Installer: ULTIMATE drivers and adb Installer
Mark.
Pro users already have the latest version. You do not need to do anything now but I am working on the March Updates.
Non Pro users have a few steps.
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the installation folder (or the Start Menu)
3. Select your device from the list
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Restart the Toolkit, select the device and new module files will be downloaded/installed
If you download the new module files without installing the updated Toolkit then you will be prompted to update to the latest version after selecting your device.
If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.
Enjoy, Mark.
DEVICE MODULE V1.0.6
Changelog:
+Fixed minor bug when using Toolkit to switch to different working device
+Added info in recovery flash option about rebooting before booting to recovery
+Added root/decryption support for MDA89D build with kpatch/decrytpion file
+Added fastboot erase commands to factory image flash for cleaner update
Pro users can just start the Toolkit as normal. After you have selected your device you will be notified there is an update available and can auto update. SIMPLE.
Non Pro users have a few extra steps.
1. Exit the Toolkit if it is open.
2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)
3. Select the Nexus 6P from the list (option 06)
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the Nexus 6P
5. Restart the Toolkit, select the Nexus 6P and new module files will be downloaded/installed
If you want to donate to the Nexus 6P project please do it through the Toolkit (after selecting the device at startup) so you get the right code fast.
Enjoy, Mark.
