[General Questions and Answers] nucleusprime:
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

Android17@BuildServer #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.