Related
Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
after root do you have flashed superSU?
RotesMeerJogger said:
after root do you have flashed superSU?
Click to expand...
Click to collapse
Well I flashed superSU to root the phone!
But when I do it, it won't boot.
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Daman5202 said:
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Click to expand...
Click to collapse
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
gigaboss said:
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
Click to expand...
Click to collapse
As you said "it stucks on boot", many times the phone gets stuck on boot when the image is corrupted , its called soft brick. Try downloading the zip file of os, flash it through recovery. The img is probably facing some errors while booting with root access. Are you nougat user? 7.1? And are you using default recovery?
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
donny110 said:
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
Click to expand...
Click to collapse
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
gigaboss said:
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
Click to expand...
Click to collapse
Have you cleared caches before the flash? And are you using the Full OOS 3.5.4? And I assume the most recent Supersu? I did exactly that 2 days ago. Using the full OOS zip that is in one of the threads here on XDA (can't link on phone right now).
Btw. It can bootloop a few times and take awhile once you flash both.. If that doesn't work I guess it's beyond my knowledge. You might want to try if the same thing happens with 3.5.3
gigaboss said:
Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
Click to expand...
Click to collapse
I don't have my 3T yet to verify, but did you flash the zip which disables encryption and dm-verity?
EDIT: From the TWRP thread, step 10: http://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
__McB__ said:
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
Click to expand...
Click to collapse
I got to the bottom of my problem (but did not solve it somehow) by formatting and trying every possibility. I lost all my data :crying:
So here is what happens:
-I start with a clean ROM, root it, install kernel, everything works fine EXCEPT for safetynet that won't pass even with root switch
-I try to install suhide 0.55, the phone won't start anymore (stays on boot animation, tried to wait all night)
AND HERE IS THE WEIRD THING.
-If I dirty flash the rom to start over, it boots, if then I flash SuperSU, it won't boot!! As if suhide was still in the data partition and preventing the phone from booting!!
So it means that if I try to install suhide once, I am not able to boot with root anymore... I need to format my data partition and start all over again.
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
__McB__ said:
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
Click to expand...
Click to collapse
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I had a similar issue with my op3t after root it, I wipe data but it won't start, I just flash the zip 5.1 no verity opt encrypt and should be work fine without flashing supersu:good:
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
No, never got it working. Upgraded to 4.0.2 and never looked back.
Maybe you already tried this version.. Otherwise...
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone, and then it was stuck at the pulsating SAMSUNG logo.
So, next step would be obvious: get into TWRP and install Magisk 14.0.
And so I did, and so it failed. This time I got a bootloop. The "Galaxy S7 powered by Android" thing appears for a few seconds, and then vibrates and starts over. And over, and over, and over.
So then, I "installed" the Magisk Uninstaller. Thinking to get rid of all traces of Magisk that introduced this problem in the first place.
So I did, and now I'm back at the first problem: stuck at booting.
Then installing Magisk 14 AND wiping cache&dalvik: boot loop
Then I installed the uninstaller again, then Magisk 15, and wipe the cache&dalvik. And it's back at being stuck while booting again.
Brilliant. What do I do to fix this?
Are you using a custom ROM, or a port ROM, or a custom kernel?
It's all stock, except for it being rooted.
I'm having the same issue. Canadian S7 W8, Stock ROM with root, Magisk 14, upgraded to 15 using direct install through magisk manager.
Yes, exactly that. No offense, but that's helping neither yourself nor me nor anyone else. Have you been able to figure anything out?
Maybe how to produce some kind of log output?...
Same thing happened to me just now. Never would have thought that upgrading through the Magisk app would cause this. I've tried all of the above and have also tried installing v 12.0 but still no dice.
I even tried a factory reset and still no dice. This is seriously infuriating.
Guess I will have to reflash everything and start fresh. If anyone else has any other ideas I'm all ears.
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
thany2 said:
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone
...
What do I do to fix this?
Click to expand...
Click to collapse
Mate 8 running 7.0 stock except rooted, running Magisk 14, did the same thing and I'm in the same boat. Have also tried removing magisk, reinstalling 14 no dice. Have not factory reset yet (trying everything else before that step) but it looks like it won't help.
thany2 said:
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
Click to expand...
Click to collapse
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Ok, I'm still not in that loop... yet.
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
I'm still not in that loop... yet.
ct1aic said:
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
Click to expand...
Click to collapse
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
If you can' t solve download Magisk Uninstaller https://forum.xda-developers.com/attachment.php?attachmentid=4370032&d=1514240372
and Magisk 14.0 https://forum.xda-developers.com/attachment.php?attachmentid=4264532&d=1504713887
Then reboot in Twrp (hope you have it) and flash
1 uninstaller
2 14.0
I had the magisk 14.5 and I installed the 15 via twrp on top, and it updated normal. Is there a problem updating this way?
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Same here, updated from v14 to v15 and got a nice bootloop.
Huawei Mate 8 with Nougat (stock) and TWRP.
EDIT:
Solved!
Flashed my stock boot.img backup through TWRP, then booted my phone and downloaded v14, flashed v14 through TWRP, booted my phone again and downloaded v15 with Magisk Manager app and checked "Preserve AVB 2.0/dm-verity" and then tapped "Install" using "Direct Install (recommended)"
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Because a custom kernel disables dm-verity. There's an issue, mainly on Samsung devices, with the dm-verity detection in Magisk v15.0. It's under investigation...
Meanwhile, flash a dm-verity disabler together with Magisk v15.0 and you should be good to go.
I'm fairly certain you need a custom kernel. I'm also on the S7 and without one I've always boot looped, I think it has to do with dm-verity.
EDIT: I didn't notice there was a second page so I guess I didn't really say anything new, oh well, sorry!
ct1aic said:
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
Click to expand...
Click to collapse
Awesome! Glad it worked. Happy new year.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Hey man. I'm just telling you what worked for me. If you don't want to try it then don't.
fattyspecial said:
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Click to expand...
Click to collapse
Hello,
Here is the problem I personnaly had (solved now !) :
Initially, my wife had a G930F (samsung galaxy S7) and a Custom 7.0 rom (i think it was the "AlexNDR.G930FXXU2DRAG" rom...but I'm not sure at all because it was installed several months ago or even years) with TWRP as recovery and Magisk as root.
I saw that Magisk not working (since when ? I don't know because it was not my phone). So, I tried to update it via the Magisk application (the initial goal was to use then Titanium Backup).
Logically, the phone then rebooted to install the Magisk update... except that a Boot Loop appeared.
I then tried many things :
1° Downgrade or Upgrade the TWRP recovery to 3.0.0.0; to 3.2.2.0 and to 3.5.2.9.0 (thes recovery .img files are here: https://eu.dl.twrp.me/herolte/)
=> It didn't work, and the bootloop continued (but, at the end, i keep the TWRP v.3.5.2.9.0)
2° I tried to uninstall and reinstall Magisk
(cf. the "Custom Recovery" tuto here : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
=> Failure. Still the BootLoop... (either with the .zip v19.1 or the .zip v23)
nb: I even tried to donwload other magisk files but still the same bootloop (cf.https://forum.xda-developers.com/t/collection-of-magisk-modules-v2.3575758/page-13#post-72542167)
4° I tried to change the kernel by using TGPKernel (https://forum.xda-developers.com/t/...2-30-tgpkernel-v6-15-5-3-18-140-esd2.3462897/)
=> Failure, the bootloop remained...
5° Finally, I found a solution :
a° I downloaded the rom "G930FXXU2DRAG_DevBase_v4.6.zip" (via the following tutorial here : https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/)
, more exactly at the following location : https://androidfilehost.com/?fid=818070582850489124
b° Then, as indicated in the tuto (https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/), I renamed the .zip downloaded on my PC to "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" (ps: so, i add "..._rescue.zip)
c° After that, I copied the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" on my micro SD.
d° In the recovery I finally installed the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" and the phone restarted after a long time (or maybe 5 minutes, I didn't watch).
=> End of the bootloop and all data was preserved!!!
Magisk worked fine on the Android P PP2 beta. Just upgraded to the new PP3 and Magisk 16.4 doesn't seem to work. It flashes fine in TWRP, but Magisk Manager says it's not installed. Just want to check if others are experiencing the same before I assume it's just me and start troubleshooting.
I'm running a Pixel XL.
Same in my pixel 2 XL
I tried patching the boot.img and I got an error
I flashed 16.4 on my Pixel with PP3 and it installed fine. Root seems to work as expected, but modules dont install.
Having the s ame issue. Can't unpack and patch boot.img.
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
SirLoinOfBeef said:
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
Click to expand...
Click to collapse
I flashed 16.4 and for some reason worked... but only couple of minutes then suddenly root dissapeared :/
For me works with no problems.
I disabled all modules (just to avoid problems), dirty flashed dp3 over dp2, removed lockscreen password (again, just to avoid possible problems with twrp).
Booted twrp img, then in recovery:
- flashed latest twrp.zip
- rebooted recovery
- I flashed Flash Kernel just because I like it
- Straight after magisk 16.4
- rebooted.
Then I re-enabled all modules and set the password back. Super smooth and zero problems, root survives every reboot, no crashes or freezes of any kind. Also if I download modules they all works.
Still can't get it installed. I am trying to patch the boot.img file via Magisk Manager.
I get:
Code:
- Device platform: arm64-v8a
- Extracting files Failed!
! Installation failed
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
djuniah said:
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
Click to expand...
Click to collapse
I assume you installed through TWRP?
joderme said:
I assume you installed through TWRP?
Click to expand...
Click to collapse
Yes, i flashed through TWRP. I basically have done the same thing TENN3R mentioned above minus a kernel install. I've tried it a few times now with no luck. Pixel XL btw.
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
billard412 said:
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
Click to expand...
Click to collapse
Magisk 19 should fix Safetynet issues. If not, use Safetynet patch Magisk module
billard412 said:
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
Click to expand...
Click to collapse
I can confirm that on my Pixel with newest android, and on my wife's moto g6, that magisk is fully working. both have pie now. both pass safetynet just fine.
HueyT said:
Magisk 19 should fix Safetynet issues. If not, use Safetynet patch Magisk module
Click to expand...
Click to collapse
tried everything. Was running magisk 19 when this occurred. Tried multiple versions of magisk and MM. Tried uninstalling and reinstalling. Tried the safetynet fix. Tried reinstalling the OS and other important partitions with fastboot (everything except bootloaders and a data wipe). And not only did I not fix the safetynet issue I'm stuck with no root at all now (magisk is not installed). This is crazy.
billard412 said:
tried everything. Was running magisk 19 when this occurred. Tried multiple versions of magisk and MM. Tried uninstalling and reinstalling. Tried the safetynet fix. Tried reinstalling the OS and other important partitions with fastboot (everything except bootloaders and a data wipe). And not only did I not fix the safetynet issue I'm stuck with no root at all now (magisk is not installed). This is crazy.
Click to expand...
Click to collapse
Have you tried rooting/magisk the old way? By flashing the no verity boot.img? I posted one a page back or so for the newest pie build. Works great from what I can see.
If it were me, and this is assuming you havent already tried this. I would reflash back to stock and make sure to erase userdata in the process. Then flash twrp and the no verity boot.img. Format data and do a factory reset. When that is done go back into twrp and flash magisk. That has worked fine for me on xt1925-6 variant. I actually just the other day followed the old root instructions and they worked fine for pie as well.
I should mention that to flash the image I extract it into the adb/fastboot dir and run the flash_all.bat in elevated CMD window. I do let it do everything including wipe userdata. Not sure if thats important. But it sounded like you were excluding some of the flashing in your process.
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
anykiel91 said:
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
Click to expand...
Click to collapse
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
I couldn't get it to boot up before firstboot. So I went with normal nonroot flash so I could use the phone.
I figured it would not matter if I installed Magisk later.
I might try to reflash everything over again
ast00 said:
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
Click to expand...
Click to collapse
topjohnwu says that you flash custom kernel after flashing Magisk
Immortalis said:
topjohnwu says that you flash custom kernel after flashing Magisk
Click to expand...
Click to collapse
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
ast00 said:
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
Click to expand...
Click to collapse
Yes, I had problems with 19.1 too, that the phone sometimes (if not always) would boot itself into fastboot mode instead of system, so at that time I moved temporarily to canary builds
I used this zip instead and it worked. Not sure what's different but I'm good now
https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932