yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
What is the difference between the two screenshots?
[Magisk] zgfg:
On first it displays Shamiko working for N processes, on the second Not working bcs DenyList is enforced
[Magisk] m0han:
i presume you meant the reverse. at least this is how i see it. btw, you also seem to have got the hack working. (y)
[Magisk] zgfg:
I did it pretty easy, unzipped Shamiko 1.2 and 1.3 and compared the post-fs-data.sh scripts. Difference is in two lines

So I basically copied over that script from 1.2 into the /data/adb/modules Shamiko folder and rebooted.

Seems the Engineer did some more adaptations (like translation of Shamiko sayings/phrases), but mine was a 1-2 minute work
[Magisk] vandyman:
Thank goodness for a smooth January update for the Pixel 6.

If the the update would have went sour for Magisk, there would have been a flood of craziness here.

🎉🎇😀
[Magisk] Stillhard:
Correction, should be: (She is queen...
[Magisk] daddy riverat:
Anyone know where i can find a proper download of magisk i have been trying to successfully root a couple of my motorola devices seeing as i could unlock the bootloader anyway feel like its nearly impossible to find phones like that anyway ive unlocked bootloader and only on my moto g -fast (xt2045-3) have i had a successful install patched magisk rebooted the system os starts gets to lock screen and touch screen fails to work connected mouse via otg and i was able to open the phone but couldnt get wifi to turn on to at least download root checker im unsure of anything else that might be wrong but does anyone have any idea as of what i might be doing wrong or ways to fix it i also have a moto g play 2021 (xt2093)-4 i have tried to install magisk but havent had a successful install if anyone knows whre i can find a proper custom recovery and root id greatly appericate it please and thank you everyone
[Magisk] Homeboy76:
Anyone know where i can find a proper download of magisk...

Magisk-Stable

Releases · topjohnwu/Magisk

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

github.com

Magisk-Canary

File Finder · topjohnwu/magisk-files

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com

Magisk-alpha

Magisk alpha

t.me
[Magisk] meric57:
Hello, following the installation of official DBT Android 12 d firmware on my S10 G973F exynos not 5G.

I installed TRWP the concern for magisk which does not root my S10 no instaltion magisk instalation ok.

TRWP install 3.6.0-9-2 and multidislabler3.2 ok works, there is no way to install magisk direct flash trwp or with magisk.
[Magisk] pndwal:
Thanks... I've made that mistake before... Nangong Xueshan is a bit obscure as a name it seems. PW
[Magisk] zgfg:
No need to hack anymore, she was updated again
[Magisk] Eng.Raman:
Yes, I translated all the japanese words and created a flashable zip by editing some scripts in customize.sh, service.sh, and post-fs-data.sh.
[Magisk] Eng.Raman:
It needs for every new release ( at least for my device to remove some props in service.sh ). Also for translating the japanese words.
[Magisk] pndwal:
Information on updated Android 12 Samsung devices issue here (fix merged downstream):

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

This fix should do it, but there are other fixes that include Sammy devices merged, eg:

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

👀 PW
[Magisk] zgfg:
For me Shamiko v0.2.0 (59) displays the status out-of-the-box - as in the screenshot.

And changelog says that module's description was fixed

(and Japanese phrase is of no practical use - it's like a tribute to anime)
[Magisk] pndwal:
Please say which props you remove / what it fixes. 👍 PW
[Magisk] zgfg:
You could translate description phase
[Magisk] pndwal:
Latest Shamiko:

# Shamiko

こっっ…　これで勝ったと思うなよ―――!!​

### Introduction

Shamiko is a Zygisk module to hide Magisk root, Zygisk itself and Zygisk modules like riru hide.

Shamiko read the list of apps to hide from Magisk's denylist for simplicity but it requires denylist to be disabled first.

### Usage

1. Install Shamiko and enable Zygisk and reboot

1. Turn on denylist to configure denylist.

1. Once denylist is configured, disable it to activate Shamiko

### Changelog

#### 0.2.0

1. Support font modules since Android S

1. Fix module's description

👍 PW
[Magisk] traversone:
dear all,

often and often I loose root during normal mobile life !

Alpha-3 version is installed.

A reboot is required.
[Magisk] meric57:
Good evening Pndwal, so I installed this patch then modified my ap firmware with magisk and flashed with odin 3.14.1 restart in recovery to do a factory reset. restart normal restore magisk 230016 corrective version still magisk not rooted on the other hand magisk app yes.

It would be a tutorial that summarizes the manipulations to do, thank you
[Magisk] Eng.Raman:
Removed all the Samsung related props below ( Fixed the unexpected/sudden reboot for my device ).

ro.boot.warranty_bit

ro.warranty_bit

ro.vendor.boot.warranty_bit

ro.vendor.warranty_bit
[Magisk] XIKingGoldIX:
Hello, i've been trying for a while, after having loaded the latest stock firmware for my S10+ (SM-G975F) which updated me to Android 12 i absolutely can't get to install magisk. Im wandering if this device with android 12 can actually be rooted, i found 0 tutorials on google. Please, can you help me?

Edit: if followed the hereby procedure from the two post including corsicanu method. I managed to install TWRP and flash recovery with Canary.

https://xdaforums.com/t/help-root-attempts.4386087/

Thanks to both corsicanu and this gentleman for their contribution.
[Magisk] Lord Sithek:
Hey guys, I thought I can give you some mystery to solve ;)

My device: Xiaomi Mi Note 10 (tucana) running custom OctaviOS ROM based on Android 12.

My current setup: Latest Magisk Alpha, Zygisk and Shamiko enabled (I always update them to the latest available). I'm passing SafetyNet just fine.

I use my local (Polish) bank app (https://play.google.com/store/apps/details?id=pl.mbank&hl=pl&gl=US) and it's generally quite liberal about root access. But recently the bank introduced the new feature of contactless payment through the app. Something similar like GPay, but within the app itself. Now, although I can normally use the app withouth a problem, I can't activate the feature of contactless payment.

When I add two suggested processes (see screenshot attached) to the Denylist and later I disable it in order to enable Shamiko, the bank app does not allow me to start the process of enabling contactless payment at all - it says something like "you cant enable the feature for the security reasons".

When I enable all available processes in the Denylist, clear caches of the app and reboot, it allows me to start the process, but it always ends with an error, saying something like "we coudn't finish activation process, if this will happen again, contact the support".

I've checked on my wife's Redmi Note 10S with stock MIUI (A11) and the process can be finished successfully. It's not a very big problem because I can use GPay as I've been doing so far, but I'm really curious what this app really detects... I'm attaching my Magisk log and a logcat taken while I was trying to enable contactless payment - in case if it tells something to somebody ;) If I could provide any addtional useful info, I'll do it gladly.

By the way, my Momo isn't very happy - it detects custom ROM and bootloader unlocked... If anybody has an idea how could I make it more happy, I'll be happy too :LOL:

Cheers
[Magisk] pndwal:
Some ideas:

Have you tried w/ debugging off?

Tried using HMA LSPosed module to hide Magisk app and other root apps from bank app? (Nb. PushTan app requires both Hide the Magisk app and HMA hiding.) Select the first 3 hide methods.

Is your wife's phone rooted? PW
[Magisk] pndwal:
I believe you are using an old device... How many apps are in denylist?

Also, is Systemless hosts module active? If so, please remind me of current ROM. PW
[Magisk] pndwal:
Sorry, what 'patch'? ... Do you mean you installed test build or Alpha with the fix? ...

Shouldn't need recovery factory reset if flashing with Odin (assuming device launched with Android 9+)... Just be sure to include all 4 components incl CSC (NOT HOME_CSC) as per official instructions for Samsung... PW
[Magisk] Lord Sithek:
Actually I forgot to mention that tried with debugging off before and that I have template in HMA configured, but after seeing your reply I decided additionally to hide Magisk App and LSPosed Manager and to add them to HMA template. Additionally I review the apps on the list and I added one or two with root access. And... voila! Magically I've been able to finish the setup 😁

The lesson: try every possible solution and don't assume it won't help 🙃

Thanks, @pndwal !
[Magisk] zgfg:
But frankly, both these two hints have alreaady been mentioned here - unfortunately, there are two many posts and it might be hard to follow

Ofc, if you uninstall the LSPosed mngr (you can, and use the shortcut instead - the so-called 'parasitic' manager), then LSPosed mngr does not go to the HMA template
[Magisk] pndwal:
You may wish to test which app is detected, but I suspect they are following Sparkasse bank S-PushTAN trick to detect even hidden / obfuscated Magisk app as use of this app is universal w/ Magisk root; detecting LSPosed etc will only catch a subset of Magisk users...

Detecting applist should be prevented in theory since Android 11, but in practice some are still able to do this using some trickery, eg using Intent queries instead of API requests. Also, some like Sparkasse bank S-PushTAN can detect the hidden ('fully obfuscated") Magisk App by detecting the classes.dex code which does not change (unlike the package name) and can be used to identify the app. Their protection engine (Promon) seems to employ simple pattern matching on installed apps.

I was able to properly hide the already 'hidden' Magisk app (with Intent query hiding set) from S-PushTAN (and it would load) by using Hide My Applist LSPosed module. Hiding the unhidden app this way doesn't work (can app find package name etc even with HMA set?).

I have just discovered LSPosed HMA solution is no longer working for S. PushTAN since 3.5.2.

https://github.com/topjohnwu/Magisk/issues/1084#issuecomment-1013811582

Is PTAN now detecting isolated processes etc in addition?...

Someone w/ Riru could test w/ Momohider... I'm using Zygisk / Shamiko. PW
[Magisk] pndwal:
Bit more on this: these banks are getting clever; Shamiko doesn't hide this (Chinese translated):

https://t.me/lynote/4564

More that banks too. (Coffee anyone?):

https://t.me/c/1414270883/35622

Not sure if MomoHider can either... Later... 😬 PW
[Magisk] meric57:
Hello Pndwal, the app-debug APK that I install on my my S10 under android 12 which is not in 5G.

I modify AP with magisk and I take the 3 BL CP and CSC home files and in AP I but magisk-patched from AP and in download mode. I flash with odin, then boot into recovery I do a factory reset boot system as on the first day, I reinstall magisk in the magisk app part intaler magisk part no.

john wu's app-debug apk patch
[Magisk] Lord Sithek:
Yes, I try to follow this thread (quite a tall order :LOL:) and I remember all those hints being mentioned, I just failed to test all of them at once :sneaky: And right - I think I didn't state it too clearly - in the end I hided Magisk app and additionally I added the repackaged manager to the HMA template, then I created parasitic LSPosed Manager and uninstalled the original app. Probably one of these tricks did the work
[Magisk] Lord Sithek:
Maybe you could try yourself with the help of this mod? https://xdaforums.com/t/module-initrchider.4369285/#post-86265161

Reportedly it doesn't require Riru to hide init.rc modifications
[Magisk] traversone:
I am currently using the "famous" S8 with Hades ROM, No systemless hosts module active and 10 apps in denylist.

Alpha-3 version in classic MagiskHide configuration.

with Canary 23.001 never got this issue.

same happens on Android Box with Android 10, 1 app only in denylist and no systemless hosts module
[Magisk] pndwal:
Official way is use CSC to do full wipe w/o need to factory reset in recovery...

Still not sure what you mean by 'app-debug apk patch'... Is that extracted from the zip in artifacts on actions page I linked or not?? ...

Because this fix is only available as test build or in late Alpha unofficial at the moment as I said... It is merged already in Magisk master branch, but DOWNSTREAM of current builds... It has NOT been carried to any TJW releases yet! PW
[Magisk] pndwal:
Then my hunches were off, sorry... Guess you are certain boot.img is definitely from current ROM (exact match)?... grasping at straws now, sorry... 🤔 PW
[Magisk] meric57:
Hello, yes we lose the thread with all this I see on github magisk 23.00 compatible with Android 12 some talk about magisk modify app-debug under 23016 of magisk. It should be clear so you just need to modify the AP with magisk 23.00 and flash with odin with restored without doing factory reset or others and put CSC not CSC at home

Current TRWP we can't install it
[Magisk] pndwal:
Many thanks for great share!

Just tried it, and unfortunately only additional init.rc solution didn't fix... Still watching... I think real users will be posting about it soon anyway... I just try it as a test. 👍 PW
[Magisk] meric57:
Hi Pndwal, I proceeded like this

with magisk 23.00 I modified AP to magisk-patched .tar .

Open odin 3.14.1 in AP the macgisk-patched and CSC BL CP and start with reboot demarage ok reinstall the magisk application.

In magisk app instaler and magisk no just SAR yes.

you don't have a link for magisk image to install it by itself.

if I go through the update channel, there is not a link to put in the personalized channel
[Magisk] shoey63:
A Canary build was done by @capntrips 15 hours ago.

It can be found in this post Here

It is of interest to Pixel users as it fixes and reinstates the "Install to inactive slot (after OTA)" option.

It may be useful to others too, as it contains all the latest commits to that point.
[Magisk] pndwal:
Yup, #5143 didn't quite do it:

https://github.com/topjohnwu/Magisk/issues/4955#issuecomment-1012369126

Yup, yup, any Sammy users keen?... Here you go!... More complete early access fixes...

Thanks for headsup!

Test build in artifacts here also:

https://github.com/topjohnwu/Magisk/actions/runs/1702416832

A new one pending workflow approval too.

👍 PW
[Magisk] pndwal:
Not sure what you mean by 'magisk modify app-debug under 23016 of magisk' then 'just need to modify the AP with magisk 23.00 and flash with odin with restored...' 🤔

I think you're getting confused... You're confusing me. 😝

What is demarage?

What does 'instaler and magisk no' mean?

What is 'magisk image to install it by itself'?

Who told you to personalise channel? - do you know how to find raw json file associated with build you want??

Please go back and read what I said; It seems you have same issue MANY Samsung users have after recent official firmware updates, ie THESE ANDROID 12 UPDATES BREAK MAGISK!! - Read 23.0 is NOT compatible with recent A12 updates on Samsung due to Samsung inexplicably including broken fstab in device tree!!!

I said try Test build or Alpha build as these include fix... It's NOT EVEN in Canary 23016! (But now we also have @capntrips build above also...)

Forget custom channel etc... Just follow John's instructions for Samsung... (Don't need TWRP.); In brief, Extract the test APK from artifacts zip linked, or download capntrips or vvb2060 (Alpha) APK ONLY. Install that, patch AP.tar, transfer files using ADB, NOT MTP, Flash using Odin... No need to install App again after boot; you've already installed both App and Magisk (mask) from same package...

Hope this sorts it out for you, and test fix works. 🥵 PW
[Magisk] pndwal:
So we're getting Allow modifying denylist without enforcement!

That was surprisingly complex to implement:

https://github.com/topjohnwu/Magisk/commit/76ddfeb93a8b3612cd68988323f422e996751e16

😛 PW
[Magisk] zgfg:
Although I have no Samsung, I'm confused a bit

Doesn't USNF similarly play with the warranty bit props.

Don't you use USNF or do you have to similarly adapt it (or is there a special version for Samsung)?

Hence, what is your final/working configuration:

ro.boot.warranty_bit=

ro.warranty_bit=

ro.vendor.boot.warranty_bit=

ro.vendor.warranty_bit=

(given props not defined)

or:

ro.boot.warranty_bit=0

ro.warranty_bit=0

ro.vendor.boot.warranty_bit=0

ro.vendor.warranty_bit=0

or:

ro.boot.warranty_bit=1

ro.warranty_bit=1

ro.vendor.boot.warranty_bit=1

ro.vendor.warranty_bit=1
[Magisk] meric57:
Good evening Panwal, I see who does this for pixel6 no.

I give up I put the official DBT A12 version back on my S10.

I expect next week to see if there is better.

Captrips did for what type of model I tried its block on userdata in odin.
[Magisk] traversone:
my curiosity led me to save full "getprop" log to compare:

a) S8-Hades ROM and MagiskHide enabled (alpha-3)

b) S8-Hades ROM and Zygisk+Shamiko enabled (alpha-3)

among others, I found this:

a) [init.svc.bootchecker]: [stopped]

b) [init.svc.bootchecker]: [running]

could this difference be relevant?
[Magisk] ipdev:
You still need to have Zygisk active to modify the denylist in the app.

You do not need Zygisk active to modify the list by command line.

You can populate the denylist once Magisk is active via CLI. 🙃​

Cheers. :cowboy:
[Magisk] ipdev:
The USNF module includes the Basic sensitive props that need to be adjusted.

system.prop

It sets the props to the "safe" value on all devices.

No check if the prop exists or what value it is set to.

If the prop is not native to the device, it is added.

The next USNF release will also add ro.is_ever_orange=0 to every device.

I have been meaning to ask about it in the USNF thread. ;)​

Example.

Pixel 5a (Stock Google).

[List of sensitive props]

Spoiler content hidden.

Spoiler content hidden.

Additional props are in bold.

Spoiler content hidden.

Prop values are adjusted. No additional props added.

Shamiko's service script should only adjust the value(s) if the prop exists and the value is different than the safe (expected) value.

Function

check_reset_prop() {
local NAME=$1
local EXPECTED=$2
local VALUE=$(resetprop $NAME)
[ -z $VALUE ] || [ $VALUE = $EXPECTED ] || resetprop $NAME $EXPECTED
}

Example

check_reset_prop "ro.boot.warranty_bit" "0"

NAME=ro.boot.warranty_bit

EXPECTED=0

VALUE=The current ro.boot.warranty_bit value of the device

[ -z $VALUE ] || [ $VALUE = $EXPECTED ] || resetprop $NAME $EXPECTED

If the current value is empty. (The prop does not exist.)

Do nothing.

or

If the current value is not empty.

If the current value is the same as the expected value.

Do nothing.

or

If the current value is not empty.

If the current value is not the same as the expected value.

Reset the prop to the expected value.

Not sure what @Eng.Raman setup is or why that part of the script is causing error and only with the Samsung prop values. :unsure:

Unless the values are being changed at the wrong time??

Might be Shamiko is checking and adjusting the props before USNF sets all the prop values. ??

If USNF sets the props before Shamiko checks the prop values, all the values should come back as expected and no changes will be made.

Cheers. :cowboy:
[Magisk] pndwal:
Ta; still looks like a concession in deference to Shamiko (requires / hides Zygisk, hijacks denylist)...

Wonder who he's referring to here!?:

www.twitter.com/topjohnwu/status/1481207454650146816

🙂 PW
[Magisk] zgfg:
It's not about Zygisk - Zygisk IS (assumed to be) ENABLED all the time

The fix is about Shamiko (Magisk module that hides Zygisk from being detected)

For Shamiko, Configure DenyList MUST BE DISABLED - and becuse of that you can not manipulate Configure DenyList (list, add, subtract) either through Magisk app nor through CLI.

However, Shamiko (taking the role of denying), REQUIRES that DenyList MUST BE properly CONFIGURED

Did you insrall Shamiko yourself?

Please install and shortly play with

Consider that you do have Shamiko installed (and everything configured).

And that you later want to add one more app to DenyList

Now, you cannot do it either through Magisk app nor through CLI , both because Enforce DenyList is already disabled

To be able to manipulate your DenyList, you need three steps:

- Enable Enforce DenyList

- Manipulate DenyList (through app or CLI)

- Disable again Enforce DenyList (because Shamiko requires that)

The fix will make it easier, making you able to manipulate DenyList (as a list of check-marked apps/processes) even when Enforce DenyList is disabled
[Magisk] pndwal:
I think it is checked however; there may be a number of 'safe' values not altered?

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

I didn't know this however! 👍

Thanks for heads up! 👍 PW
[Magisk] pndwal:
Nice spotting! Don't think I can add to your conclusions, but may be significant.

Comments from experienced log analyst(s)? 👍 PW
[Magisk] ipdev:
As I mentioned before, I have a habbit of playing in my own world when it comes to Android devices.

I run to the left when everyone else runs to the right. 🙃

With this commit 76ddfeb9, you can modify the Denylist by CLI without Zygisk enabled or Denylist enforcing.

Using the Magisk app, you still need Zygisk active to be able to modify the Denylist (enforcing or not).

Plus what ever you want to add to the list needs to be installed before you can add it to the Denylist.

By CLI you can preload the list with what ever you want to add.

Installed or not.

Same as it was before with MagiskHide and the HideList.​

​

Cheers. :cowboy:

PS.

I run personal (snapshot) builds of Magisk.

I do not hide my GitHub account.

Anyone is free to peruse my account as they wish.

I do not promote my snapshot builds since it was against John's wishes.

[UNOFFICIAL] next version Magisk and MagiskManager snapshots - [xdaThread] - Link
[Magisk] bege10:
Hello,

I saw that developers update their modules in the Magisk modules repo but that repo is not supported any more. Currently I stumble through Github to find updates.

The FoxMagiskModuleManager https://github.com/Fox2Code/FoxMagiskModuleManager supports also a second repo https://github.com/Magisk-Modules-Alt-Repo but that does not contain most of the modules of the official repo.

What do you do to keep the modules you have installed updated?

Could the module developers add their modules to the alternative repo? Or is there a convenient way for users to find updates?
[Magisk] zgfg:
That's it as you described

Yeah, developers should submit their modules to the new repository - if it would/to become the 'de-facto official' new repo

Otherwise you need to search for/monitor the Github pages for particular modules (of your interest) or even subscribe to their update/distribution Telegram channels or so

That's the current situation
[Magisk] zgfg:
Did anybody update to today's 76ddfebp Alpha from TG?

At the first glance I see no diff from 558710bb-3
[Magisk] traversone:
this release fixes the installation on (some?) armeabi-v7 architecture, now the boot patching is successfull!

but on Hades ROM, Zygisk is still not properly hided.

No regression on other (already working) systems.
[Magisk] martyfender:
For me, the magiskhide option is gone, unless it will show up again after disabling zygisk and rebooting. However, I don't have that other test device with me.
[Magisk] pndwal:
Not yet...

Changelog above. PW
[Magisk] zgfg:
Sorry, it's not your fault but frankly, those changelogs (for Alpha) are really of very limited use (problem is in the original ZH changelogs)

Compare the changlogs for previous 558710bb-alpha-3 and this new 76ddfeb9 - both posts quouted above

It's hard to see what exactly is new/changed in this latest release - 99% of items are repeated over and over for each new Alpha release

Several sections but no clear section /list what exactly is new/different in this 76ddfeb9 against the previous 558710bb-alpha-3

Or, am I missing something?