[SOLVED] Trying to root Ulefone Armor X7 Pro using Magisk - Android Q&A, Help & Troubleshooting

Dear Community,
I'm trying to root my Ulefone Armor X7 Pro using Magisk and so far I've experienced several issues, starting with unlocking the bootloader.
I hope you can help me somehow.
Here's what I've done and seen so far:
- OEM Unlock enabled and USB Debugging enabled
- Using ADB from latest Google SDK to reboot in FASTBOOT mode
- Now 'fastboot oem unlock' returns FAILED (remote: 'unknown command'). I've tried to wipe cache partition, it doesn't help, I've tried a few workarounds found on this forum with no luck so far...
- I've read that sometimes this command doesn't work so I used 'fastboot flashing unlock' instead --> that one worked
With this done, and stock boot.img, the phone will display an Orange State warning saying that the device can't be trusted. However it will boot anyway (with the stock boot.img).
Also, the OEM Unlock option will be greyed out in developer options after performing this command.
- However, after flashing the boot image that Magisk Manager generated (from the stock boot.img from Ulefone website), the phone goes into a boot loop with a Red State saying that the boot signature is wrong and verified boot should be disabled. (However I don't know how to do this.)
So I flashed back the stock boot.img and could reboot my phone again (at least it is not bricked -- but that was scary).
Now, here are my questions and thoughts:
- Is it normal that 'fastboot oem unlock' won't work? Is it fine to use 'fastboot flashing unlock' instead?
- The boot image generated by Magisk is only 10 MB while the stock one is 32 MB. I've read the thread of issue #2005 Pad Images to Original Size With Zeros on Github and I thought maybe that's why the phone won't boot with the Magisk image. But I don't know exactly what I should do about it. (I'm on Windows.)
- Finally, if the solution is to disable verified boot, how should it be done? Is there anything to do with the 'Preserve AVB 2.0/dm-verity' option in Magisk Manager?
I hope you'll be able to help me and I wish you all the best anyway.
Thank you.

---

same deal
- It's never been an issue for me if 'fastboot oem unlock' doesn't work. In fact, in my experience (which isn't really that much), it never works. I've always had to use 'fastboot flashing unlock'
- I tried padding the image with zeroes using
Code:
dd if=/dev/zero of=magisk_patched.img bs=1 count=1 seek=33554431
(on a linux box), but it produces the same bootloop. I've tried this same thing with recovery, no such luck.
- I tried flashing via SP Flash Tools, as well. Both the padded and non-padded magisk_patched.img; neither worked. I updated checksum.ini so that flash tools would accept the scatter file. I've tried formatting the section, as well as the 'write memory' tab. SPFT flashes it just fine, but the bootloop continues.
- I even tried patching and flashing boot-debug.img (because why the hell not?) and again, the loop goes on and on.
- I opened up the preloader....bin file in hex editor and removed all instances of 'verify' and flashed via SPFT. Do not do this. The phone will no longer turn on or anything. Luckily, SPFT flashes before anything else in the phone does anything, so it was recovable.
- I tried sideloading my rom as an 'update' but oddly enough adb won't recognize the phone in sideload.
I haven't tried reflashing the whole phone with magisk_patched.img as my boot. I may attempt this. I'll get back to you if I have any luck.
I plan on using mine as a media device (music, video, camera, etc) that I can bring with me on excursions, because I'm terrified to bring my pixel 4xl.. As such, I don't have a SIM card in mine. I have no idea if this would make any difference, but I'm not receiving the 'red state' status saying that verified boot is the issue. I have tried it with unchecking dm-verify, but maybe this hasn't worked. I'm thinking that it may have something to do with vbmeta*.img files. Like I said, I'll let you know if I have any luck

---

lunalsmojo said:
Like I said, I'll let you know if I have any luck
Click to expand...
Click to collapse
I'll do the same. Thank you for your feedback!

---

0

---

success!
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded

---

THANK YOU!
lunalsmojo said:
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
Click to expand...
Click to collapse
Yes, that worked for me as well!
So, first I tried to uncheck 'Preserve AVB 2.0/dm-verity' before patching the boot.img in Magisk but this didn't work (same bootloop).
Then I patched the boot.img in Magisk with the 'Preserve AVB 2.0/dm-verity' checked, and edited the file in HxD but found no trace of '2C 76 65 72 69 66 79' or 'verify'.
Finally I resigned myself to flash the empty vbmeta.img found on Hovatek's website (blog post 'DM_Verity is probably why that TWRP flash ends in a bootloop') and flashed the non-padded boot image produced by Magisk.
And this last option worked! So THANK YOU so much for your help!

---

Thank you sooo much! I finally got my brand new x7 pro rooted!

---

Have to ask
What os is does this refer to, I take it it's android 9?
What size is your bootloader/recovery in stock folder?
What mtk version?

---

lecrocq said:
... Thank you.
Click to expand...
Click to collapse
Hi May I ask if after rooting did you install a custom ROM?
Does the stock android that you get contains any personalization, like MUI or similar?

---

phaleg said:
Hi May I ask if after rooting did you install a custom ROM?
Does the stock android that you get contains any personalization, like MUI or similar?
Click to expand...
Click to collapse
I didn't install a custom rom, but I did eventually flash the Vanilla Bless GSI by @eremitein. Magisk still worked with patched boot, runs super smooth, and offers a ton of great customizations.
The stock rom is lackluster; it's the phone itself that has a ton of cool features like the underwater camera. I haven't really checked if all of those features are still usable with the GSI. To be honest, haven't really thought of it. Haven't gotten much of my intended use out of it during coroneumonia times. Sounds like a fun investigation, though. If it doesn't work straight out, I'm sure it can be made to work with a little tinkering.
@Pachacouti sorry for response forever later.... It's Android 10 with a MT6761 (Helio A22)

---

Hello boys. Thanks for how to root. I have rooted, but i had to reinstall system complete. Now i have root and new system and i have sms issue. Sometimes sms is coming, sometimes no..

---

Hello,
I'm trying to unlock my bootloader for my new Armor 7X but i'm struggling with the fastboot command.
First, there is two "fastboot" mode with this phone :
- the first when you do an : adb reboot bootloader. There is "=> FASTBOOT mode" in the screen. In this mode I can't detect my phone with "fastboot devices" command...
- the second mode is when you power on the phone with the volume "-"and you select "enter fastboot" in the menu. In this mode the phone is detected by "fastboot devices" ! But, the command "fastboot flashing unlock" always fails.
The error :
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
I've tried severals adb/fastboot tools without any succes. I think it's a driver issue but I'm not sure.
If someone have an idea, I will be greatful !

---

https://www.getdroidtips.com/unlock-bootloader-ulefone-armor-x6/ but i dont make this command fastboot flashing unlock. On phone you must chose unlock and confirm.

---

Probleme Solved, Use the NON-EU ROM !
I've find the problem ! It was the EU version of the ROM that blocked fastboot, so use the NON-EU version for that.
I've have succesfully rooted my phone, thank you for this thread !
I don't know exactly what are the differences between the two versions but everything seems to work normally.

---

Очень интересная тема. Наконец-то дошли руки до рутизации. Чрезвычайно долго описывать свой петь не буду, но скажу одно- знаю способ получения root до перезагрузки. Оранжевое предупреждение навсегда. Я допереведу ваш способ и попроьую сделать так-же. Спасибо!

---

Thanks for this guide
I got root now, has anyone got TWRP installed? Or another custom recovery

---

Does anyone have a problem receiving SMS?

---

Hi all, I've got a question.
I am trying to flash the boot.img but when I download the rom files from the ulefone website for the note 8, it does not include a boot.img. I can only see boot-debug.img and boot-sign.img . Which one should I select?

---

CupidAlaska said:
Hi all, I've got a question.
I am trying to flash the boot.img but when I download the rom files from the ulefone website for the note 8, it does not include a boot.img. I can only see boot-debug.img and boot-sign.img . Which one should I select?
Click to expand...
Click to collapse
This is not about Note 8.

---

lecrocq said:
THANK YOU!
Yes, that worked for me as well!
So, first I tried to uncheck 'Preserve AVB 2.0/dm-verity' before patching the boot.img in Magisk but this didn't work (same bootloop).
Then I patched the boot.img in Magisk with the 'Preserve AVB 2.0/dm-verity' checked, and edited the file in HxD but found no trace of '2C 76 65 72 69 66 79' or 'verify'.
Finally I resigned myself to flash the empty vbmeta.img found on Hovatek's website (blog post 'DM_Verity is probably why that TWRP flash ends in a bootloop') and flashed the non-padded boot image produced by Magisk.
And this last option worked! So THANK YOU so much for your help!
Click to expand...
Click to collapse
I would also like to confirm
lunalsmojo said:
success!
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
Click to expand...
Click to collapse
I would also like to confirm that this approached worked for me without issue. Some tips that may prove useful for someone, ensure that you have the correct drivers, adb, fastboot, vcom, and cdc. I had issues using fastboot because I did not have the correct drivers, a day was wasted on this.
I also used the tutorial from hovatek, his blog post is where you will find the vbeta.img, I could not correctly flash my patched magisk without first patching the vbeta.img.
Thanks again.