yashsingh1/xdaforums huggingface dataset:
[Magisk] badabing2003:
My answer has not changed :)

Inspect the boot file you generated and see how it differs from the expected patched boot file.

incomplete boot image downloaded

This should be a clue.
[Magisk] pndwal:
Check app prerequisites and see if it can run with Android 7 or earlier... If it can they're not enforcing strongIntegrity...

Test if app can run on any unmodded (stock, locked) device launched with Android 7 or earlier (can be running later stock Android) or any later device known to have broken keymaster implementation (eg. many OnePlus devices)... If it can they're not enforcing strongIntegrity...

Nb. It is conceivable that an app requiring strongIntegrity might not check for this on certain (whitelisted) devices. However if this behaviour did exist the App would really be compromising the strongIntegrity attestation itself since there should be no way to bypass a failing verdict... Implementing such behaviour would allow any device to bypass the verdict simply by spoofing the device properties of any whitelisted device, rendering strongIntegrity really no better than deviceIntegrity...

👀 PW
[Magisk] olik2000:
Moto edge 30 ultra

Android 12

I have magisk alpha 25210 + latest lsposed

I have shamiko and all apps that don't require root added to denylist + google services and store

I use unsf 2.4.0 mod 1.1

I also have hide my applist

snb used to work but stopped after a recent update
[Magisk] Nergal di Cuthah:
Magisk 25210 is flawed, no mods are enabled or can run. Switch to 25209 or stable. Don't forget to roll back your boot.img too.

Usnf mod 1.1 was flawed did not kick in soon enough switch to 2.4.0 mod 1.2

Then try and see if apps still are blocked
[Magisk] zgfg:
He mentioned Magisk Alpha 25210..Not sure do we have active Alpha users who know the up-to-date situation there, bugs and fixes in the recent Alpha releases, etc
[Magisk] Nergal di Cuthah:
Oops i read alpha as canary and forgot that there are forks (poorly named imho) alpha and delta. Figured since this is the general thread they were using the general magisk, at my likely mistake.
[Magisk] ctcx:
Probably you forgot that I did mention that I tried with ALL the imgs: the bad patch, the good one, and even the original unpatched one. All of them gave that result.
[Magisk] badabing2003:
Yes, I didn't realize that, so basically what you're saying you have a flashing issue, no matter what you try to flash, it does not work, even stock?

Then what @pndwal suggested is the most plausible reason.
[Magisk] Elsrougy:
-Device: OnePlus 8 Pro

-Android Version: stock OOS 11

-Other mods: for magisk modules I disabled them all and tried but no luck, also using HMA (in the log it doesn't seem they check tho) and shamiko (tried with & without)

- Magisk version: stable 25200

- USNF: 1.2 (I tried Kdrag0n & Displax mod 1.2

- Deny list: play services, store, Android service library, android setup, device health survices, support component, package installer and a bunch of apps that need root hidden to work. I know I added a lot of unecessary apps to the list but I did that when I got fedup with those apps before

I don't believe they are checking for strong integrity but it seems like there's nothing working with them right now. Worth noting that few months ago they had an update and they were not working with denylist and shamiko fixed the problem. Also from play store info absher supports (android 5.0 and up), while SNB & Nafath supports 8.0 and up
[Magisk] Elsrougy:
From play store info "absher" supports (android 5.0 and up), while "SNB" & "Nafath" supports 8.0 and up

I know it is highly unlikely that they are checking for strong integrity but because I tried alot to make them work with no luck I am starting to think of the extreme cases they may use

I do not have a device running android 7 or earlier to check on them unfortunately but my device is oneplus 8 pro stock OOS11
[Magisk] pndwal:
Praps not a flashing issue... Not sure if flashing was actually tried... I said:

... Sorry, I only saw the reference to temp booting magisk-patched image also, per:

... If by "I tried with ALL the imgs: the bad patch, the good one, and even the original unpatched one. All of them gave that result" you mean with fastboot boot xxx.img then you should try flashing... 😉 PW
[Magisk] dd805bb:
Magisk Alpha is maintained by one of the devs for lsposed and contributes to Magisk Official. The Alpha Canary is the same as the Canary Official, FYI.
[Magisk] ctcx:
With Magisk installed, in order to make banking app work I had to:

enable Zygisk, install universal safetynet fix module, and also enable deny list and add banking app to it (I thought this last one was no longer needed...)

Infamous banking app finally ran and began registration stuff. But the app is unable to scan the needed qr code: the "screen" is just complete black instead of the camera looking for qr code.

Do you think this could be related to Magisk further settings, or is it purely app's fault?

Thanks.

(I read that, supposedly, there were 3rd-party qr code apps which were able to scan the qr code and open it with another installed app, which supposedly could work for cases like this. Do you know something about this?)
[Magisk] zgfg:
I don't understand why you thought that adding banking app to DenyList is not needed - you can read that here in every guide and every answer to sime newbies asking the same every few days (there are really tons of similar posts/answers)

Anyway, don't know if scanning QR code is maybe related to USNF

You could try using Google Lens (available on Playstore)
[Magisk] ctcx:
Google lens, just like all other apps, cannot "send" scanned code to another app.

Anyway, I think I was asking for too much...
[Magisk] J.Michael:
When you try to scan a QR code, and you get a black screen:

Can you tell whether you are using the front camera or the back camera?

Do you have a case that covers the back camera?
[Magisk] pndwal:
This is correct.

This is not. PW
[Magisk] dd805bb:
The Motorola lineageOS guy. All wrong. Do not follow the XDA article and find lineageOS magisk install thread. Sounds like you are patching the wrong .img like the XDA article says. lineageOS you patch the recovery.img they provide for official ones. It's the same process through the app of select file and patch. If you got lineageOS up and running then patching the recovery.img is simple. The article about pulling the boot.img is wrong. lineageOS you don't ever do that. I have a pixel 3 xl and pixel xl both running lineageOS with Magisk. The problems you are experiencing sound like mount points are wrong from installing Magisk wrong. That procedure they have up in their article pertains to using stock procedures of getting a boot.img on a custom ROM. Whoever wrote that is way off.

This here would be closer to what to do for lineageOS. And none of this is really Magisk related. All this can be found in Motorola threads and or lineageOS threads.

https://xdaforums.com/t/guide-magisk-on-lineageos.4371987/
[Magisk] ctcx:
No, nothing of that.

It's just a plain black square completely static as a static image; no signs of slightest movement.

No, no case covering any of both cameras.
[Magisk] dd805bb:
GitHub - CoderTyn/Magisk-Alpha

Contribute to CoderTyn/Magisk-Alpha development by creating an account on GitHub.

github.com

This is the Magsik Alpha. The links on this page link to Magisk Debug latest version. The code hasn't been updated but the links and where they are the same as canary/debug official build. Did you check anything?
[Magisk] pndwal:
That's not a vv repo... That's an outdated copy by some other dev... PW
[Magisk] dd805bb:
And right over your head.. lol. Whoever forked that has now linked to official GitHub Magisk for downloading. The actions, releases and everything has been wiped out and diverted via link to Magisk Debug/canary/beta/official releases. I didn't say it is a copy repo. I said above, which you failed to read, the links go to the official so there basically is no Alpha Magisk. You may download from there but is the official links on that GitHub. Which screenshot shows the Magsik debug app off of there. So it is the same.

Look at the owner of this repo.. says who again??
[Magisk] zgfg:
This is not official Magisk Alpha. To download Magisk Alpha, developped by Magisk Alpha developers, use the Telegram (Alpha is currently closed source and you cannot look at the source files on GitHub)

When we talk here about Magisk Alpha, we refer to the 'real' Alpha from the Telegram group maintained by the Chinese Alpha developers

They have also another, closed TG channel for discussion (invitation link is no more publicly available and discussion is exclusively in Chinese)

As you can see on the screenshot, Alpha 25209 and 25210 hex tags are completely different tags than yours/Magisk Canary tags
[Magisk] dd805bb:
Also there is another Alpha, which is exactly the same too.. The other one just syncs when a canary build is pushed. Hence 100 and something commits behind. So both lead to the same Canary Build 25210.
[Magisk] zgfg:
OMG - it's not worth to waste time on this 'discussion'

Look at the attached screenshot and learn what is the package name for Magisk Alpha:

io.github.vvb2060.magisk

And the latest 25210 Alpha version is.(again different from your Magisk Canary 25210:

d52ea1b0-alpha(25210)

See the post #54950 above, look at the screenshot from Telegram, open that Telegram channel (I cannot put the link to TG here, it would be against the XDA rules) and download the official Magisk Alpha from there

And see also a dedicated Magisk Aloha thread on XDA:

[Discussion] Magisk Alpha (Public Released) fork - @vvb2060

This is the spot for the General Support Discussion of Magisk Alpha "Public Released" fork created by @vvb2060. Disclaimer: This Magisk Alpha fork is not supported by @topjohnwu and is not an official channel for him. Use at your own risk...

xdaforums.com
[Magisk] pndwal:
There are official links, but as @huskydg and others have said, no open source seems to be publicly available now...

You can LOL, "LMFAO" or whatever else you do, but that repo owner is not vvb2060... She links latest source as in a LSPosed repo that seems inaccessible to public:

https://github.com/LSPosed/Magisk/commits/db74d9b41a0f0ef736c8b1cb4583eeee18b34dde

As you say yourself, you links are way behind current Magisk ... vv's GitHub is up to date with JSONs here:

https://github.com/vvb2060/magisk_files/commits/alpha

Sure, she's left JSON pointing to official Canary notes recently (it used to point to her Chinese changelog), but Alpha itself doesn't use Canary channel; only Alpha and Custom are available in app...

👀 PW
[Magisk] dd805bb:
I am going to say ok now to whatever. If you can't access it on GitHub... NVM. Not worth it. Follow the XDA links you posted.. 2 weeks behind via GitHub commits. Which I can see. The shared APK screenshot you posted is from a group not a GitHub project. I would be able to see it. The link actually links to nothing/ 404 not found. Those shared apks are not updated alphas but say they have injection in them. Translate before installing. Because it's shared in a telegram group doesn't mean that it came from a legit source. Know what else happened 2 weeks ago? Alpha on GitHub hasn't updated. Hmm. Coincidental I guess. Alpha XDA to that telegram is way different. No way would I ever grab an APK that can gain root and say it has injection over the official, and don't know them. Wow that ballsy.
[Magisk] zgfg:
As said, Alpha is no more open source

That's the reason why many users here (incl. myself), stopped using Alpha.

Actually, the other reason is that the only support is their closed TG channel only in Chinese (English forbidden)

But once again, MAGISK ALPHA IS A FORK and hence DIFFERENT FROM THE OFFICIAL MAGISK
[Magisk] dd805bb:
GitHub Magisk Alpha( & XDA too) to Telegram Alpha Magisk, different. Got it.

👍🏻
[Magisk] pndwal:
Wrong again...

And just because public can't see code on GitHub (ie not public repo) doesn't mean it's not. GitHub project... Also, the TG channel is vv's! So don't know why you think source may not be legit... 🙄 PW
[Magisk] dd805bb:
Read above. Not even going there. Another member explained why it's not legit. The TG channel, IDK. Closed source. I am going to leave it there. You say a lot of things that don't make sense. Grabbing an APK you can't verify is, well not legit. From what I translated, I wouldn't ever install an APK off there. That is ballsy.
[Magisk] dd805bb:
Post in thread '[Discussion] Magisk Alpha (Public Released) fork - @vvb2060' https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-88296465

So what I originally said is still true. The GitHub Alpha repos all point to official Magisk now. They didn't a week ago before being wiped. I never brought up TG and don't care what is said in a closed Chinese forum nor given out in those groups. I went off links on XDA and what is found on GitHub. The Alpha repos on GitHub now point to Magisk due to it being closed source now. Only real Alpha now is on TG.. The alphas before a week ago were available GitHub but not anymore. You 2 act like this has been this way forever when it literally just changed within the past week. Playing 🥴 and being 🥴 are 2 different things. Just saying. Great way to show both.
[Magisk] zgfg:
Yes. But this is exactly what we were telling you (since we well knew about that thread and post) but you kept arguing that we don't know and that we are wrong:

1) Alpha TG channel is legit, meaning that the channel was opened by the lead developer of the Magisk Alpha group, you see her (yes, she) posts there and the apps you would download there are their legit Alpha releases

2) They do have GitGub repo but it is not open for the public

3) Again, Alpha is a fork and hence different from the official Canary.

Eg Alpha 25210 or 25209 are different from Canary 25210 or 25209 (you 'argued' in two insisting exactly on the opposite, wrong statements) - Alpha has different package name and their version tags are different

Hopefully you sorted out now and we don't need to continue😁
[Magisk] dd805bb:
It's all shared from a private channel you can't even see. And the owner isn't listed.
[Magisk] Homeboy76:
Please help me understand Magisk Alpha. Is this a Magisk Alpha - Public build?
[Magisk] zgfg:
Yes, checksum for app-release.apk is the same as when 25210 downloaded from the TG channel

But only the Readme, JSON for auto-updating and latest apk for download, no sources
[Magisk] pndwal:
I mentioned that, so did @zgfg... Who cares who said it first?...

Last Alpha with published source was July last year AFAIK... Source began to be linked from inaccessible (to public) LSPosed GitHub since Feb this year... That's inaccessible for month's in my book...

FWIW, I never reported you previously despite your allegations (a respected dev here did)... Now I am (first time)... PW
[Magisk] Homeboy76:
Ok.

So, the problem XDA Members are having with using this public build of Magisk Alpha is @vvb2060 or the creator of Magisk Alpha didn't post the source code.

Thanks for the clarification.
[Magisk] pndwal:
You originally said:

This is still NOT true... At best, JSON in vv's Alpha GitHub repo points to official Canary notes, and Alpha does build Canary commits but it adds her experimental ones... always has... And lack of public source doesn't change that; ie. Alpha builds are a very different animal...

For example, recent builds incl latest 25210 include support for experimental (not publicly released) Shamiko v0.6-141. This simply won't run on TJW releases incl. latest Canary ATM... If you want to test early Shamiko you need Alpha...

Another big (and somewhat controversial) difference is that all Alpha builds include (Microsoft based) telemetry... Her pull request for this has been up in TJW Magisk for some time now, but John has never merged this in Canary builds... Yet...

So Alpha is basically Canary with additional (experimental) commits, and there is no published "Alpha Canary" but if there were it would be reasonable to expect it that would contain the unique Alpha commits too...

Many of vv's Alpha commits end up in TJW Magisk, as do commits from Shana's Metagisk and Canyie's Bravo as well as commits developed in other test branches from these Devs (most prolific) and from other forks/Devs also... PW
[Magisk] pndwal:
That's only the original (Chinese) Alpha Discussion thread, now name has changed but a number of members here are in that discussion... Builds aren't shared there however, only in the official Alpha channel...

Anyone can still join if they find the cryptic (musical) entrance link in the official Alpha TG channel... 😁 PW
[Magisk] chazall1:
I have been using this link for current code changes.

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] Nergal di Cuthah:
Thank you, though that link is, of course, in the information thread and peppered all through this discussion thread so nothing new ;)
[Magisk] chazall1:
Thanks its been a while that I read the first page. You are correct.
[Magisk] pndwal:
Users should be aware that official @kdrag0n fix is busted ATM however.... Use this fork:

https://github.com/Displax/safetynet-fix

😜 PW
[Magisk] chazall1:
Thanks I have book marked this info .
[Magisk] ipdev:
For the record. 😉

Any one using the CI builds or personal builds of Magisk.

Personal builds from the main branch.

Today's updates (20230322), fixed the installing and patching issues. :D

Magisk - Commits (master branch) - Link

Cheers. :cowboy:
[Magisk] iwearthebelt:
I am using Magisk Delta, what's your question?
[Magisk] Nergal di Cuthah:
Who is this talking to :(
[Magisk] dd805bb:
https://twitter.com/i/web/status/1492885858634006528

John was not part of that group. Quit spreading lies.

And to go even farther.

Canary= bleeding edge

Beta= almost stable

Official/alpha(term not app=stable

Hence husky using Delta name because Delta would be before Canary. Backwards alphabet like most projects. Idk where you think Alpha would before Canary. Read the GitHub she was using. She was pulling from the main branch and basically re-forking it with a commit or 2 changed from Canary. More than likely small things like package name and update channel. Literally above in John's own post from over a year ago he denounced them using that name. He didn't say anything about him being in it..if he did start it, why use that name and then call them out for using that name? I mean that sounds off. It's a good story though. She is a contributor, or was or whatever she is now. She flipped on being open source with Alpha. That is fact. Shared in a Chinese only TG. I wouldn't trust it. "Confusing."
[Magisk] diehard2013:
my magisk is "d52ea1b0-alpha:MAGISK:R (25210)"

how do I go back to the latest stable version?

thank you.
[Magisk] zgfg:
Who is spreading the lies?

Who ever said here that John is part of the Alpha group?!

If you accuse anybody here that we are spreading lies - then link that post and quote particularly that sentence where it was 'said' that John is part of the Alpha group!!!

Or otherwise please stop spreading the lies (that somebody was saying here that John is part of the Alpha group)

---

And about the lies - it's harsh word but you were the one who stated more than once in your previous posts that Alpha is just a Magisk Canary - wasn't that a 'lie'?

And btw, the Twitter post you attached is well known for many of us here - look into the Magisk general thread for about a year ago, it was posted there by @pndwal
[Magisk] mrjuniork:
Folks, how about taking this to a PM exchange?

This is derailing this thread and you either agree to disagree or try a PM approach.

Thx for understanding.

Cheers,

mrjuniork
[Magisk] J.Michael:
If Magisk is working, get the APK of the version you want, change the name of the file so it ends in ".zip", and use the Magisk manager app to install it as if it were a module.
[Magisk] diehard2013:
can I flash/install the zip in twrp?
[Magisk] zgfg:
That old method is still valid if the appropriate TWRP (more generally, a custom recovery, it could be OrangeFox, SHRP, etc) exists for the particular phone and ROM

However, there are phones for whom no custom recovery was ported

Or worse, there is a custom recovery (like TWRP) but it does not support storage encryption, etc

For those reasons, and to avoid reports being wrongly addressed to Magisk: "I flashed Magisk through TWRP but it did not install properly" or similar - John does not recommend flashing Magisk through TWRP and instead he recommends the patch and flash method

---

Hence to put it simple - if you know that on your same phone, with the same TWRP and the same ROM you previously and successfully used TWRP to flash Magisk, then no reason it should not work properly again

But if you upgraded the ROM, particularly the Android version, then there is a chance that your old TWRP may not work properly anymore

Hence it depends (there is no definite answer Yes or No). You should know for your phone/ROM/TWRP or you should try
[Magisk] pndwal:
That should work for 25.2, but may not work properly going forward... Due to recent refactoring you'd only get limited Magisk from 25207, and, depending on fixes it may still not work w/ 25211...

Flashing .zip as module from Magisk App is better because this (and issues others mention above) don't exist when boot image is patched with system booted...

Of course there are other way to bypass version checking/downgrade prevention but this is the simplest method I've seen...

Further, when downgrading especially, it can be necessary to wipe Magisk configuration to avoid issues with changes in magisk.db or Magisk directories made for newer builds... Neglecting this may cause confusing issues...

You can simply delete /data/adb/magisk.db and contents of /data/adb/magisk (this leaves modules) after flashing the downgrade.zip (can be before rebooting) and these configuration files/directories will be rebuilt clean on reboot... 👍 PW
[Magisk] Matteo_666:
That didnt work for me. I installed stable as module, cleared directory and magisk.db and now im at version 25200 App and 2510 magisk and though systemless Module showed Up finally, adaway refuses His Job...
[Magisk] pndwal:
Do you mean 25.1 Magisk?... So you used 25.1 package for.zip... anyway, you can simply take Direct Install from current 25.2 App to get 25.2 Magisk since you no longer need downgrade prevention bypass...

Edit: If you mean 25210 Magisk you should ensure you download and use 25.2 package (click v25.2 in Magisk GitHub main page) for .zip installation as module to downgrade Magisk (core binaries running) to last Stable release... PW
[Magisk] Nergal di Cuthah:
I believe you mean 25210 which is broken and loads no modules including systemless hosts, roll your boot back to 25209 or stable
[Magisk] Vincent_40:
Pixel 7Pro stable march SP.

Some modules didn't work properly with Magisk stable 25.210, but work on 25.209 (V4A, Lsposed, PLE,....).

It seems last stable broke something.
[Magisk] zgfg:
Good morning - after about three weeks😁
[Magisk] Vincent_40:
🤣

I totally forgot to come and see on XDA if the problem was known. It is ^^😁😁
[Magisk] kullurumanoj:
Can someone please help me in hiding the root for Yes bank app. I was able to hide the root from all the banking apps but no luck with the yes bank after recent update. I have hidden it from denylist in magisk added to hide my list, also enabled it with in lsposed app hide my list app. All the other apps are working fine except this. Is there a way to find which app is the reason for the root detection. CTS profile, playstore is certified too.

YES BANK - Apps on Google Play

YES Mobile 2.0 is completely new and revamped mobile banking application.

play.google.com