yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Previously when you've asked that I said I would link sources going forward. However, mods have since warned several of us re. giving links to Twitter, Telegram etc XDA deems 'social media'. We can quote however. I've mentioned this several times now, eg:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85723289

Of course I can't link / cite John's Twitter either...

FWIW, @TNSMANI (mod) told me:

If you need more clarity on this XDA rule (or related ones), please take it up with @TNSMANI (or admins @MikeChannon or @the_scotsman)... I've argued the toss with @TNSMANI already! 😬 PW

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

EDIT:

Well, airing this (frustrating) rule (again) seems finally to have made a difference:

Make no mistake, I'm very happy about this, but let's be honest here and bill this for what it is, ie;

XDA has a shiny New Policy!

My little clarification FWIW:

Senior moderator @TNSMANI's recent ruling was both clear and emphatic, namely:

"

quoting content from social media

, it

is allowed provided it is relevant

to the topic of the thread

and no link is given

" (underlining his).

My comment accurately reflects the XDA ruling communicated as recently as the September 21 'thread cleansing' after some argument about both the intention of 'policy' cited and the logic of applying it across the board.

He further stated:

"It means that social media links in threads other than development threads will not be allowed. Though the policy talks about Telegram/Whatsapp links, it applies for all social media, past, present and future. I don't understand the "how this applies / think you draw a long bow..." comment because for me it is clear. If it is not a development thread or if the link is not posted by the Dev, then out it goes."

Does my statement regarding this clear mod ruling (and warning) need 'clarification'? I don't think so. 😬 The fact that the rules have changed / a rule has been revoked does.

Really, what has been clarified is that XDA has a shiny New Policy:

Linking/quoting social media posts (or other webpages for that matter) is perfectly fine!

Labeling this a clarification of what I stated rather than citing @TNSMANI's official ruling for clarification is misleading in that it suggests that linking/quoting social media posts has always been perfectly fine. It simply has not.

You / others may not 'care what's been said before' but after I argued for the same outcome in 5 long apeals to another senior moderator only 2 months ago (after threats that "Future violations may not be treated as lightly and your account may face infractions") and got NOWHERE, please don't minimise either my efforts to achieve the same common sense approach or your new policy by labeling it a simple 'clarification'...

I must applaud you guys / XDA on a victory for common sense however. 😃
[Magisk] BillGoss:
@ "The Moderators" How can a policy be buried in a Xiaomi Redmi Note 5 Pro Guides, News, & Discussion thread and never even mentioned in the forum rules!

The policy should be clearly stated and explained in the forum rules.

Especially since social media includes useful information and a quote is not an intention to take the conversation away from XDA.

Next thing you'll be banning quotes from the OnePlus community forums, Reddit posts, GitHub issues, ... you get the idea.
[Magisk] pndwal:
@BillGoss

Good points, and quite agree... Messaging you some details of discussion with mod. PW
[Magisk] zzz2002:
I screwed up installing a new release of my devices rom!

I did not uninstall Magisk prior to wiping storage and installing .

Could I replace the boot loader (which one might be nice to know (boot and/or sboot) using heimdall?

if so what, if any gotchas should I be aware of?

Thanks

=============

also posted to "LineageOS 19.0 (Android 12) [Signature Spoofing] for S7 Edge Exynos"
[Magisk] mrjuniork:
MOD Info:

Hey folks,

Thread has been cleaned a little in order to unclutter this already very voluminous thread.

If there are questions regarding policy, rules etc., please use the appropriate channels. So dear humans, let's stay on topic, shall we?

On another note, pls keep up the great flow of information and super useful help and support that is given here. There is a lot to learn and lean into here.

Cheers everyone (y)

mrjuniork (Forum Mod)
[Magisk] Didgeridoohan:
Keeping things on topic

The wonderful @mrjuniork has recently finished some light (but much needed) cleaning of the thread. From time to time this quite large thread runs a completely different direction than what the actual purpose is. It seems like it can be fun for those involved, but as we've seen there are many users who can find it frustrating. So please dont...

And I believe this has been covered before. It's alright to make jokes and play around a bit, but don't make the thread even harder to read than it already is. Please.

Telegram?

I'd also like to address this.

There is a "Telegram - The way forward" sticky in every device forum (or should be, at least). The routine regarding Telegram/Whatsapp was put in place because there was an overwhelming amount of threads simply pointing to a Telegram or Whatsapp group. That's not how we want to work... We want to keep the discussions about development and devices to be kept in our beloved forum, of course.

Social media?

And finally, this little tidbit. I've seen this mentioned a couple of times in this thread, but it needs some clarification.

Linking/quoting social media posts (or other webpages for that matter) is perfectly fine (as long as they're on the straight and narrow, i.e. no warez or stuff like that). I don't care what's been said before, this is where we are at now. What we care about, as I've already mentione, is if users and discussions are directed away from XDA. That's why we're so restrictive with Telegram groups (see above), even though they have their uses (which is why we allow developers to keep a Telegram channel linked in their dev threads).

Conclusion/TL;DR

Keep things on topic (and this thread has a habit of running amok when it comes to that).

Linking post on social media is fine.

Directing users and discussions away from XDA is not fine.

I'm going to keep a close eye on this thread from now on and will keep it clean from future off-topic posting. Posts will be removed without warning (but notifications will go out to those involved).

Questions?

If anyone has any questions or anything to add regarding what I've written here (I find it perfectly clear and know exactly what I mean but I'm pretty sure there's something someone is going to find unclear), for the love of whatever you find holy do not post it here (remember the off-topic cleaning without warning mentioned above?). My inbox is always open, contact me there...
[Magisk] moocow1452:
Hi all, checking back in. When testing the Oculus Go, and why it's negating the changes Magisk made to the Boot.img, it came up on my GitHub issue that it might be a SAR device, and that I would need to make changes to the ro.secure while it was on the device. Assuming that I understood that correctly, I'm not entirely sure how to do that. GitHub issue is attached, where should I start?

Magisk fails to handle special sepolicy on Oculus Go · Issue #4914 · topjohnwu/Magisk

Device: Oculus Go (pacific) Android version: 7.1.2 Magisk version name: 258e89c Magisk version code: 23013 Oculus released an unlocked build for the Oculus Go that allows user access to boot and sy...

github.com
[Magisk] J.Michael:
Your GitHub report starts by saying you got a version of the firmware that allows the user to change boot and system. What does that mean? Do you have some root access when that firmware is booted?

I thought @osm0sis wanted you to edit some props file. Do you know where that file is? Can you see that it exists? Can you read the file?
[Magisk] pndwal:
Latest vvb2060 Alpha Magisk (Unofficial Build - for mavericks only!) Translated:

Alpha update log​

Magisk (b76a3614-alpha)​

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[App] Use local version when unable to download stub

[App] Switch to Java 8 Modern Time API

[General] No longer automatically unlock the device block

[General] Use MagiskHide to hide when Zygisk is closed

[App] Delete markdown rendering

[General] Do not execute scripts that have ignored loading modules

[App] Fix that Magisk cannot be updated from notification

[App] Fix that the second time tapping the hidden app button may be unresponsive

[App] Fix the effective time of signing certificate

[App] Enable network request caching

[App] Rewrite install application function

[App] Enhance the function of repairing environment

[App] Fix that some processes in the exclusion list may not be displayed

[App] Support setting the KEEPVBMETAFLAG flag to skip processing vbmeta in the boot image

[Zygisk] Fix Xhook

[App] Adapt to Android 12L

Complete changelist incl. Upstream update log here:

https://github.com/vvb2060/Magisk/b...f003e86ff4f/app/src/main/res/raw/changelog.md

👍 PW
[Magisk] pndwal:
Latest Alpha change brings SDK 32 (API level 32) compatibility, allowing testing Magisk with newly released Android 12L Developer Preview 1 and Beta 1 (for a partner device, a virtual 12L device, a Google Pixel device or even a Treble compliant device with a GSI).

12L is a "special feature drop" coming early next year that "makes Android 12 even better on tablets and foldable devices". It provides new features for large screens among other things.

https://developer.android.com/about/versions/12/12L/get

PR commits from latest vvb2060 test builds merged in Alpha for

- Target SDK 32

as well as for

- Further fix oplus.fstab support

- Support KEEPVBMETAFLAG env variable

- xhook_clear after xhook_refresh (for Zygisk hiding compatibility)

and many other fixes have been made but not yet merged upstream in TJW Magisk.

https://github.com/topjohnwu/Magisk/pulls

👍 PW
[Magisk] VirginPC:
Hi, Thank you so much for ur

Thank you for ur help here...... For now I only have 1 phone to use, so I cant risk to reinstall TWRP (so I can boot into recovery by press the 3buttom for Samsung Note 8), worry it go to boot loop.......

I will give a try once I get an extra phone...... If cant, then I have to format my phone & reinstall the ROM........

Thank you so much for ur time here......
[Magisk] moocow1452:
On the current build, I have access to ADB Root. I was unable to find default.prop on the device, but it was under my nose in root the whole time. Thanks for your patience.
[Magisk] markbnj:
this is GREAT, can someone cross-post this as a new topic and make it sticky??

I'm new, and absolutely queasy at trying to decypher it!
[Magisk] Lughnasadh:
PSA: Just to let everyone know, seems no one is able to root after updating to the December security update on the Pixel 6 Pro (probably Pixel 6 as well). Numerous reports (including myself) of after patching the boot image on reboot there is no root. Using Magisk Canary 23015.

Seems Google has changed something and Magisk may need updating to root the Pixel 6 series.
[Magisk] zgfg:
Did you maybe try with latest Alpha:
[Magisk] Nekromantik:
One person said they were on latest Alpha and it broke root also but not tried myself.
[Magisk] pndwal:
New Magisk App functionality coming:

Introduce RootServices to the app

https://github.com/topjohnwu/Magisk/commit/edcf9f1b0c524d8b7150ffcef387f248e32f0972

www.twitter.com/topjohnwu/status/1469266620572860418

Anyone care to expand on implications / how this will change Magisk / Magisk experience? 😛 PW
[Magisk] pndwal:
But do you have root to break on P6 pro w/ latest stock updates? ... I do see the latest TG comments indicate incompatibility w/ latest P6 update...

FWIW, update to latest Alpha build went fine on my RN8T. PW
[Magisk] Nekromantik:
Im not sure what you mean exactly but on the October and November version Root works fine on Magisk Canary.
[Magisk] Lughnasadh:
No I haven't. See someone else already reported not working with the latest Alpha either.
[Magisk] pndwal:
My bad... Thought you were the member trying to solve issues with initial root on P6 Pro w/ latest stock updates... PW
[Magisk] sille:
if u tell me how i can download it, it would be awesome
[Magisk] Quinny899:
RootServices are not new, they've been around for a while.
[Magisk] pndwal:
Some insight here?:

https://xdaforums.com/t/rooting-android-12-on-sd765g-and-tensor-pixels.4354083/ 😬 PW
[Magisk] pndwal:
Got Telegram?

https://t.me/magiskalpha/390?single 😉 PW
[Magisk] Lughnasadh:
No. We have had no problems rooting the Pixel 6 series with the latest Canary Magisk (23015) before the December update. Something in the December update (which was just released this afternoon) broke root on this device.
[Magisk] pndwal:
Mmm. I see libsu has also... but I have no experience with it, and wonder what integration will do / mean for Magisk / apps using root permissions.

Any insight? PW
[Magisk] Quinny899:
It allows apps to run Java (and Kotlin) code as root via Binders. Amongst other things, my own app DarQ has used the method for a good couple of years now.
[Magisk] pndwal:
Many thanks for spelling this out for the layman!... I may need to look into this. 👍 PW
[Magisk] pndwal:
Ah... and I see you've been there...

FWIW, someone just told John (in interesting OT thread) FWIW (not you is it?):

www.twitter.com/Trav_Montana82/status/1470525871509454849 PW
[Magisk] t-ryder:
I got a Pixel 6 and was waiting for the December '21 factory image cuz it fixes like hundred bugs. Now I got warned that the Dec. update breaks magisk root and will wait. Damn, I only had trouble with that Pixel 6 since buying it.
[Magisk] Lughnasadh:
No that wasn't me but I was told by another user that they had notified John via Twitter about the problem. Since some people use different user names for different social media platforms, I'm not sure if that is the same user. 👍
[Magisk] moocow1452:
Me again, with the Oculus. I am getting a permission denied error when trying to change my default.prop over adb shell. I have done adb root and adb remount on my device, and even did "mount -o rw,remount /" for good measure. When doing a "mount | grep system", nothing comes up either, so I'm kinda stuck. Any ideas?
[Magisk] pndwal:
So there's a proper issue now... and LoveSy's onto it... says will make PR... likely first merged fix will be in Alpha...

https://github.com/topjohnwu/Magisk/issues/5057#issuecomment-993181609

...And another (duplicate?):

https://github.com/topjohnwu/Magisk/issues/5058 PW
[Magisk] Lughnasadh:
Yep. I was one of the ones that submitted a bug report in the first issue you linked. Looking hopeful. 👍
[Magisk] pndwal:
Yup. A fix already:

https://github.com/topjohnwu/Magisk/pull/5059

You could build it yourself from here if game!:

https://github.com/LSPosed/Magisk/tree/fstab

or wait... John's in gear now, but PR needs reviews...

Watch Alpha too... All those guys are aware of issue / are behind the fixes!

Detail:

Apparently it's caused by this Android commit:

https://cs.android.com/android/_/an...re/+/e98afa2687eb56184dad8569b929eba04fb93068

👀 PW
[Magisk] Lughnasadh:
Yep. Saw it. 👍
[Magisk] Rumsfield:
Worked for me, back in business! Gee that only took them 12 hours lol.
[Magisk] pndwal:
Its a race between Alpha and a TJW build now...

Many PRs being committed in TJW Magisk AWS! 'Load fstab from system/etc' for Pixel 6 issue is done... Reckon vvb2060 may hold fire w/ Alpha for TJW Canary or perhaps Beta!... But I'm not a betting man. 😉 PW
[Magisk] dimm0k:
with this version, anyone not able to hide magisk? it's grayed out on my end
[Magisk] rodken:
You can also utilize the direct source to locate the file.
[Magisk] Lughnasadh:
Betting on TJW given I don't see anything being currently committed by vvb2060 and TJW's pace seems like he wants to get out a Canary build quickly.

https://twitter.com/i/web/status/1470722938995240963
[Magisk] pndwal:
Magisk 23000 (23.0), 23001 or earlier?

Since 'make stub install fully offline' was only merged post 23001 you need to be online for older releases. Check ad blockers, firewall etc if more than no network... Please say build version if on Canary or an unofficial build. PW
[Magisk] Lughnasadh:
Can wait for new Canary or if already rooted with new apk uninstalling the new apk and reinstalling Canary 23015 should bring back that function, I believe.
[Magisk] pndwal:
No, no. - The function is there & works fine! Just not offline in 23001 or earlier. (Stub must be downloaded.) See post above.

Incidentally, '"Hide the Magisk App" fails without "Install Unknown Apps" permission' fix has just been merged also. Existing Magisk will need this permission for hiding to succeed, but I don't believe option is grayed out. PW

Edit: Sorry, understand he was speaking of a test build now...
[Magisk] Lughnasadh:
Yes and no. We are talking about the new "nightly" apk with the load fstab from system/etc commit. The hide Magisk app is greyed out so you cannot use it. Need to wait until the new Canary release for it to not be greyed out.
[Magisk] MichelH1973:
Thanks worked fine on my s21 Android 12 !

Does someone knows how too Fix s-health and Pas in Android 12 ?

The Line in build prop seems be moved OR changed ?
[Magisk] pndwal:
Haha!... I didn't connect the dots... ('this build' 🙄)

So based on 23000? Is the build still up? PW
[Magisk] Lughnasadh:
It's basically Canary 23015 with that 1 commit added. It is still up on Github ( https://github.com/topjohnwu/Magisk/actions/runs/1576410350 ) as well as on XDA ( https://xdaforums.com/t/fixed-lost-...oot-is-important.4374759/page-3#post-86094137 ).

Only needed for Pixel 6 series on December update and beyond.
[Magisk] pndwal:
Ta. (Make that P6 on latest stock updates?)

... Just spotted it's a Zygisk build from SS...

Sure links will help Pixel 6 users who can't wait a few more hours (minutes?) 😛 PW
[Magisk] Lughnasadh:
Yes, Pixel 6 series with December update. (Edited post 🙂)
[Magisk] pndwal:
😝 Why is XDA themed Mr frosty blue after visiting your XDA link? 🤪

Also re "You can download the newest magisk manager apk"...

1) You might let him know that Magisk Manager is Dead n Burried since single-package APK distribution! 😬

2) Did you guys try the (newest) test build from master Magisk?

https://github.com/topjohnwu/Magisk/actions/runs/1577670575 👀 PW
[Magisk] J.Michael:
I got blue text from the moment I visited my New Posts link. I think somebody decided to mess with a Classic.

I think the Magisk Manager app should always be called the Magisk Manager app. I think people are not careful enough about distinguishing between the app and the truly magic Magisk embedded code. Just because both are contained in a single file doesn't change the fact that you have to install two pieces, it just changes the mechanics of installation.
[Magisk] Kennyeni:
Do we know how a new Canary gets "born"? Hahaha. I see a lot of changes since the last one, so not sure how a "stable" canary gets created.
[Magisk] V0latyle:
There are quite a few developers working on Magisk; changes have to be verified and approved before commits are made. The owner of the project (or fork) can then decide when to release a new update.

If you go to the Magisk Github, you can look at all the commits that have been made between releases.
[Magisk] pndwal:
Won't comment further on this since posts are already deleted, but well done on green-lantern status! 🙂

OK... Perhaps I'm just a conformist... Or take release notes too seriously! 🤪

"Magisk Manager is dead.

Long live the Magisk app!

... "

https://topjohnwu.github.io/Magisk/...agisk-manager-is-deadlong-live-the-magisk-app

Also, Johns changelogs:

• [App] The term “Magisk Manager” is no longer used elsewhere. We refer it as the Magisk app.

https://topjohnwu.github.io/Magisk/changes.html#v220

🤔 PW
[Magisk] pndwal:
Second (test) fix for up-to-date Pixel 6 series users:

Thanks for confirming this fixes broken 'Hide the Magisk app' in LoveSy's test build from LSPosed:fstab Magisk! 👍 PW
[Magisk] replica9000:
Sorry if this is the wrong place to ask. I've been on the Canary channel since I bought my OnePlus 8T. My phone randomly failed SafetyNet. I updated to Magisk 23015, and now I don't see an option to test SafetyNet anymore. Is there a new way to test?
[Magisk] Lughnasadh:
You can use YASNAC, SafetyNet Checker, etc. from the Play Store
[Magisk] Homeboy76:
You are faster than a 'speeding bullet'. :ROFLMAO::ROFLMAO::ROFLMAO:
[Magisk] ipdev:
I have been working on writing a thread when I have time.

I sniped a few things out of it that will hopefully answer some of your questions.

Please read John's State of Magisk: 2021 for information.

WebSite - medium.com - Link

Starting with the Magisk 23 (23010) canary builds.

MagiskHide is removed.

Magisk Module online Repo is currently removed.

Everything SafetyNet is removed.

Zygisk is introduced.

The Deny list replaces the Hide list.

What does this mean?

Not much. ;)​

It is just the next step in Magisk's development.

Even before these changes, the xda family and the Android community have always been active and willing to share. :D

________________________________________________________________________________________________________________________________

@

Didgeridoohan The name of the module describes it very well. ;)

[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2 - xdaThread - Link

[MODULE] MagiskHide Props Config - GitHub - Link

@

kdrag0n figured out the current SafetyNet 'trick' to get around forced hardware attestation check.

MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0 - xdaThread - Link

Universal SafetyNet Fix - GitHub - Link

@

Fox2Code created an app to install modules from an online repo.

Fox's Magisk Module Manager - GitHub - Link

@

Xingchen & Rikka

YASNAC - Yet Another SafetyNet Attestation Checker - PlayStore - Link

YASNAC - GitHub - Link

Note:

It is still a work in progress.

The Modules I note (link to) are by xda Recognized members and/or contributors to Magisk.

Cheers. :cowboy:
[Magisk] replica9000:
I still have an option to hide the Magisk app. I do remember hearing the online repo was disabled.

So YASNAC reports I pass both tests. Play store still shows my device as certified. Yet apps like Netflix still refuse to update. I guess I'll do some more digging.
[Magisk] pndwal:
Netflix / other apps (bank etc) in denylist? denylist enforced? Cleared app data for each since 'Device is certified' restored?

Do you have Netflix from PlayStore or some sideloaded solution? If PlayStore Netflix doesn't work, check widevine shows L1 security... They rely on this TEE attestation rather than SafetyNet now... You may need to check device specific method to restore if on L3.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85232477

Further, OnePlus messed up hardware TEE attestation implementation in some (all?) of their devices... I'm not sure how this impacts Widevine for OnePlus. PW
[Magisk] BillGoss:
On my OnePlus 8T, DRM Info app shows L1. It does that on both Magisk 23.0 and 23015.
[Magisk] zulu88:
Yes, this is the next step, but backwards, not forwards.