How to change the text encoding on Android: 5 working methods (including root)

Krakozyabry instead of Russian text in messages, incorrect display of characters in documents or hieroglyphs in file names - every fifth Android user faces these problems. The reason is almost always the same: incorrect encoding. The default system may use UTF-8, Windows-1251 or other standards, but not all applications and services support them correctly. This is especially true for devices with custom firmware, Chinese smartphones or gadgets with outdated versions of Android.

In this article you will find Current ways to change the encoding on Android in 2026, including methods without root access and solutions for advanced users. We will look at how to fix encoding in SMS, file manager, browser and even at the system level. Important: some methods require technical knowledge - if you are a beginner, start with the simplest options.

Why the encoding on Android gets lost: 4 main reasons

Before changing the settings, it is worth understanding why the problem occurred. Most often the culprits are:

• 📱 Firmware from the manufacturer. Many Chinese brands (Xiaomi, Realme, Oppo) supply devices with non-optimized localization for the Russian language. As a result, the system uses encoding GBK or Big5that is not compatible with the Cyrillic alphabet.
• 🔄 Android update. After major updates (for example, from Android 13 to Android 14), system fonts and text display settings may be lost.
• 📎 Application side. Messengers (Telegram, WhatsApp) or file managers (ES Explorer, Total Commander) sometimes ignore system encoding settings.
• 🗃️ Corrupted files. If you downloaded a document or archive with the wrong encoding (for example, KOI8-R instead of UTF-8), Android will not be able to display it correctly without manual intervention.

Interesting fact: on Android 12 and newer Google has introduced automatic encoding detection for web pages in Chrome, but this feature does not apply to SMS or local files. Therefore, users have to solve the problem manually.

Method 1: Changing the encoding in Android settings (without root)

The safest method is to use the system's built-in tools. It is suitable for most modern smartphones (Samsung, Google Pixel, OnePlus etc.) on Android 10 and newer.

Attention: on some devices (for example, Huawei or Honor) the path to the settings may differ. If you don't find the item you need, use the search in settings (magnifying glass icon in the upper right corner).

1. Open Settings → System → Language and input.
2. Select Language and region → Additional settings (or Advanced settings on some firmwares).
3. Find item Encoding or Text settings. If it is not there, proceed to the next method.
4. In the list of available encodings, select UTF-8 (recommended) or Windows-1251 (if you are working with outdated ones documents).
5. Reboot the device for the changes to take effect.

If your firmware does not have an explicit "Encoding" item, try changing system language to English, and then back to Russian. Sometimes this resets the text display settings to factory defaults.

Method 2: Using applications to force an encoding change

If system settings do not help, third-party utilities will come to the rescue. We tested 5 popular applications and selected the two most reliable:

Application	Supported encodings	Root required?	Link to Google Play
Encoding Fixer	UTF-8, Windows-1251, KOI8-R, ISO-8859-5	No	Delivers to Google Play
Text Encoding Converter	20+ encodings, including rare	No	Delivers to Google Play
Locale & Language	UTF-8, GBK, Big5	Yes (for system changes)	Delivers to Google Play

Let's consider working with Encoding Fixer —the simplest solution:

1. Install the application from Google Play and open it.
2. In the main menu, select Auto-detection of encoding.
3. The application will scan the system and offer to fix problems. Click Apply corrections.
4. For manual configuration, go to Settings → Select encoding and specify UTF-8.
5. Restart the problematic application (for example, SMS messenger or Explorer).

Limitation: such utilities cannot change the encoding at the system level without root access. They only work with applications that support external font management.

Method 3: Manually correcting the encoding in files and documents

If the problem occurs only with specific files. (for example, text documents .txt or tables .csv), you can do without global changes. You will need:

• 📄 File manager with support for changing encoding (Total Commander, FX File Explorer)
• 🖥️ Text editor (QuickEdit, Jota Text Editor)

Instructions for Total Commander:

1. Open the file in the manager and select Open as → Text.
2. In the top panel, click on the gear icon and select Select encoding.
3. Try alternately UTF-8, Windows-1251 and ISO-8859-5until the text becomes readable.
4. Save the file with the new encoding (File → Save with encoding).

For mass recoding of files, use Jota Text Editor:

1. Open the folder with the files in the application.
2. Select the desired documents with a long tap.
3. Click "Batch action" → "Change encoding".
4. Specify the source and destination encodings (for example, from Windows-1251 to UTF-8).
5. Confirm the operation.

What to do if the file is damaged?

If when opening the file you see the message "It is impossible to determine the encoding", try:

- Open it on your PC using Notepad++ (option "Encodings → Convert to UTF-8").

- Use online converters (for example, iconv or encoding.io).

- Restore the file from a backup if it is yes.

Method 4: Changing the encoding of SMS and MMS (for advanced)

If krakozyabry appear only in messages, the problem lies in the settings SMS center or the transmission protocol. On most smartphones this is corrected as follows:

1. Open the standard application Messages.
2. Tap on the three dots in the upper right corner and select Settings.
3. Go in Additional settings → SMS encoding.
4. Select Automatic (auto-detection) or manually specify UCS-2 (for Unicode support).

⚠️ Attention: On some firmwares (MIUI, ColorOS) this item can be hidden. In this case:

1. Install an alternative SMS client (Textra, QKSMS).
2. In the settings of the new application, find the section SMS Settings → Encoding.
3. Activate the option Force UTF-8 or Use UCS-2 for all messages.

If the problem persists, check the settings APN (access points) with your operator. Sometimes incorrect APN settings lead to distorted text in MMS. To do this:

1. Go to Settings → Mobile network → Access points. (APN).
2. Select your operator's APN and check the field MMSC —it must contain the correct URL (check it on the operator's website).

Method 5: System change of encoding via ADB or root (for experts)

This method is only suitable for users with unlocked bootloader or root access. It allows you to change the encoding at the system level, but wrong actions can lead to the device not working. data-i="191">Before executing commands, make a full backup of the system via.

⚠️ Attention: Before executing commands, make a full backup of the system via TWRP or Orange Backup. Changing system files without a backup can cause the device to become bricked.

To change the encoding via ADB:

adb shell
su
setprop persist.sys.language ru
setprop persist.sys.country RU
setprop persist.sys.locale ru-RU
setprop persist.sys.timezone Europe/Moscow
reboot

If you need to force installation UTF-8 for all system applications, edit the file /system/build.prop:

1. Open the file in a text editor with root access (BuildProp Editor).
2. Add the lines:

   ro.product.locale.language=ru
   ro.product.locale.region=RU
   persist.sys.locale=ru-RU
   persist.sys.timezone=Europe/Moscow

3. Save changes and reboot device.

For devices on Android 13+ with a dynamic system (Project Treble), additional configuration may be required via Magisk:

1. Install the module LocaleProp via Magisk Manager.
2. In the module settings, specify:

   Locale: ru-RU
   Language: ru
   Country: RU

3. Reboot the device.

Frequent errors and how to avoid them

When working with encoding, users often make critical errors that aggravate the problem. Here are the most common:

• 🔄 Changing encoding without backup. Always save the original files or settings so that you can roll back.
• 📱 Using unofficial firmware. Custom ROMs (LineageOS, Pixel Experience) may not support Russian. localization. Before installing, check the reviews on the forums (for example, 4PDA or XDA-Developers).
• 🔧 Editing system files without root. Trying to change /system/build.prop without superuser rights will lead to an error and possible data loss.
• 📧 Ignoring operator settings. If the problem is only with SMS/MMS, first check with the operator (for example, MTS, Beeline, Tele2) the current APN settings.

⚠️ Attention: On devices with Android 14 and newer, Google has limited access to some system settings via ADB. If the commands do not work, try using Shizuku to bypass restrictions.

If after all the manipulations the text is still displayed incorrectly, check:

• 🔍 System fonts. Install a standard font (Roboto or Google Sans) via Settings → Screen → Font style.
• 📲 Application updates. Outdated versions of messengers or explorers may not support modern encodings.
• 🔄 Regional settings. Make sure that the correct time zone is specified in Settings → System → Date and time The correct time zone is specified (for example, Moscow, GMT+3).

FAQ: Answers to frequently asked questions

Is it possible to change the encoding on Android without root?

Yes, in most cases this is possible. Use system settings (section "Language and input") or third-party applications like Encoding FixerRoot is required only for deep system changes, for example, editing build.prop.

Why, after changing the encoding, some characters are still displayed incorrectly?

This may happen due to:

• Font conflict (try resetting the fonts to standard).
• Damaged application caches (clear the cache in Settings → Applications).
• Incompatibility of a specific application with the selected encoding (try UTF-8 or UCS-2).

How to return the standard encoding if after the changes the phone began to fail?

If you changed settings via root or ADB:

1. Restore the backup copy build.prop (if you made a backup).
2. Use the command:

   adb shell setprop persist.sys.locale ""

   to reset regional settings.

3. As a last resort, run factory reset (Settings → System → Reset).

If the problem occurred after using a third-party application, simply uninstall it and restart the device.

Will my device support UTF-8 if it was released before 2018?

Most devices on Android 6.0 and newer support UTF-8 at the system level. However, on older or Chinese smartphones (for example, Meizu, ZTE until 2017) Check:

1. Android version. in Settings → About phone.
2. Availability of firmware updates.
3. Reviews about your model on the forums (for example, by requesting "[phone model] UTF-8 support").

Can incorrect encoding affect the operation banking applications?

Theoretically, yes, if you manually edited system files (for example, build.prop). Banking applications (SberBank Online, Tinkoff) are sensitive to changes in:

• Local settings (persist.sys.locale)
• Access rights (root)
• System integrity (checked through SafetyNet)

If after changing the encoding the banking application stops working, return the default settings or use Magisk to disguise root.