
If you need the official service manual for the Pocophone F1 mainboard, download XQ-AT45 from Xiaomi’s authorized technician portal. This document contains the precise component-level wiring map required for micro-soldering or troubleshooting faults. Avoid unverified sources–third-party “reverse-engineered” layouts often omit critical signal paths for power management ICs and modem traces.
Trace the primary voltage rails first: VSYS_5V (charging line), VBAT (main battery), and VREG_BOB (buck-boost converter output) are highlighted in red on the lower-right quadrant. The MSM845 SoC is positioned center-left; surrounding decoupling capacitors (0201 size 10µF X5R) must be inspected if experiencing sudden reboots. Check the PM660A power IC–its ground pad connects directly to thermal vias leading to the chassis.
For USB-C port repairs, locate the FUSB302B controller near the bottom edge. The data lines (CC1/CC2, SBU1/SBU2) are routed through ESD protection diodes (marked DZ17/DZ18)–replace these if the device fails to negotiate fast charging. The dual-camera ISP traces terminate at the S5K2L7 and S5K5E8 sensor pads; continuity tests should yield <0.5Ω resistance between the flex connector and SoC.
When diagnosing audio distortion, probe the WCD9340 codec’s left/right speaker outputs (SPKR_L+/SPKR_R+). The output stage runs at 4Ω impedance; voltage swings above 1.8Vpk indicate IC failure. For SIM tray issues, verify the RY6809 SD card/SIM switch–its enable line is pulled high by the PMIC (labelled GPIO_073).
Reference Circuit Analysis for F1 Model: Hands-On Instructions

Begin by sourcing the board layout file in .BRD or .PDF format–vendors typically host these under “Service Manuals” or “Technician Resources.” Locate the PMIC (PWR6529) section, marked near the battery connector (J101). Verify input capacitors (C2101, 10µF/6.3V) and inductor (L2101, 1µH) ratings; mismatches will cause unstable voltage rails (e.g., VSYS → 4.35V). Use a multimeter in continuity mode to trace VSYS_EN line back to the MCU–broken traces often masquerade as power failures.
Critical Signal Paths and Debugging Steps

- Display Interface: Check MIPI_DSI differential pairs (pins 3-6 on connector J401). Signal degradation here manifests as flickering or unresponsive touch. Probe with an oscilloscope for 1.2Vpp eye pattern at 900MHz; weaker signal indicates faulty flex cable or corroded pads.
- RF Front-End: Confirm WTR5975 power-amplifier outputs (RF_OUT on C812, C813) deliver >25dBm. Suboptimal power triggers dropped calls–swap the module if integrity checks fail.
- Flash Memory: Validate UFS 2.1 lanes (pins 1-8 on U1401) with JTAG. Corrupted bootloader often dumps logs to UART_TX (J503)–decode raw hex output via Minicom to pinpoint partition errors.
For boot-related issues, isolate the MSM845 (pin 36: PM_TIMEOUT). A grounded timeout pin forces recovery mode; floating it risks bricking. Replace R3101 (0Ω resistor) if missing–this bridges VREG_3P3 to the PMIC. Always log bootloader stages (SBL1 → HLOS) via UART to distinguish hardware faults from firmware corruption. Keep thermal paste (MX-4) thickness
Locating Authentic and Crowd-Sourced Blueprints for the F1 Device
Start with Xiaomi’s official hardware documentation portal. Manufacturers occasionally release authorized circuit references for repair technicians–search for “Mi Authorized Repair Centers” or “Xiaomi Hardware SDK” on their global service site. Filter results by device codename “beryllium” (internal identifier) to isolate relevant PDFs. If logs or interaction histories exist, check cached versions on Archive.org using specific URL patterns like “support-files.mi.com/beryllium/”.
GitHub repositories tagged “beryllium_board_rev” or “xiaomi_hardware” often host community-verified board layouts. Use search strings: “filename:*.kicad_pcb beryllium” or “file:*.pdf PCB layout beryllium” to narrow results. Notable contributors include the “MIUI-Devs” and “XDA-Powder” teams–forked copies usually fix broken links. Alternatively, XDA Developers forum threads labeled “beryllium motherboard” or “mainboard traces” house attached archives; filter posts by date after 2021 for updated revisions.
Alternative Sources Beyond Manufacturers
Check Telegram groups dedicated to Android reverse engineering–channels like “@MIUI_Hardware_Hackers” or “@MobileBoardRepair” frequently archive board scans. Look for lossless PNG exports of both front and rear PCB layers, often named “beryllium_layer_top.png” and “beryllium_layer_bottom.png”. Another route is electronics repair marketplaces (e.g., Taobao, AliExpress) selling “beryllium disassembly kits”; sellers sometimes bundle PDFs of internal layers as incentives.
EDA software communities offer curated libraries–search KiCad’s official repo for “xiaomi_beryllium” or inspect EasyEDA’s “Popular Projects” section. Hardware modders occasionally upload zipped Gerber files under titles like “beryllium_ref_board_rev1.2”; verify these by cross-referencing component IDs (e.g., PM8998, SMB1390) with known working samples. For isolated confirmation, ping active maintainers on Discord servers tied to lineageOS porting efforts–they often retain rare internal documentation.
Key Components and Signal Paths in the X1 Flagship Device Mainboard Layout
Identify the power management IC (PMIC) first–it regulates voltage rails for the CPU, GPU, and memory clusters. The Qualcomm SDM845 PMIC integrates 8 distinct buck converters and 32 low-dropout regulators. Use a multimeter to trace each VREG line to its destination: VDD_CPU (0.85V), VDD_GPU (0.75V), and VMEM (1.1V). Cross-reference these rails with the board’s silkscreen labels–misaligned voltages during debugging often stem from damaged or shorted PMIC outputs.
| Component | Key Signals | Voltage Range | Debug Tip |
|---|---|---|---|
| PMIC | VDD_CPU, VDD_GPU, VMEM | 0.75V–1.1V | Check for 0Ω shorts on output capacitors |
| RF Transceiver | TX_IN, RX_OUT, MIPI_RFFE | 1.8V (digital), 0.6V–1.2V (analog) | Scope RX_OUT for LTE band harmonics |
| DSP Cluster | SLIMBUS, I2S | 1.2V | Signal integrity drops if impedance exceeds 50Ω |
Trace SLIMBUS lines between the DSP and audio codec–these differential pairs carry 24-bit PCM data at 19.2MHz. Use an oscilloscope to verify eye patterns; jitter above 100ps typically indicates a failed termination resistor. The NFC antenna’s L-C filter network (27nH inductor + 47pF capacitor) must maintain a Q-factor above 20 to avoid carrier signal attenuation. Replace any swollen or discolored inductors immediately–they’re the most common failure point after water ingress.
Identifying Power Paths and Voltage Lines Through Circuit Documentation

Locate the main power input pins on the board layout–typically labeled VBAT, VIN, or SYS. Use a multimeter set to continuity mode to verify connections between these points and downstream regulators. Trace lines from the battery connector or USB-C port to the first PMIC or charging IC, noting series resistors (e.g., R50, R100) that may drop voltage before reaching critical components.
Follow high-current rails (marked VCORE, VCPU, VGPU) from the power management IC to their termination points–often large inductors (L1, L2) or capacitors (C250). Check for parallel paths: smaller loads like DDR memory (VDDR) or RF modules (VRF) usually branch off via ferrite beads or low-dropout regulators (LDO). Annotate each rail’s expected voltage (e.g., 1.8V, 3.3V) to compare against live measurements.
Isolate fault points by measuring post-regulator outputs. If VCORE reads 0V but VIN shows 3.7V, suspect a failed buck converter or shorted output capacitor. For secondary rails, verify enable signals (e.g., EN, REG_EN) from the PMIC–missing pulses here indicate firmware issues or corrupted boot sequences.
Cross-reference silkscreen labels with datasheets of key ICs. PMICs like Qualcomm’s PMI8998 or MediaTek’s MT6359 route power through dozens of channels, each requiring precise sequencing. If probing reveals unstable output (e.g., 1.1V pulsing to 0.8V), focus on related feedback circuits–resistors tied to FB pins (R1K) often alter regulation targets. Log all findings in a table: Rail Name | Measured Voltage | Expected Voltage | Suspected Issue.
Troubleshooting Poco F1 Board-Level Problems Using Electrical Layouts
Start by probing the PM660A PMIC power rails if the device fails to power on. Check VSYS, VBAT, and VREG_LDO lines against the reference values in the circuit documentation–deviations above 5% often indicate a faulty PMIC or degraded solder joints. Use a multimeter in diode mode on U301 pins to verify connectivity; a reading below 0.2V suggests a short, while no continuity points to a broken trace.
For charging malfunctions, measure BQ25895 output on CHG_VBUS and BAT_CONN. A floating voltage (below 3.7V) typically means an issue with the Type-C port (J1001) or damaged U1801 charger IC. Inspect R1802 (0.01Ω shunt resistor) for burns–replacing it resolves sudden charging drops. If PP5V0_USB is absent, check Q1802 (AP2280) for gate voltage leakage.
Overheating near the SDM845 SoC often stems from failed C4302-C4305 (1μF caps) on AVDD18_SOC. Replace them if ESR exceeds 2Ω. Audio distortion? Test WCD9340 codec (U2501) pins 6-9–silence or noise confirms a dry joint or corrupt firmware in the DSP stack. For SIM detection errors, resolder U303 (SIM MUX); intermittent signals usually trace back to cold solder on SIM_DET lines.