Impacted device. I had a bloat on my battery and changed the battery due that last month or so. After that I heard google was paying up, took the cash voucher. As of today, the phone is screwed up, battery wise.
Changes coming to your Pixel 4a
- Thread starter bombadier
- Start date
Mine could barely hold a charge, the battery percentage wasn't updating, and took a long time to charge. This is consistent with other people's reports
The Day Google Killed the Pixel 4a
In 2025, Google killed the Pixel 4a.
www.lambdalatitudinarians.org
Thank you Louis Rossmann for getting public awareness of this garbage behavior
I'm fully aware of the results after the update on my "impacted" 4a. Do we know if any 4a's came through the update unscathed? The above video suggests that even Google may not know whether the issue is a batch of bad batteries or something else. Yet they do know the IMEI numbers that are likely to have problems. I wonder what info they are basing that on, and why we aren't being told. They seem to imply that impacted devices will perform like non-impacted devices after they have the battery replaced.
From Google:
From Google:
Summary of program
Google has determined that certain Pixel 4a phones require a software update to improve the stability of their battery’s performance. An automatic update to Android 13 will roll out to all Pixel 4a devices starting January 8, 2025. For some devices (“Impacted Devices”), the software update reduces available battery capacity and impacts charging performance. We want our customers to have the best possible experience with their products, so users of these Impacted Devices are eligible for an appeasement from Google. Not all Pixel 4a devices are impacted by the reduction in battery capacity and charging performance, therefore if your device is not impacted the battery will perform the same as before, and you will not be eligible for an appeasement. You can find out if your device is eligible here.
Last edited:
It's hard to gauge how many people aren't impacted, because they're not going to post about things going normally. My speculation.
Also I updated the torrents to use a tracker list because apparently a DHT can't bootstrap without initial
trackers? Frankly I don't understand how it works. Conflicting info https://superuser.com/questions/592...ent-client-initially-discover-peers-using-dht
Before or after I changed it? The reason I thought it wasn't working is my client Deluge wasn't reporting any data uploaded or downloaded at all.
Here is another one from Reddit. Looks like sunfish-ota-tq3a.230805.001.s1-965296b1.zip
I can confirm the SHA256 from one downloaded here but I have not verified the torrent.
magnet:?xt=urn:btih:c227d513092c738b7af23c8e96755dbbad419e04&dn=sunfish-ota-tq3a.230805.001.s1-965296b1.zip&tr=udp%3A%2F%2Fopen.stealth.si%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Fopen.demonii.com%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=https%3A%2F%2Ftracker2.ctix.cn%3A443%2Fannounce&tr=https%3A%2F%2Ftracker1.520.jp%3A443%2Fannounce&tr=udp%3A%2F%2Fopentracker.i2p.rocks%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A6969%2Fannounce&tr=http%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=udp%3A%2F%2Fexodus.desync.com%3A6969%2Fannounce
Last edited:
For those new to this thread, I have updated the instructions for roll back here.
Bear in mind that Google MUST have had a reason for doing this. Take time to physically check your device for any signs of battery damage, or overheating while charging. If it shows signs of damage, replace the battery or the device immediately.
Bear in mind that Google MUST have had a reason for doing this. Take time to physically check your device for any signs of battery damage, or overheating while charging. If it shows signs of damage, replace the battery or the device immediately.
When I built that ROM, that was the latest at that time. I probably haven't updated the thread OR the actual ROM was built against that version. To be honest, I think I have updated my daily to the latest firmware. ie bootloader and modem
If you ever need to upload a file to XDA that is banned, simply zip the file and attach the zip.
I think the "impacted" and not *may* be triggered by the liability laws of the region the phone was sold in. They haven't said why, but this must be a costly process for them. The IMEA check could be a bad batch issue, but I assume all regions will get the update, including those without a battery voucher.
Hello guys,
What is the difference between the factory and the OTA files?
I'm on Android 11, with a locked bootloader, no root, everything stock, and will eventually want to move to Android 13 without wiping any data. Which one should I get, the OTA, right?
Thanks!
What is the difference between the factory and the OTA files?
I'm on Android 11, with a locked bootloader, no root, everything stock, and will eventually want to move to Android 13 without wiping any data. Which one should I get, the OTA, right?
Thanks!
Manually flashing the OTA ( linked above) from recovery will get you to the November 2023 stock, but you will then face the forced update to January 2025.
How have you managed to stay on A11?
Hey @majorfigjam,
I turned off automatic updates in developer options the moment I got the phone. I didn't want to move to A12 for various reasons and I am still on A11. I got the update notification to A13 Jan 2025 when I went to System Update and clicked on Check for Updates - stupid me, I shouldn't have ever done this manual check, before this, there were 0 requests to googlezip.net from my phone even though it said Update Checked Successfully!
Btw, I'm the one who found the update URLs and posted it here and on Reddit, so I know it will ask me for a forced update to Jan 2025, but I know how to block that, for now at least
They might change the OTA update url from googlezip to something else in the future but we should be able to sniff this change and block the new urls too.Anyway, the ota linked above, is this a full OTA? Will it have all the data that's required to move my device from A11 to A13 Nov 2023?
Last edited:
It's the OTA from Google's site, so yes it should update fully from 11 to 13.Hey @majorfigjam,
I turned off automatic updates in developer options the moment I got the phone. I didn't want to move to A12 for various reasons and I am still on A11. I got the update notification to A13 Jan 2025 when I went to System Update and clicked on Check for Updates - stupid me, I shouldn't have ever done this manual check, before this, there were 0 requests to googlezip.net from my phone even though it said Update Checked Successfully!
Btw, I'm the one who found the update URLs and posted it here and on Reddit, so I know it will ask me for a forced update to Jan 2025, but I know how to block that, for now at least
Anyway, the ota linked above, is this a full OTA? Will it have all the data that's required to move my device from A11 to A13 Nov 2023?
I started the torrent and downloaded before you added the trackers, so I downloaded your updated torrent which added the trackers
Are you still using crDroid as your daily? I'm not sure whether I'll stick with the stock firmware or try crDroid but your opinion on stability and/or pro's and cons would be appreciated.
Are you saying you have flashed crDroid A13 with this Nov23 firmware?
Many thanks for any input and for your contributions.
Why are the SHA256 Checksums different for the Factory image from the two different sources?
Shouldn't they be the same?
SHA256 File Checksum #1
82902EA98C80F1A22706279A30D2BC46AA55CBE60703C9A02BA043BD052C6D99SHA256 File Checksum #2
9b03f2e5930c4669e3d4b3645fc28ed19bf82cffc428df7a186bb8d6afdfbd00
because the were uploaded differently, thats what the SHA256 is checking that the uploaded file matches the source file that was uploaded
Btw, I downloaded the Factory Image from Google Drive:
https://drive.google.com/file/d/12C99s1s8LfSKg_CASWgGT93TJKd10fvy/view?usp=drivesdk
as posted here on the Reddit comment here:
If anyone wants to download directly and not torrent, just use the Google Drive link.
This one's SHA256 is 82902ea98c80f1a22706279a30d2bc46aa55cbe60703c9a02ba043bd052c6d99 which matches the SHA256 starting letters/numbers from https://github.com/CNMan/Nexus5X/co...2ba1ceb5cefb3cc125ba64b17ffb4165a9795ecddb09b for this release, so I believe this is the real file and the correct SHA256 checksum.
The second factory image posted in the OP with the different checksum seems off for sure, paging @bombadier for more details!
https://drive.google.com/file/d/12C99s1s8LfSKg_CASWgGT93TJKd10fvy/view?usp=drivesdk
as posted here on the Reddit comment here:
If anyone wants to download directly and not torrent, just use the Google Drive link.
This one's SHA256 is 82902ea98c80f1a22706279a30d2bc46aa55cbe60703c9a02ba043bd052c6d99 which matches the SHA256 starting letters/numbers from https://github.com/CNMan/Nexus5X/co...2ba1ceb5cefb3cc125ba64b17ffb4165a9795ecddb09b for this release, so I believe this is the real file and the correct SHA256 checksum.
The second factory image posted in the OP with the different checksum seems off for sure, paging @bombadier for more details!
What do you mean uploaded differently? A file FILE1.zip has to have the same checksum irrespective of how many times FILE1.zip is downloaded and uploaded as long as it's not corrupt, right?
the checksum is to verify the files integrity so that it matches the source, when I uploaded the file I generated a checksum, that ensures that the file uploaded matches the file downloaded, as far as I am concerned the file I uploaded in the link is untouched and has not been modified, my file was downloaded from the google factory image page and generated that SHA256 when I checked here
SHA256 File Checksum
This SHA256 online tool helps you calculate the hash of a file from local or URL using SHA256 without uploading the file. It also supports HMAC.
emn178.github.io
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
11For anyone wanting to roll back to the previous November 2023 update from the January 2025 Battery hobbling update, the January 2025 update only makes changes to battery management everything else is the same as the November 2023 final update.
Some new information about the update has come to light see here for further reading
ARS Technica Article
Checking your Battery Serial Number
If your serial number contains this string, it will be nerfed by the battery performance update:
8230020501
If your serial number contains this string, your battery is unaffected:
8230015901
majorfigjam's How to Undo Google's January 2025 update without losing data (Unlocked Bootloader Only)
See this post by @amateurninja about how to block the update once you have rolled back
If you are going to unlock your bootloader to roll back then have you considered switching to a customROM? LineageOS may be the one for you
@xj0 can help with any questions
Ok since Google seem to of taken down all other firmware versions the Nov 2023 update (Pre Battery hobbling changes) can be downloaded
Android 13
Factory images sunfish-tq3a.230805.001.s1-factory-82902ea9
New link here or thanks to @Turing1ncomplete can be downloaded here
Thanks to @Xj0 both the factory image and OTA can be found on Archive.org Strap yourself in as this one will take a long time to download
SHA256 File Checksum
82902EA98C80F1A22706279A30D2BC46AA55CBE60703C9A02BA043BD052C6D99
Android 13
OTA Image sunfish-ota-tq3a.230805.001.s1-965296b1
here or here
SHA256 File Checksum
965296b1498b1d71bbf4013088b34213d5e6bc4dc836a7d06d1534eaf7621336
Thanks to @xj0 there is also a
Factory Image Torrent
OTA
SHA256 Checksums are the same as posted above and should match if downloaded correctly.
If either link doesnt work due to download requests being exceeded send me a PM and I will send an alternative link.
Older Firmware Versions
There is another torrent with the final firmware for A10, A11 and A12, the readme has the SHA - 256 Checksum for each zip file
Thanks to @smokejumper76 for posting the Checksums
Android 10 build (sunfish-qd4a.200805.003-factory-fac7c08d)
SHA-256 Checksum fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
-latest Android 11 build (sunfish-rq3a.211001.001-factory-5d6da39f)
SHA-256 Checksum 5d6da39f4611f22eb6a1e75dd5beeecb7734ae249fc8f9e725f7aa8e94100957
-latest Android 12 build (sunfish-sq3a.220705.003.a1-factory-c1963f71)
SHA-256 Checksum c1963f71ccbe9a393a16f98f53b9504620e298ea50353b0e347c7f892ff56d02
Just got this email from Google,
We wanted to let you know about an upcoming software update for your Pixel 4a that will affect the overall performance and stability of its battery. Pixel phones, like other smartphones, use rechargeable lithium-ion batteries that, over time, may experience performance, capacity or runtime degradation.
In the coming days, your Pixel 4a will receive an automatic software update to Android 13 that introduces new battery management features to improve the stability of your device. This update will reduce your battery's runtime and charging performance.
To address this, we're providing some options to consider. Please take a look and choose which one works best for you.
More details related to this change are available here. Eligibility criteria and other terms will apply.
Thank you,
Pixel team
Seems they are releasing an update that may affect the battery life if you have one of the affected devices, I have filled out the form and awaiting to find out if my 4a will be adversely affected with this new update, if it is I can get
A free battery replacement
B $50 or equivalent cash payment
C $100 or equivalent voucher towards another Pixel
Countries affected are US, Canada, UK. Germany. Singapore or India
Took me about a month to get my prefered option of the £100 Voucher, google processed my inital claim as wanting the cash with payoneer, took more as a few support sessions from Google to sort it out.
For Owners in Australia
ACCC Product Safety Announcement
In addition to the Google appeasement options it seems you may be able to get a full refund, see this @DiamondJohn post where he confirms that a full refund can be issued8I found the URLs for the ota updates and blocked them. This works even if the update has been triggered and not finished, and there's way to delete a downloaded update and stop the update too.
Posted this on Reddit and I am copy pasting it here.
THE ONLY WORKING SOLUTION to stop the forced battery update - this works even if the update is currently downloading, or has already been downloaded and it's waiting for a restart to apply it (self.Pixel4a)
submitted 3 days ago * by amateurninja
Step 1:
Block the following URLs using either:
- a firewall app
- or an app like AdAway
- or edit your hosts file directly if rooted
- or use a DNS service like NextDNS and make it the Android Default Private DNS setting
This is where the update is checked for from, and this is where it downloads the update from.
Note for NextDNS: it can block only whole domains, so use googlezip.net in the Denylist and not the full URLs
Step 2 (optional if the update is currently getting downloaded or has already been downloaded):
Go to Settings > Apps > Find Google Play Services > Clear Storage, this will delete the downloaded update, you might have to re-login to your Google Account etc. if you do this.
Step 3:
You can now go to System Update screen and hit Check Now, it will try to reach the above URLs and will say check complete and won't find the update as it can't reach the server!
The update will not get re-downloaded as long as the URLs can't be reached. You can check the NextDNS log, or the AdAway log or the log of app you are using to block the URLs - ota.googlezip.net would have been blocked.
**** Google for forcing this upon us!
I hope this helps at least a few people who are still trying to avoid this update!8*** DL LINK REMOVED ***
100% Done!
Its a free service, so the file will be up only for 6 days.
XXX
Code:Filename: sunfish-tq3a.230805.001.s1-factory-82902ea9.zip File size: 2.3 GB (2276267484 bytes) Created now (2025-01-23 06:33:15 UTC) Expires 6 days from now (2025-01-30 06:33:15 UTC)
For your own protection and certainty it downloaded correctly, check the SHA256: 82902EA98C80F1A22706279A30D2BC46AA55CBE60703C9A02BA043BD052C6D99
EDIT: Whoa! that hit 19 downloads in a few minutes!6How to undo Google's update without losing data (unlocked devices only).
As this post is now buried, I've deleted the detailed instructions, which can now be found here:
How to: Undo the January 2025 update without losing data (unlocked devices only).
You need to have some basic confidence with...
xdaforums.com
Good luck.5I just disabled automatic updates, hopefully that's enough.
"We have noticed you are still using this $50 phone that works perfectly fine and does everything you need. Therefore, your device has been queued for self-destruction triggered by the next software update. You can apply for reimbursement of e-waste disposal fees (up to $10.00 in store credit) using the attached form. Thanks for being a loyal Pixel(tm) customer!"
New posts
-
Firmware or boot.img for 2024 8" onn Tablet - 100135923- Latest: TheRandomPerson08
-
-
Need help for my onn 10.1 inch (2024 model number 100135925)
- Latest: TheRandomPerson08
