Database Users

[updated 8-27-16] [Decrypted] [Modified Boot.img's for N][MM Boot.img_SystemRoot]

I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
MM modified DM removed removed force/encryption and custom sepolicy to allow system root.
DOWNLOADS FOR 7.0 OFFICIAL
NRD90M(Decrypted)(System_root hopefully coming soon)
https://drive.google.com/file/d/0B4yuQy7Zn1WSYm5sTXNhZmsxcVk/view?usp=sharing
DOWNLOADS FOR MM
MTC20F(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSeVc1bjdDOGFETDA/view?usp=drivesdk
MTC19V(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSY3FZaVNXMjhEN2c/view?usp=drivesdk
MTC19T(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSWXMyRHF1bGQ2YUU/view?usp=sharing
MCH19q
https://drive.google.com/file/d/0B4yuQy7Zn1WSclZ6dGhCNXNUUEk/view?usp=drivesdk
DOWNLOADS FOR ANDROID N Preview builds
NPD90G
https://www.androidfilehost.com/?fid=24572369242689017
NPD56N
https://drive.google.com/file/d/0B4yuQy7Zn1WSM3FORTl4ejlUV2M/view?usp=sharing
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSTklfZW1McXZxQUk/view?usp=drivesdk
NPC91k
https://drive.google.com/file/d/0B4yuQy7Zn1WSSG5WTGNBMHVvZXc/view?usp=sharing
DIRECTIONS
fastboot flash boot boot.img

Good to see your work here as well. :good:
Would love to see more.
F.A.Q - Frequent Answers and Questions

Bringing the love to 5x!!!
To users:
Don't question just follow his directions and profit
Sent from my Nexus 5x using XDA-Developers mobile app

Tigerstown said:
I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
So this is a decrypted and DM checks have been removed. flastboot this boot.img when flashing N preview factory imgs. Also i will be posting a MM modified boot.img the has DM removed removed force/encryption and custom sepolicy to allow system root. but for now here is the N boot.img
DIRECTIONS
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys

m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
To my knowledge you need to decrypt phone then flash N and before boot flash decrypt boot img then boot twrp then flash super su 2.71. To be decrypted rooted N.
Now to begin that process you need a decrypted phone which is why i am waiting for m decrypt boot begore i proceed.
Tigerstown can correct me if i am wrong.
Sent from my Nexus 5X using XDA-Developers mobile app

m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache

DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution

m.daziale said:
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution
Click to expand...
Click to collapse
No bootloop guarantee, until you do something different than this. :victory:

DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This is exactly what I was just going to reply. If your on N flash boot.IMG and decrypt using fastboot like said above.

Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?

zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
Yes, perfectly alright. Avoid the recovery image, in case you have TWRP installed.

zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
that is How I do it on my 6P. After flashing I boot to twrp and do factory reset myself. You don't need to flash the N recovery.
Sent from my Huawei Nexus 6P using XDA Labs

Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.

exploreresp said:
Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.
Click to expand...
Click to collapse
Hey no problem just glad to be helping out.
Sent from my Huawei Nexus 6P using XDA Labs

Op has been updated added MM MCH19q support. Still have to work on sepolicy for system root on 5x like I have it for 6P. Once I get it right I'll update with that.
Sent from my Huawei Nexus 6P using XDA Labs

aaaaand thanks again for the MM boot.img ! Glad to have both actually

Thanks for this, waiting for rootable version.

Hey thanks you for this
But if i flash only the modified boot on android n and i don't make a userdata wipe ?
What happen ?

khanjui said:
Thanks for this, waiting for rootable version.
Click to expand...
Click to collapse
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs

Tigerstown said:
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I can test it.

stuck on m afetr rooting

hey guys
have just received my pure x , have unlocked bootloader, twrp, and unfortunately flashed su that have made my phone get stuck.
my question is if i may wipe data and factory reset via twrp, for im not familiar flashing roms on this device yet. if not, would you kindly post a good rooted dev rom for me?
thanks in advance for all whom reply

the-light said:
hey guys
have just received my pure x , have unlocked bootloader, twrp, and unfortunately flashed su that have made my phone get stuck.
my question is if i may wipe data and factory reset via twrp, for im not familiar flashing roms on this device yet. if not, would you kindly post a good rooted dev rom for me?
thanks in advance for all whom reply
Click to expand...
Click to collapse
What version of SuperSU did you flash? Certain versions don't work so well. Try version 2.62-3 or 2.71.
Sent from my XT1575 using XDA Labs

dustin_b said:
What version of SuperSU did you flash? Certain versions don't work so well. Try version 2.62-3 or 2.71.
Sent from my XT1575 using XDA Labs
Click to expand...
Click to collapse
hey =dustin_b, i have flashed supersu 2.49 but now i cant flash for phone stuck on m. i also looked at twrp and saw no factory reset. any ideas? thank you...

the-light said:
hey =dustin_b, i have flashed supersu 2.49 but now i cant flash for phone stuck on m. i also looked at twrp and saw no factory reset. any ideas? thank you...
Click to expand...
Click to collapse
A factory reset isn't going to help in this case. The reason you are stuck on the M logo is because marshmallow requires a modified boot.img. SuperSU 2.49 is an older version and does not do that. SuperSU 2.62-3 works for pretty much everyone on here. I would use it. But anyways, your best option would be to download that version on a PC or laptop and transfer it to internal storage or external sdcard and flash it in TWRP. The second option would be to reflash the system.img for your specific device. Then root with 2.62-3.
Sent from my XT1575 using XDA Labs

dustin_b said:
A factory reset isn't going to help in this case. The reason you are stuck on the M logo is because marshmallow requires a modified boot.img. SuperSU 2.49 is an older version and does not do that. SuperSU 2.62-3 works for pretty much everyone on here. I would use it. But anyways, your best option would be to download that version on a PC or laptop and transfer it to internal storage or external sdcard and flash it in TWRP. The second option would be to reflash the system.img for your specific device. Then root with 2.62-3.
Sent from my XT1575 using XDA Labs
Click to expand...
Click to collapse
thx man

Can't get Resurrection Remix to install

So i wanted to try RR, but can't get it too install for some reason. I've been able to flash LineageOS, but every time I try RR I get an error message in TWRP.
Wondering what steps anyone with success has used. I followed the same steps as if I were installing LineageOS.
Thanks~

When I installed RR on my LG G2 a long time ago, it let me reduce the haptic vibration. Wonder if it would do this on the PH-1 too.

mpetruzz said:
So i wanted to try RR, but can't get it too install for some reason. I've been able to flash LineageOS, but every time I try RR I get an error message in TWRP.
Wondering what steps anyone with success has used. I followed the same steps as if I were installing LineageOS.
Thanks~
Click to expand...
Click to collapse
Wipe phone completely then flash twrp-7 and flash RR.

shooterlgk said:
Wipe phone completely then flash twrp-7 and flash RR.
Click to expand...
Click to collapse
Ok. I was using twrp 6 if that makes a difference. Thanks

mpetruzz said:
Ok. I was using twrp 6 if that makes a difference. Thanks
Click to expand...
Click to collapse
I unlocked the bootloader today, I was trying to install RR with twrp 6 and the other one that is on the root guide section. They won't install it. I tried with the 7 one and bingo. The only issue I'm facing I can't get twrp to stick, is either twrp or wifi gets broken.
Sent from my PH-1 using Tapatalk

Yeah I just tried with twrp 7 and it worked!!!

If you're gonna flash Magisk, use Invisiblek's hacked version. Thanks to The_Automator for pointing this out to me. https://forum.xda-developers.com/showthread.php?p=74701054
Sent from my PH-1 using Tapatalk

mpetruzz said:
Yeah I just tried with twrp 7 and it worked!!!
Click to expand...
Click to collapse
Were you able to keep twrp and wifi?
Sent from my PH-1 using Tapatalk

Nochis said:
Were you able to keep twrp and wifi?
Click to expand...
Click to collapse
I have WiFi but I haven't gotten as far as rooting so don't know about twrp

mpetruzz said:
I have WiFi but I haven't gotten as far as rooting so don't know about twrp
Click to expand...
Click to collapse
Ok thanks. Let me know if you try it.
Sent from my PH-1 using Tapatalk

Here is what you do.
From your ADB folder
Reboot to bootloader (adb reboot bootloader)
fastboot -w (completely wipes the device)
fastboot flash boot twrp.img (flashes TWRP, I renamed mata7 to twrp to make it easier)
Reboot into TWRP
adb shell twrp sideload (this starts sideload in TWRP)
adb sideload lineage-14.1-20171130_060947-UNOFFICIAL-mata.zip (this flashes the latest RR)
adb sideload magisk_14.3_invisiblekhax.zip (this is magisk that is tweaked properly)
Then reboot. Do no reflash TWRP as you have no reason to, and it breaks stuff.
This will work everytime, I've jumped from RR to Lineage to XenonHD without any issues at all.

Nochis said:
Ok thanks. Let me know if you try it.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Just flashed Magisk 14.3 and can confirm Wifi is broken, won't turn on.
Is there a trick to get it working or is it not on RR?

mpetruzz said:
Just flashed Magisk 14.3 and can confirm Wifi is broken, won't turn on.
Is there a trick to get it working or is it not on RR?
Click to expand...
Click to collapse
You have to flash the ROM again and magisk the one invisiblek provided. WiFi gets broken because you flashed twrp.
Sent from my Pixel 2 XL using Tapatalk

Nochis said:
You have to flash the ROM again and magisk the one invisiblek provided. WiFi gets broken because you flashed twrp.
Click to expand...
Click to collapse
I reflashed everything from scratch and it's all good now!!

Does work great but one problem is that i can't use TWRP for backups.

Turbojugend said:
Here is what you do.
From your ADB folder
Reboot to bootloader (adb reboot bootloader)
fastboot -w (completely wipes the device)
fastboot flash boot twrp.img (flashes TWRP, I renamed mata7 to twrp to make it easier)
Reboot into TWRP
adb shell twrp sideload (this starts sideload in TWRP)
adb sideload lineage-14.1-20171130_060947-UNOFFICIAL-mata.zip (this flashes the latest RR)
adb sideload magisk_14.3_invisiblekhax.zip (this is magisk that is tweaked properly)
Then reboot. Do no reflash TWRP as you have no reason to, and it breaks stuff.
This will work everytime, I've jumped from RR to Lineage to XenonHD without any issues at all.
Click to expand...
Click to collapse
There's gotta be a way to do it w/o having to wipe internal storage! I have 100gb of stuff I don't want to erase and then move back all the time.

Kochoa940 said:
There's gotta be a way to do it w/o having to wipe internal storage! I have 100gb of stuff I don't want to erase and then move back all the time.
Click to expand...
Click to collapse
Just wipe with TWRP. U don't need to do the adb -w.
Sent from my PH-1 using Tapatalk

Airwolf79 said:
Just wipe with TWRP. U don't need to do the adb -w.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Do you mean I don't have to do the fastboot -w?

Kochoa940 said:
Do you mean I don't have to do the fastboot -w?
Click to expand...
Click to collapse
Yes. The steps that Turbojugend posted are just one way of doing it. You can also just download the ROM to ur phone, then wipe, and flash it in TWRP. The only adb step u need is to flash TWRP, if u haven't done that already. If u want root, just make sure u flash Invisiblek's hacked Magisk version, which saves u from having to flash Magisk to the other partition, and keeps the boot.img intact.
Sent from my PH-1 using Tapatalk

Airwolf79 said:
Yes. The steps that Turbojugend posted are just one way of doing it. You can also just download the ROM to ur phone, then wipe, and flash it in TWRP. The only adb step u need is to flash TWRP, if u haven't done that already. If u want root, just make sure u flash Invisiblek's hacked Magisk version, which saves u from having to flash Magisk to the other partition, and keeps the boot.img intact.
Click to expand...
Click to collapse
So all this can be done from slot A?

supersu - maybe these make bootloop?

Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks

I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk

funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk

so...i'm in 8.1 and these is the conclusion in that state after few tests.

I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk

What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk

stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.

the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..

[SOLVED] Unable to get Magisk Manager to work - Request help

So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
UPDATE:
Got it to work. You need to have the app installed on internal storage. Mine was installed on sdcard. doh!

buggerman said:
So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
Click to expand...
Click to collapse
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I

Haizum74 said:
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I
Click to expand...
Click to collapse
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.

buggerman said:
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.
Click to expand...
Click to collapse
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?

Haizum74 said:
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?
Click to expand...
Click to collapse
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled Magisk Manager because some people said uninstall and reinstall and try again.
I haven't installed/ uninstalled Magisk yet. Only the manager.

buggerman said:
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled it because some people said uninstall and reinstall and try again.
Click to expand...
Click to collapse
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?

Haizum74 said:
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?
Click to expand...
Click to collapse
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.

buggerman said:
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.
Click to expand...
Click to collapse
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.

Haizum74 said:
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.
Click to expand...
Click to collapse
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk

Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs

Ahh I thought so, well that yt video is ideal then.

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
buggerman said:
Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
As above

Haizum74 said:
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
As above
Click to expand...
Click to collapse
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
No, not if you still want to keep OTA updates without having to download them manually. From what I am aware, unlocking the bootloader and rooting as per the videos instructions is the only way to keep auto OTA.

buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Click to expand...
Click to collapse
TWRP by mohancm

TWRP not booting for me.

UPDATE:
Got it to work. Moved the app to internal storage. My device installed it on sdcard by default. That was causing the freeze.