Database Info

Blu R2 Plus root guide

I have searched a bit and found nothing so far. Is it even possible to gain root on this phone? I have the 32gb with 3gb ram Android 7.

Anyone?
Any help at all? Anyone?

Man I can't find anything either! I guess our only option is to wait

I'm a 3rd person looking for info on rooting this Blu R2 Plus. I have found someone using Majisk but the steps are not detailed enough.

Braunish said:
I'm a 3rd person looking for info on rooting this Blu R2 Plus. I have found someone using Majisk but the steps are not detailed enough.
Click to expand...
Click to collapse
Hmm sounds liable but I'm not too keen to risking it

Don't risk it until we get further info
totheark408 said:
Hmm sounds liable but I'm not too keen to risking it
Click to expand...
Click to collapse
I've lost one to boot loop because I patched version provided in this thread, and then flashed that to v4.01 rom is where I think problem arose.

Braunish said:
I've lost one to boot loop because I patched version provided in this thread, and then flashed that to v4.01 rom is where I think problem arose.
Click to expand...
Click to collapse
Was the rom specifically meant for the r2 plus?

Updated ROM by Blu for R2 Plus on 2/11/18
totheark408 said:
Hmm sounds liable but I'm not too keen to risking it
Click to expand...
Click to collapse
I'm not sure you found this out, but there have been 2 versions of Blu Rom issued in February 2018 alone. I did update to the 4.01 version (2.11.18) found at https://www.needrom.com/download/blu-r2-plus/#comment-389270 using SP Flash, latest version, and it worked fine.
---------- Post added at 05:59 PM ---------- Previous post was at 05:52 PM ----------
totheark408 said:
Was the rom specifically meant for the r2 plus?
Click to expand...
Click to collapse
The file is no longer available, but yes it was presented as Blu R2 Plus, but I think it was factory version 3.01 they were dealing with according to the dates on messages. Verison 4.0 and then Version 4.01 came out in February. There is another thread where they talk about using majisk manager and yes the instructions were very vague. My next step it to try to test the patched_boot.img file without flashing it or destroying my phone, or just wait. Been using KingoRoot and KingRoot to no avail.

Braunish said:
I'm not sure you found this out, but there have been 2 versions of Blu Rom issued in February 2018 alone. I did update to the 4.01 version (2.11.18) found at https://www.needrom.com/download/blu-r2-plus/#comment-389270 using SP Flash, latest version, and it worked fine.
Click to expand...
Click to collapse
I was not aware! Ill definitely look into this. Have you made any progress on rooting?

BLU R2+ root using Magisk v16.0 & ADB/Fastboot
I successfully rooted my new BLU R2 Plus using Magisk v16.0 and ADB/Fastboot. Sharing the steps I used to help any R2+ owners out there.
I did these steps on two of the stock ROMs I found at NeedROM that were linked by the BLU Development Team G+ Community.
The ROMs I used are named:
BLU_R0190WW_V7.0.03.01_GENERIC-18-10-2017
BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018
The 1st ROM matched the build ver/date preloaded on my new BLU R2+ (v3.01).
The 2nd ROM is the latest ROM available on NeedROM (v4.01) and I believed it to be the latest update.​
Tools I used:
Minimal ADB/Fastboot v1.4.3
Magisk Manager v5.6.4
Magisk v16.0(1600)​
Device details for preloaded ROM for the curious (Settings >> About Phone):
Model number
R2 Plus
Android version
7.0
Android security patch level
October 5, 2017
Baseband version
MOLY.LR9.W1444.MD.LWTG.MP.V110.5.P38, 2017/10/17 20:51
Kernel version
3.18.35
[email protected] #2
Wed Oct 18 15:22:31 CST 2017
Build number
NRD90M
Custom build version
BLU_R0190WW_V7.0.03.01_GENERIC 18-10-2017 14:31
Disclaimer: This is posted for educational purposes only. If you perform these steps you do so at your own risk.
Step-by-step Guide (aka what I did):
1. Unlocked bootloader using ADB/Fastboot using standard adb/fastboot method on Win10 laptop.
Enable Developer Opts >> Enable OEM Unlocking >> "fastboot oem unlock" >> "fastboot reboot" >> wait for FDR.​
2. On laptop downloaded ROM from NeedROM and unzipped it to a new folder.
3. Copied boot-sign.img from unzipped ROM folder on laptop and transferred to R2+ using USB File Transfer.
4. Side-loaded Magisk Manager v5.6.4 and opened it.
5. When opened Magisk Manager prompts to Install Magisk. Prompt says "Do you want to install Magisk-v16.0(1600).zip now?".
If you cancel the first prompt tap the Install button at the bottom of Magisk Manager screen.​
6. Select INSTALL at the prompt and then Magisk prompts to Select Method. Select "Patch Boot Image File".
7. Select boot-sign.img that was transferred to device. Give permissions to Magisk as needed.
8. Magisk will create a patched_boot.img and save it to the device. I copied this back to the laptop.
I had to rename patched_boot.img on the R2+ in File Manager for it to show in Windows Explorer on the laptop and be copied.​
9. Rebooted into fastboot and tested patched boot image in ADB using "fastboot boot patched_boot.img".
After booting the patched_boot.img MagiskManager app showed v16.0 was installed.
Installing and running Root Checker verified the device was rooted.
This part could be skipped but I wanted to play it safe.​
10. Rebooting the device shows Magisk is not installed and Root Checker says the device is not rooted.
11. Knowing the process worked. I then wanted to repeat it on the latest update I saw on NeedROM.
I installed the OTA Update on the device before realizing it showed v4.01 instead of v4.02.
It's worth noting the OTA installed with the bootloader unlocked.
The download was apparently done in the backgound and thus the install started immediately.
I have never found a way to dump the stock ROM on an MT6753 device I decided to test SP Flash Tool.
I flashed BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018 using SP Flash Tool v5.1804 on a Win10 laptop.​
12. Flash to stock ROM v4.01 was successful. I had to perform bootloader unlock again and then I repeated steps 1-10 on v4.01.
13. I flashed the patched boot image using "fastboot flash boot patched_boot.img" then rebooted with "fastboot reboot".
14. Confirmed again using MagiskManager/Root Checker. Success.
WARNING: I do not recommend doing these steps using the ROMs I used unless you are running the same version as the downloaded file or are doing the steps on a boot.img you know is for your hardware and currently installed firmware.. Doing otherwise may not work and could damage the device. It's also possible any boot.img for your device would work, but I am not sure and only did this using the exact same boot image as the firmware installed on my device at the time. I would prefer people be cautious and only do this with a file they KNOW is for their device.
Final thought: I have a theory that the BLU R2+ has a doppleganger named the "Symphony P9+".
Update: I had trouble installing Xposed module in Magisk Manager. I installed the Busybox for Android NDK module. Busybox installed, but after reboot Xposed still failed.
I then (re)installed Magisk via Magisk Manager using the "Direct Install (Recommended)" Option. The install was successful and after reboot Xposed 89.2 (Systemless) installed successfully but was reported in Xposed Installer for Magisk as installed, but not active. A second reboot fixed that and Xposed was active. Installing GravityBox [N] module in Xposed had no issues and works nicely so far. Root works so I think I'll try my hand at porting TWRP next.

Porting efforts and magisk/xposed/mod testing
Recovery porting experiences:
I ported a few stable builds of TWRP from two different MT6753 based devices. I used the R2+ v4.01 ROM as the stock rom and overall had limited success.
Two out of three were bootable, and those two worked correctly when booted via "fastboot boot recovery.img"; however, when flashing to the recovery partition the touchscreen does not work on either of the ones I made. Research on the issue indicates this a kernel restriction. Did not test backup/restore functions. Instead I ported a LineageOS 14.1 rom to test flashing with the ported recovery I made. Wiped and installed ROM + GApps. TWRP reported successful, however the ROM got stuck on the BLU logo white screen. With the custom roms flashed recovery/fastboot both still loaded like normal. Battery charging was bugged though which I've seen in other CM variants on many devices. It seems the flashing worked correctly from my observations. After all this I flashed back to stock using SP Flashtool.
Testing Xposed Framework/Modules and other observations:
I had continued issues with Xposed when installed via a Magisk module on both Magisk v16 and v16.3. Basically both the official magisk module and the xposed systemless module only work after a soft reboot. I did not like this and finally tried a standard Xposed Framework (v89) install using the official Xposed Installer APK (v3.1.5). This so far works without any problem and has never shown the "installed but not active" warning. As for Magisk, root access works great and the xposed not active issue aside, it's a perfect root solution. I should add I have not done any magisk/root hiding and Xposed Framework installed in any of these variations via Magisk will not be hidden from apps/services that checks for it.
I've tested Amplify, Greenify, GravityBox[N], and XLED Xposed modules and have not encounted any issues in those.
GravityBox's fingerprint launcher option works and can be set to sleep giving a combined wake/sleep using the Fingerprint scanner.
XLED control works. LED in the R2+ only seems be very basic and only have two colors (green and red). Setting to any blue shade either results in red/green or nothing. Testing in Lightflow gave similar results. At least having an override option for the apps that would default to solid blue and thus have no LED flash at all is nice though. Overall Xposed when installed via the standard/official method works great.
I've been using Substratum in Legacy mode and it also works as expected given it's limited functionality without OMS. Themes do work but there isn't a whole lot of selection for legacy themes.
Overall this phone seems very root friendly and has great potential. I do hope someone out there finds this info useful and would love to see some actual development beyond my meandering experiments and attempts.

Great work nucleusprime! Could you share a custom recovery you used to install xposed? Thanks

_renzomc said:
Great work nucleusprime! Could you share a custom recovery you used to install xposed? Thanks
Click to expand...
Click to collapse
I will gladly share anything that's helpful or interesting. If your goal is to install Xposed I was able to do that using the xposed installer app.
You can get the app from the Official Xposed thread here
Download and install the apk. Initially it will say Xposed is not installed.
Tap the INSTALL/UPDATE Version 89 button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select first option "Install" and when prompted grant Xposed Installer root permission.
Wait for the install to finish and and then reboot the device.
After reboot it should show Xposed is active.
Edit: I made a few screenshots but I'm unable to post them here yet.

I can see your screenshots from gmail app
Worked great! Thank you. I'm gonna try GravityBox now

_renzomc said:
I can see your screenshots from gmail app
Worked great! Thank you. I'm gonna try GravityBox now
Click to expand...
Click to collapse
Thanks for the update! Glad to hear it's working for you.

I am completely new to rooting and am completely unfamiliar with adb, etc. I understand the meaning of obtaining root, unlocking the bootloader and installing a custom room though. I really just want to gain root access and I don't have a newer computer I can use to assist me in this. I do have a very old Windows XP laptop. Isn't there a way I can gain root without using adb or installing another rom? The one on my.phone is newer than the one listed here as well, 7.0.04.03_GENERIC 08-06-2018. Is it not possible to gain root without the use of a PC? This phone is my daily driver so I don't want to take too big of a risk and just giving me access to light customization and being able to ditch preinstalled apps taking up space and using ram is good enough for me.

I require rom blu r2 plus
nucleusprime said:
I successfully rooted my new BLU R2 Plus using Magisk v16.0 and ADB/Fastboot. Sharing the steps I used to help any R2+ owners out there.
I did these steps on two of the stock ROMs I found at NeedROM that were linked by the BLU Development Team G+ Community.
The ROMs I used are named:
BLU_R0190WW_V7.0.03.01_GENERIC-18-10-2017
BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018
The 1st ROM matched the build ver/date preloaded on my new BLU R2+ (v3.01).
The 2nd ROM is the latest ROM available on NeedROM (v4.01) and I believed it to be the latest update.​
Tools I used:
Minimal ADB/Fastboot v1.4.3
Magisk Manager v5.6.4
Magisk v16.0(1600)​
Device details for preloaded ROM for the curious (Settings >> About Phone):
Model number
R2 Plus
Android version
7.0
Android security patch level
October 5, 2017
Baseband version
MOLY.LR9.W1444.MD.LWTG.MP.V110.5.P38, 2017/10/17 20:51
Kernel version
3.18.35
[email protected] #2
Wed Oct 18 15:22:31 CST 2017
Build number
NRD90M
Custom build version
BLU_R0190WW_V7.0.03.01_GENERIC 18-10-2017 14:31
Disclaimer: This is posted for educational purposes only. If you perform these steps you do so at your own risk.
Step-by-step Guide (aka what I did):
1. Unlocked bootloader using ADB/Fastboot using standard adb/fastboot method on Win10 laptop.
Enable Developer Opts >> Enable OEM Unlocking >> "fastboot oem unlock" >> "fastboot reboot" >> wait for FDR.​
2. On laptop downloaded ROM from NeedROM and unzipped it to a new folder.
3. Copied boot-sign.img from unzipped ROM folder on laptop and transferred to R2+ using USB File Transfer.
4. Side-loaded Magisk Manager v5.6.4 and opened it.
5. When opened Magisk Manager prompts to Install Magisk. Prompt says "Do you want to install Magisk-v16.0(1600).zip now?".
If you cancel the first prompt tap the Install button at the bottom of Magisk Manager screen.​
6. Select INSTALL at the prompt and then Magisk prompts to Select Method. Select "Patch Boot Image File".
7. Select boot-sign.img that was transferred to device. Give permissions to Magisk as needed.
8. Magisk will create a patched_boot.img and save it to the device. I copied this back to the laptop.
I had to rename patched_boot.img on the R2+ in File Manager for it to show in Windows Explorer on the laptop and be copied.​
9. Rebooted into fastboot and tested patched boot image in ADB using "fastboot boot patched_boot.img".
After booting the patched_boot.img MagiskManager app showed v16.0 was installed.
Installing and running Root Checker verified the device was rooted.
This part could be skipped but I wanted to play it safe.​
10. Rebooting the device shows Magisk is not installed and Root Checker says the device is not rooted.
11. Knowing the process worked. I then wanted to repeat it on the latest update I saw on NeedROM.
I installed the OTA Update on the device before realizing it showed v4.01 instead of v4.02.
It's worth noting the OTA installed with the bootloader unlocked.
The download was apparently done in the backgound and thus the install started immediately.
I have never found a way to dump the stock ROM on an MT6753 device I decided to test SP Flash Tool.
I flashed BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018 using SP Flash Tool v5.1804 on a Win10 laptop.​
12. Flash to stock ROM v4.01 was successful. I had to perform bootloader unlock again and then I repeated steps 1-10 on v4.01.
13. I flashed the patched boot image using "fastboot flash boot patched_boot.img" then rebooted with "fastboot reboot".
14. Confirmed again using MagiskManager/Root Checker. Success.
WARNING: I do not recommend doing these steps using the ROMs I used unless you are running the same version as the downloaded file or are doing the steps on a boot.img you know is for your hardware and currently installed firmware.. Doing otherwise may not work and could damage the device. It's also possible any boot.img for your device would work, but I am not sure and only did this using the exact same boot image as the firmware installed on my device at the time. I would prefer people be cautious and only do this with a file they KNOW is for their device.
Final thought: I have a theory that the BLU R2+ has a doppleganger named the "Symphony P9+".
Update: I had trouble installing Xposed module in Magisk Manager. I installed the Busybox for Android NDK module. Busybox installed, but after reboot Xposed still failed.
I then (re)installed Magisk via Magisk Manager using the "Direct Install (Recommended)" Option. The install was successful and after reboot Xposed 89.2 (Systemless) installed successfully but was reported in Xposed Installer for Magisk as installed, but not active. A second reboot fixed that and Xposed was active. Installing GravityBox [N] module in Xposed had no issues and works nicely so far. Root works so I think I'll try my hand at porting TWRP next.
Click to expand...
Click to collapse
Friend can have the link of the rom of the blu r2 plus, and why I need a room I can not download them. :good:

nucleusprime said:
I successfully rooted my new BLU R2 Plus using Magisk v16.0 and ADB/Fastboot. Sharing the steps I used to help any R2+ owners out there.
I did these steps on two of the stock ROMs I found at NeedROM that were linked by the BLU Development Team G+ Community.
The ROMs I used are named:
BLU_R0190WW_V7.0.03.01_GENERIC-18-10-2017
BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018
The 1st ROM matched the build ver/date preloaded on my new BLU R2+ (v3.01).
The 2nd ROM is the latest ROM available on NeedROM (v4.01) and I believed it to be the latest update.​
Tools I used:
Minimal ADB/Fastboot v1.4.3
Magisk Manager v5.6.4
Magisk v16.0(1600)​
Device details for preloaded ROM for the curious (Settings >> About Phone):
Model number
R2 Plus
Android version
7.0
Android security patch level
October 5, 2017
Baseband version
MOLY.LR9.W1444.MD.LWTG.MP.V110.5.P38, 2017/10/17 20:51
Kernel version
3.18.35
[email protected] #2
Wed Oct 18 15:22:31 CST 2017
Build number
NRD90M
Custom build version
BLU_R0190WW_V7.0.03.01_GENERIC 18-10-2017 14:31
Disclaimer: This is posted for educational purposes only. If you perform these steps you do so at your own risk.
Step-by-step Guide (aka what I did):
1. Unlocked bootloader using ADB/Fastboot using standard adb/fastboot method on Win10 laptop.
Enable Developer Opts >> Enable OEM Unlocking >> "fastboot oem unlock" >> "fastboot reboot" >> wait for FDR.​
2. On laptop downloaded ROM from NeedROM and unzipped it to a new folder.
3. Copied boot-sign.img from unzipped ROM folder on laptop and transferred to R2+ using USB File Transfer.
4. Side-loaded Magisk Manager v5.6.4 and opened it.
5. When opened Magisk Manager prompts to Install Magisk. Prompt says "Do you want to install Magisk-v16.0(1600).zip now?".
If you cancel the first prompt tap the Install button at the bottom of Magisk Manager screen.​
6. Select INSTALL at the prompt and then Magisk prompts to Select Method. Select "Patch Boot Image File".
7. Select boot-sign.img that was transferred to device. Give permissions to Magisk as needed.
8. Magisk will create a patched_boot.img and save it to the device. I copied this back to the laptop.
I had to rename patched_boot.img on the R2+ in File Manager for it to show in Windows Explorer on the laptop and be copied.​
9. Rebooted into fastboot and tested patched boot image in ADB using "fastboot boot patched_boot.img".
After booting the patched_boot.img MagiskManager app showed v16.0 was installed.
Installing and running Root Checker verified the device was rooted.
This part could be skipped but I wanted to play it safe.​
10. Rebooting the device shows Magisk is not installed and Root Checker says the device is not rooted.
11. Knowing the process worked. I then wanted to repeat it on the latest update I saw on NeedROM.
I installed the OTA Update on the device before realizing it showed v4.01 instead of v4.02.
It's worth noting the OTA installed with the bootloader unlocked.
The download was apparently done in the backgound and thus the install started immediately.
I have never found a way to dump the stock ROM on an MT6753 device I decided to test SP Flash Tool.
I flashed BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018 using SP Flash Tool v5.1804 on a Win10 laptop.​
12. Flash to stock ROM v4.01 was successful. I had to perform bootloader unlock again and then I repeated steps 1-10 on v4.01.
13. I flashed the patched boot image using "fastboot flash boot patched_boot.img" then rebooted with "fastboot reboot".
14. Confirmed again using MagiskManager/Root Checker. Success.
WARNING: I do not recommend doing these steps using the ROMs I used unless you are running the same version as the downloaded file or are doing the steps on a boot.img you know is for your hardware and currently installed firmware.. Doing otherwise may not work and could damage the device. It's also possible any boot.img for your device would work, but I am not sure and only did this using the exact same boot image as the firmware installed on my device at the time. I would prefer people be cautious and only do this with a file they KNOW is for their device.
Final thought: I have a theory that the BLU R2+ has a doppleganger named the "Symphony P9+".
Update: I had trouble installing Xposed module in Magisk Manager. I installed the Busybox for Android NDK module. Busybox installed, but after reboot Xposed still failed.
I then (re)installed Magisk via Magisk Manager using the "Direct Install (Recommended)" Option. The install was successful and after reboot Xposed 89.2 (Systemless) installed successfully but was reported in Xposed Installer for Magisk as installed, but not active. A second reboot fixed that and Xposed was active. Installing GravityBox [N] module in Xposed had no issues and works nicely so far. Root works so I think I'll try my hand at porting TWRP next.
Click to expand...
Click to collapse
good morning, friend, test and method as you explain with the version BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018, to the flah the boot the team goes into boot loop and does not start. Because this happens, could you send me the patched boot of the flash version on my phone?

[Umidigi One Max] Custom ROM, Modding, Rooting - Complete guide

Welcome to this guide, where I will guide you through rooting, flashing custom roms, and more, on our little Umidigi One Max !
WARNING : I am not responsible for your phone breaking or exploding during the night under your pillow. Please advice. If you cannot boot anymore, keep reading, your phone is NOT dead.
OFFICIAL ROM (Android 8.1)
The Umidigi One Max comes with Android 8.1 Out of the Box. Manufacturer has no plan on having 9.0 on the phone. That's why we root then ! Let's get into it.
Rooting the phone without unlocking it, or installing TWRP
Everything you'll do on this phone will NOT require a bootloader unlock. Note that this method is only in case you don't want to have your data wiped, or don't have access to an SD card (thus you cannot flash .zip in TWRP, except for ADB Sideloads)
What you'll need
Download the latest ROM from Umidigi's website : https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
Choose the ".rar" file
"E" ROMs are for European versions. It doesn't really matter what you choose.
Download SP Flash Tool on the same thread you opened for the ROM. It's "SPFT" for short
Unzip both
Install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/releases/
Steps
IMAGE COURTESY OF bencebacsi @ Umidigi forums
In the unzipped ROM folder, find boot.img
Copy it to your phone storage using an USB cable or any other method
Open Magisk Manager, press install
Choose "patch boot image file"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let magisk do it's job
Find the boot.img file you just copied
Copy the patched_boot.img back to your computer
Open SP Flash Tool
Open the "Download" tab
In "Scatter-loading file", press the folder icon and browse to the downloaded ROM folder. Choose the only file that shows up
Untick every box except for boot. There is a column called "Location" with a path, click on it to change to file.
Choose patched_boot.img
MAKE SURE YOU UNTICKED EVERYTHING EXCEPT BOOT
Click the "Download" button
Turn off your phone (not reboot) and connect is via USB
wait for the flash to succeed. Once done, unplug, boot, voila ! You got magisk !
Credits to topjohnwu for Magisk, what a great piece of work
Installing TWRP
Note that if you want to access the /data partition (internal storage), you'll have to wipe it ! If you do not need it, keep going, it won't wipe unless you want to.
What you'll need
Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html
Magisk.zip installer (NOT the manager) : https://github.com/topjohnwu/Magisk/releases/
SP Flash Tool : http://www.mediafire.com/file/wxlld9dfywk67jl/SP_Flash_Tool_v5.1916.rar/file
This method is shorter and requires less downloaded files.
Steps
Turn off your phone
Run SP Flash Tool
Load the scatter file (see pictures above) you downloaded from the latest ROM (see above as well)
Untick everything except recovery
Change path to recovery.img to be the TWRP image
Click "Download" and plug your phone
After it's done, unplug, and press Power + Vol Up
You'll see three options appearing. That's how you'll get to the recovery. Use Vol Up to scroll, and Vol Down to select. Choose Recovery Mode !
TWRP should boot by now
EXTRA STEP : Make /data readable. You will need to format data (YOU'LL LOSE ALL YOUR DATA) (Wipe > Format Data > Type "yes") and after that, flash this zip : https://androidfilehost.com/?fid=1322778262904004415
You can now proceed to flash zips, including Magisk.zip. If you made /data readable, you can send it to your internal storage. If not, use an SD CARD or ADB PUSH / SIDELOAD.
Returning to stock to fix issues / brick
Use SP Flash tool but instead of unticking everything, tick everything. Note that USERDATA, if ticked, will clear your data.
Ticking only certain partitions may work if you got issues with magisk or system mods and are still on Official ROM. Flashing boot and system will remove Magisk. If you are on custom ROM, you can flash their system again to fix issues as well. Make sure to choose the right system.img in SPFT !
OTHER ROMS
Installing GSI (Generic System Image) to get Android Pie 9.0
GSI takes advantage of Project Treble to create one system image that will work on most devices without issues due to a separate "vendor" partition. The One Max is Treble-compatible, but only up to 9.0 (No 10 Q for now)
This will allow you to get an AOSP experience, with it comes easy modding and theming, and less bugs, less chinese-spying (that's a thing apparently, but who cares really ? Not me to say the least)
GSI List
You can find a GSI List including bugs and download links in my other thread here : https://forum.xda-developers.com/android/development/gsi-gsi-experiments-t3941194
WARNING : DOWNLOAD GSIs WHICH ARE ARM64-AONLY AND NOT AB !
Installing a GSI
You will need TWRP Installed. Check above if it's not done yet. You'll also need the Magisk.zip, and I highly recommend you getting the disable-force-encryption zip
Start up by wiping /data in twrp (Wipe > Swipe the bar). It will not wipe the files in your internal storage (Music, Download, etc...). If you want to get access to /data in TWRP (which I highly recommend), you'll need to do a full format (Wipe > Format data > type yes).
Download a GSI (.img) and send it to your phone (Either using an SD Card, or adb push [file on computer] [destination folder]). Send Magisk and the disable-force-encryption zip at the same time.
Flash that system image using Install > Install Image > Browse to the .img file
Flash disable-force-encryption if you formatted /data (don't flash it if you didn't do that !)
Flash Magisk.zip
Reboot and profit !
Note that there might be some issues with the GSI you choose. Most GSI suffers issues regarding Wifi Tethering/Hotspot. Other than that, check for my thread for issues regarding GSIs.
Some GSI require installation of GAPPS (Google Apps). Download a GAPPS zip and flash it at : https://opengapps.org/ (Choose ARM64 and 9.0)
If Installation fails, saying that system size is too small, go to (Wipe > Advanced Format > Tick "System" > Repair or change file system > Resize File System) and try flashing again.
INTERESTING MODS FOR ALL ROMS
Magisk FDE.AI
A great system manager. Saves a ton of battery without a performance hit. You need magisk installed. XDA Thread : https://forum.xda-developers.com/apps/magisk/beta-feradroid-engine-v0-19-ultimate-t3284421
Fix SafetyNet not passing on custom ROMs/GSIs
SafetyNet will not pass by default on custom ROMs / GSIs.
Use Magisk Hide Prop Config : https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Run 'su' then 'props' in a terminal emulator. Edit Device fingerprint, choose Pick a certified fingerprint. I recommend using Xiaomi Redmi Note 7, as it changes the status-bar to be notch sized.
Note that you may need to do this next fix to make 'su' work :
Root request not working with Magisk
On some GSIs, root requests will not show up. You need to move some vendor files over to system.
Use TWRP's File Manager (Advanced > File Manager) or Adb shell to copy theses files :
Code:
/vendor/lib/libdirect-coredump.so
COPIED TO
Code:
/system/lib/libdirect-coredump.so
Code:
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
This will fix this issue until GSI / ROM creator fixes it in their ROM;
Enjoy your new phone ! Don't forget to say thanks to all the developers behind every project (not me ! I didn't do anything )
If you have any issues, feel free to ask questions !
See you on the other side

Downloaded phhusson's AOSP ROM
Extracted compressed image. Then...
Wiped Phone from TWRP w/ all three options Swipe, Formatted (Type "Yes"), and advanced wipe.
From TWRP went to:
Install > Install Image > Selected system-arm64-ab-gapp-su.img > Select Partition to flash image
From this screen it lists these partitions for selection:
-recovery
-nvram
-uboot
-boot
-logo
-tee
-System Image
I select System image. It starts flashing. After it has finished, I go to reboot, and that is when TWRP states "No OS installed".
Am I downloading the wrong image file?
*********************EDIT****************************
Nevermind. I downloaded system-arm64-aonly-gapps-su.img.xz and it boots fine with gapps included

Exactly, you downloaded A/B image, not A-only.

Using phhusson's AOSP ROM. I got the root requests show up. However the superuser app is blank. Nothing shows in the list.

Request for a video to install GSI
Hello
I'm using Umidigi One Max Android 8.1 and want to upgrade to 9.0 . Can you please make a YouTube video showing how to install the GSI version I'd gladly appreciate it.

Over the last month or so, I've tried multiple GSI ROMs, and stock. I've rooted stock, and everything runs nicely, I just can't stand the lack of features. Even rooted on stock, Google Pay still works. If I install a GSI ROM like Havok, root it, gpay will not work. Not sure why it works on stock rooted with magisk, but not with other ROMs.
I'm looking for a hacked stock rom for the one max that:
A.) Can be rooted.
B.) Can still run gpay.
C.) Has a advanced restart option to boot directly into recovery.
D.) Displays the battery in the status bar as a percentage rather a symbol, and a clock with seconds option.
If I had those options, I would stick with stock. I can accomplish all those options with Havoc GSI ROM, I just can't get NFC/gpay to work.

su
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works

@ _cab13_
thanks for tutorial
some comments/questions
Image shows MT6739 in phone image and scatter file of mt6739
My phone is MT6363 and appears to agree with online specs site such as
https://www.gsmarena.com/_umidigi_one_max-9525.php
Am I looking at the wrong tutorial or umm have you grabbed images from another phone and forgot to say so?

w1lh3lm3d said:
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
Click to expand...
Click to collapse
You have to mount the folder system and vendor for reading and writing and you can copy it, this is in recovery mount

Very helpfull, thanks)

Has anyone tried dual SIM and SD hack on this phone? I cant get my to work. When I do the hack, phone does not see any sim cards nor SD card.
However if I put only two sims, or sim and SD everything works well.
It is almost like issue w Samsung but no warning message

can i use this process on umidigi one as well
q1. Can i use this process on umidigi one as well?
When i visit "Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html" and search on devices they don't have umidigi one or one pro only the one max option. Other than screen size all three are pretty much spec'd the same. The umidigi one just doesn't have wireless charging or nfc that one pro and one max have and one max has 6.3 waterdrop vs one/one pro 5.9 notch display but all 720x1520 9:19 aspect ratio configurations. I found a umidigi one and one pro twrp recovery image here _https://unofficialtwrp.com/umidigi-one-umidigi-one-pro-root-twrp-recovery/ so if i have that are all the other downloads for doing non-rooted device upgrade to 9 pie non-device specific downloads?
q2. Nice to see this process covers a way to get form 8.1 to 9 w/o rooting device. Having never done so i'm curious why other search hits cover steps that require rooting device if the upgrade can be achieved without doing that, any insights?
q3. Would you say the likelyhood of bricking my device, if trying to follow these instructions using umidigi one vs one max, very low? Trying to determine if i should first line up and have on hand backup phone to use if the chance of that happening is high.

does magisk install allow me to upgrade to android 9 pie?
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?

myusrn said:
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
Click to expand...
Click to collapse
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.

drkiro said:
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
Click to expand...
Click to collapse
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?

myusrn said:
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
Click to expand...
Click to collapse
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.

drkiro said:
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
Click to expand...
Click to collapse
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?

myusrn said:
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
Click to expand...
Click to collapse
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

drkiro said:
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.

myusrn said:
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
Click to expand...
Click to collapse
You can return, to the Originate flashing state, this image, https://community.umidigi.com/forum.php?mod=viewthread&tid=18692&extra=page=1 , can experiment with any image and return it to the original state, the pixel experience does not work with this phone, in Android Q the NFC does not work, and the videos in whastapp, do not work. Android 10 image comes without gapps, you have to flash them. If the twrp you can flash it through fastboot

Custom ROMs and Recovery for Realme C12

Are you disappointed to see that there are no threads in Development section of XDA?
No worries, since Realme C11, C12 and C15 MTK share similar specs, things that are made for other two devices will work in our device too.
So our Custom ROMs and TWRP etc., are at Realme C11 forum https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Flashing Custom Recovery
First backup stock recovery
If you rooted the device, then see this, else follow below.
- Connect your device to PC
- Shift + Right click in platform-tools folder and select open command window here
- Run below commands to backup stock recovery
Code:
adb reboot recovery
adb root
adb pull /dev/block/by-name/recovery
adb reboot bootloader
You will get a file named recovery in your platform-tools folder. Rename it to stock-recovery.img and place it in safe place.
Click to expand...
Click to collapse
- Download latest TWRP from here in your PC
- Download vbmeta.img from here in your PC
- Place those two .img where platform-tools is extracted.
- Rename recovery file to custom-recovery.img
- Run below commands in command prompt that you opened above
Code:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot flash recovery custom-recovery.img
fastboot reboot recovery
Custom Recovery is not permanent when you are using Stock ROM. It will be replaced with stock recovery after you boot to Stock ROM.(See 2nd post to overcome this)
There is no Hardware button Combo like Power + Vol Up to boot to recovery mode. Only way is to use adb/fastboot or root
Spoiler
You cannot see files in Internal Storage because of decryption(FBE) is broken in OUR device's TWRP. So use External SDCard for flashing if you are using TWRP
It will be blank for 1½ minute when you boot to TWRP 3.5.0. Don't touch the screen when it is blank. Press Power Button once to wake up screen in TWRP.
Flashing Custom ROMs
- Download custom ROM from here
- Place it in your External SDCard
- Backup the things in your InternalStorage, because we are going to wipe it.
- Boot to TWRP with below command
Code:
adb reboot recovery
- Choose Wipe and select Format Data and type yes
- Go back and choose Install and choose External-Storage in Select Storage at bottom
- Select the custom ROM zip that you downloaded above
- Flash it and Reboot
- Enjoy!
Spoiler
If you get recovery bootloops, then flash stock recovery. See below post to flash stock recovery
List of ROMs for C12​Below ROMs are only for UI1. So don't flash when you are in UI2
Havoc-OS
ArrowOS
LineageOS
exTHm UI
PixelPlusUI
WaveOS
CipherOS
PixelExperience Plus
FluidOS
PixelExperience
Thanks

How to stop stock ROM from flashing stock recovery and keep custom recovery?
To do this, you need to root your C12 with Magisk.
Flash below attached RealmeRecoveryKeep.zip in Magisk app and flash custom recovery. Enjoy it accross reboots in stock rom.
Any recovery like TWRP, PBRP, SHRP, OrangeFox etc., will work with this.
Flashing Stock Recovery
Flashing it is same as TWRP.
Below I have attached Stock recovery from A.83, but it may work with any other version of UI1.
Don't flash this in UI2
First extract the zip and flash like TWRP.
SHA1 of img is:- a6ceb27226d09d6fbe9069f5e9f5448efaa10268
Guide for Flashing Stock ROM is at https://forum.xda-developers.com/t/gsi-phh-q-r-gsi-flashing-for-realme-c12.4244979/post-84630979
Thanks

I can't backup stock recovery. Getting this error:
adb: error: failed to copy '/dev/block/by-name/recovery' to '.\recovery': remote open failed: Permission denied
My bootloader is unlocked and I got magisk working.

JustAnormalGuy said:
I can't backup stock recovery. Getting this error:
adb: error: failed to copy '/dev/block/by-name/recovery' to '.\recovery': remote open failed: Permission denied
My bootloader is unlocked and I got magisk working.
Click to expand...
Click to collapse
Since you are rooted, run below commands in Termux to backup stock-recovery to internal storage.
Code:
su
dd if=/dev/block/by-name/recovery of=/sdcard/stock-recovery.img
Copy this stock-recovery.img to a safe place in your PC or External SDCard.
And also you can flash TWRP using
Code:
su
dd if=/sdcard/TWRP.img of=/dev/block/by-name/recovery

thanks a lot, i thought I got stuck with stockrom and have developer support for it

Hi!
I need to flash back my stock recovery. I have a question.
Should I flash the vbmeta.img too at first? (Just like I did while flashing twrp?)

Shawmik said:
Hi!
I need to flash back my stock recovery. I have a question.
Should I flash the vbmeta.img too at first? (Just like I did while flashing twrp?)
Click to expand...
Click to collapse
It is not needed, but flashing it will not do any harm.
Thanks

hello pa i need your help i can't flash castem room and stock room there is an error in my twrp

Zeyn0101 said:
hello pa i need your help i can't flash castem room and stock room there is an error in my twrp
Click to expand...
Click to collapse
Send the error picture

I can't post a photo here, may I ask your Instagram to send a photo of my twrp error

Zeyn0101 said:
I can't post a photo here, may I ask your Instagram to send a photo of my twrp error
Click to expand...
Click to collapse
Upload at https://oshi.at/ and send here

https://oshi.at/vZrBLB

Zeyn0101 said:
https://oshi.at/vZrBLB
Click to expand...
Click to collapse
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow this https://forum.xda-developers.com/t/unbrick-your-realme-c12.4260759/post-84859061

where do i get the super.img file

HemanthJabalpuri said:
List of ROMs for C12​Below ROMs are only for UI1. So don't flash when you are in UI2
exTHm UI
ArrowOS
PixelPlusUI
WaveOS
CipherOS
LineageOS
PixelExperience Plus
FluidOS
PixelExperience
Thanks
Click to expand...
Click to collapse
I would like to ask if the roms above now work on Realme C12 ui2 and if it's safe to flash a custom rom? Especially Arrow OS? Why can't they be flashed on ui2? Any idea on how to downgrade to ui1 so that I can flash it with Arrow OS?

GreatTech said:
I would like to ask if the roms above now work on Realme C12 ui2 and if it's safe to flash a custom rom? Especially Arrow OS? Why can't they be flashed on ui2? Any idea on how to downgrade to ui1 so that I can flash it with Arrow OS?
Click to expand...
Click to collapse
There is only Lineage OS for UI2 which is at https://github.com/techyminati/releases/releases/tag/1.0.2-RMX2185
Other ROMs based on UI2 will come soon.
Also if you want to downgrade to UI1 follow below steps
- Flash TWRP from https://androidfilehost.com/?fid=7161016148664786711 (Don't use other TWRP)
- Boot to TWRP
- Enable 'Skip Treble Compatibility error' in settings
- Flash ozip
- Format Data and wipe cache
- Reboot

HemanthJabalpuri said:
{Mod edit: Content of quoted post removed on request of OP.}
Click to expand...
Click to collapse
Hi! Thank you for the reply HemanthJabalpuri ! I would like to ask if you know the download link for ozip? I'm familiar with the other steps on TWRP except for ozip? Would I need to download ozip on Realme C12 or is it a setting? Do you know a reliable, stable and trusted download link for ozip? I apologize for the dumb question. Thank you for the explanation btw, I appreciate it!

GreatTech said:
Hi! Thank you for the reply HemanthJabalpuri ! I would like to ask if you know the download link for ozip? I'm familiar with the other steps on TWRP except for ozip? Would I need to download ozip on Realme C12 or is it a setting? Do you know a reliable, stable and trusted download link for ozip? I apologize for the dumb question. Thank you for the explanation btw, I appreciate it!
Click to expand...
Click to collapse
Normally, you can download latest stock rom(which is usually in .ozip format) can be found at realme website by searching 'Software update - realme' in Google to go your region specific site.
But many custom ROMs have bugs with different versions of stock rom. So suggested stock version version to be less buggy with custom roms is A.87.
All the latest and older .ozips can be downloaded at https://realmeupdater.com/downloads/archive/RMX2185/
So for A.87, here is the link for it https://download.c.realme.com/osupdate/RMX2185_11_OTA_0870_all_1TbYEnns8MEW.ozip
Thanks

HemanthJabalpuri said:
Normally, you can download latest stock rom(which is usually in .ozip format) can be found at realme website by searching 'Software update - realme' in Google to go your region specific site.
But many custom ROMs have bugs with different versions of stock rom. So suggested stock version version to be less buggy with custom roms is A.87.
All the latest and older .ozips can be downloaded at https://realmeupdater.com/downloads/archive/RMX2185/
So for A.87, here is the link for it https://download.c.realme.com/osupdate/RMX2185_11_OTA_0870_all_1TbYEnns8MEW.ozip
Thanks
Click to expand...
Click to collapse
Oh wow, nice. Thank you so much for this! I appreciate the help!

followed the steps you listed carefully, can't believe that it worked, thank you for the detailed instructions man, I successfully downgraded to realme ui1.

My experience - PIXEL EXPERIENCE PLUS (A11) - GSI-Unofficial

Stable enough to be used as your daily driver.
This rom is not developed nor maintained by me!
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk
Download arm64-ab-11.0-xxxxx
or arm64-ab-vndklite-11.0-xxxxx
Download: Link
Extra tip: try Lawnchair launcher
Install like any other GSI Rom including the Nfc patch.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Quick and easy way to install GSI & NFC :
1. Extract the ROM .img file from the compressed file.
2. Flash extracted ... .img in fastboot , use command
fastboot flash system (file_name).img
3. In fastboot flash TWRP over eRecovery (!) - guide:
https://forum.xda-developers.com/t/rom-official-anne-9-lineageos-16-0.4151163/post-83603363
4. Run command fastboot reboot , enter TWRP (press and hold Volume Up)
5. In TWRP unmount all except SD Card , Vendor and System (unmount and mount again if needed) and flash NFC patch
6. Go back to the TWRP's main menu, select Reboot > Recovery.
7. Now you can perform factory reset in stock Recovery.
Note: the TWRP will remain instead of eRecovery.
MAGISK ROOT :
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1 - Guide
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
1. In TWRP flash Mount-fix .zip file
2. Reboot into TWRP
3. Select 'Install Image' and flash
patched recovery_ramdisk
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
over recovery_ramdisk.
4. Go back , select Reboot > Recovery.
5. Install Magisk manager apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
(SafetyNet
Contactless payments with Magisk v23.0 )
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset, also you can use dload method).
ROOT WITH SUPERUSER:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
Not working: VoLTE, LED notification (at least for me)
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

-Alf- said:
Stable enough to be used as your daily driver.
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk for "arm64-ab" (not vndklite!)
or EMUI 8 for "arm64-aonly"
Download: here
Install like any other GSI Rom including the Nfc patch.
Not working: VoLTE, LED notification (at least for me)
Screenshots:
View attachment 5350493View attachment 5350495View attachment 5350497View attachment 5350499View attachment 5350503View attachment 5350505View attachment 5350507View attachment 5350509View attachment 5350511View attachment 5350513
Click to expand...
Click to collapse
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?

Fjord1 said:
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?
Click to expand...
Click to collapse
On Pixel Exp. some things work easier and more flexible . And I don't think it's just a placebo

Thanks so much I've been looking for an android11 pixel experience for the p20 lite
Can you use magisk with this?

joenuts2124 said:
Can you use magisk with this?
Click to expand...
Click to collapse
GSI rom is not related to recovery_ramdisk, so it is possible to use the Magisk root on any GSI roms .

I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?

Incomtus said:
I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?
Click to expand...
Click to collapse
Try this method
https://forum.xda-developers.com/t/migrate-custom-rom-migration-tool.4252863/
There are several options, I do not remember exactly, but I think that the best results I had with Flasher & Helper

Tried it but magisk is not working....

Incomtus said:
Tried it but magisk is not working....
Click to expand...
Click to collapse
...not at all, or for Migrate only ? And what about SuperUser?

DSU Loader not working, phone don't support?

joenuts2124 said:
DSU Loader not working, phone don't support?
Click to expand...
Click to collapse
DSU loader requires a/b partitions (two different system partitions).

-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
Doesn't emui 9.1 have ab?

joenuts2124 said:
Doesn't emui 9.1 have ab?
Click to expand...
Click to collapse
-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
It should be clear, hm?
"AB" in GSIs is not the same thing as physically having AB partitions .
"AB" in GSIs means SAR - system-as-root ( on EMUI 9.1).
P20 Lite supports Project Treble AB, yet is an A-only device ( does not support Seamless Updates).

-Alf- said:
...not at all, or for Migrate only ? And what about SuperUser?
Click to expand...
Click to collapse
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann

Incomtus said:
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann
Click to expand...
Click to collapse
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.

-Alf- said:
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.
Click to expand...
Click to collapse
Very strange i made a clean install,
I went back to stock 9.1.0.132 with DLOAD
I unlocked bootloader and flash the rom with fastboot, i flashed TWRP (9.1) for nfc,
I made a wipe with stock recovery, I booted again on TWRP , i flashed magisk mount fix reboot again on TWRP flashed patched recovery on recovery, and exactly same issue,
I used the same twrp for nfc and magisk. Magisk aint working on last andy Yann build either but works on Emiritein Lineage Os build ( but this one is older)
Did you tried with last build?
For Pixel I tried superuser app on fdroid but doesnt work

Incomtus said:
Did you tried with last build?
Click to expand...
Click to collapse
9.1.0.257
Incomtus said:
For Pixel I tried superuser app on fdroid but doesnt work
Click to expand...
Click to collapse
And why not the superuser linked in OP? Okay, your choice bro...
I'm afraid I can't help you anymore.

I did not see there were an Superuser app in op I was confused with Andy yann forum I made a mix with that two posts
But it is strange that magisk doesn't work if it works for you
Do I have to flag magisk AND superuser ZIP file ?

Incomtus said:
flashed patched recovery on recovery,
Click to expand...
Click to collapse
Then you need boot Recovery to get root permissions (due to patched ramdisk)
Incomtus said:
I did not see there were an Superuser app in op?
Click to expand...
Click to collapse
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"

-Alf- said:
Then you need boot Recovery to get root permissions (due to patched ramdisk)
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"
Click to expand...
Click to collapse
Yes I know that I have to reboot on recovery that's what I did, as I use to do it with other GSI. But I did not understand I have to root with phh also

How To Guide Root RUI2.0 and RUI3.0 all models with Magisk

WARNING
Do it at your own risk , neither XDA nor me will be responsible for any damage that may occur
Overview
Rooting your device will give you freedom to enjoy plethora of features like removing OEM bloatwares , using system level Firewall , backing up and restoring all data of Apps , underclocking kernel for better battery life etc .
Requirements ​
Bootloader Unlocked Realme GT Neo 2 (Guide - https://forum.xda-developers.com/t/bootloader-unlocking-on-indian-model-rui-2-0-latest-a07.4391679/ )
A PC (windows or linux) with adb- fastboot installed
USB cable
Magisk Stable Apk
TWRP.img thanks to @ SathamHussainM from his thread on the same topic
Downloads ​ADB-FASTBOOT setup for windows https://forum.xda-developers.com/at...484757/?hash=78ebfa42e75a5def462676a93fff24c7
TWRP.img file link https://www.androidfilehost.com/?fid=17825722713688258515
Magisk23 apk Click here
Root Checker App link https://apkpure.com/root-and-safetynet-checker/com.atominvention.rootchecker/download?from=details
STEPS​Copy this file to your PC C:\adb folder and rename it to twrp.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot your device into fastboot mode Open Command Line
Go To C:\adb folder , press shift and do a right click , select open Powershell window here
Now type
fastboot devices
, press enter it should show your device now
now type
fastboot boot twrp.img
Process will take 10 second
Your device will reboot and after some time it will show TWRP logo ( it takes time 1 min approx )
wait some time
then In PC file explorer it will show realme gt neo 2 , open it
go to internal storage > Downloads and copy paste the twrp.img file and magisk alpha apk
In twrp backup BOOT , EFS, Modem ,Persist-Image
after backup is done come back to TWRP home and tap on Install button go to the folder where you saved both the files
and select Install image button , now it will show twrp.img file , tap on it then select recovery partition and swipe to confirm flash
After process is complete press Back button and come to TWRP home
Again press install button and select magisk.apk and swipe to confirm flash , this will install Magisk 23 after process is complete press home button go to reboot tab and select system
, Now phone will reboot to system
In phone open file manager and install magisk.apk
Open magisk app it will show magisk installed
just to be sure press the install button and select direct install and press Lets GO
After process is complete press the reboot button and it will boot back to system mode now
Your phone is rooted with magisk 23 and you are eligible to enjoy variety of mods and themes for your device .

Q1) Why are you not flashing recovery directly ?
A) Becuase Its risky (very low chance of flashing failing from fastboot ),So
first we boot this twrp file temporarily and backup all important partitions
When it is clear recovery is working fine , we copy the twrp.img and flash it from twrp to make it permanent .

Q2) Why are you not flashing magisk patched image ?
Ans) Becuase Its risky (the patched boot image you got may not be of your model or software version which will cause bootloop , SO
we trust in magisk to use our device boot.img to create a patched boot.img with magisk support , then we reflash magisk from magisk App to confirm it .

Is there any way to flash stock rom if twrp is installed?

This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.

Spl1tz said:
This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.
Click to expand...
Click to collapse
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device

ultimatesprit said:
Is there any way to flash stock rom if twrp is installed?
Click to expand...
Click to collapse
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2

Email44841 said:
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device
Click to expand...
Click to collapse
Ah gotcha. And now i see bootloader unlock for all variants too. Finally!
Thank you for your hard work

Email44841 said:
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2
Click to expand...
Click to collapse
This is my first realme device.I would prefer to keep a stock rom to flash incase any boot loop. Not decided to flash twrp permanently. i hope i can boot to stock recovery and flash rollback package to be in stock..Will it work?

Is it possible to use Kernal editor app after root to undervolt/overvolt GPU?

I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?

lspgzz said:
I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?
Click to expand...
Click to collapse
sry for disturbe, i got it. Just rename the file into '.zip' and install it

Spl1tz said:
ow i see bootloader unlock for all variants too
Click to expand...
Click to collapse
Incorrect. Not all variants

can we update the magisk to latest version (stable or beta) ?

Yes
reversegear said:
can we update the magisk to latest version (stable or beta) ?
Click to expand...
Click to collapse
You can Safely update to latest Magisk releases

My twrp says "internal storage 0 MB", rui3.0 any idea how to fix this?

I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.

theogr91 said:
I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.
Click to expand...
Click to collapse
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data

RMX3370 said:
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data
Click to expand...
Click to collapse
After i unlocked bootloader i flashed ui 2 twrp to ui3 and bricked i fixed it with ofp flash sideload from twrp i can use my phone just bs on twrp