yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] chugger93:
how do you run adb shell in the toolkit? or maybe not even in the toolkit but the folder that holds the installation. I ran adb-toolkit.exe but I cant do adb shell

I tried doing adb-toolkit.exe adb shell , but that doesnt work. I need to access the adb shell

I did adb-toolkit.exe shell but it says error: more than one device emulator
[Google Pixel ROMs, Kernels, Recoveries, & Other De] xdeslitx:
delete
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mskip:
Do you have any emulators installed?

Type 'adb-toolkit devices' to show what devices are connected to your pc and serial numbers or the devices.

Type 'adb-toolkit -s serial_number shell' to start a remote shell in the target device. Enter commands. Type 'exit' to exit the shell.

Type 'adb-toolkit -s serial_number shell command' to send a shell command to the intended device and then exit the remote shell.

example: 'adb-toolkit -s 594b972e shell ls -l' to list the contents of the root folder.

I keep meaning to add device selection to the toolkit if more than 1 device is detected but would have about 400 commands to change and something else always seems to come up. I will put it on my list to do soon though.

Hope this helps, MArk.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mskip:
I have added a message in the first post to say that dpixel8 does not work on 7.1.1 or later to unlock the bootloader on verizon/ee uk models. At the moment I do not know of any other methods to unlock locked bootloaders, sorry.

Mark.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] regis.stration:
WiFi hotspot not working after flashing stock NMF26o

SOLVED

: Turns out I was testing the wifi hotspot immediately after flashing the factory image but before the Project Fi app had a chance to update to the latest version. I factory reset a few times testing before and after Fi app updating each time and confirmed it. Thanks. No need to read the rest of this post!

====================================================================

I got a pixel a month ago, unlocked it, and rooted with boot-to-root method. All worked well until I tried the hotspot. Would connect with devices, but not connect to internet. Called Fi support and they said it was because I bought my phone from google store, but not from google Fi. Yes, when I ordered the phone, I assumed it came with the Project Fi sim, so when the phone was delivered, I was stuck. I ordered the Fi sim and got it all registered when it came. Their solution: Send me another phone from Project Fi.

So I got the 2nd phone, and did a minimal set up with my google account and Fi to test the hotspot. It worked. Then, using the android toolkit I unlocked the bootloader and flashed the stock nmf26o. The process completed ok. I rebooted the phone several times, set up my google account and project fi again, but now the wifi hotspot was again not connecting devices to the internet!! Everything else seems to be working fine.

Is the Project Fi stock factory image different than standard google images? Is there something else I'm missing? Anyone else can confirm these results?

Thanks in advanced
[Google Pixel ROMs, Kernels, Recoveries, & Other De] cswithxda:
Everytime at launch, the toolkit check for all required files and download as needed. However, Superuser by CWM is the one that gets a failed download every time. Not a big issue for me as I do not use it, but the problem is it keeps trying to download and time out every time I launch the module, which takes several minutes and is annoying. How can we solve this issue? I tried a fresh install of the toolkit but it didn't solve the issue.

If it helps, here is the screenshot. Basically, to wait out the download process, which fails everytime, it takes about 2 minutes at least.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] lamjanus:
Where is the latest factory image/OTA in the toolkit? Please update the kit.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] obxftbll1:
OTA Question

Great toolkit, mskip. Quick question about a hole I may have dug myself into. Got a Pixel yesterday on Verizon. First thing I did was unlock the bootloader with dePixel8. I then proceeded to set up as normal, transferring all my content, etc. I used the toolkit to root the device, using the option to work with any stock build because I'm running build NDE63N. I was sure to choose read only in TWRP so I could take OTAs easier.

I then decided I wanted to unroot so I could take the 7.1.1 update. Again, I chose to unroot using the work with any stock build option. This is where things started to get hairy. When the toolkit tried to push stock recovery back to the device at the end of the unroot process, it gave me an error. I decided to try and unroot by going under build NDE63X and choosing the unroot option there. Everything, including the push of stock recovery, worked fine. However, when I try to take the OTA, the installation fails. Is this because I'm running build NDE63N and my stock recovery is from NDE63X? If so, what are my options to get to a place where I can take OTAs again? Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
I would use the toolkit to go back to complete stock take the update and go from there. I tried to take the OTA last month the same as you and somehow the process while unrooting and flashing stock recovery failed and I just did a complete wipe and restore then updated.

---------- Post added at 04:53 AM ---------- Previous post was at 04:51 AM ----------

On a side note I did use this toolkit to side load the latest OTA this afternoon.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Dodgexander:
Verizon & 7.1.1

My gf is soon going to buy the pixel from Verizon and as I understand if she updates to 7.1.1 she will lose the ability to unlock it's bootloader. I know how to avoid this (if the phone doesn't come with 7.1.1 preinstalled) but does this mean she shouldn't try to use 7.1.1 at all? Even with custom ROM or after unlocking the bootloader?

I'm worried that even after unlocking bootloader a Google ota or custom ROM may put the new patched locked bootloader on her device so is it better to avoid 7.1.1 even after unlocking the 7.1 bootloader?

Secondly, does anyone know if she buys her plan from best buy instead will she still get a Verizon pixel or will she get the stock model that just works on Verizon? Sadly her family plan limits her to Verizon only.

Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dchurch85:
If she buys from Best Buy, it'll be a Verizon Pixel.

If you unlock, you will always be unlocked. I unlocked, and took the 7.1.1 and I didn't lose my unlocked status. Have been able to flash whatever I have wanted.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] acidspider:
Is nmf26u not unlockable ? I cannot see it in the list on the toolkit
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dchurch85:
It is not. No way to unlock a Verizon model after they have taken 7.1.1
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
I see it asked about frequently so here are a couple points to remember.

If your Pixel came from Google it can be unlocked no matter what Android version you have.

If you bought from Verizon and have unlocked it will always be unlocked. You can take the OTA no problem and you remain unlocked.

If you have the Verizon device, are on 7.1.1, and are locked you cannot unlock. There is no method and to my knowledge a new one is not being sought out. You also cannot downgrade to be able to unlock. 7.1.1 blocks the ability to downgrade.

For either version if you are rooted, TWRP, or modified system in any way you cannot take the OTA. Because things are modified the OTA will fail to install. You can either unroot and restore the stock boot.img, sideload, or fastboot flash-all to upgrade. After updating you will need to reroot and TWRP if you want them.

If you manually update via fastboot flash-all removing the "-w" from the flash-all.bat file will allow the update to install without wiping user data.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] acidspider:
I am on ee, is it just not unlockable yet? But will be?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dchurch85:
I believe it's still not unlockable because it is a Verizon phone. Their phones are unlocked for any network, but it's still their tweaks on the device and the Verizon model. There are 2 separate models and the Verizon model is not unlockable after 7.1.1.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] acidspider:
OK, I have a new unit now which I unlocked first now before updating, I am now on nmf26u, can I still use the toolkit to install twrp? As the build is not shown in the list.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mskip:
Just select the closest build available as they are all have pretty similar boor/recovery images.

Mark.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mskip:
Update Available for Google Pixel device module v1.1.8 [Pro Users]

Changelog:

+Added Support [including root] for Android 7.1.1 NMF26U, NMF26V 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]

You can also download the stock image from https://developers.google.com/android/images then move it to the put_google_factory_image_here folder and flash via options 9,2 if you do not have/want the pro version.

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 ROMs, Kernels, Recoveries, & Other De] lamjanus:
Thanks Mark!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] klebane:
issue attempting to unlock bootloader with toolkit

I have a Verizon pixel with software NDE63P (7.1.0). I am attempting to unlock the bootloader. I have used the toolkit on different windows PC's (windows 7 and windows 10) to load adb drivers. I have spent hours and have not had any luck getting the depixel8 file to run in adb. Questions:

1. When I go to paste in command prompt the first line of the depixel8 command I get message "adb not recognized as an internal or external command, operable program or batch file" (I did an internet search on this error and it says it is an environmental variable problem related to the "Path"). Should I be running into this problem using the toolkit?

2. Where do I place the depixel8 file in the toolkit file structure? I know it is to go where the adb.exe file is but I cannot find the adb.exe file. Does it go in the tools folder of the toolkit? Does it go in the 'place files to be pushed here' folder?

Thanks in advance for any help....
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
I unlocked the bootloader uusing ur toolkit but couldnt root my phone. everytime i try it keeps saying Pushing Beta super su to this folder but then it says error. when i tried manually flashing it on TWRP it wouldnt work. How do i do it?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
When I had this problem it was easily solved by putting both the su zip as well as TWRP zip ( if you desire TWRP ) and use the toolkit to boot into TWRP image then unplug it from your PC and install the zips. Just make sure it sure it asks for a password if it's encrypted just repeat the process
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sharingspider:
Is there any version for MAC yet ?

Great Job in Making This !! :cowboy:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shadowfiber:
HI, hoping for some help if possible.... Just received my new phone and first thing I wanted to do was root it.. It's already on 7.1.1 26U and the program doesn't seem to be able to function without the unlocked bootloader. My phone is from Verizon.

Am I stuck? Hoping for some help if possible.

Thank you!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] wase4711:
gotta do some reading bro; 7.1.1 locked bootloader on Verizon is a no go for anything at this point
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shadowfiber:
Total bummer, I was getting hints of that, but I could never find anything solid. Thank you.. Here's hoping that changes.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Slomies:
I tried to use the toolkit on my Pixel (unlocked) and I'm stuck in a bootloop to TWRP. I unlocked the bootloader and tried to install twrp and root. Any ideas how to fix it and avoid bootlooping again?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] psu90:
I got my Verizon 7.1.1 26U unlocked and rooted. First download 26U image from the Google site. I then enabled developer options, enabled USB debugging, flipped OEM Unlocking, and used this tool using the downloaded 26U image. I did keep the stock bootloader as the switching back and forth when loading an update is a pain.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Not sure what you mean. You can't unlock a Verizon pixel bootloader once its already on 7.1.1 unless it was unlocked before 7.1.1...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] psu90:
I got the phone about a week and a half ago. I've been unlocking and rooting since the HTC Thunderbolt. I was surprised myself when it worked after what I read. The only variable I can't account for is that the Pixel was out of stock at Verizon. It was actually out of stock every place in my area except for 1 lone Pixel that just came into Target that day. It should be a Verizon, not a Google version. It was already 7.1.1 when I started. Also simply flipping the OEM Unlocking didn't unlock the bootloader. I may have just lucked out, but what I described worked for me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
It's defineltly a google pixel and not a Verizon pixel then. There's a thread somewhere on here about how to check.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] psu90:
I'll have to find the thread and check my phone. The part that made me believe it was a Verizon phone is on a Google phone flipping OEM Unlocking in Developer Options unlocks the bootloader. That didn't completely do it for my phone.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
On a google phone that doesn't unlock the bootloader. It allows it to be unlocked but it still has to be dome with fastboot

Edit. Here's how to check if it's a Google store pixel or Verizon pixel.

https://xdaforums.com/pixel/how-to/google-pixel-sailfish-tips-tricks-t3494982/post70729397
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sharingspider:
Does this toolkit support 7.1.2 as well or only 7.1.1 - can someone please confirm this
[Google Pixel ROMs, Kernels, Recoveries, & Other De] henk-jan:
I'm new at the pixel. Trying to unlock and unroot my device but I get an error (see attachment)

What to do.

I've the pixel 128 gb build 7.1.1 build number NOF26V (Dutch/Europe)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] henk-jan:
second attachment
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ziggary:
works for me like a dream well worth the donation !
[Google Pixel ROMs, Kernels, Recoveries, & Other De] scumfromohio:
Whenever i click the link to get the tool i get a 500 internal server error. Is it just me?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] henk-jan:
explanation?

I finally managed to root my pixel (with ext USB) but I get an error (see below) using the unlocked skipsoft toolkit

What does this mean?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nerdtaco:
I checked the bootloader locked state on my brand new 7.1 pixel to make sure it could communicate with my computer. When the phone restarted it suddenly became 7.1.1. I turned off OTA updates beforehand. I'm pretty pissed off about that right now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] wase4711:
if its not a verizon, it doesnt matter
[Google Pixel ROMs, Kernels, Recoveries, & Other De] chugger93:
Hey All,

I ran the tool when I first got my pixel, rooted and unlocked bootloader. However, I got the 7.1.1 OTA update somehow...and now my phone lost root. I ran the tool again, but there is no build in the tool that matches mine. 7.1.1 NOF26V.

I was gonna try to reroot...but not sure which build to select since I cant select it as an option. Got it from google play store. Any thoughts?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nerdtaco:
It's BigRed. :(
[Google Pixel ROMs, Kernels, Recoveries, & Other De] henk-jan:
Nice to quote yourself.........

I found the solution by using the password entering TWRP. The disk became decrypted and now it works.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rootnik:
I'm stuck with a soft bricked verizon pixel and could use some help...

It started when I was running Pure Nexus and decided to go back to stock by downloading the google factory image (7.1.0 (Verizon, NDE63X) and using flash-all.bat

I'd get an "unknown error" during the flashing system step.

I've reinstalled the latest adb/fastboot, drivers and get the same thing. Redownloaded the factory image incase it was corrupt...

Using this toolkit, I installed it in a different directory, let it download it's initial files, let it download the factory image itself and get the same error while flashing the system image...

This is all I am able to copy/paste, everything before this completed successfully...

It is sitting on this last step "Flashing update image again using standard command.." for hours now and doesn't seem to really be doing anything.

To add insult to injury, I never backed anything up before trying to go back to stock. I'm an idiot, ugh.

Help please????

edit: This is awesome... I can successfully flash any factory image for the pixel EXCEPT the one for Verizon (NDE63X) which gives me the errors above. This leaves me with no signal, so I can't get past the activation screen.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] CiViCKiDD:
I donated this morning, and was under the impression that the code would be sent instantly. Nothing yet 12 hours later.

I also emailed the paypal email address w/no response. Kind of a bummer, my time is super limited and I wanted to reflash this weekend with the latest OS builds on my unlocked Verizon pixel.

To the developer: please look into this!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] buzzboy:
You may need to be patient. Apparently the Dev has been unwell in hospital. I hope he feels better soon.

Edit: It may be a long shot, but have you tried using the reminder page?

http://skipsoft.net/donate/reminder.php
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Relative_Wind:
Having an issue wondering if anyone is able to assist.

I'm on the Google Pixel 128 GB, 7.1, build NDE63L. Trying to root and flash Pure Nexus.

Unlocked the bootloader, fine no big deal.

I use this android toolkit, and use the method where I basically push TWRP.zip and SuperSU.zip, and flash the TWRP from my PC.

So I start out booted into stock android. The toolkit reboots the device into fastboot, then flashes the TWRP image. I follow the instructions, which say to flash the TWRP.zip from TWRP, delete fstab.sailfish, and then reboot to recovery.

Well when I reboot to recovery, the contents of the /sdcard/ directory appear to get wiped and are replaced by a bunch of folders that have seemingly random strings for names. Critically, SuperSU is gone. If I try to reboot to fastboot and push SuperSU.zip, I can't, it gives an error.

Edit:

Oh yea, and when this happens, if I try to reboot to Android, I get stuck in a bootloop and the only way I know how to fix it is to revert to stock basically.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
All you can do now is use the toolkit to restore. When u use the toolkit to flash twrp you should then set up a password or pin then enable USB debugging then ( here is what I did) place a copy of twrp rc1 on your SD card. Along with the latest su. Use the toolkit to boot twrp image ( if it does not ask you for your unlock pin stop and repeat the reboot process do not swipe to allow modifications) . once you do this take the phone and flash the twrp zip that u places on your SD card. Then flash su and your done
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Relative_Wind:
Thanks a ton!

So with this, I am actually able to boot to android after installing SU with TWRP. So I'm in stock android with unlocked bootloader, TWRP installed, and root access.

However, now I push PureNexus.zip to the phone, boot into TWRP, and do a wipe (I'm supposed to wipe before installing a new ROM right?) and after the wipe, PureNexus.zip is gone and the folders are all scrambled again. Boot loop happens again, so I have to revert back to stock, which undoes all the nice work that was done.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
It sounds to me like you did it all correctly, but after you installed pure nexus you must have rebooted into twrp and did not get the pass code. The first thing in do with every ROM install us set a fingerprint and pass code. That way every time I boot in to twrp if it does not ask for my passcode I hold down the power button till it reboots if it does not ask for a pass code and you swipe allow modifications then it will not be able to decrypt your files and it will all be jibberish . then you have to repeat the whole process
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Relative_Wind:
Thanks!! This worked perfectly!

Now... the first time I boot into Pure Nexus, it says my ROM doesn't match my vendor image, and to flash NOF27C. So I got the Google factory image, extracted the vendor image, booted into adb and flashed the vendor. I booted into Pure Nexus, setup fingerprint and password.

Then I reboot into TWRP and flash SuperSU.zip again. I try to reboot to system and it never boots. I know the first boot after root can take a while, but we're talking 20 minutes here.

Thanks again for all the help.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
I would have used TWRP to install image and select boot image. You had it done just the wrong vender. Here is what I would do. Use the tool to temp boot TWRP. Make sure you get it asking for a passcode. Go into TWRP flash the ROM again. Then install TWRP then reboot TWRP and install the image then your done
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Dewaynelives:
HOw do i restore to stock with

i have unlocked bootloader and i want to restore back to stock i am currently on pure nexus but i am giving the pix to my wife since i got the xl and she wants it to be stock how do i do that with this ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
Can someone please tell me the steps to unlock and root my new pixel? All i need to do is unlock, root, and flash twrp.

I had an old pixel which had a defect so i sent it back. Does that mean i already have the drivers installed?

would i just hit in the MAIN MENU - 7.1.1

#3-unlock

#4-root

#6- flash twrp

Please let me know

Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mark2410:
hi, just got pixel and the rom is on 7.1.2, so its not being recognised. is it safe to pic a diff version to unlock or do i have to wait till its added?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Will the toolkit be updated to 7.1.2, I know Dev was in the hospital a ways back. Hope all is well, just curious.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kxf41:
Hope he or she is well, I'm wondering the same thing, this toolkit is awesome, well worth the small investment.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bluedawgalex:
unable to download toolkit :(
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nighty:
i donate the full pro version but no code is here..... no email answer, no reaction from the coder mskip.