Database Info

[GUIDE] How to flash a custom recovery and root a Nokia 6 Retail Phone

WARNING: This method currently doesn't work on Nokia 6 TA-1000 with latest Android O Update! Finding workaround.
Workaround found on leaked Android 8.1 Update, with Magisk Systemless Root Method.
ROOT YOUR PHONE MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
You can download new recovery from this post: https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
Changes in new TWRP Recovery 3.2.1-0:
1. Add English Interface.
2. Use Magisk ROOT instead of SuperSU ROOT.
3. You can backup EFS. However you can't backup modem or the procedure will break.
Thanks to @xinkid 's effort, we can finally root Nokia 6 on Android Oreo again.
Procedure for non TA-1000 users:
0. Backup your phone and remove your lock screen password before proceed! If your phone get stuck at "Powered by Android" splash after the procedure, you may need to format userdata.
1. Sideload the PLE-372B ota package in recovery, which you can download from here:
https://forum.xda-developers.com/nokia-6/help/nokia-6-ota-update-ddls-t3721424
Refer this guide's part 2 to downgrade.
https://forum.xda-developers.com/nokia-6/how-to/guide-upgrade-downgrade-nougat-oreo-t3752393
2. Flash the service bootloader and grant service permission
Reboot to bootloader, then flash the service bootloader with following commands. Service bootloader file (D1C-emmc_appsboot.mbn attached in this topic)
Code:
fastboot oem dm-verity [md5_of_your_device_serial_number]
fastboot flash aboot D1C-emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem dm-verity [md5_of_your_device_serial_number]
For example, if your serial number is PLEABCD123456789, and the md5 checksum of your serial number is 5f47b9a8dc1da1873c12945cf806691e, then type this command:
Code:
fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e
fastboot flash aboot D1C-emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e
You can google a website to calculate md5 checksum of a string.
3. Reflash newer firmware basis to your phone except aboot
After you grant service permission, Extract the newer one OTA package on your PC, in this case, PLE-558B.
Everything you need are placed at firmware-update folder that you extracted.
Take PLE-558B for example, type these commands (commands need to be changed if newer firmware released):
Code:
fastboot flash sbl1 D1C-0-558B-sbl1.mbn
fastboot flash keymaster D1C-0-558B-keymaster.mbn
fastboot flash devcfg D1C-0-558B-devcfg.mbn
fastboot flash cmnlib64 D1C-0-558B-cmnlib64.mbn
fastboot flash rpm D1C-0-558B-rpm.mbn
fastboot flash tz D1C-0-558B-tz.mbn
fastboot flash cmnlib D1C-0-558B-cmnlib.mbn
fastboot flash modem D1C-0-558B-NON-HLOS.bin
fastboot flash dsp D1C-0-558B-adspso.bin
fastboot flash default_nv D1C-0-558B-NV-default.mbn
fastboot flash persist D1C-0-558B-00WW-persist.img
fastboot flash hwcfg D1C-0-558B-hwcfg.img
fastboot flash mdtp D1C-0-558B-00WW-mdtp.img
fastboot flash systeminfo fver
fastboot flash sec D1C-0-558B-sec.dat
fastboot flash cda PLE-00WW-013-cda.img
You'll also need the boot img in the extracted ota package:
fastboot flash boot boot.img
Then flash the custom recovery:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
Power off your phone (case sensitive). Disconnect your phone after execute this command:
fastboot oem HALT
4. Connect your phone to a charger. When charging animation appears, press and hold Volume Up and Power until you see "7to.com" logo. Tap the white cog to choose English language, tap Advanced - Magisk Root, and wait for the procedure complete.
========================SEPARATOR====================
This new guide is only based and tested on Nokia 6 TA-1000. Non TA-1000 (e.g. TA-1021) users need to find their own old OTA package to downgrade.
1. Downgrade the bootloader according to this guide: https://forum.xda-developers.com/nokia-6/how-to/guide-upgrade-downgrade-nougat-oreo-t3752393
If you've flashed my homebrew Android O firmware, skip this step.
2. Use old method below to flash the new recovery again. You must use this recovery, otherwise you can't mount and root.
If you've flashed my homebrew Android O firmware, type this command will allow you to flash recovery:
Code:
fastboot-android oem dm-verity (your_serial_number's_md5_checksum)
3. Use old method below to enter recovery. To load English interface, tap the white cog on the top-right corner, then tap "English" and OK button, just wait few seconds.
4. Tap "Advanced" - "Magisk ROOT" and swipe.
5. If you meet recovery loop after rooted, flash the package misc_initial.zip attached below to escape from recovery loop.
That's it. It's not recommended to receive any newer OTA update since it will overwrite bootloader to patched state.
If you're using TA-1000, you can also try to flash Android 8.1 Homebrew Firmware before rooting.
I'm sorry if you found the guide looks confusing.
Following method for Nougat is archived, only for reference.
Yesterday, I got my own Nokia 6 Retail Phone. Since I’ve already rooted Nokia 5, 6 and 8 Prototype, now it’s time to find out how to root retail Nokia 6 without involving risky Qualcomm EDL Mode.
It works on any variant of Nokia 6 in theory, but I only tested it on D1C/TA-1000.
If there’s a custom recovery for Nokia 2/3/5 released, the guide also works on them. But I’ve tested it on a Nokia 8 retail phone, it doesn’t work on it.
To Nokia 7 and 8 Users, You may want to read this topic: https://forum.xda-developers.com/showthread.php?t=3729396
Click to expand...
Click to collapse
First, you need to download OFW of Nokia 6, install OST LA and patch it.
You can download them from here: https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
(Although the link is for Nokia 8, firmware for Nokia 6 is still available)
如果你是中国用户，诺6固件的下载和使用方法请看本文：
https://www.ithome.com/html/android/328333.htm
Click to expand...
Click to collapse
If you own an unlocked prototype device, just skip to step 6.
Click to expand...
Click to collapse
1. Open OST LA from INSTALLATION DIRECTORY DIRECTLY instead of Start Menu.
2. Load your OFW you downloaded with extension name nb0.
3. Power off your phone, then connect it to your PC. This will boot your phone to “Download mode” directly, in fact it’s fastboot mode.
4. Click “Edit Phone Info” on OST LA. This will load a service purposed bootloader. When your phone reboots and re-enters the Download mode, the service purposed bootloader is now loaded.
5. You can close OST LA when it prompts “Boot FTM mode fail”, or just kill it in task manager if it’s not responding.
6. Open a command prompt or PowerShell in OST LA Installation Directory, then execute this command to flash a custom recovery:
Code:
.\fastboot-android flash recovery E:\recovery.img
I assume that you put the custom recovery in drive E and named as recovery.img.
You can also use your own fastboot if you want, but I’ll prefer the one provided along with OST LA.
I used the recovery from here: https://forum.xda-developers.com/no...veryteamwim-recovery-project-nokia-6-t3650499
7. Type this command but do not execute right now:
Code:
.\fastboot-android reboot
8. Now this step is a little tricky. Press and hold [Volume Up] and [Power] on your phone, then execute the command above at the same time. DO NOT RELEASE both keys on your phone until your phone entered the custom recovery.
9. Now your phone has entered a custom recovery. In this example, we’re using TWRP from Chinese 7to forum, only Chinese is available. I believe most of members on XDA can’t read Chinese, so I’ll attach screenshots. Simply tap “Advanced” – “SuperSU ROOT” will root your phone. If you prefer your own root zip update package, tap “Install Zip” then flash your own zip package in your storage, or tap “Advanced” – “ADB Sideload” then use ADB to sideload a zip package.
You can install the Materialized Theme for TWRP to get English interface from https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 by @z31s1g
Click to expand...
Click to collapse
Currently, DO NOT FLASH Magisk, or your phone will brick as Qualcomm 900E.
You can only use Magisk Root method in latest Android O Update, which I'll cover later.
Click to expand...
Click to collapse
10. After your phone rooted, you can reboot your phone. DO NOT INSTALL ANY OTA UPDATES OR YOUR PHONE WILL GET STUCK AT STOCK RECOVERY, but I’ll recommend you to disable automatic update in settings.
That’s wraps up the whole guide. Please do feedback if there’s something wrong.
Here' the video of how to root a Nokia 6: https://youtu.be/24b-49qTheg
Special thanks:
@blackpanther0582 for Nokia 3/5/6/8 Official Firmware.
@xinkid from Chinese 7to forum for his TWRP.
@hawwin88 for providing info about adding English Interface to recovery.
UPDATE: Uploaded the SuperSU ZIP (verify-xinkid.zip) used in this recovery.

Thank you it worked on nokia6 ta-1000 chinese. I rooted the phone successfully

Finally!
Boy O Boy!
Finally, after a long, long wait, Got my Nokia 6 Rooted! (TA-1000)
Thanks a LOT, Man! :good:

Anyone tried it on any other variant yet?

Hi .i am 1st root my ta1021 with Android 7.1.2 .f**k me
but your method have some problems ...
1. I can't find powershell or anything else in ost la folder.
2.fastboot-android not working....
Now I want complete your method from 6.
6. Before you must install adb and fastboot tools and drivers and use command prompt ,
copy recovery.img to drive c
After ost la changeing phone to edit mod wait 10 second and type this command
Fastboot flash recovery c:\recovery.img
And after flashing completed hold both volume+ and power button and type this command
Fastboot reboot
Don't release buttons and after few seconds you enter Chinese recovery swipe it to right and use screen shots to root your device, after that reboot to system you can find it from screenshot, it go to download mod and then type
Fastboot continue
And enter congratulations, your phone go to normal boot.
Bla bla super su installed....
Thanks, hikari_calyx. For this thread..
Some errors happend when I use rill but after reboot again it is not happening....

same6630 said:
Hi .i am 1st root my ta1021 with Android 7.1.2 .f**k me
but your method have some problems ...
1. I can't find powershell or anything else in ost la folder.
2.fastboot-android not working....
Now I want complete your method from 6.
6. Before you must install adb and fastboot tools and drivers and use command prompt ,
copy recovery.img to drive c
After ost la changeing phone to edit mod wait 10 second and type this command
Fastboot flash recovery c:\recovery.img
And after flashing completed hold both volume+ and power button and type this command
Fastboot reboot
Don't release buttons and after few seconds you enter Chinese recovery swipe it to right and use screen shots to root your device, after that reboot to system you can find it from screenshot, it go to download mod and then type
Fastboot continue
And enter congratulations, your phone go to normal boot.
Bla bla super su installed....
Thanks, hikari_calyx. For this thread..
Some errors happend when I use rill but after reboot again it is not happening....
Click to expand...
Click to collapse
If you're running Windows Vista or Windows 7, you can open a command prompt from installation directory by click right button on the mouse while holding Shift key on the keyboard.
If you're running Windows 8/8.1 or Windows 10, you can open a command prompt or PowerShell from the left corner "File" button. Administrators privilege is optional.
Also, as I mentioned:
You can also use your own fastboot if you want.
Click to expand...
Click to collapse

IDK but you should have change/put the title of this topic as Nokia 6 - TA 1000 (Chinese variant) rather than Retail Phone.
Well, getting root is definitely a temptation but since I'm just a noob and the HMD hasn't release any official firmware/tool yet to recover the phone if thing goes wrong, I guess I'll wait a little bit longer then.

lips_1234 said:
IDK but you should have change/put the title of this topic as Nokia 6 - TA 1000 (Chinese variant) rather than Retail Phone.
Click to expand...
Click to collapse
As I mentioned on the topic, it works on any variant, not only China Variant TA-1000 and Hong Kong Variant TA-1003.
 @same6630 tested on a TA-1021 which is a global variant.
lips_1234 said:
Well, getting root is definitely a temptation but since I'm just a noob and the HMD hasn't release any official firmware/tool yet to recover the phone if thing goes wrong, I guess I'll wait a little bit longer then.
Click to expand...
Click to collapse
HMD released official firmware of Nokia 6 of course, and it's needed to flash a recovery.

Mine
I got some screenshots....

Did someone successfully rooted his Nokia 6 TA-1033?

So just to be clear before I do this to my TA-1000; how do I go about to update it later if I want to update it? For example, my TA-1000 still don't have the 7.1.2 update, and the 8.0 update coming later would be something I want as well.
Do I just update through zip files, or will I simply not be able to update?

Make.Sense said:
So just to be clear before I do this to my TA-1000; how do I go about to update it later if I want to update it? For example, my TA-1000 still don't have the 7.1.2 update, and the 8.0 update coming later would be something I want as well.
Do I just update through zip files, or will I simply not be able to update?
Click to expand...
Click to collapse
After you rooted your phone, you're not able to install any update until you reinstall stock rom.

[THEME][TWRP] TWRP Materialised
U can also install theme for your chinese twrp and you will show english language ...
download theme from this thread
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584

hawwin88 said:
U can also install theme for your chinese twrp and you will show english language ...
download theme from this thread
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
Thanks for providing info!

When I try to flash the recovery.img through command I have this:
...etc
FAILED (remote. Partition flashing is not allowed)~
finished. ´
etc...
Im using a TA-1033, unlocked UK version.
Can anyone help me, please.

wolfpower95 said:
When I try to flash the recovery.img through command I have this:
...etc
FAILED (remote. Partition flashing is not allowed)~
finished. ´
etc...
Im using a TA-1033, unlocked UK version.
Can anyone help me, please.
Click to expand...
Click to collapse
maybe u are not in bootloader mode .. try to reconnect ur phone again and tap "edit phone" on OST LA software
or try to type this in command :
"fastboot reboot-bootloader"

hawwin88 said:
maybe u are not in bootloader mode .. try to reconnect ur phone again and tap "edit phone" on OST LA software
or try to type this in command :
"fastboot reboot-bootloader"
Click to expand...
Click to collapse
When I connect my TA-0033 it enters in Download mode, when I press "Edit phone", the device continues in download mode and the OST LA software goes unresponsive.
Im using a TA-0033 with 7.1.2 N

done!!!! thank you my good friend!!!! i've just installed the recovery AND ROOT MY TA-1021 with english theme. only a question. without pc what is the best way to reboot in recovery mode nokia 6? when i'ts time to update to oreo, i've only just click to restore in: setting=>backup and restore?? thanksssssss

canapo92 said:
done!!!! thank you my good friend!!!! i've just installed the recovery AND ROOT MY TA-1021 with english theme. only a question. without pc what is the best way to reboot in recovery mode nokia 6? when i'ts time to update to oreo, i've only just click to restore in: setting=>backup and restore?? thanksssssss
Click to expand...
Click to collapse
I recommend you to install Xposed and GravityBox for Nougat to enable Reboot to Recovery option.

hikari_calyx said:
I recommend you to install Xposed and GravityBox for Nougat to enable Reboot to Recovery option.
Click to expand...
Click to collapse
I just got Nokia 6 TA 1021 android 7.1.1, Build is 00WW_3_320. Can your method also work for it?

[Guide] Install Magisk on your device, updated to handle OTAs easily

[Update in 1st September 2018] Magisk v17 stable has been released, so the August security update: a new method, more OTA-compliant, is written.
Hi all, this section is quite gaunt, so I'll post my experience on unlocking and rooting my brand new Mi A2 Lite.
I'm not responsible if you make some mistake and accidentally transform your phone in a stone (but it's almost impossible)... <3
How to root
0. You need "debug usb" and "oem unlock" enabled under "developer options" on phone's settings.
1. First, if you don't have already done it, unlock phone's bootloader:
Code:
adb reboot bootloader
fastboot oem unlock
ATTENTION: THIS WILL WIPE YOUR DEVICE, ALL USER DATA WILL BE LOST! And no, when you'll have finish this guide, you can't lock it again (each lock-unlock operation will wipe the device)
2. Download ROM system image from official site. Pay attention to download the corresponding version of your actual OS (look in system settings your current build number).
3. Extract "boot.img" from the just downloaded archive and put somewhere in your device (e.g. in a microSD, just remember where you put it).
4. Download and install Magisk Manager apk.
5. Open Magisk, choosing "yes" when it asks to install Magisk-v*.zip, then choose "patch boot image" and select "boot.img" copied in step 3.
6. At the end of patching process, Magisk will tell you where "patched_boot.img" is been stored, keep a note on it and close.
Now's the updated part, that will make possible to apply OTAs:
7. Copy "patched_boot.img" on your computer, then run this on a terminal:
Code:
adb reboot bootloader
fastboot boot patched_boot.img
fastboot reboot
This will temporarily give you root privileges (until next reboot).
8. Magisk Manager can now make the root permanent: open it and tap "Install", then "direct install (recommended)". This way (instead of flashing directly patched_boot.img) Magisk Manager can remove and reinstall root privileges directly.
9. Just to be sure that your phone doesn't install updates without your acknowledgement, go to Developer Options and disable "Automatic system updates".
Ta-dà! Now you should have Magisk permanently installed (you can check it re-opening Magisk Manager).
-------------------------------------------------------
Time to update? Here's how
If you've followed what is written above, applying an OTA should be quite easy now.
a. Go to Magisk Manager → Uninstall → Restore Images. Do not reboot now or you will have Magisk uninstalled!
b. Now go to Settings → System → System Update and apply OTA. If it fails you've some tweak on system partition that you've forgot to remove, so try to figure it out and retry. Wait for the installation to complete. DO NOT RESTART NOW.
c. Open Magisk Manager again and press Install → Install to Inactive Slot.
d. Reboot and enjoy
-------------------------------------------------------
Troubleshooting
- If your phone seems bootlooping, try to switch it off and on again (sometimes it doesn't start on first boot). If it keeps doing that, donnoh, reflash original "boot.img" and start again!
- For someone seems that Magisk 16 doesn't work well, but since the stable branch has reached 17.0, just use it!
- If you already have rooted your phone in different ways that this one explained here (and you don't have "uninstall" option on Magisk Manager), I suppose that the simpliest way to follow this guide is to reflash factory boot.img and start from the beginning of this post again, but if you figure out alternative ways, post them here!
-------------------------------------------------------
References
https://forum.xda-developers.com/mi-a1/how-to/mi-a1-monthly-updates-t3750419
https://forum.xda-developers.com/showpost.php?p=77448469&postcount=49
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Thanks to BubuXP for the efforts that he puts in this thread, helping anyone who's got problem following this guide.
Have a nice day!

If you posted this a couple of hours early, I'd save a couple hours of my life doing other things instead of discovering by myself what you just wrote :laugh:
However, add to your guide to change the update channel in Magisk Manager to "beta" instead of stable, because only starting from 16.7 (the actual beta version) has support to A/B partitions scheme (the one used by our device). When the new stable version of Magisk will be released, that could be removed.
Add also that installing modules isn't possible out of the box, because both Magisk Manager and Android stock lack the unzip binary (I'm searching for a solution).

few minutes has past and Im looking here at endless boot animation:/
so I do fastboot factory flash, did it again and now no issues at all,thanks!

BubuXP said:
If you posted this a couple of hours early, I'd save a couple hours of my life doing other things instead of discovering by myself what you just wrote :laugh:
However, add to your guide to change the update channel in Magisk Manager to "beta" instead of stable, because only starting from 16.7 (the actual beta version) has support to A/B partitions scheme (the one used by our device). When the new stable version of Magisk will be released, that could be removed.
Add also that installing modules isn't possible out of the box, because both Magisk Manager and Android stock lack the unzip binary (I'm searching for a solution).
Click to expand...
Click to collapse
That's weird, (saw also your message in the other thread)I didn't had all these issues and I'm using magisk 16.0 (no beta). I could also install modules out of the box without having to do anything special
Edit : added quote

I had another ROM installed,It was more "light" than this one posted here. Many google app was added after I did flash. My phone should be global version and I buy it from local store. It was ODLMIFF also.
edit:seems that screen cast is not working

kidoucorp said:
That's weird, (saw also your message in the other thread)I didn't had all these issues and I'm using magisk 16.0 (no beta). I could also install modules out of the box without having to do anything special
Edit : added quote
Click to expand...
Click to collapse
That's weird indeed...
I've re-downloaded the fastboot image and I'm flashing it right now, then I will retry patching boot.img
I found an updated 16.7 version in the Pixel 2 XL forum that fixes some weird behaviors other users had., I will try it too.
EDIT 1: I usually do all my operations under Debian Linux. This time I used the Mi Flash tool under Windows, and I patched the boot.img with 16.0.
I don't know what of the two changes fixed the problem, but now it's working without problems (but the first time I tried directly with your boot.img patched with 16.0 and it was not working ).
FYI, sha512 of the old and new fastboot image downloaded were the same, so it was not a problem of defective download.

BubuXP said:
That's weird indeed...
I've re-downloaded the fastboot image and I'm flashing it right now, then I will retry patching boot.img
I found an updated 16.7 version in the Pixel 2 forum that fixes some weird behaviors other users had., I will try it too.
Click to expand...
Click to collapse
Im using 16.0. Also phone sometimes wont boot, stuck at screen with unlocked text or stuck in boot animation. I guess xiaomi is very wrong choice for somebody who want customize his android:laugh:

mik.y said:
Im using 16.0. Also phone sometimes wont boot, stuck at screen with unlocked text or stuck in boot animation. I guess xiaomi is very wrong choice for somebody who want customize his android:laugh:
Click to expand...
Click to collapse
I edited my previous post, just to inform you.
I think those problems arise because the phone is too young, many things have to be fixed by Xiaomi. And also things will get better when the new stable Magisk that will support new Android features will be released.

1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that

I'm not sure, but apparently I found the culprit.
The only way to make Magisk work flawlessly is following the guide in the first post.
I mean, if I use the patched_boot.img made in another phone it causes always some problems, as if Magisk in the process of patching the boot.img put a signature of the actual phone inside the img and it will work fine only in the same phone that created the patched boot.img
Not only this, but if I flash the phone with the stock ROM via fastboot, and then use the patched_boot.img created previously on the same phone before flashing, it won't work neither (something in the "signature" changes, like it is a new phone).
kidoucorp said:
1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that
Click to expand...
Click to collapse
Probably using the beta channel with 16.7 could improve your situation. I'm using 16.7 right now, following the OP guide, and it is working great (until now).

BubuXP said:
Probably using the beta channel with 16.7 could improve your situation. I'm using 16.7 right now, following the OP guide, and it is working great (until now).
Click to expand...
Click to collapse
I can confirm that I'm using Magisk stable 16.0, and everything works fine, but I suppose it's because I've flashed booth partition A and B. I've updated the first post anyway, thanks!
kidoucorp said:
1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that
Click to expand...
Click to collapse
My old Mi A1 does the same too, it's a bit strange but once you know it, you can handle it

It works !!
Device: Mi A2 Lite (4/64GB) global version.
(cpu-z reports: Snapdragon 626 @2.02 GHz)
Using Magisk 16.7 and boot.img from global rom "V9.6.4.0.ODLMIFF (Android O) " (oem rom from xiaomi).
Only difference is the method which I tried and fail initially, was I cmd "adb reboot bootloader" from the PC which doesn't work for me.
It says failed to write boot_a and boot_b.
I had to do the hardware reset to get into fastboot. (pressing vol-down and power button simultaneously).
Once I am in fastboot mode, from the PC cmd execute the following sequence
1. fastboot flash boot_a patched_boot.img
2. fastboot flash boot_b patched_boot.img
3. fastboot reboot
And voila!, it works beautifully. Thanks for all the contributors of this thread
It runs all apps including apps that cannot be rooted. (have to do the "hide" magisk)
So far so good, no issue to be found.
Have a great day people.

eddiechanks said:
Device: Mi A2 Lite (4/64GB) global version.
(cpu-z reports: Snapdragon 626 @2.02 GHz)
Using Magisk 16.7 and boot.img from global rom "V9.6.4.0.ODLMIFF (Android O) " (oem rom from xiaomi).
Only difference is the method which I tried and fail initially, was I cmd "adb reboot bootloader" from the PC which doesn't work for me.
It says failed to write boot_a and boot_b.
I had to do the hardware reset to get into fastboot. (pressing vol-down and power button simultaneously).
Once I am in fastboot mode, from the PC cmd execute the following sequence
1. fastboot flash boot_a patched_boot.img
2. fastboot flash boot_b patched_boot.img
3. fastboot reboot
And voila!, it works beautifully. Thanks for all the contributors of this thread
It runs all apps including apps that cannot be rooted. (have to do the "hide" magisk)
So far so good, no issue to be found.
Have a great day people.
Click to expand...
Click to collapse
Same for me. Just extract the boot.img from the official Xiaomi rom (downloadable from their website), patch that through Magisk manager, and flash the patched .img to boot_a and boot_b using fastboot. Works flawlessly.
Only thing I haven't been able to do is remove the forced encryption. I was able to change the encryption password however using vdc cryptfs.

worked flawlessly, did have to re-install magisk manager after flashing the patched boot images, but all was fine after a quick apk reinstall.

Hi guys,
Sorry for those newbie questions (I come from an old Nexus 5 with Lineage, and I am far from magisk) :
How is going the update ? will it be OTA ? Will it be manual (in this case where do I find the file) ? Do we need to re-root after OS update ?
Thanks in advance !

arnofor said:
Hi guys,
Sorry for those newbie questions (I come from an old Nexus 5 with Lineage, and I am far from magisk) :
How is going the update ? will it be OTA ? Will it be manual (in this case where do I find the file) ? Do we need to re-root after OS update ?
Thanks in advance !
Click to expand...
Click to collapse
The OTA update should be automatic, but I'm not sure 100%
However, after every system update, you have to do the boot patching procedure again but using the boot.img from the new version.

Can I do the unlock part and the rest in a couple of weeks? Without data loss?

ncar123 said:
Can I do the unlock part and the rest in a couple of weeks? Without data loss?
Click to expand...
Click to collapse
You can unlock whenever you want, but every time the bootloader is locked or unlocked, the phone resets its data (but I'm not 100% sure, maybe it's only locking or only unlocking).
But why unlocking now and wait 2 weeks? Couldn't you unlock the phone directly in 2 weeks when you are ready?

BubuXP said:
You can unlock whenever you want, but every time the bootloader is locked or unlocked, the phone resets its data (but I'm not 100% sure, maybe it's only locking or only unlocking).
But why unlocking now and wait 2 weeks? Couldn't you unlock the phone directly in 2 weeks when you are ready?
Click to expand...
Click to collapse
I don't want to setup my phone with my data twice...

ncar123 said:
I don't want to setup my phone with my data twice...
Click to expand...
Click to collapse
So it's ok. Unlock now while you don't have any data in the phone and whenever you want, you can install Magisk later.

[FINAL][RECOVERY][Z010D]ASUS Zenfone Max ZC550KL Marshmallow

Introduction
I've been researching on how to install TWRP on Zenfone Max with Final Marshmallow update for a long time, and finally found and gathered information on how to do so without any consequences. So if you're on final Marshmallow update and want to install TWRP on your phone, then this guide is for you! P.S. This is for Z010D only.
How To Install TWRP
1. Download this APK on your phone to unlock your bootloader : https://drive.google.com/open?id=0B-0qEY9zypslUTFKRE5CQUU5OFk
The app says it will wipe all data, but with my experience it doesn't wipe any data at all. However, I still recommend you to take a backup.
2. Download this zip to your computer and extract it : https://drive.google.com/file/d/0B2kFletApi72QkRLZnFURDUyZk0/view
3. Download this TWRP 3.2.3-0 image : https://sourceforge.net/projects/an...covery/TWRP-3.2.3-Z010D-20180729.img/download
4. Merge the TWRP 3.2.3 image to the extracted zip
5. Make sure you have USB Debugging on and put your phone into Fastboot mode [Hold Volume Up + Power] and connect it to the computer
6. In the extracted zip folder search bar, type 'cmd' and press Enter
7. Type 'fastboot devices' and press Enter, to see if your phone is detected
8. Type 'fastboot flash recovery TWRP-3.2.3-Z010D-20180729.img' and press Enter
9. Disconnect the phone and Hold 'Volume Down + Power', when you see the ASUS logo let go the Power, but keep holding Volume Down until you see the TWRP logo
Congratulations, you've successfully installed TWRP!
Video
If you're too lazy to read like me, here's the video : https://www.youtube.com/watch?v=EwuiHBIts7M

WhatzIt2Ya said:
Introduction
I've been researching on how to install TWRP on Zenfone Max with Final Marshmallow update for a long time, and finally found and gathered information on how to do so without any consequences. So if you're on final Marshmallow update and want to install TWRP on your phone, then this guide is for you!
Before We Get Started
Download these files on your phone and move it to the root of the storage :
1. Magisk 17.1 : https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip
2. (Optional) TWRP 3.1.1 image : https://androidfilehost.com/?fid=745849072291687209
How To Install TWRP
1. Download this APK on your phone to unlock your bootloader : https://drive.google.com/open?id=0B-0qEY9zypslUTFKRE5CQUU5OFk
The app says it will wipe all data, but with my experience it doesn't wipe any data at all. However, I still recommend you to take a backup.
2. Download this zip to your computer and extract it : https://drive.google.com/file/d/0B2kFletApi72QkRLZnFURDUyZk0/view
3. Make sure you have USB Debugging on and put your phone into Fastboot mode [Hold Volume Up + Power] and connect it to the computer
4. In the extracted zip folder search bar, type 'cmd' and press Enter
5. Type 'fastboot devices' and press Enter, to see if your phone is detected
6. Type 'fastboot flash recovery Z010_3.0.0.t1_without_su.img' and press Enter
7. Disconnect the phone and Hold 'Volume Down + Power', when you see the ASUS logo let go the Power, but keep holding Volume Down until you see the TWRP logo
Congratulations, you've successfully installed TWRP!
Optional If you've downloaded TWRP 3.1.1 image, headover to 'Install' and select 'Install Image', then select the TWRP 3.1.1 image, then select Recovery and finally swipe to flash to update TWRP. To reboot back into recovery, press home, select reboot, and then recovery. You should see the TWRP version 3.1.1 upon reboot.
How To Root with TWRP
1. Boot into recovery and select 'Install'
2. Select Magisk zip and swipe to flash
3. Reboot to your OS, you should see a new app that is Magisk
Congratulations, you've successfully installed TWRP and Magisk!
Video
If you're too lazy to read like me, here's the video : https://www.youtube.com/watch?v=EwuiHBIts7M
Click to expand...
Click to collapse
Hey bro , seems you've been in mars and just arrived on Earth ! There's no issue whatsoever with installing twrp and rooting ZC550KL, there are lots of threads and video on YouTube about this for more than a year now.

jide1 said:
Hey bro , seems you've been in mars and just arrived on Earth ! There's no issue whatsoever with installing twrp and rooting ZC550KL, there are lots of threads and video on YouTube about this for more than a year now.
Click to expand...
Click to collapse
Yes, but some comments have issues where will it work with different versions (or updates), as the last update ASUS pushed was around Dec 17/Jan 18 with November 2017 security patch, some of the guides I've tried have failed, or had some issues. Also, some guides tell you to downgrade to marshmallow beta. Anyways, I just thought to do a final guide to root. ?

WhatzIt2Ya said:
Yes, but some comments have issues where will it work with different versions (or updates), as the last update ASUS pushed was around Dec 17/Jan 18 with November 2017 security patch, some of the guides I've tried have failed, or had some issues. Also, some guides tell you to downgrade to marshmallow beta. Anyways, I just thought to do a final guide to root.
Click to expand...
Click to collapse
so basically, is it all about unlocking the bootloader something to root the phone or what?

Singhisme said:
so basically, is it all about unlocking the bootloader something to root the phone or what?
Click to expand...
Click to collapse
Obviously, you need an unlocked bootloader to do any modifications! The only issue is, Asus phones don't show whether you have an unlocked bootloader or not. Sometimes the bootloader unlocker fails.

Jt380p said:
Obviously, you need an unlocked bootloader to do any modifications! The only issue is, Asus phones don't show whether you have an unlocked bootloader or not. Sometimes the bootloader unlocker fails.
Click to expand...
Click to collapse
Then how to be sure my device is locked or unlocked then?

Singhisme said:
Then how to be sure my device is locked or unlocked then?
Click to expand...
Click to collapse
Theres no sign. You just have to trust the app, unfortunately.

Urgent
Hi sir same way i did but TWRP is not showing.only black screen is displaying and i cant restart my phone please help me sir

twrp not showing

Jt380p said:
Theres no sign. You just have to trust the app, unfortunately.
Click to expand...
Click to collapse
I figure it out somehow.. there's something to do with ADB to check by this far it is the only way I know. thanks for the TWRP btw.. Good works!

Jt380p said:
Introduction
I've been researching on how to install TWRP on Zenfone Max with Final Marshmallow update for a long time, and finally found and gathered information on how to do so without any consequences. So if you're on final Marshmallow update and want to install TWRP on your phone, then this guide is for you! P.S. This is for Z010D only.
How To Install TWRP
1. Download this APK on your phone to unlock your bootloader : https://drive.google.com/open?id=0B-0qEY9zypslUTFKRE5CQUU5OFk
The app says it will wipe all data, but with my experience it doesn't wipe any data at all. However, I still recommend you to take a backup.
2. Download this zip to your computer and extract it : https://drive.google.com/file/d/0B2kFletApi72QkRLZnFURDUyZk0/view
3. Download this TWRP 3.2.3-0 image : https://sourceforge.net/projects/an...covery/TWRP-3.2.3-Z010D-20180729.img/download
4. Merge the TWRP 3.2.3 image to the extracted zip
5. Make sure you have USB Debugging on and put your phone into Fastboot mode [Hold Volume Up + Power] and connect it to the computer
6. In the extracted zip folder search bar, type 'cmd' and press Enter
7. Type 'fastboot devices' and press Enter, to see if your phone is detected
8. Type 'fastboot flash recovery TWRP-3.2.3-Z010D-20180729.img' and press Enter
9. Disconnect the phone and Hold 'Volume Down + Power', when you see the ASUS logo let go the Power, but keep holding Volume Down until you see the TWRP logo
Congratulations, you've successfully installed TWRP!
Video
If you're too lazy to read like me, here's the video :
Click to expand...
Click to collapse
anyone have working oem unlock tool for asus zenfone max (zc550kl).
tried so many tools,nothing worked for me

Android_Rom_OTA for ASUS Zenfone Max ZC550KL[Z010D]​

Android_Rom_OTA: ​
Released /LineageOS-OMS/Z010D/lineage-14.1-20180821-UNOFFICIAL-Z010D-OMS.zip​
Released /OreoTest/lineage-15.1-20180817-UNOFFICIAL-Z010D.zip​
Released /TWRP_Recovery/TWRP-3.2.3-Z010D-20180729.img​
Released /LineageOS/Z010D/lineage-14.1-20180729-UNOFFICIAL-Z010D.zip​
Download Android_Rom_OTA​

Root EMUI 9.0

Thx to topjohnwu you can use magisk on EMUI9. https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
What you need:
1. Unlocked Bootloader
2. be able to use twrp 3.2.3-1 (important! 3.2.3-1). In this case, im using latest offical twrp for the Huawei P20 Pro (charlotte). Only use ADB function, other features (backup/restore) are untested by me, it can harm your device eventually if you use other functions then ADB.
3. adb installed on PC
4. all-full-release.apk from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
5. magisk-release.zip from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
OK, so how we root the Honor 10 with EMUI9.0?
1. Download offical twrp from here: https://dl.twrp.me/charlotte/twrp-3.2.3-1-charlotte.img.html.
Be careful, this release was made for another device, but i had no issue with it on my Honor 10.
2. Download Magisk Manager (all-full-release.apk) from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds and install it.
3. Download magisk root (magisk-release.zip)
4. Enable OEM Unlock (so you can flash recovery in fastboot) , Power Off the device, push and hold VOL DOWN and plug in the usb cable. The device will start into fastboot.
5. Flash Twrp withon the PC: fastboot flash recovery_ramdisk twrp-3.2.3-1-charlotte.img
6. This one is a bit tricky! Type fastboot reboot, push and hold VOL UP and after sending fastboot reboot immediately remove cable and wait for twrp to boot. If you not remove the cable you will end up in eRecovery and have to redo the steps above.
7. In twrp, go to advanced and start ADB. Than plug in the USB cable.
8. PC: flash magisk-release.zip with: adb sideload magisk-release.zip
9. IMPORTANT: Remove cable, select reboot, but keep VOL UP pressed during reboot, otherwise you are not able to use magisk. You have to press VOL UP everytime you reboot the device otherwise you have to do Step 5-9 again.
10. Done, your device is rooted.
UPDATE to .162:
To Update succsessfully to .162 you have to do the following things:
1. flash emui stock recovery_ramdisk.img in fastboot (extract it from update.app using Huawei Update Extractor) use "fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG" You dont have to use recovery_ramdisk.img from .162. Just use the latest update.app to extract the recovery_ramdisk.img you can find in Firmware Finder.
2. Disable OEM Unlock and reboot the device
3. Go to Settings\System\Software Updates and Hit the 3 Dots on the top right. Select the Full Package Download.
4. Wait until download is complete and hit update. Now the device will boot into EMUI recovery and install the update the phone.
5. The device is now rootless, if you want root again, follow the instructions above.
Caution: Just in case: After the update and installation of magisk, adaway becomes unstable on my phone. It seems the "allow root" popup dont show up after adaway started. I have fixed this by autoallow root in magisk, start adaway, enable adblocking and set magisk to "ask permissions" again. After this, the popup shows correctly again. For now i have no clue why this was happen, another Honor 10 dont have this issue at all.
albysprx said:
Just disable battery optimization for magisk manager and the "allow root" popup will appear
Click to expand...
Click to collapse
Notice for UPDATE .179:
You can use the guide above but you have to update (Systemupdate) twice, since the update comes with 2 separate packages. After the first run, emui recovery shows "update failed". Just reboot to system, go to settings, and start the updateprocess again. The second package is about ~220MB in size. After this follow the guide above to get magisk running again.
Notice for UPDATE .203:
Just do the usual way. Flash STOCK recovery_ramdis.img with fastboot, reboot the phone, do the update. After this flash twrp in fastboot again and adb sideload magisk-release.zip.
Notice for UPDATE .207:
Works! Flash STOCK recovery_ramdis.img with fastboot, reboot the phone, do the update. After this flash twrp in fastboot again and adb sideload magisk-release.zip.
Notice for UPDATE .216:
Works!
Notice for UPDATE .223:
Works, but you have to use latest Magisk release (19.3) from topjohnwu: https://github.com/topjohnwu/Magisk/releases
At step 8. PC: flash magisk-v19.3.zip with: adb sideload Magisk-v19.3.zip
Notice for UPDATE EMUI 9.1:
9.1 Change a lot, you will have the latest stock RECOVERY_RAMDISK.IMG patched via Magiskmanager and install that with fastboot. After this, reboot and PRess VOL+. You will end up in eRecovery, hit Wipe/Factory Reset(Make BACKUP!) and reboot. This install magisk permanently. For Adaway: You need Systemless Mode activated in Magisk and Adaway.
Maybe i will write another Guide for 9.1, but for now im testing stability.

Thanks a lot man!

Well P20 hardware share similarity with honor 10. Twrp should work logically but you never know when you came up against something bad so I will for now hehe
Sent from my Honor 10 using XDA Labs

Will it work with mate 10 pro emui 9?

neo2k17 said:
Will it work with mate 10 pro emui 9?
Click to expand...
Click to collapse
I've tested and it works

Hi, either it's not working for me or i'm stuck somewhere.
Steps 1-5 are working.
Then it reboot the device with fastboot reboot and press&hold the vol up.
But my phone doesn't boot into twrp. All i get is erecovery.
When i turn the phone off, no usb cable plugged in and try to get into twrp by press&hold power + vol up i get:
error mode
attention!
please update system again
error!
func no: 11 (recovery image)
func no:2 (load failed!)
Click to expand...
Click to collapse
Normal boot still worked fine.
What am i doing wrong?
I just updated from 8.1 to 9 today fyi.
edit: after flashing my latest twrp image that worked i can access twrp recovery again.
but everything at /sdcard looks encrypted since all folders and files have crazy names like asdfASdfasdFGADSgm
I currently don't have any password etc. on my honor.

leAndroid91 said:
edit: after flashing my latest twrp image that worked i can access twrp recovery again.
but everything at /sdcard looks encrypted since all folders and files have crazy names like asdfASdfasdFGADSgm
I currently don't have any password etc. on my honor.
Click to expand...
Click to collapse
Android 9 comes with build in crypto, so its perfektly normal to see folders like "akgaufagkiugsduiphps". Thats the reason we have to use ADB with latest TWRP, only 3.2.3-1 has support for it. So i beleive, if you cant get 3.2.3-1 running, you cannot have magisk atm.

ThreeMMM said:
Thx to topjohnwu you can use magisk on EMUI9. https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
1. Download offical twrp from here: https://dl.twrp.me/charlotte/twrp-3.2.3-1-charlotte.img.html.
Be careful, this release was made for another device, but i had no issue with it on my Honor 10.
2. Download magisk (all-full-release.apk) from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds and install it. Its Magisk Manager.
3. Download magisk-release.zip
4. Disable OEM Unlock, Power Off device, push and hold VOL DOWN and plug is the usb cable. The device will start into fastboot.
5. Flash Twrp with: fastboot flash recovery_ramdisk twrp-3.2.3-1-charlotte.img
6. Type fastboot reboot, push and hold VOL UP until device boots into twrp.
7. In twrp start ADB
8. PC: flash magisk-release.zip with: adb sideload magisk-release.zip
9. IMPORTANT: Select Reboot but keep VOL UP pressed during reboot, otherwise you are not able to use magisk.
Click to expand...
Click to collapse
Thx a lot! Works fine
One question about 9. - I had to remove the cable first, otherwise by pushing VOL UP+reboot it goes directly to eRecovery-mode?!

Uhm ... just one question for my understanding.
How am i supposed to flash a new recovery in step 5 when i disable oem unlock in step 4?
As far as i know deactivating oem unlock prevents from flashing even if the bootloader is already unlocked.

leAndroid91 said:
Uhm ... just one question for my understanding.
How am i supposed to flash a new recovery in step 5 when i disable oem unlock in step 4?
As far as i know deactivating oem unlock prevents from flashing even if the bootloader is already unlocked.
Click to expand...
Click to collapse
You're right, i just went through without reading that point correctly. It's a little bit misleading

Sorry guys, i have edit the Post so now its more clear what to do. Thanks for the hints, it a pleasure to contribute to such a nice community! Keep rockin!

Haj
point 2
Installation Magisk all-full-release.apk. The application is installed, additional files are downloaded, but end with the message "Magisk not installed". Is this how it should be?

By keeping oem unlocked i was able to flash twrp, too.
And i was able to boot into twrp.
But for /sdcard it kept showing me the encrypted files and folders
What's the reason behind:
9. IMPORTANT: Remove cable, select reboot, but keep VOL UP pressed during reboot, otherwise you are not able to use magisk. You have to use this everytime you reboot the device.
Click to expand...
Click to collapse
Is magisk checking if vol up is pressend and then activates, otherwise it stays inactive?
edit:
i was not able to boot like mentioned in step 9.
1st try: i got stuck at "your device is booting now..." (still pressing vol up).
Then released vol up and waited for another 3-4 minutes but nothing happend.
2nd try: When not pressing any button my phone booted as expected but without magisk.
3rd try: Then i shut it down again.
Turned it on, pressend and hold vol up but i just got into eRecovery.
Any ideas?

Does this method keep magisk permanently after the first boot or do I need to repeat the procedure every time if my bootloader is locked?

Coraz said:
Does this method keep magisk permanently after the first boot or do I need to repeat the procedure every time if my bootloader is locked?
Click to expand...
Click to collapse
You don't have to do the whole procedure except step 9, you have to push VOL UP during every reboot to keep magisk active.

p. 2
magisk (all-full-release.apk) install.
select method:
- Download zip only
- Patch boot image file (then click)???

kmarek11 said:
p. 2
magisk (all-full-release.apk) install.
select method:
- Download zip only
- Patch boot image file (then click)???
Click to expand...
Click to collapse
Just install the app and go on with step 3.

To install using a zip file?

kmarek11 said:
To install using a zip file?
Click to expand...
Click to collapse
Install the apk file, the zip file is for rooting your device via adb sideload.

I am installing magisk (all-full-release.apk) from the given link
the application appears on the phone
in the magisk application I click "installation" I get communication, do you want to install Magisk-v18.0 (18000) zip? and choice:
1 I do not thank you
2 changes
3 this installation I click and the "Choose method" message is displayed: and the option to choose
1 download only zip or
2 Patching the boot image file
Which one to choose to go to the next steps?

How to root Ulefone Armor 11 5G

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

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

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

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

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

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

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

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

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

It should, because iy's an empty file.

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

Will this work with Android 11?

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