yashsingh1/xdaforums huggingface dataset:
[Google Pixel Guides, News, & Discussion] sliding_billy:
Installing SuperSU from the RC1 img or installing RC2 and then installing SuperSU from there?
[Google Pixel Guides, News, & Discussion] Cares:
Looks like I'll wait on May factory images ...
[Google Pixel Guides, News, & Discussion] Tulsadiver:
After booting into TWRP, flashing twrp pixel installer, then trying to boot back into TWRP bootloops without even getting to supersu.
[Google Pixel Guides, News, & Discussion] jmartin72:
The reasons to stay stock, are starting to out weigh the reasons to root.
[Google Pixel Guides, News, & Discussion] sliding_billy:
Gotcha. That stinks! I have never booted back into TWRP after installing. I have just went straight to SuperSU installer after RC2 install. I imagine that would have just created a different issue.
[Google Pixel Guides, News, & Discussion] Tulsadiver:
They will probably figure something out. Nexus 5X didn't have any problems with their May update.
[Google Pixel Guides, News, & Discussion] sliding_billy:
I'm sure. I am in no hurry for what is most likely just a security update.
[Google Pixel Guides, News, & Discussion] mikeprius:
Sideloading the correct image now. Pisses me off there is a separate image for Verizon. I flashed the Verizon version instead of the standard one.

---------- Post added at 04:42 PM ---------- Previous post was at 04:35 PM ----------

Loaded the May images on the 5x. Magisk is good to go for the 5X. Pixel is stock right now.
[Google Pixel Guides, News, & Discussion] FernBch:
Glad I came here before installing the May update.....
[Google Pixel Guides, News, & Discussion] CatThief:
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
[Google Pixel Guides, News, & Discussion] Tulsadiver:
Both
[Google Pixel Guides, News, & Discussion] GuestK00143:
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
[Google Pixel Guides, News, & Discussion] Tulsadiver:
Works for me. Thanks Misterxtc!
[Google Pixel Guides, News, & Discussion] Swerner1975:
How did you do that?

UPDATE: Problem solved...
[Google Pixel Guides, News, & Discussion] GuestK00143:
If you didn't figure it out or anyone else needs help I downloaded both the K and L updates, installed L, rebooted to bootloader and ran the following command with the K bootloader then reboot bootloader. After that you can install TWRP and root.

fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126
[Google Pixel Guides, News, & Discussion] Swerner1975:
THX!
[Google Pixel Guides, News, & Discussion] Tulsadiver:
If you flash manually you just skip the first step. The bootloader part.
[Google Pixel Guides, News, & Discussion] bush911:
Just downloaded the latest full factory image.

Is it possible for me to upgrade without modification to bootloader, then root.

If it's OK, please show me detailed commands.
[Google Pixel Guides, News, & Discussion] Tulsadiver:
If you use the flashall method you need to have both updates or at least the April bootloader. The April bootloader is enclosed. I've renamed it just bootloader.img. Unzip and flash it using the above commands after you are done with installing the May update.

Remember to take off the - w or your data will be wiped.
[Google Pixel Guides, News, & Discussion] pahlerc1:
thanks for the news guys... i updated to may n2g47o, saw everyone having issues getting TWRP and SuperSU running.. followed instructions mentioned in this thread to go back to n2g47e (april) bootloader, then installed TWRP and SuperSU worked like a charm.. thanks :)
[Google Pixel Guides, News, & Discussion] churchmice:
Well, this does not seem to work.

When executing fastboot -w update image-sailfish-n2g47o.zip command, it will check the bootloader and radio version.

Since the bootloader is outdated, the command will abort.
[Google Pixel Guides, News, & Discussion] Tulsadiver:
That is not flashing manually. If you want to use that method, follow Misterxtc's instructions.

Usually bootloader is first but in this case if you are on April update you would flash the following of the May update.

fastboot flash radio radio.img

fastboot reboot-bootloader

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

fastboot flash system system.img

fastboot flash system_b system_other.img

fastboot flash vendor vendor.img

fastboot flash modem modem.img
[Google Pixel Guides, News, & Discussion] skawtnyc:
An easier way is to use the flash-all script without -w, reboot into bootloader then individually flash the older bootloader before applying TWRP and SuperSU.
[Google Pixel Guides, News, & Discussion] mikeprius:
So you update everything except the bootloader and good to go ?
[Google Pixel Guides, News, & Discussion] Tulsadiver:
Yes.

It appears the boot.img (maybe all the img's) are now signed as of May update. Any changes to them now needs to be signed as well.
[Google Pixel Guides, News, & Discussion] killall:
Managed to get this working using the April bootloader but had to download the full April factory image and extract bootloader as the one attached by Tulsadiver did not work.

Also had to make sure I flashed to slots A and B.

fastboot flash bootloader_a bootloader-sailfish-8996-012001-1702151126

fastboot flash bootloader_b bootloader-sailfish-8996-012001-1702151126
[Google Pixel Guides, News, & Discussion] fire105:
Anyone know where the update file is located once downloaded? I accidentally had auto-update turned on, it has downloaded file but not installed yet. I turned off auto-update but am afraid it will still run this downloaded update on a restart. Anyone know where the update file is that I can delete?
[Google Pixel Guides, News, & Discussion] doubleho:
is doing this flash the bootloafer to both slot a and b?
[Google Pixel Guides, News, & Discussion] Tulsadiver:
There is no need to flash it to bootloader a and then b. Just fastboot flash bootloader bootloader.img or however you have it named.
[Google Pixel Guides, News, & Discussion] gubacsek:
I managed to make it work \o/

I have root with May bootloader....

I followed the instructions from Chainfire in this thread: https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606

I flashed the phone, installed twrp, dumped the boot images, signed them on my laptop, flashed them back, then rebooted into the installed recovery, installed root, again dump/sign/flash back boot images, reboot, and it is working :D

The process was not user friendly... Chainfire said, that he will work on an "on the fly" signing of the boot images in recovery (the signer application is a jar, and i didn't manage to execute it in recovery... ), and he will release a new version when it is done.

If you can't wait (like myself ), I can try to write a little how-to, but I think by the time i'm finished, the updated root and twrp installers will be out :D
[Google Pixel Guides, News, & Discussion] robocuff:
I could be wrong but I think once you've downloaded it there's probably no way to stop it. It downloads the update and then flashes it to the inactive slot. It all happens behind the scenes so to speak so the next time you reboot, it's​ already installed. When you reboot, it ei
[Google Pixel Guides, News, & Discussion] :
Either way I think a how-to would be helpful to many. I myself am not familiar with this device at all and would like to see how you did it.
[Google Pixel Guides, News, & Discussion] robocuff:
I could be wrong but I think once you've downloaded it there's probably no way to stop it. It downloads the update and then flashes it to the inactive slot. It all happens behind the scenes so to speak so the next time you reboot, it's​ already installed. When you reboot, it boots to the opposite slot you were on when it downloaded. Somebody can correct me if I'm wrong but I'm guessing you've already got it installed.
[Google Pixel Guides, News, & Discussion] :
WooHooo check it out.... https://xdaforums.com/showpost.php?p=72175816&postcount=14
[Google Pixel Guides, News, & Discussion] Tulsadiver:
Sure didn't take him long?
[Google Pixel Guides, News, & Discussion] :
Not at all and it works great on the May update.

---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------

@TonikJDK should pin this to the OP as the solution for now... https://xdaforums.com/showpost.php?p=72175816&postcount=14
[Google Pixel Guides, News, & Discussion] gubacsek:
See? just as I said :D Chainfire came up with a working solution faster then I would have described a terrible manual fiddling ;)

He is really awesome! What would we do without him ?
[Google Pixel Guides, News, & Discussion] fire105:
awesome :/

---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------

awesome :/
[Google Pixel Guides, News, & Discussion] 32BitWhore:
So theoretically I can sideload build L as I normally do, boot TWRP, flash TWRP, flash SU, then flash Chainfire's BootSigner and be good to go?

Just want to make sure I'm understanding this before I take the plunge.

Also, is this necessary for custom Kernels as well?

Edit: Tried it anyway. Works perfectly for sideloading to L from K.

Sideload -> reboot bootloader -> fastboot boot TWRP -> flash TWRP (or don't, your choice) -> flash SU -> flash VerifiedBootSigner -> reboot

Haven't tried ElementalX kernel yet. Think I'll drive around on stock kernel for a bit.
[Google Pixel Guides, News, & Discussion] 32BitWhore:
Yep, just the OTA L build image, not the factory image.
[Google Pixel Guides, News, & Discussion] beez1717:
So as a Pixel noob but an Android veteran, is there somewhere that someone posted the exact directions to root if you took the OTA may update? The freaking guy at Verizon updated the phone before he gave it to me yesterday :(
[Google Pixel Guides, News, & Discussion] roirraW "edor" ehT:
If you have a Verizon Pixel, you can't unlock the bootloader on 7.1.1 or higher, so you can't root. Likely ever. It likely already had 7.1.1 on it before he OTAd to the very latest security patch, but there's always a possibility that you could go back to the store, tell them (whatever) and see if a new untouched Pixel that they have only has 7.1.0, but I doubt it by now.
[Google Pixel Guides, News, & Discussion] fire105:
if i have a verizon version that i unlocked with depixel8, is there some action i should take before restarting my device?
[Google Pixel Guides, News, & Discussion] FernBch:
If you have unlocked you can update at will without issue. If you have unlocked and rooted and/or flashed TWRP you must restore the stock BL for the build you are on before taking an OTA. Either case you will remain unlocked after updating. You need to do nothing but reboot.
[Google Pixel Guides, News, & Discussion] Sh0X31:
If I'm already on the Mai-image with April-bootloader & SuperSU I just need to flash the Mai-bootloader and "VerifiedBootSigner.zip" or EX 1.11 (include the boot signer)?
[Google Pixel Guides, News, & Discussion] ubigred:
Any complete instructions for a noob?

Pixel

NHG47L

7.1.2

May 5th update

Much appreciated.
[Google Pixel Guides, News, & Discussion] :
Make sure you have TWRP Bootable version (NOT INSTALL), SuperSU flashable and Verified Boot Signer flashable.

Step by step:

Reboot to bootloader with adb or powering off then on while holding down volume button.

Enter in cmd > "fastboot boot twrp.img"

In TWRP locate and flash SuperSU.

In TWRP locate and flash VerifiedBootSigner.

Reboot.
[Google Pixel Guides, News, & Discussion] ubigred:
Reboot command?
[Google Pixel Guides, News, & Discussion] :
If your device is on,

> adb reboot bootloader
[Google Pixel Guides, News, & Discussion] bschatzow:
For some reason when the phone is in recovery I can't see the phone with ADB. If I run ADB when the phone is not in recovery I can run the ADB devices which shows my phone. Fastboot works fine and I was able to update using the following from the full factory file download. My active boot slot is A

fastboot flash --slot _a bootloader bootloader-marlin-8996-012001-1703151359.img

fastboot reboot-bootloader

fastboot flash --slot _a radio radio-marlin-8996-012901-1703291803.img

fastboot reboot-bootloader

fastboot update --slot _a --skip-secondary image-marlin-nhg47l.zip

Fastboot reboot-bootloader

fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img

From here I flashed TWRP and SU then VerifiedBootSigner

Rebooted and all updated correctly. Anyone have any ideas on why ADB doesn't see the phone while in recovery? Do I need to uninstall twrp prior to adb or can i use the twrp sideload?
[Google Pixel Guides, News, & Discussion] :
Check your ADB version. If you don't have the latest that could affect it. Also, try reinstalling the drivers. The basics of trouble shooting. If these are up to date, revoke debug auth in settings and delete the key files in .android folder.
[Google Pixel Guides, News, & Discussion] bschatzow:
I have the ADB from 4/19. Don't understand the device driver issue. My computer see the phone from command line fine. From the same window fastboot works. ADB works except in bootloader mode. I have twrp loaded and if I run adb reboot recovery my computer sees the phone. Only can't see the phone in bootloader mode.
[Google Pixel Guides, News, & Discussion] doubleho:
can we flash twrp zip after the above procedure ?
[Google Pixel Guides, News, & Discussion] robocuff:
Tlhat's normal. ADB only works when the phone is booted to the OS. When booted to the bootloader, you have to use fastboot and from what you posted, that's working as it should. Fastboot devices should show your phone when in the bootloader. ADB devices won't.
[Google Pixel Guides, News, & Discussion] FernBch:
If you want TWRP install you must it after fastbooting the TWRP image. You then reboot into TWRP, flash, SU, then sig verification.
[Google Pixel Guides, News, & Discussion] :
No. Just reboots into recovery every time. You have to flash TWRP first beforehand​. I'm against using it for the time being. In the times I've used it, it doesn't ask to decrypt device. I have to reboot recovery about 10 times before it asks. And when it does and I flash something, it doesn't stick. This is my experience with it. For whatever reason the bootable version from ADB works without a hitch. Can flash and asks for decrypt.
[Google Pixel Guides, News, & Discussion] doubleho:
saw someone reported that they can't reboot into twrp after flashing twrp, had bootloop
[Google Pixel Guides, News, & Discussion] bschatzow:
Then how do you do ADB sideload the ota.img monthly update?
[Google Pixel Guides, News, & Discussion] robocuff:
Maybe I'm misunderstanding you. If you just boot to recovery and run adb devices your computer won't see the phone. You have to first select the option in recovery to side load the​ OTA. Your computer should recognize the phone then. Have you done that?
[Google Pixel Guides, News, & Discussion] FernBch:
If you are wanting the May update I believe the process is update, fastboot twrp.img, flash twrp, SU, the flash sig verification.

Read more here

https://xdaforums.com/showthread.php?t=3600606
[Google Pixel Guides, News, & Discussion] doubleho:
so I do not have to reboot after flashing twrp to avoid bootloop?
[Google Pixel Guides, News, & Discussion] bschatzow:
If I boot to recovery TWRP loads as I have loaded this as my recovery option. Do I run advanced and run ADB sideload from here?
[Google Pixel Guides, News, & Discussion] robocuff:
Yes. In TWRP choose advanced and then select adb sideload.
[Google Pixel Guides, News, & Discussion] bschatzow:
I will try next month. When I tried it yesterday there was an error message on the top screen in TWRP but it looked like it was ready for side load. It may be a bug in TWRP. I'll try the TWRP forum to see if others have done this successfully. Checked TWRP RC1 for Pixel Devices by Dees_Troy and did not see anyone that said it worked. One of the quotes "i tired it didn't work..try and see if it works..worst case scenario..reflash boot img to a and b sideload the ota flash boot back to twrp.."
[Google Pixel Guides, News, & Discussion] mikeprius:
Is this generally the way to flash manually if you don't use the flash all bat ? There are so many files now vs the Nexus and j haven't seen a manual sequence on which of those may files to flash vs boot image system userdata etc which was much more simple before

---------- Post added at 03:18 PM ---------- Previous post was at 03:11 PM ----------

I think I read chainfires post at least 10 times. So the new may bootloader isnt not booting unless the kernel is signed by the device ? How does this affect custom kernels
[Google Pixel Guides, News, & Discussion] FernBch:
When I first moved to the Pixel I used the flash-all.bat method. I was experiencing some bugs after a few days on each build so when the new one came out I wanted to start fresh so I left the batch file alone. I could watch what was happening in the batch file as it moved through each step.

When I first started on Android a few years back it was just a simple zip file. Over the years the complexity of the files grew and now they are nothing like what they use to be, but the basic process is still the same. To me anyway.

The only thing different with the may update is Google has changed/introduced a new boot signature verification method, if I understand correctly. Hence the reason why the April bootloader needs to be manually fastbooted to get a few things working now. Just need some time for the devs to catch up.
[Google Pixel Guides, News, & Discussion] Jubbard:
Oh my god thanks I couldn't follow the other comments :D
[Google Pixel Guides, News, & Discussion] mikeprius:
Probably eventually SuperSU will pack in the boot sig script evetually as the norm
[Google Pixel Guides, News, & Discussion] skawtnyc:
The manual process is no longer necessary. Get the boot signer zip file from Chainfire's post, apply it immediately after installing the SuperSU zip in TWRP before you reboot, and you should be fine.

https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[Google Pixel Guides, News, & Discussion] CatThief:
It's been a while, but try looking for update.zip inside /data/data/com.google.android.gms/app_download
[Google Pixel Guides, News, & Discussion] gianptune:
So can we get a bit of clarification? I've tried to follow those steps but I'm still getting stuck at the boot animation. Can somebody show me where I'm messing up?

unlock bootloader

adb reboot bootloader

(cd sailfish-n2g47o && ./flash-all.sh)

wait for flash to complete and device starts to boot up. reboot to bootloader

fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img

adb push SuperSU-v2.79-201612051815.zip /tmp/the.zip

adb shell twrp install /tmp/the.zip

adb push VerifiedBootSigner-v3.zip /tmp/the.zip

adb shell twrp install /tmp/the.zip

adb reboot

Ive also tried "fastboot boot boot-to-root.img" instead of flashing SuperSU-v2.79-201612051815.zip. neither one of these has gotten me to boot into a working rooted system.
[Google Pixel Guides, News, & Discussion] FernBch:
I fastboot booted the TWRP image. When it booted TWRP I flashed TWRP, then flashed SU. If I understand correctly the next step is to install the AVB zip from TWRP.
[Google Pixel Guides, News, & Discussion] adam3914:
Mine does not work either, I am using the same SuperSU and twrp except I install SuperSU and VerifiedBootSigner inside TWRP. The phone says that there is no SuperSU binary.
[Google Pixel Guides, News, & Discussion] FernBch:
It shouldn't be needed but try booting TWRP, delete fstab.sailfish from it's file manager, flash SU and the boot signer, then reboot system.
[Google Pixel Guides, News, & Discussion] pstgh:
Has anyone else had troubles since this "May Update" ? I was running a Pixel (from Google direct) unlocked, rooted, and I'm a fairly heavy user of Google Voice on my phone (e.g. I have all of my calls originate through GV instead of my carrier, which is VZW by the way).

Anyway, took the May update and decided to re-root using SU and Chainfire's new V3 signature zip... then my troubles really started... specifically, my phone app (the actual voice dialing capability) went all haywire. The phone seemed to work for apps (e.g. texting and/or various regular data-using apps), but the phone simply wouldn't function properly.

Anyway, I've been taking lots of corrective steps to try to fix it (e.g. wiping, re-flashing older images - like April) and recently noticed that I was on the wrong build (I was on the May update, but it was the VZW build and not the un-attached build), so I re-flashed it once back to the proper May update and that didn't work, then I re-flashed it again, and it seems to be working... keeping my fingers crossed at this point. I've not yet tried it very rigorously, so we'll see, and I've not yet loaded GV back onto the phone- I want to get it working properly before trying that.

I'm curious if when you re-flash a phone using flash-all.bat, does it normally only flash to one slot or both? I'm feeling like it only went into one slot and then rebooted into the old slot that wasn't functioning properly. Then, the second time around, since it started working, maybe that's because it flashed to the other slot but then rebooted into the slot that was flashed previously? I don't have that deep of an understanding as to how the flash-all.bat flashing method works as it relates to the two slots on this phone, but again, I'm hoping that it will keep working... meanwhile, Google is sending me a new phone. I'd prefer to keep my original, but at least I have options! Thanks for any thoughts that you might have here.
[Google Pixel Guides, News, & Discussion] henk-jan:
help on updating

Please some help.

I'm trying to install the may OTA on my Pixel 128 GB without succes.

This moment I've Android 7.1.2 build N2G47E

Kernel: ElemetalX-P-1.11

TWRP sailfish 3.1.0-0RC2

1st try: flash OTA + TWRP and right afterwards the april bootloader

result: bootloop

2nd try: by adb command flash-all.bat (without /w)

error: not enough memory on slot A

3rth try: by TWRP *flash ota n2g47o-2fa538ea.zip

*immediately afterwards TWRP-pixel-installer-sailfish-3.1.0-ORC2.zip

*flash SR3-SuperSU-v2-79-SR3-2017011422372.zip and right afterwards VerifiedBootSigner-v3.zip

Then reboot.

Error: ram dump, writing to Ext4 file and again I'm on build N2G47E.

What am I doing wrong?
[Google Pixel Guides, News, & Discussion] pstgh:
Did you try rebooting again? People often get a confusing message / result from these various flashing methods because of the new dual slot architecture- you flash to one slot, reboot and voila, you're in the other slot with the old image. Rebooting a second time brings you back to that slot that you flashed... maybe?

There have been a number of issues with this new update though, so I wouldn't be surprised if Google shoots out another update relatively soon...
[Google Pixel Guides, News, & Discussion] henk-jan:
solved

Thanks for your reply

It's solved (after 3 weeks trying) thus:

I flashed the OTA, then rebooted

Flashed TWRP again, rebooted

Then flashed SU + VBS v3, rebooted

At last flashed ElementalX and everything is ok now :victory:
[Google Pixel Guides, News, & Discussion] pstgh:
What is ElementalX ? ...a ROM of some sort?

Also- did you flash OTA or sideload? If Flash, did you use TWRP or the flash-all.bat method? If TWRP, how specifically do you do that? Thanks!

---------- Post added at 12:21 PM ---------- Previous post was at 11:35 AM ----------

For grins, and try getting my Pixel back to running properly again, I have flashed the May update, and then have tried flashing the April bootloader.img file, but I'm getting the following error:

unknown partition 'bootloader-sailfish-8996-012001-1702151126.img'

error: cannot determine image filename for 'bootloader-sailfish-8996-012001-1702

151126.img'

Any thoughts here?

Thanks!