Database Info

[GUIDE]RCA Maven Pro (RCT6213W87DK), Bootloader, Custom Recoveries, Firmware and Root

SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!!​ (Or ask for help, there's a lot of friendly people around here)​
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader​
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers​
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP​
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT​
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)

Reserved

Reserved #2

Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)

equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.

My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down

GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo

So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?

ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)

NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.

ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery

Okay, I got CWM installed! Now to see if I can find a way to build TWRP...

ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.

NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.

ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo

NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.

Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!

ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...

NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...

ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:

[How-To] Root (Ulefone Armor 6)

Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.

Extosis said:
Story:
I recently bought the, Ulefone Armor 6 Android phone. Didn't do much research into rooting before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Rooting procedure:
1. Get a local copy of the boot.img file from the Ulefone website (To make things simpler for you, Ulefone.com/index.html > Scroll down and click on "download" > Select your device model "Armor series" "Armor 6" > Scroll all the way down and click the download button for "The latest rom".)
2. Now you are at the google drive folder from Ulefone, with the files you need. Select EU if you have the EU version, or Non-EU for any other country.
3. Download the compressed file of your choice EU or Non-EU. (Ex. I downloaded the one for Non-EU which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
4. Open the file in your favorite archiver software, 7-zip, winrar, etc.... open the first folder in the archive, and extract "boot.img"
5. Download, "Magiskmanager.apk" from their Magisk Manager, and install it in your, Armor 6 phone.
7. Pass the, "boot.img" file from your computer to your cellphone. Preferably the "downloads" folder.
8. Open up Magisk manager, and click install 19.3 (or what ever is the current version) then click "Select and Patch a File".
9. Find your "boot.img" file and patch it with magisk manager.
10. After magisk manager has patched your file, pass the patched file, back onto your computer.
11. Now, in your Armor 6 phone, go to settings, scroll down to system and click it, click on about phone, and then tap the crap out of build number, until you become a developer.
12. Go back from about phone, click on developer options, and tick on "OEM unlocking".
13. Scroll down and tick on USB debugging.
14. Download your ADB tools with fastboot from android/google.
15. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
16. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
17. Once you have unlocked your bootloader, reboot the phone "fastboot reboot", wait till the phone boots up, go through the set up process, enable USB debugging again (Step 13), install magisk manager again, adb reboot bootloader in adb command prompt.
18. Once in fastboot mode again, flash the patched boot.img file.
fastboot flash boot boot.img
19. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense.
Click to expand...
Click to collapse
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])

PoochyX said:
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
Upon doing a bit more research, the phone actually has TWRP & a TWRP fork.

How do we know we can trust you? I'm a nubee as I've said.

SteeleB89 said:
How do we know we can trust you? I'm a nubee as I've said.
Click to expand...
Click to collapse
Then this isnt for you and stick with stock... Stock honestly works just certain people want greater freedom with thier phones only issue is with that you yourself at greater risk of breaking something and wouldn't know how to fix it and in situations like that factory restores wouldn't even save you because the system partition doesn't go back to the way it was with a factory restore
Sent from my SM-J327P using Tapatalk

I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.

SteeleB89 said:
I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.
Click to expand...
Click to collapse
Well to start with, I didn't attach anything in this thread, only photos.
1. You bought the phone, a phone that is made from a Chinese company, odds are that it already has malware, backdoors, or things you don't want on the OS.
2. Like I said, I didn't attach anything for you to download, so I am not infecting you with anything. Fastboot even comes with Google SDK.
3. Magisk is a wide known group who release root for the public to download/install. Just like TWRP, clockworkmod, cynaogenmod, etc...
4. If you don't feel comfortable doing this process, then like stated above, you should probably feel safer staying with stock & no root.
As I am sure, everyone who mod their devices are fully aware of the consequences of exploiting their devices. Brinking, killing, or messing something up.
Cheers.

For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?

A.Fitz said:
For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?
Click to expand...
Click to collapse
I have literally used the "driver installer" from the Ulefone website. Install the MTK/VCOM Drivers.
Adb gets detected in TWRP & Fastboot is found on my computer just fine.
My suggestion would be to check if your anti-virus (if you have one) if it's blocking the drivers from being installed.
Ps: I have the latest Windows 10 1903 x64 Edu and the drivers work perfectly.

Will try at end of month and tell you guys the result later.

Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.

Stabys said:
Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.
Click to expand...
Click to collapse
Oh most definitely. I am actually going to add more detail to this tutorial once I have the free time to do so. This tutorial was mainly supposed to be like a rough idea on how to do it. However yes, I did a factory reset not to long ago and root was maintained.
Update:
Added more information and cleaned the thread up.

Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.

Stabys said:
Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.
Click to expand...
Click to collapse
Yeah, I think their new rom has a few security updates as well as other updates.
I haven't updated as of yet, because I fear I will lose root. However if I ever do, I'll update everyone if successful.
I understand you very well too.

Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.

Stabys said:
Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.
Click to expand...
Click to collapse
Hello it's been a while.
I have updated to the latest version by Ulefone for our Armor 6's.
Version: 2019.06.05.
I was able to root it again, using the same method in this thread.
As for the native apps, I haven't tried to remove them, however I am sure it is possible to.

HELP!
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Extosis said:
Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.
Click to expand...
Click to collapse

babyboy_legolas said:
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Click to expand...
Click to collapse
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?

babyboy_legolas said:
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?
Click to expand...
Click to collapse
To put the phone in manual fastboot mode, you have to power off your device first. By pressing both, "power button + volume down button" until you feel the phone vibrate.
Once the phone vibrates, quickly press, "Power button + volume up button" to view the fastboot/recovery/normal boot menu options. To select fastboot use the volume buttons.
Volume up = select
Volume down = move down through options.

Hi!
Oh I tried it once more now and managed to do it.
I did it with the ROM from Mega (20190605).
Thanks again!

[Recovery][Kernel] [8.1] Install TWRP, remove encryption, get Magisk on Visible R2

Disclaimer: This guide and the tools included are provided as-is. Testing has been limited and nothing is guaranteed to work. I take no responsibility for lost data, bricked devices, etc. Continue at your own risk, and please read carefully. THIS GUIDE WAS WRITTEN FOR PHONES ON ANDROID 8.1 - MAY NOT WORK ON DEVICES WITH THE PIE UPDATE.
Note that Magisk and TWRP can interfere with downloading and installing OTA updates. At this time the only updates are security patches, so it would be best to make sure all OTAs are installed before starting.
Mounting and decrypting the data partition is still hit-or-miss. If you haven't set up a passcode or password, TWRP should be able to mount it, and you still might be able to even if you have. Magisk will corrupt encrypted partitions and force a factory reset, and TWRP will not be able to help you back things up if Magisk has been installed before disabling encryption. You've been warned.
Guide: Installing TWRP and Magisk on the Visible R2
Tools:
prog_emmc_firehose_8917.mbn - firehose for flashing system partitions
Latest available TWRP zip - contains TWRP recovery image and the necessary files for flashing
fstab.qcom - for removing forced encryption
Patched boot image - for installing versions of Magisk newer than v16.7
Stock firmware - optional, but handy to have in case something goes wrong.
Windows users: QPST/QFIL and the QDLoad drivers (possibly the first set of ZTE drivers as well, but likely not necessary). Installing drivers in compatibility mode for XP or Windows 7 might help resolve issues.
Install adb if you don't already have it set up.
Linux users: qdl source code; the guide will cover compiling and installing it. You'll also want to install adb from your distro's repositories. There is a snap package for qdl, but it doesn't work for the purposes of this guide, so please don't use it.
Part 1: Installing TWRP
TWRP is an easy-to-use, touch-based custom recovery for Android devices, designed to make backups and installs simple and painless. Unfortunately, the installation of TWRP on the R2 is going to be a little less simple and painless; the device's bootloader isn't locked down, but it doesn't support fastboot commands, meaning we'll need to get our hands dirty to flash partitions.
Before starting, it's also worth noting that the current TWRP build cannot always decrypt encrypted data partitions, and the device is encrypted by default. This means that TWRP may not be able to mount or back up your data partition unless it's formatted and forced encryption is removed (see part 2).
To flash TWRP, we need to put the device into EDL mode and forcibly overwrite the existing partitions using an EDL tool and the firehose linked above, which unfortunately requires a PC of some sort. Enable USB debugging on your phone, then follow the steps for your operating system below.
For Windows:
1. Install the Qualcomm driver package. Before continuing, you will need to make sure Driver Signature Enforcement is disabled on your PC; QFIL may have issues communicating with the device if Windows blocks the driver.
2. Install the QPST package, then open QFIL from the Start menu.
3. Select 'Flat Build' under Select Build Type.
4. Extract the TWRP zip to an accessible directory (something like C:\TWRP works fine). Place the firehose.mbn in the same directory.
5. Press 'Browse' under Select Programmer, then navigate to the TWRP directory and select the firehose file.
6. Press 'Load XML'. Select rawprogram_recovery.xml, then patch0.xml
7. Connect the phone to your PC and make sure USB debugging is enabled. Make sure your PC is trusted by the phone for ADB commands, then send 'adb reboot edl'.
8. If everything went well, the phone should have rebooted with a blank screen, and QFIL should be asking you to select a port. Press Select Port, and then choose (hopefully) the only item available).
9. The 'Select a port' message should now read something like Qualcomm HS-USB QDLoader 9008 (COM#). IF it does, simply press download.
10. There should be some output in the status window, ending a few seconds later with a blue Download Succeeded message. If so, you're done, and can restart your phone. If there's a red error message, or the status window seems to be stuck on sending, double-check that your device is registered properly in Device Manager.
11. Once you're done flashing, you can reboot into TWRP by holding down the Vol Up button as the phone reboots.
For Linux:
1. Unzip the qdl zip into its own directory, then enter the directory.
2. Compiling qdl requires libraries that may not be installed. For Ubuntu users, you simply need to run ' sudo apt install libudev-dev libxml2-dev' to install them; people with other distros should know how to use their package manager and may have to find the packages under a similar name. If any other packages are required (errors compiling, etc.), let me know so I can update this.
3. Actually compiling should be as simple as opening a terminal in the working directory and running 'make && sudo make install'. If you get no errors, qdl should be installed and able to run from any location, and the compile process shouldn't take much time at all.
4. Before running qdl, ModemManager needs to be disabled, as it can interfere with accessing the phone in EDL mode. In Ubuntu (and most systemd-based distros) you can ensure that it's stopped by running ' sudo systemctl stop ModemMangager'. If you need the ModemManager service, make sure to restart it when you're done.
5. Extract the TWRP zip to an easily-accessed folder, like ~/twrp, and place the firehose mbn in the same folder.
6. Navigate to the TWRP folder and open a terminal there. Now would be a good time to plug in your phone and enter EDL with 'adb reboot edl'.
6a. If your phone was already connected in EDL mode before stopping ModemManager, you might need to reboot it and enter EDL again.
7. If you're in the same directory as the TWRP files, you should be able to start flashing by running 'sudo qdl prog_emmc_firehose_8917.mbn rawprogram_recovery.xml patch0.xml'.
8. If everything's good, you should see some output on your screen, and the phone should reboot momentarily. If the command finishes without output, ModemManager or something similar may have interfered. Make sure ModemManager is stopped, reboot your phone into EDL mode again, and try again. If it hangs at Waiting for EDL device, you're not running the program with admin privileges or your phone isn't in EDL mode.
9. Once the process has finished and your phone has rebooted, you should have TWRP installed. Boot into it by holding Vol Up while rebooting.
That's it! Verify that TWRP is working as expected by doing some test backups and restores, etc. Note that TWRP builds for this device are still sort of experimental; decrypting the data partition may not work for some users, and keeping data encrypted while trying to flash Magisk will not work - you will need to wipe and decrypt the device. If you're satisfied just with TWRP, there's not much else you need to do. If you want to run Magisk or decrypt your device for other reasons, keep reading.
Part 2: Removing Forced Encryption
By default, the device encrypts the data partition without input from the user. This is not ideal, and even if TWRP can decrypt and mount your data partition, from my experience Magisk's init process apparently gets things wrong and tries to write to data before its decrypted - whether that's actually the case or not, the fact of the matter is that Magisk has corrupted my data partition every time I've tried to install it while data was encrypted.
DO NOT flash any zip that removes dm-verity and force encryption - these modify the boot and recovery partitions, and the stock kernel doesn't like the way they do it. If you've flashed the patched boot.img first then you'll at least be able to boot to your system partition afterwards, but it'll still nuke recovery even with a custom kernel installed on it. If you're still using the stock boot.img, you'll get boot loops and won't be able to access recovery; your only choice is to enter diagnostic mode, and reflashing anything from that point is a gigantic pain in the ass, so please, just don't. If you feel the need to do it regardless, please please please reflash your boot and recovery images before rebooting.
Counter-intuitively, the quickest and most painless way to stop the device from force-encrypting itself is to modify the fstab on the vendor partition - the boot partition has no fstab files, and the ones in the TWRP recovery image are already set to make encryption optional. Place the fstab.qcom on the phone's microSD card (internal storage will work if you don't have one, as long as TWRP can access your internal storage; if not, use adb push/pull rather than the below commands), boot into TWRP, and adb shell into your device by USB; if done while in TWRP, you should have root permissions. If your PC doesn't see your phone as an ADB-ready device, go to Mount settings in TWRP and tap on the option to disable MTP; after confirming that ADB works, feel free to re-enable MTP. Once ADB is working, run the following commands:
Code:
mount /vendor
cp /vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak
cp /external_sd/fstab.qcom /vendor/etc/fstab.qcom
chmod 644 /vendor/etc/fstab.qcom
umount vendor
.
That's the simple part - you've replaced the fstab on the vendor partition with one that tells the device that encryption is optional, and backed up the original to your microSD as fstab.qcom.bak, just in case. Now you need to actually remove the existing encryption, which will wipe all the user data from the device. If that hasn't scared you out of continuing, read on.
While we're still in TWRP, we need to go to the Wipe menu. From there, we need to Format Data. It'll give you warnings in a scarier color than I did, but you'll have to type yes and continue regardless. Once that's done, hit the back button a couple times before rebooting. Do a standard factory reset, then reboot.
From there, it may take a couple tries for the device to boot normally as it reformats and repopulates the data partition. If you find yourself stuck on a black screen, reboot again, and if it keeps happening, boot into TWRP and then reboot to System from the reboot menu. Eventually, you should be able to get back to the device setup screen, and depending on your security settings beforehand, you may be prompted to enter your PIN, password, or Google account information.
From here, you should be able to mount, backup, and restore your data partition in TWRP without any issues. If you want to go further and root your device, keep reading for the Magisk guide.
Part 3: Any Magisk You'd Like
Note: Magisk and encrypted data partitions do not play nicely together. Follow through Part 2 first, or you'll have headaches.
ZTE's kernel has a custom SELinux plugin called policyproc, which in short doesn't play nice with a lot of things that modify what happens during the kernel's startup sequence. Unfortunately, modifying the startup sequence is what Magisk does best, and versions of Magisk past v16.7 don't play well with the stock kernel.
If you're fine with v16.7, you can download the zip from its Github release page and flash it through TWRP. However, it doesn't support current versions of Magisk Manager or the uninstaller zip, and naturally it doesn't have all the features of newer versions.
This is where the patched boot image comes in. Basically, it's the stock kernel, rebuilt with policyproc disabled, stuffed into the stock boot.img and replacing the original kernel. It's not entirely perfect as ZTE deliberately left out bits of the source, but even working around that, the kernel seems to run fine after nearly a week of testing on my own device. Still, if you run into any issues that don't show up with the stock kernel, please let me know.
So. you can take that patched boot image and install newer versions of Magisk whichever way you'd like. The default method would be to use TWRP to flash the patched boot image, then flash the latest Magisk zip (v20.1 at the time of writing). Alternatively, you could put the patched boot.img on your microSD or internal storage, install the Magisk Manager app, use it to patch Magisk into the patched boot image, then use TWRP to flash the patched-patched-image to the boot partition. Either way should work fine, and honestly I'm hoping if you've made it this far you don't need further instruction on how to get Magisk installed.
Note that on the first reboot after installing Magisk, the phone may reboot again before loading the system normally. I assume this is standard practice for initializing Magisk, but honestly I have no idea.
With that, you've done just about everything you came here to do. If you still feel like tweaking and possibly bricking your phone, however, scroll on down to Part 4.
Part 3.5: Updating Your Magisk Install
When a Magisk update is available, the Magisk Manager app will generally push a notification to you. Letting the manager handle the upgrade is a good way to get bootloops, unfortunately; upgrading requires re-patching and re-flashing the boot image, and most apps running in system mode seem to handle the task poorly on the R2. If you want to update to a newer version of Magisk, it'd be best to reboot into TWRP, flash the 'clean' Magisk-ready boot image, then install the zip for the version of Magisk you want to update to. You don't need to uninstall previous versions of Magisk to do this, and it should be doable even if a previous Magisk upgrade left you stuck in a boot loop. Note that if you previously told the Manager to 'hide' itself, you may end up with two Manager apps after the update; it should be safe to remove either of them, although the one with the Magisk Manager name will need to be re-hidden if you choose to keep it.
Part 4: Going Even Further Beyond - Project Treble and You
Google requires that all Android phones releasing with Android Oreo or newer must support the Treble framework: generally speaking, anything that's 'stock' Android lives on the system partition, and anything manufacturer or carrier specific exists on the vendor partition. This has allowed for developers to create generic system images, or GSI, consisting of particular Android system partitions that should run on a variety of Treble-enabled devices. And wouldn't you know it, the R2 launched with Oreo, and you've got a couple handy methods of writing system images to your device, through TWRP and EDL flashers.
So, does that mean the R2 supports these GSIs? Not really! Honestly, it's more that it's up to curious people to find out. I've been able to get phhussons's Oreo image working, but that's a bit boring on a device that supports Oreo out of the box. A couple more highly modified Pie builds failed to boot properly, either hanging on their splash screen or crashing the display manager before getting through setup.
There's also the fact that they're generally only distributed as sparse system.img files, something I had trouble flashing with QFIL, and up until about 18 hours before this guide went live, the only TWRP build I had for the R2 could only write images to the boot and recovery partitions, not system, so writing them meant I had to decompress them to a standard EXT4 image and then flash them with QFIL, which wasn't a lot of fun to mess with. In short, testing's been pretty limited, but this build of TWRP should make it much easier for anyone to flash whatever image they'd like. If you feel like being a guinea pig, we'd all love to hear the results! If you want to test, you should look for A-only, ARM64 images.
Questions and Issues
My phone is bootlooping after leaving recovery!
If you haven't messed with system partitions in a way that might cause a bootloop, reboot to recovery and try to boot to system from there. If it continues, reflash your boot image (and Magisk afterwards, if necessary, removing the extra Manager app that might pop up in your app tray if you've got Manager disguised in its settings).
I can't access ADB or MTP from recovery.
It happens sometimes, especially in Windows; just toggle MTP on/off from inside TWRP, or unplug and replug your USB cable.
My phone says I need a factory reset, but TWRP just reboots.
This generally happens if something messed with the encrypted data partition. Do not tap the factory reset button on your phone; instead, power off entirely and manually reboot into TWRP by hilding Vol Up while booting. Perform a factory reset (and format data if necessary) from there, then reboot.
(to be populated)
Credits
@deadman96385 - for uploading the tools that made this possible and the stock ROMs that saved my ass more than a few times
@famewolf - for feedback on what did/didn't work in the last guide
@asderdd - for his Axon 7 kernel work which I shamelessly copied to get Magisk working
Anyone who's contributed to Magisk or TWRP over the years, and the maintainers of the moto e5+ device tree for TWRP since I used most of their branch.
Sources
Kernel source, specifically the tree used for the Magisk patch
TWRP device tree

@FEGuy
Attempted to flash the new twrp via zip....acted like it worked but when I when to install section only boot and recovery were options....so I installed the twrp image itself to recovery....rebooted back into recovery and got a black screen. Additional attempts to go into recovery did same thing. I'll attempt to use the flashify app under factory rom to restore previous copy of twrp. It should work as I had magisk going...I think.

That is... not really reassuring. I've suspected the zip flash might not actually work, but I double-checked that TWRP build on my device first.
What's weird is that that's also the only TWRP image I've gotten to boot without dragging it through an AVB signing process. Let me sign that image and reupload it, see if it works any better.

FEGuy said:
That is... not really reassuring. I've suspected the zip flash might not actually work, but I double-checked that TWRP build on my device first.
What's weird is that that's also the only TWRP image I've gotten to boot without dragging it through an AVB signing process. Let me sign that image and reupload it, see if it works any better.
Click to expand...
Click to collapse
Always possible I hosed something....I grabbed the img of the previously good twrp and flashed it via flashify app...said it worked but when booted to recovery got same black screen. I'm about to experiment with the usb drivers you mentioned vs the ZTE USB ones in the op...they conflict with each other so uninstalling old ones.

If the ZTE and QDLoad drivers conflict, I'd probably say keep the QDLoad. I honestly don't remember if I ever installed any ZTE drivers other than the ones that can be served from the phone by USB.
Pretty sure flashify is just broken; I tried it the other day with the same results after flashing a test build that didn't work at all.
I just redownloaded the TWRP from the original link and it worked fine, and there shouldn't be any files or signature tied to my own device, so I don't really know why it wouldn't work on other phones. I've got another one coming in the mail for actual use on Visible, but it won't be here to test on until tomorrow.
In the meantime, try this TWRP. No different other than letting AIK give it an AVB signature, but some of my test images wouldn't boot otherwise. If it works I'll update the zip in the first post.

FEGuy said:
If the ZTE and QDLoad drivers conflict, I'd probably say keep the QDLoad. I honestly don't remember if I ever installed any ZTE drivers other than the ones that can be served from the phone by USB.
Pretty sure flashify is just broken; I tried it the other day with the same results after flashing a test build that didn't work at all.
I just redownloaded the TWRP from the original link and it worked fine, and there shouldn't be any files or signature tied to my own device, so I don't really know why it wouldn't work on other phones. I've got another one coming in the mail for actual use on Visible, but it won't be here to test on until tomorrow.
In the meantime, try this TWRP. No different other than letting AIK give it an AVB signature, but some of my test images wouldn't boot otherwise. If it works I'll update the zip in the first post.
Click to expand...
Click to collapse
If I su from adb and do a dd if=twrp-signed.img of=xxxxxxxxxxx can I overwrite it manually from shell and if so do you know the path I should use to get it to our recovery?
If flashify is broken, twrp is broken and I'm unable to use qdl nor qfil I'm kinda screwed (for the moment). The qdload drivers did not show the device on a com port when in edl mode...the zte ones do but then again I can't write anything. Any ideas what the heck is up with the linux qdl? Even with --debug it says nothing.
---------- Post added at 02:01 AM ---------- Previous post was at 01:48 AM ----------
famewolf said:
If I su from adb and do a dd if=twrp-signed.img of=xxxxxxxxxxx can I overwrite it manually from shell and if so do you know the path I should use to get it to our recovery?
If flashify is broken, twrp is broken and I'm unable to use qdl nor qfil I'm kinda screwed (for the moment). The qdload drivers did not show the device on a com port when in edl mode...the zte ones do but then again I can't write anything. Any ideas what the heck is up with the linux qdl? Even with --debug it says nothing.
Click to expand...
Click to collapse
I tried dd if=twrp-3.3.1-1-z5151v.img of=/dev/block/bootdevice/by-name/recovery and did same with new signed one. I still get black screen when recovery "loads". At this point I'm going to have to get something figured out with qdl or qfil.

Yeah, I wasn't sure if dd was going to work or not.
Try the QDLoad drivers again in Windows, make sure that the device is using them. If it's not showing up as a COM port in device manager, force it to use the proper Qualcomm driver, which on my system installed to C:\Windows\system32\qcusbcer.sys - I don't know if that installed with the QDLoad drivers or with QPST/QFIL itself.
As for qdl, I don't know; it's been hassle-free for me, for the most part. If you're sure you're in EDL mode and not diagnostics or something, an output from lsusb might help diagnose the issue. If the debug flag isn't providing useful info, might as well try it without. I don't know if there's services other than modemmanager that might interfere with qdl, it could depend on distro.
EDIT: I'll also preemptively warn against trying the TWRP app to flash; it'll do about as much good as flashify.

Will tackle it "later" in the morning. Thanks for the quick followup. I might see more clearly in morning when not so frustrated with it. I swear I haven't had this many issues with getting twrp installed in a long time.
*update* Ok so I lied....I completely recompiled qdl from https://github.com/andersson/qdl and it's working as expected..I used it to flash the original twrp. I then used that twrp to flash the twrp-signed.img and rebooted back into it with no issues.
I also flashed your patched boot and it got as far as the blue visible screen after the zte one then hung. I reverted to my nandroid copy of boot.

The Treble pie loaded ok...I did do a factory reset so data would not conflict..it did do one reboot before loading normally. See screenshots.
The First 4 are from when it was initially installed. The later photo's I had added gapps, a few apps, snapped a picture to use as wallpaper and various other minor things. I found it to be faster under treble pie than it was with factory oreo. I haven't found anything that didn't work yet on it.
Launcher: Evie Launcher

famewolf said:
I also flashed your patched boot and it got as far as the blue visible screen after the zte one then hung. I reverted to my nandroid copy of boot.
Click to expand...
Click to collapse
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.

FEGuy said:
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
Click to expand...
Click to collapse
I tried the current installer which failed. I didn't locate the 16.7 uninstaller.
*update* I did finally locate the 16.7 Magisk Uninstaller.

FEGuy said:
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
Click to expand...
Click to collapse
I also installed open gapps pico pie amd64 version on top of the pie rom without issue. I have magisk 16.7 working with treble without issue so maybe it was just the newer versions that had issues?

My 2nd R2 (You are a bad influence) arrived today. Anything you need tested on a stock model? Here's hoping qdl/qfil cooperates 1 last time.
When you were patching the kernel did you see anything that was keeping the phone in LTE only mode for calls? When I get a minute I'm going to put my t-mobile sim into the R2 and see what it will do under the pie rom but since it's still using same kernel I wondered if that would be an issue. We know on the stock rom all calls have to use VOLTE.

I haven't figured that much out yet, unfortunately. I don't know if it's due to the way the kernel is built, or custom libraries distributed on the vendor partition, or what. From what I can tell, the bands are properly unlocked in the NVRAM, and I don't really know enough about modem firmware to make heads or tails of those files.
I will note that for people using the phone on Visible, using a non-stock ROM works for getting around the one-connected-device-per-hotspot limit.

FEGuy said:
I haven't figured that much out yet, unfortunately. I don't know if it's due to the way the kernel is built, or custom libraries distributed on the vendor partition, or what. From what I can tell, the bands are properly unlocked in the NVRAM, and I don't really know enough about modem firmware to make heads or tails of those files.
I will note that for people using the phone on Visible, using a non-stock ROM works for getting around the one-connected-device-per-hotspot limit.
Click to expand...
Click to collapse
Had a couple of thoughts...a quick and dirty method to provide "flash and go" rom's might be to do a nandroid of just system or maybe system and boot for whatever rom and make that available for download. I also know there are methods to convert a nandroid into a flashable zip although I haven't done it before. This was more a thought for folks wanting to go to b12 that already had twrp...simple enough for an existing b12 user to back up system. I have verified swapping between nandroid pie vs stock oreo works ok (assuming you are restoring the right data for each). Also the fingerprint "images" continued to work fine after a restore.....on a previous device when we did a nandroid restore we would have to delete the file storing pin/fingerprints as they wouldn't let you into the phone until re-recorded. It also worked if you remember to turn those OFF before doing the backup....wasn't an issue with the R2. The phone is noticeably more responsive on pie than it was with stock oreo. I'm curious whether you found that to be the case with treble oreo?
Oh minor annoyance....I changed the device id to z5151 which is what it showed under stock but when doing an adb shell the command line is "phhgsi_arm64_a:/" Do you know how to change that? This will change it temporarily till next login: https://stackoverflow.com/questions/33069161/how-to-change-adb-shell-prompt-name-before-the-mark

You could try using setprop as root to set ro.build.product or ro.product.device back to Z5151, or manually edit the build.prop; beyond that, I don't know of a simpler way.

I'm having trouble getting the mobile data working on pie,
I can search for networks and it finds visible but it wont connect.

thanks!!!!!!!!

rangolizardy said:
I'm having trouble getting the mobile data working on pie,
I can search for networks and it finds visible but it wont connect.
Click to expand...
Click to collapse
The visible apn was missing from my pie,
If you're an idiot like me and flashed to pie before backing up "apns-config.xml" then here is the stock one with the visible apn settings: mega(.)nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Remove the () Someone else can maybe post the intact link as i seem to be unable to.
After this 4G works like a charm.

rangolizardy said:
The visible apn was missing from my pie,
If you're an idiot like me and flashed to pie before backing up "apns-config.xml" then here is the stock one with the visible apn settings: mega(.)nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Remove the () Someone else can maybe post the intact link as i seem to be unable to.
After this 4G works like a charm.
Click to expand...
Click to collapse
Posted for rangolizardy: http://mega.nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Any other important tweaks anyone has made to the treble pie image?
Factory Wallpapers are here: https://forum.xda-developers.com/showpost.php?p=79011562&postcount=2

Managed to root but cannot update

Hi!
Xperia ZXP was running the official Firmware fine. Then, I just decided to root. I followed this video:
Got my phone properly rooted.
Now I keep getting notification of an update that I had before but cannot install it. Also, I cannot setup my company work profile as it detects root.
I mainly wanted to use Cheat Engine that why I rooted.
How do I apply latest update?
How do I hide root status?

Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.

bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Is there a place/page here that lists all these tools?

Fix after root effects
bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Here is how I'm going step by step:
Download Flashtool - Done
latest version of Xperifirm - Done
Find latest firmware with Xperifirm. Should end in .107 - Done
-- Download it - Done
-- decrypt it with Flashtool - Stuck
Download Newflasher - Done
-- Unzip Newflasher into the folder you have the decrypted files
Plug your phone into your computer
-- Make sure you have the correct driver - Done
-- Developer option and usb debugging enabled on your phone - Done
Put phone into flash mode and hit newflasher.exe
-- choose "n" for the first two choices and let it run
-- That will give you the latest and final update for this phone
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt

Doomer D. Great said:
Here is how I'm going step by step:
• Download Flashtool - Done
• latest version of Xperifirm - Done
• Find latest firmware with Xperifirm. Should end in .107 - Done
○ Download it - Done
○ decrypt it with Flashtool - Stuck
• Download Newflasher - Done
○ Unzip Newflasher into the folder you have the decrypted files
• Plug your phone into your computer
○ Make sure you have the correct driver - Done
○ Developer option and usb debugging enabled on your phone - Done
• Put phone into flash mode and hit newflasher.exe
○ choose "n" for the first two choices and let it run
○ That will give you the latest and final update for this phone.
• Now use twrp to install the latest Magisk version(search online)
○ also have Magisk manager app(Play Store) on your phone
• Once that's done and you've rebooted phone
• open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
• If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt
Click to expand...
Click to collapse
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.

bobsright said:
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.
Click to expand...
Click to collapse
The latets Xperifirm also extract right after downloading so the decrypt step is not needed.
I'm flashing a I write. I'll be dealing with the next part now:
Now use twrp to install the latest Magisk version(search online)
also have Magisk manager app(Play Store) on your phone
Once that's done and you've rebooted phone
open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything
TWRP has to be flashed or installed from store?

Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.

bobsright said:
Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.
Click to expand...
Click to collapse
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?

Doomer D. Great said:
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?
Click to expand...
Click to collapse
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.

bobsright said:
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.
Click to expand...
Click to collapse
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...

Doomer D. Great said:
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...
Click to expand...
Click to collapse
So Cheat Engine doesn't detect root with Magisk?

bobsright said:
So Cheat Engine doesn't detect root with Magisk?
Click to expand...
Click to collapse
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.

Doomer D. Great said:
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.
Click to expand...
Click to collapse
Oh well, at least you got it updated and working. Maybe it'll take some searching somewhere else to get that other stuff worked out.
Just a side note; I used to work for Sheikh Hamdan bin Rashid Al Maktoum at his Throughbred operation in Lexington.

Excuse me, does anyone know how to root xz premium docomo ubl no ??? Now on Android 9 Pie, please help.

I believe the Japan market version can't have the bootloader unlocked, thus, no root.

How To Guide [Unofficial] Unlocking the bootloader, rooting, and installing TWRP on Nokia 2.2 with Android 11

to moderators: this is my first thread ever, and thought a complete guide like this really has to be done. if it's not right or not in the right place, do what is right
Click to expand...
Click to collapse
Since there are only 3 useful guides about modifying this specific phone, and some really don't answer a few barriers placed in our way by HMD Global and its ridiculous OEM unlocking restrictions (-_-), and also Google probably dropped making OTA updates for it (which was very important to me, because Android 9 and 10 had bugs), I decided to mix them all up (I will give credits, obv) and add some more info I found and create a thread which will work on Android 11, which worked on my phone, not tested on another Nokia 2.2.
Hope it helps y'all!!
Part 0: Preparations
WARNING: Your storage will be wiped completely!! so make sure to back everything you need up before doing anything. Unless you have bricked/soft locked your phone, then in that case you can use MTK Client app to backup userdata.bin (more info on Part 1-2, marked with a )
Requirements:
A good computer
Obviously a network connection on your computer for downloading files, and on your phone if you wanna update thru OTA
USB cable, capable of transferring data, and without any annoying repeated disconnections or "has to be put in the right angle and position". Just use a fresh one
VCOM and adb drivers, which can be a little annoying getting them to work. Best option is to install 15 seconds minimal ADB and make sure you say Yes when it asks if you want to install device drivers.
Android SDK Platform tools, which can be downloaded from here (NOTE: You have to use Platform tools. minimal adb will NOT work with fastboot on this device. So go to C:\adb and delete everything in there, then extract platform tools in that folder instead)
and the most important of them all: MTK Client by Bkerler which can be downloaded from here. Follow the installation instructions in the link, install Git and Python and also usbdk installer featured in the Github instructions for MTK Client
All done? Great! moving to the next part
Part 1: Unlocking the bootloader
The most annoying part. Thanks to hikari_calyx for their awesome guide on how to unlock the bootloader for this phone. We will follow it step by step until we reach step 6, where we are about to flash all those backed up img's back using mtk-su. Here's the problem, you can use mtk-su only on Android 9. it doesn't work on Android 11 sadly. so we just make sure we have unlocked sec1.img and seccfg.img in a safe place, then install a fresh stock Android 9 rom om our phone with any method we are most comfortable with, like SP Flash tool like in the guide, or booting into recovery and sideloading thru adb or from sdcard. just search the net and I'm sure you will find a loooot of sites explaining how you can flash a stock android on your phone. Just make sure you won't mess IMEI and Serial Number up!!!
**There is a "unlock bootloader" option in the flash tools tab of MTK Client. haven't tried it out myself but you can give it a try**
Extra: Booting into stock recovery
There is another detailed guide on how to enter recovery mode, by foobar1123321 which you can see in here. You might need it to apply updates to your phone
After flashing and updating your OS to latest version of Android 11, it's time for Unlocking the bootloader again. but sadly, Unlocked OEM doesn't let OTA updates to be received, and trying to flash sec1.img and seccfg.img on Android 11 is not possible without root, and root is not possible without OEM unlocking :\
So here comes the neat part, MTK Client
Part 1-2: Unlocking the bootloader again
Go to the folder where you installed MTK Client (hopefully you know how git works and got it cloned and working, if no, then read Installation instructions carefully in their Github page), and open a CMD window there by typing in cmd in the address bar. then write python mtk_gui and hit enter. Do not use mtk_gui.bat since it will close the cmd and not work. Do NOT close this cmd tab. After a while, the app will start and asks you to connect your phone.
Shut down the phone, and after 5 seconds, press and hold both volume up and down keys (without the power button) and connect the phone to your computer via cable while still holding the volume buttons. If you have installed the drivers successfully, then you'll see some texts generate in the cmd window, and will (probably) wait for the Preloader VCOM.
you can let go of the volume keys.... but not for so long. Disconnect the USB cable, hold volume keys, and connect the phone again and you'll see that MTK Client successfully gets access to your phon. YAAAY!!
now you can let go of the volume keys
Go to "Read partitions" tab, and select Boot_a, Boot_b, sec1, and seccfg (make sure you wouldn't mistake them with unlocked sec1 and seccfg)
And then click on Read partitions button in the right side, and choose a location to save these partitions
You can also check userdata, if you have bricked/soft locked your phone and wanna backup your Internal storage data. You can flash it again with this app after you have fixed your phone. and if the problem wasn't caused by your data, you can use them again like you never wiped your phone
After everything is backed up, go to "Write partitions" tab, and find sec1 and seccfg, click on "set", browse and select the respective unlocked partitions we got in Part 1 (you may need to change their extension from .img to .bin for them to show up)
Click on "Write partitions", and done! You have unlocked your OEM on Android 11!! and if everything is done correctly, you'll see
Orange state Your device is unlocked and cannot be trusted Your device will boot in 5 seconds...
Click to expand...
Click to collapse
or something like this when powering it on, congrats!!
Part 2: Installing TWRP
from the official TRWP page for Nokia 2.2, download the latest TWRP image file and move it to c:\adb on your computer and rename it to twrp.img
you will also need to download a stock vbmeta image, which can be found here or simply by reading it from your phone via MTK Client (there will be two A/B partitions, any of them works) and rename the downloaded/grabbed file into vbmeta.img and move it to c:\adb
power off your phone, then boot into fastboot by holding Volume down + Power for a few seconds, until it says FASTBOOT MODE => then connect the phone to a PC, and write:
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
and then
fastboot flash boot twrp.img
Click to expand...
Click to collapse
Now we have the latest TWRP on our Nokia 2.2 , but seems like accessing TWRP is only possible by either rebooting to recovery when the phone is powered on, via Magisk, Termux, or any other app with power options (after rooting the phone), or writing this when the phone is in fastboot mode:
fastboot reboot recovery
Click to expand...
Click to collapse
You can use TWRP and all of its awesome features now, except for MTP, backup, reading userdata partition, etc. to fix that, you gotta wipe internal storage, so make a backup of your files before processing.
**IMPORTANT: Do not flash TWRP after rooting the phone or it will unroot it**
Part 3: Rooting via Magisk
I'm gonna use Magisk because... it's better than other SU apps. Get it from here and install it on your phone. Now that you have your OEM unlocked and boot partitions too, you just have to copy the partitions we got via MTK Client on your device, launch Magisk app, select Install Magisk, then choose a file, which is gonna be Boot_a.
Wait until patching is finished, and after it's done, go into downloads folder and rename it to Boot_a or you will get confused later
After that you can choose Boot_b to be patched, and after it's done, rename it to Boot_b too
Copy them both to C:\adb from your phone to your pc, and power off your phone
after you get sure device is not connected to the computer via cable, and is powered off, hold down the volume down key with power button, until your phone boots into fastboot mode
Now open a cmd in C:\adb, and write
fastboot flash boot_a boot_a.img
fastboot flash boot_b boot_b.img
Click to expand...
Click to collapse
when done, disconnect your device, and restart. You can check the Magisk app, and realize you now have superuser permissions!!!
**UPDATE** Part 3-2: Hiding Magisk
Hiding Magisk and bypassing SafetyNet is another challenging problem on this phone. Cause when you try to Hide the Magisk app, you'll come to a simple "Failed!" error which is most probably caused by SELinux status. To fix this we gotta install some modules
First of all, install Busybox from Google Play or any other source. It's not necessary, but it's good to have. simply just install it, no need to restart
Then we need to install a module called SELinux permissive (wow, how unique ;w; ) by evdenis, which can be found here. download the zip in your phone, open the Magisk app, and in the modules tab browse for our newly downloaded zip and wait until the operation is done. Reboot your phone, and you are now able to hide Magisk app without any problem.
So do so, open Magisk -> settings -> hide the Magisk app. Choose a name (settings by default) and wait until app launches itself, asking you to add a shortcut to your home screen (optional). This way, your Magisk app now has a random package name and signature and can't be detected by other apps. Now moving to the next part
Bypassing the SafetyNet:
First, in Magisk settings, enable Systemless hosts. it will add its module to the modules tab. check if it's enabled
Then toggle Zygisk in Magisk settings, and restart your phone again (2 restarts? alright no problem)
Once your phone booted up, on the main screen of Magisk, check if it says Yes in front of Zygisk. if yes, than congrats! we are not down yet tho
Go to Magisk settings and toggle Enforce DenyList, don't reboot for now (yes, there is a 3rd one coming ), but go to Configure DenyList and choose the following apps
Google Play Service
Google Play Store
Google Service Framework
Google Play Protect Service (which is probably not present, but wrote it just in case it is on your phone)
Click to expand...
Click to collapse
and also you can choose your banking apps, or any app that prevents you from using them like Netflix or some games. Now you gotta restart (third time is the charm )
Now we gotta install another module which is Universal SafetyNet fix by kdrag0n which can be found here. Download it to your phone, choose it in Magisk module browser, wait for it to finish, and restart (I'm losing my control!!! Hmph!)
Now that we did all this, we have to clear data of apps in our DenyList so they would never remember if we ever had root or no
Go to settings (the actual settings, not our now hidden Magisk app) -> Apps -> all apps -> tap the 3 dots on top -> show system apps, then find all the apps you added to your DenyList and clear their data (not cache, data itself)
Now that this is down, restart your phone ((╯°□°)╯︵ ┻━┻) it's the last time, so you can stop raging now (┬─┬ノ( º _ ºノ))
Now we can install an app like YASNAC and run SafetyNet attestation, if the results showed two pass checks, Congratulations, you bypassed SafetyNet!!!
Totally worth the restarts. (Thanks to Droidwin for their article)
And that's it!! Hope you enjoy your now rooted Nokia 2.2 phone with Android 11

Great guide, and yes mtkclients unlock will work but it may put Ur device into verity eio mode

¿Can I use the Part 3-2 to hide Magisk in Android 9 instead of 11?, I find stock Android 11 very laggy and unstable on my phone (using the camera on any app can take from 1 to 3 or 4 tries to get it working, for example), and Android 9 has served me waaaaay better. However, my banking app refuses to work with root.