Direct answer
For the Google Pixel 7, eligibility, power, storage, network, date/time and update service should be checked before recovery. First, record the exact version, message, battery and free space.
What this covers
- Google Pixel 7 (GVU6C/GQML3)
- Google Pixel family; Tensor generation, fingerprint/face unlock, modem and Pixel Feature Drop eligibility vary.
- The specific fault this record addresses: software update will not download or install
What it does not cover
- ×The same symptom on a different Google product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
Not enough free space to stage the update
What separates it It downloads and fails at install, consistently. Installation needs room to unpack and stage as well as to store.
How to confirm Free substantially more than the update's stated size — several times it, not just a little more.
- 2
The battery is below the required threshold
What separates it It refuses to begin, or begins only on the charger. Both platforms require a minimum charge or mains power before installing.
How to confirm Charge above the threshold and connect the charger. This is a requirement rather than a recommendation.
- 3
A staged rollout that has not reached this device
What separates it The phone reports itself up to date on a version that is not the newest. Updates release in waves by region and device.
How to confirm Compare the installed version against what is actually released for that exact model. Waiting is the correct action.
- 4
The download is being interrupted
What separates it It fails at varying percentages. A large sustained download over a marginal or metered connection fails in exactly this pattern.
How to confirm Retry on a stable network. Failures at varying points are transport; failures at the same point are not.
- 5
The device has reached its supported OS life
What separates it A version is available for the model line and not for this device. Support windows end, and the phone does not always say so plainly.
How to confirm Check the manufacturer's supported-version list for the exact model. No amount of retrying changes this.
- 6
A previous partial download is corrupt
What separates it The same failure repeats at the same point regardless of network. The staged file is bad and is being reused.
How to confirm Delete the downloaded update where the platform allows it, then download it again.
- 7
A profile, VPN or management policy is blocking it
What separates it Updates are unavailable or deferred on a phone that is enrolled in workplace management. Deferral is a policy setting.
How to confirm Check for a management profile. This is not something the user can override.
- 8
Time is being underestimated
What separates it The phone appears frozen on the logo for a long time after an update. Post-update optimisation is genuine work and shows no progress.
How to confirm Leave it alone, on power, for far longer than seems reasonable. Interrupting here is what turns a slow update into a broken phone.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- The version installed now and the version being offered, both written down before starting.
- The exact stage it fails at — download, verify, or install — and whether it is the same stage every time.
- Free storage before the attempt, against the update's stated size.
- The battery level, and whether the phone was on power.
- Whether the failure point varies between attempts, which separates transport from a bad staged file.
- Whether the phone is enrolled in any workplace management profile.
- Whether a backup exists — an update is exactly the wrong time to discover there is not one.
Back up before starting
ReversibleUpdates almost always go fine, and the small share that do not are exactly the cases where a backup is the difference between an inconvenience and a loss. This is the step people skip because the update usually works.
Note which stage it fails at
ReversibleDownload, verify and install have different requirements — bandwidth, integrity and free space respectively. The stage is far more informative than the error message, and a failure at the same stage every time is describing a specific unmet requirement.
Free several times the update's stated size
ReversibleInstallation needs room to unpack and stage as well as to store the result. An update that downloads and then fails at install is nearly always this, and freeing a little more than the stated size is not enough.
Charge above the threshold and stay on power
ReversibleBoth platforms require a minimum charge or mains power before installing, and it is a requirement rather than advice. An update that refuses to begin, or begins only when plugged in, has already told you this.
Retry on a stable, unmetered network
ReversibleFailures at varying percentages are the download being interrupted. Failures at the same percentage every time are not, and retrying on a better network will not help those — that distinction saves a lot of pointless retrying.
Delete a corrupt staged download and fetch it again
ReversibleThe same failure at the same point regardless of network means the staged file is bad and is being reused. Removing it forces a fresh download, which is the only thing that clears this.
Check whether the version is actually available for this model
ReversibleStaged rollouts release in waves, and support windows end. A phone reporting itself up to date on an older version may be waiting its turn or may be past its supported life — and neither is fixed by retrying.
Leave it alone during post-update optimisation
ReversibleA phone sitting on the logo after an update is doing genuine work with no progress shown. Interrupting here is what turns a slow update into a broken phone, and the asymmetry is stark: waiting costs time, interrupting costs the device.
Check for a management profile before concluding anything
ReversibleAn enrolled phone can have updates deferred or blocked by policy, which is not something the user can override and not something any amount of troubleshooting will reveal from the update screen alone.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- GVU6C/GQML3. Google Pixel family; Tensor generation, fingerprint/face unlock, modem and Pixel Feature Drop eligibility vary.
- Tier — base flagship (Tensor G2, no telephoto)
- The Pixel 7 — Tensor G2, main + ultrawide (no telephoto), stock Android with Pixel AI. Older flagship nearing its 5-year update-window end.
- Pixel AI + Tensor
- Pixel-exclusive AI; Tensor G2 runs warm under load — normal.
- eSIM
- Supports eSIM; connectivity issues are carrier/eSIM first.
- Connector
- USB-C. A cable that fits is not necessarily a cable rated for this phone's charging speed — USB-C carries several power profiles and a cable built for data will charge slowly or intermittently while seating perfectly.
- Biometric
- An in-display fingerprint reader, which looks through the screen. A thick or incompatible screen protector genuinely interferes with it, which is why unlock reliability often changes the day a protector is fitted rather than gradually.
- SIM
- Carries an eSIM. An eSIM does not travel with the handset the way a plastic SIM does: a phone swap, a factory reset or a repair can leave the profile behind, and restoring it is a carrier action rather than a phone setting.
- Modem
- 5G capable. In marginal 5G coverage the phone hands repeatedly between 5G and LTE, which costs more battery and generates more heat than settling on either — so the preferred-network setting is a real diagnostic lever rather than a preference.
- Charging
- Supports wireless charging. Coil alignment is tighter than it looks and a thick case, a metal plate or a card in the case defeats it entirely — so wireless charging failing while cable charging works is usually the case rather than the phone.
- Water resistance
- Rated water resistant, which is not waterproof and which degrades with age, drops and seal disturbance. The rating covers incidental exposure; it is not a guarantee, and moisture-detection warnings are deliberately conservative and can persist after the port feels dry.
- Platform
- Android, with a manufacturer interface layer over it. Battery optimisation and background-execution restrictions are applied per app and are far more aggressive than on iOS — which is why 'set this app to unrestricted' is a real fix here and has no equivalent elsewhere.
- Symptom boundary
- This record covers Google Pixel 7 when it software update will not download or install. A different symptom on the same hardware, or this symptom on a different Google product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !The phone has been unresponsive since an interrupted update — stop power-cycling it, which can compound a partial write.
- !The device is past its supported OS life, which is a hardware decision rather than a fault.
- !A management profile is deferring updates and only the administrator can change it.
- !The update installs and the phone then fails to boot normally.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Pixel Help publishes this as "Check & update your Android version". Google's software-update article for Pixel. Probed 2026-08-28, after the 2026-08-23 rate limit had cleared: title-verified. What that article does not carry is the model boundary — it is written for a product line, and GVU6C/GQML3 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My Pixel 7 fingerprint reader often fails to unlock.+
The Pixel 6/7 under-display fingerprint sensor is known for being slower and less reliable than a physical reader. Delete and re-enrol your fingerprint (enrolling the same finger twice helps), press firmly and fully on the sensor, keep the screen clean, use a sensor-friendly screen protector, and stay updated. Face Unlock (added via update) is an alternative for convenience. It is a characteristic of these models rather than a one-off fault.
The update says I do not have enough space but I have more than its size.+
Installation needs room to unpack and stage as well as to store the result, so it commonly requires several times the stated size. This is normal. Free substantially more than you think you need rather than scraping past the stated figure.
It fails at a different point every time.+
That is the download being interrupted, which points at the network rather than the phone. Retry on a stable, unmetered connection. A failure at the same point every time means the opposite — the staged file is bad and needs deleting and re-fetching.
My phone says it is up to date but there is a newer version.+
Staged rollouts release in waves by region and device, so this is usually just your turn not having come. Check the manufacturer's supported-version list for your exact model though — if support has ended, no amount of waiting will produce it.
The phone has been on the logo for ages after an update.+
Leave it alone, on power. Post-update optimisation is genuine work and it shows no progress while it happens. The asymmetry matters: waiting an extra hour costs an hour, and interrupting a write costs the phone.
It will not start the update at all.+
Check the battery level and connect the charger. Both platforms require a minimum charge or mains power before installing — it is a hard requirement, and a phone that refuses to begin or only begins when plugged in has already told you that is the reason.
Should I back up first?+
Yes, and this is the step most people skip because updates usually work. The small share that do not are exactly the cases where a backup is the difference between an afternoon of inconvenience and losing everything on the phone.
Can I skip an update?+
You can defer most, but security fixes are the reason not to defer indefinitely. The practical approach is to update when you can leave the phone alone, on power, on a good network — not when you are about to need it.
My work phone will not offer updates.+
Check for a management profile. An enrolled phone can have updates deferred or blocked by policy, which the update screen does not explain and which you cannot override — that is an administrator matter.
The update installed and now the phone is slow and hot.+
Give it a few charge cycles. Photo indexing, search rebuilding and app optimisation all run once after a major update and are genuinely heavy. Judging performance in the first days measures the re-indexing rather than the update.
Does this answer apply to every Google model?+
No. It is scoped to GVU6C/GQML3. Google Pixel family; Tensor generation, fingerprint/face unlock, modem and Pixel Feature Drop eligibility vary.
What should I record before troubleshooting update failed or won't install?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing update failed, won't install. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not interrupt an active firmware install or use files for another model/region.
Answer for the exact device and software version shown above.