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

Search This thread

yung40oz84

Senior Member
Sep 23, 2014
3,090
1,027
sites.psu.edu
What exactly isnt being reset? If you choose not to wipe the userdata partition then the device will not go back to an out of box state as the device will not reset apps or data.

Mark.
Ya I realized that now, see on my 6P I could flash everything manually and not flash userdata and not format userdata and still come to a fresh setup my device.i am confused, because I was under the impression that data and internal memory is different, I should be able to wipe data, but not internal memory right?
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
Ya I realized that now, see on my 6P I could flash everything manually and not flash userdata and not format userdata and still come to a fresh setup my device.i am confused, because I was under the impression that data and internal memory is different, I should be able to wipe data, but not internal memory right?
Internal memory is part of the userdata partition so if you wipe the device (format userdata partition) then your internal storage will be deleted. Thats the same for Internal Storage on all Android devices and always has been. On your Nexus 6P the act of not flashing the userdata partition left the Internal Data intact which is why you didn't lose your data.

Mark.
 

MReprogle

Member
Apr 14, 2011
24
1
Fort Wayne
Awesome

Does anyone have any tips on how to hide my unlocked bootloader so that Android Pay continues to work? I thought I remember an article talking about flashing a kernel or something else to help with this. Any help is greatly appreciated!
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
Does anyone have any tips on how to hide my unlocked bootloader so that Android Pay continues to work? I thought I remember an article talking about flashing a kernel or something else to help with this. Any help is greatly appreciated!
SuperSu has a function called suhide (don't know if it hides unlocked bootloaders as well) but it doesn't work on Android 7.1 at the moment. As far as I know there isnt anything that will hide tampering from Android Pay on the Pixel/XL.

Mark.
 

sulpher

Senior Member
Aug 2, 2008
666
214
Hey Skip have a question about restoring to stock.... I downloaded the NDE63P version to flash my phone back to stock, and it seems to have reset everything in android itself, but for some reason the 'device cannot be checked blah blah' thing at boot that was caused by rooting is still there. Any idea if it will stop saying that eventually or do I need to flash something else?

Tried twice now, same result.
 

michaelbsheldon

Senior Member
Jan 12, 2011
781
226
Anaheim, CA
Hey Skip have a question about restoring to stock.... I downloaded the NDE63P version to flash my phone back to stock, and it seems to have reset everything in android itself, but for some reason the 'device cannot be checked blah blah' thing at boot that was caused by rooting is still there. Any idea if it will stop saying that eventually or do I need to flash something else?

Tried twice now, same result.

Are you unlocked? If yes, that's why the message appears.
 
  • Like
Reactions: sulpher

jayhammy

Senior Member
Aug 20, 2010
475
18
Schenectady, NY
hey folks,
I'm not sure I understood from the OP, but is Verizon Pixel XL rootable? I'm not really concerned about unlocked bootloader for ROMs, etc., but I'd defiintely like to root the Verizon XL device so I can use Titanium backup, and use Hotspot as well.
Thanks!!
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
hey folks,
I'm not sure I understood from the OP, but is Verizon Pixel XL rootable? I'm not really concerned about unlocked bootloader for ROMs, etc., but I'd defiintely like to root the Verizon XL device so I can use Titanium backup, and use Hotspot as well.
Thanks!!
Im pretty sure dePixel8 still works on the new builds for verizon and ee uk so first thing is to install drivers using options 1,1 (if you haven't already done so), then select options 3,4 from the main menu to go to the dePixel8 webpage and follow the instructions to force unlock the bootloader. If that works you can use options 4,2 to root and install busybox.

Mark.
 

behlski

Member
Aug 2, 2012
25
2
Milwaukee, WI
My Pixel XL will be arriving today from google. It's been a couple years since I had rooted my Galaxy Nexus and Nexus 7, but I remember this toolkit being very helpful and easy to use.

If I unlock the bootloader and root it, will I still be able to take the regular OTA updates from Google/Verizon without messing anything up or losing root? Assuming I just use root apps, and don't install custom ROM's, recovery, or kernel?
 

wtherrell

Senior Member
Dec 30, 2008
2,241
698
My Pixel XL will be arriving today from google. It's been a couple years since I had rooted my Galaxy Nexus and Nexus 7, but I remember this toolkit being very helpful and easy to use.

If I unlock the bootloader and root it, will I still be able to take the regular OTA updates from Google/Verizon without messing anything up or losing root? Assuming I just use root apps, and don't install custom ROM's, recovery, or kernel?
IIRC, unlocked you can still get the OTA. Maybe even if rooted but you will lose root by installing it. If you have a custom kernel or rom you will not get the OTA.
 

808phoneaddict

Senior Member
Dec 26, 2011
950
135
IIRC, unlocked you can still get the OTA. Maybe even if rooted but you will lose root by installing it. If you have a custom kernel or rom you will not get the OTA.
Actually I think with the pixels, I think it your bootloader is unlocked that you don't get the updates...at least for mine (from Google and was on L build) once I unlocked it, I believe it wasn't going to update....
 

wtherrell

Senior Member
Dec 30, 2008
2,241
698
Actually I think with the pixels, I think it your bootloader is unlocked that you don't get the updates...at least for mine (from Google and was on L build) once I unlocked it, I believe it wasn't going to update....
Could be. I'm going off of Nexus experience. Google. Always fixing what doesn't need to be fixed.

---------- Post added at 12:02 PM ---------- Previous post was at 11:45 AM ----------

Could be. I'm going off of Nexus experience. Google. Always fixing what doesn't need to be fixed.
Although, see post #109.
 

schwem

Senior Member
Oct 15, 2014
2,215
761
35
Auburn Hills
Actually I think with the pixels, I think it your bootloader is unlocked that you don't get the updates...at least for mine (from Google and was on L build) once I unlocked it, I believe it wasn't going to update....
Wrong, I got and installed the update to NDE63X from NDE63P all while unlocked without any issues. As long as you're not rooted and hadn't changed anything in the system if you were rooted at any point it will download and install updates with the bootloader unlocked.
 
  • Like
Reactions: 808phoneaddict

808phoneaddict

Senior Member
Dec 26, 2011
950
135
Wrong, I got and installed the update to NDE63X from NDE63P all while unlocked without any issues. As long as you're not rooted and hadn't changed anything in the system if you were rooted at any point it will download and install updates with the bootloader unlocked.


O OK my mistake sorry for the bad info...totally forgot I was rooted at the time too
 
  • Like
Reactions: schwem

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.