yashsingh1/xdaforums huggingface dataset:
[Magisk] amk316:
for anyone wants to know that "alrajhi capital" app detect zygisk

i used zygisk next and it worked!!!!
[Magisk] Spartacus500:
So Magisk 27.0 stable with zygisk enabled can't handle it 😔
[Magisk] amk316:
it seems using zygisk next and hiding magisk app to random name don't work together!!!!

i had to delete magisk app for now to make some apps work "don't want to use HMA"
[Magisk] pndwal:
b04e1394-alpha 27001

内部测试

修复部分设备无法连接WiFi

大幅减少sepolicy规则数量

--------

b04e1394-alpha 27001

Internal Test

Fixed the problem that some devices cannot connect to WiFi

Significantly reduce the number of sepolicy rules

Looks like a test fix for this (Android 10 w/ custom kernel?) Issue: WiFi not working due to new sepolicy flag confirmed core regression #7764 opened 2 weeks ago by a6680

👀 PW
[Magisk] rodken:
Version 4d5510be-alpha (27001)

Feb 23, 2024 at 00:52

12.48 MB

Major behavior change: magiskd internal mount points are uninstalled after they are no longer in use.

New feature: Enhanced safe mode. If you can't boot your computer normally twice in a row, Magisk will automatically enter safe mode the third time. Safe mode disables all functions, disables all modules, and only Magisk applications can use su. For PC debugging please use adb shell 'PATH=$PATH:/debug_ramdisk su'.

Magisk (4d5510be-alpha)

[App] Delete backup file after restore boot image.

[General] Don't unlock device block automatically

[App] Do not actively request permissions

[General] Retain ROOTOVL temp files.

[App] Check for and download updates via appcenter.

[App] Add telemetry https://t.me/s/magiskalpha/473

[General] Make blocklist work when zygisk is not enabled

[General] Remove addon.d support

[General] Remove /system/etc/hosts writable exception, please modify /data/adb/modules/hosts/system/etc/hosts

[MagiskSU] Support for removing privileges.

[General] Support for user-restricted root privileges [applications using older libsu versions will be incorrectly recognized as rootless].

[General] Automatically copy files after initial installation

[App] Add alternate DoH

[MagiskInit] Avoid patching init files for 2SI devices.

[General] Remove the image, it is no longer needed for atomic mounts

[General] magisk tmpfs path fixed, magic mount no longer required, make it optional

[General] Enhanced safe mode

[App] Reboot menu can be set to boot into magisk safe mode next time

[Denylist] Enhance uid tracking, automatically remove uninstalled apps from block list. Improve app startup performance, zygisk no longer scan app list.

[General] Improve app startup performance, zygisk no longer checks the signature of repackaged magisk apps at each app startup.

[MagiskPolicy] Fix adb can't connect to lldb server.

[MagiskPolicy] drastically reduce the number of rules

[MagiskPolicy] Fix some devices not connecting to WiFi

[General] Bypass kernel hiding su files in some custom ROMs

[General] Workaround for kernels that don't broadcast mounted peer group events.
[Magisk] manan001:
Hi Dev, @rodken it seems after yesterdays alpha release after update alpha magisk cannot hide. I can see unhide and hide magisk app. Clicking on Hide magisk app it asks for downlaod full installation. Please guide if i am doing any issues? Using OnePlus 11 device.
[Magisk] pndwal:
It's common to have hiding/unhiding issues with any Magisk... Often need to uninstall all hidden iterations to fix as they hadn't automatically been removed, but that may not be your problem...

The Chinese test group conversation is a bit hard to follow up but 4d5510be-alpha (27001) may have been withdrawn already... Seems it was aimed at testing some selinux issue, but testers may be reverting to b04e1394-alpha (27001)... Maybe you understand/participate in Chinese?

Of course 2c6adbc6-alpha (27000) was the last to be publicly released... Seems that may be for a reason. PW
[Magisk] xcl1pse:
for now use older release

Edit: new patches has been released, try redownload and flash again, the version still unchanged tho
[Magisk] xcl1pse:
it pullout from appcenter because magisk can't hide itself (if magisk was flash from twrp/custom recovery, it will be fine) + need more testing for sepolicy + more testing from magisk app itself
[Magisk] pndwal:
Mmm... 4d5510be-alpha (27001) just got pushed to public channel...

🤷 PW
[Magisk] HippoMan:
Luckily, I'm running on one of the few post-A10 devices on which nandroid backup/restore is available (a Nothing 2 device on which OrangeFox is functional). I therefore will take a full nandroid backup and then try the 4d5510be-alpha release.

I'll report my findings a little later.
[Magisk] HippoMan:
After upgrading from 27000 to this 27001 version, everything seems to be working OK for me.

I simply updated via the UPDATE command offered in Magisk itself, and I then chose Direct Install.

I didn't have to un-hide Magisk nor disable any modules.

Magisk remains hidden, modules are still all functional, root-requesting apps that are not in my DenyList are still properly running as root and not crippled, and apps in my DenyList are still not detecting root.

I'm running stock A13, and as previously mentioned, it's on a Nothing 2 device.
[Magisk] dknight178:
Hi all. I am currently using kitsune but am planning to shift to alpha.

Can I just install alpha over kitsune 26.4? Or do I need to uninstall kitsune manager, install the alpha manager then fastboot flash an inti_boot.img?

Will my magisk hide list rollover to alpha's denylist or do I have to set them again?

Will lsposed/HMA + shamiko + PIF (chiteroman) work with magisk alpha?

Will alpha + shamiko + HMA work against:

- halifax: https://play.google.com/store/apps/details?id=com.grppl.android.shell.halifax

- barclays: https://play.google.com/store/apps/details?id=com.barclays.android.barclaysmobilebanking

- citibank: https://play.google.com/store/apps/details?id=com.citibank.CitibankPH

- bpi: https://play.google.com/store/apps/details?id=com.bpi.ng.app

Thank you!
[Magisk] sawdoctor:
Not sure how well HMA will work with shamiko but switching magisk versions is pretty straightforward if you follow these instructions/guidelines

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

xdaforums.com

Edit

I have 2 troublesome apps MBNA and Lloyds Bank. No version of Magisk/shamiko hides root anymore and they refuse to open with HMA or any xposed hook.

Ksu or Apatch might work but i just created a second user on my pixel and use that for my banking apps
[Magisk] dknight178:
Thank you. Ironically, kitsune 26.4 + HMA + shamiko 0.75 works with Halifax/MBNA for me. So alpha doesn't work well with HMA?
[Magisk] sawdoctor:
For me if i try HMA with MBNA the app just FC as soon as i try and enter my login details.

HMA is by the same Dev as kitsune so compatibility is probably better but really don't know.

I had everything working great until MBNA and Lloyds forced an update on me. Tried canary, alpha and kitsune but still root was detected
[Magisk] fizzingbees:
i am on magisk v23 official and i installed kitsune mask( magisk delta ) v26.4 by following the original instructions fo installing kitsune mask apk ,granting it root and then removing original magisk app. after i rebooted i was send to bootloop and even my twrp got corrupted, had to reflash twrp,reflash magisk v23 orginal. This happened on samsung note 20 ultra ( snapdragon hongkong varient) on android 10.

On Xiaomi redmi note 10 pro( sweet global and android 11), i just flashed the kitsune mask zip from original magisk>install from storage >rebooted>open kitsune mask and let it do its thing>reboot again and then removed og magisk.

Now i am wary of playing with not 20 ultra as its wasted my whole week trying to recover it from bootloop

Tell me whether this data/adb/magisk directory deletion and data/adb/magisk.db deletion prevent this as i flash kitsune mask zip from withint magisk app?
[Magisk] zgfg:
If deleting magisk binaries and database, then specially delete modules (some of them could cause the bootloop)

Btw, Kitsune keeps its binaries on /adb/unencrypt/MAGISKBIN, /data/adb/magisk is just a linked folder

However, cannot speculate about your bootloop, causes and solving
[Magisk] jimger:
Do we have any idea if developers are actually planning to un-archive magisk alpha and lsposed and shamiko or it is final death?

Except Kitsune is there any other magisk fork focused mainly to magisk hide?
[Magisk] xcl1pse:
magisk alpha is still maintained
[Magisk] jimger:
I thought the group archived the github? I do have them on telegram but no idea as everything is Chinese...

BTW isn't the same group that has lsposed and shamiko?

Do u know lsposed maintained alternatives?
[Magisk] xcl1pse:
only vv maintained magisk alpha, so it will continue depends on vv, not LSPosed group. For LSPosed, I don't know what you really want, LSPosed is still working, unless you're on A15 or QPR latest. There's only one usefull LSPosed mod for that (other are garbage) or if you want edxp style, there's Dreamland
[Magisk] jimger:
It is working for now for me but no further updates... So I assume will come to issues sooner or later. Thanks much for the info though. No I am A14. I am fine for now. But for example one bank app detects root so potentially a magisk or lsposed update would solve the issue. Now may not be possible...
[Magisk] xcl1pse:
Then just stay. Even rovo's xposed still working lmao

80% detection are from user fault, including the one saying app detecting LSPosed
[Magisk] jimger:
Not sure, what is preventing the app. Also let's say I have a gazillion other banking apps all hidden the same way, so I assume they use another detection method...
[Magisk] sawdoctor:
Hasn't alpha always been closed source? Hence no download links on xda
[Magisk] jimger:
That's true. But I think it is the same group as lsposed etc. Time will tell I guess...
[Magisk] sawdoctor:
the lsposed and shamiko releases have stopped because of arguments with another developer/team.
[Magisk] shoey63:
And hell hath no fury like a woman scorned.

(They are all young ladies)
[Magisk] rodken:
[Off-topic] I suppose that someone felt betrayed and as a result there will be consequences.
[Magisk] Homeboy76:
alpha changelog

First, you posted several translated

alpha changelogs

on the Magisk General Support / Discussion thread, until, March 2022. I do not remember you posting the name of the TG Group with the changelogs. My guess is the name of the group was not as important as the content of the group. Further, I can not remember members sharing their opinions of alpha when you were posting the

alpha changelog

.

Second, @martyfender and I posted alpha changelogs consecutively (Post 51,422 and 51,423). After those post @Stillhard's Post 51,434 requested a

new thread

be made to post Magisk Alpha information because it is not Magisk. Stillhard, made reference to an extracted portion of @zgfg Post 14 in the [Discussion] Magisk - The Age of Zygisk thread.

Third, I complied with Stillhard's request fo a new thread for Magisk alpha information.
[Magisk] pndwal:
Not sure of your point... I cited sources till one mod quoted an obscure rule claiming we can quote but not give links for any social media sites... Later @Didgeridoohan stated that such links "are perfectly fine", but a third mod edited posts stating that links to TG threads as a file source are unacceptable on XDA... I've tried to comply with XDA's confusing 'rule' interpretations...

I was aware of vv's alpha and lite Magisk builds, as well as earlier MTK builds (to test / fix compatibility with MediaTek devices), but began using Alpha regularly and posted to that effect during John's period of 'silent' development from May to August last year (during his internal review at Google) as alpha was still getting regular updates / fixes... For me it was a temporary replacement for regular Canary updates. I did play with her Magisk Lite (implemented whitelist for MagiskHide to effectively hide Isolated process leaks from bank apps, but was highly experimental / broke many modules) also.

I posted findings / changelings and soon others began installing these builds too, incl. @zgfg who reported alot about Lite. More started using them after John's 'Magisk is back!' announcement in August when no Canary builds were forthcoming; he took till late October to release the first 'Zygisk' build, but many of us were testing both his commits and some fixes from vv and others in Alpha well before first Zy-Canary.

At that time it seems it was easier to join the Alpha discussion group too... Later, members needed to be manually accepted by admin.

I know he said that, but of course it's Magisk! ... It's a fork of magisk... That's a bit like saying unofficial TWRP is not TWRP!

Not sure @zgfg was promoting a 'don't discuss alpha' policy though... You'll need to ask him... I think he simply meant that there's currently little advantage using it over regular TJW builds...

Personally, I disagree with fragmenting Magisk General Support / Discussion as it's all inter-related, and the same fixes / discussion are needed whether on Stable, Beta, Canary, Alpha, other... This will necessarily lead / has led to much unnecessary duplication / repetition / users missing comments because they were posted in an unfamiliar thread...

Actually, I didn't fully support @ipdev with his 'Age of Zygisk' thread either; I suggested a zygisk-era related wiki/knowledge base along the lines of @Didgeridoohan's (updatable) and keeping general discussion in one place...

To me, tolerant (within reason) mods / staff / even OPs (like @Didgeridoohan) are a plus, and communication / reason are also essential in these forums.

-------------​

All that aside, what I've been repeating is that your edited post still says:

I said "Why? ... Surely if that changes you'll be needing to change the name of this thread to match! 😛"...

So, are you referring to John's request for a name change for vv's Magisk Alpha fork?... Or, in fact, to the name of Canyie's 'Alpha Discussion' group we've been monitoring / discussing here? 🤔 😬 PW
[Magisk] zgfg:
I didn't test and post only about Magisk Lite (for those who don't know, it was also from vvb2060) but also about Magisk Alpha and Magisk Custom

Since there was no other threads, we all posted to the General Magisk thread - but some users started to complain, they were bored about and they were accepting only the old, official Magisk Stable v23

It was all at the times while TJW did not release yet his pre-v24 Canary 2301x, specially not the Canary or Stable 24xxx yet

Magisk Custom and Alpha provided us a platform to test and learn about the upcoming changes from Magisk v24 - those of us who did experiment in advance (and gradually as changes were not introduced all at once), we were immediately ready for Canary and Stable v24 when they came

The others, who opposed till the last moment, they got shocked with a lot of changes in Magisk v24, and only then started to ask why this, that, etc (if they followed our previous discussions their learning curve would be easier)

Again, some users were unhappy that everything was burned down in the mastodon general Magisk thread and ipdev created a new thread (spending time to write nice OP instructions) for Magisk v24.

Nevertheless, newbies still come, do not spend a minute to read those OP posts and ask again the same things for hundredth time

Btw, I got bored by answering to the newbies questions (even reading them). Who is not able to do his homework and read/learn what is available and repeated tens of times - his own problem

Nevertheless, now we have Magisk v24, when there are some news in the code Canary is always relatively promptly released and I personally don't see a reason to monitor, install/test, etc the Magisk Alpha (myself).

The other one, Magisk Custom, was closed by a developer anyway
[Magisk] Homeboy76:
1. Did you remember the words - I do not remember... - in my post. They are there because I couldn't say you did or did not say something.

2. You articulate your opinions very well, and I respect that. The thing I like most about XDA is the fact that all members can express their opinion.

3. IMHO the name of the of the alpha TG Group

is not as important as the product (Magisk alpha) of the group. The name of this thread will not be changed to match the name of the alpha thread.
[Magisk] HippoMan:
An advantage of having the separate Zygisk thread is that people who are first starting to use Magisk won't have to search through 50,000-plus messages in order to figure out how to get started with the latest Zygisk. That Zygisk thread has the info that new users need within the first 8-10 messages.

However, I'm on the fence concerning the need for this current thread needing to be separated out. I see plusses and minuses.
[Magisk] pndwal:
Sigh... But we're not concerned with matching names with some Alpha discussion thread by Canyie or anyone else!

As I keep repeating, you said "Discussions about the name of the Magisk alpha fork by @vvb2060 , are kinda Off Topic... (Post #33 still says that!)

Thats why I keep asking if you meant John's request to have that name changed...

Because, so far, there hasn't been any discussion of the name of the Magisk alpha fork by @vvb2060 here at all!... Unless I do not remember... PW
[Magisk] pndwal:
Yup, and I was privy to some of the content before it went up; as I mentioned, a new wiki / knowledgebase could have served the same purpose without duplicating the discussion... But it still works!

mmm... I'm hoping the plusses come... PW
[Magisk] Lughnasadh:
I fully supported ipdev starting a new thread. The general Magisk thread was getting convoluted and fragmented with all the discussions about the Alpha fork, in my opinion. I believe that is why he specifically made a new thread (The Age of Zygisk) and kindly asked people in the OP of that thread to "Please try to restrain from discussing alternative (unofficial) Magisk builds that include changes that were removed or can not be included in the official Magisk builds. 🙃". Pretty sure he was referring to Alpha and any other forks (as evidenced by only referencing John's Magisk in the OP).

Anyway....
[Magisk] pndwal:
Was getting?! 😜

Well thread was HUGE well before that!...

@ipdev's wishes for 'Age of Zygisk' thread aside, you can judge for yourselves whether Alpha / vv complies with John's wish that "people won't fork Magisk just to add MagiskHide" (6 October 2021).

The official position is:

Jan 15.

😛 PW
[Magisk] Lughnasadh:
And got worse and more convoluted with all the talk of Alpha 😜

Don't think you can just throw ipdev's wishes aside, if indeed that's what his intent is (I could be totally wrong though). But if you feel so strongly about it, then by all means go into that thread and "flood" it with Alpha discussions. It didn't stop you before so what's stopping you now? I'm sure it will all be just fine... 🙃
[Magisk] pndwal:
🤔 ... You draw a long bow. 😟

I have the utmost respect for @ipdev... And I was the one who announced his new thread in TJW's thread, having discussed some of it's OP content with him earlier...

By the 'his wishes (quite reasonable ones for his thread) aside' remark, I was simply focussing on John's general wishes regarding "(unofficial) Magisk builds that include changes that were removed or can not be included in the official Magisk builds" as I think the cited comment implied / targeted builds perpetuating MagiskHide, SafetyNet Check etc against the wishes of John that I referenced...

I applauded @ipdev's efforts and that hasn't changed, but I do feel strongly that fragmenting the General Magisk Discussion is not helping... It may potentially make things very difficult to follow for contributors and searchers alike...

And re. convoluted thread, my point is that it's burgeoning nature is already a given; it's not like creating more threads will fix the original discussion thread... And it works fine for discussion purposes anyway...

I think I do more than most tho contribute to Magisk General Support & Discussion... Bit of a leap / insult to suggest I'd want to sabotage the efforts of others don't you think? 🙁 ...

Incidentally, @ipdev contributed much to the original early Zygisk / alpha discussion himself... (Sorry for more OT folks...) PW
[Magisk] Homeboy76:
You said "But we're not concerned with matching names with some Alpha discussion thread by Canyie or anyone else!" What was the post below about?

You're right post 33 needs changing, and I changed it.
[Magisk] ipdev:
Hi all. :D

I appreciate all the mentions but..

This thread is getting overrun by OT. 🙃

Sorry to add to the OT and I apologize to the moderator who will clean this thread.

You can give a link to a thread or a specific post across-threads.

If a member asks a question in the wrong thread, you can answer it in a different thread by mentioning them or quoting the post in the more appropriate thread. ;)

All of us share the responsibility to to help keep the forums clean.

The moderators have enough to do. 🙃

---

Thanks to Homeboy76 for staring this thread. (y)

Since the start of this thread, all posts about Magisk Alpha should be in (and/or answered in) this thread.

---

As for the Magisk General Discussion Thread.

The original Magisk General Discussion thread should have been closed years ago.

Some members love to tell others to search.

Search for root and you get an overwhelming amount or returns.

Is Post # 5,538 - Link relevant to anyone now?​

Each time there was a major change in Magisk..

- The current general discussion thread should have been closed.

- A new general discussion thread opened.

Cheers all. :cowboy:
[Magisk] pndwal:
It was about what I said!; If the name of the Alpha fork by vvb2060 does change, "you'll be needing to change the name of this thread to match! 😛"... 😛😛😛 PW
[Magisk] Lughnasadh:
Bit of a leap/insult to suggest that I was suggesting that you want to sabotage the efforts of others, don't you think? I merely indicated that you posted a lot about Alpha in the Age of Zygisk thread, which you did. I never once suggested, or even believed, that you were intentionally, or even unintentionally, trying to sabotage the efforts of others. That's just an absolutely ridiculous assertion. 🫤

Anyway, enough of this. From now on I'll stay on topic and apologies to the OP and moderators.
[Magisk] Homeboy76:
@Lughnasadh @HippoMan @zgfg @pndwal

I enjoyed reading Post 43, 46-51: They ,thoroughly, explained the history of the Magisk threads and the reasons you do/do not agree with them existing. Thank you for sharing this information.

Now, I'll add my 2¢ the Magisk General Support & Discussion is to big, searching it for specific information is 'impossible' i.e. I tried to search Magick Canary 24301. I got 20 pages and most of the post I read did not contain any Magisk Canary information. 🙁
[Magisk] pndwal:
I think I mentioned Alpha discussion thread there as source for Shamiko (before we had GitHub link)... Don't think I ever "posted a lot about Alpha" in that thread... 😕

I said:

So what does this mean?:

... So stop with the disparaging / false assertions. 🙁 PW
[Magisk] pndwal:
Agreed... But it works for general discussion, and especially when members are willing to link pertinent info... And @ipdev's OP posts are certainly a valuable resource / database... PW
[Magisk] Homeboy76:
:oops: So, the names of the Blogs/Threads you posted and were discussing were Off Topic.