Database Develop

Can't seem to root 6.0.1

I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.

Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message

simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.

Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.

It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs

TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.

That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs

TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.

I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.

Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.

simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.

Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0

simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0

simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?

Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.

simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.

Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.

alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.

I got TWRP and root on magisk here's how.

I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.

hey man, i'm wodering which version of magisk did you choose for oneplus 5?

ihead said:
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
Click to expand...
Click to collapse
I recommend using the latest beta (v13)
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
OcazPrime said:
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
Click to expand...
Click to collapse
Did you decrypt before installing Magisk?

Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%

OcazPrime said:
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
Click to expand...
Click to collapse
I just asked because it seems that Magisk can't work if your device is decrypted

Didn't know that. But, no it's working perfectly fine. I used the test twrp build on the stable twrp 3.1.1 thread. Everything went great, no reason to flash anything else. Stock is king.

i have tried to used magisk v12 and it didn't work perfectly, specificialy 3C System Tuner doesn't get the root permission correctly then i have to use supersu 2.8.2
so if you want to root you OP5 , magisk v13 or supersu is recommended

If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
You won't be able to update OTA because your stock recovery is gone. You'll need to download the full ROM and flash it in TWRP every time an update comes. You can uninstall SuperSU and put Magisk v13. I currently have it, works perfect and safety net passes.

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.

ArkAngel06 said:
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
Click to expand...
Click to collapse
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.

Eric214 said:
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Click to expand...
Click to collapse
Hmm, I can't remember if it auto rebooted or not now, but thanks for the tip.

[Q] Uninstalling magisk leads to bootloop

If i try to uninstall magisk from my Honor 8 i will end up with a bootloop until i reinstall magisk.
I tried to uninstall from the app and with the uninstaller zip same result.
Does someone know how to fix this

After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.

Didgeridoohan said:
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Click to expand...
Click to collapse
OK so did as you said but i still get bootloops . No idea how something like that can happen but something seems not right guess i am stuck with magisk installed until i wipe and reinstall it completly.

resov said:
OK so did as you said but i still get bootloops . No idea how something like that can happen but something seems not right guess i am stuck with magisk installed until i wipe and reinstall it completly.
Click to expand...
Click to collapse
Did you try a complete dirty flash of your ROM/firmware package/factory image?

Didgeridoohan said:
Did you try a complete dirty flash of your ROM/firmware package/factory image?
Click to expand...
Click to collapse
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.

resov said:
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
Click to expand...
Click to collapse
Dirty flashing means you don't wipe your data.
It's possible there's some kind of verified boot thing that you're going to have to restore, or something like that. Ask in your device's forum.

resov said:
If i do that my data will get wiped right? I would like to avoid that. But it looks like isn't only on my end someone else reported the same problem so maybe it's a magisk bug.
Click to expand...
Click to collapse
Not magisk, it seems to be something with your device, some samsungs too.

Seems lke this happens to phone's that has auto-encrypted /data partition. This happens to me on a Samsung S7 (Android 8/oreo) and my "stock os" has auto-encrypt of /data if /system is touched. When uninstalling via Magisk, usually Magisk will restore your original boot.img (it did so during my uninstall, but still i get bootloop). Tried two nandroid's done of just boot-partition, but only one of them worked, and it only worked if I reinstalled Magisk. Without magisk I had bootloop's with all my stock.img availible (ps: i've not yet tried the "dirty flash replacement of the boot.img", I guess using ODIN? But hey, dunno if it is the AP,BL,CP,or CSC part that needs to be dirty-flashed then, so since im tired of setting up the /data patition (going through first phone install, installing apps and settings again, then I'll wait for further/better info.
But hey

Didgeridoohan said:
After uninstalling, also flash the stock boot image from your ROM/firmware package/factory image.
Click to expand...
Click to collapse
I don't know how to thank you, you saved my life!

[Updated/All Versions & Models!] Root OnePlus 7T Pro

How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!

EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.

hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.

Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho

Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.

I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device

Ah! Will do this immediately when I get home.

I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...

Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!

Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks

Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!

droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it

Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!

Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!

HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!

droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk

HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.

Question Pixel 7 Pro boot loop after magisk root.

Hi.
I recently rooted my pixel 7 pro, everything went well until... i restarted my phone 2 days later to a boot loop, flashed init_boot back to stock, uninstalled magisk, now when i try to root again it just boot loops, everything seems good when i flash back to stock.
followed multiple guides how to root, did everything right apparently.
Pixel 7 pro
Build number: TQ1A.230105.002

Moishev1 said:
Hi.
I recently rooted my pixel 7 pro, everything went well until... i restarted my phone 2 days later to a boot loop, flashed init_boot back to stock, uninstalled magisk, now when i try to root again it just boot loops, everything seems good when i flash back to stock.
followed multiple guides how to root, did everything right apparently.
Pixel 7 pro
Build number: TQ1A.230105.002
Click to expand...
Click to collapse
Do you have a Magisk mod that may need disabling?

I uninstalled magisk, so i'm assuming that it uninstalled the mod as well?

Lughnasadh said:
Do you have a Magisk mod that may need disabling?
Click to expand...
Click to collapse
I uninstalled magisk, so i'm assuming that it uninstalled the mod as well?

Moishev1 said:
I uninstalled magisk, so i'm assuming that it uninstalled the mod as well?
Click to expand...
Click to collapse
How did you uninstall Magisk? Did you use the "Complete Uninstall" option in the Magisk app?

Lughnasadh said:
How did you uninstall Magisk? Did you use the "Complete Uninstall" option in the Magisk app?
Click to expand...
Click to collapse
i'm afraid not, i just uninstalled, i did however run the adb command after flashing while booting adb wait-for-device shell magisk --remove-module, that didn't help.

Moishev1 said:
i'm afraid not, i just uninstalled, i did however run the adb command after flashing while booting adb wait-for-device shell magisk --remove-module, that didn't help.
Click to expand...
Click to collapse
Try booting into safe mode and then rebooting (should disable mods). Could also be it's something else besides a mod. Someone recently reported that Greenify was messing with Smart Lock settings and causing a bootloop, so if it isn't a mod it could be something like that (a root app causing problems).

Lughnasadh said:
Try booting into safe mode and then rebooting (should disable mods). Could also be it's something else besides a mod. Someone recently reported that Greenify was messing with Smart Lock settings and causing a bootloop, so if it isn't a mod it could be something like that (a root app causing problems).
Click to expand...
Click to collapse
So i did boot into safe mode, then restarted, then flashed magisk. also uninstalled any root app that i downloaded.
currently that didn't help.

Moishev1 said:
So i did boot into safe mode, then restarted, then flashed magisk. also uninstalled any root app that i downloaded.
currently that didn't help.
Click to expand...
Click to collapse
Reboot into safe mode after flashing Magisk and while you are bootlooping.

Lughnasadh said:
Reboot into safe mode after flashing Magisk and while you are bootlooping.
Click to expand...
Click to collapse
IT WORKED!!!!!! Thanks so much!

Moishev1 said:
IT WORKED!!!!!! Thanks so much!
Click to expand...
Click to collapse
Glad it worked. Disabling modules via safe mode only works while you are actually rooted so that's why it worked this time