carrier-explode Explode and decode carrier data GitHub About

Wiki

iOS

Notes on iOS carrier bundles: what is in them, how iOS picks one, how they are delivered and signed, and what the modem files inside them do. Written from the bundles this site holds, and where a number can be read from them, read live.

ArticleCovers
.der.griThe global_setting files in the Default bundle - regional baseband tables that apply whatever carrier is in the phone, in Qualcomm and Intel/Apple C1 flavours.
.der.priBaseband override files in iOS carrier bundles: what they hold, the Qualcomm and Intel/Apple C1 formats, and how iOS sends them to the modem.
Bundle SelectionHow iOS gets from a SIM to a carrier bundle, how MVNOs share one, how per-phone overrides and country bundles are layered on top, and which copy wins.
Carrier BundleWhat an iOS carrier bundle is, what is inside one today, where it comes from, and how it is versioned and signed.
Carrier Bundle ManifestThe iTunes version plist that lists every published carrier and country bundle, and the lookup tables in it that turn a SIM into a bundle name.
Carrier.plistThe main settings file of a carrier bundle today: the common keys, the modern APN type-mask bits, and the strange values in current bundles.
Default bundleDefault.bundle - the fallback carrier bundle, and the 18 MB of alert sounds, lookup tables, regional modem tables and motion thresholds that ship in it.
IPCCThe .ipcc file a carrier bundle is shipped in, where Apple hosts them, how they are named and checksummed, and how the URL scheme has changed since 2009.
PRIThe plaintext .pri files in older carrier bundles - CDMA-era baseband settings as a property list, the sections in them, and carrier.prl.
Self-registrationHow Chinese carrier device self-registration shows up in iOS: terminal-registration SMS in carrier bundles and ds_autoreg in Qualcomm modem firmware.

Carriers

What is unusual in the settings of some of the larger carriers.

ArticleCovers
AT&TWhat is unusual in AT&T's iOS carrier bundle (ATT_US): its sub-brands, per-phone modem files, a Wi-Fi secret unchanged since 2009, and fast eSIM polling.
JioWhat is unusual in Reliance Jio's iOS carrier bundle: Wi-Fi Calling rules for emergency calls, a misspelled key, odd XCAP ports and live ID checks for eSIM.
Rakuten MobileWhat is unusual in Rakuten Mobile's iOS carrier bundle: a 50-minute SIP timer, XCAP over plain HTTP, one-minute emergency alerts, and a misspelled watchOS key.
T-Mobile USWhat is unusual in T-Mobile's iOS carrier bundle: 35 SIM ranges, IoT MVNOs, a lab server in production, text-to-911 test numbers and QuickSwitch.
VerizonWhat is unusual in Verizon's iOS carrier bundle: MVNOs told apart by GID2, mmWave settings, no Wi-Fi handover during 911 calls, and big MMS video.
Vodafone UKWhat is unusual in Vodafone UK's iOS carrier bundle: the only default 5G network slice, captive portal bypasses, and a once-a-day eSIM check.

Pixel

Notes on Pixel carrier settings: the files in each build, how a SIM picks one, what they set, and where each modem keeps its own carrier configuration. Written from the Pixel builds this site holds and from AOSP.

ArticleCovers
carrier_list.pbThe CarrierList protobuf in a Pixel's CarrierSettings: MCC-MNC rules, MVNO rules by GID1, SPN or IMSI prefix, the order they are read in, and its oddities.
CarrierConfig and APNsWhat is inside a Pixel carrier settings file: CarrierConfigManager keys and their value types, the APN list, vendor configs, and fields AOSP's proto lacks.
CarrierSettingsThe etc/CarrierSettings directory in every Pixel build: its .pb files, others.pb, default.pb and no_sim.pb, how they differ per Pixel, and their versions.
Pixel modem configurationWhere each Pixel's modem keeps its per-carrier configuration: Qualcomm MCFG files, Samsung Shannon cfg.db, manifests and confseqs, and MediaTek MCF files.

Galaxy

Notes on Galaxy carrier settings: the carrier pack each sales code gets in a firmware, how a SIM picks one, where its IMS settings live, and the modem's own configurations. Written from the US Galaxy firmware this site holds.

ArticleCovers
Carrier packThe carrier pack each sales code gets in a Galaxy firmware's CSC: omc.info, customer.xml and the feature files, how a SIM selects a pack, where its IMS settings come from, and its versions.
Galaxy modem configurationThe Qualcomm MCFG configurations in a Snapdragon Galaxy firmware's CP member, why none is tied to a carrier, and why an Exynos model's are not read.

How it works

How this site gets its data: the feeds it checks, what it reads from each firmware and how, what it keeps, how it indexes it, and how the pages and the API read it. Written from the site's own code.

ArticleCovers
Apple ingestHow this site reads Apple's carrier files: iPhone IPSWs found through ipsw.me and AppleDB, the root filesystem decrypted and read in a container, copies merged across a build, and Apple's OTA carrier manifest.
Galaxy ingestHow this site reads Galaxy firmware: models found through Google Play's device list and builds through Samsung's version.xml, the firmware streamed from Samsung's FUS and decrypted on the way, carrier packs from CSC, modem configurations from CP, IMS operators from AP.
How carrier-explode worksThe pipeline end to end: feeds checked on a schedule, one Workflow per unit, artifacts and profiles in R2, the index in D1, and the site and API reading both. Why it is cheap to run.
IndexingHow this site indexes what it extracts: facts written per record, then each source's timeline, head, changes and phone states derived, and sources linked into carriers by the SIMs they claim.
Pixel ingestHow this site reads Pixel carrier files: each Pixel's full OTA read in place by HTTP Range, its CarrierSettings, carrier_list.pb and modem configurations kept, and Google's carrier settings update service.
ProfilesHow this site turns an iOS bundle, a Pixel .pb file or a Galaxy pack into one platform-neutral profile: concepts, raw settings, variants and SIM identity, stored by content hash, and the defaults read under a carrier.
Storage and servingWhat this site keeps in R2 and in D1, how the pages and the API read them per request, and how answers are cached at the edge and dropped when the index changes.