Related
Hi Everyone, l have a question about this Magisk Mod and its directed to s7 & s7 edge users. If anyone is using this Mod, may you please tell us how you got it to work, coz l have tried and failed many times. Your help would be kindly appreciated..
King Addies
Root and install xposed.
I have used a stock rom, as it says on the magisk thread and followed all the instuctions and still failed.. lm not really botherd about using the mod anymore, but l made this thread so all the other people who are in my situation can get help or a tutorial on how to install it on s7 & s7 edge. Coz l could not really get much help from the official thread.
King Addies
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Mr. Orange 645 said:
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Click to expand...
Click to collapse
Thanx for your input on this issue mate, hope the info you have provided helps all those that want to use this Mod on their s7 or s7 edge phones..
King Addies
One more step, sorry. You have to also install Phh's SU app from the Google Play store.
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Galactus said:
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
Click to expand...
Click to collapse
kevinwu128 said:
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Click to expand...
Click to collapse
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Galactus said:
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Click to expand...
Click to collapse
Maybe I did have it working then, the only thing I tested it with Pokemon go and it didn't work.. so I just assumed it wasn't working, so I reverted all changes. I spent way too much time than I had hoped
Cheers Buddy
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Devilover said:
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Click to expand...
Click to collapse
Magisk is pointless right now. Simply having an unlocked bootloader causes SafetyNet to fail. The latest version of magisk also removed the checkbox to turn root on and off. To use Snapchat YOU MUST login before any modifications. Make a titanium backup of Snapchat logged in, then you can restore it whenever you want.
silverrum said:
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Click to expand...
Click to collapse
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
PoTBrain• said:
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
Click to expand...
Click to collapse
What part of S7/S7Edge do you fail to understand?
Or, boot into TWRP, format data to unencrypt then flash latest magisk and reboot. Once booted, open magisk manager hit menu button and open settings, check magisk hide. Exit settings, open menu and open magisk hide, there you can check any app you want to hide from root. done.
I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?
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.
I received my OP6T this past Tuesday and I absolutely love the phone. It was super easy to get TWRP installed after unlocking (easy since mine was purchased outright from OP).
My only problem is that I play Pokémon Go with my son. And it detects Magisk no matter how I tried to hide it from the app.
Is it not possible to flash TWRP without Magisk? I'd like to eventually try different kernels, but I just don't understand how everything appears to require Magisk.
This is my first OP device as well as the first device I've had with the A/B slots.
Any ideas would be greatly appreciated so I can unlock the phone to its full potential and still play a game I enjoy playing with my son.
Hi,
TWRP and magisk are not directly related, other than the need for twrp to flash magisk
In order to get rid of magisk you can just download the magisk Uninstaller (you can get that from the official magisk thread) - just be aware that of course any Magisk mods will be lost...
One caveat, though: this only works if you have an unmodified system partition (so you never acknowledged changes to system partition in twrp) - if you did you need root to be able to boot the system!
Cheers, Axel
Gesendet von meinem LYA-L29 mit Tapatalk
So I'm assuming I accidentally modified my system. Using Magisk Uninstaller from the app made it so the phone only booted into recovery until I flashed Magisk. Zip again.
On another attempt after resetting up the phone it seems that the Uninstall from the app succeeded but my phone would not boot for a good 15 minutes. Just a black screen nothing else. But after it turned on Magisk was gone and I didn't lose anything.
The twrp file to remove Magisk failed every time saying to use the one from the Magisk dashboard.
Is there an easy-ish way to get a stock system partition? Or will I have to use the tool to return the phone to stock and start over?
Magisk Props Module <- Have you tried this Magisk module? I don't play Pokemon go but I was able download it and open it. (I don't know at what point it detects root).
It actually was even easier ? in the settings menu and click hide magisk and it renames itself to something random and works fine!
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