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
Related
Morning all, so when I tried to root and install magisk on my Cubot Quest I noticed that above all I wasn't able to flash the custom recovery (twrp in this case).
The device is pretty new, with latest firmware (v13) while with another device (always Cubot Quest) bought 1 year ago I was able to flash everything without issue, so with latest version something in the device was changed.
In reality at some point I was able to flash twrp recovery, but it is useless becasue touch doesn't work so it must be used trought command line (trought adb sideload) and let's say it's a pain.
So I restored the original recovery (trough flash_tool) and found another way to just root device + install magisk, that is at the end the real target I was looking for.
I must advise that "playing" with modded boot image could brick the device... so if you are not brave enough just stop to read now
If you are reading this your are brave, so let's explain how to root this damn device:
1. download & flash latest firmware/rom (v13) if you haven't done yet: https://www.cubot.net/platform/Support/detail/id/129/cid/16.html
2. take from the rom folder the boot.img file and put in another device with latest magisk version installed (my other device is a Xiaomi A1 rooted and running magisk 20.4): https://magisk.download/
3. from the other device patch the boot.img trough magisk, pay attention... JUST patch it, do not patch+install and don't reboot or you'll brick the other device
4. always from the other device take the patched_boot.img and copy on your PC
5. reboot Cubot Quest on bootloader and trought adb (on your PC) flash the patched_boot.img: fastboot flash boot patched_boot.img
6. restart device and install magisk manager: https://magisk.download/#apk
7. upon running magisk it request for some updates, accept everything and restart the device
8. if all works as expected upon reboot your device should be rooted and magisk is fully operative
Regards,
Davide
Hello Davide,
I've been struggling for the last few days trying to flash twrp.img and root my new Cubot Quest (purchased on the 17th of july) but didn't make it so far despite all the methods I tried.
I just have followed your post and got my patched_boot.ini file but when I flash it via fastboot, then flash is not taken into account while if I flash it via "SP Flash Tool" then I get and endless boot error (I also tried to flash an empty vbmeta.img file without success).
May I ask you to share with me your patched_boot.img file ? I'd like to understand if I'm making any mistake in the procedure or the hw product I got is different from yours. Please find my patched_boot.img file here: anonymousfiles.io+slash+T1hCDypR
and the output of the "adb shell getprop" command here: anonymousfiles.io+slash+NzqfN2OH
I've been using latest firmware files "A798_CQ_8123C_62_P0_V1.2.8.4_S190806" from "CUBOT_QUEST_V13_20190806.zip"
Thanks for any help you might give me!
Buona serata,
V.
Nothing happens no one thanks for the contribution to no one
Hi guys. Is there any root method for the Gigaset Gs4? Thanks.
Anyone?
As long as you have the stock images there is.
Im currently trying to get the stock ROM in any way. If anyone has some tips please reply
Currently I'm trying to get the stock ROM using the image here: https://www.google.com/amp/s/unofficialtwrp.com/download-twrp-3-2-3-mediatek-mt6771-8-1/?amp
I hope that I can extract boot.img with it, to patch it with magisk.
Also take a look here:
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Software root method for MediaTek MT67xx, MT816x, and MT817x! So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I...
forum.xda-developers.com
Edit: I found another image for the mt6771 that might work as well but keep in mind that it is not made for the Gigaset GS 4: https://www.techswizz.com/twrp-recovery-for-cubot-note-20-pro/ DOES NOT WORK!!
As soon as I got the patched image I think you can use this bypass to flash it: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/amp/ DOES NOT WORK!!
StarMiner99 said:
As long as you have the stock images there is.
Im currently trying to get the stock ROM in any way. If anyone has some tips please reply
Currently I'm trying to get the stock ROM using the image here: https://www.google.com/amp/s/unofficialtwrp.com/download-twrp-3-2-3-mediatek-mt6771-8-1/?amp
I hope that I can extract boot.img with it, to patch it with magisk.
Also take a look here:
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Software root method for MediaTek MT67xx, MT816x, and MT817x! So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I...
forum.xda-developers.com
Edit: I found another image for the mt6771 that might work as well but keep in mind that it is not made for the Gigaset GS 4: https://www.techswizz.com/twrp-recovery-for-cubot-note-20-pro/
As soon as I got the patched image I think you can use this bypass to flash it: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/amp/
Click to expand...
Click to collapse
i managed to extract the stock boot.img and recovery.img using this guide with some modifications:
How to use Wwr MTK + SP Flash tool to backup Mediatek rom
This is a step-by-step guide on how to use Wwr MTK tool & SP flash tool to backup Mediatek (MTK) firmware. We had previously created guides on how to backup or dump firmware from a Mediatek (MTK) devi
forum.hovatek.com
things i did different:
i could not preform the ram test to determine the size of emmc_user so i just used a random length(0x3a3e00000) later on WwR told me that emmc_user should be: 0xe8f800000 i used this value to again read the emmc_user region and loaded it into WwR and continued on the rutorial.
now with this information we should be able to patch boot.img using magisk and flash it to our devices to root it.
to flash your device do the following: reboot into fastboot mode (power + volume up and select fastboot) then in a terminal type:
to unlock the bootloader:
fastboot flashing unlock
to flash an image to your device:
fastboot flash <partition> <image>
the stock images and the scatter file will follow
I managed to succesfully root my smartphone using magisk there was a single problem which is the following:
Android verified boot
you need to flash a new vbmeta image
i made my own empty vbmeta image and flashed it now its working and my smartphone is rooted
[HOW TO ROOT AND HOW TO INSTALL TWRP]
DISCLAIMER:
I will not be responsible for any damage to you device !!!!
step 1 :
make a backup of your smartphone data
step 2 :
unlock your bootloader
1. go to settings -> about phone -> click a few times on the build number
2. go to settings -> system -> developer options -> allow OEM unlocking
step 3 :
install adb and fastboot on your computer
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/ <- you can download a minimal version here
step 4 :
enable usb debugging
go to settings -> system -> developer options -> enable usb-debugging
step 5 :
open a console on your computer and do the adb and fastboot stuff
type the following commands into your cmd:
adb reboot bootloader <- this will reboot your smartphone into fastboot mode
wait until your phone enters fastboot mode
as soon as your phone entered fastboot mode type the following:
fastboot flashing unlock <- this will unlock your bootloader you have to press volume up to confirm it
then flash vbmeta and magisk patched:
fastboot flash vbmeta vbmeta_disabled.img <- this will flash the new vbmeta file
[ROOT]
fastboot flash boot magisk_patched-23000_tvNQq.img <- this will flash the new boot image
[TWRP]
fastboot flash recovery twrp.img <- this will flash the new recovery image
step 6 :
reboot your phone and reconfigure it
Youre Done!
EDIT: please download the twrp image from the official TWRP site: https://twrp.me/gigaset/gigasetgs4.html
@StarMiner99 as I'm thinking about buying it I'm glad to know it can be rooted.
bmwdroid said:
@StarMiner99 as I'm thinking about buying it I'm glad to know it can be root
Click to expand...
Click to collapse
well it was not easy to get the stock images xD
im currently also trying to port lineage os and twrp to the gigaset gs4
StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
That's good to hear.
Although if it can be rooted it might be sufficient for me to kill all not needed apps via adb and use Magisk for AFWall+.
Actually I've read about the possibility of a GS version with a better camera so I might wait a while before getting one.
well there arent any unneeded apps
[STOCK ROM + SCATTER FILES + PRELOADER]
here are the stock rom files, the scatter file and the preloader in a zip archive
1.5 GB file on MEGA
mega.nz
StarMiner99 said:
[STOCK ROM + SCATTER FILES + PRELOADER]
here are the stock rom files, the scatter file and the preloader in a zip archive
1.5 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
Hey StarMiner99, is the ADUPS software updating malware in the image you uploaed still working? Could hyou please explain briefly how to flash this stock rom? I have adb and fastboot already running and a rooted device too.
Thanks a lot!
StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
any progress on this?
could i do something to help?
First of all: Thank you very much! Everything has worked so far and the device is rooted.
But I still have one question. How does the device behave when the official updates from Gigaset are installed via OTA? The GS4 reports it would have security updates. Can I install them without losing root privileges? Does anyone already have experience? Thanks in advance!
UserSven said:
First of all: Thank you very much! Everything has worked so far and the device is rooted.
But I still have one question. How does the device behave when the official updates from Gigaset are installed via OTA? The GS4 reports it would have security updates. Can I install them without losing root privileges? Does anyone already have experience? Thanks in advance!
Click to expand...
Click to collapse
I have now simply installed the June 2021 update. The good news: It worked. The slightly less good news is that you have to flash the images again. But flashing also works with the latest version and the update check tells that there are no new updates. So it seems to work.
UserSven said:
I have now simply installed the June 2021 update. The good news: It worked. The slightly less good news is that you have to flash the images again. But flashing also works with the latest version and the update check tells that there are no new updates. So it seems to work.
Click to expand...
Click to collapse
Which recovery do you use?
I've read in their forum that updating doesn't work when on TWRP.
StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
Why are you not just using the LineageOS GSI?
I have LineageOS17.1 running on my GS4 since Feb. without any issues so far.
ChrisMucDev said:
Why are you not just using the LineageOS GSI?
I have LineageOS17.1 running on my GS4 since Feb. without any issues so far.
Click to expand...
Click to collapse
Is there a tutorial on how to do that?
Wolfgang-Z said:
Is there a tutorial on how to do that?
Click to expand...
Click to collapse
Here is, what I did: (on your own risk)
As far as i can remember, i did not have any issues.
Step 1: Unlock your device
1. Enable Developer Options: Tap 10x on Build-Number (Setttings -> About the phone -> Build-Number)
2. Enable Bootloader Unlocking -> activate OEM-Unlock option (Settings -> System -> (More) -> Developer-Options)
3. Enable ADB Access -> Enable USB-Debugging / ADB (Settings -> System -> (More) -> Developer-Options)
4. (Set USB-Settings (Message-Center) from "No tx" to "PTP")
5. Connect phone to usb port, grant permissions on phone and check connection with `adb devices`
6. Boot to bootloader: `adb reboot bootloader`
7. Unlock Bootloader: `fastboot flashing unlock`
Step 2: Download GSI
1. Reboot your phone and install Treble Info App
(https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en&gl=US)
GS4 should support AB-Partitions
2. Download GSI: https://sourceforge.net/projects/andyyan-gsi/files/
For GS4: treble_arm64_bv*
Step 3: Install GSI
1. Boot to recovery: `adb reboot recovery` or Volume Down + Power
2. Wipe data
3. Wipe cache
4. Enter fastboot
5. Flash GSI: `fastboot flash system <extracted-gsi-image>`
6. Reboot and enjoy
*. (just in case it does not boot, reboot to recovery -> enter fastboot and flash vbmeta: `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`)
This vbmeta-image should work (see post #6): https://forum.xda-developers.com/attachments/vbmeta_disabled-img.5325563/
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?
after patching boot.img with Magisk and flashing over the patched boot.img, the phone (Doogee S88 Plus) will just infinitely reboot after the message `Your device has been unlocked and can't be trusted`
luckily, patching the original boot.img back fixes it (albeit flashing it back is kindof tricky, have to reboot multiple times while holding down the volume-down button before i can re-flash)
so it's not bricked, but i haven't been able to root it either, any suggestions?
fwiw, i'm using this firmware: https://drive.google.com/drive/folders/13bxhk-eEsJ81FmJWZaEEsOkZBMsYJE3x
update: finally managed to root it, the final piece of the puzzle was that S88 Plus wanted the magisk-patched boot.img signed with the publicly-available-private-key from https://forum.hovatek.com/thread-35862.html
screenshot:
https://imgur.com/EbjK0qX
the magisk-patched + signed boot.img if anyone is interested:
where boot.img ?
and you chose which twrp ?
avalondrey said:
where boot.img ?
Click to expand...
Click to collapse
avalondrey said:
and you chose which twrp ?
Click to expand...
Click to collapse
i did not use twrp at all, i only used magisk, and the boot.img is the file i uploaded above with the name "magisk_patched-23000_TY62U.img" , just rename it to "boot.img"
does your phone has a vbmeta.img?
It control if the image is signed, if you don't flash an empy vbmeta.img the system will bootloop.
It was a problem when rooting the Ulefone Armor 8-11
root is ok , flash tool, install boot and reboot
Harlock1978 said:
does your phone has a vbmeta.img?
It control if the image is signed, if you don't flash an empy vbmeta.img the system will bootloop.
It was a problem when rooting the Ulefone Armor 8-11
Click to expand...
Click to collapse
interesting, yes the phone has a vbmeta.img, and no i did not patch the vbmeta.img, and i did experience the reboot-loop, but signing the patched boot.img fixed the reboot loop without touching the vbmeta.img
This did it..dont flash vbmeta...the Boot ist the only Thing you Need...flashing vbmeta will end in bootloop...maybe a signed vbmeta...but why trying when Boot is enough...
after hours of trying I finally got it working.
Because I tried so much stuff I'm not exactly sure what was the key.
The signed boot.img flashed with sp flash tool alone did not work - i did not have the device unlocked with fastboot at that moment.
Then I tried a lot of different stuff.
I _think_ what was needed is these two things:
- signed boot.img from @hans henrik
- unlocking bootloader with fastboot (fastboot flashing unlock && fastboot flashing unlock_critical)
How did you unlocked it? And are you running gsi rom?
I have the s88 pro and i like to install custom rom
the doogee s88 plus should support galileo GPS standard Pu on mine it does not show any gaileo satelites. could anybody check?
Hi please help me i have doogee S88 plus and i use this guild https://unofficialtwrp.com/twrp-3-4-0-root-doogee-s88-plus/
now me phone keeps restarting, show "orange state", logo launches, I tried different combinations of buttons but nothing helped
what can i do or is there any way i can get it back to normal?
only now found this thread, currently the phone has a bootloop after these three commands
fastboot erase userdata
fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
OK, i use sp flash tool but when i turn on me phone i see a bars on screen
i tried with all the stock roms i found, everywhere the same, the phone seems to work but instead of images there are stripes
this rom worked
OneDrive
onedrive.live.com
I finally managed to root my phone after days of endless boot loops (fixed by flashing stock using SP flash tool). Turns out I didn't need to flash an empty vbmeta or install TWRP at all. I was able to root it by following this guide https://www.hovatek.com/forum/thread-35862.html. For some reason your patched magisk image didn't work on my S88 Plus, so I made my own using the stock boot image from the official Doogee website (which appears to be the same one used in your patched version?) and Magisk 25.2 apk. For the Hovatek guide, I used python2 since python and python3 did not work. I currently have a red "Not Verify" watermark and an NVRAM WARNING: Err = 0x10 wifi network error, but should be able to resolve those with root access from guides I read earlier.
I would also like to install a GSI (lineageos preferably) but have had no success since nothing seems to officially support the S88 Plus even though it is project treble compatible, and I have ran into boot loops so far.
I have attached my working magisk_patched.img but would recommend building it from scratch using the linked guide to avoid any issues.
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