• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[TOOL] SKIPSOFT ANDROID TOOLKIT -Google Pixel XL- Drivers,Unlock,Firmware,Root

Search This thread

TonikJDK

Senior Member
Dec 9, 2012
2,637
1,318
Did anyone ever figure this out? If I flash the TWRP image manually with fastboot or use this Toolkit (which I donated to even though it hasn't ended up working) I just get stuck at the TWRP flash screen. I never get any menus to flash the TWRP zip or anything else. Used the toolkit to return to stock and start over. Manually returned to stock and started over. It makes no difference. Whatever I do I get stuck at the TWRP screen when I flash the temporary TWRP image. Can't get past it.

Did you used to be on the O beta? If so your partitions are messed up. You need to flash stock. The switch active partitions and flash stock again.
 
  • Like
Reactions: jhs39

jhs39

Senior Member
Oct 8, 2015
2,485
716
Chicago
Did you used to be on the O beta? If so your partitions are messed up. You need to flash stock. The switch active partitions and flash stock again.

Did that but now I'm having another problem. My computer is no longer recognizing the Pixel XL as a device for USB transfer, only for PTP transfer, so now I can't transfer the TWRP and DU zips to the internal storage of my phone before trying the TWRP boot image again. This phone is literally driving me insane. :mad:

---------- Post added at 09:40 PM ---------- Previous post was at 09:38 PM ----------

Did that but now I'm having another problem. My computer is no longer recognizing the Pixel XL as a device for USB transfer, only for PTP transfer, so now I can't transfer the TWRP and DU zips to the internal storage of my phone before trying the TWRP boot image again. This phone is literally driving me insane. :mad:

I miss the days when you could install a custom recovery and ROM on a phone without getting a migraine.

---------- Post added at 10:32 PM ---------- Previous post was at 09:40 PM ----------

Did you used to be on the O beta? If so your partitions are messed up. You need to flash stock. The switch active partitions and flash stock again.

That seems to have done the trick. Thanks!
 

jhs39

Senior Member
Oct 8, 2015
2,485
716
Chicago
I'm having an odd problem with the Skipsoft Toolkit. I installed it on my Windows 10 computer. When I click on the icon in the start menu to open the program an error message comes up so quickly I can't read it then the program closes again. I checked my antivirus and antimalware programs and neither seem to be flagging the Toolkit as a threat. But if I click on the program icon where the program is physically installed on my C drive then it opens fine. The regular ToolKitClean icon in the start menu works fine. Is there something I can do to get this program to open normally on my computer? The program path that the start menu icon points to appears to be correct, so I can't figure out why this is happening.
 
Last edited:

Foxhoundz

Member
Aug 22, 2012
20
2
Is it possible to provide a newer build version without having to buy this thing? The instructions, the UI, and the functionality of this thing is very convoluted.
 

jhs39

Senior Member
Oct 8, 2015
2,485
716
Chicago
Is it possible to provide a newer build version without having to buy this thing? The instructions, the UI, and the functionality of this thing is very convoluted.
I bought this thing and can't get any support for it. I ended up flashing everything manually because I couldn't get the kit to work properly and using manual fastboot commands turned out to be much easier. I'm admittedly not a fan of kits but I thought i would try one in this case because I wasn't completely comfortable flashing on this phone. I still ended up manual flashing. The kit just sent me around in circles and never got past the splash screen of the fastboot version of TWRP. Then it would have me repeat the same steps again and again to get the same results again and again.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,065
Norfolk
AutoUpdate Available for Google Pixel XL device module [Ultimate/PRO Users Only]

Changelog:
[06TH JUL 2017]
+Added FULL Support for July builds [Android 7.1.2 NHG47O,NJH47D,NKG47M,NZH54B]
+Added above STOCK and OTA images to download/flash directly from Toolkit using option 9,1 [firmware download/flash] or 10,1 [ota download/sideload]
+Added 'secret' developer section at startup [option ds] to download/make model files for samsung and google devices to send to [email protected] to speed up updates. May not help anyone but I will add to it with more features
[23RD JUN 2017]
+Updated base version to 1.6.4 to add OnePlus 5 support plus enhancements
+Fully integrated Custom Build loader in device module for Builder/Ultimate users
+Fixed file not found error message on certain openrecoveryscript options
[13TH JUN 2017]
+Added NEW ULTIMATE FEATURE to add build support for any supported Toolkit device from download link, firmware or boot/recovery images. More Info at skipsoft.net

If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link *HERE* so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy.
 

Ad.Shk2

Senior Member
Sep 25, 2012
503
173
Mississauga
I keep running into weird issues or bootloops trying to root this dang phone ... Using SKIPSOFT toolkit for everything.

Scenario-1: Unlocked BL, flashed TWRP and Verisign V8. Reboot into recovery - no recovery present. Flashed Google Factory image to get everything back to normal.
Scenario-2: Unlocked BL, flashed TWRP and Verisign V8, Flash Resurrection Remix. While rebooting into system, get a message that there is no OS, but still boots up into ROM. Reboot into recovery to flash SuperSU, TWRP is gone! only Custom recovery!!
Scenario-3: In continuation to Scenario-2, installed TWRP again, phone goes into TWRP Bootloop! Everytime TWRP boots up asking for password, I enter password, it reboots into TWRP again. So flash Google factory images again!!!
Scenario-4: Install everything again, reboot into recovery , flash SuperSU for root, Bootloop into RamDump!!!!!

Now I have just flashed the google factory image and locked the bootloader. I cant believe Ive given up!

This is the first time I have wasted a whole day trying to unlock/root/install a custom ROM on a phone. What am I doing wrong?????
 
Last edited:

3aucla1r3

Senior Member
Dec 11, 2013
137
62
South Carolina
I keep running into weird issues or bootloops trying to root this dang phone ... Using SKIPSOFT toolkit for everything.

Scenario-1: Unlocked BL, flashed TWRP and Verisign V8. Reboot into recovery - no recovery present. Flashed Google Factory image to get everything back to normal.
Scenario-2: Unlocked BL, flashed TWRP and Verisign V8, Flash Resurrection Remix. While rebooting into system, get a message that there is no OS, but still boots up into ROM. Reboot into recovery to flash SuperSU, TWRP is gone! only Custom recovery!!
Scenario-3: In continuation to Scenario-2, installed TWRP again, phone goes into TWRP Bootloop! Everytime TWRP boots up asking for password, I enter password, it reboots into TWRP again. So flash Google factory images again!!!
Scenario-4: Install everything again, reboot into recovery , flash SuperSU for root, Bootloop into RamDump!!!!!

Now I have just flashed the google factory image and locked the bootloader. I cant believe Ive given up!

This is the first time I have wasted a whole day trying to unlock/root/install a custom ROM on a phone. What am I doing wrong?????

Here's what works for me:
Unlock BL
Make sure I have either June or July factory images on both slots, then
fastboot boot twrp.........img (I use the RC1 image)
When in the temporary twrp, flash ROM or if you want stock OS modified just flash the twrp.....zip (I still use RC1 zip). If you flash the ROM then twrp flashes after it.
reboot to OS
then back to twrp and flash your supersu zip and (flash vendor image if your ROM and stock vendor don't match, that might only be in the Pure Nexus ROM) reboot back to OS
then back to twrp and flash your kernel if you want one.
then I do the audio package that I use

If I do it in these steps and if I have the factory images on both slots before I start, it always works for me. Hope that helps.

I'll just edit to add again: flash TWRP after the ROM not before
 
Last edited:

Ad.Shk2

Senior Member
Sep 25, 2012
503
173
Mississauga
Here's what works for me:
Unlock BL
Make sure I have either June or July factory images on both slots, then
fastboot boot twrp.........img (I use the RC1 image)
When in the temporary twrp, flash ROM or if you want stock OS modified just flash the twrp.....zip (I still use RC1 zip). If you flash the ROM then twrp flashes after it.
reboot to OS
then back to twrp and flash your supersu zip and (flash vendor image if your ROM and stock vendor don't match, that might only be in the Pure Nexus ROM) reboot back to OS
then back to twrp and flash your kernel if you want one.
then I do the audio package that I use

If I do it in these steps and if I have the factory images on both slots before I start, it always works for me. Hope that helps.

I'll just edit to add again: flash TWRP after the ROM not before

Thank you very much for the detailed response. However, since I've only had Samsung and Nexus phones for the last 10 years, this is all new to me. I find it counter intuitive and cumbersome, i guess you really do get old when you hit your thirties :)

I'll try to ask questions where i stumble and maybe you can help me out.

First, how do i flash factory images on both slots? I flashed June FIs thrice yesterday, but I'm not sure which slot they went to!

Second, When you say fastboot twrp image, what do you mean? Do i flash twrp through FB or something else? What command do i use?

Third, which slot do i install the ROM to and how do i know which slot its in?


What happened to the good old days of "flash everything and reboot" :)
 

3aucla1r3

Senior Member
Dec 11, 2013
137
62
South Carolina
Thank you very much for the detailed response. However, since I've only had Samsung and Nexus phones for the last 10 years, this is all new to me. I find it counter intuitive and cumbersome, i guess you really do get old when you hit your thirties :)

I'll try to ask questions where i stumble and maybe you can help me out.

First, how do i flash factory images on both slots? I flashed June FIs thrice yesterday, but I'm not sure which slot they went to!

Second, When you say fastboot twrp image, what do you mean? Do i flash twrp through FB or something else? What command do i use?

Third, which slot do i install the ROM to and how do i know which slot its in?

The easy answers; skipsoft tool flashes to both slots so if you did June, that should be covered. the other easy one is that twrp will flash it to the right slot you shouldn't have to worry about that. OK, so you use platform tools or fastboot/adb tools to fastboot boot yourself to twrp the first time (command is: fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img), that's a twrp image not a zip, then when in the temporary twrp (the one from fastboot) you flash the twrp zip to give you permanent twrp. That should get you a permanent twrp recovery but if you flash a ROM, it'll wipe out the twrp because it has it's own boot image. So, flash the "permanent" twrp zip after you flash the ROM but in the same flash episode. Then I boot and do separate flash episodes for SU and then again for ElementalX kernel.

This is a complicated device but I love the challenge! (not everyone agrees with that, though.) By the way, the image and zip downloands are linked in the twrp rc1 thread.
 

Ad.Shk2

Senior Member
Sep 25, 2012
503
173
Mississauga
Thank you very much for the detailed response. However, since I've only had Samsung and Nexus phones for the last 10 years, this is all new to me. I find it counter intuitive and cumbersome, i guess you really do get old when you hit your thirties :)

I'll try to ask questions where i stumble and maybe you can help me out.

First, how do i flash factory images on both slots? I flashed June FIs thrice yesterday, but I'm not sure which slot they went to!

Second, When you say fastboot twrp image, what do you mean? Do i flash twrp through FB or something else? What command do i use?

Third, which slot do i install the ROM to and how do i know which slot its in?

The easy answers; skipsoft tool flashes to both slots so if you did June, that should be covered. the other easy one is that twrp will flash it to the right slot you shouldn't have to worry about that. OK, so you use platform tools or fastboot/adb tools to fastboot boot yourself to twrp the first time (command is: fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img), that's a twrp image not a zip, then when in the temporary twrp (the one from fastboot) you flash the twrp zip to give you permanent twrp. That should get you a permanent twrp recovery but if you flash a ROM, it'll wipe out the twrp because it has it's own boot image. So, flash the "permanent" twrp zip after you flash the ROM but in the same flash episode. Then I boot and do separate flash episodes for SU and then again for ElementalX kernel.

This is a complicated device but I love the challenge! (not everyone agrees with that, though.) By the way, the image and zip downloands are linked in the twrp rc1 thread.
I did use the Skipsoft tool kit. Although, the last time i flashed the Google factory image, the phone wouldn't go into recovery or anything so i had to flash the zip through fastboot. I just used the flash-all.bat. Would that have flashed to both slots?? How do i check if it has or hasn't?

Im thinking of returning this phone and getting the S8, since the ease of rooting was the primary reason i got it :)
 

3aucla1r3

Senior Member
Dec 11, 2013
137
62
South Carolina
I did use the Skipsoft tool kit. Although, the last time i flashed the Google factory image, the phone wouldn't go into recovery or anything so i had to flash the zip through fastboot. I just used the flash-all.bat. Would that have flashed to both slots?? How do i check if it has or hasn't?

Im thinking of returning this phone and getting the S8, since the ease of rooting was the primary reason i got it :)

Yeah that should have flashed a and b both. Can't figure why you're having the trouble. How about taking the factory image as your OS without flashing a ROM but just doing the fastboot twrp image and then flashing the twrp zip, then booting up? Does that give you a twrp that you can boot back to?
 

Ad.Shk2

Senior Member
Sep 25, 2012
503
173
Mississauga
Yeah that should have flashed a and b both. Can't figure why you're having the trouble. How about taking the factory image as your OS without flashing a ROM but just doing the fastboot twrp image and then flashing the twrp zip, then booting up? Does that give you a twrp that you can boot back to?
I guess I'll give it another try tomorrow if i do not finalize the s8 by then, otherwise I'll have to ship it back.
But thanks a lot for the troubleshooting!!! I may bug you again in case i delve into it tomorrow.
 

jimmmysil

Senior Member
Aug 24, 2012
247
92
My bootloader is unlocked. I used the unified tool to flash a permanent custom recovery twrp but my phone stays forever at the temporary twrp loading screen. Any solutions? I even downgraded to 7.1.1 june update and still nothing. Temporary twrp keeps stacking at loading screen can't go in to flash the permanent one.
 
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,065
Norfolk
AutoUpdate Available for Google Pixel XL device module [Ultimate/PRO Users Only]

Changelog:
[V1.3.4] 09TH AUG 2017
+Added FULL Support for ALL August builds [7.1.2 NHG47Q/NJH47F/NKG47S/NZH54D]
+Added above STOCK and OTA images to download/flash directly from Toolkit using option 9,1 [firmware download/flash] or 10,1 [ota download/sideload]
+Updated file version checker after device selection for more stable checking
+Improvements and minor bug fixes in Main Code
[V1.3.2] 21ST JUL 2017
+Added section in root/unroot section for new Magisk root options
+Added flash Magisk root and Magisk Manager app
+Added flash Magisk root and Magisk Manager app and install Busybox installer
+Added flash Magisk Uninstaller [if you dont want Magisk anymore]
+Added flash Magisk Root and Uninstaller for Pixel/XL Devices
+Updated Root uninstall zip file in root/unroot section for proper unroot
+Updated text for several procedures for clarity
+Added flash no-verity-opt-encrypt zip file to disable verity and allow decryption
+Fixed several options that were not linked correctly

If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link *HERE* so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy.
 

Night·Fire

Senior Member
Jul 30, 2010
155
13
Fort Worth
I decided to try to root with Magisk with the August update, NKG47S. I keep getting an error in TWRP during the install. I've tried to sideload and push it, verified and not. I ended up going back to SuperSU without issue. I'm using the most recent auto update of the toolkit.

Pixel XL, 128GB
The steps I took, all through:
Updated to NKG47S factory image (downloaded from Google outside of tool kit)
Fresh install TWRP during each root attempt.
Attempted verified Magisk push install, received error.
Deleted files and attempted unverified Magisk push install, received error.
Deleted files and attempted Magisk sideload, received error.
Achieved root with SuperSU.

Any help would be appreciated.
 

kpoverdorf

Senior Member
Jan 1, 2012
142
23
I decided to try to root with Magisk with the August update, NKG47S. I keep getting an error in TWRP during the install. I've tried to sideload and push it, verified and not. I ended up going back to SuperSU without issue. I'm using the most recent auto update of the toolkit.

Pixel XL, 128GB
The steps I took, all through:
Updated to NKG47S factory image (downloaded from Google outside of tool kit)
Fresh install TWRP during each root attempt.
Attempted verified Magisk push install, received error.
Deleted files and attempted unverified Magisk push install, received error.
Deleted files and attempted Magisk sideload, received error.
Achieved root with SuperSU.

Any help would be appreciated.

I had the same issue and also settled for SuperSU. Now I am eagerly waiting for Oreo support.
 

mongonexus

Senior Member
Oct 21, 2012
371
104
55
bayville
question for anyone in the know,i have 2 pro modules for nexus 6p and pixel xl,, my toolkit is showing a basic toolkit, when in the past it had full functions, root,unlock,etc etc,can anybody help a fella out,,thanx guys
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    GOOGLE PIXEL XL- SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS.
    SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*

    NOTE: Verizon and ee uk models have locked the bootloaders. In this case you will not be enable the oem unlock setting to unlock the bootloader via the developer screen. You can force unlock the bootloader using dePixel8 in the Bootloader unlock section if your build is 7.1.0 NDE63X or lower. This method was patched in 7.1.1 and does no longer work. If you have a Verizon/ee uk model on 7.1.0 you MUST force unlock the bootloader before accepting the OTA update or your bootloader will be unlockable.

    The Unified Android Toolkit brings together Nexus, Google, Samsung and OnePlus Toolkits and supports many devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.

    FUNCTIONS OF UNIFIED ANDROID TOOLKIT
    * Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
    * Backup/Restore a single package or all apps, user data and Internal Storage
    * Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
    * Unlock/Re-Lock your Bootloader [Nexus]
    * Root Stock builds
    * Various Root options using insecure boot image or custom recovery
    * ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
    * ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
    * [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
    * Install BusyBox on your device
    * Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC [if insecure boot image available]
    * Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
    * Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
    * Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
    * Extras, Tips and Tricks section
    * Auto Update ToolKit to latest available version at startup (professional only feature)
    * Program up to 10 Quickpick slots and run them very quickly (professional only feature)
    * Mods section to automatically perform certain tasks on your device
    * Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
    * Check md5 of stock image to make sure downloaded file isn�t corrupted before flashing [Nexus]
    * Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
    * Flash Custom Recovery or Google Stock Image to Device
    * Flash any part of a stock Nexus image to device [boot, system, recovery] � Great for fixing broken parts of firmware
    * Rename the Recovery Restore File present on some Stock Roms
    * Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
    * Flash Custom Recovery to Device
    * Boot [Nexus] or Flash .img Files directly from your PC
    * Install a single apk or multiple apks to your device
    * Push Files from your PC to your device
    * Pull Files from your device to your PC
    * 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 [calls log, sms, contacts]
    * Install EFS/Partition Backup/Restore app by Wanam
    * Dump selected LogCat buffers to your PC
    * Dump BugReport to your PC
    * Set Files Permissions on your device
    * Open new Command Prompt for manual input
    * Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
    * Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
    * Display Important Information about your device

    --------------------------------------------------------------
    Toolkit_main_menu.png

    --------------------------------------------------------------

    SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*

    DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)

    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: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, 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.

    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).

    MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.

    YOU CAN ALSO NOW UPGRADE TO THE ULTIMATE MODE. ONCE THIS MODE HAS BEEN ACTIVATED YOU WILL BE ABLE TO UNLOCK ALL DEVICE MODULES (PRESENT AND FUTURE) AND WILL NEVER HAVE TO BUY ANOTHER PRO CODE AGAIN.

    AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv

    --------------------------------------------------------------

    PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT 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 ADB/FASTBOOT 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.

    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.

    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 SKIPSOFT 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 if you have one, 'dr' will allow you to install drivers, '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).

    --------------------------------------------------------------

    USEFUL INFORMATION
    How to get into your FastBoot Mode
    1. Turn your phone off
    2. Unplug your usb cable if you have one plugged in
    3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode

    How to get into Recovery
    1. First boot into FastBoot Mode as described above
    2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery

    Show the Menu in the Stock Recovery Screen
    1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.

    --------------------------------------------------------------

    *DISCLAIMER*
    I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
    12
    Update Available for Google Pixel XL device module 1.0.6 [ALL USERS]

    Changelog:
    +Added Support [including root] for November Updates, Android 7.1.0 Europe NDE63U, NDE63V and Verizon NDE63X builds
    +Added above STOCK firmware AND OTA images to download/flash directly from Toolkit using option 9,1 [firmware download/flash] or 10,1 [ota download/sideload]
    +Added alternative fastboot version which will download and try if there are errors flashing stock images
    +Fixed Stock zip image file not showing in list if flashing using options 9,2
    +Added warning against relocking bootloader in Bootloader Unlock/Re-Lock section

    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 option 62 to update the Toolkit base to the latest version
    4. Select the device (google pixel xl) from the list
    5. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
    6. Restart the Toolkit, select the device and new module files will be downloaded/installed

    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 and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

    Enjoy, Mark.
    11
    **FAQ**

    Q: How do I enable Developer options?
    – Go to Settings from the apps drawer
    – Scroll Down and Tap on About Phone or About Device
    – Go down to the Build number section
    – Tap on the Build number option 7 times
    – Go back to the Settings screen
    – Scroll Down and Tap on Developer options (just above the About option)

    Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
    Starting with Android 5.0, on certain devices you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
    – Enable Developer options (go to Settings, About and tap on Build number 7 times)
    – Enable USB Debugging (Settings, Developer options)
    – Look for the ‘Allow OEM Unlock’ or ‘OEM Unlock’ Option and tick it

    Q: When I boot in to TWRP it asks me for a password
    Android 5.0 Lollipop brings new security features like encrypted data. TWRP for Nexus 5X, 6, 6X and 9 is able to decrypt all the data using “default_password “. This allows TWRP to decrypt the information without any problems.
    10
    AutoUpdate Available for Google device module [PRO Users Only]

    I apologise to everyone who has not been answered or thinks I am done with this project. I am definitely not done with it. I have had 12 surgerys on 2 crushed hands and a shattered pelvis after a car crash.

    I had to buy a new laptop and whole new set of programs to make/compile the updates as I lost everything when my hard drive crashed and took out my pc. All this cost me £600 which I had to scrape together and why it took a few more days to get everything done. Updates should come thick and fast now but I have no money left. Im not begging for handouts but if you have ever found the Toolkit useful and want to give back you can send me anything at https://www.paypal.me/mskip. I wouldn’t be saying this unless it was critical and my family and me (and the Toolkit) will be very grateful for anything.

    Changelog:
    +Added Support [including root] for ALL BUILDS up to and including May 2017 builds
    +Added ALL above STOCK and OTA images to download/flash directly from Toolkit using option 9,1 [firmware download/flash] or 10,1 [ota download/sideload]
    +Updated Toolkit base to 1.6.0. Updated app versions and improved functions
    +Toolkit will automatically disable all server pings if they cause any trouble with downloads
    +Added direct link to google download site in factory image downloads section
    +Improved some Main Menu functions

    I uploaded public device modules last month to support March and lower builds so if you are not a pro user and do not want to donate you should still be able to use the public build to download a new image from google servers, then use the toolkit (selecting the latest available build) to work with it.

    If you find any of this useful PLEASE donate to a device project. You can 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 and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

    Enjoy, Mark.
    10
    Sorry for the absence I have been in hospital for the last week. I will be updating the device modules in a bit with custom recovery added (enabled via the build selection screen) and root via custom recovery. I have been working on the updates on my laptop (since theres not much else to do in hospital) so please let me know of any bugs so I can fix them right away.

    Just wanted people to know I haven't abandoned the threads and im back home now so should be able to get back to work as normal.

    Mark.