Database Info

Rooting for March Update?

Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.

lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer

rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.

lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.

rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)

lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute

Won't let me simend the link

rob420p,
Please provide links.

rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?

I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.

lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?

I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY

marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!

lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:

Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks

max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952

I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.

max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?

lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....

Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now

Brick - No fastboot - EDL only - Set active slot?

I have not one, but two bricks. I bought one to unbrick the other, but the reverse happened. Using the EDL tool from this forum, I made a full and then an all backup and tried to use it to unbrick the other. No success. Now I cannot enter fastboot on either device, but both will enter EDL. I think at least one will fastboot if I can switch the active a/b slot.
Can the active a/b slot be switched via a command in the edl mode? Or is there another way to switch the active slot on a brick without fastboot access? Thank you

I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA

noobstyle1337 said:
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
Click to expand...
Click to collapse
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?

There's no command to switch active slots that I know of and I've gone into the source on fh_loader.
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
The fact that you aren't getting a ZTE logo at all indicates that you do not have a mixed up slot a/b situation anyway. It probably means you need to fix your AOP files. Of course the original EDL tool doesn't really let you do that. If you have the US version you can use the tools I uploaded to target just the AOP files and try restoring them from your original backup... either the a or b slot one should work.
Make sure you keep your original ALL/FULL backups (both) from the EDL tool, they're probably 99% good and you'll be doing yourself a favor not to delete or modify them.
groundslug said:
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
Click to expand...
Click to collapse

You can only change the slots if you are in Fastboot. You have doing it wrong ... if you have an A2020G you can flash the firmware ... if you have the A2020u version then you should ... flash the correct one
so in itself quite simple .... flash edl firmware and then unlock .. then you boot into the fastboot mode and then you have to use these lines
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then
fastboot --set-active=a
in any case you have to unlock to access the fastboot menu
then you should be able to boot
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
remember to flash Android 9 edl firmware because otherwise the unlock won't work
---------- Post added at 04:47 PM ---------- Previous post was at 04:39 PM ----------
also remember that some firmwares have to be in the flash folder or in the backup folder if it doesn't work

bobthenormal said:
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
Click to expand...
Click to collapse
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!

groundslug said:
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
Click to expand...
Click to collapse
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.

bobthenormal said:
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
Click to expand...
Click to collapse
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.

groundslug said:
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
Click to expand...
Click to collapse
Just replying real quick since I have a min and I saw a few things you can try... 1. make sure you're installing twrp itself with the zip after you boot into it with fastboot, 2. use the two flags when you write vbmeta just in case (I forget them but one is dm verify and the other is no verity, should be in the original LOS16 thread) and 3. try the fix bootable partition tool from my tools after you install. the LOS16 image has a similar problem as all other images that it has a specific slot it works on (B I think) so if you end up installing and trying to boot it from the other slot it locks into a fast bootloop. Don't bother installing the addons until LOS is booting, so just do a reboot to system after you flash it, fix bootable. If it doesn't boot then it has to be something I'm not thinking of. Goodluck!

It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!

groundslug said:
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
Click to expand...
Click to collapse
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.

Rise55Chrom said:
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Click to expand...
Click to collapse
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!

groundslug said:
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
Click to expand...
Click to collapse
Phenomenal! Best advice, I have received... Thank you so very much. You hit it right on the head. I'll be sure to fill ya in asap when I have the time to get after it. Appreciate you.

bobthenormal said:
EDL tool
Click to expand...
Click to collapse
Hello, where can I find this program? EDL tool

Is there a root for the ulefone Armor 9?

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

Infinix hot 10 play (X688B) stuck bootlooping to fastboot after orange state, help

i recently rooted my phone with magisk patched boot image and was working good after i restored my files, then it rebooted itself and now its stuck on orange state then going to fastboot mode, after that it loops back to orange state over and over again, please help

Reflash phone's Stock ROM to get rid off of all modifications you applied so far.

and what if i want to root the phone? flashing the stock rom gets rid of magisk, am i stuck without an option to root it? or should i install a custom recovery or cus os like calyxos?

new problem, i cant flash the stock rom using sp flash tool, gives me this weird error:
STATUS_BROM_CMD_STARTCMD_FAIL
any help?

I did this to my old phone if sp flash ain't working
"fasboot flash all slot a". if a/b partition
"fastboot flash all". if not a/b partition
and I feel like this method is faster than sp flash tool
edit:
lucky you could go to fastboot unlike mine can't go anywhere when I tried to flash my device it just reboot after 6 or 5 seconds ;-;

Does somebody have the stock rom for Infinix Hot 10 Play X688B?
There is the builder number X688B-H659ABCEFGHI-Q-GL-220109V524

Tzuyoda said:
Does somebody have the stock rom for Infinix Hot 10 Play X688B?
There is the builder number X688B-H659ABCEFGHI-Q-GL-220109V524
Click to expand...
Click to collapse
Download Infinix Stock ROM for all models (Latest Firmware)
Download the latest Infinix Stock ROM Firmware (Flash File) for all the available Infinix smartphones, feature phones, and tablets.
androidmtk.com
I could only find this one site that has all of the stock roms of XOS. Not exactly the model number. Just a 'c' and 'b' difference

Did you fix it? If not I can help you

I think the stock roms would work.

boomzkik said:
Did you fix it? If not I can help you
Click to expand...
Click to collapse
do you have the latest firmware files? i removed root and updated ota and i cant find any source of firmwares online, only the stock ones. can i use stock boot.img and patch it with magisk then install the patched stock boot.img with fastboot on an updated firmware?

mlgpro12345 said:
i recently rooted my phone with magisk patched boot image and was working good after i restored my files, then it rebooted itself and now its stuck on orange state then going to fastboot mode, after that it loops back to orange state over and over again, please help
Click to expand...
Click to collapse
Please I need your help on how you were able to root your infinix hot 10. I have the same phone and I was following YouTube tutorials they told me to use minimal adb and fastboot.. all the commands worked great but when I use command fastboot flash boot and paste my patched boot img it shows error... Unknown partition cannot determine image filename for boot img or so.

Stuck at TWRP splash screen

I recently updated to MIUI v12.5.1.0.RCDMIXM using a recovery zip through TWRP. A few days later I decided to flash Magisk by patching the boot.img from the same zip and flashed using fastboot.
Everything worked fine until I rebooted to recovery using the Magisk app. Now it's stuck at the TWRP splash screen, can't even reboot or enter fastboot with power and volume buttons because it will always try to boot to TWRP.
What do I need to do to fix this?
This is where I got the TWRP

Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.

VD171 said:
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
Click to expand...
Click to collapse
Okay, but how exactly can I do that? It's been stuck like this since last night and won't go to fastboot with vol keys..

Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.

VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?

VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash

Reyproject said:
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
Click to expand...
Click to collapse
Exactly.
You need to bypass EDL auth:
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com

Reyproject said:
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Click to expand...
Click to collapse
You said "fastboot", so you need the fastboot ROM.
SP flash tool does NOT need the device to be turned off, it just need to REBOOT.
If you try to flash while a reboot to another reboot, it will works perfectly.

Which magisk did you flash? 23 is not working for 9A

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk V23.0 is the BEST MAGISK EVER !

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
It does tho, i've been using it since the first use of this phone (12 and 12.5)

Applewubs said:
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Click to expand...
Click to collapse
Are you still in 12.5? Do you also use a custom recovery in that version?

Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk v23 works just fine, just patch the boot.img file of your ROM version and flash it with custom recovery or fastboot.

Reyproject said:
Are you still in 12.5? Do you also use a custom recovery in that version?
Click to expand...
Click to collapse
Theres one TWRP that doesnt have a splashscreen, in that one just block and unblock the screen while on recovery and it'll work fine. BUT your internal storage isn't going to be accesible, its encrypted and (for some reason) on 12.5 twrp cant unlock the storage, you'll have to do everything on your sdcard

Reyproject said:
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
Click to expand...
Click to collapse
I thinks its because they cant unlock the storage, they keep trying and just keeps stuck on trying.