I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t
Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...
maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image
maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.
maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...
We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.
5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful
so i'm going thru the same thing as OP.
I need help.
Related
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Trickee360 said:
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Click to expand...
Click to collapse
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
veeman said:
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
Click to expand...
Click to collapse
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Trickee360 said:
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
got it. thanks much
Will only boot to stock recovery
veeman said:
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
You can just root again and you will have root access.
I lost root too, so I just opened wugtoolkit and hit root. no unlock needed so no loss of programs either.
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
Any news about this. I stay in the same problem.
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
jayyo said:
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
Click to expand...
Click to collapse
So, the bootloader 3.41 is the problem?
Southmad said:
So, the bootloader 3.41 is the problem?
Click to expand...
Click to collapse
For some people, yes. No idea why.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Would that image work ok for Galaxy s3? Or there is no difference at all, just matter the 4.1.2 android version?
Cuz i updated my device throught Kies (cuzz from the device itself it didnt allow, stating that the image has been modifyied :angel: ) and after that even with the persistent mode on Super SU the root is gone
After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
yes flash the newest image
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse
Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader
Cool thx for your continued help :good:
The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.
Hey I'm trying to install TWRP on the latest Android N preview and whenever I reboot from boot loader into recovery TWRP loading screen just hangs.
I read online that you need to decrypt but how would I do that?
same problem here :/
Had the same problem, flashed this http://rootjunkysdl.com/getdownload.php?file=Nexus%206P%20Angler/Android%20N%20Preview/Angler%20npc56p%20Remove%20Encryption.zip with fastboot and it worked.
Techno Peter said:
Had the same problem, flashed this http://rootjunkysdl.com/getdownload.php?file=Nexus%206P%20Angler/Android%20N%20Preview/Angler%20npc56p%20Remove%20Encryption.zip with fastboot and it worked.
Click to expand...
Click to collapse
You will first need to disable forced encryption, and then decrypt the 6P running Android N Dev Preview: http://www.droidorigin.com/decrypt-nexus-6p/
DJBhardwaj said:
You will first need to disable forced encryption, and then decrypt the 6P running Android N Dev Preview: http://www.droidorigin.com/decrypt-nexus-6p/
Click to expand...
Click to collapse
I love Droid Origin! Thanks I'll take a look
Techno Peter said:
Had the same problem, flashed this http://rootjunkysdl.com/getdownload...N Preview/Angler npc56p Remove Encryption.zip with fastboot and it worked.
Click to expand...
Click to collapse
What is the proper command to flash this in fastboot?
poor2rican1 said:
What is the proper command to flash this in fastboot?
Click to expand...
Click to collapse
I renamed the image in the folder to boot.img and flashed it with "fastboot flash boot boot.img"
ZacksBuilds said:
Hey I'm trying to install TWRP on the latest Android N preview and whenever I reboot from boot loader into recovery TWRP loading screen just hangs.
I read online that you need to decrypt but how would I do that?
Click to expand...
Click to collapse
Dont know if you fixed the issue but i posted on another thread my experience and found that reverting back to twrp 3.0 was my fix. Flashed in fastboot. To decrypt I flashed the midified boot.img and than twrp and than formatted data to decrypt. Hope it helps.
Hi there XDA, I've recently been having issues with custom roms and random reboots, so I decided to go back to stock. Going back to stock I used fastboot to flash the system and boot images. After some setup I wanted to get root. Instead of there being twrp I ended up with the stock recovery somehow. TWRP 3.1.1 seemed to stick, then I decided to upgrade to the most recent version. And it no longer sticks(TWRP recovery).
I just don't know what to do or what the cause for this to happen may be. My only thought is that I'll have to fastboot flash recovery every time I want to modify something.
Any way you guys would be willing to shed some light on what's going on for me???
Sent from my SM-N7507 using Tapatalk
probably since you are not rooted
@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.
wizardwiz said:
probably since you are not rooted
Click to expand...
Click to collapse
Nah, I'm rooted through magisk
Exodusche said:
@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.
Click to expand...
Click to collapse
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.
double post
dirtyreturn said:
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.
Click to expand...
Click to collapse
So your flashing twrp after first boot, rooting and still won't stick?
Exodusche said:
So your flashing twrp after first boot, rooting and still won't stick?
Click to expand...
Click to collapse
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
Who knows maybe google changed something. Do it my way and you will be fine.
dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
When you flash system and boot images, root is removed. On Oreo, TWRP does not persist without root being maintained. I believe on Nougat or Marshmallow, this was not the case. When you booted into the stock rom, this restored the stock recovery.
Flash TWRP then boot directly into TWRP and flash Magisk. When installing new security patches, boot directly into TWRP and reinstall root.
Sent from my Nexus 5X using Tapatalk
any help ?
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
As far as i remember there were 2 files. dm-verity and forced encryption. I never needed them but if you stay on stock you will have to flash those so that twrp doesn't get replaced by stock recovery everytime you reboot. Check the how to root forum you should find more information there about this.
Or you can just root it and twrp won't erase with stock recover.
naikxda18 said:
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Click to expand...
Click to collapse
Do this:
[email protected] said:
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
Click to expand...
Click to collapse
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
Thanks but i flashed RR pie soon after flashing twrp now its working fine
[email protected] said:
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Click to expand...
Click to collapse
I didn't either, as you wrote if you boot into TWRP before going to system it should stick or also if you flash magisk before booting the OS.
But there are some devices/ROMs that need the no verity flag to be disabled so flashing this file might help if TWRP won't stick (even when DM verity looks for a tampered system partition in the first case). There are also some terminal commands to do that but I forgot them at the moment.
I mainly used the zip to keep my /data partition decrypted after reformating it. When flashing Nougat magisk did the job for me but when I upgraded to Oreo /data was reencrypted again after flashing magisk and booting into system.
The above zip prevents /data from being encrypted again and may make sure that TWRP sticks.
ahhh, ok I see. Thanks for the explanation.