Database Users

[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

[ZCX TWRP] Install TWRP and Flash SuperSu without breaking incremental OTA's!

{
"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"
}
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles. Use the SuperSU option under Advanced option for flashing SuperSU.
​
How to update Incremental OTA via ZCX TWRP?
1. Reboot to ZCX TWRP.
2. Go to Settings and select "support MIUI OTA".
3. Flash the full rom of the current version [Mandatory]. It will automatically back up system and boot for the OTA survival.
4. Now reboot to system and check for any update, when update releases, download it and press update.
5. Automatically device will reboot to TWRP and OTA flashing will start, this time the backed up system and boot will be flashed and thus patching will happen and your device will be updated.
Downlaod the instruction PDF from here.
Note: Step 1 to 3 to be done only while installing TWRP afterwards no need to follow those steps, when an update releases you need to follow from Step 4.
ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Changelog
20160917
Updated Translation
20160916
Built SuperSu Pro into official Supersu (before installing twrp built supersu pro, be sure to uninstall and then install)
Updated the partition table
20160914
Updated the partition table
Used android 7.0 TWRP source compiler
20160908
Updated the partition table
Repaired the previous version incorrectly installed
20160907
Updated TWRP source
Updated the partition table
Updated Translation
Other details Updated
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you already rooted your device or you used anyother TWRP you won't be able to use this recovery for flashing the OTA's. You should install this recovery in a factory ROM. Steps to follow,
1. Flash the latest beta through fastboot method using Mi flash tool.
2. Unlock bootloader if it is relocked (usually this happens when you flash rom from Lollipop to Marshamallow)
3. Now put your device in fastboot mode and connect to the PC.
4. Run the flash.bat and go to settings and tick the "Support MIUI OTA" option. Take a back up of your EFS,MODEM and Persist if you don't have one.
5. Use the SuperSU option under advanced option (refer the images above).
6. Now use your device as normal, when an OTA update releases, just download it using the OTA and flash using updater/TWRP.
Q. I am getting error in fastboot mod or while running Flash.bat?
Ans: Ensure the device is in fastboot mode (Press Volume up + Power button) and make sure that you have installed the drivers (or Install MI FLash tool).
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.Couldn't Restore back-up through this recovery?
Ans: Please untick firmware while selecting the restore option.
Note: Always it is advised to backup your EFS,MODEM and Persist partitions before flashing any zip files.
Q.Is this recovery can be used in any ROM?
Ans: Yes! You can use this recovery in any ROM.
Credits: TWRP and BY~XM
Thank you,
Raaj

Raaj52 said:
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles.
​ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Credits: TWRP and BY~XM
Thank you,
Raaj
Click to expand...
Click to collapse
Can i flash in miui 7 lollipop base

Raaj52 said:
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles.
​ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Credits: TWRP and BY~XM
Thank you,
Raaj
Click to expand...
Click to collapse
Is this for MIUI OTA's only or it could be used with other custom ROMs too...?

Awesome! Flashing now

Raaj52 said:
Hello guys,
I am here with a glad news that now you can enjoy TWRP and SuperSu without sacrificing your incremental OTA's. Yes! Now you don't need to download the full ROM to flash in TWRP in our beloved Redmi Note 3 SnapDragon . This is because MIUI China Forum member BY~XM compiled a new TWRP with inbuilt feature to flash incremental OTA's. So all credits goes to BY~XM for his awesome work and please thank him on his original post. So let's get started.
Pre-requisite
Redmi Note SD version
Unlocked Bootloader
Common sense
Steps
Downlaod the Flash folder from here.
Run the Flash.bat
Now phone will boot to "ZCX TWRP"
Follow the images to set up the TWRP initially
Now you can flash SuperSu and incremental OTA's without any hustles.
​ZCX TWRP Features
OTA incremental update support
Support for ad-hosts
SuperSu v2.76
android 6.0 Data partition decryption support [No more Internal Storage/Encryption error]
Credits: TWRP and BY~XM
Thank you,
Raaj
Click to expand...
Click to collapse
Thanks for sharing
This works only for root or can be used with supersu and xposed framework too and one more thing how to flash Ota by twrp or by updater

Again posting plz confirm
Will i flash it ti lollipop bootloader??? plz tell

Thank ..awesone
Sent from my Redmi Note 3 using Tapatalk

Thank you Raaj52 for awesome work...

Ol cnfm working woith lollipop base but getting error while flashing error 7
Ota i am on miui 7 got update miui 8 555mb
Done all this as on op

Shulod we download OTA.zip from internet or we will get incremental update via updater app?

sasukay said:
Is this for MIUI OTA's only or it could be used with other custom ROMs too...?
Click to expand...
Click to collapse
I think it's only for MIUI
---------- Post added at 11:54 AM ---------- Previous post was at 11:37 AM ----------
p.chandra284 said:
Thanks for sharing
This works only for root or can be used with supersu and xposed framework too and one more thing how to flash Ota by twrp or by updater
Click to expand...
Click to collapse
If you have installed TWRP only and not root, then also MIUI incremental OTA fails. I think Supersu install systemless on MIUI 8 (Android M based) so it can be survived after OTA update. Xposed framework may be need to install again. May be not. Needs to check once next incremental update comes.

Can we flash any custom rom by this TWTP?

Can I flash this recovery from current cofface twrp ??

Go to advance setting you will see option for supersu you can also root from there..

iamnived said:
Can I flash this recovery from current cofface twrp ??
Click to expand...
Click to collapse
Yes. You can.
Yogendra Kher said:
Can we flash any custom rom by this TWTP?
Click to expand...
Click to collapse
Extract the zip and flash recovery.img using your current TWRP

I flash mm, 9.14... Working now. I not tested yet for Ota update.

So ota flash not work with miui 7 lollipop

Should i flash cracked boot.img for this twrp?

AldyRambe said:
Should i flash cracked boot.img for this twrp?
Click to expand...
Click to collapse
Check disable dm-verify in settings ,it will patch boot image itself,no need for cracked boot image.

I'm on MIUI Global Stable 8.0.1 & Android Version is 5.1.1 (Unrooted). I want to root my rn3, should I directly flash this recovery by this method??

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.

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?

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.