Research / compatibility data last verified
CAPABILITIES / APPLE INTELLIGENCE / MODEL DOWNLOAD
A storage number is not a download verdict. Separate a missing setting, an unavailable switch, an active queue, a static 16 KB entry, multi-gigabyte files and a feature that actually works—then take only the next step that fits that state.
THE DIRECT ANSWER
Apple documents prerequisites and says download time varies. It does not publish 16 KB as an error code, one correct model size or a universal timeout. We call the model stage complete only when the download message clears and one supported task works.
Record the exact Settings message.
Compare the same state at two times.
Run one supported feature.
Confirm core services still work.
CHOOSE THE RIGHT ROUTE
Start with how the Apple Intelligence surface appeared. That determines whether normal Apple support guidance or an experimental-state boundary applies.
Compatible device, current supported software, at least 7 GB free, supported region, matching supported device and Siri languages, Wi-Fi and power.
A flag or identity edit can expose UI without supplying compatible hardware, complete models or working services. A stuck queue can be the final partial result.
DOWNLOAD STATE ROUTER
This form runs locally in the page. It cannot inspect your phone, USB connection, files, account or network.
NEXT SAFE STEP
Select the route, visible status, storage observation, change over time, prerequisites, functional result and device health.
EXACT OBSERVED STATES
Each row closes one diagnostic branch. Do not skip from a missing setting to model-file troubleshooting.
Pre-download: UI/eligibility not reached.
Resolve hardware or exact product/build. Do not diagnose model storage.
Pre-download: prerequisite or eligibility gate.
Check hardware, language, region and storage; preserve experimental partial state.
Active queue observed; completion not proven.
On the official route, keep stable Wi-Fi and power and compare later.
Tiny incomplete or unverified entry—not an Apple code.
Capture the exact message. Do not delete assets or repeat Apply.
Assets present; readiness still not established.
Use Settings status and function, not a target number.
Model-ready state reported; service/function incomplete.
Verify feature availability, language and region. Stop stacking edits.
Device-specific functional observation.
Save exact build, route and test. Do not generalize to other devices.
SAFE OBSERVATION RUN
The goal is not to wait a magic number of minutes. It is to learn whether the state is changing without adding another variable.
Device model and origin variant, ProductVersion, BuildVersion, product release, ProductType/region edits, device language and Siri language.
ONE ATTRIBUTABLE STATERecord time, Settings wording, storage value and unit, free storage, Wi-Fi/power state and any temperature message.
DO NOT PARAPHRASE AN ERRORKeep the supported path on stable Wi-Fi and power. Later, record whether the message or storage changed. Do not Apply between observations.
CHANGE / STATIC / UNKNOWNRun one feature Apple supports in that language and region twice. Siri glow or Settings alone is not a functional test.
REPEATABLE TASKCheck Face ID, Siri, Dictation, microphone/audio, calls, cellular data, activation and device identity.
BASELINE OVERRIDES FEATUREUse it to decide whether the supported path has enough available storage. Do not treat it as the expected size of downloaded models.
16 KB, a growing value or several gigabytes can help describe the state. None proves a usable service alone.
A completed message plus a repeatable supported task is stronger evidence. It still does not turn unsupported hardware into Apple-supported hardware.
DO NOT TURN ONE QUEUE INTO THREE PROBLEMS
Conflicting community “fix lists” are reports from different devices and builds, not a universal runbook.
Another write can make the result impossible to attribute and the original-file revert harder to verify.
Public reports include Face ID, voice, identity and activation effects. Do not add them to solve a storage number.
Apple does not document manual MobileAsset deletion as the normal download fix. It also does not restore MobileGestalt changes.
Do not keep the phone hot to prove activity or wait for a community gigabyte target. Cool the device if temperature controls appear.
STOP + REVERT BOUNDARY
Once a core service changes, this is no longer a “models stuck” problem.
Preserve the exact release, build, file and last action. Do not test another flag.
Do not click through unexpected activation or Apply again. Move to state-specific safety guidance.
Follow the reset route for the same product and release, then recheck identity and every affected service.
MODEL DOWNLOAD FAQ
Use the answer that matches the observed route and screen. Avoid combining fixes from different builds.
On Apple-supported hardware, first verify free storage, Wi-Fi and power, a supported region, and matching supported device and Siri languages. Apple says download time varies, so compare the status at two times instead of assuming a universal deadline. After a MisakaX or misaka26 identity change, a static queue can also be an unsupported or partial result; waiting and repeated Apply are not guaranteed fixes.
Apple does not document 16 KB as a readiness code or a complete model size. Public misaka26 issues show 16 KB alongside a stuck model state, and one report also had no new UI. Treat it as a tiny incomplete or unverified asset entry until Settings reports readiness and a real Apple Intelligence task works.
No. It proves only that a tiny storage entry was observed. Record the exact Settings message and whether the value changes between two observations; neither a static 16 KB value nor storage growth by itself proves a completed usable model.
There is no single size we use as a pass condition. Model assets vary with device, software, language and enabled features, and community reports show different multi-gigabyte values while Settings still says downloading. The pass condition is a completed status plus a repeatable supported task—not a target number.
Apple currently lists 7 GB of available device storage as a requirement. That is a free-space requirement, not a published model-size target and not evidence that an experimental device can download or run the models.
Check the message in Settings under Apple Intelligence & Siri and record the Apple Intelligence or iOS storage entry shown in iPhone Storage. Apple does not provide a universal percentage or progress bar. Compare the same fields later and test a real feature only after the downloading message clears.
Apple says the time varies and recommends Wi-Fi and power; it publishes no universal maximum. A changing status or storage value is different from a static state, but neither has a guaranteed duration. If a core service changes, stop immediately rather than waiting.
Apple recommends Wi-Fi and power for the initial model download. A hotspot may behave differently from a normal Wi-Fi connection and is not a reliable troubleshooting control. Use a stable Wi-Fi connection on the supported path; do not alter MobileGestalt or ProductType to compensate for network behavior.
Yes on Apple’s supported path: Apple says the device language and Siri language must be the same supported language. After changing Siri language, Apple Intelligence can remain unavailable until that language finishes downloading. Matching them does not override unsupported hardware, region or build.
Apple says Apple Intelligence can remain unavailable while the newly selected Siri language downloads. Record the language change and allow that supported download to finish. Avoid cycling languages repeatedly because it destroys a clean before-and-after observation.
Do not treat a region or ProductType edit as a stable model-download fix. Apple currently says Apple Intelligence does not work on supported devices purchased in China mainland and describes additional restrictions when both location and Apple Account region are China mainland. Community workarounds reach conflicting states, including missing UI, an unavailable switch and models that never finish.
That is not yet a model-download problem. First resolve compatible hardware or the exact MisakaX/misaka26 release and build, then determine whether the intended settings surface was exposed. Do not use a storage number to diagnose models when the settings stage itself is absent.
A visible but unavailable switch usually means the flow has not passed eligibility or prerequisites. Check Apple’s hardware, software, language, region and storage requirements on the official path. On an experimental path, preserve the partial result instead of stacking ProductType or region edits.
File presence and service readiness are separate states. Community reports on supported devices and experimental devices show multi-gigabyte storage while the UI still reports downloading or functions remain unavailable. Use Settings status and a real task as the completion test.
Preparing is still an incomplete state, not a ready result. Record it exactly, then compare the same Settings message and storage entry later without changing language, identity or region between observations. Legacy community procedures include multi-gigabyte files that remained on Preparing, so file size cannot close this state.
Downloaded assets do not prove that eligibility, language, region, hardware support and each service are ready. Test one feature that Apple supports for the selected device, language and region. If it fails, classify the result as models present but function not verified.
No. Apply is a device-state write, not a download retry button. Repeated writes make attribution and rollback harder and can introduce unrelated identity or service changes. Capture the first result, verify prerequisites and stop at the first incomplete stage.
We do not recommend changing ProductType as a generic download fix. Community procedures are beta-specific and reports include Face ID, identity, UI and model failures. If ProductType was already changed and a core service changed, restore the untouched MobileGestalt from that device using the matched reset route.
Do not assume the models or UI will persist. Community results conflict, and the project publishes no persistence contract for this sequence. Restore the real identity to recover the baseline; if Apple Intelligence disappears, record that outcome instead of reapplying the spoof.
Apple says turning off Apple Intelligence removes its on-device models on the supported path. That switch does not restore ProductType, region or eligibility values written through MobileGestalt, so it is not a substitute for the matched MisakaX reset route.
A normal restart is a reversible observation on a responsive, Apple-supported device. Apple reserves a force restart for an unresponsive iPhone. Neither action repairs an unsupported ProductType edit, and repeated restarts are not proof of progress.
Do not use Reset Network Settings as a first-line download button. Apple says it removes saved networks and VPN settings that were not installed by a profile or device management, and disconnects the current network; Apple does not promise that this fixes Apple Intelligence models. First use a known stable Wi-Fi connection and preserve the current download evidence.
On Apple-supported hardware, first back up and follow Apple’s current update guidance. On a MisakaX or misaka26 path, do not update only to fix the queue until you recheck the exact product and build range; the update can remove the available write or revert path.
Do not delete system model assets based on a storage value or community path. Apple does not publish manual asset deletion as the normal fix, and deleting files adds a new variable without restoring MobileGestalt identity changes. Preserve evidence and use documented controls.
No. Heat is not a completion signal. If the iPhone becomes unusually warm or displays Charging On Hold or a temperature warning, stop stressing it, disconnect unnecessary activity and let it cool according to Apple’s temperature guidance.
Not as a first-line test. An erase can cause data loss and still does not prove the cause of a queue. Record the exact state, protect a current backup and exhaust the supported prerequisites or matched revert path before considering recovery actions.
Keep the two timestamped observations, exact Settings wording, free storage, language and network details, then contact Apple Support. A supported-device queue can still be a service or software incident. Do not borrow an experimental ProductType procedure or delete system assets to turn it into a different problem.
Include device model and origin variant, ProductVersion and BuildVersion, MisakaX/misaka26 release, whether ProductType or region was changed, device and Siri languages, region, free storage, network and power state, exact Settings message, two timestamped storage observations, one functional test, and any Face ID, voice, call, data, activation or boot change.
SOURCES + EVIDENCE BOUNDARIES
Apple pages support prerequisites, restart, update and temperature guidance. GitHub issues and forum threads are device-specific reports, so we use them to name failure states—not to promise a fix or a model size.