Database Users

My approach to rooting 7.1.1

Hey all,
After my rooting experience with marshmallow, I used that with 7.1.1 and have had no issues. MODS: This was my approach to rooting 7.1.1. I apologize in advance for creating this thread if it's not necessary yet since XDA has given me so much help, I'm returning the favor.
NOTE: for those that want to roast me on this thread and/or flame me, don't do it. We are all noobs at one point or another. I have provided no links but have supplied the filename to the best in my capacity.
XDA gang,
After numerous attempts to root nougat, I tried this approach. This was the same approach I took w/ marshmallow.
I used Odin3_v3.12.3
selected 7.1.1 – look for filename j700tuvu3bqi5 NOTE: uncheck auto reboot. I do\did because in my experience, I encountered a boot loop.
after odin processes the flash, I disconnected the usb cable and did a battery pull.
Boot up your phone and let your phone build the recovery. After your phone reboots after the recovery, do a battery pull when the samsung splash screen starts to display itself.
Enter stock recovery and perform a cache, dalvik, and factory reset. Reboot from recovery.
Do a battery pull when the samsung splash screen starts to display itself. Boot back into download mode while holding volume down, home button, and power button. Let go of the buttons when the download mode screen comes up.
Use odin again and click on the AP button – select twrp_3.0.3-1_sm-j700t_23217. I found and downloaded this from XDA. Click start on odin and let odin do it thing. Disconnect the usb cable and do a battery pull.
Enter twrp recovery while holding volume up, home button and power button. Release buttons when twrp comes up.
Here, you will need to flash the latest supersu. I used v2.82-SR5. Also download no-verity-no-encrypt-ashyx.zip (big ups to ashyx for creating this)
Install these 2 files and reboot. NOTE: your phone will reboot twice – no cause for alarm.
After your phone boots up into nougat, go through the setup and reboot your phone.
After doing all of this, I've had zero issues. It may seem arduous but I found it necessary for my goal.

Did you have any issues with unlock screen lag on pin;/pattern?
There are reports and my own experience with this on a 7.0.0 version of otherwise identical process as yours to root. conclusion seems to be the no-verity-no-encrypt patch causes this, and that this patch (or something functionally identical) is integrated into supersu 2.82 versions.
edit - what model phone did you do this one? 7.1.1 not available for the j730g yet, unfortunately.

im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.

leo31 said:
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
Click to expand...
Click to collapse
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well

DullPeon said:
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
Click to expand...
Click to collapse
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?

leo31 said:
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
Click to expand...
Click to collapse
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.

fullofhell said:
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
Click to expand...
Click to collapse
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?

leo31 said:
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
Click to expand...
Click to collapse
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too

fullofhell said:
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
Click to expand...
Click to collapse
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.

leo31 said:
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
Click to expand...
Click to collapse
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.

fullofhell said:
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
Click to expand...
Click to collapse
this is the 2nd time i root my device.
the first time i rooted my a3, i didn't face any lag and never laggy while unlocking screen.
but the problem is i forgot how i rooted it. which files did i flashed. which tutorial did i follow.
but no problem so far , because the fingerprint unlock does not give any lag.

Issue with Magisk and OTA version 7.1.2

I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?

I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.

Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.

It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.

ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.

_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?

ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).

Best way to cleanup my nexus 6p

hey all!
I'm a newb....
I have a rooted 6p with the factory image installed, twrp recovery.
I don't recall doing a backup before rooting.....yeah I know not smart....didn't know what the heck I was doing in this process....never rooted a phone.
I installed Magisk......then in my infinite wisdom installed supersu
the phone for the most part works fine, but I am having a problem running frida, it complains about magisk hide. I have removed all the magisk modules...
I am hoping I can some how clean up this phone and completely remove magisk.....and get frida running.
am I toast without a backup?
what is the best way to completely remove and uninstall magisk.
tried to run magisk install again and also magisk uninstall gives me error 1, which I see there are videos for dealing with on youtube...though haven't gone done that rabbit hole
I am quite comfortable using adb
I see bits of magisk all through the file system, just not sure if I should be deleting as I might be getting myself into more trouble.
TIA

Well if you don't mind starting fresh (backing up all your data) as this would erase everything and set your phone back to "factory stock" on the latest official version from google and its as easy as clicking one batch file to get things sorted. You may have messed up some stuff permanently on your system partition by installing/uninstalling two incompatible root solutions etc.
Link: https://developers.google.com/android/images#angler
Direct link to latest file: https://dl.google.com/dl/android/aosp/angler-opm7.181205.001-factory-b75ce068.zip
Then you just plug your phone in and run the 'flash-all.bat' file.

11.0.2.2 and keeping root?

Now that 11.0.2.2 is available OTA, can anybody give me a quick guide on how to upgrade from my existing 11.0.1.1 without losing root?

Hi. you have to download the full rom package. disable all modules in magisk. update in local update system. especially do not restart. and in magisk manager click on install and install on inactive slot after OTA update. magisk will recreate a boot image on the inactive slot. which will become active on restart. once the restart is complete the root is kept. all that remains is to reactivate the magisk modules.
Envoyé de mon IN2023 en utilisant Tapatalk

Merci beaucoup - cela a parfaitement fonctionné!

Philip said:
Merci beaucoup - cela a parfaitement fonctionné!
Click to expand...
Click to collapse
I have a guide in the guides section for this very reason with img's

Hello.... Normally you have to install the twrp a/b script after install the local update and then the magisk in inactive slot.....
That was ok in a lot of older updates and works.
This time if can't install the twrp a/b script. Everytime I get a fault message that twrp is not present....?!
Very strange.....

jensemann1974 said:
Hello.... Normally you have to install the twrp a/b script after install the local update and then the magisk in inactive slot.....
That was ok in a lot of older updates and works.
This time if can't install the twrp a/b script. Everytime I get a fault message that twrp is not present....?!
Very strange.....
Click to expand...
Click to collapse
That script is for older devices that has recovery inside boot.
OnePlus devices launches with Android 10 has a separate recovery slot. This means in order to install TWRP again your need to flash it with fastboot again.

Twrp not working on Oos11
Envoyé de mon IN2023 en utilisant Tapatalk

So it isn't necessary to install, only magisk in inactive slot....?!

Have said this before, shouldn't be any confusion, like I said I have a guide for it.
Extract from the guide for retaining root.
Update from 11 stable to 11+ stable whilst retaining root
For these guides the version used, was canary, simply change the channel to canary then select install / update:
Magisk Manager - Magisk (Canary) version: 1469b82a (21101)
Magisk - Magisk (Canary) version: 1469b82a (21101)
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I copied out the whole firmware to my computer and extracted payload then extracted the contents of payload using payload dumper, the full firmware for 11.0.1.1 EU IN2023BA ,the boot img and patched boot img are at the foot of this guide.
3. Open up settings / system / system updates, click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage /sdcard
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select Install to Inactive slot (After OTA) then select "LET'S GO" once complete click reboot
7. Once your phones booted up your system / files should all remain as they were and you should have root access.
Thread:. https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033

You have an easier method if the OTA update is there in the system. Follow below guide. Specifically, step 2,3 and 5. That's all you need. You don't need the whole update. Tested this twice. 11 to 11.0.1.1 and so on.
https://www.the***********.com/install-ota-update-rooted-android-device-guide/

dladz said:
Have said this before, shouldn't be any confusion, like I said I have a guide for it.
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select Install to Inactive slot (After OTA) then select "LET'S GO" once complete click reboot
7. Once your phones booted up your system / files should all remain as they were and you should have root access.
Thread:. https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033
Click to expand...
Click to collapse
Steps 5 and 6 did not preserve root comping from OOS10. Magisk Manager is still there though. Looks like I'll be looking for a way to apply root again.
Edit: used the boot image from this link to get root back. I wasn't able to patch the file myself using Magisk Manager and fastboot boot it and have root enabled. https://forum.xda-developers.com/showpost.php?p=83775505&postcount=471
I was able to use the oneplus-8-pro_15.O.30_boot_patched IMG from the link to adb boot oneplus-8-pro_15.O.30_boot_patched.img from fastboot screen and then direct install Magisk from the manager. I retained root after a reboot.

ProfEngr said:
Steps 5 and 6 did not preserve root comping from OOS10. Magisk Manager is still there though. Looks like I'll be looking for a way to apply root again.
Edit: used the boot image from this link to get root back. I wasn't able to patch the file myself using Magisk Manager and fastboot boot it and have root enabled. https://forum.xda-developers.com/showpost.php?p=83775505&postcount=471
I was able to use the oneplus-8-pro_15.O.30_boot_patched IMG from the link to adb boot oneplus-8-pro_15.O.30_boot_patched.img from fastboot screen and then direct install Magisk from the manager. I retained root after a reboot.
Click to expand...
Click to collapse
That must be you're magisk manager and or you left magisk modules enabled..
Otherwise your phone wouldn't be booted at all..
To confirm, the steps have been used 100's of times without problems, the few that have issues have specific problems, namely what I mentioned above but more often than not they have an issue they aren't aware of and don't declare to be so I can't help them.
I would hazard a guess that that is the problem

dladz said:
That must be you're magisk manager and or you left magisk modules enabled..
I would hazard a guess that that is the problem
Click to expand...
Click to collapse
It was a couple of modules I forgot about. Got it sorted now. Thanks.

Not sure if the question was answered really. I have the ota update alert but can't install the ota without flashing the original boot.img (not a problem just have to get in front of a computer)..I tried this method but the full image on oxygen updater and OnePlus support site is 11.0.1.1 and not the new 11.0.2.2.
What's the easiest way of doing an ota without having to flash back stock boot.img, taking the ota, and reinstalling magisk/patching image if there's one?

Wait for the 11.0.2.2 Full update to keep root; that's what a few of us are waiting on as well

galaxys said:
Wait for the 11.0.2.2 Full update to keep root; that's what a few of us are waiting on as well
Click to expand...
Click to collapse
Thanks. Anybody had problems flashing back stock boot partition and taking the ota/rooting again manually via patched magisk image?

I've read some threads about problems and success's. I would check them out if your interested. I just take the ota, have magisk install to the inactive slot, and then reboot.

galaxys said:
I've read some threads about problems and success's. I would check them out if your interested. I just take the ota, have magisk install to the inactive slot, and then reboot.
Click to expand...
Click to collapse
You were able to take the ota without reflashing stock boot.img? It's currently failing for me and I'm fairly sure it's because I have a patched boot partition (this happened already when I upgraded via ota from oxygen 10 that's why I'm fairly sure). Let me know.

Sounds like because of your patched boot.
No, I have not seen the full ota 11.0.2.2 to download, I was giving an example....

bootloop after magisk update

after uptade magisk my phone stuck in fastboot . i cant go to recovery . what i can do ?
phone is over or i can fix it ?

Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk

zgfg said:
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
Click to expand...
Click to collapse
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Add me on discord for live support :
SneezeOnYou2#8507

AC420 said:
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Click to expand...
Click to collapse
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well

zgfg said:
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
Click to expand...
Click to collapse
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.

AC420 said:
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
Click to expand...
Click to collapse
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time

zgfg said:
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
Click to expand...
Click to collapse
Its not that i didnt look up on youtube about flashing in revovery mode. When i did search for more information i get those videos of people in india talking their own language. Np if you dont have time and on other topic someone said that they wint use discord because it wont be public for someone else with the same problem but i was gonna make photos with the steps i did for fixing it. The thing is i cant find the uninstall. File or the older version of twrp. Skip i wont takr your time good luck with your private life

And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you

AC420 said:
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
Click to expand...
Click to collapse
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc

zgfg said:
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
Click to expand...
Click to collapse
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.

AC420 said:
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
Click to expand...
Click to collapse
I've had this ****, i just used abd to flash a new twrp img and dirty flashed the ROM after it flashed magisk back on again, only problem I got was safety new which idk how I solved but I think was using lsposed