I rebooted after installing the updated android studio but still can not get it to flash the November update. It recognizes my device and I was able to unlock bootloader but when I try to flash OTA it still says "device not set". I am not sure what to do now. I am searching forums but in the meantime if anyone has suggestions they would be welcomed.
[TOOL] SKIPSOFT ANDROID TOOLKIT -Google Pixel 2 XL- Drivers,Unlock,Firmware,Root
- Thread starter mskip
- Start date
Same with mine! I have even run the flash-all script. For whatever reason, I am missing the boot.sig, recovery.img, system.sig, and vendor.sig.
Bet you haven't tried to flash newest Nov factory image.
Older fastboot before Oct 25 will not successfully flash.
I'm sure.
I was having fun with mine coming up corrupted and not being able to flash the stock image back. I fixed it by using the 8.1 developer image. After it boots use the update that reverts it back to stock and it will boot fine.
Follow this
https://xdaforums.com/pixel-2-xl/how-to/easy-unlock-8-1-developer-preview-t3695306
[/COLOR]
You "used" the 8.1 image. So does that mean you downloaded the 8.1 zip file and side loaded it and flashed it? Thank you.
You "used" the 8.1 image. So does that mean you downloaded the 8.1 zip file and side loaded it and flashed it? Thank you.
I just downloaded the file it linked to. Unzipped it. Ran the bat file.
Follow the directions in the link. Yes it is the 8.1 dev image. Once it loads go through the setup skip everything just connect to wifi. Go into system click the check for update. It should show that at the top that you opted out of the dev program and the update will take you back to stock image using ota. Install and it should get you back to the stock image.
---------- Post added at 01:27 PM ---------- Previous post was at 01:24 PM ----------
Your welcome. No problem. Glad I could help. I suspect it has something to do with flashing to the a/b slot. I haven't had to deal with that before since I just came from a Nexus 6.
Just wanted to update if this helps anyone. I used the toolkit to sideload the November security update by downloading the factory update from the Google sure and adding it to the sideload folder in the toolkit.
Root I'm not going to do yet because it's a little sketchy to me.
Thank you Susie go all the help.
Root I'm not going to do yet because it's a little sketchy to me.
Thank you Susie go all the help.
Thanks for this, will definitely try. Do you have a link?
---------- Post added at 10:26 PM ---------- Previous post was at 10:20 PM ----------
Disregard.. Just saw you can do it directly from toolkit.. great work OP
Geekser
Senior Member
i must be an idiot - but I can't seem to get the ultimate code to activate.
I purchased the Ultimate for the Google Pixel Xl2 - when I put follow the instructions to enter that code in the toolkit - I get an error message saying that I entered the wrong code. I thought I did everything as described to activate the code - but apparently I am doing something wrong -
Can you tell me what i am doing wrong?
EDIT - I am an idiot - but I figured out what I was doing wrong. Never mind - all set. thanks for an awesome Tool kit. I have used previous versions of this tool kit - you do amazing work my friend. thanks for everything.
I purchased the Ultimate for the Google Pixel Xl2 - when I put follow the instructions to enter that code in the toolkit - I get an error message saying that I entered the wrong code. I thought I did everything as described to activate the code - but apparently I am doing something wrong -
Can you tell me what i am doing wrong?
EDIT - I am an idiot - but I figured out what I was doing wrong. Never mind - all set. thanks for an awesome Tool kit. I have used previous versions of this tool kit - you do amazing work my friend. thanks for everything.
Last edited:
@mskip
Ultimate user here, device not set message when trying update November img.
Android sdk updated, sideload ota worked until 97% then failed.
Thank you in advance.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Ultimate user here, device not set message when trying update November img.
Android sdk updated, sideload ota worked until 97% then failed.
Thank you in advance.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
I think your problem is related to outdated adb/fastboot files being used. I have updated the Toolkit installer to version 1.7.1 with the latest adb/fastboot files, as well as fixing the adb/fastboot auto updater as it wasn't working properly. If you have the pro version I will be uploading an autoupdate in a few minutes which will hopefully fix your problem.
Non Pro users PLEASE take the latest update to Toolkit base version 1.7.1 when you start the Toolkit as it should fix a lot of flashing related problems being talked about.
UPDATE FOR GOOGLE PIXEL 2 XL DEVICE FOR ALL USERS (PRO AND PUBLIC)
This is to update your Toolkit.exe file so that adb/fastboot files can be automatically updated to the latest version. This should fix any problems with flashing November firmware images due to outdated files. This update will also fix pro users restarting to the wrong device module after taking an AutoUpdate (affective from the next 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 [v1.0.3] 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 device from the list (option 10)
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Select option 62 from the list to update Toolkit.exe to the latest version
6. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
7. Restart the Toolkit, select the device and new module files will be downloaded/installed
If you want to donate to the device module project or purchase an Ultimate Code to unlock all devices/features please do it through the Toolkit so you get the right code fast.
This is to update your Toolkit.exe file so that adb/fastboot files can be automatically updated to the latest version. This should fix any problems with flashing November firmware images due to outdated files. This update will also fix pro users restarting to the wrong device module after taking an AutoUpdate (affective from the next 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 [v1.0.3] 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 device from the list (option 10)
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Select option 62 from the list to update Toolkit.exe to the latest version
6. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
7. Restart the Toolkit, select the device and new module files will be downloaded/installed
If you want to donate to the device module project or purchase an Ultimate Code to unlock all devices/features please do it through the Toolkit so you get the right code fast.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
37GOOGLE PIXEL 2 XL- SUPPORTS ALL MODELS WITH UNLOCKABLE BOOTLOADER UP TO THE LATEST ANDROID BUILDS.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
NOTE: Verizon models (not sure about ee) have locked the bootloader. In this case you will not be able to toggle the oem unlock setting to unlock the bootloader via the developer screen.
NOTE2: At the moment TWRP is still in alpha testing and lots of things do not work on it such as device decryption, mtp and backup. It's very risky to add this to the toolkit in this state as someone could easily brick their device if they dont know what they are doing so until a more stable version is made custom recovery will not be added.
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
* 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 or check status (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check sha256 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)
* Custom Device Builder can add build support for listed device and add device support for any Samsung device with an unlocked bootloader [included in ULTIMATE, can be added as an extra]
* Download/sideload stock OTA image (G,N,O)
* Install Magisk Root on device [and uninstall if needed]
* Disable dm-verity check
* 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 Recovery [Stock, CWM, Philz_touch or Twrp Touch]
* 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 files to latest versions
* Auto Update Custom Recovery to latest versions [PRO ONLY]
* Disable forced encryption on device if needed
* 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
* 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 Pixel, N-Nexus, O-OnePlus, S-Samsung
--------------------------------------------------------------
--------------------------------------------------------------
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, PROFESSIONAL AND ULTIMATE 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 CUSTOM RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE QUICK PICKS SECTION ALLOWS YOU TO PROGRAM UP TO 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 ULTIMATE MODE ALLOWS YOU TO ACTIVATE THE PRO MODE ON EVERY DEVICE MODULE THE TOOLKIT SUPPORTS. NO MORE NEED TO BUY A NEW PRO CODE EVERY TIME YOU BUY A NEW DEVICE. THE ULTIMATE MODE ALSO INCLUDES THE NEW CUSTOM BUILDER MODE WHICH LETS YOU ADD SUPPORT FOR NEW BUILDS EVEN BEFORE THE TOOLKIT CAN ADD IT. CUSTOM BUILDER MODE CAN ALSO ADD SUPPORT FOR SAMSUNG DEVICES THAT HAVEN'T YET BEEN ADDED TO THE TOOLKIT.
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW. WITHOUT YOUR SUPPORT THE TOOLKIT CANNOT EXIST.
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'.
Newer devices also require you to enable OEM Unlocking in the developer section to allow the bootloader to be unlocked. Tap Developer options and enable OEM unlocking and USB debugging. (If OEM unlocking is disabled, connect to the Internet so the device can check in at least once. If it remains disabled, your device may be SIM locked by your carrier and the bootloader cannot be unlocked.)
--------------------------------------------------------------
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.8Hi, 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.
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.
Pro/Ultimate User Auto Update Available:
The device module has been updated for all builds up to the latest version. All the firmware and OTA firmware images have been added to the firmware section on the Google devices and the OTA images added for the OnePlus devices. These can be downloaded and flashed directly through the Toolkit for your convenience.
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 https://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 and unlock ALL device modules for the lifetime of the Toolkit. Follow us on twitter at https://twitter.com/skipsoftnet for posts/updates.5
I don't know @mskip for nothing but I do know this community. I'm going to assume you contacted the dev directly to give him the opportunity to resolve your issues first before publicly calling him a liar...5UPDATE FOR GOOGLE PIXEL 2 XL DEVICE FOR ALL USERS (PRO AND PUBLIC)
Changelog [Google Pixel 2 XL] v1.0.2:
+Added FULL Support for Android 8.0.0 OPD1.170816.025, Nov 2017, EMR
+Added FULL Support for Android 8.0.0 OPD3.170816.023, Nov 2017, Verizon EMR
+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 new critical-partitions unlock command to bootloader unlock procedure for full unlock
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 device from the list
4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device
5. Select option 63 to update to the latest md5 firmware check file (if you are downloading new firmware)
6. Restart the Toolkit, select the device and new module files will be downloaded/installed
If you want to donate to the device module project or purchase an Ultimate Code to unlock all devices/features please do it through the Toolkit so you get the right code fast.
