Database Users

[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.

Perform the update without losing the root

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.

[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?

Updating Or Installing Magisk 17.0 resulted in bootloop

Is There any Other Way To Update Magisk?

{
"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"
}

prawinraj8045 said:
Is There any Other Way To Update Magisk?
Click to expand...
Click to collapse
i am also faced same problem while updating to magisk 17

I haven't updated magisk but what method did you use to update? Via recovery or by patching the boot image?

patching the boot image failed, then tried to update via recovery, then became boot loop. can't even flash magisk v16 after this procedure in twrp. my device became rootless. i need to do full wipe and start from beginning again

Before flashing magisk 17 , I'll suggest removing 16 by flashing magisk uninstaller from twrp, after this , flash magisk 17.

Lucky me
Not happened to me, just flash via twrp and wipe devlik cache
Reboot and pray

100% working solution to upgrade Magisk to 17.00 without BootLoop
Please follow the below Steps to update Magisk without getting into a bootloop.
1. Uninstall the Magisk by using the uninstall .zip
2. Now flash the ver 17.00 and it will work just fine.
This will work 100%

I faced same issue.
Just uninstall with uninstaller and re install it will fix issues

I had just updated by patching the boot image then flashing through fastboot. It worked with no bootloops for me.

Update to v17.1

vitcp said:
patching the boot image failed, then tried to update via recovery, then became boot loop. can't even flash magisk v16 after this procedure in twrp. my device became rootless. i need to do full wipe and start from beginning again
Click to expand...
Click to collapse
You just need to use Magisk Uninstaller in TWRP before updating! Nd then install Magisk 17.1 which is latest as of today

rocky29b4u said:
Please follow the below Steps to update Magisk without getting into a bootloop.
1. Uninstall the Magisk by using the uninstall .zip
2. Now flash the ver 17.00 and it will work just fine.
This will work 100%
Click to expand...
Click to collapse
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.

abubin said:
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.
Click to expand...
Click to collapse
Your system partition cannot be mounted due to encryption. If possible, try uninstalling from Magisk itself

abubin said:
I have downloaded the uninstaller and tried running it but failed. Error 1. Says something about unable to mount partition. I even run the decrypt first but it still fail. Should I run the uninstalled from within Magisk? Appreciate any advice.
Click to expand...
Click to collapse
Which partition does it say about not being able to mount ?

rocky29b4u said:
Which partition does it say about not being able to mount ?
Click to expand...
Click to collapse
The uninstaller.zip that is not working with Error 1 and unable to remove magisk.
I already tried running decrypt first then run the uninstaller but still doesn't work.
Edit: Nevermind, I flashed with latest firmware, decypt, magisk 17.1, camera2api and all working fine. Rebooted to firmware 326 now with magisk 17.1. All seems to be working fine and fingerprint is faster! Will see how it goes because the fingerprint scanner usually goes back to being sloppy after a week of update.

Realme X2 Pro Root | RUI 1.0 | C.38 | Custom Recovery | Magisk Canary | SafetyNet Pass | FP

~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Update your Realme X2 Pro with C.38 with System Update or download the file specific for your device CN/IN/Global and simply opening the ozip file in your File Manager. Latest RUI Updates since c27 and Magisk Canary fixes FP which used to break when rooted. Magisk 20.4 gives issues with RUI and custom roms
Official TWRP for Realme X2 Pro which is also maintained by Mauronofrio is not the same as unofficial TWRP 3.4.0 by Mauronofrio which is given below. Use only as mentioned in this post. Official TWRP has issues when flashing ozip.
​If TWRP 3.4.0 by Mauronofrio or OrangeFox Recovery for realme X2 Pro is already installed. Repeat these steps for every RUI Update. Thanks @minoccio​
Install c38 update ozip with TWRP and dont reboot to avoid bootloop/softbrick
No need to wipe any partition (Dirty Flash)
[Not recommended] Reboot only if its needed to automatically replace the custom recovery with stock by not installing modified vbmeta or not rooting the device by installing magisk.
Install vbmeta.imgwith TWRP by selecting vbmeta partition.
[This step is essential to have TWRP persistent by not getting replaced with stock recovery and also to avoid bootloop]
Install Magisk Canary - Rename apk tp zip and flash (Optional only if root is required)
Reboot to System (May take 5-7 minutes to complete booting)
Follow the below procedure to root RUI or to replace stock recovery
Make sure the bootloader is unlocked. click here for Unlock Procedure
Boot to fastboot(power off device and hold vol- and power)
Install latest TWRP or OrangeFox in fastboot with a Windows PC. Use Minimal ADB Fastboot v1.4.3
TWRP - Download: TWRP 3.4.0-0 Thanks @mauronofrio
Code:
fastboot flash recovery twrp-3.4.0-0-RMX1931-mauronofrio.img
OrangeFox - Download: OrangeFox-R10.1 Thanks @Jerry08
Code:
fastboot flash recovery OrangeFox-R10.1_1-Unofficial-RMX1931.img
OrangeFox Recovery for realme X2 Pro - Download: OrangeFox-R11.0_1-Stable-RMX1931 Thanks @Jerry08
Code:
flash OrangeFox-R11.0_1-Stable-RMX1931.zip in custom recovery
Reboot to Custom Recovery
Install VBMETA with Custom Recovery - To avoid bootloop or softbrick your device and to make custom recovery persistent.
Download: VBMETA
Flash Magisk Canary - Download to your device.
Download: Magisk Canary module[12.1 MB]
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file. Thanks @topjohnwu
[*]
{
"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"
}
Get Magisk Canary Uninstaller to your device as a precaution to uninstall magisk canary by flashing this uninstaller zip file in custom recovery in case of any issues or bootloops related to Magisk.
Download: Magisk Canary Uninstaller [2.54 MB]
Reboot to System (May take 5-7 minutes to complete booting)
New Magisk Canary app will be installed automatically in few seconds
Update Magisk Canary app
Download: Magisk Canary app [9.45 MB]
Uninstall any previous old versions of magisk
Open Magisk Canary app
Click Gear button on the Right Top Corner
Under section Manager click Hide Magisk Manager
Enter any new name of your preference
Modified Magisk manager will be installed
Under Magisk section, enable MagiskHide Toggle
Go Back to Magisk home and click shield icon present at the bottom
Go to MagiskHide - Enable toggle for all banking apps/Google Pay/apps which fail when rooted
Go To SafetyNet - It would Pass basicIntegrity and ctsProfile in basic evaluation mode with Success message.
Note: SafetyNet in canary build passes in stock roms above (C.28) and custom roms still have to use Magisk V20.3
Troubleshoot:
Recover from Black Screen of Death (BSoD) or stuck with realme logo on boot
Can follow the following instruction(s) in any order
Hold Vol+ and Power button till it restarts (more than 10 seconds)
Work in Flashboot to Flash or Wipe anything as per your requirement.
Try flashing Custom Recovery
Flash Magisk Uninstaller if issue related to Magisk
Download: Magisk Canary Uninstaller [2.54 MB]
Check if there are two magisk app installed then Uninstall only the newly magisk app installed which was the result of flashing the magisk module.

Cool! Thanks.

Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.

Rj_Param said:
Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.
Click to expand...
Click to collapse
Install vbmeta only when you replace stock recovery with custom recovery. If custom recovery is previously installed with vbmeta, they don't need to install vbmeta again.

I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?

adsubzero said:
I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?
Click to expand...
Click to collapse
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.

hack-os said:
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.
Click to expand...
Click to collapse
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?

I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure

adsubzero said:
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?
Click to expand...
Click to collapse
Yes when you have custom recovery then you cant install ozip directly from file manager but when you click the ozip in file manager, it takes you to custom recovery if not de-bloated and its completely safe

minoccio said:
I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure
Click to expand...
Click to collapse
Yes you are right, the custom recovery stays only if modified vbmeta is installed if not gets in bootloop.
I suggested this procedure because it is safe for everyone who initially have stock recovery or custom recovery

Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0

nkbhr said:
Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0
Click to expand...
Click to collapse
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.

hack-os said:
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.
Click to expand...
Click to collapse
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.

Magisk hide keep failing
Please help

nkbhr said:
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.
Click to expand...
Click to collapse
Data and system partitions enough imo

Series of the nightfall said:
Magisk hide keep failing
Please help
Click to expand...
Click to collapse
Did you enable magiskhide in settings? Check op for attached images

hack-os said:
Did you enable magiskhide in settings? Check op for attached images
Click to expand...
Click to collapse
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.

hack-os said:
Data and system partitions enough imo
Click to expand...
Click to collapse
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.

nkbhr said:
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.
Click to expand...
Click to collapse
System image should be what you need

Series of the nightfall said:
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.
Click to expand...
Click to collapse
Uninstall magisk and try everything again. If you never missed any steps and magisk hide option to rename should definitely work on devices above Android 9.