Magisk General Support / Discussion

[zgfg]

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?)

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)

 

[ctcx]

Google lens, just like all other apps, cannot "send" scanned code to another app.

Anyway, I think I was asking for too much...

 

[J.Michael]

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?)

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?

 

[pndwal]

Magisk Alpha is maintained by one of the devs for lsposed and contributes to Magisk Official.

This is correct.

The Alpha Canary is the same as the Canary Official, FYI.

This is not. PW

 

[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.

[GUIDE] Magisk on LineageOS

I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently...

forum.xda-developers.com

 

[ctcx]

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?

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.

 

[dd805bb]

This is correct.

This is not. PW

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?

 

[pndwal]

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?
View attachment 5868811

That's not a vv repo... That's an outdated copy by some other dev... PW

 

[dd805bb]

That's not a vv repo... That's an outdated copy by some other dev... PW

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??

 

[zgfg]

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??

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

 

[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.

 

[zgfg]

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.

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...

forum.xda-developers.com

 

[pndwal]

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??

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

 

[dd805bb]

OMG - it's not worth to waste time on this 'discussion'

Don't you know that Magisk Alpha installs with the different package name:
io.github.vvb2060.magisk

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:
[URL https://forum.xda-developers.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845

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.

 

[zgfg]

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.

View attachment 5868853

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

 

[dd805bb]

GitHub Magisk Alpha( & XDA too) to Telegram Alpha Magisk, different. Got it.

 

[pndwal]

GitHub Magisk Alpha( & XDA too) to Telegram Alpha Magisk, different. Got it.

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

 

[dd805bb]

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

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.

 

[dd805bb]

Post in thread '[Discussion] Magisk Alpha (Public Released) fork - @vvb2060' https://forum.xda-developers.com/t/...c-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.

 

[zgfg]

Post in thread '[Discussion] Magisk Alpha (Public Released) fork - @vvb2060' https://forum.xda-developers.com/t/...c-released-fork-vvb2060.4424845/post-88296465

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