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?

[ROOT]Root Guide for Huawei MediaPad M5

DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.

C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.

samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.

Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk

I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.

Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...

Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.

@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...

Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.

Question is, for those of us with the Non Pro version, can this still be done.

@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?

OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.

magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:

OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).

magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:

struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img

The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.

I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost

Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?

@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...

This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod

AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101

[guide]how to upgrade from unofficial LineageOS 15.1 to 16.0 while keeping data

sorry for my bad english,i am chinese
items needed:
blu_spark twrp(people says it is better than official twrp.less bug,somehow i cant fully restore a backup in official twrp,get bootloop or error 255,i have not try to use this twrp to do a full restore yet,maybe official twrp will work for you)
i am using
twrp-3.2.3-x_blu_spark_v9.85_op6.img
twrp-3.2.3-x_blu_spark_v9.85_op6.zip
download link
blu_spark twrp:
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
unbrick tool:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
los
from lineage-15.1-20180819_185755-UNOFFICIAL-enchilada.zip
to lineage-16.0-20180913_083011-UNOFFICIAL-enchilada.zip
https://forum.xda-developers.com/oneplus-6/development/rom-lineageos-16-0-t3839750
step:
0 already in a working los 15.1 rom
1 remove screen lock(maybe not necessary)
2 backup data partition in twrp(dont need other partion unless you will go back to los 15.1),then copy to a computer,you need to copy other files manualy to a computer for example: photos
3 use unbrick tool to install oneplus rom (nothing bad will happen using this,this way is cleaner,the real reason i use it is because when i installed open beta 3,some serious bug happened,i cant boot into official twrp,i get qualcomm crashdump mode instead and i get device is currupted where it should say bootloader is unlocked),maybe you can skip step 3 and 4 if you are lucky
4 oem unlock
5 download open beta 2 rom to your computer
6 fastboot boot twrp.img
7 wipe then install open beta 2 rom+twrp(twrp says no OS installed when chose reboot ,but it is fine)
8 i booted into open beta 2 rom just to make sure it works,maybe not necessary
9 reboot into twrp ,wipe then install los 16.0+twrp
10 reboot into twrp (twrp says no OS installed when chose reboot ,but it is fine)
11 intall opengapps+magisk
12 boot into los to make sure it works
13 reboot into twrp
14 restore data partition (dont need manually wipe before this)
15 wipe dalvik/art cache(maybe not necessary)
16 boot into system(may take 4 minutes)
i used for a few hours,works fine,no serious bug,dont need to login apps.if you have errors,plz follow this guide precisely,it works for me at least,and i tried this method twice,it works
tip:you can use adb to copy mutiple files or folder at the same time, for example
adb push "F:\oneplus twrp ubrick\lineage-16.0-20180913_083011-UNOFFICIAL-enchilada.zip" "F:\oneplus twrp ubrick\open_gapps-arm64-9.0-nano-20180915.zip" "F:\oneplus twrp ubrick\twrp ob3\twrp-3.2.3-x_blu_spark_v9.85_op6.zip" "F:\oneplus twrp ubrick\Magisk-v17.1.zip" /sdcard/
adb push "F:\oneplus twrp ubrick\TWRP" /sdcard/
bugs i discovered,these bug exist even using normal clean install method(dont keep app data ),this restore method is fine
using opengapps nano or stock
dont have adaptive battery and adaptive brightness(the google AI version),cant copy text in recent view,but have digital wellbeing
privacy guard not working,force close,other appops apps like appopsx not working

Thank you for posting this guide. I have a couple edits/notes.
After you use the unbrick tool, you'll need to use the version of TWRP here, and not the blu-spark version: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Once OB2 is installed, you need the blu-spark version.
Step 7 needs to be repeated. OB2 must be installed twice to cover both A and B slots.
I had trouble finding the Qualcomm drivers, but eventually found something that didn't seem to be bundled with some other software and *also* worked on 64-bit Windows. Some of the links out there are designed for Windows Vista.

0xScott said:
Thank you for posting this guide. I have a couple edits/notes.
After you use the unbrick tool, you'll need to use the version of TWRP here, and not the blu-spark version: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Once OB2 is installed, you need the blu-spark version.
Step 7 needs to be repeated. OB2 must be installed twice to cover both A and B slots.
I had trouble finding the Qualcomm drivers, but eventually found something that didn't seem to be bundled with some other software and *also* worked on 64-bit Windows. Some of the links out there are designed for Windows Vista.
Click to expand...
Click to collapse
Somehow I only used one twrp,it works for me,I think when you install OnePlus rom in twrp,it has two steps,I think it automatically install in both slots
You may get some battery issus after using this install method,it will automatically fixed in a few days,it seems battery need to adjust

[RECOVERY]TWRP_3.1.0_unofficial_ALCATEL_U5_&_TCL_5044_all_va riants

******TWRP 3.1 FOR TCL 5044 all variants******
---------------------------------------------------------------------------
DISCLAIMER : this is an unnoficial build created by myself Tested and confirmed working, i used magisk V18 as test.zip and is now rooted with magisk, there will be bugs comment here any issues you find & i will fix them asap,
UPDATE : 26th Jan 2019 : WORKING
* SD card mount now added
*OTG fixed
* terminal now works within TWRP no more child process exited error,
* sideload is functional
NOT WORKING : MTP
---------------------------------------------------------------------------
CHIP VERSION
---------------------------------------------------------------------------
Compatible chip type: FSTYPE
MEDIATEK : MT6737M EMMC
MEDIATEK : MT6735M EMMC
---------------------------------------------------------------------------
NOTICE : take a firmware backup before flashing
Anything to your device though this recovery is
Confirmed working you should always back your original firmware up, This recovery does NOT come with a Scatter.file included to stop bricking with incompatible device partitions, should you require it please ask in the comments.
--------------------------------------------------------------------------
0. make sure OEM unlock is ON in the developer options before doing anything.
1. Unzip the recovery from the .zip.
2. Open SP Flash tool.
3.set your DA AGENT to all in one MTK DA.
4.load your scatter.file into the Flash tool.
5.wait for your scatter to load your files.
6.unselect all files for flash but recovery.
7.load twrp_3.1 into recovery slot.
7.1 if you have 5044T flash my patched boot.img below also.
8.MAKE SURE DOWNLOAD ONLY is set DO NOT use format all + download.
9. Click start download.
10. Remove battery from phone.
11. Connect to pc with usb cord.
12. wait for flash to complete.
13. Unplug & insert your battery.
14. Hold power & volume up until the first screen appears and release, TWRP will now load.
15. Swipe to allow modifications.
16. Tap wipe.
17. Tap format & type yes then press ok
18. Reboot recovery once complete,
19. You can now root your device or flash what you need to.
20. Hit the thanks button here on XDA i spent hours upon hours building this for everyone once you reboot after formatting the data partition it will take roughly 5 minutes for your 5044 to boot.
---------------------------------------------------------------------------
If you need help please dont be afraid to ask here im here to help, if it does not boot on your device your board is different in which case you will need to attach your boot.img & recovery.img in a post so i can download and create a compatible twrp for your device.
_____________________________________________
LINKS :
TWRP 3.1.0 updated 26th Jan 2019
https://drive.google.com/file/d/1hi19OtPeVqSpe3c6VyRu8XusBcCpmai0/view?usp=drivesdk
PATCHED BOOT.IMG (no dm-verity) 5044T ONLY
https://drive.google.com/file/d/1SR99R4Bo-VoZnd4T9rQebt5tczaHNQxT/view?usp=drivesdk

Pics of twrp

NEW UPDATED TWRP 3.2.3-0 here for OPTUS X SPIRIT ( 5044T MT6737M - MT6735M ) everything is confirmed working in the latest build including MTP
TWRP 3.2.3-0
https://forum.xda-developers.com/android/development/twrp-t3903337

Alcatel Versa
First off... Great work and an awesome easy to follow tutorial. Now for the million dollar question... I have an Alcatel 5044c. It's the Cricket version and it's called the Versa. It has Android 7.0. Is this compatible?

Illbeurhuckleberry6666 said:
First off... Great work and an awesome easy to follow tutorial. Now for the million dollar question... I have an Alcatel 5044c. It's the Cricket version and it's called the Versa. It has Android 7.0. Is this compatible?
Click to expand...
Click to collapse
Hey mate,
No not for this recovery your kernel will be different,
If you 5044C is mediatek you can upload me your recovery.img and i can most certainly make you twrp for your 5044C
android version your currently on wont matter TWRP version 3.x.x supports from android 6-9

Matty1993 said:
Hey mate,
No not for this recovery your kernel will be different,
If you 5044C is mediatek you can upload me your recovery.img and i can most certainly make you twrp for your 5044C
android version your currently on wont matter TWRP version 3.x.x supports from android 6-9
Click to expand...
Click to collapse
Hi,
Since others are asking:
Does this support the Alcatel 5044Y?
Is this the latest release?
/Martin

5044c boot.img and recovery.img
Need scatter and flash files please
GH

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img