yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hutzdani:
You could leave the settings/option as "OTA SIDELOAD with STOCK recovery" this way you can run the standard commands to boot into bootloader and establish FASTBOOT and then "fastboot reboot recovery" then display a message asking the user to press power and volume up and then type the file name of the file residing in the "files_to_push" or however you call that folder and then just accept this command and process the ADB SIDELOAD with the stock recovery on the device.

You could also leave a message saying this option is only enabled for the stock recovery until custom recoveries land for these devices.

This way you don't need to push the stock recovery, also from here you could ask if after the reboot would you like to flash boot-to-root.img SR3 for your device.

this way you can flash OTAs with stock recovery and root in one foul swoop and you'd only need to collect the boot_to_root.imgs for Sailfish and Marlin
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Has anyone with the PRO version of the Google PixelXL device module had the same problem with flashing stock images? I think I found the problem (with a kick in the brain from Scott) in that the main Toolkit installer includes a slightly older version of fastboot that may be causing the flashing errors. The AutoUpdate (for Pro Users) updates fastboot to the latest version so I assume the Pro Users shouldn't have the same problems public users are facing.

I am adding an update to the latest version of adb/fastboot when the Toolkit first starts to hopefully fix this problem for everyone, as well as some more updates to enable OTA updates and enhance the flash procedure. I new version will be released later today and I would advise everyone to update.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hutzdani:
I'd say thats the cause, if the old fastboot drivers are from a lower API they will likely not recognise any of the new commands
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fchowd0696:
I reflashed the stock image because my device was stuck at boot after trying to root. Now it's still stuck at a boot loop. Is my device permanently bricked? What else can I do?

---------- Post added at 06:54 PM ---------- Previous post was at 06:03 PM ----------

Now I tried doing the flash-all.bat script for the NDE63V facotry image and it's still stuck on a boot loop. Can someone for the love of god please help? I have a dead 700 dollar device.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
WAIT WHAT?!?!?!

I sent you a PM last night at 01:42 AM (GMT -5) telling you the issue. Before you even made this thread. Can I get a free code?

No just B/S'ing you. Give the code away to someone who needs it :good:

Hit me up if you ever have issues like this again. I have been known to be crafty :angel:

-Scott
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] a lawless a:
I need the code
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
Give it to him :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] a lawless a:
Thanks brother...I was just messing about! I was going to donate one I got paid as I only get paid once a month.

---------- Post added at 11:37 PM ---------- Previous post was at 11:36 PM ----------

However I will surely take the code
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] a lawless a:
So for 2 days the toolkit would not upgrade me to new nde63x until today it worked flawlessly!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SirLoinOfBeef:
Should option 10 be telling me "no boot or stock recovery image will be downloaded" for my Pixel XL?

I have paid for the pro version.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] a lawless a:
I think option 10 is disabled. For now because we don't have a recovery yet.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Option 10 does not is there to be used if your build is not listed, to root or use other tools. No boot/recovery image is downloaded in that option.

On a side note I updated the base version to 1.5.5 last night which will check the adb/fastboot files the toolkit is using and automatically updates them to the latest version (r25) if needed. Im hoping this will fix the stock firmware flashing errors. Has anyone updated to v1.5.5 (it should tell you there is a new update at startup) and tried the flash procedure? Im also adding some more fixes which I will release if I can ever fix a stupid problem im having.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Flashing the firmware image? Did you upgrade the Toolkit to the new v1.5.5?

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] a lawless a:
Yes sir!

However I didn't see where you posted that you had updated it. Thank you for all your hard work!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
Good stuff!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Thanks mate, talking to you made me think if I had the correct adb/fastboot versions in the full installer (which I didn't) so I came up with the fix. You should be taking all the credit not me lol ;) :highfive:

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
I actually forgot to post a message about it as most people will see the update message when they start the Toolkit but I will will put something on my twitter and skipsoft website for the ones that may have been scared off the Toolkit from bad flashes (because of the old fastboot file).

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] a lawless a:
It's all good brother. I was just messing about with it yesterday.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 808phoneaddict:
So if I have pixel xl, that is rooted but is on L, stock kernel, I should be able to use this to update to V and have root right?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SirLoinOfBeef:
You can load V firmware but this will effectively unroot your device. You can attempt to re-root afterwards, however people seem to be having mixed results with post-upgrade rooting.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 808phoneaddict:
Oh OK, I thought that was figured out, but wasn't sure...that's kind of why I brought it up to check
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SirLoinOfBeef:
To be fair I think most people are re-rooting fine, but some (including myself) find devices stuck in a boot loop when trying to re-root. A simple sideload of firmware fixes this without losing anything, but if you find yourself in this category then you are likely stuck without root until you wipe the device and make a clean start, or wait for an updated root tool.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muttley06:
I have followed all directions to T I cant find out what is causing my root not to boot.. I just get the 4 bouncing dots for 45 min and nothing happend. Any ideas? thanks in advance.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] moosc:
I've flashed multiple times to day. Works perfectly. As soon as o Launched it this morning said there was update..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SirLoinOfBeef:
You are not alone in this. Many of us are unable to root after the laest update: http://xdaforums.com/pixel-xl/help/root-marlin-t3498858

I would expect Chainfire to release an s4 update soon enough that resolves this.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] muttley06:
Thank you for the heads up I was looking around in a panic and couldn't find anything.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Update Available for Google Pixel XL device module 1.0.7 [ALL USERS]

Changelog:

+Added Adb/Fastboot version check at startup so latest versions are always used

+Finally fixed stock firmware flashing problems [I hope]

+Toolkit will now flash system.img in 512M chunks to fix low memory flashing problems

+Enabled stock boot/recovery image download after build selection if needed

+Enabled OTA Stock image download/flash section in main menu

+Enabled some more functions in Toolkit for Google Pixel device

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. VERY IMPORTANT!! Select option 62 to update the Toolkit base to the latest version 1.5.5 (adb/fastboot fixes)

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.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
I donated and got the pro version for Pixel XL, when I go to my model it says server cannot be located....? Any help would be appreciated, thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
That message is displayed if there is an error downloading model files. How many times have you tried? Did the Toolkit download extra files after first installing it (supersu, etc)? Internet connection is needed sometimes so if you keep having problems then let me know and I will post a test program to check you can connect to my server.

You can open a command prompt and try "ping -n 3 skipsoft.net" to see if your computer connects to skipsoft ok.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
The request keeps timing out when pinging. I tried quite a few time from skipsoft, I am connected to a wired ethernet, and I am not 100% sure if it downloaded those extra files........
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Start the Toolkit and select option "cp" to start a command prompt.

Paste the following in to the command prompt and check if any work

ping -n 3 skipsoft.net

ping -n 3 google.com

tools\curl -L -C - -o MARLIN710_NDE63V.zip http://skipsoft.net/download/toolkit/googlepixelxltoolkit/model_files/MARLIN710_NDE63V.zip

If the skipsoft ping doesn't work but the model file download works then I will add an option to disable the pings to skipsoft before downloading. Hopefully that will fix the problem.

Let me know.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 808phoneaddict:
I have the old version on my computer since galaxy Nexus days! I updated it to the current version, got rid of the pro code cuz I did a fresh install, but that's fine...

I'm on L, rooted, with stock kernel...

Trying to figure out what I should do if I wanted to update to the V...

I'm guessing flash stock image (whole thing or partial?)...

Also am I able to reroot after? Do I need to flash a custom kernel to do so?

And I didn't see anything about updating the adb/fastboot drivers...?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Good to see Galaxy Nexus users still using the Toolkit with new devices :)

If you want to update to NDE63V you can either use option 9,1 to download/flash the stock firmware image or option 10,1 to download/sideload the stock ota image. Both options are fine and theres no real advantage of one over the other. If you are rooted and don't have too much on your device it may be safest to backup your app and data and then flash the new stock firmware image (option 9,1) with a format usedata (which will wipe the device), then you can reroot. SuperSU will patch the stock kernel so you do not need to do anything else. Some users have reported bootloops when rerooting after updating builds so I don't know if its a problem with SuperSU or something left from a previous build after updating. I don't know if chainfire is looking in to this (probably is knowing him).

If you start the Toolkit and it says 1.5.5 at the top in the device selection screen then you already have the latest base with the adb/fastboot checker. I spent a LOT of time on this version to make sure its as stable as possible but if you do have any problems please let me know. Always happy to help.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
I imagine this means the download worked, it says 100%, and none of the pings worked, all timed out.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
I have added a hidden option in the device selection screen, option "dp" to disable/enable the server pings before downloading file. AutoUpdate to v1.0.8, when the Toolkit restarts at the device build selection screen type option "b" to go back to the device selection screen. You can then type "dp" to disable the server pings in the Toolkit base and Google Pixel XL programs. If you get an download error try again as it may be trying to resume a bad download. If you get another error you can assume its not worked and you will have to download files manually (I can arrange links).

If you aren't sure what I just said or need more help let me know, and let me know if disabling the server pings lets you download the files.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 808phoneaddict:
Thank you for your hard work! The process of updating the toolkit was very smooth and seamless...Ill probably try updating tonight and jus backup everything, go for the clean update with formating userdata and reroot from there...hopefully that works and I don't get bootloops...will post how it goes if I do do that tonight... chainfire is the man, hopefully he is looking into it!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
ANNOUNCEMENT:

TWRP has been released for the Google Pixel and Pixel XL by dees_Troy. Its easy enough for the Toolkit to install it (a bit different from existing recovery method as you need to boot twrp and then install a zip). At the moment there are a few problems such as restoring a backup "may" wipe the data", no support for multi-user and root will be removed (chainfire would need to update SuperSU as installing twrp will remove patches rquired for root). Installing Twrp will of course open up flashing zips and custom roms.

Im just posting this to ask if users want me to add twrp to the toolkit now (with appropriate warnings and some explanation) or just wait a while. I will bow to your wishes.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SirLoinOfBeef:
I have already flashed TWRP manually with no hassles whatsoever... That being said, you currently have to choose between root or TWRP, the two cannot coexist on Pixel untill Chainfire works out an update for root.

My vote would to wait untill TWRP and root can play nicely together, then add it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
OK, everything there worked, now I have a couple other questions, lol.

First, obviously the flashing procedure manually is not the same on the pixel devices as there are some images missing from old nexus devices and new ones, as well as the multiple systems, etc. So my question is if I choose flash google factory image stock, will it do it correctly? Because I know on the nexus 6P you could not flash userdata on anything higher than the 32gb model, and flash-all.bat has userdata in it and wiping of internal memory which I do not want. I have searched and searched and searched, and the only method of manually flashing the images from the factory image zip does not even wipe apps, or data...... I just like to be thorough and know what I am getting into, lol. Thanks for all your help!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] in_dmand:
I'm trying to follow the guide here to root, but don't know how to get and use fastboot and the reboot into fastboot mode isn't working w/ this toolkit yet... for me at least. can anyone help me out?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wase4711:
I agree completely; its ok to wait awhile to have a safe and easy way for N00Bs to use this tool for both root and TWRP; otherwise, the thread will be over run with them freaking out about how they bricked their phones, and begging for help..

If you are experienced enough, and can't wait for root to be updated to work "normally" with TWRP, then you dont need this tool to get it done now..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Fauert:
Ok to wait for optimal working TWRP , also avoiding many post about naggy "issue's" ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] humdrum2009:
While I can use adb just fine ,some users cannot this tool is a godsend.

But they also need to be adb proficient.

Go ahead put it in the toolkit,but warn then against bugging you with questions.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
Its your app and I take no credit but do take consultant fees :angel: LOL!

Mark,

Between me and you... I would hold off a bit. TWRP "can" be "flaky" at this time, which is why its Alpha. That will turn your thread into a mess! Trust me on this one!

Your call... But my vote is to hold off for now... Alpha is too experimental!

-Scott
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Ok the majority has spoken :)

I will start adding TWRP for the Pixel devices to the Toolkit as I will have to make a new page with warnings and possible problems. The install process also needs

coding in as it will be different from previous Nexus devices. I will however leave it disabled with a "hidden" code (apart from maybe getting some experienced users to test it) until it can be considered a bit more stable. Shouldn't take more than a day to add everything and put out an update for some testers to try.

At least chainfire has updated SuperSU so it will work with TWRP installed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
Smart move my friend!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 808phoneaddict:
So I updated to V with the toolkit, but ended up trying to boot to root but got stuck... Fastboot flashed the stock boot.img, and am up and running without root right now...was wondering if u thought it was safe to just try and root again with the toolkit this time, or if I should reflash the stock IMG so I'm all clean again, I don't really know what chainfires boot to root does/changes so not sure if I'm good to just try root again or if I should clean it up again
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
Its a bit hit and miss with rooting the newer builds I think. Reflashing the stock image and wiping userdata will not do much good as the root works from outside the system. If you have flashed the stock image then try the root-to-boot again and see if it works. If it doesn't work you may have to wait a day or so. Im adding twrp but disabling the functions until its out of alpha version but you can be a tester for me if you wish and I will pass on an "enable code" to try twrp rooting.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
Alright so the steps to flash the factory image for pixel XL needs revised I guess, I used the toolkit to do so and chose not to wipe my internal memory and after rebooting it took me right back into my old setup, of course wiped out root, and TWRP, but it was not a stock vanilla experience like flashing a factory image on my 6P. SOme commands or whatever need revised as I am sure the slots are being messed up and this is what I have been trying to figure out for days, how to get it back to an out of box state, with no success. I have posts, on G+, google forums, everywhere, and nobody can figure it out
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
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.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yung40oz84:
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?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] orb3000:
Thanks mate, nice to see familiar amigos still around!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
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.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
I have a private message to send (with a gift included). If you can delete a couple of your messages I can send it to you as it won't let me right now.

Mark.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MReprogle:
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!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
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.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sulpher:
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.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] michaelbsheldon:
Are you unlocked? If yes, that's why the message appears.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sulpher:
Ah ok, im such a newb, thanks ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] orb3000:
Done! :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jayhammy:
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!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mskip:
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.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] behlski:
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?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wase4711:
honestly, those questions really dont belong in a development tool thread...there are several other threads that address those questions