Related
As you may imagine this simple guide will show you how to root your device with magisk from twrp recovery.
I know, there is already a guide by jashancheema that shows how to root this device, however it's difficult to update the system once you are rooted. In my opinion the way i'm about to show you is faster and easier.
Disclaimer: I am not responsible for ANY damage done to your phone, act at your own risk.
That's how you can root your phone with magisk and recovery without disabling ota.
1. First download magisk manager and magisk flashable zip from here (official thread)
Install magisk manager and copy the magisk flashable zip somewhere in your device or sd.
2. Download mohancm twrp recovery (recovery-3.2.1-2-oreo) from here (official thread)
NOTE: do not download the installer, you need the .img file bootable from fastboot (recovery-3.2.1-2-oreo.img)
3. Copy recovery-3.2.1-2-oreo.img into the fastboot folder.
4. Enable developer option from in the device, enable OEM unlocking.
5. turn off your device and enter into fastboot mode by holding voume down + power button, then connect your device to the pc.
6. now open fastboot and type this to check the connection, if the terminal return an andress your phone is correctly configured.
Code:
fastboot devices
7. type this from fastboot to unlock your bootloader.
Code:
fastboot oem unlock
8. now type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
9. once your recovey boot flash the magisk zip and reboot.
NOTE: do not install or flash twrp into your device or you won't be able to update through ota.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
RESERVED
All works!!! :good::good::good::good::good:
WORK
I tried, it works. thank you!
funziona da dio! fantastico! bella guida
Great work!
i already flash twrp on my device, so i cannot install update OTA until i go back to unroot?
@H.A.L. 9000, I'm sorry for my ignorance but I wonder whether the bootloader unlock passage (that'd reset everything) is inescapable after installing an OTA update
Can I install ota with the unlocked bootloader?
Thanks for this I was always confused on how to update the phone after magisk.
Edit: you think it's possible to use a custom kernel with magisk and still maintain ota?
Thank you, the rooting part worked flawlessly. :good: Now waiting for the next OTA to see if that will work well too.
1. USB debugging doesn't have to be allowed?
2. Updating Android can be done with PC only?
I did exactly the same (as nicely outlined in MP) for the last few updates, and can confirm it's working perfectly. I was using this as the 'normal' way failed due to unknown reasons.
This approach does not required a patched boot-image available, so imho it's more robust and reliable than the 'normal' method.
iG0tB0lts said:
Thanks for this I was always confused on how to update the phone after magisk.
Edit: you think it's possible to use a custom kernel with magisk and still maintain ota?
Click to expand...
Click to collapse
+1
Have you found out?
H.A.L. 9000 said:
As you may imagine this simple guide will show you how to root your device with magisk from twrp recovery.
I know, there is already a guide by jashancheema that shows how to root this device, however it's difficult to update the system once you are rooted. In my opinion the way i'm about to show you is faster and easier.
Disclaimer: I am not responsible for ANY damage done to your phone, act at your own risk.
That's how you can root your phone with magisk and recovery without disabling ota.
1. First download magisk manager and magisk flashable zip from here (official thread)
Install magisk manager and copy the magisk flashable zip somewhere in your device or sd.
2. Download mohancm twrp recovery (recovery-3.2.1-2-oreo) from here (official thread)
NOTE: do not download the installer, you need the .img file bootable from fastboot (recovery-3.2.1-2-oreo.img)
3. Copy recovery-3.2.1-2-oreo.img into the fastboot folder.
4. Enable developer option from in the device, enable OEM unlocking.
5. turn off your device and enter into fastboot mode by holding voume down + power button, then connect your device to the pc.
6. now open fastboot and type this to check the connection, if the terminal return an andress your phone is correctly configured.
7. type this from fastboot to unlock your bootloader.
8. now type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
9. once your recovey boot flash the magisk zip and reboot.
NOTE: do not install or flash twrp into your device or you won't be able to update through ota.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse
Can't I just install syst update through twrp?
Rooting Mi A1 using this method worked. But the guide needs updating:
1.You must enable usb debugging
2.You must install magisk manager after unlocking bootloader. Installing it before is useless because unlocking bootloader will wipe all data.
freekarol said:
unlocking bootloader will wipe all data.
Click to expand...
Click to collapse
not till 9.5.11
freekarol said:
Rooting Mi A1 using this method worked. But the guide needs updating:
1.You must enable usb debugging
2.You must install magisk manager after unlocking bootloader. Installing it before is useless because unlocking bootloader will wipe all data.
Click to expand...
Click to collapse
Well, that happened to me.. Total WIPE... So, i decide to stop. But this night i'll try again, after a full backup. For me this is important because i need to use Android Auto, with aamirror.
I do regular backups so it was ok with me. It also should be in the guide as a first step: backup your phone. It seems like the guide is not for beginners... After rooting, you can face two problems:
1. From time to time, Magisk crashes. Just open it again.
2. There will be a camera lag. Installing a Magisk module should solve it(I haven't tried it yet): https://www.youtube.com/watch?v=UqcQKqhL3ok
there is some indication that 'fastboot boot twrp.img' wipes all the data!
Not sure when it started and if there is a way to avoid it - any idea?
im serous this is the worst device i ever had to root in my life. ive rooted meany devices and modded meany other stuff without issue, had one brick that i was then able to restore and get right the 2nd time. this time however this is the 2nd! pixel that has went into an unrecoverable bootlap when following root tutorials via magisk.
when i then attempt to unbrick eaither of the devices the fast boot official flash all dosent cut it, and adb ota restore dosen't work as recovery menu is destoyed., and dosent revive when original boot.img is flashed. when i looked at the first phone what i found on net is hawrdware issue can cause corruption in flash and cause them to be unrecoverable...... but a 2nd one now? is this upside down world? "root friendly" my A......
Nightmare-Rex420 said:
im serous this is the worst device i ever had to root in my life. ive rooted meany devices and modded meany other stuff without issue, had one brick that i was then able to restore and get right the 2nd time. this time however this is the 2nd! pixel that has went into an unrecoverable bootlap when following root tutorials via magisk.
when i then attempt to unbrick eaither of the devices the fast boot official flash all dosent cut it, and adb ota restore dosen't work as recovery menu is destoyed., and dosent revive when original boot.img is flashed. when i looked at the first phone what i found on net is hawrdware issue can cause corruption in flash and cause them to be unrecoverable...... but a 2nd one now? is this upside down world? "root friendly" my A......
Click to expand...
Click to collapse
In my opinion, you should use root tutorials from your phones forum, not magisk. You haven't explained what your steps were or even asked a question. If you tried using stable channel/files, try the canary debug channel and files instead. I've never had any problem rooting the pixels though I've read where the magisk version 20.2 has caused bootloops for some phones.
allright so it might just be the magisk. it was magisk 20.1 first phone magisk 20.2 2nd phone. i cannot boot into recovery mode and fastboot mode restoring ota dosen't work and it still bootlaps weather i restore just the boot_A and boot_B or whole thing. also where can i find unbrick and root tutorials made for my phone when looked it was mostly magisk and little TWRP.
Nightmare-Rex420 said:
allright so it might just be the magisk. it was magisk 20.1 first phone magisk 20.2 2nd phone. i cannot boot into recovery mode and fastboot mode restoring ota dosen't work and it still bootlaps weather i restore just the boot_A and boot_B or whole thing. also where can i find unbrick and root tutorials made for my phone when looked it was mostly magisk and little TWRP.
Click to expand...
Click to collapse
Hi, I thing, that you need to download factory image (not OTA) for walleye:
Code:
https://developers.google.com/android/images#walleye
Latest SDK Platform Tools:
Code:
https://developer.android.com/studio/releases/platform-tools.html
than boot to bootloader, open command prompt in folder with extracted SDK platform tools run flash-all.bat script with command:
Code:
flash-all.bat
This should format/flash your phone to "factory" state. Good luck.
Btw, I have no problem with magsik 20.1 neither with 20.2...
Just to rule the magisk thing out, I recently bought a used pixel 2 to replace my broken og pixel and I got round to unlocking it last night and had no issue gaining root using magisk 20.2 following the usual process.
Updated to latest platform tools.
Unlocked the bootloader via adb
Skipped through the set up and re enabled usb debugging
Rebooted to bootloader
fastboot booted twrp 3.3.0-0 via adb
flashed magisk 20.2 from fastbooted twrp
rebooted and all good.
If you are having problems booting to the existing recovery you could try fastboot booting the latest twrp in adb (may not work if you had a pin set up as may not be able to decrypt) and try flashing the original or fresh boot.img from there other than that follow the previous post and do a full re flash to stock.
Good luck
I have been looking for some sort of root for the ulefone armor 9, and I can't seem to find anything apart from sketchy websites. Can anyone help?
I found the scatterfile, but i still need to find the authentication file, and a download agent? I don't recall ever having to do any of this to root a phone before. Where do I get these files for a ulefone armor 9?
Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com
jwoegerbauer said:
Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com
Click to expand...
Click to collapse
there isn't a twrp for this phone.
M8E1 said:
there isn't a twrp for this phone.
Click to expand...
Click to collapse
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
jwoegerbauer said:
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
Click to expand...
Click to collapse
I did this, and I got a "red state" boot loop
M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Am I missing something? The phone is apparently locked in fastboot mode, and will not accept downloads.
M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Then report this issue in the related XDA-thread.
jwoegerbauer said:
Then report this issue in the related XDA-thread.
Click to expand...
Click to collapse
What thread would that be? This is for support and questions, isn't it?
M8E1 said:
What thread would that be? This is for support and questions, isn't it?
Click to expand...
Click to collapse
Of course this one:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.
M8E1 said:
Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.
Click to expand...
Click to collapse
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.
kanadali said:
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.
Click to expand...
Click to collapse
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html
Totem95d said:
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html
Click to expand...
Click to collapse
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Trying this method works fine for me until I try to relock the bootloader. Once I do that, I end up with a red state again.
Any advice? I am relocking the bootloader via fastboot flashing lock - is that correct?
MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Hi!
I'm having the same issue as MulBe039.
Device: UleFone Armor 9E (Android 10)
My steps so far:
0.0 Get boot.img, scatter file, checksum generator (from ulefone), magisk.apk (from github), vbmeta.img, drivers, SP Tool (from Hovatek)
0.1 Install magisk on my phone and patch boot.img.
0.2 Enable developer options on my phone
0.3 Enable OEM unlocking and USB debugging on my phone.
0.4 Install drivers on my PC
0.5 Copy scatterfile, boot.img, vbmeta.img into checksum generator's folder and get checksum.ini.
1.0 Connect phone
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Phone boots in orange state.
2.0 Re-enable dev opts, (phone shows as already unlocked), USB debugging and turn off the phone.
2.1 Start SP Flashtool
2.2 Select scatter file
2.3 Check only vbmeta.img
2.4 Start download
2.5 Connect phone
2.6 Download completes successfully.
2.7
> fastboot devices
> fastboot reboot
Orange state.
2.8 Factory reset from phone
3. Repeat 2., except at 2.3 check only the patched boot.img
Still orange state.
Magisk app is installed.
4.0 Turn the phone on, enable dev opts and USB debugging, connect to PC
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem lock
> fastboot reboot
Red state - boot loop.
5.0 Hold power button until it turns off abruptly
5.1 Hold volume up until load some sort of boot selector menu.
5.2 Select fastboot mode with vol up button.
5.3 Vol down to boot selected mode
5.4
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Orange state - everything else is working.
What am I missing / doing wrong? How do I re-lock the bootloader?
Thanks in advance!
I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it
0xf331dead said:
I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it
Click to expand...
Click to collapse
And remember that you cannot lock your bootloader after modifying stuff because signatures will not match and so on
I had to press volume up + volume down while connecting the usb to get mtkclient working
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?
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP