Database Info

[GUIDE][ROOT] How to root Cubot Note Plus with Magisk

Code:
Your warranty is now void!
I'm not responsible for any bricks/data loss
In this guide I will show you how to root your CUBOT NOTE PLUS using Magisk.
Make sure you back up all your files. Because everything will be lost.
1. Unlock your boot loader
01. Download Minimal ADB and Fastboot and the Universal ADB Drivers and install them somewhere
02. Enable Developer Options and enable USB Debugging and OEM Unlocking
03. Connect your Phone via USB to your PC
04. Open the MAF32.exe (in newer Versions: cmd-here.exe) in your Minimal ADB and Fastboot folder or run the Shortcut in your Start Menu
05. Type
Code:
adb reboot bootloader
Your Phone should reboot into bootloader
06. Type
Code:
fastboot oem unlock
All youre files will be deleted!
07. Follow the OnScreen Information on your phone (Press the VOL+ button on your phone)
2. Flash patched boot image
1. Download the patched boot image here: https://mega.nz/#!L3IWka7Y!pSR9MPdGdfWxXAZPcBMx_ysyF1CQ2VNVE9w3Uy11X7A. (patched with magisk v18.0)
2. Put it in the same folder as Minimal ADB and Fastboot.
2. type
Code:
fastboot flash boot patched_boot.img
3. Restart your phone and install the Magisk Manager App.
[/I]
If I made any mistakes or forgot something please correct me!

theres an update out. V14_20200820 with "minor bug fixes"
question to those how have a rooted quest... does it stay rooted when you install that update?
edit: okay normal way update does not work, becouse of custom twrp recovery... does anyone know where the downloaded ota-update file is located... i cant find it... (need to flash it with twrp)...

I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?

veretragna said:
I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?
Click to expand...
Click to collapse
That happens when flashing TWRP. The guide says you should boot TWRP.

Garyyy said:
That happens when flashing TWRP. The guide says you should boot TWRP.
Click to expand...
Click to collapse
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.

veretragna said:
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.
Click to expand...
Click to collapse
The TWRP Version isn't made by me. I know that it wont work when flashing it. Does your phone gets listed in the weird "artifact mode" when you type fastboot devices?

A couple of questions. Does this work with the V12 firmware? I also got the faulty bootloader screen with the artifact lines. Thinking that reflashing one of the original firmware files might fix it.
Pity that there isn't much going on for this phone as far as custom firmwares, recoveries etc go. It's a decent bang for your buck in terms of specs but a lot of wasted potential without some good custom roms.

veretragna said:
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.
Click to expand...
Click to collapse
I did exactly the same, weird atifact screen is unreadable for me it appears after unlocking bootloader , my Note Plus hung at boot to ,reflashed stock rom and recovery all good now artifact line stays till phone finishes boot as bootloader loader remains unlocked. :good:

Steve8262 said:
I did exactly the same, weird atifact screen is unreadable for me it appears after unlocking bootloader , my Note Plus hung at boot to ,reflashed stock rom and recovery all good now artifact line stays till phone finishes boot as bootloader loader remains unlocked. :good:
Click to expand...
Click to collapse
For me the artifact screen appears before doing the unlocking bootloader step and when it's on that screen, the device doesn't respond to ADB at all, so I cannot actually continue and root this device. I tried reflashing the stock firmware and even that didn't help. I'm honestly starting to regret purchasing this phone.
Does anyone else with this device ever use it for USB tethering or WiFi hotspot? First device I've ever had that actually loses power while it's plugged in. I can plug the phone into my computer, activate USB tethering, and it'll lose about 15% of battery every hour. I can keep the phone plugged into the wall, activate WiFi hotspot, and it'll lose about 10% of battery power every hour. This device is a bad joke.

Phenom2122 said:
A couple of questions. Does this work with the V12 firmware? I also got the faulty bootloader screen with the artifact lines. Thinking that reflashing one of the original firmware files might fix it.
Pity that there isn't much going on for this phone as far as custom firmwares, recoveries etc go. It's a decent bang for your buck in terms of specs but a lot of wasted potential without some good custom roms.
Click to expand...
Click to collapse
The patched boot image is from the V12 firmware. I also had the artifacts but I was able to continue anyways.

Hey thanks for replying man. For me, ADB gets stuck on "detecting devices" and doesn't actually pick up my device at that point. But I have contacted the shop regarding the battery and charging issues and they have told me that my device is faulty and I'm picking up a replacement tomorrow. So hopefully I'll be able to do this soon.
I've just been kinda depressed about my purchase. I could've bought a Nokia 2 for just a little bit less and I would've been guaranteed quality. But I took a gamble on this 'Cubot' device with specs that were too good to be true for the price. It's a nice phone but it's battery and charging sucks balls. And I knew that it shipped with Android 7.0 but I thought that there would at least be an update to Android 7.2.1. I dunno, I'm just disappointed. My S4 Mini seems to kick this thing's ass in terms of battery power. And my S4 Mini is 6 years old, still on its original battery and has literally half the processing power and two thirds the RAM. I just needed this device for its 4G capability because my S4 Mini is the 3G model. I might sell it at a loss and pick up a MiFi router and new battery for my S4 Mini instead.
These phones are a huge missed opportunity. They pack some great specs for the price but offer a crappy, limited version of Android with no custom firmwares to be seen. Maybe if the battery thing works out and I can actually use this phone as a Wifi hotpot without it dying, I'll look into how to port a custom firmware to it. I think Slim or Carbon are in order, if they still exist.
Thanks for the reply dude. Maybe I'll have a different attitude to this phone once I have my replacement.

veretragna said:
I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?
Click to expand...
Click to collapse
Adb a different twrp

Garyyy said:
Code:
Your warranty is now void!
I'm not responsible for any bricks/data loss
In this guide I will show you how to root your CUBOT NOTE PLUS using Magisk.
Make sure you back up all your files. Because everything will be lost.
1. Unlock your boot loader
01. Download Minimal ADB and Fastboot and the Universal ADB Drivers and install them somewhere
02. Enable Developer Options and enable USB Debugging and OEM Unlocking
03. Connect your Phone via USB to your PC
04. Open the MAF32.exe (in newer Versions: cmd-here.exe) in your Minimal ADB and Fastboot folder or run the Shortcut in your Start Menu
05. Type
Code:
adb reboot bootloader
Your Phone should reboot into bootloader
06. Type
Code:
fastboot oem unlock
All youre files will be deleted!
07. Follow the OnScreen Information on your phone (Press the VOL+ button on your phone)
2. Flash patched boot image
1. Download the patched boot image here: https://mega.nz/#!L3IWka7Y!pSR9MPdGdfWxXAZPcBMx_ysyF1CQ2VNVE9w3Uy11X7A. (patched with magisk v18.0)
2. Put it in the same folder as Minimal ADB and Fastboot.
2. type
Code:
fastboot flash boot patched_boot.img
3. Restart your phone and install the Magisk Manager App.
[/I]
If I made any mistakes or forgot something please correct me!
Click to expand...
Click to collapse
Does this method work with the Cubot P20 too ???

frank808 said:
Does this method work with the Cubot P20 too ???
Click to expand...
Click to collapse
No, because it is the boot image from the cubot note plus.

... dont want to open a new topic.
is there root option for the new cubot quest out there allready?

tko said:
... dont want to open a new topic.
is there root option for the new cubot quest out there allready?
Click to expand...
Click to collapse
You can probably follow the same steps. But you need to patch the boot image yourself. You can get the firmware for your phone on cubots website.

Garyyy said:
You can probably follow the same steps. But you need to patch the boot image yourself. You can get the firmware for your phone on cubots website.
Click to expand...
Click to collapse
the firmware i have.
but how do i patch the boot image?

tko said:
the firmware i have.
but how do i patch the boot image?
Click to expand...
Click to collapse
Install the Magisk Manager, press Install and choose BootImage. Than flash the patched boot image with fastboot.
Edit: On latest Manager it is called "Select and Patch a file" than select the boot image which is somewhere in the firmware.

Garyyy said:
Install the Magisk Manager, press Install and choose BootImage. Than flash the patched boot image with fastboot.
Edit: On latest Manager it is called "Select and Patch a file" than select the boot image which is somewhere in the firmware.
Click to expand...
Click to collapse
okay i did that, but the i get a bootloop with the patched boot.img
btw, the original img is ~32mb and the patched only 9mb
this seems strange.

tko said:
okay i did that, but the i get a bootloop with the patched boot.img
btw, the original img is ~32mb and the patched only 9mb
this seems strange.
Click to expand...
Click to collapse
Maybe try with a different version of the manager. Maybe report that issue in the Magisk thread.
Edit: Maybe Magisk returns only a patched ramdisk. Try and flash the patched image as ramdisk. If you have a ramdisk image, try to patch and flash that instead.

Garyyy said:
Maybe try with a different version of the manager. Maybe report that issue in the Magisk thread.
Edit: Maybe Magisk returns only a patched ramdisk. Try and flash the patched image as ramdisk. If you have a ramdisk image, try to patch and flash that instead.
Click to expand...
Click to collapse
okay if i could find a earlier version... , i would like to try it with 18.0
edit: found it... will try now.
crap, now the app does not give me the option to patch... no popup, no button, ...
edit2: okay, i cant use an older version, when i "install/patch" the app always first wants to update to the newest version.

Root Guide

Found this while trolling through the Chinese forums, none of this is my work, I have translated the instructions as best I can.
Disclaimers; I have not tried this, it may brick the global rom, the custom recovery is likely only in Chinese language.
You need:
Boot Loader unlock code (currently probably not possible to get)
Huawei USB drivers
Recovery image (attached)
Magisk package (attached)
files: https://mega.nz/#!PM0EmYLA!384hZjmJ9ExNc7Q8rSqssHunWSO7AxQ3GA4qet6RX4E
Extract files to a folder, open command prompt and change into this folder.
Unlock bootloader (BL unlock will clear the phone data, please do a backup)
- Obtain an official unlock code
- double-click to open the "Huawei Toolbox.exe"
- click "unlock bootloader "
- enter the unlock code in the pop up window , click OK, and wait for the phone to unlock complete restart.
Flash the third-party recovery
- Turn off the phone and connect the computer. Press and hold the “Volume Down” button and “Power button” until the phone displays the android page and release your finger.
- open command prompt and run:
fastboot flash recovery_ramdisk twrp.img
- after seeing the two OKAY feedback from the command line, the flash is successful.
Enter recovery to flash root image (this step will clear all data of the mobile phone including memory card, please make a backup in advance)
- long press “Volume Up” and “Power” ", until you see the a twrp logo, release the keys and wait to enter recovery mode
- After entering recovery, click the second item “Clear”, click “Format Data Partition” in the lower left corner, slide the slider to enter the clear, wait for the progress bar to complete
- Return to the recovery homepage, click on the last item "Advanced", select the last item "Remove data forced encryption", slide the slider to release, wait for completion
Copy the root package to the phone
- In Command Prompt type or copy the following commands
adb push magisk-installer.zip /sdcard
adb push magisk.apk /sdcard
Install Image
- Whilst still in recovery mode, click the first item to install the magisk-installer.zip package from the sdcard , slide the slider to install, wait for the flash to complete, and restart the phone
- After reboot is complete, click “File Manager”, select the apk file “magisk.apk” just copied from the memory card when install is finished, open the magisk app and click “No, thank you” in the pop-up window
- Return to the command line tool, type the code to execute, and wait for the phone to automatically restart
Fastboot reboot recovery
- after the restart, open "magisk", it should show that the installation is complete, that is, ROOT is achieved.

Anything in that forum on how to manually update phone?

technotika said:
Anything in that forum on how to manually update phone?
Click to expand...
Click to collapse
That is actually what I was looking for
But none, problem is the v20 (china version) seems to get OTA way before us, they all got v143 2 weeks ago.
I did find the menu to do it, but it only supports if the image is stored on an sdcard, and when I click it it says no sdcard found. so its impossible.

Tried same with similar results. One day eh? ?

İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader

greenblueye said:
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
Click to expand...
Click to collapse
If you read what I wrote in the first post you would see you cannot root without a bootloader unlock code.

Tested! Work bootloader code on Russia services (Cost 20USD)

belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Nice! Did unlocking bootloader factory reset your device?

Yes of course. All new Huawei and Honor do a reset after unlocking

i get bootloader unlock code from funkiehuwai for 20$
any one tried this instructions and have success?
I just wonder comments below will work?
*adb push magisk-installer.zip /sdcard
*adb push magisk.apk /sdcard
because there is no sd card support for view20?
when i opened huawei-toolbox.exe its in chinese and im afraid to continue other instructions

Did anyone use TWRP and which version?
Did the View 20 Boot correctly?
I read in a Forum, that with the view 20 doesn´t boot correctyl with TWRP. The reason should bei the Storage...
Best regards

Unlocked Bootloader
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Does that mean you rooted you device (with the files from above) or you just unlocked the bootloader?
I was able to unlock my bootloader with a code from funkyhuawei (about 18 €, site seems to be down currently). I did not use the unlock tool above, mainly because its chinese
- Enabled "USB debugging" and "OEM unlock" in developer settings
- Connected phone to PC, opened adb and used "adb reboot bootloader"
- Unlocked via "fastboot oem unlock *16digit code*"
This worked out fine. However, as far as i understand it magisk is installed over twrp (recovery_ramdisk), removing twrp but granting you root. This makes me kind of nervous since twrp has been a nice safety net on several occasions. This is why I stopped after unlocking the bootloader. Maybe someone has more experience on this? Why is there so little interest in rooting this phone?
Regards

root achieved
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards

garris_bibop said:
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
Click to expand...
Click to collapse
Well done good job:good:
İ have chinese version PCT-AL10 9.0.1.144 right now. Do you think i can use the same way? İ wonder from which version to extract recovery_ramdis.img

I have my view20 rooted
Thanks for the instructions.

greenblueye said:
I have my view20 rooted
Thanks for the instructions.
Click to expand...
Click to collapse
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?

garris_bibop said:
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
Click to expand...
Click to collapse
I get recovery-ramdisk from firmware PCT-AL10 9.0.1.129 . my phone is on version 9.0.1.144 but it worked:good:

After root i can not auto update software. 9.0.1.166 version is seen on ota but after download it says update is unsuccessful. Do you have any suggestion?

I think thats to be expected when rooted. Go for manual update I guess (https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). Personally I wouldn't bother with every update unless theres interesting new features and/or security updates. just to be on the safe side I would reflash the original recovery_ramdisk before updating! And backup your data!

NM Card
Hello !
Unless I'm mistaken, the View20 must be able to use nano sd cards (NM Card)

[GUIDE] Rooting the UMIDIGI S5 Pro | Magisk

EDIT: I attached a zip with AIDA64's reports for this phone. One report has Magisk hidden from AIDA64, the other doesn't.
This mostly a copy of _cab13_'s Rooting the UMI F2 post as the same instructions for rooting that phone are how I rooted the S5 Pro. So please give _cab13_ thanks here if this helped you root your phone. I'll take a thanks for removing the orange state warning if I helped you with that
Please be patient when posting questions, I will get back to you as quickly as I can. I just have many responsibilities which take up a great deal of my time.
Rooting the S5 Pro
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEI['s]s and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
Once bootloader is unlocked, warranty is considered void. By following this guide, you consent to that happening. Safety net CTS will not pass anymore unless you flash Magisk which hides the unlocked bootloader.
Never re-lock your bootloader while running anything unofficial as the phone will not boot until you unlock again.
And, once again, a lot of bad things can happen like boot loops, if that happens to you, don't freak out! Simply re-flash the stock ROM, redoing the rooting process from the start. It might be time consuming, but that's your safest bet!
More important even, have fun rooting, it's before all a hobby!
Various Resources
>>> Latest official stock ROM <<<
[Non European] UMIDIGI_S5Pro_20210107.V3.04
[European] UMIDIGI_S5Pro.E_20201130.V3.04
Minimal ADB and Fastboot by shimp208
> Magisk (and Manager) by topjohnwu <
Mediatek SP Flash Tool
UMIDIGI Community Forum S5 Pro Thread
Unlocking Bootloader
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate "Developer options" through Settings > About Phone > Tap Build Number multiple times.
2) Open "Developer options" in Settings > System > Tap Advanced.
Enable "OEM Unlocking" and enter your password to confirm. Enable "USB Debugging" as well.
3) On Windows, download and install Minimal ADB and Fastboot by shimp208
On Linux, use your package manager to install android-tools-adb and android-tools-fastboot
4) Open command prompt (Win + R > type cmd) or a terminal on linux.
5) Plug your phone, accept the prompt about adb and the PC signature.
6) Type adb reboot bootloader to reboot in fastboot mode. Unplug your cable from your phone
and replug it after fastboot is printed at the bottom of the screen.
THESE NEXT TWO STEPS WILL COMPLETELY WIPE YOUR DATA
7) Unlock the bootloader using fastboot flashing unlock and pressing Vol+
8) Unlock the secure partitions using fastboot flashing unlock_critical and pressing Vol+
9) Restart using fastboot reboot
You will now always see "Orange State" at boot; this is completely fine and will only delay your boot by 5 seconds.
Rooting using Magisk patched boot.img
This is "experimental" and is probably overkill, but everyone managed to install Magisk with it.
1) Clean install UMIDIGI_S5Pro_20200702.V3.02 (or the European one) with SPFT by selecting the scatter file, pressing download an rebooting the phone
(Make sure it is in "Download Mode" and not "Format + Download")
2) Patch boot.img by copying it to your device, using Magisk Manager to patch it, and get back the magisk_patched.img in the Download folder back to your PC.
3) Start ADB while booted; run adb reboot bootloader. Alternative is to reboot to recovery and selecting "reboot to bootloader"
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) In the following code, the vbmeta.img and the recovery.img are the stock files from the ROM you downloaded and extracted.
Code:
fastboot erase boot
fastboot --disable-verity --disable-verification flash boot magisk_patched.img
fastboot --disable-verity --disable-verification flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
When rebooting, install Magisk Manager. It will prompt to finalize the installation, you can do so.
Congratulations ! You are now a proud Magisk user ! All credits goes to @topjohnwu he's the real MVP here.
Returning to stock / Resolving issues
The best way to resolve any issue is to return to stock. Here is the method.
1) Download latest stock ROM on UMIDIGI's forums
2) Download SP Flash Tool if you don't have it yet (Windows only)
3) Extract stock ROM in SP Flash Tool directory. Refer to Flash Tool guide if needed.
4) Open SP Flash Tool, Download Tab, "Choose" in Scatter-loading file, select the scatter file in the stock ROM directory.
5) If you want to keep your data, untick "userdata" partition. MAKE SURE FORMAT IS NOT SELECTED!
6) Press Download and connect your device via USB. Reboot the phone or turn it off and everything will be flashed.
7) If you want a full stock experience, I recommend relocking the bootloader so that SafetyNet will pass. Get into fastboot mode by using adb reboot bootloader and use fastboot flashing lock_critical followed by fastboot flashing lock. This will wipe your data once more.
You should be good to go.
ONE LAST THING
Get rid of your orange state warning.
Download the attached zip file and extract.
Put your phone into fastboot and:
Code:
fastboot erase lk
fastboot erase lk2
fastboot flash lk lk_patched.img
fastboot flash lk2 lk_patched.img
fastboot reboot
No more orange state warning! Reflash the stock lk before unrooting, though.
ATTACHED LK FILE IS FOR UMIDIGI S5 Pro ONLY.

Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?

Hey guys it's me again !
Got some good news : I bought a S5 Pro as well
And I ABSOLUTELY LOVE IT !
I might get into rooting it soon, idk.
Thanks for the shout-out @zerosava

hermeez said:
Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?
Click to expand...
Click to collapse
No luck for me finding a custom recovery (twrp or anything else.)
If you have any exp with them, see if you can make the F2's (found in the F2 root thread) work. It SHOULD only need a minumum of tweaking, just to account for the (afaik) slight soc differences. i'm not gonna hold my breath. there seems to be a void when it comes to enthusiasm for this phone. by my serial no, i have the 4832nd phone manufactured. compared to serials ranging from 22000- 189000 for my other umis (f1play, s3pro, f2, power3)

I think I'll try making TWRP soon for it.
The F2 TWRP would not be usable this easily, it's easier to start fresh.
If anyone wants to try, download the sources for the F2 TWRP on my GitHub, then you need to extract the stock kernel and replace the F2's with the S5pro's

root working thanx

Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.

QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
Sorry, but I made this clear in the original post:
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEIs and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
I do not know how to help you. My only suggestion is to post your problem in UMIDIGI's forum here: UMIDIGI Forum
If anyone can help you, that's where to find them.

Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please

Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
I am sorry, but you will have to contact UMIDIGI support. Only they can help you as far as I know. I feel for you, I really do. I did this when I was a newbie with my F1 Play.

QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1

Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1

i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol

hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks

stick2020 said:
hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks
Click to expand...
Click to collapse
Do a "download only" flash of the "super", " vbmeta_system", and "vbmeta_vendor" partitions only (uncheck all other partitions) from the previous ROM. That should do it.

ZeNNoP said:
i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol
Click to expand...
Click to collapse
What precisely stuck you?

There is a new update firmware please make a rooting tutorial on youtube.,

Somebody made a custom TWRP and posted it on here. So if that'll help anyone out and get them to make a tutorial video, that be great. 'Cause I'm reading this over and over again, and I think I can do it, but I'm being very hesitant about it. And it's getting me all frustrated. I had it on "Flash Mode". And when I continued typing it out, it didn't go through and that had me on a raging panic attack. Luckily, it didn't mess up. But now I'm more hesitant. Please make a quick tutorial, doesn't even have to be perfect...
TWRP is at the bottom of this page:
[MT6785]How To Root Umidigi S5 Pro And Install TWRP 3.4.0 Recovery ~ Techswizz
To Root Umidigi S5 Pro, we will be using the Adb Tool Mode with TWRP recovery for Umidigi S5 Pro. It will be wise to read the post very well before flashing the recovery to avoid any Device errors or brick.
www.techswizz.com

Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?

bmaz121 said:
Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?
Click to expand...
Click to collapse
I am able to get FastBoot Mode on my screen (through step 6). I plug the phone back in per directions & I hear the Windows device connected chime.
I type: fastboot flashing unlock in the same cmd window
and I get "<waiting for any device>" in the cmd window and it hangs.
Every few seconds I hear the Windows device disconnected noise, but no device connect chime. This lasts indefinitely.
I repeated step 7 several times with variations with the Vol+ button: pressing first, holding down while pressing enter in cmd window, pushing afterward, holding down afterward, etc. Same results as described above.
Any help available? Should I not unplug my phone from the PC? The F2 directions did not require that.
thanks!

How to root Ulefone Armor 11 5G

I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
adb reboot bootloader
Click to expand...
Click to collapse
- When done verify the connection with the phone:
fastboot devices
Click to expand...
Click to collapse
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
fastboot flash vbmeta vbmeta_null.img
Click to expand...
Click to collapse
If you receive a positive answer we can go to next step
- Install patched Boot Image:
fastboot flash boot magisk_patched_xxxxx.img
Click to expand...
Click to collapse
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
fastboot reboot
Click to expand...
Click to collapse
Done now your phone should be now rooted.
Enjoy.
Have fun

Thanks for this, I was missing the vbmeta_null.img and was getting a boot cycle. Works perfectly.

Harlock1978 said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
- When done verify the connection with the phone:
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
If you receive a positive answer we can go to next step
- Install patched Boot Image:
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
Done now your phone should be now rooted.
Enjoy.
Have fun
Click to expand...
Click to collapse

it works for me ... thanks!!!!

They will release an update with Android 11 for Armor 11 this summer, should i wait for that or is it just to root on? Sincerly the n00b

morwlin said:
They will release an update with Android 11 for Armor 11 this summer, should i wait for that or is it just to root on? Sincerly the n00b
Click to expand...
Click to collapse
Did you update to android11. What are your findings? Android 11 good? bugs?

So let's say I tried the steps above and I somehow ended in a boot loop. For reference, I removed the OS and had TWRP Recovery installed. I restarted while on TWRP Recovery from the phone and I been stuck on Boot Loop since. For whatever reason, for the life of me, I can't remove the battery or figure out how to enter Recovery Mode (I tried so many combinations).
Anyone know how to get into Recovery Mode or find a way to get out of this boot loop? =(
PS: These were the last steps I did:
1) adb reboot-fastboot
2) --- Reboot to bootloader
3) fastboot flash vbmeta vbmeta_null.img
4) fastboot flash recovery recovery.img (The TWRP img)
5) fastboot flashing unlock
6) - Reboot from TWRP on phone after browsing around

dummiedroid said:
So let's say I tried the steps above and I somehow ended in a boot loop. For reference, I removed the OS and had TWRP Recovery installed. I restarted while on TWRP Recovery from the phone and I been stuck on Boot Loop since. For whatever reason, for the life of me, I can't remove the battery or figure out how to enter Recovery Mode (I tried so many combinations).
Anyone know how to get into Recovery Mode or find a way to get out of this boot loop? =(
PS: These were the last steps I did:
1) adb reboot-fastboot
2) --- Reboot to bootloader
3) fastboot flash vbmeta vbmeta_null.img
4) fastboot flash recovery recovery.img (The TWRP img)
5) fastboot flashing unlock
6) - Reboot from TWRP on phone after browsing around
Click to expand...
Click to collapse
Well since this post, I just basically let my phone battery die. With a clear mind, and some help from here (https://forum.xda-developers.com/t/...h-stock-unlock-boot-loader-root-twrp.4297803/) I was able to save the phone (yay!).
I got the ROM and MPD from here: https://www.ulefone.com/support/software-download.html which lead me to their drive for Ulefone Armor 11 5G here: https://drive.google.com/drive/folders/12N1nQVACM4noSO4klyrOk0-sfEnTWMRN
1) Download ROM, SP_MDT_AFterSale_20.32.rar and PDF (RAR and PDF in the "Upgrade tools and USB driver" folder)
2) Follow the steps on the PDF which basically said to scan the port, add the scatter file then start the update. (Read full PDF before trying it)
Hopefully if anyone is frustrated out there, this helps. (I know I was not thinking rationally... lol)
PS: The drive said it might brick your phone with Android 11 but mine worked with Android 11. No issues. So good luck!

Harlock1978 said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
- When done verify the connection with the phone:
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
If you receive a positive answer we can go to next step
- Install patched Boot Image:
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
Done now your phone should be now rooted.
Enjoy.
Have fun
Click to expand...
Click to collapse
Hi, does the VBmeta work for all models? I am trying to root my Ulefone Power Armor 13.

It should, because iy's an empty file.

Harlock1978 said:
It should, because iy's an empty file.
Click to expand...
Click to collapse
Just tried it and it works great! Any idea anyone where I can get TWRP for Ulefone Armor 13? This phone has the recovery in the boot partition

Will this work with Android 11?

I forgot to update my progress. Works great on R (11) so far. Lots of modules seem to be updated too. I am considering using a custom ROM and finally disconnecting from GMS though I would like to retain the customised camera app for,the night vision. I will find a thread that might have a way to do this though if anyone here can help me or point me to the right place, would be much abliged. Also, any ROM recommendations, that are working best?

How To Guide Root Edge 2021 with Magisk

I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted.
Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled.
You should have Lenovo RSA installed which also has needed driver installed. Get the latest ROM from RSA and let it run rescue (phone will be wiped, but bootloader unlock wiped the phone anyway). Doing this in order to grab boot.img from C:\Program Data\RSA\Download\Romfiles\.
You will lose Widevine L1 after bootloader unlocked. Stop if it matters to you.
Are you ready? Let's do it
1. Unlock the bootloader if you didn't do it. The way to get "oem get_unlock_data" is to use mark on command window and copy 5 lines of code and paste on notepad, and make it into one line. Submit to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You should get the code in few minutes over email. Then use this below:
Code:
fastboot oem unlock (code received from email)
(your phone will be wiped]
To enter bootloader. Turn the phone off (make sure you make a backup and copied files to host computer) then press and hold volume down and power buttons.
2. Patch boot.img. After bootloader unlocked, you can stay on bootloader screen and run RSA rescue. Doing this to make your phone up to date as well as getting boot.img. Your phone will be wiped again during the process.
Now you have to do initial setup and install Magisk. Copy the boot.img to the phone and patch it, and copy the patched_boot.img back to host computer.
You can get USNF, fox Magisk Module Manager, Adaway, and other modules if you want.
3. Post root process. You should re-enable USB debug and allow the host computer.
Enter fastbootd
Code:
adb reboot fastboot
or
Code:
fastboot reboot fastboot
Flash patched_boot
Code:
fastboot flash boot
Press space once to make a space, drag and drop patched_boot into command window, and press enter.
Since 24.1, Magisk has different approach to hide/deny.
Enable Zygisk, enforce deny list, install USNF as module (don't worry about GMS because USNF takes care of it).
Put any app can detect root on deny list and reboot everytime you updated the list
Happy rooting

This is my first time rooting an android phone, so thank you. Perhaps I might suggest you add some more details to the "patch boot.img" section, as it took me some extra looking about before I figured out what I was doing.
Thankfully it's pretty simple, I just had to download the Magisk apk from its official github repo onto the phone (post step 1), transfer over the downloaded "boot.img" that the lenovo RSA app downloads during its rescue process (it tells you were it downloads it in the app), over to the phone (usb file transfer), patch "boot.img" on the phone using the Magisk app (install > pick file > done!), transfer back over the newly patched image (stored in downloads) to pc, and then use the above instructions to `fastboot flash boot /path/to/your_patched_boot.img` when the phone is once again put into fastboot mode.
Okay maybe that isn't super simply explained, but I wanted to write it down so others might benefit.
Thank you again, I now have my phone rooted, and will be looking into various things I can do with it, such as degoogling, TWRP (if it's even available for this phone), etc.
---
As far as I know, there is no TWRP yet pre-made for this phone. Unless I'm mistaken, I'd have to manually compile TWRP for my phone? (Not exactly sure how to go about that.)
Also, any tips for a newbie like me?

Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao

ninjakira said:
Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao
Click to expand...
Click to collapse
Yes, this is how I did mine