Because the Nokia 2.2 (code name: WSP), Nokia 3.2, and Nokia 6.2 share a similar chipset (SDM632), developers often port firmware between them. You may find ports of stock firmware or tweaked versions of the Nokia 3.2 system that work on the 2.2. These generally offer better stability than generic GSI images because they utilize the correct hardware drivers.
Assuming you have an unlocked bootloader and TWRP installed.
Step 1: Boot into Fastboot Power off the phone. Hold Volume Down + Power until you see the fastboot screen.
Step 2: Flash Temporary TWRP (Crucial Step) Because the Nokia 2.2 has a recovery partition that is integrated into the boot image, you usually cannot permanently install TWRP. Instead, boot it temporarily:
fastboot boot twrp_wasp.img
Step 3: Wipe Partitions Once in TWRP, go to Wipe > Advanced Wipe.
Step 4: Format Data Go back to Wipe > Format Data. Type "yes". This removes encryption.
Step 5: Flash the ROM
Step 6: Flash GApps (If not included)
Step 7: Reboot & Patience
Need help?
Ask specific questions in the Nokia 2.2 XDA Forums – include your current software version and which GSI you tried.
Last updated: April 2026
The Nokia 2.2, a budget-friendly device released under the Android One program, occupies a unique position in the world of smartphone customization. While it was designed to offer a "clean" Android experience with guaranteed updates, its entry-level hardware—specifically the MediaTek Helio A22 chipset and limited RAM—often leads to performance degradation over time. This has made the pursuit of custom ROMs not just a hobby for enthusiasts, but a practical necessity for users looking to extend the device's lifespan. The Barrier: Bootloader Unlocking
The primary hurdle for any custom software on Nokia devices is the locked bootloader. Unlike many competitors, HMD Global does not provide an official method for unlocking bootloaders on most of its Nokia-branded phones. However, for the Nokia 2.2, developers discovered unofficial methods to bypass this restriction. Unlocking the bootloader is the critical first step; without it, the device's security prevents the installation of any non-official operating system partitions. The Solution: GSIs and AOSP custom rom for nokia 2.2
Due to its modest hardware and the lack of widespread official developer support, the Nokia 2.2 rarely sees "device-specific" custom ROMs like dedicated builds of Pixel Experience or LineageOS. Instead, the community relies heavily on Generic System Images (GSIs).
Project Treble: Because the Nokia 2.2 launched with Android 9.0 (Pie), it is Project Treble compatible. This allows it to run GSIs—universal versions of Android that can boot on a wide range of hardware without needing device-specific kernel modifications.
AOSP GSIs: Users often opt for bare-bones Android Open Source Project (AOSP) GSIs. These versions strip away the heavier elements of the stock Nokia software, which can significantly improve responsiveness on the phone's quad-core CPU and 2GB/3GB RAM configurations. Why Install a Custom ROM?
For a device like the Nokia 2.2, the benefits of custom ROMs are primarily functional:
Performance Optimization: By removing "bloatware" and background processes inherent in official builds, custom ROMs can free up precious system memory.
Extended Software Support: While official support typically ends after a few years, the GSI community continues to release versions based on newer Android iterations, potentially keeping the phone secure and compatible with modern apps long after its official end-of-life.
Customization: Beyond performance, custom ROMs allow users to modify the user interface, system fonts, and navigation gestures far beyond what is possible on the stock Android One software. Conclusion
Customizing the Nokia 2.2 is a journey from overcoming HMD Global's restrictive bootloader policies to utilizing the flexibility of Project Treble. While it may not be the most powerful device in the modding community, the availability of GSIs ensures that this budget smartphone can remain a viable, functional tool for those willing to venture into the world of custom flashing. HMD Global's Nokia 2.2 can now be bootloader unlocked
Custom ROM development for the (codename: ) has transitioned from a "bleak future" into a specialized niche for enthusiasts
. While HMD Global does not provide official bootloader unlocking, community exploits have made it possible to bypass these restrictions to install custom software. The Unlock Barrier: A Prerequisite
The most significant hurdle is the locked bootloader. Unlike Pixel or OnePlus devices, Nokia does not offer an official unlock code. Users must utilize the
exploit, which targets the MediaTek MT6761 (Helio A22) chipset. This involves putting the device into and using specialized scripts to patch the partition. Availability: Unofficial services like Hikari Calyx or free open-source tools like are the primary routes. postmarketOS Wiki ROM Ecosystem: GSI vs. Device-Specific Because the Nokia 2
There are few "native" device-specific custom ROMs (like official LineageOS) built specifically for the Nokia 2.2. Instead, the device relies heavily on Generic System Images (GSI) GSI Compatibility:
Because the Nokia 2.2 launched with Android 9 and supports Project Treble, it can run various GSIs including , LineageOS GSIs, and Pixel Experience GSIs. Android Developers Stability:
Stability is generally "mixed." While basic functions like WiFi and Bluetooth usually work, you may encounter issues with the camera app or specific MediaTek-related optimizations. Performance Impact The Nokia 2.2 is a low-end device with 2GB or 3GB of RAM. Bloatware Removal:
Moving from the official Android One software to a light GSI (like ) can significantly reduce background RAM usage. Real-World Gains:
Users report smoother UI transitions compared to the often-stuttery official Android 11 update, though the weak Helio A22 processor remains a bottleneck for heavy apps. The Verdict HMD Global's Nokia 2.2 can now be bootloader unlocked
LineageOS is the grandfather of custom ROMs. For the Nokia 2.2, the unofficial builds of LineageOS 20 are remarkably stable.
Since the Nokia 2.2 launched with Android One, it supports Project Treble. This is a Google initiative that separates the Android OS framework from the vendor implementation.
What this means for you: Even if there isn't a specific "Nokia 2.2" ROM, you can install a GSI (Generic System Image). These are "universal" ROMs that can run on any Treble-supported device.
Popular GSI Options:
Note: GSI installations are experimental. You may face bugs such as non-functioning VoLTE (Voice over LTE) or camera issues, as GSI images use generic drivers rather than the specific hardware drivers optimized for the Nokia 2.2.
If you want, I can:
Related search suggestions provided.
For a device like the Nokia 2.2, which is a budget-tier smartphone with a MediaTek Helio A22 chipset and modest RAM (2GB or 3GB), a custom ROM should focus on efficiency, de-bloating, and extending hardware life.
Since an unofficial bootloader unlock is available for this model, the most "interesting" feature would be a "Deep Sleep & Resource Management" module specifically tuned for its low-end hardware. Feature Concept: "Dynamic Lite Mode"
This feature would automatically adjust system behavior based on the current load to keep the interface smooth despite the limited quad-core CPU.
Aggressive RAM Management: A custom kernel feature that aggressively kills background processes for apps not in the "whitelist," keeping at least 400MB-500MB of RAM free at all times to prevent the UI from stuttering.
De-bloated GSI (Generic System Image): Utilizing a Vanilla AOSP GSI without any Google Mobile Services (GMS) by default. This significantly reduces background CPU cycles and storage usage, making the 32GB internal storage feel much larger.
MediaTek-Specific Thermal Tuning: A feature to under-clock the CPU slightly during non-intensive tasks (like reading or music) to prevent the "thermal throttling" that often plagues budget Nokia phones during charging or light multitasking.
"Retro" Camera Processing: Since the stock Nokia 2.2 camera is basic, a custom ROM feature could include a built-in GCam Go port with custom XML configs optimized for the Helio A22's image signal processor to improve HDR and low-light performance.
Legacy App Support: A built-in "MicroG" toggle that allows you to run essential apps like WhatsApp or Maps without the heavy overhead of the full Google Play Services suite. Summary Table: Stock vs. Custom ROM Features Stock Android One Proposed Custom ROM Feature System Overhead Heavy (Full Google Suite) Ultra-light (Vanilla AOSP/MicroG) RAM Usage Often near-limit (2-3GB) Optimized "Lite" memory management Updates Ended at Android 11 Potential for Android 12L or 13 (via GSI) Performance Tends to lag over time Consistent via aggressive background control
Before diving into specific ROMs, it is crucial to understand the biggest hurdle for Nokia users: the Bootloader.
Unlike Xiaomi or OnePlus, HMD Global (the company behind Nokia) does not officially support unlocking the bootloader on their devices. The bootloader is a piece of software that loads the operating system. If it is locked, you cannot install custom software.
Historically, the Nokia 2.2 has been a difficult device to root. While there were methods involving paid services (like FunkyHuawei or HikariCalyx) to temporarily unlock the bootloader or flash firmware, there is no official, free, and permanent method endorsed by the community.
Prerequisite: You must confirm that your specific device is compatible with the current unlocking methods available on forums like XDA Developers. Without an unlocked bootloader, the ROMs listed below cannot be installed. Step 3: Wipe Partitions Once in TWRP, go
Solution: The Nokia 2.2 stores IMEI in a partition called NVRAM. If you wiped NVRAM, you need to restore a backup. Always back up NVRAM before flashing. Use MTK Client to write back your IMEI.