• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

General January update has dropped.

Search This thread

Alekos

Senior Member
My OTA update is 215MB. Unfortunately, it has been frozen on "Optimizing your device" for the last 30 minutes.
the update is supposed to work in the background without impeding the user experience. I know we all want it to update fast but it's not how it's meant to work. depending on the device, amount of apps and free system resources, it can take 20 mins to 3 hours.

it's all good! supposed to be that way
 

Alekos

Senior Member
This was a pleasant Jan update surprise! My hope this resolves annoying issues with the phone for me:120Hz bug and BT LDAC 990kbps bug.

whatsisnametake2


which BT DAC /usb dacs are you guys using? I'm using the BTR5 and LDAC 990 isn't working but is on my other Pixels.
sorry messed up the quotes (not sure how to add a quote or name after the fact lol its only been 12 years of posting
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

Vash369

Member
Sep 4, 2012
9
13
Tampa

whatsisnametake2


which BT DAC /usb dacs are you guys using? I'm using the BTR5 and LDAC 990 isn't working but is on my other Pixels. sorry messed up the quotes
Nothing in particular in this case. I use by headphones directly connected to the phone, so only the DAC within the cans are used. LDAC 990kbps works great with the phone but only in a certain condition pre-update.

When the phone screen is on the sound stutters in the LDAC config. Hopefully that's remedied.

Update: issue still exists
 
Last edited:
  • Sad
Reactions: roirraW "edor" ehT

LLStarks

Senior Member
Jun 1, 2012
1,673
689
It was a painful wait. Everything through November was technically August build fingerprint. Not sure why Google keeps doing that for Pixels.
 

whatsisnametake2

Senior Member
Sep 15, 2008
227
56
Google Pixel 6 Pro

whatsisnametake2


which BT DAC /usb dacs are you guys using? I'm using the BTR5 and LDAC 990 isn't working but is on my other Pixels.
sorry messed up the quotes (not sure how to add a quote or name after the fact lol its only been 12 years of posting
I'm using a hidizs sonata. neutron player can communicate directly with the dac usually. doesn't work with p6p. sent log files to neutron dev he confirmed it was an issue with the phone firmware.
 

Lughnasadh

Senior Member
Mar 23, 2015
2,710
2,351
Google Nexus 5
Huawei Nexus 6P
Hoping to get the Google Assistant "Quick Phrase" back with this January update, but no, it still missing!
It's showing up for me

Screenshot_20220114-221841_Google.png
 
  • Like
Reactions: roirraW "edor" ehT

Alekos

Senior Member
Nothing in particular in this case. I use by headphones directly connected to the phone, so only the DAC within the cans are used. LDAC 990kbps works great with the phone but only in a certain condition pre-update.

When the phone screen is on the sound stutters in the LDAC config. Hopefully that's remedied.

Update: issue still exists
yeah I worded my post wrong, it was quite a mess. my ear buds don't do Full quality LDAC either on the 6 pro (but are fine on other pixels). I'm not an audiophile but I do like good quality music. Spending $1380.00 CAD and it not working, is mostly what irks me
 
Last edited:
  • Like
Reactions: Vash369

Guyinlaca

Senior Member
Sep 13, 2010
423
197
Google Pixel 6 Pro
So the January update improved stability but now Fabricated Overlay mods no longer work. Good thing I got the unlocked model because it looks like unlocking the bootloader and root are the only ways to customize anything, even just hiding the navigation pill.
 

foobar66

Senior Member
Jan 8, 2011
2,036
2,068
Brussels
Google Pixel 6 Pro
Grr ... I'm stuck (I think) ... I was rooted:
- removed all magisk modules
- removed magisk
- changed the flash-all.sh script with:
Code:
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:
Code:
--------------------------------------------
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 ...
 

vlubosh

Senior Member
Sep 8, 2007
220
143
Bratislava
Google Pixel 6 Pro
Grr ... I'm stuck (I think) ... I was rooted:
- removed all magisk modules
- removed magisk
- changed the flash-all.sh script with:
Code:
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:
Code:
--------------------------------------------
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 ...
Try to update platform tools
 
  • Like
Reactions: roirraW "edor" ehT

foobar66

Senior Member
Jan 8, 2011
2,036
2,068
Brussels
Google Pixel 6 Pro
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).
 
Last edited:

RetroTech07

Senior Member
Apr 24, 2021
205
106
Google Pixel 2 XL
Google Pixel 6 Pro
Grr ... I'm stuck (I think) ... I was rooted:
- removed all magisk modules
- removed magisk

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 ...
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.
 
  • Like
Reactions: foobar66

foobar66

Senior Member
Jan 8, 2011
2,036
2,068
Brussels
Google Pixel 6 Pro
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.
Yes, as mentioned in my previous post (https://forum.xda-developers.com/t/january-update-has-dropped.4388425/post-86259799) ... it was the cable ... back up and running on January build & rooted (without wiping).
 

Top Liked Posts

  • 2
    I did the January update yesterday and MMS didn't work afterward so did a factory reset to fix it. I posted about this and got good pointers on how to fix it.

    This update has REALLY improved my mobile connectivity. The phone isn't constantly polling 5G like it was before and it hands off between 5G, 5G UC and LTE much better.

    There are a couple locations where signal is weird and it drops down to H+.

    I'm really glad that this appears to have addressed the majority of my signal issues.
    2
    Over the last couple of days I had 2 voicemails that just showed up. My phone never rang when they called. Who knows how many other calls that never rang and they didn't leave a voicemail. It could be a coincidence but I didn't have the issue before the update.

    Were they spam, or possibly identified as spam? Depending on your settings spam calls will be sent straight to voicemail.
    2
    Were they spam, or possibly identified as spam? Depending on your settings spam calls will be sent straight to voicemail.
    Nope. Both were from people in my contacts. They're not even listed as missed calls, just voicemails.
    1
    I started the update with it plugged in and left it updating and charging overnight. I unplugged it in the morning, restarted the device as per update instructions, within 30 seconds of unplugging. I used it the same way as normal throughout the day and ended with a displayed 19% on screen.

    Battery level currently on 72%, so it might have been a one off by the looks.
    Cool, hopefully, it continues working well for you.

    I'm still trying to get the update from system->system updates. It starts downloading, but after about a minute it stops and says it cannot continue. I haven't done the side load (yet) as I'm trying to see if the built in update works. Has anyone gotten it to update without side loading?
    My wife has and some others in this forum section have, yes. I'm rooted so I manually updated.

    Did anyone lose the weather off of the lockscreen after the update?
    The weather is still there for me.
    1
    The weather is still there for me.
    Guess I'll do some digging. Hopefully I don't have to factory reset.
  • 5
    Please everybody check if you get the missed call notification... Doesn't work for me:

    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.
    4
    Fingerprint scanner is so much faster...
    A lot of people seem to be saying this. I noticed it was faster before I saw other people comment, so don't think it's placebo on my part.
    4
    I never take chances. I always factory flash without wiping. OTAs are such a messy process.

    So far, things are very stable.
    4
    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.
    4
    Fingerprint scanner is so much faster...