yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] akenis:
https://developers.google.com/android/images

Not sure what the difference in the two images are, but I would think that at least some features might work better on non Fi/Canada version of Sep update.

What is it about the Verizon pixels that make the bootloader locked? Could having a Verizon Simm (or service...does Verizon have Simms) end up permanently locking your bootloader?

My T-Mobile Simm was out of my phone for the Sep update, and I ended up on Fi version? I did a flash-all to the non-Fi/Canada images.
[Google Pixel XL Guides, News, & Discussion] smallsmx301:
Any idea which one is the Tmo version? I used fastboot to flash the non fi/Canada build and now I have the radio I was on last month when I manually upgraded to the wrong August O release.
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
Updated the OP with October build numbers.
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
Manual update check under Settings / System / System updates now bypasses the staged rollout and always offers available OTAs if the latest Google Play services are installed.
[Google Pixel XL Guides, News, & Discussion] gm007:
Just got it via ota
[Google Pixel XL Guides, News, & Discussion] ithehappy:
Sideloaded full OTA. Rooted with SR5 via TWRP updated version. All's good. On first boot WiFi was lost but a reboot fixed it.
[Google Pixel XL Guides, News, & Discussion] Akira Takamedo:
I thought if you had the latest Play Services it'll push the OTA when you press Check For Updates. I've been doing it for half an hour, no update. Ever since I ported this line from Verizon to T-Mobile I've had to sideload everything including Oreo, I don't understand what I'm doing wrong.
[Google Pixel XL Guides, News, & Discussion] lucky_strike33:
When doing ota, did you lose data?
[Google Pixel XL Guides, News, & Discussion] lucky_strike33:
I got the update but got this error hmmm, I'm on verizon
[Google Pixel XL Guides, News, & Discussion] smallsmx301:
What's the latest Google services?

---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------

So I have the latest play services and still no dice. And by the way the Fi Canada builds are also for TMO and Sprint
[Google Pixel XL Guides, News, & Discussion] michaelbsheldon:
Yes, Verizon uses sims.

The simple act of booting up in the Verizon network with a VZN sim locks the bootloader.

They HATE unlocked bootloaders. Has cost them too much warranty dollars.
[Google Pixel XL Guides, News, & Discussion] gm007:
11.5.17
[Google Pixel XL Guides, News, & Discussion] smallsmx301:
Thanks! That's what I got! Oh well. My wife isn't getting it on her regular pixel either
[Google Pixel XL Guides, News, & Discussion] Akira Takamedo:
Anyone have an idea why the OTA still isn't coming up for me? Latest Play Services, and ever since changing networks I haven't gotten the last few OTAs either. I had to sideload Oreo.
[Google Pixel XL Guides, News, & Discussion] ithehappy:
No absolutely not, that's why OTA man. No method of OTA wipes data as far as I know.
[Google Pixel XL Guides, News, & Discussion] Sab3elbromba:
After reading this: https://9to5google.com/2017/09/22/google-android-ota-check-for-update/ I assumed that when I pressed the check for update button I would then receive the latest update in this case being the october security update, but when I pressed the button I got nothing!
[Google Pixel XL Guides, News, & Discussion] gm007:
In security and location settings there is security update click on it maybe it will make any difference.

That's where i got the update from.
[Google Pixel XL Guides, News, & Discussion] biggiestuff:
Unfortunately that didn't work for me :(
[Google Pixel XL Guides, News, & Discussion] brangalm:
Can someone help me please?

Pixel XL, coming from Sept 8.0, had the newest TWRP and SuperSU installed.

Downloaded the full images of the Oct 8.0 from the Android website. Used the flash-all but removed -w so that I could keep my data.

I keep getting this stupid message and I can't boot. Hit the 'try again' multiple times. Tried re-flashing, tried the Fi and the non-Fi versions, and tried re-flashing the Sept version again, but keep getting this message, argh!

Any suggestions? I would really prefer not to wipe data (hence why I removed the -w in the first place!).

Thanks!

Edit: nevermind, just wiped data and it's working. Not sure what happened exactly. Grr!
[Google Pixel XL Guides, News, & Discussion] gbeardmore:
I bought a Pixel XL thru Google directly. Are you saying when I inserted the Verizon SIM from my old Nexus 6P and booted, the Bootloader became PERMANENTLY locked?

:crying:
[Google Pixel XL Guides, News, & Discussion] lucky_strike33:
Hold down power for 10 seconds and it should reboot then press power and vol button down to go to the bootloader. Try to run the flash all bat again.

Next time when you just want to update to new firmware, while having TWRP installed. Just flash the ota file. YOu can download the OTA file to your phone and flash it through twrp.
[Google Pixel XL Guides, News, & Discussion] michaelbsheldon:
If you do not unlock that bootloader first while on Wi-Fi, yes when you put the Sim in it won't be unlockable anymore. That's my experience.
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
No, it doesn't work off the SIM. They phone home to Google and get permission to unlock. Matters not what SIM is in it. We have seen lots of cases where Google has the phone tagged incorrectly. Sometimes what happens to you, and the converse..a VZ phone will unlock.

Call Google, get another phone.
[Google Pixel XL Guides, News, & Discussion] gbeardmore:
Thank you TonikJDK! I haven't unlocked yet, I'm still reading (and reading, and reading, and READING) before I attempt to root.

There's so much conflicting info out there and I don't want to bork the phone. I don't have a lot of time available to spend "fixing" it if things go badly, so I'm going to wait until my comfort level improves.

I was really bumming for a minute there though! Thanks again! :)
[Google Pixel XL Guides, News, & Discussion] patroll:
I have the Pixel XL international version (2200), which Oreo 8 version I should install?

Edit. Flashed the newest factory OPR3 and seems to be working ok. Magisk also working.
[Google Pixel XL Guides, News, & Discussion] brangalm:
Thanks, I actually tried the flash all again several times to no avail unfortunately.

Thanks for the tip about the OTA. Will do that next time.
[Google Pixel XL Guides, News, & Discussion] Jestre:
clarification on 2017-Oct Pixel XL updates

Sorry to disappoint but some phones will not update, nor recognize there is one available even with all other "App" updates completed.

They are forced to wait in the queue. Mine is among them with no update as of 10am on the 4th. My daughters was also but she did get finally her update last night but my wife had it Monday.
[Google Pixel XL Guides, News, & Discussion] Lost497:
HI, Any Ideas? Im Lost
[Google Pixel XL Guides, News, & Discussion] Pain-N-Panic:
Based on the error message at the bottom of your command prompt, it looks like you don't have all the files required in the platform-tools folder.
[Google Pixel XL Guides, News, & Discussion] veskostoev:
Hi, i had same problem trying to flash stock oreo over 7.1.2 Pure nexus i fixed when i boot to twrp and switch to another slot.
[Google Pixel XL Guides, News, & Discussion] HikingMoose:
Google revoked the ability to use a custom ringtone? (.mp3 anyway, maybe I can convert it to .ogg).
[Google Pixel XL Guides, News, & Discussion] speedingcheetah:
nope....not for me. My custom ringtones stil work fine and are mp3.
[Google Pixel XL Guides, News, & Discussion] Born<ICs:
.

Using .mp3 ringtones and .ogg notifications ok.

I did however paste mp3 files directly into Ringtones folder .
[Google Pixel XL Guides, News, & Discussion] galaxys:
Another no issue with MP3 ringtones...
[Google Pixel XL Guides, News, & Discussion] HikingMoose:
I stand corrected. After putting my normal ringtones and notification tones on, I just had to reboot, then it allowed me to use them. Errored out every way that I tried to do it before the reboot.
[Google Pixel XL Guides, News, & Discussion] fiverings:
Usually, the flash-all will start downloading and it will get to part about archive can't find something sig. And another sig. And system.sig and it will look like it gets hung up at that point. You need to just wait and it will continue and finish. Yours says to exit. That's not right. Make sure you download the correct file and unzip in to a new folder. Make sure you have all the files and open a cmd or just double click the flash-all file and a cmd window should open and the install will start. Good Luck
[Google Pixel XL Guides, News, & Discussion] EmperorX:
So uh, my T-Mobile SIM Pixel XL just got the OTA and I am now on the Fi/Canada October build. Is this expected behavior? I saw another user mention this but they said their sim was out during the update, mine was definitely not out.

Thanks!
[Google Pixel XL Guides, News, & Discussion] specd_out:
Hey guys I got a question. I have a Verizon pixel xl and standard pixel both of them have bootloader unlocked, twrp rc1 recovery installed, su installed and are currently running 7.1.1. Id like to upgrade to 8.0 on both phones. From what I read I can just flash the correct version through twrp. This is where I start to get confused. At this point will my bootloader be locked again? Will it be basically a fully stock phone at that point? The process seems simple on non verizon phones but I am seeing very little about Verizons locked loader issue when flashing an update. Thanks in advance for any help
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
It won't relock. And if you edit the flashall bat file and remove the-w all your data will still be there.
[Google Pixel XL Guides, News, & Discussion] specd_out:
Will I have to reinstall twrp and SU?
[Google Pixel XL Guides, News, & Discussion] Ozark_8125:
What is the exact name of the zip you're trying to flash?
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Yes you will.
[Google Pixel XL Guides, News, & Discussion] specd_out:
I have seen people installing twrp using twrp, and other using adb. If you install it with twrp how does that work? I am assuming you flash the ota but do not boot, then install the twrp zip, then boot. Does that make sense
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
No idea, with recovery and boot part of the same partition I don't mess around trying to cut corners. I flashall with the -w removed.
[Google Pixel XL Guides, News, & Discussion] specd_out:
Yea I agree I get lost with the partition part as well. Honestly as long as my bootloader isnt locked I am fine. a recovery and root are just bonus imo
[Google Pixel XL Guides, News, & Discussion] specd_out:
hey guys Im gonna need help here. my phones seems to be stuck in a bootloop after I tried to install the new software. Is anyone online that can help me out please

***** I fixed it myself. I was able to get into the bootloader and reflash the file. It took the second time. The first time it said archive does not contain boot sig, recovery sig, system sig, vendor sig. Then it failed. The second time it said the same but the install continued. Now its working fine all my data is there, everything works fine, I am on 8.0.0 and I am still unlocked.
[Google Pixel XL Guides, News, & Discussion] akenis:
I wanted to see OTA actually work OTA.

Remove suhide.....OTA fail

Remove root from su...OTA fail

Flash boot to both slots...OTA fail

Flash system to both slots...OTA fail

Flash all..OTA fail

Flash all other slot...OTA fail

Switch slot in TWRP, reboot....

Your system has been updated. But like you on the wrong build. Went from 007 to Oct Find build.

Flash-all 008 finally. Wasted time.

Next step was to flash Magisk....boot loop?

Unmagisk zip....boot ok

Flash Magisk....boot loop

Will try flash all again from PC. Previously did it from Linux running in Chromebook Crouton.
[Google Pixel XL Guides, News, & Discussion] altwu:
has anyone flashed the latest security update for verizon (OPR3.170623.008)? any issues with the modded twrp or supersu?
[Google Pixel XL Guides, News, & Discussion] galza:
if im on 8 rooted and want to install full oct image without erasing data how to do that? fastboot flash flash-all -w? right?
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
No, you edit flash-all.bat with notepad and remove the -w inside and save it.

Then from a command prompt you just run flash-all.bat
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
OP updated with November builds.
[Google Pixel XL Guides, News, & Discussion] prot-:
Root working ?
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
Everything is fine including SuperSU, TWRP and suhide. Installed on a Pixel and a Pixel XL. 8.1 will be more telling given the TWRP issues in the preview.
[Google Pixel XL Guides, News, & Discussion] wazza1991:
Why doesn't the 'check for update' button work?
[Google Pixel XL Guides, News, & Discussion] snapilica2003:
Boy, I really hope this update fixes the "Mobile data has run out" bug. It's been driving me crazy!
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
Do you mean after update or are you looking for the update to show as available. After I had updated, the check button is working fine and showing the new patch level. I have noticed in the past that if you run check for updates immediately after the install it will hang until you do one more reboot and then it works. I have just got used to rebooting once after the upgrade reboots itself.
[Google Pixel XL Guides, News, & Discussion] wazza1991:
No. What I mean is that when I hit the 'check for update' button, it searches for an update but the 'last successful check for update' shows the old time. So it's actually not successfully checking for an update.
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
I understand what you are doing but am still wondering if you mean after doing a manual update or not. Assuming not, I have seen it do what you are saying for as long as the Google update server is down (hours is the most I have sen) but eventually returns. Either way, I assume you have rebooted...
[Google Pixel XL Guides, News, & Discussion] wazza1991:
Thank you! It was before the update. I have not received the November update yet so I was trying to manually search for it.
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
The OTA for sideload and the factory image (if your bootloader is unlocked) are both available on the Google site. No need to wait for the OTA to be pushed.

https://developers.google.com/android/ota
[Google Pixel XL Guides, News, & Discussion] sb1893:
I just updated to the November 2017 security update. Went pretty much as expected but I did run into a slight issue that I thought I'd share in case anyone else encountered the same thing...I'm running a Google Store Pixel XL, Verizon network - Grandfathered UDP, unlocked, stock, rooted with SuperSU 2.82-SR5 and suhide-lite-v.109. SafetyNet passing / AP working, tethering working via build.prop mod.

My typical process is below with the slight glitch I encountered, along with the extra step I had to perform to get past it in red.

1) Sideload OTA

2) Reboot into android, verify new version, security patch level.

3) Fastboot Boot TWRP-3.1.1.1

4) Flash SuperSU-2.82-SR5

5) Reboot into Android, Verify root is working.

6) Fastboot Boot TWRP-3.1.1.1 (to install suhide-lite1.09). This time fastboot boot TWRP-3.1.1.1 failed with Too Many Links error.

6a) Install latest platform-tools (I had been running version I installed at end of August 2017, noticed there was a newer version from October 2017. Unclear why the older fastboot worked to boot TWRP after the first

reboot on the latest November patch, but then failed after SuperSU-2.82-SR5 was installed. Fastboot boot TWRP now works with latest fastboot version.

7) Install suhide-lite-v.109 from within TWRP.

8) Reboot into android.

9) Verify SafetyNet passes, Android Pay works

9) Edit build.prop to insert net.tethering.noprovisioning=true

10) Reboot. Verify tethering works.

Fin.
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
Updated the OP with a note about KRACK vulnerability not having been patched in November updates.
[Google Pixel XL Guides, News, & Discussion] thearch1tect:
A noob question but it seems like we can update without issue if we're stock rooted and no need to unroot first, is that correct?I'm currently using the google version on TMobile unlocked w. SU v.2.82-SR3 and September build OPR3. Can I just take the download OTA or do I need to sideload it? Thanks for the assistance!
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
A standard download will fail because you are rooted. So you sideload it and reroot. No, you do not need to unroot first. If you unroot and then try a regular download it will most probably fail any way because boot and recovery are still modified.

Or you can flash the full image after editing the flash all bat file and removing the -w so you don't wipe data. Then reroot. That is how I do it. Feels cleaner to me.

I have not tried it but many report that flashfire will sideload the OTA and save root.
[Google Pixel XL Guides, News, & Discussion] vlucchetti:
Which OTA file did you DL? A full version or just the updates themselves?
[Google Pixel XL Guides, News, & Discussion] sb1893:
The only OTA file version I am aware of...hosted on Google's support site...snip attached...

that is what I sideloaded.
[Google Pixel XL Guides, News, & Discussion] vlucchetti:
Thanks, wasn't sure to do the full ota or the binaries.
[Google Pixel XL Guides, News, & Discussion] r1nstang:
need a little advice. Im used to the whole flash-all.bat file for the OTA but it seems the October and the November updates do not have the typical files within it. instead it has a meta-inf folder, compatibility.zipm, care-mpa, payload.bin files.

what do i do with those?? and how do i avoid losing all my data and photos o the phone with these new files

im rooted with unlocked bootloader so i cant download thru the system update

thanks
[Google Pixel XL Guides, News, & Discussion] ithehappy:
Full firmware images will always have a flash-all.bat file, I think you're looking at the OTA packages, which never had that.

Just download the latest full OTA and sideload through ADB, simple. Data kept and you're updated still.
[Google Pixel XL Guides, News, & Discussion] r1nstang:
still having problems with this. updated everything on android sdk, adb. and still get this error when trying to sideload the ota.zip opening 'pixelota.zip'...

connecting...

falling back to older sideload method...

terminate called after throwing an instance of 'std::bad_alloc'

what(): std::bad_alloc

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information

i am stock rom, rooted, unlocked bootloader with the flashable TWRP. if i go into android recovery i just get the red ! android guy and pushing the buttons does not bring up any kind of menu. do i need to flash stock recovery again?
[Google Pixel XL Guides, News, & Discussion] altwu:
have you tried flashing the full factory image instead of the ota? the links for both the full factory images and the otas are in the op. i've never tried the ota sideload method. i've always flashed the full factory image for every update, after removing the -w option from the fastboot command in flash-all.bat in order to prevent a data wipe. i haven't had any problems.

i just flashed the november update for verizon, opr3.1706230.13 and i still have the notification to download and install an update. shouldn't this go away since i'm on the latest update? or is there an ever newer update?
[Google Pixel XL Guides, News, & Discussion] altwu:
never mind. the notification went away. i guess it took a while for the rom to check and realize that it was up to date.
[Google Pixel XL Guides, News, & Discussion] GrahamCracker0:
https://www.dropbox.com/s/vmq23g8by3f2m9c/Screenshot_20171130-221444.png?dl=0

So, I finally flashed the November update. Also got it re-rooted and hidden but I'm still getting the "Update Available" notification. Anyone else getting this still? I checked the Verizon site and it doesn't show any new updates yet.
[Google Pixel XL Guides, News, & Discussion] xdatastic:
I wonder what update it is trying to give you. Send yourself a Bug Report and find the update URL (ends with .zip) and post it here.
[Google Pixel XL Guides, News, & Discussion] GrahamCracker0:
Got the bug report but wasn't sure where exactly that url would be located. Suddenly though the update notification stopped popping up but now it won't connect to wifi. Tried rebooting the phone and my modem. Wifi is working on my S5 just fine and the Pixel can see the networks but won't even try connecting when I click on one. Going to turn it off, let it sit and reboot the modem again for the hell of it.
[Google Pixel XL Guides, News, & Discussion] xdatastic:
The URL ends with ".zip" so just to a find\search for that.
[Google Pixel XL Guides, News, & Discussion] GrahamCracker0:
(/data/user_de/0/com.android.shell/files/bugreports/bugreport-marlin-OPR3.170623.013-2017-11-30-22-24-31.zip)

[194837035,0,0,https://ota.googlezip.net/packages/...e8171630a983111d9f8885135473daa30d247e67.zip]

Either of these look right? Wifi is still not connecting. Tried deleting and adding my SSID again but there was no improvement. Shows networks but won't connect. Then all of the networks go away, it searches and finds them again but still won't connect. I'll have to battle this in the morning.

Wifi Screen
[Google Pixel XL Guides, News, & Discussion] xdatastic:
Thanks, second URL is the OTA update. It was an incremental OTA for OPR3.170623.013 from OPR3.170623.008.

ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR3.170623.013/4397526:user/release-keys
post-build-incremental=4397526
post-timestamp=1508181255
pre-build=google/marlin/marlin:8.0.0/OPR3.170623.008/4294783:user/release-keys
pre-build-incremental=4294783
pre-device=marlin
[Google Pixel XL Guides, News, & Discussion] GrahamCracker0:
Well, I'm stumped. After updating my phone it refuses to even attempt to log on to my WiFi. Won't even get as far as to verify the password.

So far I've tried:

Kicking everything else off of the network.

Changing the SSID.

Changing the password.

Creating a second SSID.

Rebooting both the DSL Modem and my phone multiple times.

Forgetting and then adding the SSID back in.

Booting into Safe Mode on my Pixel.

Nothing is having any effect. I was able to connect to WiFi at both of my jobs today just fine. No issues what so ever. My Pixel just seems to suddenly hate my home for some reason after flashing the update. Does ANYONE have any idea as to what might have happened and how to fix it?
[Google Pixel XL Guides, News, & Discussion] xdatastic:
Take a bug report and have a look at the logs. Or adb logcat. I wonder if your device has blacklisted that particular wifi network for some reason.

You can also enable wifi verbose logging in Developer Options which might, but might not show a reason for failure in the wifi settings screen.

Otherwise try a reset of the networking.
[Google Pixel XL Guides, News, & Discussion] Kisakuku:
December 8.1 images are up.
[Google Pixel XL Guides, News, & Discussion] sb1893:
Can anyone confirm that the prior combination of SuperSu 2.82 SR5 and suhide-lite-v09 will continue to work on 8.1 as they have on 8.0 (Nov Sec Patch) to provide root, and root-hiding capabilities and continue to pass SafetyNet? From reading the 8.1 Dev Preview threads it seems like majisk is getting more adoption. My preference would be to stay on SuperSu/suhide if possible....any feedback would be appreciated.

Thanks,

S
[Google Pixel XL Guides, News, & Discussion] xdatastic:
Urgh. The ro.build.date and ro.build.version.incremental are prior to the Beta 2 build so the OTA probably won't work.

The final build is 2 days prior to Beta 2.