Database Users

root and superSU

I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)

BallaratBloke81 said:
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
Click to expand...
Click to collapse
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005

thahim said:
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
I have given it privileges. But when I open supersu says there is something wrong with su binary.

BallaratBloke81 said:
I have given it privileges. But when I open supersu says there is something wrong with su binary.
Click to expand...
Click to collapse
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....

ultramag69 said:
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
Click to expand...
Click to collapse
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)

BallaratBloke81 said:
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
Click to expand...
Click to collapse
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...

ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
Yes hello, can someone please upload the note 3 4.3 touchwiz apk, i accidentally deleted mine, so please.

ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
I have already reflashed stock back to my phone, re rooted and the problem still exsists
Currently I'm on stock again (downloaded from sammobile)
Every time I open superSU, it tells me there is a problem with the SU BINARY (when I was rooted. I'm not trying to use super SU unrooted lol)

Just rooted again and its still the same...

Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.

antique_sonic said:
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
Click to expand...
Click to collapse
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?

BallaratBloke81 said:
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
Click to expand...
Click to collapse
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked

Rosli59564 said:
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Click to expand...
Click to collapse
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?

BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?

gee2012 said:
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
Click to expand...
Click to collapse
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU

BallaratBloke81 said:
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
Click to expand...
Click to collapse
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.

gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
I can't even get into the app to unroot

BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot

gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
ES explorer can't get root access either.
Should I flash superSU.zip straight over the top using recovery? Or is that not a good idea?

Rosli59564 said:
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
Click to expand...
Click to collapse
I have unrooted (flashing stock rom using recovery) and rerooted (using CF auto root... Or whatever it's called) many times.

Magisk v11.6 compatible with Droid Turbo Stock ROM

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?

[Question] Can i get twrp and root on official nougat

just got nougat in the UK, and i was wondering if i can get twrp and root on it. The answer is probably yes but i just want to make sure, thanks

yes, i did it today

fliperpl said:
yes, i did it today
Click to expand...
Click to collapse
Thanks, good to know. Might wait on it, as if i do this and theres a new update im screwed

What about Systemless Root?

CLETjB said:
What about Systemless Root?
Click to expand...
Click to collapse
magisk works without problems

Instead of flashing TWRP as the permanent recovery, just boot to it by putting your phone into Bootloader mode and use the command Fastboot boot twrp.img (replace twrp.img with the filename of your twrp). Then you can install either SuperSU or Magisk as you desire. If using SuperSU, I would recommend using the SuperSUConfig to ensure that it is installed in Systemless > SBIN so that you can then install SUHide in order that you can get the likes of Snapchat working. Magisk of course has this all ready built in so you don't have to mess about flashing extras.
All being well, your device *should* then be able to accept any further OTA's, although I wouldn't hold my breath for any further ones being released.
You might also want to look at Flashfire by the same chap who gave us SuperSU.

lmulli said:
Instead of flashing TWRP as the permanent recovery, just boot to it by putting your phone into Bootloader mode and use the command Fastboot boot twrp.img (replace twrp.img with the filename of your twrp). Then you can install either SuperSU or Magisk as you desire. If using SuperSU, I would recommend using the SuperSUConfig to ensure that it is installed in Systemless > SBIN so that you can then install SUHide in order that you can get the likes of Snapchat working. Magisk of course has this all ready built in so you don't have to mess about flashing extras.
All being well, your device *should* then be able to accept any further OTA's, although I wouldn't hold my breath for any further ones being released.
You might also want to look at Flashfire by the same chap who gave us SuperSU.
Click to expand...
Click to collapse
Thanks a lot! The only problem was that suhide doesn't seem to want to flash. However my root works and so does my snapchat
Edit: Logging out of snapchat wont let me log back in? So is there any way to hide the root?
Edit 2: Nvm. You have to flash SuperSu-SR4 instead of the normal 2.82 one. I was now able to flash suhide and get everything working

[Q] Successful rooted, but /system is read only?

Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?

Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.

zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.

Cool:good:

Xposed isn't working with magisk? I was planning to install it

amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk

Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )

how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks

maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.

soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?

We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.

soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.

We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop

soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.

We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.

soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...

We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?

We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.

soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?

We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2

Help with installing Magisk on Verizon Samsung Galaxy Note 3 SM-N900V

I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?

jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.

cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.

please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager

@cssr any other input or suggestions?

jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.

cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(

@cssr should i try another version of magisk?

jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?

cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?

What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.

I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.