Magisk General Support / Discussion

[amk316]

Yup, Magisk daemon will restore (rebuild) Magisk config files on bootup if deleted, and has similarly, for some time now, detected if Magisk app is missing and restored stub app at boot time if necessary.

In recent months I've noticed this has stopped functioning (removed / regression?), and I actually searched to see if it was removed on purpose... Couldn't find a commit, so guessing it was a regression, and it has been fixed or reinstated again here in any case:
Install stub if necessary
(topjohnwu committed 7 days ago)

So sorry, this is a feature, but I wondered myself if it is really necessary for the same reasons as you... I don't know how it can be easily bypassed... PW

the rebooting is not the problem, i do it once a week and delete magisk app stub
but now every time i run an app with root access the stub appers without rebooting my phone
and some banking apps didactic that my phone is rooted

 

[Huyqwerty]

Hello, I heard that Magisk is systemless so I cannot modify file permission, am I correct ?

 

[zgfg]

Hello, I heard that Magisk is systemless so I cannot modify file permission, am I correct ?

You cannot modify if FILE SYSTEM is read-only on your phone (mostly for the phones released with A11 and newer, for the system partitions)

If File system on your phone is not read-only, you can still modify everything on the phone with root.
Hence if you have an old device,with old Android, sky is your limit

Hence it's not a 'defect' on the Magisk side. Magisk just provides Systemless mechanism (mounting over instead of overwriting) on devices where system-as-root comes read-only (not just that but there is no free room left) to overcome that limitation.
Because with root, you can still not change the SAR filesystem characteristics

But even if you have that old device/Android, you can still use the Systemless mechanism (all new modules use it, you like it or not), because it's safer - your real system partitions will not be affected - just boot without Msgisk

The whole story is not so easy but you can further search, read, etc

 

[Huyqwerty]

You cannot modify if FILE SYSTEM is read-only on your phone (mostly for the phones released with A11 and newer, for the system partitions)

If File system on your phone is not read-only, you can still modify everything on the phone with root.
Hence if you have an old device,with old Android, sky is your limit

Hence it's not a 'defect' on the Magisk side. Magisk just provides Systemless mechanism (mounting over instead of overwriting) on devices where system-as-root comes read-only (not just that but there is no free room left) to overcome that limitation.
Because with root, you can still not change the SAR filesystem characteristics

The whole story is not so easy but you can further search, read, etc

So is there any way I can overwrite files ?
Or disable scoped storage ?

 

[zgfg]

So is there any way I can overwrite files ?
Or disable scoped storage ?

As I said, the whole story is more complicated than yes or now

Pls read my edited prev answer

 

[J.Michael]

So is there any way I can overwrite files ?
Or disable scoped storage ?

If you have Magisk installed, you can get the effect of "replacing" or "inserting" files. I think if you make your own copy of an existing file, and change the permissions on the copy, it will have the effect of changing the permissions on the original.

For your own use (i.e., not for distribution), there is very little to making a module: just pick a name, make a directory "/data/adb/modules/m-name", then reproduce the directory structure of the file you want to replace or insert.

Read the document on creating a module.

 

[Huyqwerty]

As I said, the whole story is more complicated than yes or now

Pls read my edited prev answer

Ok, thank you for your support

 

[Huyqwerty]

If you have Magisk installed, you can get the effect of "replacing" or "inserting" files. I think if you make your own copy of an existing file, and change the permissions on the copy, it will have the effect of changing the permissions on the original.

For your own use (i.e., not for distribution), there is very little to making a module: just pick a name, make a directory "/data/adb/modules/m-name", then reproduce the directory structure of the file you want to replace or insert.

Read the document on creating a module.

Thanks for the advice

 

[m0han]

So is there any way I can overwrite files ?....

not sure if these apply to your case. wouldn't hurt to check, i suppose

[SCRIPT][Android 10+] Universal Mount SystemRW / SuperRW featuring MakeRW (read/write)

If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeni line SystemRW / SuperRW (feat. MakeRW) v1.32 by lebigmac NEW VERSION COMING SOON! STAY TUNED!;)(y) ANY TALENTED DEVELOPERS...

forum.xda-developers.com

[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition

Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...

forum.xda-developers.com

 

[pndwal]

Definition of rumor
(Entry 1 of 2) 1 : talk or opinion widely disseminated with no discernible source. 2 : a statement or report current without known authority for its truth. 3 archaic : talk or report of a notable person or event. 4 : a soft low indistinct sound : murmur.
- Merriam-Webster

eg, Magisk 25 coming... PW

 

[pndwal]

Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (bf04fa13) (24314)​

• [App] Fix language switch
• [MagiskSU] Handle system_server restarts to prevent UID reuse abuse

Diffs to v24.3​

• [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
• [MagiskInit] Introduce new sepolicy injection mechanism
• [MagiskInit] Support Oculus Go
• [MagiskInit] Support Android 13 GKIs (Pixel 6)
• [MagiskBoot] Fix vbmeta extraction implementation
• [App] [MagiskSU] Properly support apps using shared UID
• [MagiskSU] Fix a possible crash in magiskd
• [MagiskSU] Prune unused UIDs as soon as possible to prevent UID reuse attacks
• [MagiskSU] Verify and enforce the installed Magisk app's certificate to match the distributor's signature
• [MagiskSU] Handle system_server restarts to prevent UID reuse abuse
• [Zygisk] Fix function hooking on devices running Android 12 with old kernels
• [DenyList] Fix DenyList on shared UID apps
• [BusyBox] Add workaround for devices running old kernels

https://github.com/topjohnwu/magisk-files/blob/4cc20a9dfb66ddd96b88499c0f4fffeee357afe8/notes.md

PW

 

[pndwal]

D is for disambiguation:

PW

 

[ipdev]

Just for the record.

Indicate debug builds - commit.

Closes issue 5,859.
Nice one pndwal

Cheers all.

 

[MDG-VN]

Guys, after i was flashing magisk patched, my phone restarted and open up download mode again, and it shows vbmeta error on top left conor. I was panicked until i reflash a stock rom. Is this a bug or my fault? My phone is Samsung Galaxy A30 (SM-A305F)
(unlocked bootloader)

 

[m0han]

Latest Official TJW debug Canary (release) & Debug (debug) Magisk builds...

If you can, please include md5 checksums in your posts about new magisk releases.

8f28251215f99a3e185b7759abdc18cf is what I got for the latest release.

 

[Stillhard]

Just for the record.

Indicate debug builds - commit.

Closes issue 5,859.
Nice one pndwal

Cheers all.

Yes, saw that, and a quick one too, never happen to his other issue(s)/request(s)
Let's call him Gandalf from now on, he'll help us to keep away from 'the tower of telemetry' pull

 

[pndwal]

Just for the record.

Indicate debug builds - commit.

Closes issue 5,859.
Nice one pndwal

Cheers all.

Thanks Doc... Bit more where that came from, coming soon:
More debug indication in UI …

D is for done deed.

POC:

... It's all happening now it seems... Not like me to spread rumors but. PW

 

[ipdev]

Thanks Doc... Bit more where that came from, coming soon:
More debug indication in UI …

D is for done deed.

POC:
View attachment 5626199

... It's all happening now it seems... Not like me to spread rumors but. PW

You are a commit behind.

Interesting..
It does not recognize my custom update channel as debug.
My update channel is a fork of magisk-files.



So not quite D is for done deed yet.

Cheers Mate.

 

[pndwal]

You are a commit behind.

Interesting..
It does not recognize my custom update channel as debug.
My update channel is a fork of magisk-files.

View attachment 5626643

So not quite D is for done deed yet.

Cheers Mate.

Mmm... You sure?

TJW's link in last (not fully fixed) debug JSON:

"link": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app-debug.apk"

Yours:

"link": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app-debug.apk"

This is Zachery same! ... (gotta edit JSON to make it call your hosted fork doc.)

----​

There seems to be one small issue remaining however; Debug Stub may not be properly indicated.

If user doesn't un-hide App before moving to Debug, stub isn't always (ever?) updated. (Currently retains (29) instead of fetching (30).) Since debug built stub now differs from release build, clearly with:
App Installed bf04fa13 (24314) (29) (D)
Stub installed is still release build while App is debug, but there is no seperate indicator for stub.

Here, I have same actions build installed, set channel to Stable and took Hide the Magisk app, so Stub is release build:

This has debug built Stub:

There is no clear distinction between Stub build types, and clearly the common (D) does not apply despite appearing to.


I did note this inconsistency in last issue as side note.

PW

 

[ipdev]

Mmm... You sure?

TJW's link in last (not fully fixed) debug JSON:

"link": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app-debug.apk"

Yours:

"link": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app-debug.apk"

This is Zachery same! ... (gotta edit JSON to make it call your hosted fork doc.)
<SNIP>

Yep.
My fork includes (and updated) with the official links.

Did you notice the additional file.

Spoiler: snapshot (e4094c0ca)

"link": "https://cdn.jsdelivr.net/gh/ipdev99/[email protected]/app-debug.apk",

<SNIP>
There seems to be one small issue remaining however; Debug Stub may not be properly indicated.

If user doesn't un-hide App before moving to Debug, stub isn't always (ever?) updated. (Currently retains (29) instead of fetching (30).) Since debug built stub now differs from release build, clearly with:
App Installed bf04fa13 (24314) (29) (D)
Stub installed is still release build while App is debug, but there is no seperate indicator for stub.

Here, I have same actions build installed, set channel to Stable and took Hide the Magisk app:
View attachment 5626707


I did note this inconsistency in last issue as side note.

PW

The stub version only shows if magisk (apk) is hidden (renamed).

Since the stub is only used when the full app is not installed, there is no reason to show the stub version of the full app.

Cheers Mate.