The most productive firmware for Android. Ten best Android firmwares for the most demanding users

In our articles and in the book, we wrote a lot about the basics of Android security, authentication methods and data extraction. However, everything that we wrote earlier applied exclusively to devices running original software - firmware - developed directly by the device manufacturer. About 98% of devices run on firmware from the manufacturer of one version or another.

There remains a relatively small layer of enthusiasts who like to experiment with their devices and install third-party firmware. Why do users need this, in addition to satisfying the curiosity of the researcher, what are the types and advantages of third-party firmware, what is the security situation in them and how to extract data from them - in this article.

Possibility of installing third-party firmware

The vast majority of Android users have no choice: all major manufacturers block the device's bootloader, which completely negates any attempts to modify the pre-installed software.

Locking the bootloader can be a company policy in general or in relation to a specific device (for example, LG locks the bootloader on the LG G Flex 2 smartphone, but allows users to unlock the lock on some LG G4 models).

Locking the bootloader can also be a requirement of the operator: most American operators require manufacturers to block the bootloaders of devices that will be sold through operator retail. These requirements may be more or less stringent; Thus, for the first generation Motorola Moto G model, official bootloader unlocking is available for all models except those sold by the Verizon operator.

At the same time, many devices that are sold as unlocked and "international" versions allow users to unlock the bootloader and install third-party firmware. This is especially true for devices that users order from China: all these OnePlus, Xiaomi, Oppo, UMI, Elephone, Vernee, LeEco, ZUK and dozens, if not hundreds of others, come either with already unlocked bootloaders, or allow them to be unlocked with one or another degree of difficulty.

In fact, to install third-party firmware you don’t need anything other than an unlocked bootloader and a third-party recovery for the device - for example, TWRP. Third-party firmware is quite possible even without source code, which manufacturers are supposed to publish under the GPL license. More on this below.

Types of third-party firmware

For many popular models, the enthusiast user will have a choice: stay on the firmware from the manufacturer or install one or another third-party assembly. What are the differences between different types of firmware? Let's try to figure it out.

1. All devices, even those coming from China, will always have some kind of firmware from the manufacturer. As a rule, there is not even one: different versions (by numbers), versions for different regions, sometimes versions for different hardware versions of the device. Sometimes there are firmware for the domestic Chinese market (without Google certification) and firmware for other markets (India, Russia, international) with certification, which, in particular, often introduces mandatory encryption of the data section. These firmwares can differ greatly from each other, to the point that installing the wrong version disables the device. This is the so-called “stock” (stock ROM), “stock firmware”.
   • A variation of the “stock” firmware is the so-called “shop ROM”, or firmware that is installed by Chinese stores. During the installation process, stores add Google services (but not certification) and activate additional languages. Very often, “store-bought” firmware also contains malicious software – spyware and adware modules. By definition, no updates are provided for such firmware; An attempt to install OTA leads to an error or completely disables the device (personal experience). Despite this, a significant percentage of Chinese device buyers use store-bought firmware.
2. If we talk about Chinese firmware on devices supplied to foreign markets, they will usually have a lot of unnecessary stuff, but will not have vital software (for example, there is no Google Play Services). Accordingly, the first type of third-party firmware is the usual modification of the firmware from the manufacturer: removing what is unnecessary, adding what is needed. Since everyone has different concepts of “extra” and “needed,” there are several modified ones for each version of the manufacturer’s firmware. These are the so-called “mods”, modified firmware from the manufacturer. As a rule, nothing global changes in such firmware; the user interface and security features most often remain unchanged. If we are talking about firmware for Google-certified devices (Nexus, Motorola, etc.), then they are often offered as modified firmware in which mandatory encryption of the data section is disabled.
3. A deeper modification of the firmware from the manufacturer implies a global replacement of the functionality and interface of the firmware based on the stock one. In this case, all system drivers and some part of system applications remain, but some elements of the framework and UI, as well as many system applications (dialer, contacts, camera, etc.) may change. This achieves a radically different appearance and UX, but All this functions on the basis of the same drivers as the firmware from the manufacturer. As a rule, such firmware provides fairly good compatibility with the device hardware (since they are based on the same drivers). This is the so-called patchrom. For example, for many devices the MIUI firmware family is done in this way.
4. The third stage of development is independent firmware (Cyanogen, Lineage and many others), which is compiled from source codes. In this case, the kernel, in which all the drivers are built in, as well as part of the system libraries and frameworks, is taken from stock. At this stage, a wide variety of problems are possible (and often happen) - with compatibility, with support for certain hardware components (most often the camera and non-standard sensors suffer - for example, a built-in infrared port with a remote control), with overheating, with unexpected battery consumption and etc. This category of firmware does not have its own name; it is already a full-fledged custom ROM; for many devices, this is where the developers’ options end (in particular, for many models on MediaTek processors, for which source codes are often unavailable).
5. Finally, the last, most interesting stage is firmware compiled from source codes after the manufacturer publishes the kernel source codes. The kernel includes all the necessary drivers, they are available in the form of blobs (BLOB - Binary Large OBject). Based on the kernel source codes, the development team (often the only developer, maintainer) creates a so-called “device tree”, which contains everything that relates not to Android as a whole, but to a specific device. Such firmware is the most interesting, as it can radically change the behavior and functioning of the device. In such firmware, developers can add features at the kernel level (for example, managing screen color profiles, support for exFAT file systems, NTFS for memory cards, support for network file systems, etc.). In such firmware, you can assemble your own kernel with what is needed specifically for this firmware, and everything works (more precisely, it should work) properly. Such firmware still uses some proprietary components (drivers supplied by the chipset manufacturer).
6. The icing on the cake is firmware built using open source drivers. For example, drivers for some models of audio path and graphics accelerators exist in the form of source codes that can be rebuilt, optimized and used in the firmware. Based on them, you can try to replace the blobs from the manufacturer with your own, made based on open sources. Device manufacturers (for example, Qualcomm) are not required to provide the source codes of their drivers, limiting themselves to blobs. But if such codes are found, then it becomes possible, for example, to build firmware on Android 7.1 for devices on which this version of Android is not officially supported. Unfortunately, open source drivers are often worse than proprietary ones (worse sound quality, lack of support for some APIs, and so on). Overall, this is a double-edged sword.
7. Firmware based on alternative operating systems stands out: Tizen, Ubuntu Touch, Sailfish. We will not consider them in this article.

Some vendors, especially third-tier vendors, encourage third-party development by open sourcing the kernel code immediately, completely, and without deliberately introducing bugs. Very often, such manufacturers (for example, OnePlus) officially support developers. Larger manufacturers cannot boast of such an attitude, so third-party firmware for such models may appear with long delays.

Brief overview of popular third-party firmware

It is impossible to talk about the widespread use of third-party firmware; they are the lot of enthusiasts, whose share among the Android user community does not exceed 1-2%. But even here there is no uniformity; There are firmwares for every taste and pocket.

What third-party firmware are the most popular? Firmware based on “mods” - for example, from the Cuoco92 team. Patchrom – MIUI, FlyUI. Firmware compiled from source codes - Cyanogen (currently Lineage) and firmware based on it. Let's take a closer look at the latter.

Until recently, third-party firmware was assembled by developers either based on AOSP (Android Open Source Project, that same semi-mythical “pure” Android) or based on Cyanogen. Recently, firmware based on AOSP is becoming less and less, and firmware based on Cyanogen (Lineage) is becoming more and more numerous.

The only AOSP-based firmware that I can think of is Omni ROM. Pure Android with a few but very useful additions (for example, a “night” mode that lowers the color temperature of the screen in the evening and at night). There is no riot of unnecessary settings, even more so; The interface is made in a strict Android style. The firmware is energy efficient and highly optimized. There is no built-in root access (but it is possible to install it additionally), the SELinux context is enforcing.

The most popular alternative is Cyanogen (lately Lineage OS, builds are only available for devices running Android 6.0 and 7.1). The appearance is pure Android, the additional features are minimal, but useful. Optimization is excellent, energy efficiency is also excellent. The Lineage development community tries to use open source drivers whenever possible, often at the expense of performance and functionality. Root access in Cyanogen firmware was available normally through the Developer Options menu; in Lineage firmware, you need to download and install an additional module via recovery (which is more correct from the point of view of overall system security).

It is on the basis of Lineage source codes that most of the alternative firmwares are assembled today. Let us briefly consider the features of some of them.

• Resurrection Remix– a popular firmware among enthusiasts with a maximum (for many, excessive) number of settings. Refers to “heavy” firmware. Energy efficiency on our test devices is low, but performance is high. Built-in root access via Developer Options, SELinux context – permissive. A colorful animated logo, many settings, and a general attitude towards security classify this project as a “hacker” firmware.
• AOKP– can be considered as a kind of spin-off or continuation of Resurrection Remix. Lots of settings, high performance, greater energy efficiency compared to RR (note that this applies to our test devices). Built-in root access via Developer Options, SELinux context – permissive. Perhaps another “hacker” firmware.
• AICP also has many settings, and root access built into Developer Options. An interesting point is that the SELinux context can be switched normally in the same Developer Options. Another interesting point is that root access is built-in, and the Magisk application is used for management, with which you can both control the assignment of privileges and hide the very fact of having root access from selected applications (for example, banking programs that often refuse to work on devices with root). Color animations, children's drawings on standard screens (for example, the picture that appears on the multitasking screen after clearing all applications), built-in root access and the ability to hide it, as well as a fairly free vocabulary (typical menu item names: Panel porn, Other shit) allow We are confident in classifying the firmware as “hacker”.
• Mokee is a popular project, this time from Chinese developers. There is no built-in root access, the SELinux context is enforcing, the strict design, the absence of a million settings and the polished performance of the existing ones put Mokee on par with Lineage OS firmware, on whose source code it is based. Energy efficiency and productivity are high. It is interesting because of the Aegis application integrated into the system, which allows the user to selectively disable services and wakelocks and applications, including system ones.
• crDroid– another project based on the Cyanogen/Lineage source codes. The firmware differs little from Lineage as such and is based on the same basic principles: the cleanest Android possible, a minimum of settings with maximum performance, high energy efficiency and performance. The SELinux context is enforcing, there is no built-in root access, it is available through the firmware of an additional module.
• Dirty Unicorn– another interesting and popular project. We have no experience using this firmware, but we can’t help but mention it.

Of course, there are other third-party firmwares: OctaOS, XenonHD, DarkNess-reDefined, Validus OS and many, many others. It is not possible to consider them all.

Root access in third-party firmware

From a brief review of third-party firmware, we can draw only one conclusion: the attitude towards root access is implemented differently in all firmwares. In some places it is not available at all (but you can flash SuperSU via TWRP), in others it is available via the firmware of an additional module (Lineage), in others the root access control mechanism built into the firmware is used, and in others solutions (Magisk) are used that allow how to manage root access and hide the fact of its presence from some applications.

In order to extract user data with a third-party recovery (TWRP), root access is usually not needed. It can be useful, for example, to extract a complete image of a data partition along with unallocated blocks. In TWRP, this option is available only for the system partition, but not for the data partition. This may make it possible to recover deleted files.

Third Party Firmware Security and Data Extraction Methods

We come to the final part of the article, to what it was written for: the ability to extract user data from devices running third-party firmware.

You may like the way your smartphone's interface looks and works, but other ROMs give you the opportunity to explore new design and interface options. They may also offer new functionality. If you're interested, read on.

The best custom firmware

Good firmware has a community of users who support it and works on different device models. Unfortunately, fewer and fewer third-party downloaders meet these requirements. Those who want to keep their old Nexus 5 smartphones up to date or have few installation options. If your device requires a better user interface, less bloatware, and faster software updates, you should consider installing custom firmware.

LineageOS (formerly CyanogenMod)

Numerous fans had to say goodbye to the popular CyanogenMod firmware and all its functionality. It was great for beginners, as Wikipedia offered an extensive description of the features. It was replaced by Lineage firmware, which also has its own Wiki.

Lineage has a compact bootloader, a functional application for working with the camera and a number of pre-installed programs that take up a small amount of memory. There are sound profiles that make it possible to mute the sound or make the smartphone louder under certain conditions. Privacy settings send incorrect data to elevated apps to mislead them. The main thing is that Lineage allows old smartphones to become fast again.

This firmware was created for Nexus devices, some and . The functions here are similar to Lineage, root rights are given, there are regular security and stability updates.

A wide range of devices is supported, updates are released with enviable regularity. Multitasking is possible thanks to OmniSwitch. Dirty Tweaks contains important settings that are not found in stock Android.

SlimROMs

A stripped-down version of Android allows the user to choose which part of Google Play services he needs. It also allows you to modify the DPI of fonts and icons, you can make everything tiny. Currently, about 50 device models are supported.

An alpha version of the build on Android Lollipop has been released, development here is not going very quickly.

Other firmware

Positioned as an all-in-one solution. The developers shamelessly copy functionality from other firmware from this list, including OmniSwitch and CyanogenMod's Pie controls, combining them into their own product.

So, this firmware may lack some personality, but if you're looking for a highly customizable option, this is it. The loading animation deserves special praise. More than 50 devices available.

This firmware first appeared in early 2013 based on Android Jelly Bean. There's no radical design change here, but the few changes are quite effective, including in notifications and navigation.

Immersive mode allows you to see information on the screen by hiding the status bar, a system of dynamic panels combines status and navigation. This increases the external attractiveness of the system.

In early 2015, OnePlus hired a number of key employees from Paranoid Android. As a result, the project was frozen, one of the developers left, and another denied this information. Whether this project will be revived or not is unknown.

Paranoid Android can be installed on a variety of devices, including the Nexus line and OnePlus One.

Description of custom firmware

Firmware is a build of the operating system that runs on the device with basic applications such as address book, calendar, camera, etc. The main advantage of Android smartphones is that they can work on third-party systems and not only with original firmware. Custom firmware replaces the pre-installed version of Android. The replacements are various variations of AOSP from volunteer developers with a lot of free time.

What is AOSP

This abbreviation translates as Android Open Source Program. This is Google's open source version of Android and is available to everyone. Developers can change it without having to follow Google's standards and install its apps.

Thanks to this project, such firmware as CyanogenMod, Paranoid Android, MIUI appeared.

Advantages: Should I install custom firmware?

Many owners of Android devices are aware of the problem: the device is only a year old, and manufacturers are no longer going to update it. New versions of Android are interesting not only because of the expanded functionality, but also because of the security updates.

Third-party firmware uses official Google code and compatible smartphone drivers. This allows you to update the system to the latest version. Often, custom firmware is updated more often than original Android.

The smartphone is getting faster

One of the main advantages of custom firmware. Manufacturer-installed graphic themes and applications are almost absent here. This saves memory and increases speed.

Customization

Custom ROMs not only bring the latest version of Android, but also provide extensive customization options. The possibilities are almost limitless.

By rooting, you get full access to all features of the device. In the original version of Android, some functions are hidden. The modified firmware gives unlimited access to all the capabilities of the smartphone. It's also easier to back up.

Ideal for lovers of clean versions

Since custom ROMs are based on the Android Open Source Project, they have more features and suitable drivers from the developers of these ROMs. If you buy non-stock Android smartphones, such as Samsung, you can still get stock Android.

Compatibility b: is there firmware for my device?

The answer to this question must be sought on forums on the Internet. There you will find a list of devices supported by a specific firmware and tips for updating.

Disadvantages of custom firmware

Before you decide on the difficult process of installing firmware, you should know about their disadvantages.

• Loss of warranty
  If your devices are still under warranty, installing custom firmware may invalidate it. Many manufacturers are patient with changes to the device's operating system. One of them is Xiaomi.
• Difficulty of installation
  Custom firmware is well suited for those who like complex tasks. If this does not apply to you, it is better not to install the firmware. Updates, rooting and version instability can quickly get boring.
• Google App Lack
  There are few Google programs in third-party firmware. Play Store apps will have to be reinstalled. Google programs can be found at .

Conclusion: to put or not

Custom firmware can be a salvation for old smartphones and tablets. They can also rid new devices of bloatware. They often improve speed and add features. However, this is not an easy process, especially for beginners. It's made easier by firmwares like LineageOS and a large number of CyanogenMod users who can provide hints.

The easiest way to seriously update your gadget is to install custom firmware on it. With it, you can not only expand the number of controls over the system, but also try something new, get many convenient features or even a new version of Android. In this article I will talk about the ten most popular, interesting and functional firmware created on the basis of Android.

Paranoid Android

Harvesters

Temasek's

MK (MoKee)

The interface is truly original. Absolutely all standard Android applications have been replaced with applications of our own, and the rest have been significantly improved. The notification panel has quick toggles that appear above notifications. The “Energy Consumption” section has been renamed to “Power Management” and is much more convenient and informative; the “Network Modes” button allows you to enable the “3G Only” and “2G Only” modes.

There are no complaints about the speed of the graphical shell. Everything is very fast and smooth. It is worth saying that the firmware has an interesting permission management mechanism built into it. It allows you to limit significantly more parameters than Android Marshmallow. The settings interface and almost all system applications are completely Russified. But in all applications that work via the Internet, you will see only Chinese characters, but the method of scientific poking and knowledge of how such applications work allows you to use them.

The Chinese equivalent of the Play Store has almost all popular (and not so popular) applications. But Google programs will refuse to work without Google Play services, and installing these services is not so easy. There is a solution to the problem on the Internet, but it does not always work; you will have to use either the built-in market or various unofficial stores, and also come to terms with the fact that some applications will not start without Google Services.

Dropped out of the test

Bliss

Official site: blissroms.com/
48 (as of 08/13/2016)
The basis: CyanogenMod
Android Version: 6.0.1

The developers claim that Bliss is one of the most customizable tailoring. Actually this is not true. The firmware is indeed a collection of interesting features from other firmwares, but it is very far from RR, AICP or Temasek. Unless they are initially built in and launched through the Kernel Adiutor and SuperSU settings. The settings of the firmware itself are not translated into Russian. The translation only applies to items that are in CyanogenMod.

crDroid

Official site: ww2.crdroid.org
Number of officially supported devices: 29 (as of 08/09/2016)
The basis: CyanogenMod
Android Version: 6.0.1

The purpose of creation, like everyone else, is to add the best features from other firmwares. On the welcome screen during initial setup it is written that the firmware includes a lot of functions from OmniROM, Paranoid Android, Temasek and others. Unfortunately, it's the same story as with Bliss. Lack of exclusive features and a significant lag in capabilities compared to RR, AICP, Temasek. There are no interesting applications built in.

Outside the test

• NexSense 6.0- an attempt to port HTC Sense 6.0 (Android 4.4.2) to Nexus 5. At first, only the firmware itself was launched, but over time, enthusiasts were able to get Wi-Fi, Bluetooth, GPS, and various sensors to work. But for a very long time this could not be achieved from the camera and sound. Over time, the developers came to the conclusion that it was necessary to rewrite some libraries almost from scratch. Local craftsmen seemed to have tried to do this, but to no avail.
• ASUS ZENUI CM 13 (Nightly) Based- a project to port applications from Asus ZenUI to CyanogenMod 13. Officially, development is carried out only for LG G2. According to the developers, about 90% of all applications have already been moved.
• MIUI- the firmware has been officially ported to 286 different devices. Developed by Xiaomi and based on the source codes of CyanogenMod and AOSP. Many features have migrated here from iOS, TouchWiz, UX (LG), HTC Sense, but there are also some of our own. There are so many useful functions that their description is a topic for a separate article.
• MaruOS- a very original firmware, which, when connecting a smartphone to a monitor, turns it into a full-fledged desktop. You can read a detailed review and interview with the developer.

How to install?

For most devices, the stock firmware looks like this:

1. Unlock the bootloader (this is individual for each device, so go ahead, Google).
2. Install a custom recovery (in rare cases, you can install custom ones without it, but this is not a good idea).
   2.1. We go to the official TWRP website, enter the name of your device there, and download the newest version for it.
   2.2. We connect the smartphone via USB and install drivers for your device on the computer.
   2.3. Download and install Android SDK.
   2.4. We launch the terminal and flash the recovery with the command fastboot flash recovery recovery_name.img (fastboot is located in the platform-tools folder inside the SDK).
3. After flashing the firmware, go to TWRP, select the Russian language (at the very bottom), check the “Allow changes” box and swipe to the right.
4. Go to the “Cleaning” section and select “Format Data”. This is necessary if the data section is encrypted.
5. We connect the smartphone to the computer and transfer the file with the new firmware to the memory card.
6. Select “Install”, and then the firmware file. We agree by swiping to the right.
7. Click on “Reboot into OS” and wait for the download to complete (about ten minutes, including application optimization).
8. After the initial setup, we recommend booting into recovery again and making backups. At a minimum, an EFS partition in which IMEI, s/n and other important data are embedded.

If you don’t want to lose the main firmware, you can install the custom one with a second system. The one-of-a-kind MultiROM Manager will help with this. It allows you to install multiple firmware at once. The device prompts you to select the firmware from the installed ones when you turn it on. Installing the program is quite simple (just don’t forget to make backup copies before doing so, just in case):

1. Install MultiROM Manager from the Play Store and launch it.
2. Click the “Install” button.
3. We wait for the installation to complete, and then agree to reboot.
4. After rebooting and installing some scripts, the firmware selection interface will open.

Installation of the second firmware is performed through MultiTWRP in the Advanced -> MultiROM section or through the application itself.

Dictionary

• Stock (stock, stock firmware)- official firmware, preinstalled by default by the manufacturer. Also, not only absolutely clean images of stock firmware are often called stock, but also images prepared for installation through unofficial recovery.
• AOSP (Android Open Source Project)- original Android source codes from Google, available for downloading and modification by anyone. The term “based on stock, based on AOSP” means that the firmware was compiled based on these sources (and not CyanogenMod sources, as is sometimes the case). Most Xposed modifications only work in AOSP/CyanogenMod and firmware based on them.
• CAF (Code Aurora Forum) is a project supported by the Linux Foundation that accelerates the advancement of open source in mobile technology. The main participant in the project is Qualcomm, which maintains the Android for MSM repository, which contains Android source code with optimizations for Qualcomm chips. If developers claim that their firmware is based on CAF, then it includes all these optimizations. But it is worth keeping in mind that changes from Android for MSM often flow into AOSP.
• CyanogenMod Based (CM based, based on CynogenMod)- firmware based on CyanogenMod code. Immediately after the release of a new version of AOSP, CyanogenMod developers copy its sources into their own repository and begin to implement their additions to it and port it to new devices. And the list of devices supported by CyanogenMod is such an impressive number that many developers of custom firmware choose it as a base, and not AOSP.
• Recovery (recovery mode, recovery)- Android recovery console. Designed to perform a factory reset or install a zip file of firmware signed with the manufacturer's key. For many devices, there are third-party recoveries with advanced functions, such as ClockworkMod, TWRP, Philz. They allow you to make full backups of both the entire system and individual parts, install third-party firmware, format and resize partitions, install any add-ons and much more useful things.
• Bootloader (bootloader, bootloader)- loaded first. It passes the partition table of the on-chip NAND memory to the kernel, loads it into memory and runs it. It is the bootloader that connects to the PC in fastboot mode and launches the recovery. Therefore, before installing custom recovery and often third-party firmware, it must be unlocked. Almost always, after unlocking the bootloader, absolutely all data is erased from the device’s memory.
• GApps (Google Apps)- a set of services and applications from Google. GApps packages come in various sizes, from the smallest (less than 100 MB), which include only Google Play and the services it runs, to large ones, which contain almost all existing Google applications (the size of such packages is approaching 800 MB). Many firmware developers recommend installing Open GApps. Differences between versions can be viewed in the Open GApps Wiki. Please be aware that some GApps may replace system applications.
• Nightly (“nightie”)- overnight firmware assembly. For many devices, assemblies are done daily (nightly). In theory, they have low stability, but in practice, unsuccessful builds are extremely rare, and bugs that pop up are fixed very quickly.

File system F2FS

Almost all custom firmware supports the F2FS file system, which is designed specifically for working with flash memory and, in theory, uses it more efficiently and more carefully than ext4. You can switch to this FS in the following way:

1. Login to TWRP.
   2.0. Open the item “Cleanup -> Custom Cleanup”.
   2.1. Check the Cache section.
   2.2. Click “Restore or change file system -> Change.” file system -> F2FS" and swipe to confirm.
   2.3. Press the "Home" button.
2. Repeat step 2 for the data and system sections.

Notes:

• Not all firmwares support F2FS. If there is no support, you will end up with endless loading.
• After changing the file system of the data partition, not only program data and firmware settings will be lost, but also files saved on the internal memory card.
• In practice, the performance gain will be a few percent at best.

Conclusion

We have not reviewed all existing firmware. However, even this is enough to have an idea about modern firmware. In terms of interface, they are almost all similar, they all work very smoothly, and it is very difficult to notice any differences in operating speed. But their functions are different. On my own behalf, I can add that if you spend a long time at least on MoKee, or especially Resurrection Remix, then you won’t even want to go back to pure CyanogenMod. But you will probably have to turn to Xposed for help. Fortunately, almost all existing custom ROMs work with almost any Xposed module.

The Android operating system has gained great popularity due to its simplicity and excellent developer support. At the same time, its distribution scheme is such that each device manufacturer must create its own version of the firmware. Moreover, for a specific model of phone or tablet. This article will discuss methods and flashers for Android via PC.

A little theory about what firmware is

First, it’s worth talking about what the firmware of any device is. This is a set of software to perform basic functions and for the operating system itself. Since Android versions are produced very often, and each device has its own set of equipment, there are a lot of firmware versions. Therefore, before changing the software, you need to find it specifically for your device.

Goals and objectives of flashing a device

Why might firmware be needed at all? There are many different answers to this question. For example, the device began to malfunction and behave incomprehensibly. Resetting to factory settings did not help, and then, as an option, you can reflash it. This is done if you are simply tired of the appearance of the menu and the functionality provided by the current version. It also happens that the manufacturer has stopped supporting this device software, and the current version of Android is no longer being developed.

Firmware can be either official, representing original images of the system installed by the manufacturer, or “custom”, that is, assembled by amateurs and enthusiasts. Installation of the latter is done at your own peril and risk, so you should carefully study the instructions and manuals.

Review of flashers for Android

Now let's talk in more detail about what it is. A flasher for Android is a special program or a set of programs that knows how a smartphone or tablet works and can install software into the required memory sections. We will look at some of these applications.

SP is probably the most famous flashing tool for Android. It is mainly focused on installing software on devices with MediaTek processors. Using the program can be described step by step:

1. Installing a device driver on a personal computer. This is necessary so that the SP Flash Tool can see and use the gadget correctly.
2. Find the required firmware for your phone version. At this stage you should be very careful, as there are many of them. And they can differ not only in date, but also in revisions of the smartphone or tablet.
3. After the firmware is found, you need to unpack it to a convenient place on your hard drive.
4. Now you need to run the Android flasher via PC SP Flash Tool. The main program window will open, in which all the action will take place.
5. There is a button on the right side of the window. It allows you to download Scatter files contained in the archive with the firmware.
6. Now you need to click on the button with an arrow and the inscription on the toolbar Download. And only at this stage connect the device to the computer.
7. The firmware process should begin, the progress of which can be observed in the yellow line below.
8. After completion, the device must be rebooted. The first launch can last about 5-10 minutes.

You need to use this method and the Android flash tool SP Flash Tool carefully, as this is a universal method. And each specific device has its own features and tricks.

Odin is a powerful tool for Samsung

Odin is an Android flasher via a computer for Samsung devices. It is a multifunctional machine that can not only change the firmware on the device, but also install recovery, kernels and much more.

For normal operation of the program, you will need an installed Windows system, drivers for the Samsung device, as well as a special set of ADB Fastboot. Some tips and tricks when working with Odin:

• Before starting the firmware, you need to make sure that the battery is charged at least 50%;
• in order not to turn the device into a “brick” during the procedure, you should use a laptop or PC with an uninterruptible power supply;
• use the original USB cable;
• When saving the firmware file, there should be no Russian characters in the path.

As a rule, you should look for firmware on the official Samsung website. If you need some kind of custom one, then you need to go to some thematic forum for it, for example, w3bsit3-dns.com.

Phoenix Suit

This flasher for Android tablets and phones is designed for Allwinner BoxChip processors. The functionality of the program is small, but sufficient to perform firmware flashing for many device models on the Android platform. The process itself does not require special knowledge or effort.

First, drivers are installed on the device, then the required software version is found. Then, on the Firmware tab, the downloaded firmware file is indicated and the procedure itself starts. Upon completion, the program will reboot the device itself.

Conclusion

There are many programs on the network for flashing firmware on devices with the Android OS. Some have already ceased to be used and supported, some are simply not needed due to the availability of more functional and simpler solutions. The article described the current and popular types of stitchers today.

But when using any program, it is worth remembering that firmware is a very responsible task. Getting a non-working phone in the process is as easy as pie. Therefore, you should study in more detail how and with what firmware is installed for a particular phone and tablet. And also clarify which version of the firmware is required.

We must not forget about kickbacks. That is, you should create backup copies of your working system. This will allow you to return everything to its place in case of an error.

Android is open source, so developers can freely modify it, add new features, and create their own images of the operating system for phones and tablets. Some of these firmwares become extremely popular and even become the basis for successful commercial projects. We introduced you to some of them in this and also. And now we want to discuss with you the reasons that may convince you to take a risk and install third-party firmware on your Android.

Getting the latest version of Android

It's no secret that many manufacturers of even expensive devices don't bother themselves too much with supporting their products. As soon as they sell you their product, they immediately forget about the need to release new firmware versions for them. As a result, it turns out that you do not have the opportunity to update to a new version of Android, even if the smartphone’s hardware freely allows it.

In this case, the best and sometimes only solution would be to use the well-known CyanogenMod, which, although it has many of its own “chips,” is in many ways similar to stock Android. Thanks to this development, owners of even fairly old devices can use the latest versions of the system.

Refusal of “branded” shells

Many popular manufacturers (let’s not point fingers) love to equip phones with their own proprietary shells, which, however, is not liked by all users. Not only are many of them frankly ugly and inconvenient - this, as you know, is a matter of taste, but they also manage to noticeably slow down the system. Naked Android against this background shows speed records and impresses with its responsiveness.

Yes, of course, you can install your own launcher and remove all these widgets, but there is no way to refuse all the dubious settings that the manufacturer has made in the operating system. So in order to get a truly "pure" Android, you will have to install a custom ROM.

Removing pre-installed software

Having received your brand new phone and having played enough with the programs installed on it, you gradually come to the understanding that it would be better not to have them at all. Most often, manufacturers complete the software package of a device, focusing not on feasibility and quality, but purely for commercial reasons. In addition, these programs are considered system programs and cannot be easily removed. As a result, we get a device full of outright rubbish that interferes with our lives.

A radical solution to this problem is to flash the device to a custom assembly that does not contain pre-installed software.

Getting additional features and system settings

Many firmwares have such a different appearance and set of functions from the original Android that we can safely talk about independent operating systems. First of all, we are talking about such popular Chinese projects as MIUI, Lewa, Oppo, which are developing at a gigantic pace. It is likely that after trying this oriental cocktail at least once, you will look at the bland Android dish with undisguised regret.

Other firmware, for example AOKP, although based on stock Android, give such scope in settings, such customization possibilities that owners of ordinary smartphones have never dreamed of.

Safety

It may sound strange, but free community-created firmware can sometimes be safer than Google's product. In them, if you wish, you can completely get rid of the all-seeing eye of this company, completely replacing all their services and applications with third-party developments. It turns out, therefore, “Android without Google,” no matter how strange it may sound.

In addition, many custom ROMs contain a built-in antivirus and such detailed permission settings for each application that you can thoroughly specify who can do what on your device for what purpose.

Reasons not to use third-party firmware

But, as you understand, everything is not so rosy and there are quite significant problems that you may encounter in your experiments with firmware.

1. Bricks. The flashing process, although thoroughly developed and quite easy, still, with a certain degree of bad luck and crooked hands, can turn your device into just a dead block of plastic and microcircuits.
2. Battery problems. A custom ROM may not be optimized enough for a specific device and may drain your battery faster than the official firmware.
3. Hardware problems. Your new firmware may not fully support all the hardware in your phone, so you may encounter errors, some broken modules, and other issues. For example, your device's camera may not capture images as well as it used to, or your GPS may suddenly be slow to find satellites.
4. Errors. The manufacturers of your device test the software well before releasing it for sale, which, of course, cannot be said about independent firmware developers. Therefore, you may encounter annoying errors, which, although they will be corrected in the future, can spoil a lot of blood for you.
5. Guarantee. If you use third-party firmware, you will lose your warranty. If this is important to you, then think about it.

And now I would like to know your opinion about the need to flash Android. We ask you to participate in the survey and express your point of view in the comments.