Magisk General Support / Discussion

[zgfg]

How does one join that telegram? I can't search it in the telegram app and finding a link for it in Google seems very difficult...

See my post above, I edited, added a link to Github and then screenshots to follow

But you need to install TG app and register:

Telegram - Apps on Google Play

Telegram is a messaging app with a focus on speed and security.

play.google.com

 

[Olorin92]

See my post above, I edited, added a link to Github and then screenshots to follow

But you need to install TG app and register:

Telegram - Apps on Google Play

Telegram is a messaging app with a focus on speed and security.

play.google.com

Thanks - I'm noticing in the newer app I can't enable magiskhide, it just turns itself off everytime I go out and come back in. Is this meant to happen?

Or do I need to re-flash the boot img after patching it with this APK?

 

[pogo-airsupport]

Hi all,

Is anyone aware of a working solution for hiding mocked locations when using Magisk Canary + Android 12? The latest smali patcher causes boot loops when I try activating the module.

I have to use canary as the P6 Pro seems to only support that. I've tried the lsposed mock mock location module, but it doesn't work as I have to remove Pokemon Go from the denylist for it to properly work (and Pokemon subsequently detects root after that).

I'm guessing Magisk Alpha is probably my only bet here for now (assuming that implements Magisk hide still)

It's working for me though.
Are you using lsposed zygisk and passing safetynet?
I am using USNF 2.2.0 and mock mock.
DenyList doesn't have PoGo on it.
Doing this on 2 phones and no issues. (P6Pro + P4XL)
Make sure you don't have other files in storage or folders that PoGo can detect.
Remember your Lsposed MUST be zygisk version, otherwise Lsposed will not work with Zygisk denylist, making your mock mock useless as well.

 

[Olorin92]

It's working for me though.
Are you using lsposed zygisk and passing safetynet?
I am using USNF 2.2.0 and mock mock.
DenyList doesn't have PoGo on it.
Doing this on 2 phones and no issues. (P6Pro + P4XL)
Make sure you don't have other files in storage or folders that PoGo can detect.
Remember your Lsposed MUST be zygisk version, otherwise Lsposed will not work with Zygisk denylist, making your mock mock useless as well.

So I assume I've got the right lsposed version as the mocking works where it didn't before (I just got a could not find location error 12 in pogo). Whenever I remove Pokemon from the deny list, it pops up again complaining about the OS not being compatible/supported.

What folders or files should I look out for? As far as I know I've gotten rid of any Magisk related stuff...

 

[zgfg]

Thanks - I'm noticing in the newer app I can't enable magiskhide, it just turns itself off everytime I go out and come back in. Is this meant to happen?

Or do I need to re-flash the boot img after patching it with this APK?

Could you elaborate:
- New app = Magisk Custom 23015 or what?
- MagiskHide by itself turns off or some app gets removed from MagiskHide list or what?

If you installed Magisk Custom app - that is not enough, you need to install the corresponding Magisk Custom itself (Magisk app is only front-end) - by patching your (boot) img and flashing (that Magisk Custom 23015 debug cannot be reanamed to zip and flashed through TWRP).
And if you were switching from new Canary or Alpha, you better had to completely Uninstall your old Magisk (with all modules, everything) before switching to Magisk Custom - please read the Cudtom TG channel and/or posts about Custom in this thread.

That is because every of those Magisk versions: old Stable, new Canary, Alpha, Custom has (slightly) DIFFERENT format of magisk.db and if you don't perform proper switch, who knows what is your actual environment

Then, you will have to fully configure the new Magisk Custom (MagiskHide, root apps, modules), everything from scratch.
Obviously, you would not enable Zygisk but only MagiskHide.
And if you use LSPosed, you would need Riru and Riru-LSPosed
(but if you are talking about new Canary, then you should enable Zygisk and DenyList and use ZygiskLSposed - hence please be precise and specific in your posts, otherwise you will get wrong answers and if you apply you wrong instructions you will make things even worse)

Finally, I don't mock locations and don't use PoGo and cannot advise anything about

PS: I also use Magisk Custom d208be84 (23015) and have no problem with MagiskHide, nothing turns off - but see my screenshots

 

[pogo-airsupport]

So I assume I've got the right lsposed version as the mocking works where it didn't before (I just got a could not find location error 12 in pogo). Whenever I remove Pokemon from the deny list, it pops up again complaining about the OS not being compatible/supported.

What folders or files should I look out for? As far as I know I've gotten rid of any Magisk related stuff...

Make sure you are using Magisk and not some custom version.
Enable zygisk, enforce deny list, and add what is necessary in denylist (I only have my work stuff denied, not PoGo)
Then use Lsposed zygisk version (you need to download this from telegram, if you didn't, you probably have the wrong version).
Then use mock mock, and check pogo.

PoGo will look for any files that suggest magisk (make sure this is hidden as well!), or any custom recovery folders.
If you had used backup restore when you started using your P6P, you it may have transfered some old files from your old phone. The other thing is whether you hid your mocking app. If you are using it directly as downloaded, PoGo may be looking for the package name.

I'm not sure whether you actually need to pass SafetyNet for PoGo now. Previously on A11, you didn't. I only have 3 modules in magisk - systemless, USFN and Zygisk Lsposed. If you add anything else, you may be inadvertantly tripping PoGo detection.

That's it. I have this setup running on A12 P6P and P4XL and P2XL (A11). Not sure if anyone else has similar experience, or if it's not working for others?

 

[pndwal]

Latest Alpha Magisk (Unofficial)
Translated:

# alpha update log

## Magisk (0f71edee-alpha)
-[App] Support SharedUserId
-[App] Delete the backup file after restoring the boot image
-[App] Built-in current version update log
-[App] Use local version when unable to download stub
-[App] Switch to Java 8 Modern Time API
-[General] No longer automatically unlock the device block
-[General] Use MagiskHide to hide when Zygisk is closed
-[App] Delete markdown rendering
-[General] Do not execute scripts that have ignored loading modules
-[App] Fix Magisk cannot be updated from notification
-[App] Fix that the second time tapping the hidden app button may be unresponsive
-[App] Fix the effective time of signing certificate
-[App] Enable network request caching
-[App] Rewrite install application function
-[App] Enhance the function of repairing environment
-[App] Fix that some processes in the exclusion list may not be displayed
-[App] Support setting the KEEPVBMETAFLAG flag to skip processing vbmeta in the boot image
-[Zygisk] Fix Xhook

PW

 

[pndwal]

Nb. New Alpha Magisk has Xhook fix merged (Not yet in TJW Magisk downstream:
https://github.com/topjohnwu/Magisk/pull/5010 ) so supports new Zygisk hide solution which is "Shadow Mistress Yuko: Hide for zygisk".

New Shadow Mistress Yuko is also available. Shamiko-v0.1.2-47-release zip

PW

 

[zgfg]

Nb. New Alpha Magisk has Xhook fix merged (Not yet in TJW Magisk downstream:
https://github.com/topjohnwu/Magisk/pull/5010 ) so supports new Zygisk hide solution which is "Shadow Mistress Yuko: Hide for zygisk".

New Shadow Mistress Yuko is also available. Shamiko-v0.1.2-47-release zip

PW

Trying with 0f71edee-alpha (23015) but Shamiko reports that Magisk is somewhat broken and Momo still finds Zygisk

All other things work for me (SafetyNet hence DenyList and Zygisk, Superuser grants, modules - and of course, I do testing without Riru)

PS: Tested also with all other modules disabled, still Shamiko reports the same error and fails to hide Zygisk

EDIT:
With the updated:
Shamiko-v0.1.2-47-release.zip
It worked!!!

 

[zgfg]

Trying with 0f71edee-alpha (23015) but Shamiko reports that Magisk is somewhat broken and Momo still finds Zygisk

All other things work for me (SafetyNet hence DenyList and Zygisk, Superuser grants, modules - and of course, I do testing without Riru)

PS: Tested also with all other modules disabled, still Shamiko reports the same error and fails to hide Zygisk

EDIT:
With the updated:
Shamiko-v0.1.2-47-release.zip
It worked!!!

Updated to Shamiko 47 and it works:
- Enforce and Configure DenyList
- Install Shamiko
- Disable DenyList - Shamiko takes over, DenyList will work although disabled in Magisk app

Then Momo does no more find Zygisk while SafetyNet still passes (I have two other apps that I had to add to DenyList and they also don't complain about root)

 

[pndwal]

Trying with 0f71edee-alpha (23015) but Shamiko reports that Magisk is somewhat broken and Momo still finds Zygisk

All other things work for me (SafetyNet hence DenyList and Zygisk, Superuser grants, modules - and of course, I do testing without Riru)

Working for me.

I suspect you have broken db or other in /data/adb due to unofficial Custom Magisk use if didn't take full Magisk Uninstall. I was able to take 'dirty' Alpha install (w/ Direct Install) over Canary however.

Also, to clarify, you will need to disable Enforce Denylist after you configure it as per original instructions. (Google translation could be clearer / doesn't help):

LSPosed:

Shamiko Preview

Simple hide based on zygisk.

Configure inheritance denylist. After installing Shamiko, configure denylist and close denylist, Shamiko will automatically take over and hide.

Theory supports Android 8.1+, but only tested on 11

Clearly we will need to wait for Zygisk compatible solutions / details for other traces / environmental abnormalities detected. I have no idea how @nu11ptr got completely happy Momo.
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86032113

Both Rootbeer Fresh and Rootbeer Sample are happy with my setup, and I can still hide 'root' from PushTAN app.

PW

Edit: See you got it sorted...

Nb. Solution is not open sourced yet, and @nu11ptr indicated that this will likely not change.

 

[Lord Sithek]

Working for me.

View attachment 5475567

I suspect you have broken db or other in /data/adb due to unofficial Custom Magisk use if didn't take full Magisk Uninstall. I was able to take 'dirty' Alpha install (w/ Direct Install) over Canary however.

Also, to clarify, you will need to disable Enforce Denylist after you configure it as per original instructions. (Google translation could be clearer / doesn't help):


Clearly we will need to wait for Zygisk compatible solutions / details for other traces / environmental abnormalities detected. I have no idea how @nu11ptr got completely happy Momo.
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86032113

Both Rootbeer Fresh and Rootbeer Sample are happy with my setup, and I can still hide 'root' from PushTAN app.

PW

Edit: See you got it sorted...

Nb. Solution is not open sourced yet, and @nu11ptr indicated that this will likely not change.

How the heck you got SPushTan happy? Its more for testing purposes for me, I dont really need this app, but no idea how to bypass it Shamiko latest enabled and working, denylist disabled after configuration, rebooted, RootBeer Fresh doesnt find anything, but SPushTan complaining constantly! Also I hided Magisk app and LSPosed manager. Have no idea what else could I do

EDIT: Possible that lack of encryption results with this?

 

[pndwal]

How the heck you got SPushTan happy? Its more for testing purposes for me, I dont really need this app, but no idea how to bypass it Shamiko latest enabled and working, denylist disabled after configuration, rebooted, RootBeer Fresh doesnt find anything, but SPushTan complaining constantly! Also I hided Magisk app and LSPosed manager. Have no idea what else could I do

Yeah, Push-TAN is simply detecting Magisk App but using special tricks, which is why freezing this works, but 'Hide the Magisk App' alone is not enough as with that

only the package name changes. The classes.dex with the code does not change and can be used to identify the app.

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-893367674

Their protection engine (Promon) indeed seems to employ a very simple pattern matching on the installed apps. Rebuilding the stub app combined with Magisk Hide hides it successfully.

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-892775076

So if stub app is rebuild it can be hidden. Simply put, "a simple app packer [does] mitigate the detection very easily"
https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-892224424

However I found this method solved it more simply about one month ago:
https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-964222271

I don't need it (in Australia) either; just tried out of curiosity and as I knew it was a long standing issue.

EDIT: Possible that lack of encryption results with this?

Doubt it. My results w/ encryption above are similar... PW

 

[Lord Sithek]

Yeah, Push-TAN is simply detecting Magisk App but using special tricks, which is why freezing this works, but 'Hide the Magisk App' alone is not enough as with that

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-893367674

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-892775076

So if stub app is rebuild it can be hidden. Simply put, "a simple app packer [does] mitigate the detection very easily"
https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-892224424

However I found this method solved it more simply about one month ago:
https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-964222271

I don't need it (in Australia) either; just tried out of curiosity and as I knew it was a long standing issue.

Doubt it. My results w/ encryption above are similar... PW

Oh yeah, I've seen this solution of yours before, just totally forgot about it Using HMA is enough indeed, thanx

 

[Schroeder09]

I'm on Android 10 march 5, 2020 update on a p2xl. I can't open the manager. I think I was on like v20.4. A couple weeks ago I clicked the update button in the manager. I think it was to a v22 or something. The direct install option never popped up. The installation didn't complete, but I think something is messed up because I can't open the manager. The message I get is:
Upgrade to full magisk manager to finish the setup. Download the install?

I click "ok" and it just says the same message. What's the proper way to install the most recent and compatible version of the manager on my current install? I don't want to have to go to Android 11 and deal with the 3 weeks of getting my phone set back up to how it was. I don't have time for rooting anymore.

 

[zgfg]

Working for me.

View attachment 5475567

Edit: See you got it sorted...

Not that I 'sorted out' but they fixed Shamiko - with (42) three other users reported the same problem on TG channel, but when you woke up , the bug was already fixed in the new Shamiko build (47)

Anyway, more about my tests with Magisk Alpha 23015, Zygisk+DenyList, Shaniko and Momo v4.0.1:

With USB debugging disabled, Magisk app repackaged and all modules disabled except Shamiko, I still have:
- Partitions mounted abnormally
- Restriction on non-SDK interfaces is not working
- Bootloader unlocked

Unfortunately, I cannot get any better than that?!

I.e., compared to you, I have additional detection:
- Restriction on non-SDK interfaces is not working

but on the other side, I don't have yours:
- Found Magisk
- ART parameters are abnormal

---

I can Restore Magisk app, enable BusyBox, Systemless hosts, AML, Viper4Android (using v2.7.2.1 - it doesn't switch to Permisive mode) and Smali Patcher (I only patch Secure Screenshots), they don't make any worse, I still have the same three Momo detections as above

---

When I enable Zygisk-LSPosed module, Momo ads:
- ART parameters are abnormal

but by disabling the (single) line in the LSPosed system.prop file (workaround suggested by @Eng.Raman), I can avoid that abnormal Art params detection

And with that workaround all my LSP modules (GravityBox, CustoMIUIzer, Hide My Apps) and their corresponding mods still work correctly

---

When USB debugging in Developer options is enabled, Momo will add:
- Debugging mode is enabled

---

Finally, I can also enable Systemless debloating (by use of .replace files) and debloat various apps (tested by debloating 25 of them) from /system, /system_ext and /product - with no implications to Momo detections

However - that's strange, if I debloat any app from /vendor (I tested separately with 3 of them), then Momo immediately detects (and only in that case for me):
- Found Magisk

 

[J.Michael]

I'm on Android 10 march 5, 2020 update on a p2xl. I can't open the manager. I think I was on like v20.4. A couple weeks ago I clicked the update button in the manager. I think it was to a v22 or something. The direct install option never popped up. The installation didn't complete, but I think something is messed up because I can't open the manager. The message I get is:
Upgrade to full magisk manager to finish the setup. Download the install?

I click "ok" and it just says the same message. What's the proper way to install the most recent and compatible version of the manager on my current install? I don't want to have to go to Android 11 and deal with the 3 weeks of getting my phone set back up to how it was. I don't have time for rooting anymore.

Do you still have a rooted phone?

If so, maybe you can use the Magisk command-line program to determine what version of Magisk is installed, then pick a corresponding version of the Magisk Manager app.

 

[Schroeder09]

Do you still have a rooted phone?

If so, maybe you can use the Magisk command-line program to determine what version of Magisk is installed, then pick a corresponding version of the Magisk Manager app.

Root checker says I'm not rooted, but titanium backups says I am. Every root app is functioning the same. Substratum, adaway, matlog, and tasker are all still doing their thing. I just can't see anything or change any settings on them through the magisk manager.


Is it an option to flash the old manager in twrp? I know have two magisk apps on my phone since the half way install of v22 got on here. I have the magisk app and then another one that says magic mask. When I tap on that one I get the install message I described before.

 

[GivIn2It]

First of all, I did multiple searches. The search this thread function does not work correctly for me. My problem is: magisk canary 23015 has no modules. Suggestions online said clear repo cache, That option does not show. touching the layers button does nothing, all I have is install from storage. Can someone tell me how to populate this modules list, or how to download and install the modules to storage? Its a Pixel6Pro. Root is working great so I don't intend to re install.

 

[zgfg]

First of all, I did multiple searches. The search this thread function does not work correctly for me. My problem is: magisk canary 23015 has no modules. Suggestions online said clear repo cache, That option does not show. touching the layers button does nothing, all I have is install from storage. Can someone tell me how to populate this modules list, or how to download and install the modules to storage? Its a Pixel6Pro. Root is working great so I don't intend to re install.

There are problems with search in XDA - nevertheless, when you updated Magisk, you could have read the ChangeLog to realize that support for Repo is gone from Canary and there is no such thing as wiping cache or so to 'help'

Install Fox Magisk Modules Manager root app (sorry, I'm not going to search where from to install, but that was also posted here maybe twice - google for Fox Mmm on the Net)