yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] foobar66:
Grr ... I'm stuck (I think) ... I was rooted:

- removed all magisk modules

- removed magisk

- changed the flash-all.sh script with:

fastboot --disable-verity --disable-verification update image-raven-sq1d.220105.007.zip --skip-reboot

- bootloader flashed OK

- radio flashed OK

- update step started executing, after a while it rebooted into fastbootd, so far:

--------------------------------------------
Bootloader Version...: slider-1.0-8013568
Baseband Version.....: g5123b-93368-211225-B-8029609
Serial Number........: 19251FDEE006LW
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.005s]
extracting boot.img (64 MB) to disk... took 0.179s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.014s]
Writing 'boot_b' OKAY [ 0.254s]
extracting dtbo.img (16 MB) to disk... took 0.027s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.461s]
Writing 'dtbo_b' OKAY [ 0.060s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.206s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.851s]
Writing 'vendor_boot_b' OKAY [ 0.222s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.003s]
Updating super partition OKAY [ 0.014s]
Resizing 'product_b' OKAY [ 0.012s]
Resizing 'system_b' OKAY [ 0.012s]
Resizing 'system_ext_b' OKAY [ 0.013s]
Resizing 'system_a' OKAY [ 0.019s]
Resizing 'vendor_b' OKAY [ 0.007s]
Resizing 'vendor_dlkm_b' OKAY [ 0.010s]
Resizing 'vendor_a' OKAY [ 0.009s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2659 MB) to disk... took 8.943s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/11 (262140 KB)

And now it looks like it is stick on this last step ...

This process worked fine for me last time (December full image).

Any idea what to do next? I don't dare to reboot ...
[Google Pixel 6 Pro] vlubosh:
Try to update platform tools
[Google Pixel 6 Pro] foobar66:
Thanks for the hint. I'm on linux. Platform tools are up-to-date (I checked upfront).

BUT BUT BUT ... I found the problem.

I was using USB-C to USB-C original cable !!!

Update got stuck as per my previous post.

I only very recently (2 or 3 days) started using that cable to charge my phone on PC.

I am now retrying with a USB-A to USB-C cable (a cable from OnePlus).

This is a cable which I have used since day 1.

I have now re-done the update with this cable and it was proceeded until the end !

Very very weird, as I would expect that the original Pixel cable is fine. Maybe it has got to do with the USB-C port on my PC (it's a linux PC which is ~6 years old) ... Anyway ... now going to try to boot ...

EDIT 1: phew ... I've been able to 'boot normally' (still without root) ... it has done 'completing system update' and 'play-systemupdate' (after entering my phone PIN) ... and I can see that I'm on SQ1D.220105.007!

EDIT 2: rebooted to bootloader, then booted OK with patched boot.img

EDIT 3: flashed patched (magisk) boot.img, rebooted phone ... and I've properly retained root.

Phew ... stressy start of a Saturday morning. All back to 'normal' now ;-)

EDIT 4: one thing I noticed: fabricated overlays do not seem to stick across reboots ... I recall reading something about this on twitter from https://twitter.com/MishaalRahman. Can't find the link to the exact tweet now but this was a loophole and one day Google was going to close it. So looks like Google already included this into this upgrade. The weird thing is that I have 2 fabricated overlays generated as root. Even these are removed upon a reboot. But I have a script in my personal magisk module that recreates them upon reboot (so 'solved' for me).
[Google Pixel 6 Pro] RetroTech07:
I know you've already fixed your problem, but all I did was download the OTA, rebooted into bootloader and applied the update via sideload. I didn't uninstall magisk or any modules and the update applied just fine.

I booted into Android, patched and flashed the new boot image and all is well. :)

Hopefully next time it's less of a process for you.
[Google Pixel 6 Pro] foobar66:
Yes, as mentioned in my previous post (https://xdaforums.com/t/january-update-has-dropped.4388425/post-86259799) ... it was the cable ... back up and running on January build & rooted (without wiping).
[Google Pixel 6 Pro] RetroTech07:
I know, and I saw, I'm just saying you didn't have to uninstall magisk for this. Just say thank you lol
[Google Pixel 6 Pro] lssong99:
Not sure why, after updated with the Jan factory image, my phone just wont boot. After reboot, it just enter a screen similiar to Bootloader but with the message of "Your device is corrupted." then if i push the power button, it will enter recovery, then reboot, stuck on "Google" screen.

The flash seemed smoothly since no error message on my PC cmd line.

I was still able to enter bootloader with PWR+Vol up, then after flashing again, same thing happens but after one time reboot, now the phone wont even turn on... (tried Power button, power+vol up, power+vol down, vol up=vol down, three keys together, all above for more than 30 sec...)

(battery was around 70% before flash.)

It seems my phone is hard bricked... Any suggestion?

P.S. My phone is unlocked with Canary Magisk root... I have been doing flash since OG Pixel so pretty much know my way around...

The -w option are removed from flash-all.bat,

I haven't have any chance to flash the Magisk boot.img since I always try to boot 1st time stock then flash modified boot.img...
[Google Pixel 6 Pro] roirraW "edor" ehT:
I think it was earlier in this thread, a Mac user with an Apple M1 processor had a similar problem with the OEM USB-C cable. In their case, they said it was a problem with the USB-C ports on their new Mac, and similar to you they were able to use their old Mac with USB-A ports just fine.

I believe Mac has some basis in Linux, but I don't really know how much, it's just interesting. Like Ash in Alien, I'm collating data.😂 Glad you got it solved.

Doesn't sound hard bricked in that state. You'll likely have to full wipe, though. Try Official Google Android Flash Tool. If that doesn't work, try Official Google Pixel Update and Software Repair. They've worked when others weren't able to fix their phones stuff the full firmware image.
[Google Pixel 6 Pro] lssong99:
Thanks for the suggestion for Official Google Repair site, I didn't know this site exists!

Just checked the site, however, since my P6P doesn't even enter Fastboot (with PWR+VolDn)... but the site need Fastboot to go ahead.....
[Google Pixel 6 Pro] Android-Desire:
First set of issues with the new update :

The simcard cant be detected in the first setup on fresh install(i went from ProtonAOSP to stock with Android Flash Tool website)

It asks for sim code but when i get to two step auchentication and the sms option, but the sms dont arrive, i have to skip my gmail login and go to settings and setup apn before i can recieve sms(worked fine on december update, as in i did not need to setup apn for my sms to arrive)

APN settings are removed from december update as in all for my carrier, i had to setup data and mms apn(The APN settings are there on october update and december update on fresh install)

Regarding my Android Auto Issues, i havent drived in my car yet so i dont know if the audio is still buggy(audio is fine from my Oneplus 8t using Android Auto and my GFs iPhone´s Apple Carplay, or just bluetooth music from parent´s in law´s S21 Ultra) and the issue is not there when using my wireless headset for music, so it should not be a problem with my phone but rather googles software/drivers/firmware.

The fingerprint seems to have the same ok speed in unlocking the phone.
[Google Pixel 6 Pro] Shipoftheline:
Not had enough time to see if its fixed the freezing issues but still no 5G on this while my other phones (same sim) do
[Google Pixel 6 Pro] spotmark:
Sorry, as others have mentioned, it took forever to install. It's build SQ1D.220105.007 on my Verizon version. Same as listed on the Google download page. I don't know if it will install any faster by sideloading it, but it's probably worth a try.
[Google Pixel 6 Pro] bobby janow:
Do we have a dedicated root / magisk thread? You know the... After I update will I have root still, does magisk still work, what's the best way, does SN pass? Please!
[Google Pixel 6 Pro] Android-Desire:
First one is today with January update and the second is from December update.

This is with all my apps logged into and device ready for my use, all apps closed with the close all in the recents before running the Geekbench.
[Google Pixel 6 Pro] wilpang:
I get similar scores.
[Google Pixel 6 Pro] RetroTech07:
This happened to me before for no apparent cause, and seemed to follow after a Play Store update or from modifying a UDID file. I had to do a full wipe in order to get my phone back.

Are you able to get into fastboot at all when your device boots / restarts? There's something you may be able to try if you can...

Yes, try these threads:

https://xdaforums.com/t/guide-root-pixel-6-pro-with-magisk.4356231/

https://xdaforums.com/t/method-to-u...thout-wiping-data-and-retaining-root.4356065/
[Google Pixel 6 Pro] eddiedimitris:
Hello today I received the 45mb update...

So now we have to wait for February or we will take another update on January?

thank you
[Google Pixel 6 Pro] RetroTech07:
That was the January update, merged with December. If you already had the December build before it was pulled, you received both Dec and Jan updates which was consolidated. That's why it was only 45mb.

Read the notes here:

Google Pixel Update - January 2022 - Google Pixel Community
[Google Pixel 6 Pro] lssong99:
no, can't get into fastboot... The phone doesn't power on with any key combinations and not accessable on PC....

Strange thing is i didn't do anything unusual... Been flashing for so many years never have a phone brick like this...
[Google Pixel 6 Pro] uicnren:
constantly disconnects/reconnects
[Google Pixel 6 Pro] bobby janow:
That's not good. Not even a boot loop just unresponsive entirely? When you plug it in does the battery icon show?
[Google Pixel 6 Pro] foobar66:
After 7 hrs on Jan update ... 'all good' for me so far (after the initial update whoes with my cable).

I don't notice any differences with the December upgrade (which has always been working fine for me).

Fingerprint seems a tiny little bit faster but just based on 'feeling'.

There's the fabricated overlays which don't stick any longer after reboot. But can work around that when rooted.

My APN settings were reverted to the network on which my MVNO operator is hosted, so had to change these again manually (not a big deal).

I have:

- security update: Jan 5, 2022

- play-systemupdate: Dec 1, 2021

And I noticed that the play store itself has upgraded to: 28.8.17-21

So far so good for me ...
[Google Pixel 6 Pro] Shipoftheline:
I'd agree with that HOWEVER that long long slow install is a big drain on the battery
[Google Pixel 6 Pro] Morgrain:
After having played around with the January patch (came from December Europe A4 firmware that was pulled), it seems that the FP scanner got even faster and more reliable, even though it's not stated in the patchnotes. Maybe it's just placebo.
[Google Pixel 6 Pro] lssong99:
It's very bad. The phone does not have any reaction no matter what... Plug in power, push combination of keys.... I think the only way is a warranty return...
[Google Pixel 6 Pro] Morgrain:
Did you follow the guide linked in the OP post?

Did you triple check the file that you downloaded? Checksum? Are you absolutely certain that the cable and USB port on your PC that you use, actually work with ADB (I have a similar problem, if I use certain ports, sideloads will never work properly, I get corruption problems - if I use a particular USB port, that in the past worked without trouble, it works without problem)?

Can you tell us exactly what you did and in which order? Step by step?

Maybe we can find the mistake together.
[Google Pixel 6 Pro] prohibido_por_la_ley:
I'm going to call user error on this one. My Pixel wasn't a laggy jittery mess even when I first got it in November. Now with the January update it's soaring.
[Google Pixel 6 Pro] NippleSauce:
This January build seems excellent thus far! I have manually updated to it as I'm on T-Mobile but have bought the phone from Google. If you purchased your phone from Google's website and live in the US with a GSM phone carrier, then this is the build for you (and this information was posted on Google's blog by their Community Manager). But also, if you were previously a Sprint customer, this build should also work for you as people whom were previously using that service now connect to the T-Mobile's GSM towers as well.

The one thing that I'm unsure about is whether or not the current January Radio image somehow works over both GSM and CDMA lol. Regardless, my mobile data connections are as good as they were with the November radio image =).
[Google Pixel 6 Pro] MArtyChubbs:
CDMA and GSM are related to 2G and 3G services.

From what I'm reading, most US carriers are shutting down or plan to shut down their GSM and CDMA networks by the end of this year.

I hope you're using 4G or even 5G with this phone. You'll get way better performance.
[Google Pixel 6 Pro] NippleSauce:
Ahh, then this answers the part that I was unsure of, haha. Thanks! So once that happens (if it hasn't already), then the global images should definitely work for all who bought their phones from Google's site. Perhaps Verizon will still have a different image though as they always have in the past, for whatever reason (presumably due to the 2G and 3G bands they use).

Also, yes, I'm using 4G and 5G. I'm traveling to an area where I should get 5G UC, and so I should be able to test my 5G speeds within the next few hours =)
[Google Pixel 6 Pro] lssong99:
I use the port and PC update several phones before.... The wire is also okay since I used it to transfer files just before update...

The procedure are followed closely since I do this almost every month, on 3 different pixel phones (P6P, P4XL, P4XL)....

I didn't check the hash of the file I downloaded from Google's factory image site (I have direct link to it, not via 3rd party web site), and since the file unzip correctly, so I don't think there are any integrity problem (also unzip the inner zip to get boot.img.)

But I think you do have a point, something must went wrong somewhere. I will re-download the file again tomorrow and make a comparison to see if anything missing ....

My P6P is pretty dead now... already contacted Google and let's see if I could get a warranty return....
[Google Pixel 6 Pro] MArtyChubbs:
This month it's a unified build for all carriers. So, you are good to go!

Have a great weekend and I hope you get killer 5g speeds today (y)
[Google Pixel 6 Pro] Vio281:
that might be your phone or router man, I have two pixel and none of them on any build does that.
[Google Pixel 6 Pro] cmh714:
Have you seen this, not sure if this is general or specific to VZ.... https://www.verizon.com/support/4g-sim-card-faqs/#compatible
[Google Pixel 6 Pro] dmarden:
Yay call screening! 🙌
[Google Pixel 6 Pro] roirraW "edor" ehT:
In the future, just click on the How To Guide filter at the top of every page of threads and it will show the relatively few How To ones
[Google Pixel 6 Pro] uicnren:
nope, its exclusive to the pixel, and is a known issue. several other wifi 6 devices in the household, including samsung z fold 3, none have any issue, just the pixel.
[Google Pixel 6 Pro] NippleSauce:
You seem to be correct! And ohhhh yeah. I just did a 5G speedtest and got great download speed on a 5G UC tower! It's faster than my WiFi at home on my gigabit network! I'll attach a screenshot!
[Google Pixel 6 Pro] foobar66:
One positive improvement in the January build is the scrolling behaviour, e.g. in Twitter. Much smoother.
[Google Pixel 6 Pro] NippleSauce:
Sorry for the double post. I'm terrible with the newer "multi-quote" feature here on XDA when I'm on my phone. The old setting used to be easier for me on mobile, haha.

Regardless, try turning off "Adaptive Connectivity" and then restarting your phone. See if that changes anything as doing this seemed to help me resolve a similar issue when I first got this phone.
[Google Pixel 6 Pro] uicnren:
I appreciate the suggestions, but have had that off for about a month now. Makes no difference.
[Google Pixel 6 Pro] whatsisnametake2:
usb direct dac access I regret to report isn't fixed. and another user said the ldac problem isn't fixed either. I'm new to pixel phones - what is google track record like when it comes to sorting this kind of thing out?
[Google Pixel 6 Pro] Mic Muted:
flashed the january build last night and after using it all day I'm extremely happy with it. Far smoother UI experience, Battry life has been excellent and thats just on first cycle, not had system UI force close yet when was happening 4 times a day on november, no problems with blutooth dropping to my jabra 75t's, blutooth earphone volume when listening to music is much better, gboard not having weird stutters when typing. Will see how this continues but so far after a days use I'm very happy.
[Google Pixel 6 Pro] whatsisnametake2:
for the record, no problem updating and keeping root here, using the download factory image and modify flash-all method. very quick too.
[Google Pixel 6 Pro] d.cortez:
happy to know things are positive for other users. however, no "january build" connectivity love for me...this, after a factory reset and then install using the full OTA image. cellular signal is a little better, but cellular data connections are not working. all i see is the "!". spent 1 hour with ATT, but no luck. put the sim in my S21U and calls and data works fine. *sigh*. i give up (P6P back to the drawer).
[Google Pixel 6 Pro] Batfink33:
Agree with this. Signal for me is no better and still getting overheating on 5g, over 40degC doing basic tasks. Also still got bugs like the phone freezing and general stutter. Already done a reset so that's not the problem. Getting to the point of giving up on this phone.
[Google Pixel 6 Pro] RetroTech07:
By chance, what did AT&T have you do? Have you tried manually updating your APN settings? Sometimes these can be incorrect for your phone, so a manual update can sometimes fix spotty connections.

Give this a try - https://www.att.com/support/article/wireless/KM1062162/
[Google Pixel 6 Pro] d.cortez:
ATT rep reset my cell account, walked me through adding the APN as detailed in the link you posted, activated and use a new sim, and factory reset again. I placed the new sim in my S21U and cellular and data worked without issue. Never had these issues with other Pixel phones.
[Google Pixel 6 Pro] RetroTech07:
I find AT&T reps a 50/50 chance you'll get actual help. I remember calling and chatting with them online to get an eSim, and to this day I never received one lol.

Anyway, you can simply put in a new SIM that's activated by an agent and the phone should update itself with new carrier settings. All you'd have to do is just reboot the phone at that point for it to update, not a factory reset. I'm sorry you're going through this and hope it gets solved.
[Google Pixel 6 Pro] NippleSauce:
If I remember correctly, after a factory reset you can't use the OTA images (and if you do, it'll cause problems). You need the full factory image build (they're usually around 2.3GB). If you're doing it all manually, you would have to flash the bootloader image, then the radio image, then the update zip (whilst disabling verity and verification).

If you want root, you would then have to copy the new boot image out of the update zip and patch it with Magisk on your phone. Then, you would copy it back to your PC, go back into fastboot, and then flash the patched boot image.
[Google Pixel 6 Pro] RetroTech07:
I think the user is fully stock, so taking an OTA image is not going to cause any harm. If rooted, the OTA will fail which would then require it to be sideloaded via ADB. Disabling verity and verification isn't required on the latest Magisk Canary (if rooting) unless you're flashing certain custom kernerls or other files that would require it.
[Google Pixel 6 Pro] d.cortez:
i used the raven 12.0.0 SQ1D.220105.007, Jan 2022 (1.9GB) image from Google's Full OTA Images page.
[Google Pixel 6 Pro] dinosore1:
Battery seems to drain a lot faster since installing the update...
[Google Pixel 6 Pro] RetroTech07:
what evidence do you have that has drawn you to this conclusion? I'm currently charging my phone to see what battery is like. I wish we had the old 'battery usage' stats graph that would reset after each charge, and not just fluctuate through multiple charge cycles the way it does now. It was easier to see what was causing battery drain.
[Google Pixel 6 Pro] Lughnasadh:
Not for me. On stock kernel getting 5.67%/hr active drain and .74%/hr idle drain. Active drain will likely go up as I haven't done all the things I usually do since updating. Idle drain is the same as when I was on a custom kernel in December.
[Google Pixel 6 Pro] lawtq:
Totally agree! This new way is terrible. I don't bother look at stock battery now. Gsam thankfully still resets battery usage after unplugging charger
[Google Pixel 6 Pro] Alekos:
I think most of us want you to get it working (either by trying to fix it or warranty).

Can you go to the Flash Tool website, and hit the "pencil" and pick "Wipe device" and "flash all partitions" - this will obviously wipe your phone - and this will also reinstall all the firmware and partitions.

I think if this doesn't work, you should try for an advanced RMA. Mention to support you used this tool, and that should be enough to warrant an advanced RMA.

Its this page specifically:

Android Flash Tool

flash.android.com
[Google Pixel 6 Pro] dinosore1:
No evidence whatsoever, my statement was based off an observation, previously the phone would use less than 50% in a day from unplugging, yesterday it used 81% - with what I would say is my normal usage, will see what today brings.
[Google Pixel 6 Pro] d.cortez:
Appreciate your suggestion; however, I'm done with my P6P, and I've decided to stick with my S21U.
[Google Pixel 6 Pro] Lycidias:
Please everybody check if you get the missed call notification... Doesn't work for me:

https://xdaforums.com/t/no-missed-call-notification-bug.4389179/
[Google Pixel 6 Pro] roirraW "edor" ehT:
Was that 81% including the amount of battery used to actually update? Hopefully, the battery performs better for you in the very near future. I only charge between 25% and 75%, and that 50% usually lasts me a day as well, so I'll be monitoring to see if it seems about the same or not.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Please don't post in multiple threads asking about the same problem, especially since you created a dedicated question thread for the issue already. I tested and I'll answer you in the other thread.
[Google Pixel 6 Pro] Lycidias:
Sorry but I originally thought it was a kernel problem. But it wasn't... So I created a thread and just wanted to share my experience in this update thread, regarding this issue....

Sorry again