yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Solved and answer myself right in the post above yours - I update LSPosed and the latest from TG has a button to install shortcut
[Magisk] HippoMan:
That will install the shortcut on the Home screen, which is probably fine for almost everyone.

But I use Nova7 and I don't want that shortcut on the Home screen. I want to put it into one of the "app drawers" that Nova7 manages. But since it's only a shortcut and not a full-blown app, Nova7 won't let me me relocate it in that way.

I know that's a just a limitation of the Nova7 launcher, but I'm not going to change launchers just because of this one issue.

Anyone who shares some of my weird, idiocsyncratic preferenes for how to use Android and wants an actual app and not just a shortcut for invoking the LSPosed manager can try what I described above.
[Magisk] zgfg:
Excellent to know - it works

Create a file, eg:

openLSPosed sh

with the content:

#!/system/bin/sh
su -c am start -c org.lsposed.manager.LAUNCH_MANAGER com.android.shell/.BugreportWarningActivity

Save and execute from MiXplorer - see the screenshots
[Magisk] JiiJii:
My problem with banking apps is that after i updated Magisk Manager app to 26.3 it keeps coming back after i remove the app. 25.2 didn't do that. The app taht appears is not the full Manager, it only links to full app, but the banking apps still recognise it as Magisk Manager.

How do i keep it unistalled?

My banking apps work when i remove Magisk Manager.

Pixel 7 pro.
[Magisk] Homeboy76:
Check for hidden magisk apps or multiple magisk installations: https://xdaforums.com/t/guide-unlock-bootloader-root-pass-safetynet-on-pixel-7-pro-more.4505353/

OP (post# 1)

~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...

6. Root/Reroot with Magisk and Pass SafetyNet.

•

Patching the init_boot.img

- to root/reroot.

Important Notes

2. If you hid the Magisk manager app...

When you were rooted did you use Displax / safetynet-fix magisk module v2.4.0-MOD_1.3?
[Magisk] J.Michael:
I do not know which version, but at some point Magisk started installing a manager if, upon booting, there was no manager.

If you uninstall the manager and, without rebooting, try to use the banking app, does the banking app still seem to detect the Magisk manager app?

If you need to clear caches and reboot before the bank app will give you a fair try, try uninstalling the Magisk manager just before running the bank app.

Try searching the thread for talk about "freezing" an app -- that might be more convenient for you.

Also, check to see if disabling the Magisk manager app is enough to satisfy the bank app. Then check to see if on the next boot Magisk is satisfied. (I'm not sure what Magisk could install if there is already a manager app but the manager app is disabled, but I've been surprised before.)
[Magisk] JiiJii:
The banking app works if i uninstall Magisk Manager and dont reboot.

Manager appears after few days with no reboot.
[Magisk] badabing2003:
Hiding Magisk Manager is not hiding it from the bank app?
[Magisk] JiiJii:
No, it has to be uninstalled.
[Magisk] sawdoctor:
Have you tried magisk Delta? Think you can "freeze" magisk with delta
[Magisk] J.Michael:
Have you looked into "freezing" and "disabling"?
[Magisk] pndwal:
Please say which app... also, where Hide the Magisk app is not enough, adding the already hidden app (stub) in Hide My Applist LSPosed module is often enough to thwart both package detection and dex pattern matching (pushTAN apps did this). Have you tried that?

🤠 PW
[Magisk] paper88:
Hello together

I got some strange scenario. I rooted my Nothing Phone 1 and hide the Magisk App, after a few days i wanted to start the hidden Magisk Manager and it said "Your phone isnt rooted anymore, please restore Magisk Manager". I use the iOS Emoji Module and i still have them, so I know that root is still here. I already checked if there is another hidden Magisk App, but its just one installed. Now i can use my modules which I installed but I cannot delete or add some.

Does anyone have an Idea?

BR,

Maceo
[Magisk] pndwal:
App you show opened above is the full Magisk app...

Close it, find and uninstall all iterations of hidden App (stub) as you named them (default name is 'settings') from device settings, Apps, then try opening full App again... Assuming it finds Magisk properly now you can hide it again if you wish...

Nb. Issues often occur with update process, especially when updating Magisk without taking Restore the Magisk App when hidden stub is in use... PW
[Magisk] paper88:
Thanks for response! I checked already my Apps, I used "Manager" or "MM" for the hidden Names but both aren't installed on the system. The strange thing is, that after the update it worked and a few days later I wanted to start the hidden Magisk App it showed me the Restore Message. I could flash the boot.img again to Stock and back to root to check what will happen.
[Magisk] Papote3:
Does resetprop mods trigger SN because I flashed a new "Google assistant enabler" for magisk v9 and it seemed to not pass SN because of it
[Magisk] android_htc:
Magisk hide enabled and rebooted:

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Enabling systemless hosts file support

Mount: /magisk/.core/hosts

Enabling BusyBox

Mount: /magisk/.core/busybox

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

** Removing tampered read-only system props

** Starting Magisk Hide

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

MagiskHide: [com.google.android.backuptransport]

MagiskHide: [com.google.android.gms]

MagiskHide: [com.google.android.gsf]

MagiskHide: Error occurred...

Unfortunately, safety net still fails :(
[Magisk] :
It is my problem as well on my galaxy s5 w8 model.

Went further and tried with both stock enforcing and a custom permissive kernel.(worked with v8 for me but not this time.)

Damn Google...

I switched from apple to android because of their aggressive stance on modding. Guess I'll ditch google too and just get a tablet and a flip phone next lol. Micro**** was sued for less haha.
[Magisk] Captain_Throwback:
Well, you do see that error, right? Where's the logs?

(please include logcat)

EDIT: And make sure the advanced logging in the app is enabled.
[Magisk] ericotena:
View attachment recovery.log

Thanks.
[Magisk] Maxamillion:
How do you bypass safetynet with systemless Xposed activated? Root switch doesn't work for systemless Xposed
[Magisk] Nomelas:
Interesting, because when I enable magisk hide and reboot, I lose root. I have superSU 2.78-SR3 and suhide 0.55 and xposed 86.6
[Magisk] :
I'll likely make another attempt this weekend on a factory reset and provide a log for my part.

This phone runs crazy hot when doing operations like this.
[Magisk] westeight:
Magisk Hide enabled here from the go. Works fine. Also added Google Services, Android Pay and my banking apps to Magisk Hide. All work fine.

Only need to disable root with root switch to pass SafetyNet :p

Able to add a card to Android Pay, but haven't had the chance to actually attempt a purchase yet.
[Magisk] vegaman:
Thanks for the v9 update - I can pass SafetyNet now... under some circumstances.

Running on:

Nexus 6P

Franco Kernel (since stock kernel won't pass SafetyNet with an unlocked bootloader now)

NBD90X (October update, November update wouldn't boot with suhide, haven't tried with Magisk Hide yet)

On v8 I had been using the Pixel Launcher and Google Assistant modules. It looks like the Google Assistant module needs an update for v9. Pixel Launcher installs and works, but seems to break things with Magisk Hide enabled - I lose root and to get it back I have to disable the module or disable hide. Does anyone know if this can be fixed with an update or by me changing something?

I see others having issues saying that magisk is unmounting completely when they enable hide. To clarify, both root and hide work fine on my phone - with only the phh superuser module enabled. It only stops working when I enable the Pixel Launcher module, I wouldn't be surprised if it happens with other modules too, but I haven't tested any. Rebooting doesn't seem to help.

Logs attached, one with only phh and one with Pixel Launcher as well. The Magisk Hide stuff looks the same between them.

Cheers

Edit: Just tested a little more, it seems like root *is* working. It's more of a compatibility issue. Magisk Manager gets root, running su in terminal emulator works, but Root Explorer and Titanium Backup can't detect root.

Edit 2: I've tested with the Google Assistant module from here https://github.com/stangri/Google_Assistant_Enabler this works fine with hide, SN passes. So it's something about the Pixel Launcher module or the features it uses.
[Magisk] dimm0k:
any idea why I keep getting "This zip is not a Magisk Module!!" with this custom created module?
[Magisk] andrew2432:
Deleted.

Does rootswitch work with the new magisk/phhsu? Not su hide, but the xposed hiding app
[Magisk] westeight:
New version of SuperSu 2.78 (SR4) 'breaks' SafetyNet for some reason.

No longer able to pass now... even with root switch.

So, Magisk v9 + SuperSu 2.78-SR4 is currently not working.
[Magisk] Captain_Throwback:
Update your TWRP.
[Magisk] phuhcue:
Maybe someone can confirm some speculation on my part. I have a Tmo Note 5. I've done everything there is to try for hiding root/passing SN.

It seems to me that SN is looking at my boot.img and any modification there fails SN. If I flash a stock boot.img I pass. If I install Magisk to get root and then uninstall it everything works again. Suhide, rootswitch, magiskhide... none of these are working and it would seem are incapable of working if they modify my boot.img.

Is there any potential work around if this is the case?
[Magisk] Maxamillion:
Would also like to know.
[Magisk] Captain_Throwback:
Doubtful, unless there's been a Root Switch app update to support Magisk.
[Magisk] Vinnom:
Magisk still not working for Moto X 2014, trying to boot leads to bootloader.

My boot image
[Magisk] leisurebird:
My current setup is Super SU 2.78-SR3, Magisk v9, suhide, systemless xposed 86.6.

Would phh's superuser, Magisk v9, systemless xposed 86.6 give me the same result with regards to safetynet, hide root and xposed working? i.e. can i basically 'replace' SuperSU & suhide with phh's su and Magisk?
[Magisk] :
Root switch 1.3.3.2 is still the latest I've seen. And doesn't disable root for phh superuser. I still had root access after disabling root when i tried last night.
[Magisk] J.Michael:
Please don't.

Now you are mentioning an update. What did you update? (from and to) How did you update?

If you uninstall every manager app you can find, then reboot, Magisk should install a new manager app. Try that one.
[Magisk] pndwal:
Did you uninstall them?... Generally hidden stub will remain even if root is 'lost' AFAIK...

Do you have a 'second space' like Workspace (maybe your Parallel space app) or within a sandboxed environment (Island etc)... Please check no Magisk iterations are running within these...

Apps like Applist Detector will show random package names for any hidden Magisk stub instances installed (if applist hiding is not activated for it in HideMyApplist module etc)... Please run that and say what appears under Magisk App...

Typing magisk -c in a terminal emulator app will show version and version code for Magisk binary installed despite "Installed - N/A" showing... Please report that response too...

Maybe the installed full Magisk App doesn't match binary installed?...

🤠 PW
[Magisk] iwearthebelt:
Not sure if this will help you or not but I've run into something similar with my device and just a simple reboot fixed the problem. I always think that I lost root and start uninstalling Magisk and reinstalling it again but a simple reboot has fixed it for me. Can't hurt to try a reboot first, it might just work for you (sometimes we overthink the problem).
[Magisk] paper88:
Hello together

Thank you for your fast help! Uninstalling all Magisk Apps and rebooting really helped. I can use now the full App Features again. Thanks alot!
[Magisk] TheSamOfTheDay:
Updating to Magisk 26.3 disabled my unlocked phone's ability to read my SIM card, so now it gives me Invalid SIM card or SIM card not detected
[Magisk] zgfg:
Did you describe what is your phone/ROM, procedure you used for upgrading? What was the previous Magisk version you had .. to which version you upgraded (Stable or Canary or something else like Alpha or Delta)... what modules do you have installed?

I doubt that it would be a bug in Magisk- - if so, why all us others don't have?

Therefore, most likely something is wrong the way you upgraded.

From the "upgraded and now have the problem" nobody could provide you a meaningful help
[Magisk] pndwal:
Issues like that are classic symptoms of mismatched boot.img, eg user updates ROM then flashes previously patched boot.img... Many system updates require corresponding changes in kernel which resides in boot.img... PW

Please say how you updated (how boot.img was obtained)... and did you update ROM also? PW
[Magisk] TheSamOfTheDay:
All I did was upgrade with direct install
[Magisk] TheSamOfTheDay:
It was the stable version 26.3 through a direct install from stable 25.2. I looked through logs and no error whatsoever came up so I doubt the modules had anything to do with it.
[Magisk] J.Michael:
I think that 25.2 to 26.3 is a big enough jump that there have been problems, but they usually prevent booting.

Still, it couldn't hurt for you to restore your stock system, then manually patch and flash using Magisk manager app 26.3 to patch.

Let us know if your SIM card behaves any better.
[Magisk] zgfg:
Again, what is youe phone/ROM? Things like that are important and you still omitting to provide the info

Eg, if some Pixel, better use PF app for installing/updating Magisk, specially if the model/ROM requires patching init_boot

Does Magisk app show Randisk No on top - if so, it has been mentioned here several times that before Direct install (or also before patching the boot img !!!), user should disable Recovery option (yes, that's a known bug in v26.3)
[Magisk] TheSamOfTheDay:
Moto G Stylus 2021 on Stock Rom and all I did was a direct install
[Magisk] TheSamOfTheDay:
It says yes to everything and all modules run like normal. All I remember was that this started on Saturday from updating Magisk and SafetyNetFix Mod 2.0. It's a Moto G Stylus 2021 on stock Android 11.
[Magisk] TheSamOfTheDay:
You mean like uninstall Magisk and then patch it directly to 26.3?
[Magisk] TheSamOfTheDay:
Really my issue is that it seems Magisk locked my phone or something and I'm trying to figure out how to get it unlocked without paying for a scam service that may or may not work.
[Magisk] pndwal:
Magisk won't do that... Unless you used some hacked nefarious build!?

Won't phone boot at all now?

Edit: Please consider this post before the following:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-89077123 👍

----​

Assuming you only have the SIM issues mentioned, I'd suggest you simply check exact current ROM version/build, download full ROM and dirty flash that to restore stock booting...

If all works as expected again, do initial patch /flash to root again using boot.img extracted from that ROM... This will ensure you have boot.img properly matched to ROM and possibly correct other issues.

Nb. Your Magisk settings and configuration incl. modules will still be there... If there are still issues, next delete /data/adb/magisk directory and /data/adb/magisk.db folder and reboot... Magisk configuration will be rebuilt (modules will still persist, but need to set up superuser apps, denylist etc fresh)...

If there are still issues, try booting with all modules disabled...

🤠 PW
[Magisk] cadko:
I've installed LineageOS on my OnePlus 3T. Then I've installed Magisk according to Magisk Installation Instructions. My phone does haven't separated vbmeta partition. So, I checked "Patch vbmeta" option

After every LineageOS update, I patched boot.img and checked "Patch vbmeta" option

And now, in latest Magisk release I have not seen this option, when trying to patch boot.img.

What should I do now? Does Magisk now can determintate that vbmeta partition doesnt exist?
[Magisk] TheSamOfTheDay:
My phone boots as normal just the SIM card doesn't work and I can't access mobile network settings because of it.
[Magisk] pndwal:
Yup...

26202+ built these commits:

- Always check mounts to detect legacy SAR on bootmode

- Disable boot vbmeta patch when found vbmeta.img

- Fix device detection scripts and logic

- Do not allow user to configure boot vbmeta patching

👀 PW
[Magisk] pndwal:
Good... I wondered since you added that

So seems that's a bit of an overreaction?

... Anyway, I gave you some suggestions to try...

Edit: please read post below first. 👍

🤠 PW
[Magisk] pndwal:
PSA:

Another thing, I just checked @Displax USNF mod 2.4.0 mod 2.0 code again...

Nb. This was an experimental build to pass strongIntegrity while the "fake-strong-for-Pixel2" anomaly remained unpatched...

I had thought that this continued to work fine for devices not launched with A13+... It now appears that DEVICE_INITIAL_SDK_INT may have been set to 'nul' for all devices rather than to a proper API level (32 etc)... It only really needs changing to 32 for A13+ LV devices...

The 'nul' value may actually be equally bad for older devices, an may account for SIM and other issues...

I now recommend that ALL users AVOID @Displax's USNF mod 2.4.0 mod 2.0...

For devices launched with A7 - A12, use @Displax's USNF mod 2.4.0 mod 1.3 or @chiteroman's PIF... Both should work fine.

For devices launched with A13+, @Displax's USNF mod 2.4.0 mod 1.3 will work but is known to break VoWiFi on P7 series devices due to globally set shipping level prop... @chiteroman's PIF (with GMS targeted shipping level adjustment when 33+) should circumvent VoWiFi and other such issues...

👀 PW
[Magisk] cadko:
So, now a can patch my boot.img and should not be scaered about bootloop or making brick... I've had a sad experience, when I forgot to check "Patch vbmeta" option :confused:
[Magisk] pndwal:
Well supposedly... but I don't think we can make any guarantees with Magisk!... Doubt even John would... 😆

Nb. Magisk has kept AVB intact (ie. has not automatically stripped vbmeta flags etc) since it stopped patching fstab for modern 2SI devices in a magiskinit rewrite John called "a full paradigm shift on how Magisk hot-patch(es) the device at boot" for Magisk v25.1 some 16 months ago... There is no need to patch seperate vbmeta partitions in most stock installations since that time, and John noted that since "some custom kernels rely on AVB being stripped out for them by Magisk", Devs would need to change this approach...

Presumably (hopefully) where a device does NOT have a separate vbmeta partition, Magisk will handle any needed patching of vbmeta within a boot image properly... Not doubt the Installation Instruction page will be amended soon also to reflect the change.

The changes I linked for you above will no doubt reduce user error and issues, but modders should always have contingency plans incl. data backups, an understanding of how to restore unpatched partitions to fix boot issues, how to disable incompatible modules that may cause bootloop (read Magisk FAQs) etc. etc...

While much can go wrong at the best of times, be aware that an enormous amount of refactoring (with Zygisk even in TJW Magisk, with module/selinux rules and directory detection, with magiskinit injection, with code migration from C++ etc to rust, and much much more) in Magisk has been occurring lately, and many issues / regressions have already occurred / are to be expected, sometimes even in public Stable builds...

If you are concerned, I'd at least avoid Canary and public Beta builds... Still, to be forewarned is to be forearmed... 🤠 PW
[Magisk] TheSamOfTheDay:
Yeah I just uninstalled this thinking it was gonna revert the changes but NOoooooo...
[Magisk] TheSamOfTheDay:
The post you made seemed like you suggested I unroot and then root and then flash Magisk again. Seems like a long process since I dont even know HOW to unroot let alone rooting itself since I only did it once. This is bad for me since I have multiple accounts with 2FA on so I think it makes more sense to get a new phone in the meantime while I try to fix the current one.
[Magisk] pndwal:
Did you replace it with @Displax 2.4.0 mod 1.3 USNF?... PW
[Magisk] pndwal:
Unrooting is as simple and quick as restoring unpatched images, usually just unpatched boot.img, eg using fastboot or one of the two options John gives you in the Magisk App's big red 'Uninstall Magisk' home page button... 😜 PW
[Magisk] TheSamOfTheDay:
Yeah I was gonna ask if uninstalling Magisk would fix it
[Magisk] TheSamOfTheDay:
I used a Play Integrity Fix in place of it and nothing changed
[Magisk] TheSamOfTheDay:
I uninstalled Magisk and I have no more root and the SIM card still doesnt work so that means this phone is useless now
[Magisk] J.Michael:
Did you restore the original ROM, confirm that the SIM card was "working", *then* install Magisk -- just Magisk, none of the modules you've decided you need -- and check to see if the SIM card is working?

If you restore by flashing the unpatched images, but do not wipe data or otherwise eliminate the contents of /data/adb, then the newly installed Magisk will find the leftover pieces of earlier attempts. That might be fine, but we are not interested in learning which versions of Magisk can work with pieces left over from which versions of Magisk. Get rid of all the crap and test whether Magisk with no modules and no remnants of previous installations of Magisk seems to be responsible for your SIM card problems.
[Magisk] J.Michael:
Please explain what you mean by "uninstalled Magisk". Exactly what did you do?
[Magisk] TheSamOfTheDay:
the big button that said Uninstall Magiak, hit restore Images, did nothing, then I completed uninstall, unrooted my phone, then i factory resetted my phone, and my phone is still locked.
[Magisk] iruiz2:
Just to make sure... Did you test your SIM card is working on another phone, and that another SIM card is not working on yours?
[Magisk] TheSamOfTheDay:
Yes I literally walked into a T MOBILE store and the employee put the same sim card into a display phone and it worked normally, even that same phone showing up on my T-Mobile account
[Magisk] J.Michael:
How "did nothing"?

If "did nothing", how "completed uninstall"?

And what then is "unrooted"?

I will grant you that factory reset almost certainly removed the remnants about which I was concerned.

Maybe instead of wasting more time trying to get you to explain what you did, just follow the instructions you have been given repeatedly:

flash the stock ROM

confirm that the SIM related functions work

install a Magisk manager app

patch the boot image (and please make sure that it is the boot image from the stock ROM; and if your device/ROM is one where you need to patch something other than boot.img, patch the right thing, don't patch or flash the wrong thing; remember to uncheck the Recovery option if you have one)

flash the appropriate patched file

test the SIM related functions

And please stop saying that your phone is "locked". Unless you have relocked your bootloader. In which case, I'm done.
[Magisk] J.Michael:
I really wish I could hit the Like button a few more times for this one.
[Magisk] HippoMan:
... except the poster did indeed try that, and the SIM card is fine. See above.
[Magisk] J.Michael:
That's not the point. The point is it was an obvious thing to check, I never thought of it, @iruiz2 did, and I would have liked to be able to paste glitter and unicorns all over his post to express how much I Liked it.

You, on the other hand, can expect coal in your stocking.