Database Info

[GUIDE] Rooting your Essential PH-1

WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Useful and important general information can be found in the second post here.
NOTES
1. If you flash the TWRP Installer when you've already got Magisk installed, your device will keep booting to the recovery. You should be able to fix this by just simply reflashing Magisk.
2. If you have TWRP installed via the TWRP Installer, you will not be able to install stock OTA updates. You will have to reflash the stock boot image for whatever build you're running beforehand.
3. The prebuilt TWRP image may not have touch functionality if you're using the September 2018 Update or newer. Patching the boot image, however, for these builds with the TWRP Installer will allow touch to work flawlessly. Here is a pre-patched September 2018 Boot Image with TWRP. It should also work with builds newer than September. Since it's based off the September 2018 update, I suggest not using this as your main boot image but rather just as a replacement for the pre-built TWRP image from the official TWRP thread.
4. Simple "flash and forget" boot images pre-patched with Magisk and TWRP are provided by @aer0zer0 and are available here. They are based on ianmacd's variant of Magisk. If you are running stock, you can flash these boot images to get root and TWRP instead of following the guide to patch it yourself. Here is January's.
If you don't care about TWRP and simply want to just root your device, you can just simply patch the boot image for your ROM with the Magisk Manager and flash it in fastboot with
Code:
fastboot flash boot patched_boot.img
The link to the boot images for most stock builds can be grabbed from my Google Drive link in the second post or from the back-to-stock zips.
REQUIREMENTS
An unlocked bootloader
Working adb and fastboot environment, along with knowledge on how they work.
The latest build of TWRP along with the TWRP Installer. Read Note 3 above beforehand.
1. Download the latest build of TWRP and the TWRP Installer. Transfer the TWRP Installer zip to your device.
2. Reboot your phone into fastboot. Once in fastboot, change your device's current slot using the command
Code:
fastboot set_active other
If the command above doesn't work for you, use fastboot getvar current-slot followed by fastboot -aX, replacing "X" with the slot opposite (a or b) from your current slot.
3. Once your device's current slot has been switched, flash the TWRP image you downloaded earlier using the command
Code:
fastboot flash boot twrp.img
Depending on your version of fastboot, the above command might not work either. In that case, you can enter the following command, replacing "X" with your current slot (a or b).
Code:
fastboot flash boot_X twrp.img
4. Once TWRP has been flashed, boot into the recovery.
5. Once you have booted into TWRP, simply flash the TWRP Installer zip.
6. Once you have finished flashing the TWRP Installer zip, boot to recovery on the OPPOSITE slot. You can do this from TWRP by going to "Reboot", then selecting the opposite of the current slot (if on A, select Slot B. If on B, select Slot A), then select "Recovery." You can also do this through fastboot by running the same command from step 2.
7. Once you have booted back into TWRP, simply flash the Magisk zip and you are now good to go! Feel free to flash anything else like kernels while you're at it.
8. Reboot. :good:
NOTE: TWRP WILL remain installed on your device so long as you reflash the installer zip after every update.

Important Information for the Essential PH-1 can be found here. Keep it bookmarked.
Tips on updating via OTA after rooting can be found here.
In the case that you mess something up on your device, you may find it helpful to revert back to stock with the unofficial factory images graciously provided by @invisiblek and @aer0zer0 over here.
Official TWRP XDA Thread for the Essential PH-1
Join the Essential PH-1 Discord Server! -- Lots of cool people here!
Join the Essential PH-1 Development Telegram Channel!
Stock Boot Images for most builds can be found at my Google Drive link here.
Have a Red Verity Warning when booting your device? Click here.
If the link to the boot.fix.red image isn't working, you can also find it here or in my Google Drive link in the first post.
Essential Phone (PH-1) Partition Layout
Dumping Boot Images
1. Find the current slot with
Code:
fastboot getvar current-slot
or
Code:
adb shell getprop ro.boot.slot_suffix
2. Switch to the opposite slot in Fastboot using the command
Code:
fastboot set_active other
3. Flash TWRP using the command
Code:
fastboot flash boot twrp.img
4. Now, boot into TWRP and use the following command from your PC, replacing X in "boot_X" with the original slot from step 1 (a or b). TRIPLE CHECK:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot_X of=/sdcard/boot.img
5. Profit! Don't forget to switch back to the original partition with the same command from step 2!
extractTarFork() error when restoring data from a TWRP backup
1. Reinstall the ROM from which the backup is based on.
2. Wipe your data. You can do this from the recovery or from fastboot using the command
Code:
fastboot -w
3. Boot into the ROM. When going through the initial setup, use the EXACT same security setup as the one from your backup. For example, if you used a Fingerprint + Password in the backed up ROM, use the exact same combo along with the exact same password as well. There is no need to set up anything else, like accounts.
4. Flash, install, and reboot into TWRP. You should now be able to restore the data backup without any issues.

AFH mirrors for images:
Build NMJ32F
NMJ32F patched boot image
NMJ32F factory image
Build NMJ20D
NMJ20D patched boot image
NMJ20D factory image
TWRP (alpha v4)

Thanks for getting the latest boot image up so quickly.

Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?

how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.

prgopala said:
how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.
Click to expand...
Click to collapse
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.

Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?

@bmg1001 , good looks, here are more free XDA points to trade in for that pool table, lol.

gk1984 said:
Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?
Click to expand...
Click to collapse
As far as I know, TWRP still doesn't have decryption fully working just yet, but installing Magisk works fine without any factory resets.

prozo said:
Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?
Click to expand...
Click to collapse
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.

Did anyone manage to disable encryption? I tried everything and failed

bmg1001 said:
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.
Click to expand...
Click to collapse
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?

prozo said:
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?
Click to expand...
Click to collapse
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk

bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt

prozo said:
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt
Click to expand...
Click to collapse
The apk should be the same one found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Alright I got it to work
So I didn't use the APK instead I downloaded the zip from the XDA thread that is specifically for Magisk Module and then added via the modules tab on the left side of the Magisk Module APK.
After I restarted I had the newly installed APK to download and install the proper version of Xposed 88.2 sdk25
Another restart and boom I got the active module notification in green.
Thanks man!
Thread for downloads can be found here:
https://www.google.com/amp/s/forum....ed/unofficial-systemless-xposed-t3388268/amp/

Thank you for this!
My PH-1 is arriving today. SooOoo excited!

spotmark said:
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.
Click to expand...
Click to collapse
Would using flashfire work to install the ota?

drocny87 said:
Would using flashfire work to install the ota?
Click to expand...
Click to collapse
Couldn't tell you. I just used TWRP to flash the system and boot, and then took the update, and then rerooted.

[ALTERNATIVE] Root Mi A1 with TWRP Without disabling Ota

As you may imagine this simple guide will show you how to root your device with magisk from twrp recovery.
I know, there is already a guide by jashancheema that shows how to root this device, however it's difficult to update the system once you are rooted. In my opinion the way i'm about to show you is faster and easier.
Disclaimer: I am not responsible for ANY damage done to your phone, act at your own risk.
That's how you can root your phone with magisk and recovery without disabling ota.
1. First download magisk manager and magisk flashable zip from here (official thread)
Install magisk manager and copy the magisk flashable zip somewhere in your device or sd.
2. Download mohancm twrp recovery (recovery-3.2.1-2-oreo) from here (official thread)
NOTE: do not download the installer, you need the .img file bootable from fastboot (recovery-3.2.1-2-oreo.img)
3. Copy recovery-3.2.1-2-oreo.img into the fastboot folder.
4. Enable developer option from in the device, enable OEM unlocking.
5. turn off your device and enter into fastboot mode by holding voume down + power button, then connect your device to the pc.
6. now open fastboot and type this to check the connection, if the terminal return an andress your phone is correctly configured.
Code:
fastboot devices
7. type this from fastboot to unlock your bootloader.
Code:
fastboot oem unlock
8. now type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
9. once your recovey boot flash the magisk zip and reboot.
NOTE: do not install or flash twrp into your device or you won't be able to update through ota.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.

RESERVED

All works!!! :good::good::good::good::good:

WORK
I tried, it works. thank you!

funziona da dio! fantastico! bella guida

Great work!

i already flash twrp on my device, so i cannot install update OTA until i go back to unroot?

@H.A.L. 9000, I'm sorry for my ignorance but I wonder whether the bootloader unlock passage (that'd reset everything) is inescapable after installing an OTA update

Can I install ota with the unlocked bootloader?

Thanks for this I was always confused on how to update the phone after magisk.
Edit: you think it's possible to use a custom kernel with magisk and still maintain ota?

Thank you, the rooting part worked flawlessly. :good: Now waiting for the next OTA to see if that will work well too.

1. USB debugging doesn't have to be allowed?
2. Updating Android can be done with PC only?

I did exactly the same (as nicely outlined in MP) for the last few updates, and can confirm it's working perfectly. I was using this as the 'normal' way failed due to unknown reasons.
This approach does not required a patched boot-image available, so imho it's more robust and reliable than the 'normal' method.

iG0tB0lts said:
Thanks for this I was always confused on how to update the phone after magisk.
Edit: you think it's possible to use a custom kernel with magisk and still maintain ota?
Click to expand...
Click to collapse
+1
Have you found out?

H.A.L. 9000 said:
As you may imagine this simple guide will show you how to root your device with magisk from twrp recovery.
I know, there is already a guide by jashancheema that shows how to root this device, however it's difficult to update the system once you are rooted. In my opinion the way i'm about to show you is faster and easier.
Disclaimer: I am not responsible for ANY damage done to your phone, act at your own risk.
That's how you can root your phone with magisk and recovery without disabling ota.
1. First download magisk manager and magisk flashable zip from here (official thread)
Install magisk manager and copy the magisk flashable zip somewhere in your device or sd.
2. Download mohancm twrp recovery (recovery-3.2.1-2-oreo) from here (official thread)
NOTE: do not download the installer, you need the .img file bootable from fastboot (recovery-3.2.1-2-oreo.img)
3. Copy recovery-3.2.1-2-oreo.img into the fastboot folder.
4. Enable developer option from in the device, enable OEM unlocking.
5. turn off your device and enter into fastboot mode by holding voume down + power button, then connect your device to the pc.
6. now open fastboot and type this to check the connection, if the terminal return an andress your phone is correctly configured.
7. type this from fastboot to unlock your bootloader.
8. now type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
9. once your recovey boot flash the magisk zip and reboot.
NOTE: do not install or flash twrp into your device or you won't be able to update through ota.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse
Can't I just install syst update through twrp?

Rooting Mi A1 using this method worked. But the guide needs updating:
1.You must enable usb debugging
2.You must install magisk manager after unlocking bootloader. Installing it before is useless because unlocking bootloader will wipe all data.

freekarol said:
unlocking bootloader will wipe all data.
Click to expand...
Click to collapse
not till 9.5.11

freekarol said:
Rooting Mi A1 using this method worked. But the guide needs updating:
1.You must enable usb debugging
2.You must install magisk manager after unlocking bootloader. Installing it before is useless because unlocking bootloader will wipe all data.
Click to expand...
Click to collapse
Well, that happened to me.. Total WIPE... So, i decide to stop. But this night i'll try again, after a full backup. For me this is important because i need to use Android Auto, with aamirror.

I do regular backups so it was ok with me. It also should be in the guide as a first step: backup your phone. It seems like the guide is not for beginners... After rooting, you can face two problems:
1. From time to time, Magisk crashes. Just open it again.
2. There will be a camera lag. Installing a Magisk module should solve it(I haven't tried it yet): https://www.youtube.com/watch?v=UqcQKqhL3ok

there is some indication that 'fastboot boot twrp.img' wipes all the data!
Not sure when it started and if there is a way to avoid it - any idea?

[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 new Mi A2 Lite.
I'm not responsible if you make some mistake and accidentally transform your phone in a stone (but it's almost impossible)... <3
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
-------------------------------------------------------
Troubleshooting
- If your phone seems bootlooping, try to switch it off and on again (sometimes it doesn't start on first boot). If it keeps doing that, donnoh, reflash original "boot.img" and start again!
- For someone seems that Magisk 16 doesn't work well, but since the stable branch has reached 17.0, just use it!
- If you already have rooted your phone in different ways that this one explained here (and you don't have "uninstall" option on Magisk Manager), I suppose that the simpliest way to follow this guide is to reflash factory boot.img and start from the beginning of this post again, but if you figure out alternative ways, post them here!
-------------------------------------------------------
References
https://forum.xda-developers.com/mi-a1/how-to/mi-a1-monthly-updates-t3750419
https://forum.xda-developers.com/showpost.php?p=77448469&postcount=49
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Thanks to BubuXP for the efforts that he puts in this thread, helping anyone who's got problem following this guide.
Have a nice day!

If you posted this a couple of hours early, I'd save a couple hours of my life doing other things instead of discovering by myself what you just wrote :laugh:
However, add to your guide to change the update channel in Magisk Manager to "beta" instead of stable, because only starting from 16.7 (the actual beta version) has support to A/B partitions scheme (the one used by our device). When the new stable version of Magisk will be released, that could be removed.
Add also that installing modules isn't possible out of the box, because both Magisk Manager and Android stock lack the unzip binary (I'm searching for a solution).

few minutes has past and Im looking here at endless boot animation:/
so I do fastboot factory flash, did it again and now no issues at all,thanks!

BubuXP said:
If you posted this a couple of hours early, I'd save a couple hours of my life doing other things instead of discovering by myself what you just wrote :laugh:
However, add to your guide to change the update channel in Magisk Manager to "beta" instead of stable, because only starting from 16.7 (the actual beta version) has support to A/B partitions scheme (the one used by our device). When the new stable version of Magisk will be released, that could be removed.
Add also that installing modules isn't possible out of the box, because both Magisk Manager and Android stock lack the unzip binary (I'm searching for a solution).
Click to expand...
Click to collapse
That's weird, (saw also your message in the other thread)I didn't had all these issues and I'm using magisk 16.0 (no beta). I could also install modules out of the box without having to do anything special
Edit : added quote

I had another ROM installed,It was more "light" than this one posted here. Many google app was added after I did flash. My phone should be global version and I buy it from local store. It was ODLMIFF also.
edit:seems that screen cast is not working

kidoucorp said:
That's weird, (saw also your message in the other thread)I didn't had all these issues and I'm using magisk 16.0 (no beta). I could also install modules out of the box without having to do anything special
Edit : added quote
Click to expand...
Click to collapse
That's weird indeed...
I've re-downloaded the fastboot image and I'm flashing it right now, then I will retry patching boot.img
I found an updated 16.7 version in the Pixel 2 XL forum that fixes some weird behaviors other users had., I will try it too.
EDIT 1: I usually do all my operations under Debian Linux. This time I used the Mi Flash tool under Windows, and I patched the boot.img with 16.0.
I don't know what of the two changes fixed the problem, but now it's working without problems (but the first time I tried directly with your boot.img patched with 16.0 and it was not working ).
FYI, sha512 of the old and new fastboot image downloaded were the same, so it was not a problem of defective download.

BubuXP said:
That's weird indeed...
I've re-downloaded the fastboot image and I'm flashing it right now, then I will retry patching boot.img
I found an updated 16.7 version in the Pixel 2 forum that fixes some weird behaviors other users had., I will try it too.
Click to expand...
Click to collapse
Im using 16.0. Also phone sometimes wont boot, stuck at screen with unlocked text or stuck in boot animation. I guess xiaomi is very wrong choice for somebody who want customize his android:laugh:

mik.y said:
Im using 16.0. Also phone sometimes wont boot, stuck at screen with unlocked text or stuck in boot animation. I guess xiaomi is very wrong choice for somebody who want customize his android:laugh:
Click to expand...
Click to collapse
I edited my previous post, just to inform you.
I think those problems arise because the phone is too young, many things have to be fixed by Xiaomi. And also things will get better when the new stable Magisk that will support new Android features will be released.

1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that

I'm not sure, but apparently I found the culprit.
The only way to make Magisk work flawlessly is following the guide in the first post.
I mean, if I use the patched_boot.img made in another phone it causes always some problems, as if Magisk in the process of patching the boot.img put a signature of the actual phone inside the img and it will work fine only in the same phone that created the patched boot.img
Not only this, but if I flash the phone with the stock ROM via fastboot, and then use the patched_boot.img created previously on the same phone before flashing, it won't work neither (something in the "signature" changes, like it is a new phone).
kidoucorp said:
1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that
Click to expand...
Click to collapse
Probably using the beta channel with 16.7 could improve your situation. I'm using 16.7 right now, following the OP guide, and it is working great (until now).

BubuXP said:
Probably using the beta channel with 16.7 could improve your situation. I'm using 16.7 right now, following the OP guide, and it is working great (until now).
Click to expand...
Click to collapse
I can confirm that I'm using Magisk stable 16.0, and everything works fine, but I suppose it's because I've flashed booth partition A and B. I've updated the first post anyway, thanks!
kidoucorp said:
1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that
Click to expand...
Click to collapse
My old Mi A1 does the same too, it's a bit strange but once you know it, you can handle it

It works !!
Device: Mi A2 Lite (4/64GB) global version.
(cpu-z reports: Snapdragon 626 @2.02 GHz)
Using Magisk 16.7 and boot.img from global rom "V9.6.4.0.ODLMIFF (Android O) " (oem rom from xiaomi).
Only difference is the method which I tried and fail initially, was I cmd "adb reboot bootloader" from the PC which doesn't work for me.
It says failed to write boot_a and boot_b.
I had to do the hardware reset to get into fastboot. (pressing vol-down and power button simultaneously).
Once I am in fastboot mode, from the PC cmd execute the following sequence
1. fastboot flash boot_a patched_boot.img
2. fastboot flash boot_b patched_boot.img
3. fastboot reboot
And voila!, it works beautifully. Thanks for all the contributors of this thread
It runs all apps including apps that cannot be rooted. (have to do the "hide" magisk)
So far so good, no issue to be found.
Have a great day people.

eddiechanks said:
Device: Mi A2 Lite (4/64GB) global version.
(cpu-z reports: Snapdragon 626 @2.02 GHz)
Using Magisk 16.7 and boot.img from global rom "V9.6.4.0.ODLMIFF (Android O) " (oem rom from xiaomi).
Only difference is the method which I tried and fail initially, was I cmd "adb reboot bootloader" from the PC which doesn't work for me.
It says failed to write boot_a and boot_b.
I had to do the hardware reset to get into fastboot. (pressing vol-down and power button simultaneously).
Once I am in fastboot mode, from the PC cmd execute the following sequence
1. fastboot flash boot_a patched_boot.img
2. fastboot flash boot_b patched_boot.img
3. fastboot reboot
And voila!, it works beautifully. Thanks for all the contributors of this thread
It runs all apps including apps that cannot be rooted. (have to do the "hide" magisk)
So far so good, no issue to be found.
Have a great day people.
Click to expand...
Click to collapse
Same for me. Just extract the boot.img from the official Xiaomi rom (downloadable from their website), patch that through Magisk manager, and flash the patched .img to boot_a and boot_b using fastboot. Works flawlessly.
Only thing I haven't been able to do is remove the forced encryption. I was able to change the encryption password however using vdc cryptfs.

worked flawlessly, did have to re-install magisk manager after flashing the patched boot images, but all was fine after a quick apk reinstall.

Hi guys,
Sorry for those newbie questions (I come from an old Nexus 5 with Lineage, and I am far from magisk) :
How is going the update ? will it be OTA ? Will it be manual (in this case where do I find the file) ? Do we need to re-root after OS update ?
Thanks in advance !

arnofor said:
Hi guys,
Sorry for those newbie questions (I come from an old Nexus 5 with Lineage, and I am far from magisk) :
How is going the update ? will it be OTA ? Will it be manual (in this case where do I find the file) ? Do we need to re-root after OS update ?
Thanks in advance !
Click to expand...
Click to collapse
The OTA update should be automatic, but I'm not sure 100%
However, after every system update, you have to do the boot patching procedure again but using the boot.img from the new version.

Can I do the unlock part and the rest in a couple of weeks? Without data loss?

ncar123 said:
Can I do the unlock part and the rest in a couple of weeks? Without data loss?
Click to expand...
Click to collapse
You can unlock whenever you want, but every time the bootloader is locked or unlocked, the phone resets its data (but I'm not 100% sure, maybe it's only locking or only unlocking).
But why unlocking now and wait 2 weeks? Couldn't you unlock the phone directly in 2 weeks when you are ready?

BubuXP said:
You can unlock whenever you want, but every time the bootloader is locked or unlocked, the phone resets its data (but I'm not 100% sure, maybe it's only locking or only unlocking).
But why unlocking now and wait 2 weeks? Couldn't you unlock the phone directly in 2 weeks when you are ready?
Click to expand...
Click to collapse
I don't want to setup my phone with my data twice...

ncar123 said:
I don't want to setup my phone with my data twice...
Click to expand...
Click to collapse
So it's ok. Unlock now while you don't have any data in the phone and whenever you want, you can install Magisk later.

Root Guide

Found this while trolling through the Chinese forums, none of this is my work, I have translated the instructions as best I can.
Disclaimers; I have not tried this, it may brick the global rom, the custom recovery is likely only in Chinese language.
You need:
Boot Loader unlock code (currently probably not possible to get)
Huawei USB drivers
Recovery image (attached)
Magisk package (attached)
files: https://mega.nz/#!PM0EmYLA!384hZjmJ9ExNc7Q8rSqssHunWSO7AxQ3GA4qet6RX4E
Extract files to a folder, open command prompt and change into this folder.
Unlock bootloader (BL unlock will clear the phone data, please do a backup)
- Obtain an official unlock code
- double-click to open the "Huawei Toolbox.exe"
- click "unlock bootloader "
- enter the unlock code in the pop up window , click OK, and wait for the phone to unlock complete restart.
Flash the third-party recovery
- Turn off the phone and connect the computer. Press and hold the “Volume Down” button and “Power button” until the phone displays the android page and release your finger.
- open command prompt and run:
fastboot flash recovery_ramdisk twrp.img
- after seeing the two OKAY feedback from the command line, the flash is successful.
Enter recovery to flash root image (this step will clear all data of the mobile phone including memory card, please make a backup in advance)
- long press “Volume Up” and “Power” ", until you see the a twrp logo, release the keys and wait to enter recovery mode
- After entering recovery, click the second item “Clear”, click “Format Data Partition” in the lower left corner, slide the slider to enter the clear, wait for the progress bar to complete
- Return to the recovery homepage, click on the last item "Advanced", select the last item "Remove data forced encryption", slide the slider to release, wait for completion
Copy the root package to the phone
- In Command Prompt type or copy the following commands
adb push magisk-installer.zip /sdcard
adb push magisk.apk /sdcard
Install Image
- Whilst still in recovery mode, click the first item to install the magisk-installer.zip package from the sdcard , slide the slider to install, wait for the flash to complete, and restart the phone
- After reboot is complete, click “File Manager”, select the apk file “magisk.apk” just copied from the memory card when install is finished, open the magisk app and click “No, thank you” in the pop-up window
- Return to the command line tool, type the code to execute, and wait for the phone to automatically restart
Fastboot reboot recovery
- after the restart, open "magisk", it should show that the installation is complete, that is, ROOT is achieved.

Anything in that forum on how to manually update phone?

technotika said:
Anything in that forum on how to manually update phone?
Click to expand...
Click to collapse
That is actually what I was looking for
But none, problem is the v20 (china version) seems to get OTA way before us, they all got v143 2 weeks ago.
I did find the menu to do it, but it only supports if the image is stored on an sdcard, and when I click it it says no sdcard found. so its impossible.

Tried same with similar results. One day eh? ?

İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader

greenblueye said:
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
Click to expand...
Click to collapse
If you read what I wrote in the first post you would see you cannot root without a bootloader unlock code.

Tested! Work bootloader code on Russia services (Cost 20USD)

belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Nice! Did unlocking bootloader factory reset your device?

Yes of course. All new Huawei and Honor do a reset after unlocking

i get bootloader unlock code from funkiehuwai for 20$
any one tried this instructions and have success?
I just wonder comments below will work?
*adb push magisk-installer.zip /sdcard
*adb push magisk.apk /sdcard
because there is no sd card support for view20?
when i opened huawei-toolbox.exe its in chinese and im afraid to continue other instructions

Did anyone use TWRP and which version?
Did the View 20 Boot correctly?
I read in a Forum, that with the view 20 doesn´t boot correctyl with TWRP. The reason should bei the Storage...
Best regards

Unlocked Bootloader
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Does that mean you rooted you device (with the files from above) or you just unlocked the bootloader?
I was able to unlock my bootloader with a code from funkyhuawei (about 18 €, site seems to be down currently). I did not use the unlock tool above, mainly because its chinese
- Enabled "USB debugging" and "OEM unlock" in developer settings
- Connected phone to PC, opened adb and used "adb reboot bootloader"
- Unlocked via "fastboot oem unlock *16digit code*"
This worked out fine. However, as far as i understand it magisk is installed over twrp (recovery_ramdisk), removing twrp but granting you root. This makes me kind of nervous since twrp has been a nice safety net on several occasions. This is why I stopped after unlocking the bootloader. Maybe someone has more experience on this? Why is there so little interest in rooting this phone?
Regards

root achieved
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards

garris_bibop said:
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
Click to expand...
Click to collapse
Well done good job:good:
İ have chinese version PCT-AL10 9.0.1.144 right now. Do you think i can use the same way? İ wonder from which version to extract recovery_ramdis.img

I have my view20 rooted
Thanks for the instructions.

greenblueye said:
I have my view20 rooted
Thanks for the instructions.
Click to expand...
Click to collapse
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?

garris_bibop said:
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
Click to expand...
Click to collapse
I get recovery-ramdisk from firmware PCT-AL10 9.0.1.129 . my phone is on version 9.0.1.144 but it worked:good:

After root i can not auto update software. 9.0.1.166 version is seen on ota but after download it says update is unsuccessful. Do you have any suggestion?

I think thats to be expected when rooted. Go for manual update I guess (https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). Personally I wouldn't bother with every update unless theres interesting new features and/or security updates. just to be on the safe side I would reflash the original recovery_ramdisk before updating! And backup your data!

NM Card
Hello !
Unless I'm mistaken, the View20 must be able to use nano sd cards (NM Card)

How to root Ulefone Armor 11 5G

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?