Hello to all,
i've been trying since 1 week now to root an Ulefone Armor 8, but it doesn't work. All drivers are installed. The OS installed on the device is Android 10, the build version is X70WSFFB.GQU.EEA.FHJ.Q0.TJAPA9VDYPTS.0703.V3.01. I have already contacted Ulefone and asked if there is another build version (for EU), but it is the only one currently available.
In the firmware there are two boot.img. One is called "boot.img" and the other is called "boot-debug-img". First I only patched the "boot.img" with Magisk and flashed the patched "magisk-patched.img" via ADB. After that the Armor 8 had a bootloop. The bootloop could be removed by flashing the original "boot.img" via ADB. The Armor started normally again.
After that I patched the "boot.img" and the "boot-debug.img" with Magisk and renamed them to "magisk-patched1.img" and "magisk-patched2.img". After that I flashed first the " magisk-patched1.img" and then the " magisk-patched2.img" via ADB. The Armor 8 then had a boot loop again. To get the bootloop away, the original "boot.img" was flashed back and Armor 8 is back in its factory default state.
How can it be rooted, what should I do differently? Could it be because there are two "boot" files in the firmware?
Sorry if my english is not perfect.
Thanks for your help and tips.
Greetings
https://www.getdroidtips.com/root-ulefone-armor-8/
I have tried that too, but it doesn' t work.
I flashed the "boot.img" with Magisk, from this Magisk created the file "patched_magisk.img". I moved this file to the ADB folder. After that I did it again with the file "boot-debug.img". Then I put the armor in fastboot mode and first I entered the command "fastboot flash boot_a magisk_patched.img".
ADB writes: writing 'boot_ a'... FAILED (remote: This partition doesn't exist)
After that I still moved the patched "boot-debug.img" into the ADB folder and entered the command "fastboot flash boot_b magisk_patched.img".
ADB writes: writing 'boot_b'... FAILED (status read failed (Too many links))
Magisk didn't create 2 patched files from 1 "boot.img", but in the unpacked ROM there are 2 .img files, namely "boot.img" and "boot-debug.img", which I patched one after the other and then flashed.
I have also downloaded the firmware of Armor 7. Of course not to install it, just to see if there are 2 boot.img (= boot.img + boot-debug.img) in it, too. For Armor 7 there is only 1 file "boot.img". For Armor 8 in the firmware there are "boot.img" and "boot-debug.img"
I have now tried overall:
just flash the patched "boot.img" = bootloop
flash only the patched "boot-debug.img" = bootloop
then first the patched "boot.img" and then the patched "boot-debug.img" = bootloop
Now just now again with the command "fastboot flash boot_a magisk_patched.img" = error message and then continue with the command "fastboot flash boot_b magisk_patched.img" = error message.
I think the problem is that there are 2x boot.img files in the ROM?
Edit:
And the SP-Flash-Tool shows that I should remove the battery, but the Armor has a fixed battery.
The SP Flash Tool now works after reinstalling the Vcom driver.
I have now extracted the boot.img of Armor 8 with the SP Flash Tool via "Readback". This file was then patched with Magisk. The file "magisk_patched.img" is together with the file boot.img in the same folder.
This was then flashed to the Armor with the SP Flash Tool in "Download only" mode. The flashing process is running normally and finally "Download Ok".
After that the Armor 8 will start normally and without bootloop, but it still has no root.
Does anyone have an idea?
I also have an armor 8 and I noticed that when u enter developer mode u can unlock the bootloader from there. Which allows you to install root access more successfully
after tapping on the kernel build go back and enter the option where it says system. There u will find the developer options.
after that, I had to follow some steps from this video
I got the stock ROM from the Ulefone website https://www.ulefone.com/support/software-download.html
where I was able to get the boot.img and patch it with magisk however I kept on getting a boot loop so I'll probably figure out another way to root it
1st
2nd
ignore
Have you succeeded yet? I am interested in this phone but want to be sure it can be rooted
Instead of trying to patch it from fastboot, just try booting! Follow the instructions below.
You may want to try the following steps: Just ignore the part about using their rom since it is a different phone. You should be using the Ulefone ROM
[Guide] Install Magisk on your device, updated to handle OTAs easily
[Update in 1st September 2018] Magisk v17 stable has been released, so the August security update: a new method, more OTA-compliant, is written. Hi all, this section is quite gaunt, so I'll post my experience on unlocking and rooting my brand...
forum.xda-developers.com
So save you some clicking, I'll just paste the relevant part below:
How to root
0. You need "debug usb" and "oem unlock" enabled under "developer options" on phone's settings.
1. First, if you don't have already done it, unlock phone's bootloader:
Code:
adb reboot bootloader
fastboot oem unlock
ATTENTION: THIS WILL WIPE YOUR DEVICE, ALL USER DATA WILL BE LOST! And no, when you'll have finish this guide, you can't lock it again (each lock-unlock operation will wipe the device)
2. Download ROM system image from official site. Pay attention to download the corresponding version of your actual OS (look in system settings your current build number).
3. Extract "boot.img" from the just downloaded archive and put somewhere in your device (e.g. in a microSD, just remember where you put it).
4. Download and install Magisk Manager apk.
5. Open Magisk, choosing "yes" when it asks to install Magisk-v*.zip, then choose "patch boot image" and select "boot.img" copied in step 3.
6. At the end of patching process, Magisk will tell you where "patched_boot.img" is been stored, keep a note on it and close.
Now's the updated part, that will make possible to apply OTAs:
7. Copy "patched_boot.img" on your computer, then run this on a terminal:
Code:
adb reboot bootloader
fastboot boot patched_boot.img
fastboot reboot
This will temporarily give you root privileges (until next reboot).
8. Magisk Manager can now make the root permanent: open it and tap "Install", then "direct install (recommended)". This way (instead of flashing directly patched_boot.img) Magisk Manager can remove and reinstall root privileges directly.
9. Just to be sure that your phone doesn't install updates without your acknowledgement, go to Developer Options and disable "Automatic system updates".
Ta-dà! Now you should have Magisk permanently installed (you can check it re-opening Magisk Manager).
-------------------------------------------------------
Time to update? Here's how
If you've followed what is written above, applying an OTA should be quite easy now.
a. Go to Magisk Manager → Uninstall → Restore Images. Do not reboot now or you will have Magisk uninstalled!
b. Now go to Settings → System → System Update and apply OTA. If it fails you've some tweak on system partition that you've forgot to remove, so try to figure it out and retry. Wait for the installation to complete. DO NOT RESTART NOW.
c. Open Magisk Manager again and press Install → Install to Inactive Slot.
d. Reboot and enjoy
-----------------------
PLEASE ADVISE IF THIS WORKS!
As the guy clearly mentioned, there's a boot.img and a debug_boot.img whenever i try to patch any of that and use fastboot to flash it I only get a bootloop
The bootloader is already unlocked and there's nothing else I can do to get this phone rooted
There's also no twrp currently supported for.it and that's pretty much it
I just needed help with this but it seems like this phone is very unknown and unsupported
MasDbs101 said:
As the guy clearly mentioned, there's a boot.img and a debug_boot.img whenever i try to patch any of that and use fastboot to flash it I only get a bootloop
The bootloader is already unlocked and there's nothing else I can do to get this phone rooted
There's also no twrp currently supported for.it and that's pretty much it
I just needed help with this but it seems like this phone is very unknown and unsupported
Click to expand...
Click to collapse
Have you explicitly tried
fastboot BOOT patched_boot.img
just BOOTING the patched boot image. just ignoring the the flash command for now.
This shouldn't cause a bootloop since it'll just revert back to the virgin boot.img
TWRP isn't needed for rooting.
Thank you for sharing this , I will try it later today and let you know what happens.
MasDbs101 said:
Thank you for sharing this , I will try it later today and let you know what happens.
Click to expand...
Click to collapse
Any luck?
stizarch said:
Any luck?
Click to expand...
Click to collapse
Bootloop
Finally, I successfully rooted! Procedure is the same as in the post 7, but before flashing patched boot you should flash empty vbmeta image:
fastboot flash vbmeta vbmeta_null.img
and then:
fastboot flash boot boot_magisk_patched_root.img
and reboot to system:
fastboot reboot
I attached empty vbmeta and patched boot.
knedlyk said:
Finally, I successfully rooted! Procedure is the same as in the post 7, but before flashing patched boot you should flash empty vbmeta image:
fastboot flash vbmeta vbmeta_null.img
and then:
fastboot flash boot boot_magisk_patched_root.img
and reboot to system:
fastboot reboot
I attached empty vbmeta and patched boot.
Click to expand...
Click to collapse
how did you get a null vbmeta file i need one for the ulefone armor 10 5g i wonder if its just empty it will work or something will try
zenoblank34 said:
how did you get a null vbmeta file i need one for the ulefone armor 10 5g i wonder if its just empty it will work or something will try
Click to expand...
Click to collapse
yes flashing vbmeta null over vbmeta on ulefone armor 10 5g worked as well i got root access
Armor8 said:
Hello to all,
i've been trying since 1 week now to root an Ulefone Armor 8, but it doesn't work. All drivers are installed. The OS installed on the device is Android 10, the build version is X70WSFFB.GQU.EEA.FHJ.Q0.TJAPA9VDYPTS.0703.V3.01. I have already contacted Ulefone and asked if there is another build version (for EU), but it is the only one currently available.
In the firmware there are two boot.img. One is called "boot.img" and the other is called "boot-debug-img". First I only patched the "boot.img" with Magisk and flashed the patched "magisk-patched.img" via ADB. After that the Armor 8 had a bootloop. The bootloop could be removed by flashing the original "boot.img" via ADB. The Armor started normally again.
After that I patched the "boot.img" and the "boot-debug.img" with Magisk and renamed them to "magisk-patched1.img" and "magisk-patched2.img". After that I flashed first the " magisk-patched1.img" and then the " magisk-patched2.img" via ADB. The Armor 8 then had a boot loop again. To get the bootloop away, the original "boot.img" was flashed back and Armor 8 is back in its factory default state.
How can it be rooted, what should I do differently? Could it be because there are two "boot" files in the firmware?
Sorry if my english is not perfect.
Thanks for your help and tips.
Greetings
Click to expand...
Click to collapse
Hello I tried but I fail ..
I install all drivers..
But when
Adb reboot bootloader .. rebooted..ok
Fastboot oem unlock ... Waiting for device...
So I cannot unlock the bootloader
have you tried
fastboot flashing oem
or
fastboot flash oem
zenoblank34 said:
have you tried
fastboot flashing oem
or
fastboot flash oem
Click to expand...
Click to collapse
Only work for me
adb reboot bootloader
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock
fastboot -i 0x0E8D flash boot magisk_patched.img
fastboot -i 0x0E8D flash vbmeta vbmeta_null.img
fastboot -i 0x0E8D reboot
rebooting...
Thanks people, it worked for me.
Can you tell me how much time do you need to fully charge from 0 to 100% ?
And do you use charger from box?
PabloWalker13 said:
Only work for me
adb reboot bootloader
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock
fastboot -i 0x0E8D flash boot magisk_patched.img
fastboot -i 0x0E8D flash vbmeta vbmeta_null.img
fastboot -i 0x0E8D reboot
rebooting...
Click to expand...
Click to collapse
What does it mean the code 0x0E8D?
Would anyone be able to direct me or send me the proper information on how to root my OnePlus 9 global LE2115? Because their are to many threads and Im getting confused
You can either use boot.img or you can boot into twrp and flash magisk.apk. 2 options for A11
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
xLLALLOx said:
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
Click to expand...
Click to collapse
A12 root method is different. Not like A11 where you flash the patched boot.img,it won't work. VBmeta and a vendor.img is used also. Also, TWRP is for A11. If you want root,Use the tool here: https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/
Use option 5 and then 6 and reboot. Magisk will be installed. Click the magisk app and update it.
Note: use your phone to download and extract file with password that OP provides in the link
I unlocked my bootloader successfully for my IN2019 Verizon edition listed here: https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
But I can't find the Boot.img for my build number 11.IN67CD - Does anyone know where I can find this? I could boot any of the TWRP versions successfully.
Do you need to root it? Sideload a Magisk .zip instead.
www.windows11xda.sa/arabiasaudit
i already rotted the device with android 11
original is boot file and patched magisk delta boot file down bellow
those file for same as instantnoodlev_15_O.01_210110 OP8 Verizon 11.IN67CD
to flash just reboot device into fastboot mode and then open Minimal ADB and Fastboot and follow the command bellow after unlocking bootloader
fastboot devices
fastboot flash boot (drag the file into command)
fastboot reboot
done
thank me later
T_A_Z_202 said:
i already rotted the device with android 11
original is boot file and patched magisk delta boot file down bellow
those file for same as instantnoodlev_15_O.01_210110 OP8 Verizon 11.IN67CD
to flash just reboot device into fastboot mode and then open Minimal ADB and Fastboot and follow the command bellow after unlocking bootloader
fastboot devices
fastboot flash boot (drag the file into command)
fastboot reboot
done
thank me later
Click to expand...
Click to collapse
Can u share twrp file sir
T_A_Z_202 said:
i already rotted the device with android 11
original is boot file and patched magisk delta boot file down bellow
those file for same as instantnoodlev_15_O.01_210110 OP8 Verizon 11.IN67CD
to flash just reboot device into fastboot mode and then open Minimal ADB and Fastboot and follow the command bellow after unlocking bootloader
fastboot devices
fastboot flash boot (drag the file into command)
fastboot reboot
done
thank me later
Click to expand...
Click to collapse
Please share patched boot.img sir
i did share it but the site delete it
T_A_Z_202 said:
i did share it but the site delete it
Click to expand...
Click to collapse
Do u have telegram? U can send from telegram
T_A_Z_202 said:
i did share it but the site delete it
Click to expand...
Click to collapse
i need boot.img sir
Hello,
how can I root my phone with magisk 25.2?
My bootloader is already unlocked.
Thank you very much!
t0bM said:
Hello,
how can I root my phone with magisk 25.2?
My bootloader is already unlocked.
Thank you very much!
Click to expand...
Click to collapse
First,
Find the boot.img of your firmware
Patch it using magisk app
Find a patched vbmeta of your phone's version
Move those to your pc and into the folder where fastboot is found
Reboot to fastboot mode and connect it to your pc
Type fastboot devices to check if it is connected
Type fastboot flash boot nameoffile.img(the boot file name)
Type fastboot flash vbmeta nameoffile.img(the vbmeta file name)
Restart the phone either manually or using fastboot reboot
you should also put this command to avoid bootloop or any problem with booting your phone
fastboot --disable-verity --disable-verification flash vbmeta nameoffile.img(vbmeta file name)
The easiest method is by downloading magisk latest apk from the github and rename it to Magisk.zip and flash it with your custom recovery
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
What device are you talking about ?
f1tm0t said:
What device are you talking about ?
Click to expand...
Click to collapse
Tab p11 4gig
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
f1tm0t said:
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
Click to expand...
Click to collapse
Threr is no twrp sadly
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
mingkee said:
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
Click to expand...
Click to collapse
I tried it i flashed patched boot.img only in fastbootd still boots me in to the bootloader
LSS4181 said:
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
blocky3321 said:
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
Click to expand...
Click to collapse
Which Magisk version did you use? From what I can tell any official Magisk version should work.
I haven't really tested the recent builds of vvb2060's Alpha or huskydg's Delta... so if you're using these versions I can't really help you much...
Additionally, you need to check which slot you are now, and through fastbootd check which slot actually has system, vendor and such. Normally the super partition only has enough size for one slot. You may have entered a wrong slot that doesn't have usable system.
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
Getting Started: What's Your Device ?
Tab p11 4gig
Device->settings->About : Model & Hardware -> Lenovo ??? (Tb-j606f,TB-J616F...) In your case stiker on box or on back.
mingkee said:
who told you to flash vbmeta.img?
Click to expand...
Click to collapse
???