yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Unfortunately, I had to disable all my three audio modules: AML, V4A and certain 320 Kbps Bitrate increase (specific to my Mi 9T)

By enabling any of the three audio modules, Magisk 24304 does no more boot

I know that this is Canary but changes in Canary usually later go to Stable. And up to v24303, Magisk, Zygisk, audio modules, everything worked perfectly - but now, with this redesign in Magisk, seems that audio modules (as they are) are no more compatible

Unfortunately, eg V4A is not really maintained anymore hence I don't know would it be adapted to the new changes.

Similarly for that Bitrate increase (for my device)

I can live without Bitrate increase and AML - but don't want to go without V4A (V4A was one of the reasons I started to root).

If so, I will probably stopped updating Magisk

I still have a second phone, with JamesDSP (as the only audio mod).

I'll try later today if JamesDSP is also affected with Canary 24304
[Magisk] zgfg:
Unfortunately, the same with JamesDSP:

If JamesDSP module enabled, Magisk 24304 does no more boot

Seems that all audio modules became incompatible with Magisk v24304 ;-(
[Magisk] asripath:
Have you tried v4afx-rootless_10.21.202.zip ?

Available at https://zackptg5.com/android.php#viper
[Magisk] Lughnasadh:
My V4A is working for me. Once I realized that AML was causing bootloops I knew I couldn't install JamesDSP since AML is needed to run both. Maybe later when I have time I'll uninstall V4A and install JamesDSP to see if I get the same results as you 👍
[Magisk] kk100:
Thanks very much for taking time to reply. It will help others also. I understand what you said about hardware attestation process. I also understand Top John wu's problem /dilemma. There could be lot of things he may now not able do. I am Grateful to all the developers in the past who created supersu or Magisk or anything else. Magisk was always free.

You suggested to read https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot. I am just amazed

Thanks very much for taking the time to reply. I understand what you said about hardware attestation.

I am grateful to ask the past developers who developed apps like super su or Magisk. I also understand topjohnwu dilemma but there has to be workaround. I read this which you suggested https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot.

I am just amazed how much power an app is given to check internal storage for files etc. This is just invasion of privacy. It's my phone and I should be in charge of it. Whether I unlock bootloader or not it's my choice or keep Magisk apk in my internal storage or not it's my choice.

I am so frustrated. I don't even have official TWRP for my phone (the Chinese ones changes the build number).

Titanium backup Abandoned. I just can't count how many times TWRP absolutely Titanium backup have saved my phones in past years from bricking and other problems like saving the data.

I just hope some developers shows courage and work on Magisk or create something new so that a user can use the phone as they want. I want the cake to eat it otherwise what's the point of buying the cake.

Starting a crowdfinding could be a good idea if time and money is the problem.

Again thanks very much for your reply. Really appreciate it.

I hope everyone excuses a non developers rant here.

Best Wishes
[Magisk] kk100:
That's the Spirit. I hope some developers show courage and do the work. It's a community. Not a good idea to look only for one developer for all the solutions.

Best Wishes
[Magisk] zgfg:
For backup/restore, you can use Swift Backup (root requied) - you can find the app on Google Play
[Magisk] VD171:
I'm using Titanium Backup on Android 11, it is working perfectly, as I don't need to backup/restore apk/apks.

(Not cracked, I paid for it.)
[Magisk] zgfg:
I didn't use V4A and JamesDSP on the same phone (why would I need to mix) - I used JamesDSP on the other phone

I used V4A 2.7.2 1 (I don't need AML for, I was able to use V4A without AML), but Magisk 24304 does not boot with V4A 2.7.2.1 for me (I enable only V4A module and phone stays forever displaying the boot splash screen Redmi)

MIUI 12.5.2, A11
[Magisk] kk100:
Thank you so so much for mentioning Swift backup. Grateful to to you. Really appreciate it. May life brings peace, happiness and prosperity in your life.

THANKS SO MUCH. 😊😊

Best Wishes
[Magisk] kk100:
Thanks for the reply. I am also using the paid TB version but there is serious problem in TB it doesn't batch restore app and app data correctly. I am not alone lot of people have complained about TB. Sometimes there is backup problems too. One senior member just recommended swift backup and it's really good. It backs up both app and app data. I just don't understand I couldn't find any TB alternatives on Google. Most of the apps were just app (apk back up) which is of no use to me also don't like any kind of cloud backup due to privacy reasons.

Thanks again for the reply.

Best Wishes
[Magisk] VD171:
Titanium Backup keeps restoring app data perfectly.

The issue is only for splitted apks.
[Magisk] kk100:
Thanks for the reply. I think I will use both Titanium Backup and Swift backup just to be on safe side.

Best Wishes
[Magisk] Lughnasadh:
I mix because I prefer certain things from JamesDSP and other things from V4A. For instance, for my tastes the bass from JamesDSP is superior, whereas I find the reverberation and differential sound from V4A more to my liking. Just a couple of examples.

I don't need AML to use V4A either, only when I'm using both V4A and JamesDSP.

Anyway, I digress from the main topic at hand...

Pixel 6 Pro

A12L QPR3 Beta 1

Canary 24304

V4A 2.7.2.1 (Working)
[Magisk] digger16309:
I just used Swift Backup when upgrading from A11 to A12. Perfect. No data loss after a clean wipe and restore. Same as when I upgraded from A10 to A11. The Dev continues to improve it with cloud backups, etc...
[Magisk] pndwal:
Pretty much the point I made...

... Johns point too:

Not sure who your sheep are though... 🤔 PW
[Magisk] VD171:
Some bypasses can be detected.

Any new detection can be bypassed again.

That's simple.

There is nothing to try to create panic in the herd.
[Magisk] anko184:
Hi guys, i just installed Magisk 24.3 but i can't find the online button to access modules. Is their any fix for that?
[Magisk] zgfg:
No 'bug' and no 'fix' here

It's already as that simce v24.0 was released, and in the release notes

There is a new thread opened for Magisk v24 (Magisk - Zygisk), please find it here on XDA. All the important changes (and 'workarounds') are outlined in the exce OP posts there

Similarly, you have no more the integrated SafetyNet tester, but more important there is no more the old MagiskHide...
[Magisk] anko184:
Firstly i want to thank you for your time to answer me. I've been away from rooting and Magisk the last 3-4 years so i need to catch up. The new thread you are talking about is this:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

I apologize for all the trouble but i feel completely a dinosaur here.. :(
[Magisk] edyny1:
Here you go, just scroll down the page

http://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page489
[Magisk] mobileman88:
Could be a corrupted zip. Did you try downloading again and are you able to unzip the file manually?
[Magisk] roshan_shahi:
Was able to flash from the Magisk manager app.. Ran the first command, still false result in SN
[Magisk] Lester_Neo:
Looks like I am not the only one. Had to revert back to v7 for now. Will wait for a stable update.
[Magisk] Captain_Throwback:
Ran what command? The module doesn't require running anything...:rolleyes:.
[Magisk] roshan_shahi:
This one: xsetprop ro.boot.flash.locked 1

Was this unnecesary?
[Magisk] Captain_Throwback:
If you're using v0.2.1, then yes, it was completely unnecessary. Did you not read the post where you downloaded it from?

If your device isn't passing SafetyNet, then your issue is something else. But I didn't see any details on your setup, so...:rolleyes:.
[Magisk] roshan_shahi:
Could you please tell me what steps should I have followed? Could you, please. I have latest Magisk manager and phh Superuser, thats it. Nougat on top.
[Magisk] Captain_Throwback:
Do you have magiskhide enabled? Are you using the phh Superuser Magisk module, not the standard zip?
[Magisk] roshan_shahi:
Yes Magisk hide is enabled and I flashed the standard phh Superuser zip that I downloaded from Magisk thread.
[Magisk] Captain_Throwback:
You didn't say what device you're using, did you?

I still don't understand what Superuser zip you flashed. Can you just provide the filename?
[Magisk] roshan_shahi:
Okay, phh-superuser-magisk-r259.zip is flashed already. And what did you mean by, "using the phh Superuser Magisk module, not the standard zip"?
[Magisk] Timster292:
I installed the systemless Xposed version that should be working
[Magisk] rfgamaral:
I have Magisk installed with phh's Superuser and Xposed. I have enabled the "Magisk Hide" option, disabled Xposed (with Xposed Installer) and rebooted my device. Running the SafetyNet Helper gives me:

SafetyNet request: success

Response validation: success

CTS profile match: false

(red screen with X)

There's also a Request token, Timestamp and Package name displayed.

Wasn't this supposed to be enough to pass the test? What am I missing?
[Magisk] Captain_Throwback:
There's a Superuser zip that isn't a Magisk module. But it looks like you flashed the correct one. Still don't know what device you have, though.
[Magisk] Captain_Throwback:
That should be working with what?
[Magisk] roshan_shahi:
I have Xiaomi Redmi Note 3, AICP ROM Android N, Agni custom kernel if you wanted to know.
[Magisk] Captain_Throwback:
Really depends on the device. Yours might include the bootloader check, in which case you need the xSetProp module as well.
[Magisk] Techy4198:
Any more info on unbricking my device? I've tried using fastboot to flash a stock boot image and that made no difference. I've tried Flashtool and that just fails with the message "Unable to read from phone after having opened it". What can I do?
[Magisk] Captain_Throwback:
I don't know anything about that device.

However I believe AICP is one of those ROMs that usually has root built into it, isn't it? Did you remove system root before flashing Magisk and phh's root?
[Magisk] heinhuiz:
Problem is not if root is God, problem is Google thinks they own God and can manipulate him. (They even bought god's truest disciple.)

Much better would be if we abandon these blasphemers and concentrate on the true child of us and we and it's even the father of Android: Linux. If all us's, ours and we's building power would concentrate on building better Linux for phones and developing and porting apps, we'd be the god's of our own digital world.

I've decided already not to run for the cat or be the mouse, but to be a lion of my own class. My next daily driver will be Linux.

Sorry to all for this off-topic post and thanks for all the excitement of you guys trying to win a lost battle. i'm off here and heading for the future.
[Magisk] VD171:
No, thanks.

I love Google and I love Android.

As Android is Linux, I can do everything I want.

That's simple.
[Magisk] m0han:
seems to be the case for me too. btw, @Rokcy98, @macoloco, @zgfg, @asripath, @Lughnasadh, @vandyman, @Fishawy, are you able to get 'cts profile match' to pass in yasnac app? it was all fine for me. not sure whether this canary 24304 fiasco is what has caused it to start failing. on a side note, vd infos app says my bootloader is locked, while momo says it is unlocked. any tips to get 'cts profile match' to pass, anybody? see screenshots (too many, i know). how to put screenshots under a spoiler?

edit: i've reported my own post to get help to move the screenshots under a spoiler. :D

Spoiler content hidden.
[Magisk] asripath:
Back on 24301 magisk and magisk app.

CTS passes on yasnac.
[Magisk] Fishawy:
I'm on 24304 and Safety Net passes. The culprit modules in my case were Fullscreen Gestures and FontFix (to make AOD & lockscreen clock font similar to system font).

P.S., you need to enable "Enforce DenyList".
[Magisk] zgfg:
Of course, with 24304 (I returned to 24303 and I have no intentions to go back to 24304) I was passing SafetyNet, and had Momo results (not all green) as usual

Make sure that when you update Msgisk that you don't change your settings - I think last time you (also) first didn't have proper DenyList dettings, etc
[Magisk] Fishawy:
How do you revert to 24303 without wiping or unrooting?
[Magisk] zgfg:
I always update by patching and flashing. And I keep my previous (good) patched boot img

Hence I just flashed my boot img that was previously patched by 24303

Also (but this was not neccessary), I uninstalled Canary app 24304 (only uninstalled the APP, not the complete Magisk) and installed Canary app 24303
[Magisk] zgfg:
Btw, when I was downgrading Magisk app:

- I uninstalled Canary app 24304

- I already had downloaded Canary app 24303

- Switched the phone to Airplane mode

- Installed Canary app 24303

- Opened its Settings and disabled Checking for periodic updates

However, when I switched off Airplane mode and reopened Magisk app, it again bothers about the 24304 update

Some would advocate that there is no 'bug' here (TJW is like God, no mistakes), that I disabled only PERIODIC updates but here it checked for updates on reopening the app, but the long story short, you cannot disable checking for updates (even if it does not check periodically, you sometimes need to open the app/mngr to manage something, and from then on you will always have that Update button activated)
[Magisk] J.Michael:
Can you set a Canary to a Custom Channel? Would that eliminate the update nag?
[Magisk] pndwal:
Well put! - Although that doesn't mean I agree entirely. 😜 ...

I think 'roots truest disciple' was born to work for the corporation whose mobile OS is android and who established and heads the body that oversees all major milestones / enhancements... They and "many" of their engineers are pro modding, pro root too, and despite all the naysayers their seniors have even said that they view the 'Magisk community' as "white hat", that Android benefits from their innovations, that this community is not viewed as nefarious, nor as the one abusing root or Google's security model despite tinkering with it (which frankly, Google has tolerated quite knowingly for much longer than most including myself expected)...

Another Frank observation: while some view John as having been 'bought' by Google (even as a traitor), I was very surprised this offer didn't come earlier and that Apple recruited him first!... But what do Magisk users expect? John was 'just a poor uni student' a few years ago when he began this project... What sort of job would we expect him to aim for on completing studies? ... It's obvious to me; his dream job!

I don't know why people view Google as the enemy here either; sure they are slowly developing / tightening security, and of particular interest to us, hardware key attestation to Trusted Execution Environment, but this is the world we live in! All players are doing this, even Microsoft and their chipset partners! ... Google must play catch-up with Apple, already having such a reputation for security that many big corporations ban Android phones for their employees and issue IPhones!

To me these security moves, particularly to give banks etc the assurance of TEE for running their code, are inevitable... What's more, these will actually serve to keep Android relavent & viable, and hopefully the OS of choice for all kinds of software / app developers... Seems to me it has to happen... And most modders wouldn't want the alternative...

Joining a Pride of lions does sound preferable to dodging a clowder of prowling cats!... What phone / Linux mobileOS?

Haha... Some are trying to win, some to eat cake while it lasts, some just having fun playing the game while possible, some are taking it all very seriously, some are waging a war... Others are just trying to be informed of their options...

🙂 PW
[Magisk] zgfg:
In that case Update will be silenced
[Magisk] m0han:
as can be seen from my screenshot, i'm on 24310 (manager and magisk). not passing sn.

and keep it enabled? but, i'm using shamiko and the recommendation is to disable.

i was passing safetynet fully all the way till 24303. but, now 'cts profile match' keeps failing. i don't remember changing any settings in magisk.

did that; didn't work.

i uninstalled app and when that failed to do the job, uninstalled magisk too. still didn't work.

do you think i should set up 'everything magisk' from scratch? i mean, disable/remove all modules....
[Magisk] VD171:
About my app VD INFOS:

- The app does NOT check anything about safetynet. I suggest the app YASNAC: https://github.com/RikkaW/YASNAC/releases

- If you select only "simple root check", the app checks for "su" only.

- If you want to perform other checks, you need to select other options after clicking the "detect root" button.

- If you click the "update contents" button, the app will show if ANY way to read the unlocked bootloader return as "locked".

- If you click the "detect root" button, the app shows if ANY way to read the unlocked bootloader return as "unlocked".

- If you want to perform a complete scan, just select the option "everything: select all" or choose one or more of the other options.

If you want suggestions about your checks and hides, just reply on the thread of the app, please, and I will try to help you:

https://xdaforums.com/t/app-vd-informations-vd-infos-package-com-vitaodoidao-vdinformacoes.4097379/
[Magisk] m0han:
could you please see the screenshots in my post and help me pass safetynet? thanks.
[Magisk] amit_coolcampus:
Hey bro, how and where to get boot.img for Samsung note 9?
[Magisk] pndwal:
ATM may be true... Full HKA deployment will be the clincher however...

Your sheep herd? Who's trying to spook them? 🤔 ... Sorry if I'm missing your point(s)... PW
[Magisk] VD171:
That can be caused by thousands of reasons.

You need to try everything you can exhaustively.

Not always the same solution that works for me, it will work for you.

With each new installation/customization can generate a new result.

I always write all my steps so I can reproduce them whenever necessary.
[Magisk] zgfg:
On March 14, in the private Convo, you had SN passing (at first you didn't pass bcs you forgot to set DenyList or something)

Hence I really don't know why are you constantly playing and resetting - first please make sure you know/learn/remember how to set all things (DenyList, modules, HMA, etc)

Actually, when upgrading (or downgrading) Magisk, you don't need to uninstall Magisk and loose everything.

That way, upon upgrading, everything will be set as previously and it will (usually) continue to work/pass as before

Second, once you satisfactory set things, make a checklist (eg in Notes) how did you set with a dozen of screenshots/scrollshots (Magisk settings, DenyList, Modules, HMA settings, YASNAC, MOMO) and keep them safe (PC, clouds) - then you can always easily go by yourself, compare and fix things if necessary
[Magisk] kramer04:
If you have stock rom you have to download your firmware from Samsung then extract boot.img from AP file.

Or may be more easier download from https://xdaforums.com/t/rom-n960f-d...ase-v7-4-dex-gear-encryption-support.3847061/
[Magisk] VD171:
Very good work, my friend.

Certainly, comparing our own choices, greatly helps understanding.

Every magisk/lsposed module can applies many and many changes on the device.

We need to do a thorough analysis.
[Magisk] hardcorehenry:
Don’t know which commit/s made it possible, but now I’m able to flash latest(canary) Magisk on my Huawei P8 Lite 2017 GSI custom rom LeaOS A11, which was impossible earlier without some modifications.

THANK YOU DEVS!
[Magisk] dr4go:
I love your enthusiasm, but that's not gonna work when Google enforces the hardware backed SafetyNet attestation (TEE). Then your so called god can scrub his-/herself everywhere he/she wants, because your god still depends on the underlying hardware, which is the real god in your comparison.

The question is just whether Goggle is really able to... I remember the not really working TEE on OnePlus devices, etc.

Don't be sorry, I thank you about your post, because I'm struggling myself where my place will be after this phone (Galaxy S10, the devil itself, because of the phone's inability to boot of an initramfs).

I'm also tired of this game, because it's a game you can't win. Period. That's why I've also decided to change something - I didn't think of Linux phones in comparison, but to not root anymore instead.

I've put countless hours into maintaining this current state of my phone where everything runs, lost 3 months of data, because of a bootloop and a possibly broken / corrupt data partition and a subsequently failed Titanium Backup, which is why I rooted in the first place (and better battery life and privacy reasons). I'm getting old and tired as well. But I want to be able to use the phone as my daily driver, not with a second phone in my pocket, etc...

I don't love Google, but I love(d) their work. In the last years their pushing too hard to pursue rooted phones, etc. Obviously their data tracking sucks as well, but I try to circumvent in where / however possible without the sacrifice of Gapps, Google Apps and banking apps, which rely on SafetyNet.
[Magisk] m0han:
well, in that conversation, what i said was:

After I upgraded to A12

, Applist Detector, Magisk Detector, Oprek Detector, Momo etc. are playing up. How can I tame them?

i was on canary 24301 then and didn't have any issues with passing safetynet. and like i mentioned in one of my earlier posts of today, i don't remember changing any settings in magisk.

i have no idea why you thought i was '

constantly

playing and resetting'. yeah, you could say i'm not as good as most when it comes to the know/learn/remember process.

during my attempts, upon upgrading, everything was set as previously but cts didn't continue to work/pass as before. hence my post.

i had made a lot of screenshots earlier and also this morning. i compared, made sure everything was as before and posted only after i couldn't get cts to pass in spite of all that i did.

so, my question as before: do you think i should set up 'everything magisk' from scratch? like, disable/remove modules, rename canary apk to uninstall.zip, flash it to remove magisk fully, boot up clean, install canary manager, use it to install magisk the recommended way.....

p.s.: not sure whether you noticed from the screenshots, but almost everything except yasnac is as before. btw, i was on aospextended rom then. now i'm on crDroid - if that matters.
[Magisk] zgfg:
Yes, I'm referring to YASNAC. Just a week ago, upon upgrading to A12, you were passing SN

SN did not stop passing by itself. You had to change something - and that's the problem, you have to know what did you change and how to revert back

And as said, you had to make notes yourself and screenshots how your settings looked to pass SN

Also, things (incl SN) are described in the Magisk - Zygisk thread, OP posts

For SN, you only need proper settings for DenyList, potentially USNF, and potentially MHPC.

But eg, if you didn't need MHPC with Magisk v24301, I doubt you would start needing with Magisk v24303

Momo, that's another story - but if it recognizes your custom ROM or so, that's really bad luck (consequence of using 'wrong' device with 'wrong' custom ROM - being detected by Momo)

I really don't care for my Momo, hence I would not care for somebody else's Momo either

But sorry I cannot watch for the third time to your DenyList, etc to find what you (again) forgot to set

Sorry but people have to be able to learn from the previous results, past questions/answers, guides and his own successes and failures
[Magisk] m0han:
i did not change anything. i'll wait to see if someone can offer an answer to this:

so, my question as before: do you think i should set up 'everything magisk' from scratch? like, disable/remove modules, rename canary apk to uninstall.zip, flash it to remove magisk fully, boot up clean, install canary manager, use it to install magisk the recommended way.....​