yashsingh1/xdaforums huggingface dataset:
[Magisk] oldman20:
And every time i open Oprek alway has a toast message, is it wrong smt?
[Magisk] wugga3:
Same here but Oprek is all green and no all problems so far... So good? May be Oprek issue idk
[Magisk] An68:
Please I need help, I was trying to pass SafetyNet with Magisk officiale and alpha, and now I'm in RescuParty of TWRP. What can I do forma restore my data. Thanks
[Magisk] pndwal:
Won't boot?

If you just want to restore boot w/ data, depending on the issue, simply flashing unpatched boot.img and/or recovery image from current ROM should do it for most devices. Use method for Samsung from official Installation Instructions if you have a Sammy Android 9+ device. Nb. You may need to delete modules, database file or all content from /data/adb if you want to install Magisk again later.

🤠 PW
[Magisk] m0han:
yeah. the failed: unspecified error toast was reported here earlier.
[Magisk] m0han:
i'm using magisk-alpha. ideally, you need to create template, name it something and add Magisk (or it's renamed version), HMA, LSPosed to it. remember to save each step.

then add Oprek in Effective apps, enable Hide, Blacklist, All methods and enable your created template. remember to save each step.

enable zygisk in magisk, add magisk detector and oprek detector in denylist and disable enforce denylist.

if you have custom recovery (TWRP) it's good to rename the folder to something else. reboot and check. all should be good now. ymmv.
[Magisk] An68:
Thanks I've

Thanks, I don't know the issue, after reboot the phone xiaomi vaju, is the Rescue Party trigger. For uninstall Magisk alpha is the same of officiale, renamed the zip?
[Magisk] zgfg:
Everybody has the toast in Oprek, so many times commented.

But then toast dissoears and Oprek shows results

If the toast is showstopper for somebody, don't use Oprek
[Magisk] pndwal:
Yup, you can run as uninstall.zip from twrp, and it should restore stock images / remove magisk installation from /data/ADB... My method is manual way, and should work even if anything is borked in magisk... Is that Xiaomi POCO X3 Pro, Vayu?

NB. If you see ramdisk = no, you should generally ignore ths and leave Recovery mode unchecked on Xiaomi devices... (This may also be causing you to land in TWRP.) PW
[Magisk] An68:
Yes.

Thanks. I check

I can boot now, after uninstall Magisk alpha and delete Magisk adb folders.

Just one thing, when installed the uninstall.zip I saw install process, then I found the Magisk folders in adb. I deleted that again and reboot.

Thanks
[Magisk] zzz2002:
When I installed Shamiko it asked for permission to access to things like addresses ... (Sorry I did not manage to note all of the permission demanded).

After installation I was directed to a list of modules to be installed, several of which I consider "if yyy".

I it safe to use this device, or should I wipe it and start again.
[Magisk] zgfg:
That is not Shamiko module
[Magisk] zzz2002:
So wipe, install stock and redo lineage? Would be a good idea?
[Magisk] ahpekriderzbmx:
How To Bypass This?
[Magisk] pndwal:
What hiding solutions are you using? PW
[Magisk] m0han:
if you haven't yet, try the steps in my post above. i get 'all green' that way on everything latest. people like @zgfg, @pndwal are always at hand to help.
[Magisk] iceman1875:
I remember many years ago, one could search modules with the Magisk app. Is this still the case?
[Magisk] zgfg:
Magisk v24 Changelog - support for Modules repo removed.

This thread - many times mentioned Fox Magisk Module Manager (Fox Mmm) as a possible replacement (it looks to the old but frozen Repo and the new Alt Repo where not so many modules are moved yet by their developers)
[Magisk] iceman1875:
Okay thanks.. i havent looked at Magisk yet, but was just wondering about that feature
[Magisk] zgfg:
LSPosed supports what they naned Parasitic behaviour - uninstall LSposed apk, it will create the shortcut instead and Oprek will not find it anymore

You must also include XPrivacyLua apk into your HMA blacklist template that you apply to (effective apps) to Oprek (and to your banking apps)
[Magisk] ahpekriderzbmx:
Like This Right?
[Magisk] zgfg:
Supposidely, I don't know how you named the template (but if it offers only one template, then you only have one template).

Also, don't know what others apps you listed in the template (Magisk app, HMA app, etc)
[Magisk] ahpekriderzbmx:
I'm confius in HMA...
[Magisk] J.Michael:
"confius"?
[Magisk] J.Michael:
and identify the source of this probably-not-Shamiko
[Magisk] hjjiang:
what is HMA? i tried looking for it but all i see is instructions on how to use it but not what it is
[Magisk] m0han:
maybe he meant he's confused about configuring hma
[Magisk] m0han:
Hide My Applist: https://github.com/Dr-TSNG/Hide-My-Applist/releases

GitHub - Dr-TSNG/Hide-My-Applist: An Xposed module to intercept applist detections

An Xposed module to intercept applist detections. Contribute to Dr-TSNG/Hide-My-Applist development by creating an account on GitHub.

github.com
[Magisk] pndwal:
https://github.com/Dr-TSNG/Hide-My-Applist 👍 PW
[Magisk] HippoMan:
Confucius.

These words of his apply in this thread: "He who knows all the answers has not been asked all the questions."
[Magisk] K_a_m_i:
If you install Oprek Detector into the work profile everything is green.
[Magisk] oldman20:
Thank, i will try it. And what i understand is to create a blacklist template in this case? I using HMA 2.3.2 currently, but but is it necessary to install additional modules in the installed HMA apk?

Thank you
[Magisk] zgfg:
Use HMA = Hide My Apps and list there together with Magisk app and other LSPosed modules/apps also Lucky Patcher

See:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86376291
[Magisk] zgfg:
See my post right above - link to the guide(s) how to use HMA
[Magisk] oldman20:
But sadly HMA is discontinuos , I am concerned about its effectiveness in the near future by the way, is it possible/should we use both HMA and Xprivacy Lua? Is it superfluous? Which one is better at the moment?
[Magisk] bege10:
Some module developers still update their modules in the no more maintained magisk module repo. That's why Fox's Magisk Module Manager meanwhile shows updates in both repos the old Magisk module repo and the alternative module repo.

So it is possible again to stay updated with all modules in these two repos.

As a user I'd apreciate it very much if devs will put their modules in the alternative repo or add their own repo to Fox's Magisk Module Manager.

GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it

A module manager for Magisk because the official app dropped support for it - Fox2Code/FoxMagiskModuleManager

github.com
[Magisk] zgfg:
Old TJW Modules Repo should have been FROZEN and NOBODY COULD SUBMIT or UPDATE their modules to that repo anymore - according to what TJW tweeted and wrote to the Magisk v24 ChangeLog

Instead, new Magisk v24 supports the new feature:

- modules may have the their update.json file somewher on the Net (usually on the dev's own Github page) where one link points to the nodule's changelog and another to the zip file with the new version.

E g.,Shamiko module is NOT on any Repo

But if you have Shamiko installed, Magisk app v24 will see from its module.prop where the Shamiko's update.json is, and from there it will see if/when Shamiko has an update and you will be able to update Shamiko
[Magisk] bege10:
?

Because there are modules that are not in any repo yet and can only be found by reading forum threads I'd apreciate if the devs added their modules to the alternative repo or add their own to Fmmm.
[Magisk] zgfg:
Mechanism behind the Update icon (if you don't have the latest version of that module) illustrated for Zygisk-LSPosed module (screenshot "update") in Magisk v24 app

1) Use some root explorer like MiXPlorer and go to:

/data/adb/modules/zygisk_lsposed

2) Open its module.prop file (text file) and see the last line:

updateJson=https://lsposed.github.io/LSPosed/release/zygisk.json

(screenshot "module")

3) Copy that URL to your browser, it will open the LSPosed's update json file, you will see (screenshot "json") a page with two links:

"zipUrl": "https://github.com/LSPosed/LSPosed/releases/download/v1.7.1/LSPosed-v1.7.1-6358-zygisk-release.zip", "changelog": "https://lsposed.github.io/LSPosed/release/changelog.md"

4) Copy that (last) changelog URL to browser, it will open the changelog md file (screenshot "changelog")

Similarly, if you copy and open the zipUrl URL, browser will download the latest version of Zygisk-LSPosed zip

Similarly, if you have Shamiko installed, go to:

/data/adb/modules/zygisk_shamiko

Open it's module prop and follow the same procedure to find the changelog for the latest Shamiko and the URL to download

Hence, when e.g., newer (stable) Zygisk-LSPosed module would be released, developers will update the json file (on their Github page) to point to the changelog and zip for the e.g. new v1.7.2

Magisk app will see that you still have v1.7.1 and will un-gray the Update icon, offering you to update the Zygisk-LSPosed
[Magisk] zzz2002:
I wish, but unfortunately I wiped my system and reinstalled without magisk.
[Magisk] bege10:
@zgfg

Thank you for your explanation how it works in Magisk.

I only explained how it works in Fmmm (with updated modules in the old and alt repo), and that is a way that is very comfortable for users like me.
[Magisk] zgfg:
More about freezing the old TJW Modules Repository

In Magisk v24 app, main window, l click to Install icon on the right from the Magisk App v24 info (screenshot Magisk-v24)

Magisk v24 Changelog will open (you don't need to accept re-installing).

Scroll down to find the paragraph about the Modules Repo and read Top John Wu's own words about freezing the old Modules repo and removing the On-line Modules supports (connection to his old Repo) from the new Magisk v24, and about the suggested new updateJson mechanism (screenshot Repo)
[Magisk] zgfg:
Fox Mmm connects to the old/original Repo (that TJW talked about freezing) and to the Alt-Repo

Plus, Fox also supports that new updateJson mechanism (although, seems, with some bugs in their app)
[Magisk] bege10:
This is all correct and there will be no new modules in that repo. And it is also correct that there are - still - module updates in that repo (screenshot above) and that they can be easily installed via Fmmm.
[Magisk] bege10:
Do you talk about this repo https://github.com/Magisk-Modules-Alt-Repo or about this one https://www.androidacy.com/modules-repo/ ?

I am talking about the first one.
[Magisk] zgfg:
Ok, I see in Fox Mmm that some modules have been updated on the old Repo e.g even on Feb 4 (screenshot)

This seems to be in conflict (?) to what the Magisk v24 ChangeLog describes about the freezing of the Repo

There was also a lot of discussion about the Old Repo in THIS THREAD, citing/pointing to TJW's tweets where he also explained his standpoint not only about removing the Repo support from the new Magisk app but also about FREEZING the old repo
[Magisk] zgfg:
I don't know for and Don't talk about the second

Ok, that's it... (so many posts)
[Magisk] bege10:
Yes, there is enough information that every user and developer can form one's opinion.
[Magisk] pndwal:
correct

wrong*

The Release Note says

"Was frozen" officially occurred late Dec 2021 when John locked repo for new submissions by archiving

https://github.com/Magisk-Modules-Repo/submission

and 'shut down' Magiskbot responsible for moderating and maintaining Magisk Module Repo.

www.twitter.com/topjohnwu/status/1474101935611408389

However this had already effectively occurred many months earlier as no 'moderator reviews' had been occurring.

[App] Downloading modules from the centralized Magisk-Modules-Repo is removed

Download functionality was actually first removed in Zygisk enabled canary builds but continued to work in 23.0- until Magiskbot 'shut down' in December.

*Nb. Magisk-Modules-Repo/submission is archived but Magisk-Modules-Repo is not, so maintainers can still update their module repos hosted there. However Magiskbot 'shutdown' means that even in 23.0- Magisk, module update feature is gone.

FWIW: The Magiskbot 'shutdown' is actually a complete repurposing.

Readme.md is updated from:

to:

https://github.com/topjohnwu/magiskbot/commit/43e39211708251bb7900799e0e7705e9672d9264

So far Magiskbot is reassigned to Moderate issues to follow template and Auto close spam issues/Pull Requests among other things. This coincides with the following commit (to remove old issues Bot) in Magisk master:

Remove issues action …

'Handled by external MagiskBot'

🤠 PW
[Magisk] zgfg:
What's the difference between those last two posts #50607 and #50608?
[Magisk] 73sydney:
Just to make sure things are clear on this story

The issue (that i have) is androidacy scraping both the official, and alt-repo, and trying to monetize them on their site.

The alt-repo itself isnt trying to monetize, but they have agreed to let androidacy to scrape their repo (note androidacy didnt ask to scrape the original one)

Hypocritically, while androidacy says on their website that to submit your module to them you have to "have the permission of the author". But if youre an author like me and you find (by accident in my case) theyre scraping your module from the offical or alt-repo, and inserting ads into the displayed readme's and download pages on their web repo and complain about it and expressly tell them they dont have permission to do it, they block you from contacting them via any method after telling you (very rudely) you dont have any rights and they can do what they like.

The author of Fox MM (Fox2Code) has been very understanding about my objections and the problem, and is kind of stuck in the middle on this one. He has floated the idea of adding a module.prop option allowAndroidacy=false for Fox MM to interpret and not present it for scraping to androidacy to get around the issue, but for me thats a bit too late, given androidacys attitude. They can burn in hell as far as im concerned
[Magisk] zipalign:
THIS is the solution I've been waiting for.

you da man!

thanks a lot!
[Magisk] pndwal:
... From this member:

https://github.com/topjohnwu/Magisk/issues/5361#issuecomment-1027061705

How do you know this is a developer?

Incidentally, I made this issue:

https://github.com/topjohnwu/Magisk/issues/5382 - PW
[Magisk] zgfg:
Nb: Issue simply Closed: No support for older versions (of Magisk)
[Magisk] pndwal:
Re. Broken 'Hide the Magisk app' function in non-current builds:

For 23.0 and earlier you will need to set / use Custom Channel to successfully 'Hide the Magisk app' due to standard URL channel using JSON that always points to Latest builds and therefore fetches latest (not backward compatible) stub file.

Set Update Channel to Custom, then place the following URL (by version) in Custom Channel dialogue box:

23.0:
https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c304e59f631280cc26ccc6d40a7cf04f7f37/stable.json
22.1:
https://raw.githubusercontent.com/topjohnwu/magisk-files/aede114205ae3d9b488f96e68e958ed2c26652fe/stable.json
22.0:
https://raw.githubusercontent.com/topjohnwu/magisk-files/ac33fd25f0dfeae9d5898df4c249785b42ce131d/stable.json
21.4:
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad863d3a15c6a2276b1061a280ece80ed7/stable.json

For 24.0+ - Going forward, the same issue will occur where updated stub file in current Latest Magisk build is incompatible with the earlier build in use due to standard URL channel using JSON that always fetches latest stub file. However, we won't need to use Custom Channel to fix this as we do for pre 24.0 builds.

From 24.0 we already have 'Use the local version of the stub when it cannot be downloaded' fix. Therefore this issue can be overcome going forward simply by turning off all network connections to force 'Use the local version of the stub' which works flawlessly. (I've tested this with 24.0 and 24.1)

👍 PW
[Magisk] Cyndaquissshhh:
Hello. To anyone using steadfasterX's LineageOS builds for SM-T285, flashing v24.1 will not work (it won't boot). Stay on v23 for now. Also, upgrading to v24.1 via Direct install would result in "Custom binary blocked by FRP lock" and you'll have to flash stock again since your bootloader locked itself.

Unfortunately, I wasn't able to get logs of those errors... 😥
[Magisk] szazs89:
I got this "FRP lock" trap when disabled OEM unlock, too... (S7 edge, SM-935F)
[Magisk] shoey63:
And another one

"He who goes to bed with stiff problem wakes up with solution in hand"
[Magisk] Gosbo:
Thanks i will try this when i have a bit of time ;) Do you know how to update it?

I don't seed a flashable uninstaller but i think i can remove it in magisk and reboot then flash version 0.2

all is fine ^^
[Magisk] :
Now that I don't know sorry.

From that shot it appears ready to proccess media. The status would usually show abnormal if the drivers were not installed.

I had an issue once before with soundalive and viper. I disabled soundalive and fixed the conflict.

Perhaps another eq taking fighting for dominance?

The master switch is also off in your shot :)
[Magisk] edyny1:
Where can i find super SU helper? And what does it do?
[Magisk] Captain_Throwback:
You don't have to remove the previous version to update a module....just flash the updated version.
[Magisk] :
http://xdaforums.com/apps/supersu/suhide-t3450396

Look at the bottom of post 1

You want the suhide - rm
[Magisk] darkmage93:
Its off because I kept switching it on and off, adjusting settings ect. with no luck. :(
[Magisk] Ronfallorock:
i can't uninstall the module " [cache] Google assistant", someone have the same problem? :(.
[Magisk] edyny1:
What is the google assistant module for?
[Magisk] Ronfallorock:
It is a module that activates the assistant google. It is available in the downloads section of magisk.
[Magisk] edyny1:
Ok, but what does the assistant do?
[Magisk] Ronfallorock:
the module activates the google pixel assistant
[Magisk] Ninoh-FOX:
Has anyone tried the application "NO DEVICE CHECK" Xposed? It gives green safetynes ​​but does not work pokemon

Enviado desde mi E5603 mediante Tapatalk
[Magisk] :
I kinda figured that :)

Did a quick google search but i found mostly old references to a 3rd party equalizer being the problem. When that happened to me it was soundalive.

Myself I'd clear your cache and check if there is another EQ enabled. Maybe try to and reinstall both the module and app.

I do have a permissive kernel but i was able to run viper on my stock enforcing kernel. So that shouldn't have any effect. I needed the permissive kernel for magiskhide to work in the end. As i couldn't pass safetynet.
[Magisk] requiiiem:
on my Nexus 6, I do not have that "xml" file

:/
[Magisk] edyny1:
Xsetprop not working

Well i guess xsetprop ain't working for me, I'm still failing SafetyNet (i get blue screen). I flashed the zip, the activated it in magisk manager, after reboot ran the shell

Xsetprop ro.boot.flash.locked 1

But nothing

Look at screenshot in terminal and read message i got to see if i did it right.

I also just ran getprop and while i was scrolling i noticed it says selinux enforcing when i have a permissive kernel installed and bootstate (green) see screenshots also
[Magisk] Captain_Throwback:
Again, saying "xsetprop not working" is inaccurate. It's doing exactly what it's supposed to do.

Just because you're not now passing SafetyNet has nothing to do with xsetprop. Something else in your setup must be the issue, especially since the prop you set didn't previously exist. That basically proves that it wasn't the problem in the first place.
[Magisk] Papote3:
I saw a discussion about another file on vendor, something about an audio configuration file... If I find something I'll let you jnow
[Magisk] edyny1:
Ok,

Steps i took was unroot, then flashed magisk v8, in terminal echo "SYSTEMLESS=true" > data/.supersu, then flashed RC1 superSU 2.78, rebooted then installed magiskmanager, went back to recovery and flashed xsetprop zip, rebooted, activated module and rebooted again.
[Magisk] Captain_Throwback:
SuperSU makes SafetyNet fail, so it doesn't matter what else you've done - it'll still fail.
[Magisk] Ninoh-FOX:
This is my getprop, safetynet help green, safety cigital red, pogo device not support. Magisk v8, systemless >> supersu 2.78, suhide 0.55, xposed 86.6, busybox 1.5.

Spoiler content hidden.

Could was the wrong [ro.bootmode]: [unknown]?

Enviado desde mi E5603 mediante Tapatalk
[Magisk] Stillhard:
We're damned, after all

Through fortune and flame, we fall

credit: mcr 😘
[Magisk] zputnyq:
Actually I'm confused, I should report it here or on mixplorer thread since it only happens to mixplorer on my device so far.

I'm having problem with mixplorer + magisk canary (24102). Mixplorer's root permission has been granted but it can't show folders or files inside /data /cache and any folders that require root access however there is no problem when I use magisk (24101) or any previous magisk. Does anyone experience this as well or have any solution ?
[Magisk] pndwal:
Latest debug Canary Magisk:​

Magisk (1a1b346c) (24102)​

Diffs to v24.1​

[MagiskSU] Fix buffer overflow

[MagiskSU] Fix owner managed multiuser superuser settings

[DenyList] Allow targeting processes running as system UID

[Zygisk] Workaround Samsung's "early zygote"

[Zygisk] Improved Zygisk loading mechanism

[App] Fix BusyBox execution test

[App] Improve stub loading mechanism

[App] Improve stub upgrade flow

👍 PW
[Magisk] Frenk 19:
Hello. Can anyone help me find a module to hide apps that detect non-genuine software? Many thanks in advance
[Magisk] zgfg:
With HMA you can hide apps from the other apps

If that is what you are looking for, there were really a tons of posts here sbout - hence please scroll back and read what was discussed eg last days

Or read, and conclude is that what you are looking for
[Magisk] TheEpicFlame:
How do I downgrade Magisk 24.1?

I rooted my phone for the first time recently and used Magisk 24.1 but now I want to downgrade and can't install any other version, all attempts resulting in lots of different errors.
[Magisk] pndwal:
Just remove the apps, they serve no purpose... I recently discovered that if it's not actually software it just won't execute! 😜 PW
[Magisk] zgfg:
You had to fully uninstall Magisk from Magisk app or by flashing uninstall.zip - if you didn't, please consult the Magisk documentation on Magisk GitHub for details

Probably you have some legacy device with TWRP (and who knows how Magisk is already messed up), hence flash the uninstall.zip (again, read the docs to know how/where to obtain the uninstall.zip)

Then install your older version of Magisk (the way you used to do it, through TWRP or by patching and flashing - again, if needed, consult the mentioned Magisk docs)

You would have issues hiding the old Magisk app - how to overcome has already been advised here, specially earlier today in another post
[Magisk] TheEpicFlame:
I cant uninstall it through app and I cant get twrp either. :/
[Magisk] pndwal:
Did app itself update? PW
[Magisk] TheEpicFlame:
Ive tried installing it in Magisk in several versions.
[Magisk] pndwal:
You're still not being clear... Update App or Update Magisk (core/mask) fails? ... Screenshot? PW
[Magisk] J.Michael:
I think you should explain again what you are trying to do, and maybe explain why you are trying to do it.

I don't think I've ever heard anyone say "Magisk 24.1 is the first Magisk I've tried to use, and now I want to downgrade."

More often I have heard "I was happy with an old version of Magisk; I tried upgrading, but I don't like the new version; I'm trying to downgrade, but I'm having a problem."

The ultimate "uninstall" is to reflash the stock firmware.
[Magisk] TheEpicFlame:
I can update the app just fine if thats what youre asking. Its the actual .img that only works in 24.1.