Perform the update without losing the root - Xiaomi Mi A1 Questions & Answers

Perform the update without losing the root - Xiaomi Mi A1 Questions & Answers

Hi,
I would like to do the last update for the Mi A1, but without losing the root. I'm rooted with CF-Auto-Root and SuperSu is installed without TWRP. How can I do? Possible with FlashFire?
Thanks.

AFAIK it isn't possible. There is a feature in MagiskManager that lets you root the OTA update in the second slot but its not working for our device yet. The same goes for FlashFire.

Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.

So, I too rooted my phone using the CF-Auto-Root. I tried to unroot through SuperSU, but it didn't work. I also tried to flash the boot.img, and that didn't work either. I'm new to all of this, and I don't really know what I'm doing.
How can I actually unroot this sucker?

What do you mean by it "didn't work"? What steps have you tried? You're not supposed to flash the CFAR boot.img, instead you should use `fastboot boot boot.img` to boot into it (don't do anything after it's run, it'll automatically boot), use FlashFire to flash the zip version of SuperSU (found here http://supersu.com/download), and then reboot normally on the phone.

justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
After the full unroot, all the apps that had access for root (eg. Viper4Android, BusyBox, SELinux, etc) will working again after the update?!
http://techintouch.it

The apps will work once the system is rerooted, but you'll need to authorize the apps in SuperSU again.

Can I use the SuperSu OTA survival mode? Maybe it works?

Ok, so here's what I did.
I followed kraatus90's guide to using CF-Auto-Root. I ran the .bat executable, and I rooted my phone. Everything works. I downloaded SuperSU from the Play Store to manage the apps.
I then tried to lock the bootloader, and got the "The system was destroyed" error. So, I had to unlock it again for the phone to function.
I went into the SuperSU app and tried to do the full permanent unroot, but all I got was "Uninstallation Failed"
So, then I went to find a stock boot.img, and got one.
Now, I don't know how to reverse what I did.
I tried booting into the stock boot.img from fastboot mode, and it looked like it worked because my rooted apps spotted working, but I wasn't able to download the latest security patch.
Those are the steps I did, and I don't know how to proceed further.
EDIT 1: So, after toying around with it some more, and trying to recover the stock.img in both FlashFire, and SuperSU, and trying to flash an external stock.img through fastboot, I think I know what the problem is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that the A/B partitions are what are getting me in trouble. Do I need to change the active partition through fastboot? do I need to flash something to one of the partitions through FlashFire? What can I do?
EDIT 2: So turns out, you need to use fastboot flash boot_b boot.img, and then it'll work.

Can I flash the OTA file with FlashFire without losing root? I don't have TWRP installed and I'm rooted with SuperSu.

justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data

kkn14 said:
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data
Click to expand...
Click to collapse
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp

DeV91 said:
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp
Click to expand...
Click to collapse
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?

kkn14 said:
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?
Click to expand...
Click to collapse
i didnt read the whole thread, but i didnt find a january oreo boot image there.
only flash a patched boot.img that is from the current build you are on.
anyway, you could try to simply boot the patched boot.img with fastboot:
fastboot boot patched_boot.img
while this may boot the system without problems, things like not being able to activate wlan could happen. because this boot image was for a different build.
however, as long as it boots the patched image, you could then simply go to magisk manager and press install direct (recommended method) - this way it will patch your stock boot image, modfying your partition directly. remember: you only "booted" the patched boot image before with the "fastboot boot" method, this will only "load" the boot.img in to memory, and will not modify your actual partition.
another way would be to just boot into twrp revovery and flash the newest magisk on your own. i'd recommend this method as you will not risk in flashing a wrong boot.img from a different build version
fastboot boot recovery.img
as long as you just boot stuff, this will only be loaded into RAM, which is a volatile memory and will be lost on a reboot - hence not modifing partitons and maintaining the possibility of taking OTAs.

Related

Guide: Setting up Android Pay on a rooted Note 5

***THIS GUIDE DOES NOT WORK. THIS SIMPLY ALLOWS CARDS TO BE ADDED TO ANDROID PAY. PAYMENTS WILL NOT PROCESS. THIS IS A WORK IN PROCESS.***
Unfortunately us rooted users are unable to use Samsung Pay. Samsung Pay is superior to Android Pay due to its MST feature which allows the use of any card reader to take payments from the phone. Samsung Pay as of this time doesn't support a lot of cards, So Android Pay is a great backup. Just as Samsung tries to stop rooted users from using Samsung Pay, Google tries to stop them as well by blocking Android Pay. This guide will show you how to get around that.
1.) You need a non rooted phone to start.
You can either flash your Note 5 completely back to stock, or use another phone to do it. Whichever phone you use MUST be able to be rooted or this will not work. This guide will assume you will use a second device to setup Android Pay, as I did, so that you don't have to wipe your Note. If you use your Note 5 to do this, just modify the guide as needed.
2.) Download the Android Pay app from the Playstore to your non-rooted phone
3.) Setup Android Pay application fully with all your bank cards and info
4.) Force close Android Pay app
5.) Root the device
6.) Install Titanium Backup
7.) Make a backup of the Android Pay app using Titanium Backup
8.) Move the Titanium Backup folder to either a computer or OTG drive
- If you only backed up Android Pay, there should be 3 files inside of the folder.
9.) Move your Titanium Backup folder to your rooted Note 5
10.) On the Note 5 download and install Titanium Backup
11.) Open Titanium Backup and select: menu - preferences - backup folder location
- Point the backup folder location to wherever you moved the Titanium backup folder to on the phone.
12.) Close and reopen Titanium Backup if it does not automatically do this when you exit settings
13.) Select menu again and then "batch actions"
14.) Select restore missing apps with data
- Android Pay should be the only app being restored
15.) After the app is restored, DO NOT OPEN IT.
16.) Open the superSU app and select: settings - "Enable Superuser" (uncheck the box) and let it finish
17.) Reboot
18.) When the phone boots up, open Android Pay and set it up as normal
19.) Open the superSU app and select: settings - "Enable Superuser" (check the box) and let it finish
20.) Reboot
21.) Done.

I do not think it'll work when making a purchase...
You can install "cigital safety net playground" from the play store to test if the state of your phone will allow it to pass Android Pay verification.
I my experience (I was using Android Pay on a rooted Moto X 2015), the only way to get Android pay to work with root, is to use Chainfire's systemless root and NOT to modify anything "major" in the system (host file and minor files edit are okay, replacing or adding a system app breaks it)

Hmm, the app says failed. I will test the pay function right now. I just need to run to the store.

seh6183 said:
Hmm, the app says failed. I will test the pay function right now. I just need to run to the store.
Click to expand...
Click to collapse
Yup... no surprises there.
Now try this:
- Back to stock, unlocked bootloader
- Install and setup your cards in Android pay
- Install TWRP or any custom recovery
- Try rooting with the latest systemless root (you may have to force a systemless install by typing "echo SYSTEMLESS=true>>/data/.supersu" on shell before install the zip in TWRP)
- Remove the folder "/su/xbin_bind" and reboot for Android pay compatibility
- Try "Cigital safety net playground" it should pass.

timeToy said:
Yup... no surprises there.
Now try this:
- Back to stock, unlocked bootloader
- Install and setup your cards in Android pay
- Install TWRP or any custom recovery
- Try rooting with the latest systemless root (you may have to force a systemless install by typing "echo SYSTEMLESS=true>>/data/.supersu" on shell before install the zip in TWRP)
- Try "Cigital safety net playground" it should pass.
Click to expand...
Click to collapse
Isn't systemless for android 6.0+ only and the kernel has to support it? I have it on my nexus but didn't think it was possible on the note.

seh6183 said:
Isn't systemless for android 6.0+ only and the kernel has to support it? I have it on my nexus but didn't think it was possible on the note.
Click to expand...
Click to collapse
From the man himself in the linked thread: "If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image (...)"

timeToy said:
From the man himself in the linked thread: "If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image (...)"
Click to expand...
Click to collapse
This is amazing news and will be implementing this immediately.

Yup it failed at the card swiper.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Booted to CWM and flashed "unsu.zip" which removed all superuser from the phone. Then flashed beta 2.61 because they say it's the last working version for Android Pay. I rebooted from CWM and chose not to install root. When it Booted the phone was not rooted. I don't have a folder in /data. Supersu says this when I open it:

Wiped everything and reflashed my rom and still doesn't work. I am getting this error in CWM after flashing the superSU zip:
- Extracting ramdisk
--- Failure, aborting
I'm going to Odin back to stock and try again.

seh6183 said:
Wiped everything and reflashed my rom and still doesn't work. I am getting this error in CWM after flashing the superSU zip:
- Extracting ramdisk
--- Failure, aborting
I'm going to Odin back to stock and try again.
Click to expand...
Click to collapse
About the ramdisk issue, make sure you have the stock kernel and use the latest version v2.65, it fixed a lot of compatibility issues. To enable Android pay compatibility on v2.65 you need to delete the folder "/su/xbin_bind" and reboot.
I am not yet able to test this (waiting for my Samsung promos to go trough before messing up with KNOX), but Chainfire's himself is reporting it working:
Chainfire said:
(...)It's working great on my Note5 (G920T) on OJ5 and S6 on OI9(...)
Click to expand...
Click to collapse

I got systemless root installed.
My kernel (Arter) wasn't compatible with the systemless flash and that was causing the error. Had to switch back to ext4 and flash a modified stock kernel to get it to work.
Now here's the problem. You can't flash a custom rom without a custom recovery and you can't boot with a custom recovery unless you have a modified kernel. So that means you need a kernel and recovery at minimum if you want a custom rom. Once you install those 3 android pay fails to work again.
The only way I can get it to work is totally stock. That's boring. I need at least a custom rom. I was thinking that maybe I can flash my rom, flash unsu.zip, my kernel, and then somehow Odin my stock recovery back. Then setup android pay, then reboot and go back to a custom recovery to flash root.
Thoughts?

Flashed stock recovery and rebooted. Android pay still didn't work. Rebooted and flashed stock kernel and now it hangs on the first splash screen lol
Back to the drawing board. Going to ODIN back to stock and try different kernels I guess.

seh6183 said:
(...)Now here's the problem. You can't flash a custom rom without a custom recovery and you can't boot with a custom recovery unless you have a modified kernel. So that means you need a kernel and recovery at minimum if you want a custom rom. Once you install those 3 android pay fails to work again. (...)
Click to expand...
Click to collapse
Android pay will ONLY work with a 99.9% stock system partition. (no custom ROM that I know of)
Maybe this can work:
- Back to 100% Stock
- Install custom kernel and custom recovery
- Reboot into recovery, then install stock Kernel, no reboot, then flash systemless root, no reboot, then flash back stock recovery, then reboot.
That should get you systemless root with Android pay. No ability for full ROMs but the ability to run an Ad Block and disable the bloat...

timeToy said:
Android pay will ONLY work with a 99.9% stock system partition. (no custom ROM that I know of)
Maybe this can work:
- Back to 100% Stock
- Install custom kernel and custom recovery
- Reboot into recovery, then install stock Kernel, no reboot, then flash systemless root, no reboot, then flash back stock recovery, then reboot.
That should get you systemless root with Android pay. No ability for full ROMs but the ability to run an Ad Block and disable the bloat...
Click to expand...
Click to collapse
My rom is a stock deodexed, debloated rom. I am trying something, well two things, that may get me working. Otherwise I am confident that I can get a stock rom, debloated myself, systemless root, custom kernel, xposed, and android pay all working. I can live with that. I will update my guide when I make it happen.
So far the things to remember is that systemless root needs a certain kernel format to be able to flash, and android pay needs certain things in the rom to be present or it wont work. I know the chroma rom for nexus devices has working android pay with systemless and its heavily modified. I doubt the dev will share how he did it though

Didn't work. Can't get any modified rom to work. I just booted two different roms with a stock kernel and stock recovery and it failed the safetynet check. Wiped all and am reflashing stock as I write this and will do it one step at a time to see what causes the safety check to fail.

Flashed a stock rom with ODIN and booted. It passed safety check. Flashed CWM recovery and it passed. As soon as I flashed a custom kernel it failed the check and I haven't even gotten to the rooting part yet. As of right now I don't want to give up a rom AND a kernel simply for android pay. I will be updating this guide to have the mods take it down.

[N00B FR13NDLY] How to Root Android Nougat in 10 Steps (Much Easy)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video about this tutorial please watching
https://www.youtube.com/watch?v=n-2XYEUNy1o
Hi guys,to make root in 5x in nougat is much easy
1 - Put your device in fastboot mode and Unlock your bootloader
https://www.youtube.com/watch?v=hwDwxy3Z7bQ (use this,or other video of you like )
2 - Download This Files
5x TWRP https://dl.twrp.me/bullhead/
ADB Tools http://files.androidpit.info/content/adb-tools_treiber.zip
SuperSU (Put in your memory this file to install in TWRP)
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
3 - Extract "ADB Tools" and open all folders like this "adb-tools_treiber\adb-tools_treiber\adb-tools"
4 - Put TWRP "https://dl.twrp.me/bullhead/" in this folder
5 - in Windows 8 or 8.1,10 select "file,in top" and select open prompt command,and select open prompt command in administrator
6 - in "CMD" put this code :
fastboot flash recovery twrp-3.0.2-1-bullhead.img
7 - push volume down button 2x and push power button
8 - in recovery mode go to install,and select SuperSU2.76 after install select reboot system
9 -waiting your phone turn on
10 - Enjoy <3

Flashed, supersu app is there, but I still don't have root access?

It's already been mentioned in another thread that this does not work, at least not if you're encrypted.

pkadavid said:
It's already been mentioned in another thread that this does not work, at least not if you're encrypted.
Click to expand...
Click to collapse
I was told that encryption doesn't matter with the new TWRP that was released yesterday. Is that not true? I haven't tried it yet. Waiting for the Android N factory images to start clean.

I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.

Ryandos said:
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Click to expand...
Click to collapse
Do you mind sharing your steps? I followed Heisenberg's instructions however TWRP didn't stick, and SU didn't install. Thanks!
jsgraphicart said:
I was told that encryption doesn't matter with the new TWRP that was released yesterday. Is that not true? I haven't tried it yet. Waiting for the Android N factory images to start clean.
Click to expand...
Click to collapse
You can give it a try. Looks like people have had mixed results. TWRP hasn't stuck for me, and I couldn't install SU. I've seen a few other posts with the same result.

Is the SuperSU linked in this thread systemless root? If not, is systemless root available for the Nexus 5X? Chainfire creates so many threads I can't keep up with what's the latest and what's systemless and not systemless.

pkadavid said:
Do you mind sharing your steps? I followed Heisenberg's instructions however TWRP didn't stick, and SU didn't install. Thanks!
Click to expand...
Click to collapse
I decided to boot into TWRP instead of flashing it; instead of "fastboot flash recovery twrp.img", I just did "fastboot boot twrp-3.0.2-1-bullhead.img". This booted my 5x into TWRP without flashing it.
After that I flashed supersu-2.76.zip through twrp the usual way and rebooted. Obviously my twrp didn't stick but I'm not sure why or how this method succeeded in rooting.

Well, I did the same, did you flash supersu linked in the op?
Btw, twrp didn't stick for some reason first time I installed it(I unlocked bootloader, flashed twrp through fastboot, rebooted in twrp, and it worked. However, after I rebooted into the system, I couldn't boot back into twrp. It said 'no command'.)
Then I flashed it again with the same method, rebooted the system, and tried to boot back into twrp, and voila, now it did stick.
Weird.
Then I flashed supersu, the one linked in the op, and I've got supersu app, but as I said, no root access.

Ryandos said:
I decided to boot into TWRP instead of flashing it; instead of "fastboot flash recovery twrp.img", I just did "fastboot boot twrp-3.0.2-1-bullhead.img". This booted my 5x into TWRP without flashing it.
After that I flashed supersu-2.76.zip through twrp the usual way and rebooted. Obviously my twrp didn't stick but I'm not sure why or how this method succeeded in rooting.
Click to expand...
Click to collapse
I resolved the issue with these steps. Looks like something was messed up after I upgraded from 6.0.1 to 7 yesterday using the beta program. I noticed something was wrong because changes to the system UI via the stock settings (% in battery) didn't stick. A factory reset solved it.
1. factory reset (stock, encrypted)
2. install twrp -1 (it has stuck so far after two reboots) - https://dl.twrp.me/bullhead/
3. install su 2.76 (confirmed rooted) - http://forum.xda-developers.com/showthread.php?t=1538053
---------- Post added at 12:30 AM ---------- Previous post was at 12:24 AM ----------
jsgraphicart said:
Is the SuperSU linked in this thread systemless root? If not, is systemless root available for the Nexus 5X? Chainfire creates so many threads I can't keep up with what's the latest and what's systemless and not systemless.
Click to expand...
Click to collapse
It automatically installs systemless on newer versions of Android. Use the one below, and you'll be fine.
http://forum.xda-developers.com/showthread.php?t=1538053
---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------
Nightshadow931 said:
Well, I did the same, did you flash supersu linked in the op?
Btw, twrp didn't stick for some reason first time I installed it(I unlocked bootloader, flashed twrp through fastboot, rebooted in twrp, and it worked. However, after I rebooted into the system, I couldn't boot back into twrp. It said 'no command'.)
Then I flashed it again with the same method, rebooted the system, and tried to boot back into twrp, and voila, now it did stick.
Weird.
Then I flashed supersu, the one linked in the op, and I've got supersu app, but as I said, no root access.
Click to expand...
Click to collapse
Try the steps in my post above. I had the same thing happen. You'll have to do a factory reset.

Actually, seems like I have root access. Root checker says I do have it, the app I tried(quickboot) couldn't acquire root access at all. I guess it's because of the systemless root?
Only systemless root is available on 5X?

If you want Android Pay to work, then you need to do the following.
Flash Magisk.
Flash phh's SuperUser 17 (Magisk Version).
Install phh's SuperUser from the Play Store.
Then when you want to use Android Pay, temporarly disable root with Magisk Manager.
It would do you some good to read those thread's to see how things work. You can discuss Android Pay/magisk here.
Should go without saying you need to unlock and install twrp before you do any of this.

I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.

The1nonly1 said:
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
Click to expand...
Click to collapse
I can confirm that, I did completely the same.
Including flashing TWRP two times through fastboot, and it works now.

Ryandos said:
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Click to expand...
Click to collapse
The1nonly1 said:
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
Click to expand...
Click to collapse
I confirm this.
I'm using exactly same configuration (TWRP 3.0.2-1), flashed thru fastboot (fastboot flash recovery twrp-3.0.2-1-bullhead.img) and using SuperSU 2.76 systemless root

ikyeye said:
I confirm this.
I'm using exactly same configuration (TWRP 3.0.2-1), flashed thru fastboot (fastboot flash recovery twrp-3.0.2-1-bullhead.img) and using SuperSU 2.76 systemless root
Click to expand...
Click to collapse
So what's new? This is usual procedure to root every android version on a Nexus: flash latest TWRP recovery, latest supersu, done.

This worked perfectly on the first try! Thank you
Sent from my Nexus 5X using Tapatalk

[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
It should work when you flash it, but using it is still a try at your own risk procedure.
Our device comes with forced encryption and, more important,
verity which checks at every boot if /system partition has been changed or not.
If /system has been changed, verity won't allow booting your device which means
you can't flash anything unless you disable verity.
So, you must be sure to keep /system in ReadOnly mode in TWRP and don't try to alter it unless you're using a custom Kernel/boot to disable verity.
Of course, custom ROMs come with custom boot, so no worries about verity security with Lineage or AOKP for example.
Click to expand...
Click to collapse
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on moto.shreps.fr.
Changelog:
twrp-3.0.3-n2-athene_shreps.img
- Kernel and boot update - should be compatible with more variant
- Some TWRP fixes
twrp-3.0.3-n1-athene_shreps.img
- Qseecom and crypto stuff updated to N
> I'm able to decrypt my /data partition (F2FS) - Tested on XT1650-03_NPL25.86-17-3
- Fully rebased on AOSP Recovery 7.1
- TWRP bump to 3.0.3, with a lot of fixes
- Dark Material Theme
- Removed cursor pointer
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z, Tool/Utility for the Moto Z
Contributors
Shreps
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2017-01-30
Last Updated 2017-03-07

[ROOT] How to root with latest N firmware NPL25.86-17-3
Simple procedure:
Unlock your BL
Flash this TWRP Recovery
Download the superuser zip (thanks to phh)
Flash it through TWRP
Reboot
Install phh's SuperUser app from play store
Enjoy

Shreps said:
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
Click to expand...
Click to collapse
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again

erfanoabdi said:
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again
Click to expand...
Click to collapse
Use superuser systemless root, has mentionned in post #2. It's safer.

Shreps said:
Use superuser systemless root, has mentionned in post #2. It's safer.
Click to expand...
Click to collapse
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser

erfanoabdi said:
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser
Click to expand...
Click to collapse
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser

[email protected] said:
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser
Click to expand...
Click to collapse
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser

erfanoabdi said:
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser
Click to expand...
Click to collapse
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2

Shreps said:
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2
Click to expand...
Click to collapse
Currently I'm using phh without any issue but FlashFire doesn't work with this, it requires SuperSU

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP

erfanoabdi said:
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP
Click to expand...
Click to collapse
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA

kethsawant said:
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA
Click to expand...
Click to collapse
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
I tried that in Stock rom but ended up in bootloop..

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)

kethsawant said:
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)
Click to expand...
Click to collapse
OK use my TWRP and flash this super su
This is not modded version just old version of stock superSU
Please test it and tell how is it.

Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.

paulnorinn said:
Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.
Click to expand...
Click to collapse
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.

Shreps said:
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.
Click to expand...
Click to collapse
Ok, thats fix it. I can now touch the screen. Guess I have to do it on every boot?
Thanks for the tip.

OK I formatted my partitions in twrp and it was formatted as ext4. I read somewhere that the moto Z uses f2fs by default. Is this true and I just reduced performance of my phone because of a bug in twrp? I couldn't find an option to format as f2fs.

I need help flashing boot.img

My moto e4 is the USC XT1768 one.
I wanted to install magisk so I removed root with SuperSU Unroot, then tried to flash the stock boot.img and it just got stuck on the bad key screen.
so i reflashed my backup boot.img and i'm back where i started.
How can i flash the boot.img without getting stuck in the loop?

shogunreaper said:
My moto e4 is the USC XT1768 one.
I wanted to install magisk so I removed root with SuperSU Unroot, then tried to flash the stock boot.img and it just got stuck on the bad key screen.
so i reflashed my backup boot.img and i'm back where i started.
How can i flash the boot.img without getting stuck in the loop?
Click to expand...
Click to collapse
It's likely dmverity causing issues. After you flash the stock boot.img, before booting system, you could try flashing dm no verity zip.
Or better yet,when you have your system running properly, install magisk manager app. Then inside the app, use it to patch the stock boot.img. then install the magisk patched boot.img. then you will have magisk installed.

madbat99 said:
It's likely dmverity causing issues. After you flash the stock boot.img, before booting system, you could try flashing dm no verity zip.
Or better yet,when you have your system running properly, install magisk manager app. Then inside the app, use it to patch the stock boot.img. then install the magisk patched boot.img. then you will have magisk installed.
Click to expand...
Click to collapse
there are 2 advanced options, should i have both "preserve force encryption" and "preserve AVB 2.0/dm-verity" checked in advanced settings or just the first one? (that's default)

shogunreaper said:
there are 2 advanced options, should i have both "preserve force encryption" and "preserve AVB 2.0/dm-verity" checked in advanced settings or just the first one? (that's default)
Click to expand...
Click to collapse
I don't use either one. I find running encrypted with root causes issues. I usually disable dmverity and encryption, then format data in twrp (format, not wipe. To remove encryption). But you can try to keep encryption if you like. Definitely don't want to preserve dmverity.

madbat99 said:
I don't use either one. I find running encrypted with root causes issues. I usually disable dmverity and encryption, then format data in twrp (format, not wipe. To remove encryption). But you can try to keep encryption if you like. Definitely don't want to preserve dmverity.
Click to expand...
Click to collapse
alright so i patched the boot.img and then flashed it in twrp, it was able to boot successfully.
quick question, are all the things under the downloads tab compatible? Can you brick your phone by installing them?

shogunreaper said:
alright so i patched the boot.img and then flashed it in twrp, it was able to boot successfully.
quick question, are all the things under the downloads tab compatible? Can you brick your phone by installing them?
Click to expand...
Click to collapse
Magisk modules won't install on e4. It's because of the f2fs loopback bug in Moto devices. There is a fix. F2fs loopback bug workaround module. It's in the download section in magisk manager. Download it (not install) then boot to twrp and flash it there. Then you can install magisk modules. Most should be compatible. Non will brick. If one causes your phone not to boot, you can remove it. There is a magisk mount zip in magisk forum. Flashing it mounts magisk in recovery so you can remove the offending module with twrp file manager. Which ones do you want to try?

madbat99 said:
Magisk modules won't install on e4. It's because of the f2fs loopback bug in Moto devices. There is a fix. F2fs loopback bug workaround module. It's in the download section in magisk manager. Download it (not install) then boot to twrp and flash it there. Then you can install magisk modules. Most should be compatible. Non will brick. If one causes your phone not to boot, you can remove it. There is a magisk mount zip in magisk forum. Flashing it mounts magisk in recovery so you can remove the offending module with twrp file manager. Which ones do you want to try?
Click to expand...
Click to collapse
I was going to try out the sony apps enabler to start.
I seem to get "/data/magisk_merge.img mout faled..." when trying to install from inside magisk, but it works from in twrp. Is that just something i have to deal with on my device or is there a workaround?
thanks for helping.

shogunreaper said:
I was going to try out the sony apps enabler to start.
I seem to get "/data/magisk_merge.img mout faled..." when trying to install from inside magisk, but it works from in twrp. Is that just something i have to deal with on my device or is there a workaround?
thanks for helping.
Click to expand...
Click to collapse
That's the f2fs loopback bug I was talking about. Get the f2fs loopback bug workaround module from the download list. Download it (don't install in magisk manager) you have to install it in twrp. Then modules will install normally. I outlined all of that in my previous post.

madbat99 said:
That's the f2fs loopback bug I was talking about. Get the f2fs loopback bug workaround module from the download list. Download it (don't install in magisk manager) you have to install it in twrp. Then modules will install normally. I outlined all of that in my previous post.
Click to expand...
Click to collapse
i did install that, it was the first thing i did.

shogunreaper said:
i did install that, it was the first thing i did.
Click to expand...
Click to collapse
If you installed that in twrp, you should be able to install all modules normally in magisk manager. Some modules need to be updated to work properly in the latest magisk version. Some do say to flash in recovery. But if you installed the work around module, you should not get the "failed to mount" error anymore. It moves magisk to /cache, which is already mounted and ext4.

madbat99 said:
If you installed that in twrp, you should be able to install all modules normally in magisk manager. Some modules need to be updated to work properly in the latest magisk version. Some do say to flash in recovery. But if you installed the work around module, you should not get the "failed to mount" error anymore. It moves magisk to /cache, which is already mounted and ext4.
Click to expand...
Click to collapse
it's there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Where did you find the stock boot.img? I have accidentally deleted it and could do with it back...
If anybody has it then can they send it to me please?
Thanks

voxboi said:
Where did you find the stock boot.img? I have accidentally deleted it and could do with it back...
If anybody has it then can they send it to me please?
Thanks
Click to expand...
Click to collapse
You can get it from the stock firmware package

madbat99 said:
You can get it from the stock firmware package
Click to expand...
Click to collapse
Where can I find that?

voxboi said:
Where can I find that?
Click to expand...
Click to collapse
Depends on which version you have. You haven't provided any info.
All Moto firmwares are here
You need to know which version you have.

madbat99 said:
Depends on which version you have. You haven't provided any info.
You need to know which version you have.
Click to expand...
Click to collapse
I have attempted to flash the stock boot.img but when I do, nothing happens. (my boot partition is completely gone - is there any way to remake it?) I tried to flash the full zip as well but it had no META-INF so it was unflashable.
Moto E4 (woods)
SKU: XT1761

voxboi said:
I have attempted to flash the stock boot.img but when I do, nothing happens. (my boot partition is completely gone - is there any way to remake it?) I tried to flash the full zip as well but it had no META-INF so it was unflashable.
Moto E4 (woods)
SKU: XT1761
Click to expand...
Click to collapse
You can't flash a firmware package in TWRP. You have to use fastboot.
What do you mean "nothing happens"? How are you flashing it?
Flash the firmware for your specific model. There are a bunch of different versions. Flash the full firmware, it has the partition table in it.
How do you think you got rid of your boot partition? That's not likely.
Flash the firmware with fastboot. The commands are in the flashfile.xml in the firmware zip. Extract it.
Or you can use RSDlite to flash it.
What is your model (SKU) and software channel?

[GUIDE] How to Root Xiaomi Mi A2 Magisk

Clarification:
This tutorial only works in the system compilation V9.6.10.0.ODIMIFE, August 5 2018.
Requirements:
Unlocked the bootloader, PC with the installed drivers and the adb tools.
Here is the guide on how to unblock the bootloader, install the drivers and the adb tools.
Steps:
1-Preparing the smartphone
Download Magisk manager from the following link, and install it on our cell phone.
Then we will proceed to turn off our smartphone.
Once turned off, we will press at the same time volume - and power for about 5 seconds, until our cell phone turns on (this in order to enter the fastboot mode), if everything was done correctly, the following image will appear on your screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We connect the cell phone to the PC
2-Preparing the PC
Download the following .rar file and extract it and find two folders.
The folder "ROOT XIAOMI MI A2 MAGISK 16" is for those who wish to root their smartphone with version 16 of Magisk.
The folder "ROOT XIAOMI MI A2 MAGISK 16.7" is for those who wish to root their smartphone with version 16.7 of Magisk.
You must choose whichever you like and open it, inside it you will find the .bat file called "ROOT AUTO", (we make sure to have our smartphone connected to the PC in fastboot mode) we double click to execute it, and it will begin to flash the "patched_boot" file. After finishing the flashing, you must double click on the .bat file called "REINICIAR REBOOT" and your smartphone will restart.
Finally, open the Magisk Manager app and you can verify that your smartphone is rooted with the version you chose from Magisk.
Suggestion:
If for some reason it does not allow you to install modules, I advise you the following solution.
Enter the Magisk Maneager app, then the "Install" option, select "install" again and finally select "Direct Install (Recommended)".
With that, the boot image will be patched again, solving the problem.
Here I leave a video on YouTube that is a visual guide to the procedure.
In the future I will share a guide on how to root regardless of the compilation of the system.

Reserved

If the next OTA arrives, what should I do? Can it soft brick the device? What I need to do to update and mantain the root? Thank you

After the recent Magisk update I don't have root anymore.
Is it possible to use this method with magisk v.17?
Which boot image should I use?

Yes. I just updated to 17.
Use the recommended option.
Update the manager app too.

NVM
I've figured it out by myself
Sorry to be such a big noob, but i don't understand how to update magisk.
I tried to follow again this guide and to use the "ROOT AUTO.BAT" file inside the ROOT XIAOMI MI A2 MAGISK 16 folder, but everytime it reboots into the system Magisk 17.1 is asking to be installed and there's no "direct install" option (i can download the zip file or select the boot img to update).
I already tried to uninstall the magisk manager app and to reinstall it only after the aformetioned procedure, but the result is the same.
I tried to install the old Magisk manager 5.8.3, to use magisk 16, but it says it's not rooted and it asks for update.
I tried following this other guide, and using the direct command "fastboot boot patched_boot.img", but the result is always the same: there's no option for direct install Magisk and there's no root.
Please help me. What am I doing wrong?
Posting the solution for all the other noobs like me:
With the new magisk version installed, I downloaded on my phone the stock boot.img (of the august firmware that is currenlty running on my phone) as indicated in this post from the OTA dump thread .
Then I launched the magisk app (still without root) and selected install, and chose boot image to patch from the download folder on the phone
The magisk app patched the boot image creating the patched_boot.img that i trasnferred on my pc.
I then used the automatic method in this thread replacing the patched boot img in the folder, rebboted the phone and now I have root on magisk 17.1
Sorry to be such a noob but I'm not very experienced with magisk

I was have the same problem.
What I did is full reset and it did work.

Malobestino said:
NVM
I've figured it out by myself
Sorry to be such a big noob, but i don't understand how to update magisk.
I tried to follow again this guide and to use the "ROOT AUTO.BAT" file inside the ROOT XIAOMI MI A2 MAGISK 16 folder, but everytime it reboots into the system Magisk 17.1 is asking to be installed and there's no "direct install" option (i can download the zip file or select the boot img to update).
I already tried to uninstall the magisk manager app and to reinstall it only after the aformetioned procedure, but the result is the same.
I tried to install the old Magisk manager 5.8.3, to use magisk 16, but it says it's not rooted and it asks for update.
I tried following this other guide, and using the direct command "fastboot boot patched_boot.img", but the result is always the same: there's no option for direct install Magisk and there's no root.
Please help me. What am I doing wrong?
Posting the solution for all the other noobs like me:
With the new magisk version installed, I downloaded on my phone the stock boot.img (of the august firmware that is currenlty running on my phone) as indicated in this post from the OTA dump thread .
Then I launched the magisk app (still without root) and selected install, and chose boot image to patch from the download folder on the phone
The magisk app patched the boot image creating the patched_boot.img that i trasnferred on my pc.
I then used the automatic method in this thread replacing the patched boot img in the folder, rebboted the phone and now I have root on magisk 17.1
Sorry to be such a noob but I'm not very experienced with magisk
Click to expand...
Click to collapse
after a reboot root is gone and also magisk shows not installed

I dont know how to help you.
For me is working fine e even after rebooting the device.
Maybe someone more experienced than me can give you a better solution

Malobestino said:
I dont know how to help you.
For me is working fine e even after rebooting the device.
Maybe someone more experienced than me can give you a better solution
Click to expand...
Click to collapse
""Then I launched the magisk app (still without root) and selected install, and chose boot image to patch from the download folder on the phone
The magisk app patched the boot image creating the patched_boot.img that i trasnferred on my pc.
I then used the automatic method in this thread replacing the patched boot img in the folder, rebboted the phone and now I have root on magisk 17.1""
can u explain these methods more elaborately please?
i have downloaded noot.img from august update.

Syed Shahriar said:
""Then I launched the magisk app (still without root) and selected install, and chose boot image to patch from the download folder on the phone
The magisk app patched the boot image creating the patched_boot.img that i trasnferred on my pc.
I then used the automatic method in this thread replacing the patched boot img in the folder, rebboted the phone and now I have root on magisk 17.1""
can u explain these methods more elaborately please?
i have downloaded noot.img from august update.
Click to expand...
Click to collapse
I downloaded magisk manager 5.9.1 from the magisk github
I installed magisk manager 5.9.1 on the phone and it says that magisk is missing and is asking to download magisk 17.1
Downloaded stock boot.img from the august update (since the phone has that firmware version installed) from the link in this post
I launched magisk manager 5.9.1 and once again it says that no magisk is installed
I tap install and choose the "patch boot image file" method and then selected the stock boot image that i previously downloaded.
Magisk downloads magisk v17.1 and then patchs the boot.img creating a new patched_boot.img
I copied that patched_boot.img on the PC
From there i basically followed the OP post of this thread.:
Inside the ROOT XIAOMI MI A2 MAGISK 16 folder i renamed the old patched_boot.img to old.patched_boot.img and then put the new patched_boot.img inside the folder
put the phone in fastboot mode and connected it to the pc
I ran the ROOT AUTO.bat file (which basically flashes the patched_image.img in the phone) and then REINICIAR REBOOT.bat

Worked like charm! Thank you!

Thanks, this is working great!
Update to Magisk 17.1 is also working with direct upgrade.

No wifi
Thanks for this work. Unfortunately installing Magisk v18 (performed through TWRP) removes the wifi on my Pie roms (mac address 02:00:00.:00...) The only way to fix is to remove Magisk, using the Magisk manager for instance. Do you have any solution to keep the wifi working ?

AsterixLG33 said:
Thanks for this work. Unfortunately installing Magisk v18 (performed through TWRP) removes the wifi on my Pie roms (mac address 02:00:00.:00...) The only way to fix is to remove Magisk, using the Magisk manager for instance. Do you have any solution to keep the wifi working ?
Click to expand...
Click to collapse
Same problem here but I believe it's only in January Pie update

Is this tutorial is suitable with Mi A2 Android version 10?

Database Users

welcome