yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
Can you deactivate the Intune app as a Device Administrator?

Will that be less trouble than uninstalling Intune?
[Magisk] J.Michael:
Was your original Magisk installation a Canary version?

There have been posts about a misalignment of the "update channel" settings resulting in endless nagging about a need to update, but no update being possible.
[Magisk] Rcedude:
Thanks a lot :)
[Magisk] Bouls:
Yes this is what I was doing in general, but now for the latest magisk version, I cannot flash disable dmverity forceencrypt.zip and then flash after it magisk.zip. I get an error "Unsupported boot image extra"
[Magisk] n.p.:
HELP! This release (25.1) has become an absolute disaster. Of my first device, I did direct install as recommended, but upon rebooting, I had no Magisk, just the app. After some struggles, I managed to patch a raw boot image and flash that.

On my second device (with 24.3 installed and working for months). I again tried direct install, and Magisk appear to install, as normal. Again, after I rebooted, I had no Magisk (the app simply says "Installed: N/A"). I tried patching the boot image (several boot images actually, older patched ones, ones backed up from TWRP, and one extracted from the latest firmware - every one of them produced the same output file, meaning that all of the magisk_patched-25100_xxx.img had the same sha256 value). Every attempt keeps producing "Installed: N/A" after flashing the patched boot image.

I would like (for now) to go back to the old version (24.3) but attempting to install it produces "Please connect to the internet! Upgrading to full Magisk is required." If I connect to the internet, I get version 25.1 again (app only, and still no Magisk).

Any ideas? Thank you in advance for your help.
[Magisk] huskydg:
The author of Magisk is currently positive for covid (post on twitter) so the development process might be delayed
[Magisk] pndwal:
Seems you have stub app (not original Magisk app) installed... That's what Hide the Magisk app does; uninstalls Magisk App, installs stub, populates its data with "full Magisk" binary...

Updating w/ app 'hidden' is supposed to work, but, as reported here often (and in my experience) it only works 50% of the time in practice w/o issues... If you hid app(s), my bet is that you'll find conflicting renamed stub ('Settings' or whatever you named it) in system settings, Apps... Uninstall these instances and try with correct corresponding full Magisk app...

If this isn't your issue, please give some details about devices... model, OS, Android version... PW
[Magisk] pndwal:
Aside from what I already told you about Direct install (and I believe this applies to custom ROM zip installation also if updating previously installed Magisk rather than flashing over unrooted system) being broken / producing this type of error due to refactored MagiskInit when updating from 24.x or less, I see you have Galaxy Note 9... Despite launching with Android 8.1, since updating to Android 10 you now have 2SI "SAR" device, so you should read and follow Samsung (System-as-root) instructions:

https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

- Just ignore the statement "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section"...

Is your recovery twrp-3.6.2_9-0-crownlte?... Doesn't it decrypt /data?

🤠 PW
[Magisk] zgfg:
The only components I upgraded in the last weeks are:

- Magisk Canary

- USNF

- Shamiko (same if using instead Unmount DenyList))

- Momo (but I also downgraded Momo but did not help)

wngraded Momo but did not help)

All the rest, except for apps over Google play are not touched.

I checked Google Play System Update, it's still May 1, 2022 - well before Momo started to detect su

The whole mystery is in Magisk, Zygisk, Shamiko whatever

TG, I don't have any sensitive app on the phone to start complaining about the root but frankly, with every new round of refactoring or revolutionary improvements, root detection becomes more vulnerable - I wonder why people who really want to run sensitive banking apps or so, that frantically follow all upgrades here. Seems that old technologies (eg MagiskHide in Delta) provide more: root but less vulnerable to detections

Pls don't respond that preventing root detection is not TJW's business - we all know that. I'm talking from the users perspective, not from his or his employers perspective
[Magisk] zgfg:
You really overlooked that post (and the discussion it was followed by)?

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87031661
[Magisk] Bouls:
That's the same thing I did bro, I got my stock AP and patched it in magisk then flashed the firmware with this patched AP using odin. But my data is still encrypted, I cannot see my internal storage in twrp, yes I have the latest twrp install and it doesn't ask me to decrypt /data, I cannot access data
[Magisk] pndwal:
Then difference between our results is probably your Android 11, 2SI, custom XiaoniEU(?)... I have 10, LSAR, stock MIUI...

True... at least every WIP change requires remedial action which can be W...I..............P too! 😜

Also, Zygisk itself is just out of beta... Guess we shouldn't expect hide for Zygisk era Magisk to mature overnight...

Sure...

Why would I say that? 🙄... He's only threatened to force root detection! 😁

www.twitter.com/topjohnwu/status/1452188664780500995

😜 PW
[Magisk] pndwal:
Saw the member post... Never saw the TJW comment... PW
[Magisk] zgfg:
Yes but there is no difference between me and me - I had and still have the same MIUI 12.5.8 with A11, on the same A/B device, etc

And those detections were not showing like ten days ago. That's what's bothering me
[Magisk] rodken:
Did you at least attempt to:

-- The first thing to try is if somehow your internal storage became encrypted when using a legacy screen lock method.

-- Go to your Android device’s Settings > Security > Screen Lock, and change your screen lock method to either Pass or Pin.

-- Create a new one.

-- Reboot into TWRP, and it should ask for a password – enter the pass or pin you just created.

-- TWRP will attempt to decrypt your device’s internal storage, and if it succeeds, you should not have further issues.

-- However, if this does not solve your issue of “unable to mount data, internal storage 0mb”, continue with the rest.

-- Reboot your device into TWRP again.

-- Navigate to Wipe > Advance Wipe > Data, and choose Repair or Change File System.

-- Press Repair File System to see if this fixes the issue. If not, continue.

-- Press Change File System, choose Ext2, and swipe to confirm.

-- Now switch back to Ext4 and swipe to confirm.

-- Go back to TWRP main menu, then the Mount menu, and check if your partitions can be mounted now.

-- If you are still unable to mount your partitions, you need to repair Internal partition, which will most likely wipe your storage.
[Magisk] n.p.:
I had never done the Hide the Magisk app, but the issue does seem to involve remnants of something. The first time i tried to uninstall it (using Settings / Apps / Magisk), I then attempted to install via adb, and received a warning the app already existed. I then uninstalled via adb, and attempted to install after that (no warnings, but something still not working).

Later, with 25.1 supposedly installed again, I noticed in F-Droid (I have never used F-Droid to install Magistk, but of couse it reports the existence of any app with the same name as one in its repository) that it still reported 24.3 installed. So, I used F-Droid to uninstall Magisk (why not?), but then, after reloading F-Droid, it still reported version "1.0" as installed. So, I uninstalled that as well, and F-Droid no longer reported any Magisk on the system. I searched through System / Apps (even with Show system enabled), and saw nothing that I did not recognize. I installed the 25.1 apk downloaded from github again, flashed the patched boot image again, and... same result (Magisk just shows as N/A).

I do notice that if I attempt to install Magisk 25.1, I get the full app (Settings / Apps shows Magisk as 23.42 MB), but if I install 24.3 (working perfectly until a few hours ago), it initially shows as 22.80 MB, but the first time I attempt to start it, it crashes immediately, and then the icon changes to the generic Android icon, and the size in Settings / Apps changes to 224 KB.

The device (a Teclast T10 tablet with the exact model number of E3C5) has the latest stock firmware (1.05_20180306) built from Android 7.0.
[Magisk] n.p.:
I have made some progress here without understanding any reason why.

I randomly noticed this post directed torwards another user, and I had a similar problem with the inability of TWRP to mount data.

I have never had a screen lock on this device, but I decided to go through the repair steps, which did completely wipe everything from the system (I do have recent backups of all of the important apps, but might have lost some other things I don't care too much about). So I set up USB debugging again, and installed the Magisk 25.1 apk again. Much to my surprise (without flashing anything additional), it showed Magisk 25.1 as installed, though it did want to reboot to complete the installation. I verified that Magisk remained installed after the reboot (it did), but then In went into settings, enabled Zygisk, and rebooted again. That brough me back to the previous state (no Magisk installed and TWRP could not mount /data). I could only proceed by reformatting /data (again), setting up USB debugging (again), installing Magisk (for about the 20th time today), and noting (again) that the app shows Magisk 25.1 as installed without any additional flashing (though, again, with another reboot required).

Obviously, I will avoid Zygisk for now, but I would appreciate some enlightenment regarding a way to recover from this in the future (without having to reformat data), and guidance on the timing of the ability to use Zygisk safely (I do have an app on this device that I need to hide root from).
[Magisk] flostie74:
Hi maybe somebody can help me here. I installed magisk on my LOS. I downloaded the 25.1 apk and renamed it to .zip and flashed via recovery. So far so good. But iam unable to see any packages. It just shows "no modules installed". Am i missing something?
[Magisk] zgfg:
Did you have any module installed - it should be showing

On the other side long ago, since Magisk v24, Magisk app does no more connect to Repository. Its in the Changelog and really been asked and answered hundredth of times here

You can install a module if you already have it downloaded (from eg GitHub). Or search back to find about Fox Magisk Module Manager app
[Magisk] rodken:
Maybe, uninstall Magisk by TWRP - then reinstall Magisk again.
[Magisk] Timmmmaaahh!:
Or boosted, actually :D
[Magisk] flostie74:
Okay so there is no online installer of modules anymore? Thanks for the clarification.
[Magisk] zgfg:
There is, extra app Fox MMM
[Magisk] razes:
I've flashed recently CSC file and lost the root. I updated MAgisk app up to 25.1 version (not a zip file just apk) but still no root. I have flashed Magisk 25.1.zip file in TWRP recovery. Now the phone is rooted, but I unable to start Magisk app. It just stuck on the start (The Mask). I tried to uninstall Magisk app via Application manager, and reinstall it following by reboot. Still Magisk unable to start. I don't remember whether MAgisk was unhidden before the update and zip installation. What should I do next?

Should I rename the Magisk.apk to uninstall.zip and run this file in TWRP. Then install Magisk apk and install zip file from within Magisk App? If so, what the best way to install MAgisk App; via TWRP or File Manager?

Samsung Galaxy S5

Marshmallow 6.0.1
[Magisk] pndwal:
I'm guessing flash CSC = factory reset? Did you do this in Odin w/ other needed binaries incl. AP?...

Strange issue... Do you have issues starting other apps? Tried clearing its app data?...

Also, try deleting everything in /data/adb and rebooting to rebuild Magisk config files... Use TWRP if you can't use a root explorer...

Hidden app would be gone if did factory reset...

If installed since, check in device settings, Apps for 'Settings' (default name) or whatever you named it. Uninstall if found...

Install app like any other .apk from 'unknown aources'...

👍 PW
[Magisk] zgfg:
After having no luck with Shamiko or DenyList Unmount, I now run without of them and with Enforce DenyList enabled

I still have the same Momo detections (su, Zygisk, Magisk) but bystem boots evidently faster and runs (hard to be sure since the phone is fast anyway) maybe even more fluid then with Shamiko
[Magisk] dohanin:
Hi all, just some sharing on my experience in the past week.

I updated Magisk from stable 24.3 to 25.1, everything seemed fine.

Then noticed there were updates of USNF and Shamiko, which are the only modules I use, then I updated both.

Then the latest Momo reported nothing found (only bootloader unlocked), so all looked good.

However, in my Work profile, Zimperium zIPS detected ROOT! This is the last thing I want because it will automatically reports to my company that I'm using a rooted device to access company mails, etc. :_(

I reverted USNF and Shamiko to the previous versions, still no luck.

Then a full uninstall of Magisk, followed by installing 24.3. Then latest versions of USNF and Shamiko.

Well, Momo this time reported Zygisk found. Then zIPS only reported App Tampering instead of ROOT.

Ok, reverted Shamiko from 0.5.1 to 0.5.0, then App Tampering is gone too. So, everything back to normal for me (except Momo reporting Zygisk, which I don't care!)

So Magisk 24.3, USNF latest, Shamiko previous (0.5.0) works for my device to defeat zIPS.

Edit: Momo only detects Unlocked Bootloader for me in this setup.

Just some sharing :)
[Magisk] pndwal:
Assuming 25.1 binary is installed, this seems to be intended behaviour for 25.1+ daemon:

[General] Enforce the Magisk app to always match or be newer than magiskd

(Commit:

Force app version not lower than daemon)

This issue seems strange however, and may warrant a GitHub issue ticket... Do what you can to ensure no stub is installed first however...

Type Magisk -c in terminal emulator to see Magisk binary version installed, or Magisk -v to see daemon version running...

Note that since 16.6 we had

[Daemon] Check whether a valid Magisk Manager is installed on boot, if not, install stub APK embedded in magiskinit

This has been working in older Magisk, but seems to be removed / broken in 25.x on my device... I'm guessing you've been getting stub installation on boot after removing full app w/ 24.3 binary installed...

Anyway, check you are installing full app matching installed binary and stub is not present...

Nb. There have be many recent tweaks for app loading, signature checks, stub functions etc, so you are ikely experiencing some regression... More changes are coming too, eg this is already merged in TJW master but not yet built in a release:

Build dynamic stub resource APK at runtime ...

Close #6013

Co-authored-by: vvb2060

topjohnwu and vvb2060 committed 8 days ago

🤠 PW
[Magisk] pndwal:
Yup... But boost = catalyst for Oxidation... he's excited about Rust... 😛

2 commits in his CXX (interop) repo, 1 in ONDK (w/ rust tool-chain), and 6 in Rust (Programming language) Custom and fix-lid branches in last 10 hrs...

Of course this is all still relevant!:

www.twitter.com/topjohnwu/status/1538462758332575744

... and he's been studying Rust for more than a year... good to see such commitment being distilled now for Android modders benefit!

Seems open source & equally committed contributors / collaborators have also allowed him to do this...

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

Linus says Rust is coming to the Linux kernel "real soon now... Rust is a way to try something new. And hopefully, it works out, and people have been working on it a lot, so I really hope it works out because otherwise they'll be bummed."

https://www.theregister.com/2022/06/23/linus_torvalds_rust_linux_kernel/

Seems Rust is coming to Magisk injection for kernels 'real soon now' too... If Rust is a way to try something new, hopefully it works out for Magisk too... John's clearly been working on it a lot, so I really hope it works out... because we don't want to be given the bum's rush...

😷 PW
[Magisk] HippoMan:
... nor the bum's Rust.

(Sorry, couldn't resist!)
[Magisk] pndwal:
... Now in Magisk repo... Sooner than I thought!...

Setup preliminary rust infrastructure

topjohnwu committed 1 hour ago

Rain setting in... Covid setting in... Rust setting in...

May need some WD40... Go John!

😀 PW
[Magisk] traversone:
other Shamiko release (.117) but no significant improvement at my end...
[Magisk] pndwal:
Covidtime = downtime?... Nah! It's Dreamtime... For the TJW-CPU, uptime! -

www.twitter.com/topjohnwu/status/1542633717495083008

😴💭💡😝 PW

Maybe it's a game to him... "The RUST sleep command will allow admins and moderators, upon issuing the command, to instantly put themselves into sleeper mode. Once they're in sleeper mode, they are required to press any button on their keyboard or mouse to wake up."

https://www.corrosionhour.com/rust-sleep-command/
[Magisk] 73sydney:
Theres no stopping him

Theres a rumour he can actually see Ponkles in real time
[Magisk] Finnzz:
Issue fixed
[Magisk] dl200010:
I have a question about OTA incremental updates. I have a OnePlus 9 on OxygenOS 12 C.48. C.61 is now being pushed out. Oxygen Updater no longer offers the full updates and is telling me to use incremental. Everytime I updare with incremental I get a boot loop and have to factory reset to be able to boot again, of course losing all data. Is there some new way we are supposed to update with incremental? The following is how I usually try to do it.

1. Magisk > Uninstall > Restore Images

2. System Settings update (DO NOT REBOOT)

3. Magisk > Install > Install Into Inactive Slot (After OTA)

Am I missing something? I do not have any modules installed, except Systemless Hosts. I have read that I should disable modules. Should I just restore images and complete uninstall Magisk?
[Magisk] ipdev:
Yes.

The /data/adb directory will be created the next time you boot a magisk patched boot image.

There might be a few extra magisk files in /data (magisk backup files).

If you installed magisk by flashing in recovery and you ROM supports addon.d scripts, there will be a Magisk script in the /system/addon.d directory.​

Use the App Info section to uninstall the Magisk app.

Normally long-press the icon and you will get an option for info or, go though system setting, Apps.

Use app info to Force stop, clear cache and data then uninstall the magisk app.​

---

Then reboot with your stock boot image.

Install Magisk (app) and patch your stock boot image.

Reboot with the new Magisk patched image.

Cheers. :cowboy:
[Magisk] Finnzz:
Thank you, I got it sorted. I forgot to I was using an incompatible magisk boot image. Once I switched that out everything was working again. Two hours wasted on that lol
[Magisk] meric57:
Hello, how does it work well there is this package ddgv.cdb that normally there was John Wu.com.
[Magisk] zgfg:
OMG

'Hiding' Magisk app does repackaging (changing package name to random).

Unhide if you don't like and don't hide in the future (or get to know and understand that renaming package to random helps to hide it from banking and similar apps)
[Magisk] meric57:
Good evening zgfg, thank you so as I hid magisk as proposed setting so it comes from this package of its name.
[Magisk] zgfg:
I don't know where is the problem. How hiding works and what it does and everything about has been mentioned and discussed literally hundredth of times in this thread

And one of the XDA forum rules (and not only on XDA) asks that people read and learn before asking. Hence it really makes no sense to ask about something absolutely basic and to be surprised about, and for others to waste time teaching that hiding the Magic app will rename it's package name and what for
[Magisk] martyfender:
Your posts are very difficult to understand due to problems in proper translation.

Maybe others here will have suggestions about getting a better translator?
[Magisk] meric57:
Good evening Martyfender, Thank you Google translator if there is better I take.
[Magisk] shoey63:
If you are on the latest version of Magisk (some previous versions had issues), and no other partitions are modified other than boot and you reboot from within Magisk manager after flashing to other slot, then that should work.

I take OTA updates on Pixel 6 that way.
[Magisk] shoey63:
Pretty sure you would have had to learn English when you were at school in your country. France is it?

Maybe try without Google translate. Can't be much worse.
[Magisk] dl200010:
I last did it with 24.3 Magisk and it boot loop. Am I supposed to turn off the module I have? Systemless Hosts.
[Magisk] shoey63:
Not necessarily, but you DO need to update Magisk to the latest version as I mentioned.

Edit: Disabling modules before taking an OTA update and re-enabling later is a good idea. It eliminates them as the cause of boot loops.
[Magisk] martyfender:
The problem may be with proper English grammar and punctuation. I am trying to help us better understand your posts so as to better help You.

Suggestion:

"Good evening martyfender. Thank you. I am using Google Translator, unless someone can suggest a better alternative."
[Magisk] dcarvil:
I think your posts would be easier to understand if you included the original French below the English translator output. From the forum rules:

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
[Magisk] dl200010:
I am on 25.1. Last time I tried to update using OTA incremental was with 24.3.
[Magisk] pndwal:
Please say if you are doing anything different, eg use custom kernel, change Verity flags (options) etc... Also, what is current Magisk version and update version...

Method looks fine. - ie. recently fixed method here:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md#devices-with-ab-partitions

How are you rebooting after updates?... From Magisk App? ... This may be important:

Nb. Direct Install to 25+ from earlier Magisk will fail where previous Magisk installation (ie. method of injection etc) is no longer supported. This does affect OnePlus in particular it seems, and is a result of change from patching fstab in 2SI devices

on 2SI devices, we patch fstab and execute the original `init` to mount partitions for us.

to patching original init

on 2SI devices, we patch the original `init` to redirect the 2nd stage init file to magiskinit and execute it to mount partitions for us.

https://github.com/topjohnwu/Magisk/commit/4f1a1879e572891bc005b489f82421303f602f72?diff=split

In these cases, a fresh install (patching previously unpatched image) will work, and Direct updates should work again going forward.

As I understand it, this shouldn't affect Install to Inactivate Slot method, but I guess it's possible Magisk may carry over some settings / flags from the previous slot installation, so this might help / apply...

I put information on this here:

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

Hope it provides clues... PW
[Magisk] pndwal:
... So it may be connected to new init injection method (see my post above)... It'll be interesting to see if Install to Inactive Slot method is sorted going forward... PW