Related
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.
After updating to the latest software I found that with the exception of the first time I tried it which weirdly enough worked, I can't for the life of me successfully boot after rooting.
I rooted once and had to uninstall magisk because of a conflicting module but now no matter what I try I always get stuck on essential's splash screen.
Does anyone else have this problem? If I flash the stock boot image I can boot just fine.
have you try flashing update, then boot image then magisk consecutively before any reboot? I'm out of the country at the moment w/o access to my PC, and I can't even risk a soft brick while traveling.
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Ibanez33 said:
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Click to expand...
Click to collapse
I can't believe I hadn't thought of that. The conflicting modules were still there and I just had to remove them. Thanks so much man, I was about to wipe my phone out of frustration!
Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!
bigbraintime said:
Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!
Click to expand...
Click to collapse
Check out this guide. It may be of some use
https://www.didgeridoohan.com/magisk/HomePage
spawnlives said:
Check out this guide. It may be of some use]
Click to expand...
Click to collapse
Thanks. I tried the methods listed in the "Lost root randomly" section and unfortunately they didnt work. Do you have any other ideas? Maybe I could "Select and Patch a File" in Magisk's Install but afaik Magisk doesnt have its img./tar. file.
I should probably just flash a fresh stock and redo the root process, but then my data will be wiped and I dont really want that lol
bigbraintime said:
Thanks. I tried the methods listed in the "Lost root randomly" section and unfortunately they didnt work. Do you have any other ideas? Maybe I could "Select and Patch a File" in Magisk's Install but afaik Magisk doesnt have its img./tar. file.
I should probably just flash a fresh stock and redo the root process, but then my data will be wiped and I dont really want that lol
Click to expand...
Click to collapse
Have you tried the uninstaller through magisk or twrp then try again with magisk.
When trying to re-install magisk do you get any errors.
https://github.com/topjohnwu/Magisk/releases
Also if worried about losing apps/data do a backup before trying anything.
The easiest way is to flash firmware and start from scratch again but backup first.
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?
c_86 said:
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?
Click to expand...
Click to collapse
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...
aktap said:
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...
Click to expand...
Click to collapse
After which point should i do it?
I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app
c_86 said:
I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app
Click to expand...
Click to collapse
Okay i'll try
Thank you for your help
aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.
elmarian756 said:
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.
Click to expand...
Click to collapse
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?
aktap said:
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?
Click to expand...
Click to collapse
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it
dladz said:
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it
Click to expand...
Click to collapse
I rooted my phone again, without LP the system is stable. Thank You for Your help!
Good good.
Tbh there is no reason to use that app. And now it causes a lot of crap anyway, best to avoid it
I am in need of assistance.
I am using a OnePlus 8 Pro (EUR)
After using stock magisk rooted OOS 10 for quite a while I updated to OOS 11 and rooted it again.
All goes well until an hour or 2 have been passed.
After those 2 hours my banking apps won't show anything more than a blank screen. Some apps won't open or start freezing on launch. All with Magisk Hide enabled.
Strangely enough, Magisk manager still says that I'm passing safetynet.
I have tried to root my OP8Pro on OOS 11 several times but I will get these problems eventually. Sometimes combined with a bootloop.
Has anyone else also had this. And if so, is there a way to fix this? I would be glad if I can root my phone again.
Help will be appreciated.
ps: I am aware that this thread has to be moved somewhere else.
I really don't know what's causing the issue you're having but I highly recommend to do a backup and then factory reset, it could fix all the issues
I was having reboot and freeze issues. I had to follow the unbrick method for a full clean slate, have been good since aside from some rogue apps lol
Sounds like you've booted the magisk patched IMG and then not made it permanent by installing directly afterwards.
Apps can begin to fail after turning on systemless in magisk. You are meant to reboot which would inadvertently disable root if you haven't installed directly after booting like I said
If you have 100% installed directly and it survives a reboot then it is more than likely your boot IMG, reobtain another and patch it with the latest magisk beta. Then boot it then install directly.
Reboot to see if it's taken.
Then go systemless and magisk hide.
Then reboot.
dladz said:
Sounds like you've booted the magisk patched IMG and then not made it permanent by installing directly afterwards.
Apps can begin to fail after turning on systemless in magisk. You are meant to reboot which would inadvertently disable root if you haven't installed directly after booting like I said
If you have 100% installed directly and it survives a reboot then it is more than likely your boot IMG, reobtain another and patch it with the latest magisk beta. Then boot it then install directly.
Reboot to see if it's taken.
Then go systemless and magisk hide.
Then reboot.
Click to expand...
Click to collapse
Ok, I will try it out, thanks!
Apexrajang said:
Ok, I will try it out, thanks!
Click to expand...
Click to collapse
Very welcome sir
some of my bank apps only work with private dns, for some reason, otherwise they show random bugs about "slow connection" or whatever