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

Search This thread
By:
Advanced…
JazzMozz

JazzMozz

Senior Member
Dec 21, 2010
237
25
Lawlrus said:
Email Google and ask them.

It's listed NOWHERE what it means. So you need to ask the people calling it that.
Click to expand...
Click to collapse
Yeah, and if they will ever reply...

But if Mark lists these builds in the toolkit, he must know what the difference between the builds is? Otherwise it is just like a car manufacturer and you ask him: what does this button or switch do and the manufacturer can't answer that because he doesn't know. It is him that build the car so surely he must know
 
mskip

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
krash2k said:
Hi everyone, I am trying to flash a stock google factory image (I have the ultimate version) right now because I think I screwed something up. I can get into fastboot and the toolkit will walk me through all the way to the point where it should actually do the flashing part. Then it just says..

Your device has not been set

.. and goes back to the main menu. I did it a few times and made sure I selected the correct device (#10, google pixel xl2).. but it just keeps doing it.
Click to expand...
Click to collapse
Im sorry about this I only just realised I hadnt added the Pixel 2 devices to the stock flash selection list (resulting in the Device has not been set error). I have been back in hospital for a few weeks so now back and trying to catch up. Im enabling the flash procedure now and giving an option of a normal flash or extracting all the image files and flashing seperately. The second method is more proven to fix soft bricked devices so may come in useful for some people. I haven't added Magisk yet but have enabled custom recovery as TWRP is in beta now so rooting with SuperSU should be possible/ I will try and add Magisk in the next few days but have to catch up on emails and November updates that never got finished so please be patient.

Updates for ALL users should go live today.
 
Last edited:
  • Like
Reactions: AlSimmons, burbank and CyberpodS2
mskip

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
As to the questions about the EMR build, that part was listed by google and has now been taken off. As other people have said I assume it is some kind of maintenance release but I dont think its anything to worry about or spend too much brain power trying to work out. I have taken it off the listings in the Toolkit.
 
  • Like
Reactions: burbank
B

Branj812

Member
Sep 27, 2010
40
2
mskip said:
Im sorry about this I only just realised I hadnt added the Pixel 2 devices to the stock flash selection list (resulting in the Device has not been set error). I have been back in hospital for a few weeks so now back and trying to catch up. Im enabling the flash procedure now and giving an option of a normal flash or extracting all the image files and flashing seperately. The second method is more proven to fix soft bricked devices so may come in useful for some people. I haven't added Magisk yet but have enabled custom recovery as TWRP is in beta now so rooting with SuperSU should be possible/ I will try and add Magisk in the next few days but have to catch up on emails and November updates that never got finished so please be patient.

Updates for ALL users should go live today.
Click to expand...
Click to collapse

im stuck in a soft brick right now so I'm hoping this flash procedure will work for me! thank you for the work you do and time you put into this, its much appreciated
 
K

krash2k

Member
Aug 31, 2017
32
3
mskip said:
Im sorry about this I only just realised I hadnt added the Pixel 2 devices to the stock flash selection list (resulting in the Device has not been set error). I have been back in hospital for a few weeks so now back and trying to catch up. Im enabling the flash procedure now and giving an option of a normal flash or extracting all the image files and flashing seperately. The second method is more proven to fix soft bricked devices so may come in useful for some people. I haven't added Magisk yet but have enabled custom recovery as TWRP is in beta now so rooting with SuperSU should be possible/ I will try and add Magisk in the next few days but have to catch up on emails and November updates that never got finished so please be patient.

Updates for ALL users should go live today.
Click to expand...
Click to collapse

I appreciate the response but no explanation necessary. I know what I'm getting into when I buy a device that was just released.. and I further know what I'm getting into when messing around with it while development on it is only a handful of weeks old.

Thanks for your contribution to furthering the development.
 
mskip

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
UPDATE FOR GOOGLE PIXEL 2 XL DEVICE FOR ALL USERS (PRO AND PUBLIC)

A couple of updates to post. Sorry there hasn't been much activity over the past few weeks I have been in hospital.

Changelog [Google Pixel 2 XL]
[V1.0.5] 01ST DEC 2017
+Fixed/Enabled Stock image flash routine [option 9 from main menu]
+Added option in stock flash routine for standard flash or extract images/flash
+Updated Magisk Beta to v14.5.1456 with support for Pixel2/XL devices
[V1.0.4] 27TH NOV 2017
+Enabled Custom Recovery functions and added TWRP 3.1.1.beta2 to download/use
+Made some minor adjustments to toolkit procedures

Custom recovery options are now available so you can try rooting with SuperSU. The Toolkit should also push SuHide to protect it from safetynet. You can also try Magisk as I think the beta version works with Pixel2/XL now. When I added the Pixel2/XL devices to the Toolkit I forgot to add them to the list for stock image flashing which is why it came up with the message saying device has not been set. This has been fixed and I have provided 2 flashing options for all Pixel devices. You can use the standard method google uses or you can extract the images from the image zip file and flash them separately. This 2nd method will set the active slot to slot a before flashing. It has been proven to better fix soft bricked devices but both should work fine.

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.exe file to the latest version.
4. Select the device 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 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.
 
  • Like
Reactions: chinabear13, burbank and CyberpodS2
M

markp99

Senior Member
May 9, 2011
306
61
Mark,

FYI, the donate link within the Pixel 2 XL module seems broken.

Toolkit > 10 > D > 1 = Error
 
Last edited:
seanerixon

seanerixon

Senior Member
Apr 5, 2010
214
24
Philadelphia
erixon.me
Well, I just came back from the iOS realm. And I'm happy to see you're still around mskip. Definitely appreciated your tool when I had my few Nexus devices a few years ago, and look forward to using this again when my Pixel XL 2 comes later this week :)
 
C

cvoid

Member
Nov 5, 2010
30
1
great tool! just bought the premium version and will immediatley root my pixel =)
 
Last edited:
Y

yousif666

Senior Member
Apr 20, 2011
139
8
will i be able to backup apps and data to PC without rooting/unlocking bootloader?

Thanks.
 
Last edited:
J

Jiibus

Senior Member
Dec 17, 2010
130
10
The toolkit isn't unlocking my phone. I have debugging and OEM unlocking turned on. When I do the steps it says I'm already unlocked.
 

Attachments

  • Capture.jpg
    Capture.jpg
    144.2 KB · Views: 343
Jiggs82

Jiggs82

Senior Member
Dec 22, 2010
5,960
2,858
The Bronx, NY
Google Pixel 6 Pro
Hey guys I had followed most of the instructions from op and thread but twrp wouldn't work for me when rebooting to it even though my drive is unlocked and was rooted but after trying to install/flash it again (twrp 3.1.1. beta) I seem to brick my device or well it's stuck on bootloop and now I don't have a stock rom or files on my device smh so how can I get back the stock rom without using fastboot flashing the stock image from Google since I have issues trying to use it on my PC ?☹️ Thanks.

Edit: Nvm i flashed the google stock 8.0 image/zip and it booted to android....
 
Last edited:
bemagrp

bemagrp

Senior Member
Jan 30, 2014
153
42
@mskip

Mark, tried flashing 8.1, got error message while flashing bootloader to currently active spot b. About critical unlock.
Please advice, thank you.
 
samteeee

samteeee

Senior Member
Mar 7, 2010
1,427
256
Brampton
Apple iPhone 12
Google Pixel 6 Pro
Life Saver!

@mskip

Just wanted to let you know that this tool saved my P2XL from being a "paper weight"!
I tried every tool, trick and script to no avail but someone suggested your tool and I thought
spending a few bucks better than loosing a Grand!
It took me two "Flash Run" to get my beloved P2XL back to the world of living!
Thank you.:good:
 
JazzMozz

JazzMozz

Senior Member
Dec 21, 2010
237
25
@mskip: I received my pixel 2xl last week and the first thing I did was give it the toolkit treatment. As with any other phone I used your toolkit with, it was a walk in the park.

This week 8.1 has been released. On other forums here on XDA, I found several (often confusingly different) methods on how to update, all involving adb commands. As I'm a lazy bugger who likes things easy (hey, that's why I keep buying your toolkit [emoji2]) would you mind explaining in detail how to update to 8.1 using the toolkit? I think other users would find this useful as well.

FWIW, I'm on the November build, Magisk rooted (14.5) and with Adaway and jrummy busybox installed. If I'm not mistaken my recovery is still stock.

Thanks.
 
You must log in or register to reply here.

Similar threads

T
[UPDATED][2017.11.6][Magisk] Root Pixel 2 (XL)
Replies
3K
Views
359K
7
73sydney
Dees_Troy
TWRP 3.2.3-1 for Pixel 2 XL
Replies
3K
Views
303K
Alxoom33
Alxoom33
flar2
[KERNEL] Pixel 2 XL ElementalX
Replies
2K
Views
205K
N
northsail
nitin.chobhe
[ROM][Pixel 2 XL][13.0] PixelDust Android 13 for taimen [04 Feb 2023]
Replies
2K
Views
202K
L
letli
xFirefly93
[MOD] BlackenedMod v11.2 (Pixel 2 / Pixel 2 XL)
Replies
2K
Views
124K
Subhojit
Subhojit

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 37
    mskip
    mskip
    GOOGLE 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

    --------------------------------------------------------------
    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, 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.
    View
    8
    mskip
    mskip
    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.

    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.
    View
    5
    slaydog
    slaydog
    Hello, how do I root with Magisk? I see several other options to root while using the Toolkit, but not to install Magisk- although it is listed in the OP...
    Thanks!
    View
    5
    CyberpodS2
    CyberpodS2
    HooverFan said:
    Ok, this thing has screwed me over twice now...

    Just wanting to reflash boot, but since you LIE about what's available in the public version for download (1.0.7 is the only option I get, and I ain't paying you anything for screwing up my phone TWICE now just to get 1.0.8 when that's the listed public version available) and it flashed the damn december boot and now I just want to flash stock without wiping, and tried doing that using the manual option... but nope, now it's corrupt and I need to flash from scratch.

    Paying just to get "module updates" and lie about what's actually in the damn thing.

    What a load...
    Click to expand...
    Click to collapse

    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...
    View
    5
    mskip
    mskip
    UPDATE 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.
    View

New posts