Can't successfully hide root with magisk 18.1 for square reader app - OnePlus 6 Questions & Answers

I've been rooting my Android phones since about 2012, but today I got a point of sale card reader for my business and I'm not having any luck hiding root from the app (square reader app). The app wont work at all so I tried a number of options in magisk manager (magisk hide the app, hide magisk manager, enable core mode only) rebooting between each try and clearing the square reader app data and setting it up fresh each time, but still no luck
I tried to uninstall magisk but the app still didn't work. So I eventually flashed back to stock and got rid of magisk all together, now the app works but I don't have root...
I tried installing magisk again after I got the app to work and hiding root from the app before I opened it up again, but it still somehow knew the device was rooted
Can anyone suggest anything I haven't tried? Or is there an alternative to rooting the OnePlus 6 (other than magisk) and hiding root? I had a bit of a look around but didn't find anything.
Thanks

I had to go back to 18.0, heard 18.2 works as well.

qbanlinxx said:
I had to go back to 18.0, heard 18.2 works as well.
Click to expand...
Click to collapse
Thanks for your reply. I tried with 18.0, damn, it still doesn't work, it still picks up that the phone is rooted
I tried the 18.2 canary build as well (18.2-e72c6685) no luck either
This app must be looking somewhere out of the ordinary for evidence of root in the phone

I have a bank application and facing the same problem. Hope someone can help us to make applications run by hiding the root
I think recent applications are looking for if knox security is tripped !! so in this case Magisk will not help

Ooohhh had to subscribe to this as I face the exact same issue!! Been trying to get my Square reader to work for a while with root and could never figure out how they are detecting root. Using Pixel XL here

Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.

Skreelink said:
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Click to expand...
Click to collapse
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.

Idledev said:
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Click to expand...
Click to collapse
I agree, I have no problem hiding magisk and root from other apps, the square reader app must be somehow different. I've even gone through my storage and deleted any files or folders that might suggest the phone is rooted, but still no luck...
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
I've found a temporary workaround to my problem anyway, I realized that I can share my internet (wifi hotspot) with my ipod touch, this way square reader works as the ipod touch isn't jailbroken or modified. It just means I have to carry around my ipod touch with me, which is a better trade off for me than having a stock, non root phone

Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try

Idledev said:
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Click to expand...
Click to collapse
That's awesome! What canary build did you use?
I tried the latest build a few weeks ago and it didn't work for me

Build 18120

Idledev said:
Build 18120
Click to expand...
Click to collapse
No luck for me...
I updated to the latest canary build, cleared all data from square reader app, selected magisk hide, rebooted the device. After it booted up I tried to run it and it still detected root. I have a feeling that the OnePlus OS does something that doesn't totally allow me to hide root from the square reader app. It's annoying because for other apps root can be hidden
Maybe there's something in the Android Q build that lets you hide root better

Something that seems reliable right now on 18.1, Pixel Experience and OOS :
Combine Magisk Hide with Magisk "Core Mode". This seems to do the trick for now, Google Pay is triggered with normal mode, but works in Core Mode. Same for Snapchat and banking apps like N26.
But within this, you can't use any module.
kage00 said:
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
Click to expand...
Click to collapse
This is always a good idea, on OOS at least, Magisk being optimized sometimes prevents the granting of root rights to apps, it never reacts to kernel applications requesting root on startup for example.

There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616

DaveW1972 said:
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
Click to expand...
Click to collapse
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes

kage00 said:
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
Click to expand...
Click to collapse
Ummm yeah.. then the problem doesn't lie within Google pay it lies within the modifications that you are using.
I have to say I have never had any issues with Google pay or Android pay or any banking app using magisk. I don't even have to hide anyting. Of course I'm also not using any modified ROMs or kernels either

Hi guys,
I have this issue for a couple years now and I just cannot find a solution!
Google Pay, and 4 banking app from two different countries work fine with my 1+6 (stock ROM OOS 9.0.9 with magisk 19.4 - 7.3.4) but Square does not.
Did anyone find a solution?
Magisk config:
Magisk hide
Two modules OOS phone record and youtube
No core mode
All banking app and Square hidden

Related

Magisk not always active?

Hey,
phone unlocked/rooted with Magisk 17.3 - now 2 issues:
1. apps with root rights can not always use them. I have to start magisk app manually, close and reopen the app (e.g. SD Maid cleaning app) and then it has root rights again and works properly
a big problem seems to appear then on AFWall+, which is super slow for me. have to reopen especially instagram 3 times to get connection. I guess this is connected to the same issue with magisk, would be worth a try at least. anyone got an idea how I can fix the magisk issue?
2. apps that check for root (my online banking wont work on rooted phones) cant be tricked by the "magisk hide" function apparently. anyone got experience with that? what can i do?
thanks in advance guys :good:
steffenmix3 said:
Hey,
phone unlocked/rooted with Magisk 17.3 - now 2 issues:
1. apps with root rights can not always use them. I have to start magisk app manually, close and reopen the app (e.g. SD Maid cleaning app) and then it has root rights again and works properly
a big problem seems to appear then on AFWall+, which is super slow for me. have to reopen especially instagram 3 times to get connection. I guess this is connected to the same issue with magisk, would be worth a try at least. anyone got an idea how I can fix the magisk issue?
2. apps that check for root (my online banking wont work on rooted phones) cant be tricked by the "magisk hide" function apparently. anyone got experience with that? what can i do?
thanks in advance guys :good:
Click to expand...
Click to collapse
Flash latest magisk
yup for everyone who missed it....we had to skip v18 but the new v19 seems to be fully compatible #magisk

Can I install SuperSU on the OnePlus 7 Pro?

Hi everyone,
I'm curious if anyone has gotten the SuperSU root method running on this phone. I know that magisk exists but snapchat has problems with magisk for some reason so I would prefer to use SuperSU instead. I already have the latest twrp installed if that helps at all. Flashing the SuperSU zip doesn't seem to do anything so I'm hoping somebody has figured this out already.
Thanks,
TomatoesOnBluRay
TomatoesOnBluRay said:
Hi everyone,
I'm curious if anyone has gotten the SuperSU root method running on this phone. I know that magisk exists but snapchat has problems with magisk for some reason so I would prefer to use SuperSU instead. I already have the latest twrp installed if that helps at all. Flashing the SuperSU zip doesn't seem to do anything so I'm hoping somebody has figured this out already.
Thanks,
TomatoesOnBluRay
Click to expand...
Click to collapse
just realized i put this in guides instead of questions and answers. Is there a way to move it? Serious noob here.
Do not think anyone has used SuperSU in a few years really. What is wrong with Snapchat and rooted with Magisk?
Snapchat wont get along with Supersu either. At least you could try to hide Magisk from Snapchat
I'm abit curious now, why would you prefer having supersu when magisk works the same way but even better?
schmeggy929 said:
Do not think anyone has used SuperSU in a few years really. What is wrong with Snapchat and rooted with Magisk?
Click to expand...
Click to collapse
it seems like supersu hasn't been updated in a couple years now, so you're absolutely correct. Snapchat keeps locking me out of my account for "using a third party app" even though I haven't been using a third party app. My guess is that it's detecting root somehow even when I have magisk hide enabled, magisk changed to manager, and xprivacylua restricting snapchat's access to files. I even tried using parallel space to copy snapchat into an isolated environment, but it doesn't even log in. It might have something to do with Oxygen OS, but I'm not sure. Although it's unlikely, I'm trying to see if there is a way to install SuperSU on this phone because I know snapchat works as it did on my old phone (if you log in before you root, of course). If it's not possible, I'll just have to figure something out.
TomatoesOnBluRay said:
it seems like supersu hasn't been updated in a couple years now, so you're absolutely correct. Snapchat keeps locking me out of my account for "using a third party app" even though I haven't been using a third party app. My guess is that it's detecting root somehow even when I have magisk hide enabled, magisk changed to manager, and xprivacylua restricting snapchat's access to files. I even tried using parallel space to copy snapchat into an isolated environment, but it doesn't even log in. It might have something to do with Oxygen OS, but I'm not sure. Although it's unlikely, I'm trying to see if there is a way to install SuperSU on this phone because I know snapchat works as it did on my old phone (if you log in before you root, of course). If it's not possible, I'll just have to figure something out.
Click to expand...
Click to collapse
You need to Magisk hide Snapchat. Go to menu(top left, 3 lines) click Magisk Hide. Scroll to Snapchat and check it. Clear data for Snapchat. Log back in.
schmeggy929 said:
You need to Magisk hide Snapchat. Go to menu(top left, 3 lines) click Magisk Hide. Scroll to Snapchat and check it. Clear data for Snapchat. Log back in.
Click to expand...
Click to collapse
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
TomatoesOnBluRay said:
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
Click to expand...
Click to collapse
Weird, never had an issue with Snapchat and was always rooted.
I used to have the same issue with snapchat until I started using the Magisk Beta versions, since then I haven't had that issue at all. Which version of Magisk are you using?
TomatoesOnBluRay said:
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
Click to expand...
Click to collapse
Get it up and running, create a backup with titanium and when you are on magisk, restore the data.
Thats how i used to do it when it wouldnt let me log in. But I havent had the issue for years with magisk. Ensure you are using the current and ensure you pass safety net.

MagiskHide & Microsoft Teams

Hey guys
I've been using Microsoft Teams on my on my rooted phone using Magisk Hide for a while and it suddenly stopped working (saying my phone was rooted).
I then updated Magisk Manager & Magisk (22.0) but then Safetynet didn't pass anymore. I fixed it using safetynet-fix module as suggested here.
However since then I can't manage to use Teams, it still detects my phone is rooted. Magisk Hide is activated on the Teams app and companyportal app
Any help ?
Thanks
Mouchoir said:
Hey guys
I've been using Microsoft Teams on my on my rooted phone using Magisk Hide for a while and it suddenly stopped working (saying my phone was rooted).
I then updated Magisk Manager & Magisk (22.0) but then Safetynet didn't pass anymore. I fixed it using safetynet-fix module as suggested here.
However since then I can't manage to use Teams, it still detects my phone is rooted. Magisk Hide is activated on the Teams app and companyportal app
Any help ?
Thanks
Click to expand...
Click to collapse
Which rom?
Did you flash Magisk before the first boot?
NOSS8 said:
Which rom?
Did you flash Magisk before the first boot?
Click to expand...
Click to collapse
Hello,
MIUI 12.0.2 is my ROM. It was the same when Teams used to work.
And no I didn't flash Magisk before first boot
Mouchoir said:
Hello,
MIUI 12.0.2 is my ROM. It was the same when Teams used to work.
And no I didn't flash Magisk before first boot
Click to expand...
Click to collapse
Maybe try an older version of Magisk(Miui 12.02 android 10).
Uninstall your actually version.
Mouchoir said:
Hey guys
I've been using Microsoft Teams on my on my rooted phone using Magisk Hide for a while and it suddenly stopped working (saying my phone was rooted).
I then updated Magisk Manager & Magisk (22.0) but then Safetynet didn't pass anymore. I fixed it using safetynet-fix module as suggested here.
However since then I can't manage to use Teams, it still detects my phone is rooted. Magisk Hide is activated on the Teams app and companyportal app
Any help ?
Thanks
Click to expand...
Click to collapse
hey man, had the same problem and solved it yesterday after a lot of tries
I'm using the Magisk v21.2.zip and the Magisk 22 (manager). I uninstalled the Teams and the Company Portal app, made Magisk appear with another name (you can do it in the settings, I just put "Manager"), installed those apps again, used Magisk Hide and then it finally worked
math.rangel said:
hey man, had the same problem and solved it yesterday after a lot of tries
I'm using the Magisk v21.2.zip and the Magisk 22 (manager). I uninstalled the Teams and the Company Portal app, made Magisk appear with another name (you can do it in the settings, I just put "Manager"), installed those apps again, used Magisk Hide and then it finally worked
Click to expand...
Click to collapse
That worked for me thanks a lot !
If anyone needs :
Uninstall Magisk using the Manager
Uninstall Teams & Company Portal
Download Magisk 21.2 on the official Github
Flash it using TWRP
Install the Magisk manager
Rename it in the app settings
Install Teams & Company Portal and use Magisk Hide
Good afternoon,
Excellent tip! I was using version 22.0 and it didn't work.
I tested with Magisk 20.4, it also works.
Thanks
Mouchoir said:
That worked for me thanks a lot !
If anyone needs :
Uninstall Magisk using the Manager
Uninstall Teams & Company Portal
Download Magisk 21.2 on the official Github
Flash it using TWRP
Install the Magisk manager
Rename it in the app settings
Install Teams & Company Portal and use Magisk Hide
Click to expand...
Click to collapse
Tested on 21.1 debug version, working perfectly.
For me it didn't work so I tried older version of Portal ...teams then moan that it's not the latest, so I downloaded an older teams version too! ...now it works
So older portal version and teams and with the above mentioned ....it works
evronetwork said:
For me it didn't work so I tried older version of Portal ...teams then moan that it's not the latest, so I downloaded an older teams version too! ...now it works
So older portal version and teams and with the above mentioned ....it works
Click to expand...
Click to collapse
What versions did you installed for Teams and for Portal?
kbs23 said:
What versions did you installed for Teams and for Portal?
Click to expand...
Click to collapse
Well after like a day or two it just moans about root access and you still have to do uninstall both and reinstall - So it's either that or remove root - It seemed to work but it's not for long 2 days of usage tops
For me, I managed to fix it somehow by uninstalling some root apps (TitaniumBackup, Swift Backup, Tasker, etc) and deleting my twrp folder in my root storage and removing CP/Teams and then restarting and then re-installing CP/Teams and then unchecking MagiskHide on these apps (it was already-reselected) and then re-enabling MagiskHide. I think ultimately it was this last step (re-toggling MagiskHide on/off) that fixed it. Previously, after re-installing CP/Teams, MagiskHide (and all sliders) was already enabled and I just figured it was working, but it might not have been.
EDIT - nevermind, it still gave me the error after some time.
Still not working for me on my OnePlus 9 Pro. Removed all files/folder with root/kernel/boot naming from root storage. Deleted MS Teams and Portal app and reinstalled them. Reenabled in Magisk Hide but the Portal tool still detects root. Any other solutions?
Edit:
It worked now. In Magisk Hide I had to select all services from the Portal app and not just the main one.
I did some testing and the latest Microsoft Teams (V1416/1.0.0.2021114201) works with company portal app with up to this version:
Intune Company Portal - 2021-05-12 - v5.0.5147.0
Anything newer eventually leads to 'non-compliant device' error, even with the latest magisk hide fixes.
You can get it on apkpure.
same problems here, even though some months have passed after this thread,
teams requested that I go over and install this intune company portal app,
the problem occurred in 2 (of my 3) devices, all rooted, the 2 that had the problem are rooted with magisk,
no problems on the 3rd one rooted with super su,
anyway, I've spent many hours trying to make it work,
I changed package name of magisk, I updated it,
I uninstalled edxposed and switched to lsposed, etc,
nothing worked,
only thing that worked for me was to roll back to an old teams version,
back to august of 2020,
I downloaded from apkmirror
Would it not be possible to just keep everything the way it is and only unroot the phone?
Or does unrooting mean you have to go back to stock rom...?
of course it would be possible,
I'm not using a custom rom (miui actually) but you wouldn't have to go back to stock anyway,
anyway, I wouldn't want to lose root only for some app that I use on a laptop or work desktop
most of the time, it's useful for the notifications though..
muca89 said:
It worked now. In Magisk Hide I had to select all services from the Portal app and not just the main one.
Click to expand...
Click to collapse
It does work, and you do not need to reinstall or delete anything - just select the Portal app in Magisk Hide, select it again to display its services, and check all the services.
I'm using Teams on different Magisk rooted Androids, also MIUI 12.5.12.0. Why should that be an issue?
jerzyjerzy said:
It does work, and you do not need to reinstall or delete anything - just select the Portal app in Magisk Hide, select it again to display its services, and check all the services.
Click to expand...
Click to collapse
in my opinion, this is the solution.
it works for me

Safety net ,Multiple fails. List of what I tried and no luck so far.

My daughter got a new phone, after struggling with bootloops and magisk issues. Finally got everything working correctly.
But,
I got root to go fine, only thing is she has had location issues. Google maps, other GPS or location services did not work.
So I uninstalled xprivacylua and seems like services came back, looks like I wasn't hiding anything on it anyways. Or I don't remember what it was.
So instead of reinstalling xprivacylua I decided to look for different answers .
Maybe some other solutions.
Here is a list of apps and modules that are installed. I think some of them overlapped and are kind of messed up. To many that my head is spinning.
Magisk
23.0 (23000)
Magiskhide Props Config.
Riru
Riru LS exposed (Tried switching back and forth to edxposed)
Systemless Hosts
Universal Safetynet fix 1.1.2. (Tried different versions)
LS Esposed one module,
Hiddencore module (enabled Google services Framework and google play services)
Also cleared Data and Cache on google play store.
Rebooted every time
Always safety net failure.
I know its a lot to take in , and do appreciate any feedback or help on this issue.
Is it an 8T? Are you running stock OOS with magisk?
In that case all you need to pass safteynet should be Magisk 23 with magisk hide activated. No need to bother with Magisk hide propconfig, or edexposed or anything.
If you are running a custom rom it is a different matter
I have magisk 23 and magisk hide is active on all google play services, but it still fails.
Its 8t with stock rom.
I think this is why its a little confusing since on my stock 7 pro I have google play services and only android.gms, and android gms unstable hidden and it works fine.
There is not a custom recovery on either of these phones.
Magisk and magisk hide works fine for me, so don't know what to say.
Perhaps try to uninstall Riru and exposed to make sure that they aren't triggering safety net?
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Screens of magisk hide props config
scottlam1 said:
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Click to expand...
Click to collapse
Nope.. Terminal Emulator is actually recommended. With Termux, you are required to use root access for props to work.
with Terminal Emulator, you can just type:
props
and then it'll load. no "su" necessary. That's termux. I've had some issues that these people are talking about with my OnePlus 8T (KB2005, unlocked completely).. I'll try Termux just to rule this out, but this is highly doubtful as to whether or not safetynet passes based on this--it's attempting to modify the same values. Anyway, when I unlocked that bootloader on a stock rom, CTS Profile started showing as false. So I did get the stock on there correctly and it initially passed with a LOCKED bootloader. There's an alpha TWRP that you can actually flash if you want. There's a couple others where you can only boot it.. there's a lot of "only's" here.. and I couldn't get it going with any of the apps mentioned, including ditching EdXposed and deciding to try LSPosed, but that + XPrivacyLau didnt seem to help me. Maybe I'm doing something wrong. From what I can tell I've done everything right and I've got quite a bit of experience attempting/doing this. Sometimes Device SImulation and forced BASIC ATTESTATION can be a lifesaver.
On my OnePlus 6T, I don't have this problem.. then again it's on Android 10. I can't even get a proper root explorer for Android 11. I seriously can't stand what they did to Android 11.. it's so ridiculous how many apps are now incompatible. Root Explorer Pro was possibly the best Root File Manager I've ever used and I've used it since day 1.
Anyway, I'm gonna give all of this a shot in different order.. and this time I'll see if Magisk can do the trick (last time it was on some different firmware and i just now was able to get it going by flashing via Fastboot in Linux). It's the manual way (payload dumper) as opposed to MSMDownloadTool -- which could be used via a VM.. and maybe even better than using Windows tools where you literally have no idea what you're actually doing. I'm just saying. Android is a linux distro, technically.. and we're trying to use just basic root apps for Android 11, and they don't seem to work.. it's insane. They did something with the partitions and it's apparently having issues even mounting R/W even with Magisk giving it root permissions. Btw, Magisk Canary is now outdated, as far as I can tell? Or it's just nowhere to be found when it comes to versions. Either way, I have tried multiple. So I'll try again in a different order.
Sorry for the long post. I've just had it. I've been working on this for a WEEK non stop.. 5-6 days and this is the first sign of progress (reverting via fastboot via Linux, which is the same thing as the MSMDownloadTool ultimately... without the hassle of finding it)
Let me know if there's anything else.. cause I've tried just about everything out there. Remember, for me, so far... unlocked bootloader = CTS Profile failure.. but locked bootloader + stock rom? Passed. I don't know. Before it wasn't passing with a stock rom that came with it so that drove me nuts and made no sense, hence me saying "progress" ... heh. Anyway.. Please let me know if you guys do find anything that works for it. I'm at my wits end. There's basically almost zero support for the 8T but plenty for the 8 and 8 Pro. So that also gets on my nerves. Sorry, once again, for this really long post. Some of it is just venting and I'll update if I get somewhere with it.
.. and now this morning after installing magisk, by just booting twrp (not flashing, but booting) and then using LSPosed/XPrivacyLua (I installed MagiskProps too but I barely did anything aside from pick a fingerprint) --- and it passed? WHAT?
I'm gonna look into this, but I'm not complaining. Let's see if I can find good Android 11 apps for actually browsing the system and being able to r/w any elusive partitions -- wasn't working well with Android 11 before. Not sure if that's around with a simple design anymore. Root Explorer Pro was king of that. Then Android 11 stepped in. I still have to install Lucky Patcher, if it will even work as a module for LSPosed. (Yes, I'm one of those idiots) -- I fully expect it to fail with that but I might be pleasantly surprised. Who knows. So, we'll just call this mixed results. For now -- Passing somehow. I don't understand aside from LSPosed and XPrivLua.. maybe magiskprops. Not sure which one did what first to cause this to go the right direction.
All I can say is all I have is magisk props not the other 2 modules you speak of
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
eracet said:
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
Click to expand...
Click to collapse
Ok asked her what she did. Mentioned updated YouTube vanced. And not sure of anything else.

I Broke Magisk

It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
I'd been holding off on the update because I knew there was something going on with the developer going to Google and all the root/hide stuff being disabled. Not sure how to roll back or what to do.
Click to expand...
Click to collapse
Can you uninstall Magisk and install the stable or last working canary app?
simplepinoi177 said:
Can you uninstall Magisk and install the stable or last working canary app?
Click to expand...
Click to collapse
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
koberulz said:
No clue, I'm not sure what its status is these days. That's why I was hesitant to update (I've also been knocking back the Android 12 system update for the same reason).
Click to expand...
Click to collapse
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
simplepinoi177 said:
You can't uninstall the Magisk app; like from the App section in Settings or app info of the app? I'm not talking about the applied Magisk patched boot image.
Because I'm thinking you can just uninstall the Magisk app (as it's glitching and force closing), and try installing the stable or earlier canary builds...
Click to expand...
Click to collapse
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
koberulz said:
I don't know how that would affect root, or Magisk hide, as I know a lot of that has been nuked since topjohnwu got hired at Google.
I also currently have Magisk hiding itself, which may make even an uninstall difficult if I even knew what to install over the top of it.
Click to expand...
Click to collapse
Uninstalling the Magisk Manager app would not affect root; you might not be able to run certain rooted apps properly without granting them root access, but that's because of not having the Magisk app to grant it.
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings") so it's not detected by any root detection. In any case, you should be able to find it in the Apps list in Settings/Apps, and uninstall it that way.
As to what to install over the top of it, installing the latest stable 25.2 would be the best idea -- the Magisk App does not need to match the version that is patched and flashed to your boot partition...
simplepinoi177 said:
I don't know about topjohnwu being hired and working for Google or what not, but Magisk is still being currently worked on and developed so it has not been "nuked"...
Click to expand...
Click to collapse
My understanding was that he got hired and they said he had to give it up, there was some negotiation and they let him continue working on it as long as Magisk Hide was removed as a feature.
But this isn't something that really interests me all that much, so I don't keep up with the news on it. I more just check in whenever I get a new phone in order to figure out how to root it.
simplepinoi177 said:
How is Magisk Manager hidden "itself" if you claim you attempt to run the app and it force-closes? The only way for Magisk Manager to "hide itself" is that it merely renames itself (to a name you can choose; default is "Settings")
Click to expand...
Click to collapse
Yes, this is what I was referring to.
koberulz said:
Yes, this is what I was referring to.
Click to expand...
Click to collapse
koberulz said:
It updated today, and now I can't open it and I keep getting error messages to say it keeps stopping.
Click to expand...
Click to collapse
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
simplepinoi177 said:
Again, I ask, as you stated; you try to open it -- so you must know what name it's under then (even though it's hidden since it being hidden is just it hiding its name) -- and it keeps force closing or stopping... so why can't you find the app details and uninstall it?
Click to expand...
Click to collapse
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
koberulz said:
Because I don't know how that will affect root/hide. I'm not sure what the status of Magisk is these days.
Click to expand...
Click to collapse
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
simplepinoi177 said:
Magisk is pretty much the only way to root at this point -- I just learnt of another method KernelSU, but it seems pretty basic, especially in comparison to Magisk -- and the status of Magisk is that it is still very much active and actively developed; as it is the sole rooting method for numerous Android running devices, not just Pixels.
Your original issue is that Magisk Manager isn't working properly after updating and seems to be freezing/force-closing. The standard way of fixing that is to uninstall/remove the Magisk Manager app and re-install it (either the stable version or an earlier canary version that had worked previously).
Removing Magisk Manager app will NOT affect root and/or the patched boot partition. It WILL affect granting apps root access and will affect Magisk Hide (or Zygisk DenyList) -- but that will only last as far/long as rebooting and re-installing the Magisk Manager app. Once you re-install it, you will gain all of that back; it is only momentarily lost in between the uninstallation and re-installation.
Click to expand...
Click to collapse
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
koberulz said:
Is there a dedicated Magisk thread? It's very difficult to find things on this forum, given how large it is.
Click to expand...
Click to collapse
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
What's the difference?
koberulz said:
What's the difference?
Click to expand...
Click to collapse
dcarvil said:
There are 2 threads.
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
The first one is the first, general Magisk thread (that is still active and currently discussed). The second is as it is stated in the headline -- "This is a discussion and help thread for the newer versions of Magisk".
Most likely this is where you should go for your issues -- and to see how actively developed it is currently being.
It's just as you said, you've been away from rooting/Magisk for a while; the newer version of Magisk contains/employs Zygisk -- "Zygisk is new generation Magisk hide...Zygisk is what the Magisk developers call running Magisk in the Zygote Process of Android. The Zygote Process is the first process that the OS starts when it boots up, ... Since zygote starts first after system, it can hide root without sending data to apps." (source) As such, that's why a new thread was created and why it is sub-titled as "The Age of Zygisk"...
*but there are many more methods of hiding root than Zygisk (or in conjunction with); Shamiko, Magisk Delta, HideMyApp, etc.
In the end, I'm sure they'll suggest what I've suggested to you in some fashion -- you'll have to uninstall the Magisk Manager (hidden or not), and re-install the stable or earlier canary versions. But it'll be better coming from the people in that thread...
Good luck!

Categories

Resources