Xiaomi Redmi magazine generator: detailed guide to use and set up

If your Xiaomi Redmi smartphone starts to slow down, overheat or suddenly discharge, the first thing experts recommend is to collect system logs (logs). These files contain detailed information about the operation of the device, from application errors to malfunctions in the iron part. But how do you get them if the phone doesn't turn on or isn't working well? Here comes the built-in log generator -- a hidden feature. MIUI, Which is not known to all users.

In this article, we will discuss in detail what a log generator on Xiaomi Redmi, how to activate it in different scenarios (including “bricks” and freezes), what data it collects, and how these logs can help in diagnosis or repair. Particular attention will be paid to the unique feature of Xiaomi: the ability to collect logs even with a locked bootloader, which distinguishes the brand from competitors.

What is a magazine generator and why you need it

Log generator is a built-in tool in firmware MIUI, It automatically collects system logs when critical errors occur, as opposed to manually collecting through a system log. ADB Or apps like MatLog, which works at a low level and captures data even when the smartphone does not respond to touch.

The main tasks of the generator:

• 🔍 Diagnostics of hardware failures: fixes errors of the processor, memory, battery or communication module.
• 🐞 Filling software bugs: Records system process crashes (e.g, system_server mediaserver).
• 🔧 Repair assistance: Service centers request logs to accurately determine the cause of the malfunction.
• 📱 Performance analysis: Shows which applications or services are overloading the system.

It's important to understand that a log generator is not the same as standard Android logs. It collects advanced telemetry, including:

• 📊 Data from sensors (temperature, accelerometer, gyroscope).
• 🔋 Information on battery charging/discharge in 1 second increments.
• 📶 Logs of Wi-Fi modules, Bluetooth, GPS and cellular.
• 🖥️ Status of processor cores and graphics accelerator.

⚠️ Note: On Redmi models with MediaTek processors (e.g. Redmi Note 11 or Redmi) 10C) The log generator can collect data about the radio part (modem logs), which are not available on smartphones with Qualcomm.

How to turn on the magazine generator on your working smartphone

If your Xiaomi Redmi is turned on and reacts to touch, you can activate log collection through a hidden menu of engineering settings. MIUI 12–14.

Step instructions:

1. Open the Phone app and enter the combination: ##4636##.
2. In the menu that appears, select Phone Information (or Phone Information).
3. Scroll down and find the option to Enable Log Collection (or Enable Log Collection).
4. Confirm the action and restart the device.

Once rebooted, logs will be collected in the background to retrieve them:

1. Connect your smartphone to your PC via USB (file transfer mode).
2. Go to the file. /sdcard/MIUI/debug_log.
3. Copy files with the.zip or.log extension.

Enable debugging over USB in the developer settings

Make sure there is enough space on your phone (minimum 500MB)

Connect the original USB-cable

Start collecting logs 10-15 minutes before the problem occurs

-->

On some models (e.g. Redmi) K50 or Redmi Note 12 Pro+) The path may be different. debug_log missing, check the directory /sdcard/log or use ADB-team:

adb pull /data/logs/

⚠️ Attention: Logs take up a lot of space — up to 1-2 GB per hour of active collection. Before you start, delete unnecessary files or transfer them to a memory card. On models with 128 GB of memory and less, this can lead to freezes.

Collect logs on a locked or broken phone

If Xiaomi Redmi does not turn on, hovers on the logo or went into the “brick”, the magazine generator can still be activated via Fastboot mode or EDL (This method requires a PC and special tools.

For smartphones on Qualcomm (most flagship Redmi, for example, Redmi) K60):

1. Turn off the phone (if it freezes, press the power) + Volume Down for 10-15 seconds).
2. Press Volume Down + Power to log in to Fastboot.
3. Connect the device to the PC and start the command: fastboot oem bg_dml 1 This will include collecting logs in the background.
4. Wait for the next crash and extract the logs by the command: fastboot oem bg_dml 0 fastboot getvar log

For devices on MediaTek (e.g., Redmi) 10A or Redmi 9C):

1. Log in to Fastboot (similar to paragraph 2 above).
2. Use the utility. MTK Client or SP Flash Tool for reading logs through the Preloader port.
3. V SP Flash Tool select Readback and specify the memory address with logs (usually 0x7800000 MediaTek).

For models with unlocked loader can be used ADB even in the "brick" state":

adb shell


su




logcat -d > /sdcard/bootloop_log.txt

Analysis of collected logs: what to pay attention to

Log files from Xiaomi generator have a specific structure, let’s look at the key sections and what they mean:

For log analysis, you can use:

• 🖥️ Notepad++ Compare plugin (to find differences between logs before/after a crash).
• 🔍 Logcat Reader (Android app, makes it easier to read logcat).
• 📊 Excel/Google Sheets (for thermal logs or battery data visualization).

Examples of critical errors that should be noted:

• 🔥 kernel: CPU1: Thermal shutdown – emergency shutdown due to overheating.
• 🔋 Battery: voltage drop to 2.8V — Deep battery discharge (may damage the controller).
• 📵 RIL: SIM Not detected - a problem with the slot SIM-map.
• 🖥️ E/MiuiCamera: open failed: -19 — Camera failure (possibly hardware).

💡

If there is a line in the logs WCNSS_FILTER: Fatal error, which indicates a problem with Wi-Fi/Bluetooth-On Redmi models with Qualcomm, this is often solved by flashing. WCNSS_qcom.cfg through QPST.

Common Mistakes and How to Avoid Them

When working with a log generator, users often encounter typical problems that prevent proper data collection.

1. Logs are not stored or empty

Reasons:

• 🚫 Lack of space on the internal drive (needs at least 1 GB of free space).
• 🔌 Log collection interrupted due to power outage (always use the charger).
• 🔧 On some models (Redmi 9, Redmi) 8A) Manually enable the Persist.logd option via ADB: adb shell setprop persist.logd.logpersistd true

2 Logs are collected but not opened

Decisions:

• 📁.zip files can be corrupted – try unpacking them through 7-Zip.
• 📄 For.dmesg, use Linux editors (like Vim or Nano) as Windows may not display characters correctly.
• 🔍 If logs are in Chinese, use Google Translate with file download ("Translate document" function").

3. The log generator is not included through the code

Alternative methods:

• 📱 On some firmware (MIUI Global) code ##4636## blocked. Use ##284### (equipment test) → Log Test.
• 🖥️ For Redmi on Android 13+ Enable the collection of logs through ADB: adb shell am broadcast -a com.miui.intent.action.LOG_COLLECTION --ez enable true

⚠️ Note: On Redmi models with HyperOS (e.g. Redmi) K70) Standard log collection methods may not work, in which case use the Mi Flash Tool in mode. EDL with the option of Save logs.

From the Engineering Menu (#4636##)

With ADB

In Fastboot mode

I never collected logs.

Another way.-->

How to transfer logs to Xiaomi Service Center

If you use the official Xiaomi service (for example, under warranty), the collected logs will significantly speed up the diagnosis.

File requirements:

• 📂 Archive logs in.zip without password (use file name in format) Redmi_Date Date.zip model, for example, Redmi_Note11_20260515.zip).
• 📝 Attach a text file description.txt describing the problem (when it occurred, under what conditions, what have already tried to do).
• 📸 If the problem is with the screen or camera, add a photo/video defect.

Where to send:

• 📧 By e-mail: support@mi.com (Please enter the order number from the service center).
• 🌐 Using the feedback form on the Xiaomi Support website (select Repair category).
• 📱 In the chatbot Mi Assistant (in the Mi Community app) → Support → Chat).

Example of archive structure:

Redmi_Note12Pro_20260515.zip




├── logs/




│   ├── kernel_dmesg.log




│   ├── bugreport.zip




│   └── thermal_data.csv




├── description.txt




└── screenshots/




├── overheat.jpg




└── battery_drain.png

Xiaomi service centers in Russia and CIS usually request logs in the following cases:

• 🔋 Suddenly shutting down the phone when charging >30%.
• 📶 Loss of network or inability to register on the network.
• 🖥️ Logo hangings MIUI cyclic.
• 🎮 Artifacts on the screen or graphics failures in games.

💡

If the service center refuses to accept logs by e-mail, insist on writing in paper form - according to paragraph 4.2 of the Xiaomi regulations, the customer has the right to provide diagnostic data in any convenient way.

Alternative Diagnostics without a Log Generator

If the log generator is not available (e.g. on custom firmware or after reset), alternative tools can be used:

Applications for collecting logs

• 📱 MatLog (free, collects logcat in real time).
• 🔍 Logcat Extreme (paid version, supports filters and export to the UK) CSV).
• 📊 CPU Monitor (tracks processor load and temperature).

2. Integrated equipment tests

Dial in the phone application:

• ##6484## - Test MTK (MediaTek).
• #64663## is a Qualcomm test.
• ##4636## → Battery Information - Battery Information.

3. Analysis via PC

• 🖥️ QPST (Qualcomm allows you to read modem logs and EFUSE.
• 🔧 MTK Droid Tools – for smartphones on MediaTek (collection of preloader logs).
• 📡 Wireshark – Network Traffic Analysis (useful for diagnosing Wi-Fi or mobile internet problems).

For a deep diagnosis of hardware problems (such as motherboard malfunctions), use a multimeter or an oscilloscope, such as checking the voltage at the battery contacts:

• 🔋 Norma: 3.7V–4.2V.
• ⚠️ Critical: below 3.0V (It may indicate a failure of the power controller).

FAQ: Frequent questions about the magazine generator on Xiaomi Redmi