Hey guys,
Recently moving back to Android with a Samsung Galaxy S7 (SM-G930F) and I have some problems to get everything working. I didn't find (or didn't managed to find) the informations I was looking for on the forum or anywhere else on internet.
Here is what I did since now:
1. Rooted my phone with CF-Auto-Root.
2. Phone rooted correctly, SuperSU installed => no problem
3. Installed TWRP Manager.
4. Launched installation of TWRP from the TWRP Manager and selected the latest version of herolte (3.0.2-2).
5. Installation failed, relaunched it, didn't get any notice of success or failed this time so I presumed it was good.
6. Restarted the phone in normal mode => No problem.
7. Restarted the phone in recovery mode => Access to TWRP asking me if I want to stay in read only or allow read/write.
> Can I boot up at this stage in read/write without causing any issues since I saw in the TWRP root installation process (http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770)
"By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications."
> Since I am already rooted, it shouldn't cause any issues right?
8. I tried to do a backup of my phone but the data folder is showing no data and when performing a backup I am getting a "failed to mount /data error"
> Don't really know how to fix this error.
> I can backup without any issue Boot and System.
Thank you per advance for your answers
1. You need to flash dm-verity and force encryption disabler before you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.
Thank You.
I just did the steps described but it seems that I lost my root after having wipe the data partition.
Now when I am rebooting the phone I am getting "kernel is not seandroid enforcing" in red on top of the screen but the phone still boot up fully.
Tried to reboot in recovery but it seems that TWRP is not present anymore.
I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?
Julek_Fr said:
I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?
Click to expand...
Click to collapse
Hi
did you do this?
Point 11
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........
MAX 404 said:
Hi
did you do this?
Point 11
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........
Click to expand...
Click to collapse
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?
Julek_Fr said:
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?
Click to expand...
Click to collapse
Hi
Flash a stock firmware is an option but not necessary at this point
Go back to TWRP page
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
and re do all this steps one by one ( 1 to 13 ), make sure OEM unlock is enables , back up important thing before you do anything just in case
FULL STEPS FOR OBTAINING ROOT
You can follow this video by Max Lee if you'd like: How to Root Galaxy S7 & S7 Edge! [Exynos ONLY]
Otherwise, follow these instructions:
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for herolte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
try this first....
GerasVille said:
1. You need to flash dm-verity and force encryption disablerbefore you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.
Click to expand...
Click to collapse
How to flash this file? Please treat me like an idiot. What exactly do I have to do?
I am trying to flash the ROM of a different model of my phone, and thus need TWRP, but this needs to be unlocked first somehow.
Related
Hi,
okay, so i had a rooted samsung j500f phone running android lollipop 5.1.1 stock rom (downloaded from sammobile). I was using Apps2Sd for linking my apps to the external SD Card. Few days ago, my phone turned off on the battery getting empty and when i turned it on, all linked apps were missing. I was getting an error that "Disable mount namespace seperation in Chainfire SU". I did that but nothing happened and the App2Sd was unable to remount 2nd partition.
Frustrated, i contacted their developer who suggested to reinstall SuperSU. So, i opened the SuperSU app (chainfire) and went to settings and then chose the option "Reinstall from google play store". It uninstalled SuperSU which i later downloaded from Google Play Store. After it had installed, it asked to install binaries and gave me two options:
1) Normal in-app method
2) TWRP/CWM recovery method
I chose the second one (because i had TWRP installed).
Then my phone rebooted into recovery and ran a few scripts. However it later stated that there is no root on your device (which i believe may have been removed when SuperSU was uninstalled). TWRP gave me options to reinstall SuperSU but it did nothing. I downloaded the latest SuperSU zip file from chainfire site and tried to flash it. But the script would show failure. Now, my phone wouldn't boot into the system. Only into recovery mode.
Being really pissed, i decided to do a factory reset. So i did a factory reset from within the TWRP (normal wipe). Still, my phone wouldn't boot but would go to recovery. So i got angry, went into the Advanced wipe option in which i selected dalvik cache, internal storage, SYSTEM and wiped them all.
Now on trying to reboot, TWRP would say "There is no OS installed. Are you sure you want to continue?"
I knew i had messed up my phone and so i decided to flash it with stock rom again using ODIN. But, whenever i try to go into download mode it gets stuck on the Samsung Galaxy J5 Logo screen with "ODIN Mode" written on the top left along with a couple of other details such as Knox void 0x1(4), Rom statusfficial, etc.
Clearly, i am unable to flash using ODIN as my phone isn't being able to go to Download Mode. ODIN doesn't detect my device.
So i thought of flashing the stock rom using TWRP, which failed.
I also have a TWRP Backup but TWRP won't let me select it. I have the backup folder on my SD card.
Now my phone has just TWRP, Can't get into download mode using the key combinations or through TWRP bootloader option which on selection gives me the "No OS" error. I can't boot my device up as it goes into recovery.
Kindly help as soon as possible.
Thank you.
If you wipe the SYSTEM Partition, then of course that no OS is installed. Like a Hard Brick. Good Job...
Unlocked bootloader and tried to with SuperSU but no boot. Having a hard time to go back to stock but need to find stock recovery for newest FW C567B190. I could not boot into TWRP only flash it so I couldn't make a backup. I just was able to get into the wifi restore screen and it downloads the 2.4gb image and installs but then said I have serious errors and recommended a factory restore, did it but same error. I did make a backup of all the other partitions so I hope to be able to get something going. New here and all this was certainly easier on my 6P and OP3. Thanks for the help.
rzracer2 said:
Unlocked bootloader and tried to with SuperSU but no boot. Having a hard time to go back to stock but need to find stock recovery for newest FW C567B190. I could not boot into TWRP only flash it so I couldn't make a backup. I just was able to get into the wifi restore screen and it downloads the 2.4gb image and installs but then said I have serious errors and recommended a factory restore, did it but same error. I did make a backup of all the other partitions so I hope to be able to get something going. New here and all this was certainly easier on my 6P and OP3. Thanks for the help.
Click to expand...
Click to collapse
Which SuperSU did you try? The only official working one is SuperSU 2.82 SR1, the others fail to install.
And unless you decrypted (Wipe - 'Format Data' button in TWRP) SuperSU will remove the encryption flag in fstab in ramdisk... That means you'll boot but stay encrypted, which leads to a bootloop.
You could try flashing this stock boot image for C567B190 in TWRP (Install - Install Image - select 'boot' partition): https://mega.nz/#!cw01zCCS!AX3wKw0V7pbIYC79Ny6OJ5CTuyxq-xA1ibltLMIRRZQ
Then flash this SuperSU (It's to stay encrypted): https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
If that fails, here's stock recovery for C567B190: https://mega.nz/#!hgsEhBiC!Jf2Utp768UIS0N1-3jhPeoN0qaW_TlFsFf5uN9vKLEs
Recovery needs to be flashed with fastboot in download mode.
Thanks for the information Stockholm! After the second wifi recovery download it booted fine but did relock the bootloader. I did use 2.82 Sr1 but didn't format data which as you stated caused a bootloop. Might give it another try but I might just return it. Not happy with the stock firmware so I need to spend some time and see if there is a ROM available proper smartlock, raise to wake would be nice as it even works on my S8 with Glipse Notifications but not on the Mate. Thanks again!
ante0 said:
Which SuperSU did you try? The only official working one is SuperSU 2.82 SR1, the others fail to install.
And unless you decrypted (Wipe - 'Format Data' button in TWRP) SuperSU will remove the encryption flag in fstab in ramdisk... That means you'll boot but stay encrypted, which leads to a bootloop.
You could try flashing this stock boot image for C567B190 in TWRP (Install - Install Image - select 'boot' partition): https://mega.nz/#!cw01zCCS!AX3wKw0V7pbIYC79Ny6OJ5CTuyxq-xA1ibltLMIRRZQ
Then flash this SuperSU (It's to stay encrypted): https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
If that fails, here's stock recovery for C567B190: https://mega.nz/#!hgsEhBiC!Jf2Utp768UIS0N1-3jhPeoN0qaW_TlFsFf5uN9vKLEs
Recovery needs to be flashed with fastboot in download mode.
Click to expand...
Click to collapse
As you can see from the title, I am looking for a way to stop my phone from re encrypting itself every time I update his firmware.
It is rooted with magisk and has twrp installed.
If there is no way to prevent it from re encrypting everything, is there a way to backup all my data in a manner that would allow me to reinject it retaining all the data? (like the authentication tokens and such)
I really need help in this domain since I seem to be unable to find a workaround myself and also the 8.0 update seems to be just around the corner and I want to be able to update and keep everything.
Smart Switch is not an alternative since it does back up all the apps but it does not back up the data.
~Thanks
bump
anyone?
heeeeeeeeelp
Have you found a way?... I'm in your situation and it's been frustrating me for a decade...
After updating my ROM, I don't have access to /data in TWRP, because the Update encrypts it.
I haven't set a password, so I tried the TWRP Terminal and do "twrp decrypt default_password". I read that "default_password" is the standard encryption password, but it doesn't work...
How to update ROM without /data getting encrypted
Dude, I found out how to disable the Forced Encryption!
Or in other words, how to update ROM without /data getting encrypted!
The key is: Before the first android boot, flash TWRP, boot into TWRP, flash Magisk.
Why: Because the first android boot encrypts /data. And Magisk disables this Encryption-process.
So, step by step:
1. Make a complete backup, in case you fail the steps (I use TWRP for backups)
2. Flash your updated ROM with ODIN.
3. Let it reboot to the blue screen stuff. (That's not the android boot, yet! It's just the Samsung Bootloader finalizing the update)
4. Your phone will reboot again now, DON'T LET IT BOOT TO ANDROID! Boot into Download Mode instead!
5. In ODIN, uncheck "Auto Reboot" and flash TWRP.
6. Now reboot from Download Mode into TWRP.
7. Flash Magisk.
8. Done! You can reboot now.
/data is now accessable in TWRP and in Android, in Settings > Biometrics and Security, you will now see the option to "Encrypt device" "Device not encrypted".
Notice:
Everytime you flash an updated ROM, you need to flash Magisk immediately afterwards. After the blue screen process, but before the first android boot!
Do not forget this, when flashing an updated ROM in the future!
Too bad i'm 2 years late for you, but I hope other people with the same problem find this.
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
sapalot said:
Hey guys, so i had weird problem (status bar not visible after unlocking device) when updating my phone to 9.5.8. so i decided to flash the rom again to see if the issue goes away. I am rooted and unlocked and everything was working fine (apart from the status bar). I tried this method:
1. Downloaded the 9.5.8 update from Oxygen Updater (DONT REBOOT)
2. Went to Settings\System\System Update and click on the wheel on upper right corner.
3. Select Local Upgrade, then install the update (DONT REBOOT)
*DO NOT REBOOT after applying the update.
4. Launch Magisk, and click the first "install"
5. Choose the "Install to inactive slot (OTA)" option
6. Reboot once completed
On step 6 it failed, i rebooted directly into the Oneplus recovery and not TWRP. So i tried fastboot boot twrp.img and flash the installer. After that i rebooted the device and now it goes directly into twrp but without decryption, it wont ask for my PIN and i get the screen "Unmodified System Partition. Keep System Read only? Installing zips or performing adb operations may still modify the system partition." On the bottom i can "swipe to allow modifications", which i swipe to allow but i can't access any files on my phone, and that is my dead end. Help would be much appreciated.
I also tried flashing Magisk and also Magisk Uninstaller (uninmod wasn't found).
Also tried command "twrp decrypt password" in the Terminal and got "Failed to decrypt data"
Click to expand...
Click to collapse
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
reaper000 said:
So to be clear: right now, you have access to twrp but not the data partition (twrp does not prompt you to decrypt), and when you reboot to system from, you are bounced back to twrp. Right?
Click to expand...
Click to collapse
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
sapalot said:
Yes, but i got frustrated and as i had done a Titanium Backup i just wiped everything on stock recovery and flashed the latest rom with twrp. Is there a clear instruction on how to update the rom when rooted? I just don't want it to happen again.
Click to expand...
Click to collapse
Don't mess with stock recovery if you already have TWRP and Magisk aboard.
Here's how to update to 9.5.9 (or whatever) when it arrives:
- download your 3 zips: the latest full ota ROM, the latest Magisk, and the latest TWRP installer.
- boot to TWRP recovery
flash the ROM and TWRP installer
- reboot to TWRP recovery
flash Magisk
wipe dalvik
- reboot to system
There's a possibility after these steps and you're happily on the ROM, you might find that you're not rooted (it's more likely on a custom ROM than OOS). In which case you just reboot to recovery and flash Magisk, and then reboot to system. Done.
Discussion:
If you want a clean flash, you'd simply do a TWRP factory reset (standard wipe) instead of wiping dalvik.
Consider flashing both slots (A and B) whenever you update OOS, for two reasons. First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base. The second reason is more compelling: the way the data partition changes encryption every update has obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck
tl;dr
TWRP doesn't encrypt/mount storage,
Magisk kills WiFi.
Before I bricked the phone with a Magisk module, everything was working.
Had to revive my phone with MSM, stuck in qualcomm crashdump.
Now stock firmware is working, but I cannot get phone rooted with working WiFi / working TWRP.
==================================================
This is how I did it before (clean install, unlocked OEM)
1. boot into fastboot/bootloader
2. fastboot > fastboot flash boot twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
3. boot into recovery mode
4. install OnePlus7ProOxygen_21.E.21_OTA_021_all_1910071445_89e89c225a754eb6.zip
5. install twrp-installer-3.3.1-4-guacamole.zip
6. reboot into recovery
7. Install Magisk-v20.0.zip
8. reboot system
DONE and it worked.
NOW:
1-6 stay the same.
But when I get back into recovery, TWRP doesn't read/mount the storage.
adb push magisk to sdcard/ and try to install leads to following:
Updating partition details...
...done
Unable to mount storage
Failed to mount "/data" (Invalid argument)
Full SELinux is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
- blablabla
- installing
- Done
Updating partition details...
...done
Unable to mount storage
Click to expand...
Click to collapse
...guess what, Magisk is not installed/working
- Repair/change file system doesn't work.
(phone will boot into system instead of recovery, back to recovery still Internal Storage at 0 MB)
- formatting data + Wiping Dalvic / ART Cache, System, Cache doesn't work
(will all lead to stuck in Fastboot -> recovery due to fastboot image)
(installing boot.img (on A & B) and TWRP.zip doesn't help)
- install OOS and then just flash TWRP without flashing stock firmware doesn't change
Alternative
1-6 stay the same.
7. boot into fastboot
8. boot TWRP *-70 again
9. encrypting now works, mounted
10. isntall MAGISK (20.0 or 20.1)
11. reboot system
At this point it seems like everything is working, but with MAGISK now installed, WIFI won't work. Can't activate WiFi it at all.
So, i have no idea what I changed.
Rooting worked before the brick. Now it stopped working.
My friend has that problem after rooting his phone with magisk..
Just flaah the rom and wifi will be back..
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 Pro in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
https://forum.xda-developers.com/on...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Click to expand...
Click to collapse
Thank you, Sir
I should have mentioned that I already flashed a dozen times to stock firmware. Used the package from your link as well when I was stuck in fastboot.
My mistake, I should have been more accurate with my problem.
Getting it back to stock firmware isn't the problem.
Getting it back as a rooted device with working WiFi and working TWRP is the problem.
Stock OOS - without TWRP, without Magisk » ROM working
Stock OOS + TWRP (3.3.1-4) » TWRP not working; ROM working (but this combo worked before)
Stocks OOS + TWRP (3.3.1-70) » TWRP working, ROM working[/b] (but TWRP *-70 should be replaced by *-4 afaik[/U]; correct me if I am wrong)
Stock OOS + Magisk + TWRP *-70/TWRP*-4 » Magisk working, ROM no WiFi. (fixable through reflashing stock firmware and deleting everything)
So maybe any ideas why Magisk/TWRP stopped working now? And how I can get my OP7P rooted and the stable TWRP working?
Solved
Reinstalling boot.img + TWRP 3.3.1-70 installer.zip + Magisk v20.1.zip did it this time
saexcore said:
Solved
Reinstalling boot.img + TWRP 3.3.1-70 installer.zip + Magisk v20.1.zip did it this time
Click to expand...
Click to collapse
Hey, can you go into more details? I'm having the same trouble of not being able to install magisk (stock rom with twrp installed).
Where can I get this boot.img? And what's the exact process to installing it? Thanks.
For me, I never booted into bootloader. I ran fastboot boot /path/to/TWRP.img, while still booted up and that took me to recovery and I used TWRP installer and flashed magisk from there.
I tried almost all the other methods, and kept soft bricking. I didn't patch anything, booting from fastboot soft bricked me.
I just started experiencing connection issues after installing a Magisk modules, but I read a custom kernel solves that.
meleeb4kr said:
Hey, can you go into more details? I'm having the same trouble of not being able to install magisk (stock rom with twrp installed).
Where can I get this boot.img? And what's the exact process to installing it? Thanks.
Click to expand...
Click to collapse
Sure.
The boot image I got from:
https://androidfilehost.com/?w=files&flid=294300
(download the fastboot firmware for your device, for me it was "10.0.1-GM21BA".
open the archive, open the next folder, extract the "boot.img" file to your PC)
Magisk I got from:
https://github.com/topjohnwu/Magisk/releases
(I used 20.1, 19.4/20.0 seems to work more stable for more people)
TWRP I got from:
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
(Download image for Q and twrp-installer.zip)
===================================
1. Boot into fastboot
(developer options > advanced restart > restart bootloader or power device off > HOLD volume down and press power till in fastboot)
2. In fastboot: "fastboot boot twrp70.img"
(#protip: drag & drop file into CMD)
2.1. wait till phone encrypted everything and TWRP started
3. Copy twrp70.zip, boot.img & Magisk-v20.1.zip to your phone
(I put it in the TWRP folder)
no reboots in-between!
3. In twrp homescreen: install > install image > boot.img > choose "boot" > install
4. In twrp homescreen: install > install zip > twrp70.zip > install
4.1 wipe dalvik
5. In twrp homescreen: install > install zip > magisk-v20.1.zip > install
5.1 wipe dalvik
6. In twrp homescreen: reboot > system
Done.
Hope it works for you too.