yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
I am still investigating, but it would seem SU is not working.

I ran flash-all.bat after removing the -w

Boots and runs fine.

fastboot booted twrp RC1 and flash SU 2.79 SR3

It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
Just was a gut feeling that whatever was going wrong in the developer build would somehow been implemented in the May build. I am sure they are unrelated, but that was why I asked before the OP was updated to include the SU break.
[Google Pixel XL Guides, News, & Discussion] James4.0:
The VZ OTA will download if you set the date to May 4th.
[Google Pixel XL Guides, News, & Discussion] jaygleazey:
just checked my phone and got Verizon update without changing date
[Google Pixel XL Guides, News, & Discussion] iceman4357:
My OTA for Verizon didn't hit yet. And moving the date forward didn't help. Hopefully soon.
[Google Pixel XL Guides, News, & Discussion] bush911:
what will happen to supersu if try to flash this full factory image via flashfire and
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
It will be gone.
[Google Pixel XL Guides, News, & Discussion] FernBch:
Pixel users are reporting bootlooping on the May update after flashing TWRP only

https://xdaforums.com/showthread.php?p=72121371

https://xdaforums.com/showthread.php?p=72120712
[Google Pixel XL Guides, News, & Discussion] DR3W5K1:
What are the chances that this was done purposely? "Breaking root and twrp"
[Google Pixel XL Guides, News, & Discussion] yearn2burn:
Anyone try Magisk? I imagine same result.
[Google Pixel XL Guides, News, & Discussion] dowlf:
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
[Google Pixel XL Guides, News, & Discussion] itchy67x:
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
[Google Pixel XL Guides, News, & Discussion] Taebom:
Just use April's bootloader.
[Google Pixel XL Guides, News, & Discussion] itchy67x:
thx that works
[Google Pixel XL Guides, News, & Discussion] GuestK00143:
Thanks, that works for the Pixel too. I flashed April's K bootloader on the May L version no problem. TWRP and SU work fine now.
[Google Pixel XL Guides, News, & Discussion] cam30era:
FWIW: sideload of n2g47o worked fine on my (stock) XL. Did you have any modifications?
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
I haven't tried it yet, but I copied April's bootloader to the May directory. Then while editing out the "-w" from flash-all.bat, I modified it to install the April bootloader instead. Hopefully that will work and save a step or two. :fingers-crossed:

I tried this and it didn't work.
[Google Pixel XL Guides, News, & Discussion] gubacsek:
Guys this is b u l l s h i t ! This damned phone is the flagship android device, it should be the most open, "most developed for" device, the one that has everything first. And what do we have? :D NOTHING! not even a damn working TWRP! For most of the nexii, there was a recovery even before they came out....

Don't missunderstand me! I'm not judging anyone, not blaming anyone but google! They are messing up big time. It looks like they are against the dev community with all these ****s they do with each update. Slots ? No recovery partition? WHY ? What did it bring to us, except that we are ****ed? It's like old times when I owed a samsung device without any development (locked bootloader, no kernel sources, nothing...). Same ****, if we can't even flash root!

I need to check what happens here. The problem is that I am afraid messing up this device which costs a damned fortune, and that I don't know how to debug what is wrong... Does anyone know how to get the latest TWRP sources ?
[Google Pixel XL Guides, News, & Discussion] MrDrift42:
I believe when it goes to update the image it checks for the bootloader version, that may not work.
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
Yes sir, you were right!
[Google Pixel XL Guides, News, & Discussion] canemaxx:
So what would be the process to do that? Is this just flashing the bootloader or the who k factory image?
[Google Pixel XL Guides, News, & Discussion] mac796:
Fastboot flash bootloader_a bootloader 8996-012511-1611190200.img

That may be wrong bootloader but you get the idea
[Google Pixel XL Guides, News, & Discussion] canemaxx:
Funny you say slot a ... As I installed the new factory image it's only flashing to slot b and it end with remote: partition table doesn't exist
[Google Pixel XL Guides, News, & Discussion] mac796:
I usually flashall to whatever slot im on then change slots with fastboot, then you need to reboot to bootloader for it to change officially. Then flashall other slot. Then you can go into last months image open command, and flash old bootloader

I actually do it individually now but this is easiest way
[Google Pixel XL Guides, News, & Discussion] canemaxx:
I just need to find that guide again to flashing slots ....once I find something it seems virtually impossible to find it again lol
[Google Pixel XL Guides, News, & Discussion] vaerio81:
This phone is Google's flagship and it's not meant for it to be rooted or modify. Google made this device so it's good to go right out of the box , but I do understand your frustration but to be honest this device is good without root a lot of people use it that way . The rooting world it's just a few of us so they pretty much focus on the regular consumer.
[Google Pixel XL Guides, News, & Discussion] gubacsek:
Well, you are right, the experience is almost perfect, but there are 2 points:

1. It is my device, and I want to do with it what ever I want. I want to be an administrator on my own device. Set/install/remove what ever I want, even if it is a bad thing...

2. I need root for restoring backups (yes google, pointing at you, because YOUR backup doesn't work on my device...) and for installing ARISE sound mod. Can't live without that anymore.

Actually these are the only 2 reasons left. I'm not even installing a custom kernel anymore, because stock became good enough for me. But I want to be able to do so IF i want to :D

Why isn't there a huge red switch somewhere hidden in development settings, which you need to press 100 times, then sign 200 times that you take over full responsibility, and then get root by activating it? why oh why? :D
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Way too soon to panic. We don't know what they did to cause this to happen, let alone why. Their spokesman is quoted saying it would be rootable and unlockable just prior to launch. Google is usually good on their word.
[Google Pixel XL Guides, News, & Discussion] Scott:
This

|

|

\/

Im sure [MENTION=631273]Chainfire[/MENTION] and [MENTION=702506]dees[/MENTION]troy will be able to resolve. Probably just some stupid minor issue.

Im not at all worried. Plus flashing the bootloader from prior build seems to resolve it for everyone (not that I ever advocate running mismatched firmware unless completely needed).
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Me too, not worried at all. This update is still less than 24 hours old. The way this phone combines kernel, ram disk and all that is going to make it more interesting.
[Google Pixel XL Guides, News, & Discussion] dowlf:
I didn't make any mods, but I just downloaded n2g47o again and the file size is different than the first one. Must have gotten screwed up somehow. I will try again with the fresh download.
[Google Pixel XL Guides, News, & Discussion] Golf c:
I'm curious if this has something to do with it.

https://plus.google.com/+DeesTroy/posts/ASNYUijFhaJ

Or maybe just a bootloader issue?
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
I think it's this htc bootloader patch.

https://source.android.com/security/bulletin/2017-05-01#eop-in-htc-bootloader
[Google Pixel XL Guides, News, & Discussion] echardcore:
Just unboxed her last night. Dir from Google. Need root to survive...

Unlocked and flashed 7.1.2 (N2G47E, Apr 2017) then and still no go. That should have worked, no? I booted "Ramdisk-Recovery.img" from "twrp-pixel-installer-marlin-3.1.0-0RC2". Is this the right version?
[Google Pixel XL Guides, News, & Discussion] gubacsek:
I'm not sure... the developer preview is out since almost two months, and the same (?) issue is still not solved. The phone is out since half a year, and there is no stable, working TWRP for it. And most probably not because Deestroy is lazy, or does not want to do it. In my opinion it is because it is hard to solve. Or not possible ? :P

Anyway, I would offer my help, but I didn't manage to get the sources yet... I see that all roads lead to one post in the TWRP thread, describing how to compile TWRP, but it is a bit too generic for me :D I have to work on it to even be able to compile the current version. Not to mention finding out what the problem is...
[Google Pixel XL Guides, News, & Discussion] milan187:
This is not developer device like Nexus don't forget that.

I've been using TWRP and custom ROMs since November. No problems. Just do your reading.

Also even Nexus updates used to break root and stuff. Nothing new.

Multiple slots make device a little more complicated for flashing but it has a purpose. Faster updates.

It's really not that bad.

For TWRP if you want to use backup and restore use RC1 not RC2. Otherwise RC2 is good. We had TWRP working since October.
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Looks like we are going to be ok. Chainfire has it figured out and Franco is also on it. They are just going to have to self sign the image. Chainfire has SU working in his tests but it needs some more work.

https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[Google Pixel XL Guides, News, & Discussion] gubacsek:
I was also using TWRP since january, but it could only restore from system image, and last time i tried to restore data, my whole device got wiped :D It's a good thing that I'm cautious and I backed up everything before that. I had a lot of troubles restoring only the vendor partition, the decryption after booting into TWRP sometimes works, sometimes not :D So I wouldn't call it a "working" TWRP. There are too many unknown variables :D

And again: I'm not talking against the devs in this community, it is not their fault (I am very very thankful for their hard work!). I'm asking why don't we have a normal working recovery from google ? Why don't we have a built in possibility to use root on our devices?

Why isn't the pixel a developer phone ? What is the developer phone if not the pixel? Nexus? for which the support will end this year? What will be after that ?

eh... I'm a bit disappointed that's all.. Sorry for being so negative :D I'm coming from the 6P (which died with the bootloop, so i was very very upset and disappointed already when I bought the pixel - which is a wonderful phone, best I ever had by the way - ), so I'm used to the freedom, and full access to my phone, and I can't stand that there is a dead end with the developer preview, and the latest "prod" android version also.... I know you can get around it by installing previous bootloaders, but that is not the way it should be... I hope google will come up with something, because as I see, we are loosing the best part of owning an android phone: the freedom to do what ever you want with your own device.

---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------

great news! :D

I'll stop crying soon (if TWRP will also works)...
[Google Pixel XL Guides, News, & Discussion] milan187:
Changes happen, we will have our root back within a couple of days I'm sure.
[Google Pixel XL Guides, News, & Discussion] replica9000:
I also bought my PXL straight from Google. Unlocked it. Updated to the N2G47E firmware. I then booted the twrp-3.0.2-0-RC1-fastboot-marlin.img image, flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip file, and was good to go.

---------- Post added at 02:58 PM ---------- Previous post was at 02:48 PM ----------

Just a thought, but SuperSu modifies the kernel so dm-verity won't bootloop the device, right? So what if a custom kernel, or maybe the previous update's kernel that SuperSu is known to successfully modify, was flashed?

I know unlike traditional Linux, Android kernels are pretty specific to firmware releases, but could be worth a shot.
[Google Pixel XL Guides, News, & Discussion] phamine:
Just did it. Stuck in bootloop.

Don't flash with flashfire!!!
[Google Pixel XL Guides, News, & Discussion] echardcore:
Been using this phone without root. Missing my Tasker stuff but I wanted to see how it felt and I got about 5+ hrs of SOT with heavy browsing and casting. I think I'll just wait until the issue is fixed.
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
I'll wait as well but not without root (I would root if only for Adaway). I don't see the point in doing an update that is simply a security update and then reverting to a previous supposedly insecure (and mismatched) bootloader. I will just stay on the full April install and not upgrade just for the sake of upgrade.
[Google Pixel XL Guides, News, & Discussion] savi0:
Sorry if this is a stupid question, but if the bootloader is unlocked, isn't it already insecure? Would there be a difference being on the April vs May bootloader, security-wise, if the bootloader is already unlocked.
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
This would appear to be true, but they just rolled out a new bootloader that while not relocking the bootloader still blocks some amount of exploit (or at least attempts to by way of the signature requirement). My guess is that they will play cat and mouse again with the signature changes once CF has finished that hack.
[Google Pixel XL Guides, News, & Discussion] savi0:
I see. Thanks for the clarification.
[Google Pixel XL Guides, News, & Discussion] jova33:
Why is this? I just got the phone 3 days ago.
[Google Pixel XL Guides, News, & Discussion] FernBch:
If I understand what I have read correctly you need to install the May update package then fastboot flash April's bootloader and you can install TWRP & SU again no problem.
[Google Pixel XL Guides, News, & Discussion] 21cdb:
I went back to stock from Resurrection Remix and flashed the April stock image. I totally forgot to quickly turn off updates, so it installed the May update before I could even see what was going on. I did flash the April bootloader and could install TWRP and SuperSU fine after that. Just another data point for those who are wondering. I haven't seen any issues yet running with a mismatched bootloader.
[Google Pixel XL Guides, News, & Discussion] DirtydAmbrose:
Are these the complete updates for may ? I thought I read somewhere that there is more coming for may possibly on the 5th ?
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
Yes.
[Google Pixel XL Guides, News, & Discussion] sb1893:
That didn't take long. Chainfire has solved the issue introduced with the May bootloader which now checks for properly signed boot images. Details at the link here:

https://xdaforums.com/showpost.php?p=72175816&postcount=14

Worked perfectly for me as follows:

1) Coming from April 2017 update, I sideloaded NHG47L.

2) Reboot

3) Fastboot Boot TWRP-RC1

4) In TWRP, Flash SuperSU-2.79-SR3

5) Still in TWRP, Flash VerifiedBootSigner.zip from above link

6) Reboot

All looks good.

Thanks again, Chainfire! Really appreciate all that you do for the community!
[Google Pixel XL Guides, News, & Discussion] RobAtSGH:
One gotcha: depending on if you took the update and had it bootloop/crash back to the second slot, you might have to do some additional mojo in TWRP. Just flashing to the default slot in TWRP didn't fly for me. I had to switch boot-slots from the current, and flash the ZIP files to both slots before I got root back.

How I did it:

adb reboot bootloader

note the current active boot-slot ("A" in my case)

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

Input PIN to decrypt

Select REBOOT at TWRP main screen

Select SLOT B

Back to TWRP home, then INSTALL

Flash SuperSU zip

Flash VerifiedBootSigner.zip

Go back to TWRP home

Select REBOOT and SLOT A

Flash both ZIPs again.

Reboot
[Google Pixel XL Guides, News, & Discussion] Tb0n3:
What about us plebs without twrp? I didn't want to go that route and have been flashing with fastboot. Is there a way to "fastboot boot" SuperSU yet? Or is it fine to use TWRP recovery now?
[Google Pixel XL Guides, News, & Discussion] john7760:
Does the file have to be sideloaded? Or can I flash the OTA in the TWRP, flash TWRP, Flash SR3 then the Bootsigner.zip?
[Google Pixel XL Guides, News, & Discussion] sb1893:
Just for clarification. Other than the very first root of the Pixel in late 2016 where "boot-to-root" was used, I have been "fastboot boot"ing TWRP. This only boots to TWRP recovery and allows you to flash and otherwise leverage its capabilities. (TWRP doesn't persist on your device using this method.) This has been the recommended approach for obtaining root for quite some time. I still have stock recovery and have never installed/flashed TWRP as my recovery. Only boot it to flash SuperSU (and now the verifiedbootsigner.zip).

Good luck!

---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------

Sorry - I do not know. I have only been sideloading OTAs since the very first update came out for the Pixel/XL. What you describe could very well work - but I have no firsthand experience with it. Having said that, the sideload process is pretty straightforward.

thanks.

S
[Google Pixel XL Guides, News, & Discussion] Tb0n3:
I hadn't seen the thread.
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
Just did this on a BL unlocked Verizon XL. Did the sideload in TWRP RC2 coming from K and going to L. Did the temp img and then the RC2 full install/SU/signer. All is working well. Time to do the wife's non-XL... and that worked as well.

P.S. The new April platform tools (adb/fastboot only) are working since Google fixed the large file sideload issue.
[Google Pixel XL Guides, News, & Discussion] gordonlw:
Worked perfect!
[Google Pixel XL Guides, News, & Discussion] canemaxx:
So I could flash the may image, reboot to bootloader, fastboot boot RC1, install twrp installer , flash su zip, flash verifiedbootsigner.zip......and I should be good yes?
[Google Pixel XL Guides, News, & Discussion] john7760:
The only way to update is like it was mentioned and sideload the OTA, When I tried flashing only with the other files it just boot loops and reverts back to April update no change.
[Google Pixel XL Guides, News, & Discussion] prot-:
How do we install TWRP though?

I tried both before and after your step 4 and it results in bootloop.

flashing boot.img fixes it though so i just did you method, but no TWRP installed
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
Flash TWRP before step 4 but do not reboot into it or alternatively flash verified boot signer right after flashing TWRP and before rebooting to recovery.
[Google Pixel XL Guides, News, & Discussion] canemaxx:
Step 2 I assume is rebooting to bootloader?
[Google Pixel XL Guides, News, & Discussion] echardcore:
I am slightly unsure when to flash TWRP as well. I am rooted without TWRP right now.

1) Latest build will work now...

2) ADB reboot bootloader

3) Fastboot Boot TWRP-RC1

4) In TWRP, Flash SuperSU-2.79-SR3

5) Still in TWRP, Flash VerifiedBootSigner.zip from above link

6) Reboot

7) ADB reboot bootloader

8) Fastboot Boot TWRP-RC1

9) Fastboot flash TWRP ?
[Google Pixel XL Guides, News, & Discussion] epsix:
Whoew.....Im still on November update, was about to update to May. Bit seeing all these bootloop, I'm scared to update. I need root, can't live without it. Maybe theirs a better way to update in near future? I'm lost!!!!
[Google Pixel XL Guides, News, & Discussion] altwu:
i'm on a verizon pixel xl with the bootloader unlocked. i was previously running the april update, nhg47k, with twrp 3.0.2.0 rc1 and supersu 2.79-sr3. i just flashed the may update, nhg47l, and was able to install twrp and supersu again with no bootloops. here's the process i followed.

flash the latest update, either the full factory image or the ota. i prefer to flash the full factory image.

fastboot boot the twrp rc1 image.

install the twrp zip. i prefer the rc1 zip because i'm not running magisk and others have reported issues with restoring backups with rc2.

install [MENTION=631273]Chainfire[/MENTION]'s VerifiedBootSigner zip.

reboot to recovery.

install the supersu 2.79-sr3 zip.

install [MENTION=631273]Chainfire[/MENTION]'s VerifiedBootSigner zip again.

reboot.

if you don't want twrp installed, then i think you can skip steps 3-5.
[Google Pixel XL Guides, News, & Discussion] frank_datank:
This worked perfectly for me, coming from March update. I flashed full n2g47o image (sans -w) and no problems.

A tip for those who are far from regular flashers or TWRP-ers (like me), don't forget to put the SuperSU & VerifiedBootSigner zips onto your phone before starting the above process.

---------- Post added at 09:15 AM ---------- Previous post was at 09:11 AM ----------

Super easy man, just 1 extra step - flash Chainfire's zip after updating, and you're golden. Follow the steps above and you'll be good. Worst case, you flash the April update, and you're still improving by a few month's patches.
[Google Pixel XL Guides, News, & Discussion] 335Deezl:
Worked for me!View attachment 4145397View attachment 4145401View attachment 4145402
[Google Pixel XL Guides, News, & Discussion] yearn2burn:
Anyone here used Magisk for root rather than SuperSU?
[Google Pixel XL Guides, News, & Discussion] liam_davenport:
I was using it till I noticed I/O governors were disappearing back on SuperSU now
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
VerifiedBootSigner v6
[Google Pixel XL Guides, News, & Discussion] canemaxx:
I just randomly lost root when updating SuperSU has anyone else experienced this
[Google Pixel XL Guides, News, & Discussion] liam_davenport:
Use 2.82 from HERE
[Google Pixel XL Guides, News, & Discussion] canemaxx:
I'm sorry it's been a while so now that I don't have root, I would have to fastboot flash the zip file right?
[Google Pixel XL Guides, News, & Discussion] liam_davenport:
No just flash in twrp if on May bootloader you will need to flash the VerifiedBootSigner-v7.zip after anything that modifies boot img
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Boot to TWRP and use TWRP to install the zip.
[Google Pixel XL Guides, News, & Discussion] canemaxx:
Thanks ...all is well again
[Google Pixel XL Guides, News, & Discussion] echardcore:
I'm going to flash the latest factory image. Is this process still the same?
[Samsung Gear S3] YMark:
Is there a web site that lists or shows all the Gear S3 Frontier watch faces and apps? Before I purchase, I would like to verify a couple of things. Sorry for the NEWB questions, but not a lot of online info for the G3.

- Looking for a digital watch face that has a shortcut to a TIMER app, preferably more than one.

- Is it possible to download a watchface and modify the widget on the face to open a "timer" application?

I referee high school football and need to time the play clock/timeouts/etc. Ideally, this would be some shorcuts on a watch face.

Thanks﻿
[Samsung Gear S3] Landshark928:
You can make your own (or use others) with the Watchmaker app, however i'm finding that the steps, compass, and hr monitor dont seem to work on my S3.