[Discussion] Magisk - The Age of Zygisk.

[koberulz]

Why do you want Zygisk?

Did you look in the working Magisk manager app to see if there is a setting "enable Zygisk"?

I don't know what Zygisk is.

Okay, seems it's a setting, and I need it for the new Magisk Hide equivalent, so...I need it.

Now...there was another thing to do with SafetyNet, right? I HAVE TOO MANY OPEN TABS, ugh. And I need to hide Magisk again, right?

 

[pndwal]

It's working more than it was before. Although the hidden app icon is still there and clicking on it still gets me a "this app has stopped working" error. Ugh.

Yup... My remark was just for clarity; App is only a Magisk UI / 'dashboard', not Magisk... Magisk itself still isn't working... PW

 

[koberulz]

Yup... My remark was just for clarity; App is only a Magisk UI / 'dashboard', not Magisk... Magisk itself still isn't working... PW

In what way is it not working? I have root, and everything seems as it should:

 

[pndwal]

I don't know what Zygisk is.

Okay, seems it's a setting, and I need it for the new Magisk Hide equivalent, so...I need it.

Now...there was another thing to do with SafetyNet, right? I HAVE TOO MANY OPEN TABS, ugh. And I need to hide Magisk again, right?

Zygisk is extra (hooking) functionality for Magisk... You'll only have it once Magisk is actually installed and recognised by the Magisk App (please don't confuse the two)...

In App you need to see a version under Magisk Installed, not N/A, first... PW

Edit: Yes! Magisk is good now!

 

[koberulz]

Well my first takeaway is that Android 12 was clearly designed for blind people, JFC. Is there any way to shrink the UI down? I have basically nothing in my quick settings now, the pad to enter my PIN on is bloody huge, the clock occupies the entire lock screen...

 

[zgfg]

In what way is it not working? I have root, and everything seems as it should:
View attachment 5869541

To enable Zygisk, go to the Settings and enable - eg, you will need for USNF

About the Zygisk is covered in the OP posts

 

[J.Michael]

Well my first takeaway is that Android 12 was clearly designed for blind people, JFC. Is there any way to shrink the UI down? I have basically nothing in my quick settings now, the pad to enter my PIN on is bloody huge, the clock occupies the entire lock screen...

Check Android settings -> Accessibility -- maybe there's a "zoom" option.

Failing that, take things one at a time. Look at the clock on the lock screen, maybe there were several widgets to choose from and you chose (or had chosen for you) a really, really, big one.

 

[J.Michael]

I don't know what Zygisk is.

Okay, seems it's a setting, and I need it for the new Magisk Hide equivalent, so...I need it.

Now...there was another thing to do with SafetyNet, right? I HAVE TOO MANY OPEN TABS, ugh. And I need to hide Magisk again, right?

I would suggest *not* hiding Magisk until you need to. Never mind whether you used to. Try the suggestions about USNF and HMA. Which really means, until there is an app that refuses to run, don't bother with anything.

 

[exis_tenz]

Well my first takeaway is that Android 12 was clearly designed for blind people, JFC. Is there any way to shrink the UI down? I have basically nothing in my quick settings now, the pad to enter my PIN on is bloody huge, the clock occupies the entire lock screen...

For that I use AOSP Mods, which is a combined Magisk/LSPosed module. It gives you at least the option to have a row of 4 shortcuts in your panel instead of 2. Still not perfect, because 6 or 7 is way better. I totally do not understand why anyone in Silicon Valley thought this was an update. To make QUICK TILES harder to reach. At least they could scratch the word QUICK now. TILES it is. Large tiles. Huge tiles. Ugly tiles. But tiles.

There IS also a forked and non-offical version of GravityBox for A12. Many things do not work though! And before playing around install a bootloop-protector in Magisk! I use GravityBox PURELY to re-map my onscreen buttons (double tap to sleep, for example).

 

[Fishawy]

For that I use AOSP Mods, which is a combined Magisk/LSPosed module. It gives you at least the option to have a row of 4 shortcuts in your panel instead of 2. Still not perfect, because 6 or 7 is way better. I totally do not understand why anyone in Silicon Valley thought this was an update. To make QUICK TILES harder to reach. At least they could scratch the word QUICK now. TILES it is. Large tiles. Huge tiles. Ugly tiles. But tiles.

There IS also a forked and non-offical version of GravityBox for A12. Many things do not work though! And before playing around install a bootloop-protector in Magisk! I use GravityBox PURELY to re-map my onscreen buttons (double tap to sleep, for example).

Does this GravityBox fork provide an option for more than 4 tiles in QS? And do they work on A13?

 

[exis_tenz]

Does this GravityBox fork provide an option for more than 4 tiles in QS? And do they work on A13?

Nope, it's in there, but malfunctions (does nothing). What DOES work is "AOSP Mods", which can show up to 4 columns, but you can set the first swipe down to show 2 rows. That makes 8 in total. By pulling down, you can adjust another 8.

 

[Fishawy]

Nope, it's in there, but malfunctions (does nothing). What DOES work is "AOSP Mods", which can show up to 4 columns, but you can set the first swipe down to show 2 rows. That makes 8 in total. By pulling down, you can adjust another 8.

Thanks, I'm already using AOSP Mods with the 8 tiles in QQS, but I was hoping for something that gives more than 8 (coming from OnePlus).

 

[M3m3nt01]

Hey I'm currently having a issue with Google wallet and I'm trying to figure out if it's a linage os issue, a magisk issue, or a Google issue rn.

Everything works pretty much, I pass safteynet check, Google certification is good, I can download stuff like Netflix and for the most part Google wallet works.

I'm using Android 12 on lineage os 19.1 with a oneplus5t. The problem I'm having is the wallet tile in the quick access menu and the lock screen wallet toggle in the settings menu are both grayed out and none functional. It's really a minor issue but are features I want to take advantage of.

If anyone has any idea about this issue, or at the very least know where I should be pointed at, it would be a lot of help

View attachment 5759701View attachment 5759703

Have you come accross a solution or a fix for this problem?

 

[JAIMASS]

You can bypass "bootloader unlocked" on mediatek devices just following this:
1. Unlock bootloader.
2. Backup the partition seccfg.
3. Relock bootloader (or just erase the partition seccfg).
4. Backup anything you want to backup and then, Format data.
5. Flash the partition seccfg with unlocked bootloader.
Done, now your device is unlocked but the system thinks it is locked.
(Yes, I did it.)

Hello Bro Am Having Mi 11x momo is detecting bootloader unlocked. Could you please elaborate the steps clearly. My device is snapdragon. How to backup the partition seccfg. Please tell the methods bro . As am I new to this

 

[JAIMASS]

You can bypass "bootloader unlocked" on mediatek devices just following this:
1. Unlock bootloader.
2. Backup the partition seccfg.
3. Relock bootloader (or just erase the partition seccfg).
4. Backup anything you want to backup and then, Format data.
5. Flash the partition seccfg with unlocked bootloader.
Done, now your device is unlocked but the system thinks it is locked.
(Yes, I did it.)

Bro also am having OnePlus 9R is this possible in OnePlus 9R. Because in momo it detects TEE broken. But I can bypass bootloader unlocked by safety net fix. How to bypass TEE broken. Is your method works for OnePlus snapdragon device. Could tell the method

 

[zgfg]

Hello Bro Am Having Mi 11x momo is detecting bootloader unlocked. Could you please elaborate the steps clearly. My device is snapdragon. How to backup the partition seccfg. Please tell the methods bro . As am I new to this

He said that the method works for Mediatek - if you have Snapdragon, it's not Mediatek...

 

[joegreat]

On my OnePlus 7T the manual downloaded Magisk 26.0 app installation/opening fails with "...was denied Superuser rights" - installed app version stays on version 25.2 (with recently updated SafteyNet Fix).

Any idea what the version 26.0 app needs/changed to be installed?

 

[Homeboy76]

On my OnePlus 7T the manual downloaded Magisk 26.0 app installation/opening fails with "...was denied Superuser rights" - installed app version stays on version 25.2 (with recently updated SafteyNet Fix).

Any idea what the version 26.0 app needs/changed to be installed?

I don't have a OnePlus T7, but if you have Magisk 25.2 installed on it. Open the Magisk Manager. Tap the settings Icon and set the channel to Canary if you want to install Magisk 26001 or set it to Beta if you want to install Magisk 26 Beta. When the update arrived Tap Update then Direct install.

 

[pndwal]

On my OnePlus 7T the manual downloaded Magisk 26.0 app installation/opening fails with "...was denied Superuser rights" - installed app version stays on version 25.2 (with recently updated SafteyNet Fix).

Any idea what the version 26.0 app needs/changed to be installed?

Very likely you still have a previous hidden Magisk App (stub app) installed... Uninstall the older App and conflict with 26.0 should be gone...

This can occur as hidden stub has different signing keys etc but dual apps will still compete for superuser control of Magisk... The App (UI) shouldn't ask for superuser permission anyway; it's usually a sign you have competing app iterations. PW

 

[ashish1989]

I accidentally installed v26 beta, how can I roll back to v25.2 stable?