yashsingh1/xdaforums huggingface dataset:
[Magisk] Skrjorge9:
Now that i installed twrp and installed the magisk apk doesnt happen nothing from this what i do now?
[Magisk] zgfg:
Of course. You still did not install Magisk

Magisk app is an app that everybody can install, Bootloader does not need to be unlocked for

Please, please , please, search here on XDA and find another, new thread (opened as a clean start for Magisk v24)

I.e, sesrch on XDA for Magisk and Zygisk and read the OP posts there (post #1 and the following posts at the beginning, by the same author)

There you will find all info you need how to install and set-up the new Magisk v24
[Magisk] Skrjorge9:
Oooohhhhhh thank you now i have it with the magisk hero brother thank you so much
[Magisk] pndwal:
John's been very busy with, and has just released major libsu update 4.0.0 w/ multiuser support! 🎉🎊 !!

www.twitter.com/topjohnwu/status/1498231468631347200

Changelog:

4.0.0​

Improvements / Bug Fixes​

[service] Add multiuser support

[service] Add new APIs returning Shell.Task to allow launching root processes with your Shell instance of choice.

[core] Prevent a possible deadlock

[core] Support creating Shell instances with custom Process

[io] Support setting a Shell instance to SuFile. This shell will also be used if the SuFile is passed to open SuFileInputStream and SuFileOutputStream streams.

Behavior Changes​

[service] The way how "Daemon Mode" services work has changed. This change is required to work with multiuser. Please check the Javadoc of RootService for instructions on how to launch daemon services and more information about its behavior.

[core] Shell.rootAccess() no longer requires the main shell, so it is now non-blocking. Replaced with a best-effort heuristic that guarantees no false negatives. Please check its Javadoc for more details.

Breaking Changes​

[core] The core module now requires at least API level 19

[io] The I/O module now requires at least API level 21

[io] SuFileOutputStream.openNoCopy(...) APIs removed as those are irrelevant on API 21+

[io] SuFileInputStream and SuFileOutputStream constructors removed. Please use the corresponding open(...) static methods.

[service] RootService.attachBaseContext(Context) is made final to prevent breakage. onAttach(Context) is provided as an alternative.

Deprecation​

[core] I have received too many feedback that the Shell.su/sh(...) APIs are extremely confusing. Those APIs are now all deprecated, replaced with Shell.cmd(...). Shell.cmd(...) is 100% the same as the original Shell.sh(...); the API is just renamed to a less misleading name.

[service] RootService.createBindTask(...). Replaced with RootService.bindOrTask(...). Will be removed in the next release.

https://github.com/topjohnwu/libsu/blob/master/CHANGELOG.md#400

This particular (proper) fix is a result of Canyie's discovery of busybox issue causing Magisk not detected (N/A) issue in Samsung and other devices:

https://github.com/topjohnwu/libsu/pull/99

... Guess John may now pick up on Magisk proper again... 😄 PW
[Magisk] TheKara:
Hello,

Sorry if this topic has already been covered in this thread.

I can't upgrade to Magisk 24.1on my Samsung Galaxy S7 (with ALEXNDR ROM).

If I do (via update directly from the app or by flashing the ZIP in TWRP) I lose root.

I can still go back to version 23 by flashing it from TWRP.

I have "Cannot find vbmeta partition, patch vbmeta in boot image" error when I flash for which there is indeed a ticket on gitlab

Do I have to wait for this ticket to be solved?
[Magisk] pndwal:
Probably best as seems to be same issue...

I'd comment w/ your details in that thread; participants will be notified and it may get more priority...

Actually, that issue may be better than one opened for your device on custom ROM; issues with stock are usually resolved in good time. 🙂 PW
[Magisk] lcsboy:
I did a test, just uninstall 24.1 from TWRP and install 23.0 from TWRP.

After booting on 23.0, the boot time is fast.

Then update 23.0 to 24.1 from Magisk Manager, then reboot, the boot time is also fast.

After I enable Zygisk from Magisk Manager, then rboot, the boot time takes a long time.

Does anyone have the idea?
[Magisk] zgfg:
Current status:

FoxMmm includes modules from three repositories - Magisk repo (old/original), Androidacy and Alt Repo

However, Androidacy does no more include/copy modules from Alt Repo but only from the old Android modules repo (and modules submitted directly to them)
[Magisk] pndwal:
...and wadayaknow... first Magisk commit in 12 days!:

Update libsu

topjohnwu committed 2 hours ago

😛 PW

Edit: Make that 5 hours ago, and now two more!... Johns stirring his pot again... smells good...
[Magisk] zgfg:
It's been long ago since I updated from v23 to v24 (and gradually through 2301x Alpha and Canary versions, adding Zygisk, Shamiko, LSPosed, HMA...)

Over that time I also upgraded to A11

But indeed, on my 2,5 years Xiaomi Mi 9T (A11) booting takes very long and even after I enter the unlock pin and my SIM pin, the phone is still terribly slowly responsive for about a minute (I better have to leave it for a minute or two after booting, before starting it to use).

Eg, I specially noticed that yesterday upon updating Shamiko.

I have tested to compare booting with stock boot.img (no Magisk) and it was a way faster

However, on my new Xiaomi 11 Lite 5G NE (almost the same configuration) that is not noticable (must be due to the faster processor).
[Magisk] m0han:
Is there a version newer than v0.4.3-102 that was released in Magisk Alpha TG Channel 11-Feb?

answering myself: v0.4.4-106 at https://github.com/LSPosed/LSPosed.github.io/releases

edit: also in fox's mmm
[Magisk] zgfg:
For me, it's still the easiest way to check Update buttons in Magisjlk app, Modules

If Update button is ungreyed/active, update for the module is available.

Click, read ChangeLog, download or install

Of course, module must support updateJson mechanism, but eg Shamiko and Zygisk-LSposed do support

It will not include unofficial daily/automatic builds for LSPosed, pushed only to their TG channel
[Magisk] pndwal:
FWIW, I think next builds of many modules will support this. Eg. support already merged downstream for USNF... PW
[Magisk] pndwal:
Latest TJW Canary:​

Magisk (9968af07) (24103)​

[MagiskBoot] Support lz4_legacy archive with multiple magic

[MagiskBoot] Fix lz4_lg compression

[Zygisk] Fix application UID tracking

[Zygisk] Fix improper umask being set in zygote

[MagiskSU] Fix command logging when using su -c <cmd>

[MagiskSU] Prevent su request indefinite blocking

[App] Major app upgrade flow improvements

[General] Improve commandline error handling and messaging

Diffs to v24.1​

[MagiskSU] Fix buffer overflow

[MagiskSU] Fix owner managed multiuser superuser settings

[MagiskSU] Fix command logging when using su -c <cmd>

[MagiskSU] Prevent su request indefinite blocking

[MagiskBoot] Support lz4_legacy archive with multiple magic

[MagiskBoot] Fix lz4_lg compression

[DenyList] Allow targeting processes running as system UID

[Zygisk] Workaround Samsung's "early zygote"

[Zygisk] Improved Zygisk loading mechanism

[Zygisk] Fix application UID tracking

[Zygisk] Fix improper umask being set in zygote

[App] Fix BusyBox execution test

[App] Improve stub loading mechanism

[App] Major app upgrade flow improvements

[General] Improve commandline error handling and messaging

https://github.com/topjohnwu/magisk-files/blob/0ef3837e3b400d4a751dd7cfb0acdd19d2f01959/notes.md

👍 PW
[Magisk] pndwal:
Is Hide the Magisk app broken in 24103, or is it just me? PW
[Magisk] dohanin:
it kept showing error in downloading when hiding the app... then i manually kill it, and restart and install again, it then ok
[Magisk] pndwal:
For me,

Device: Xiaomi Redmi Note 8T

Android version: 10

'Hide the Magisk app' function fails for me with never-ending 'Hiding the Magisk app' message.

This occurs with or without internet access. PW
[Magisk] dohanin:
do you have any ad-blocking like adaway, netguard, etc? i also disabled it as some old posts suggested this.... not sure if it's related this time though
[Magisk] zgfg:
Thankfully, it's easy to support updateJson mechanism

(My modules, available also through Alt Repo / Fox Mmm, do support the Update mechanism for a loong time)
[Magisk] vandyman:
I had the same problem on my Pixel 6.

It would error while downloading.

So I rebooted and opened the manager.

The app version was updated and I was able to continue using a direct install of Magisk system.

Odd.
[Magisk] zgfg:
Canary 24103, hidden/repackaged as shown on the screenshot

I enabled Install over USB in Developer settings - now I remember I've seen two or three weeks ago some discussion that 'automatic' installation would not be allowed in Magisk (Canary) anymore but didn't know it would translate to that Install over USB (for MIUI)

Fortunately, I already knew from another case about that Install over USB

PS: Then also successfully Restored Magisk app
[Magisk] klemi71:
Does libsu update have to be updated manually or is it included in latest Magisk canary?
[Magisk] pndwal:
How would you update it manually?; Only source is released...

libsu is "A complete solution for apps using root permissions". Magisk (App) is such an app and implements libsu to call busybox etc.

It has also just been updated:

https://github.com/topjohnwu/libsu/releases/tag/4.0.0

and latest Canary builds w/ ver 4.0.0 also:

Update libsu

🙂 PW
[Magisk] pndwal:
So I see you've somehow managed to hide the Magisk app using older (working) stub version (from previous builds)... Are you able to hide with this build - (24103) (26)? PW
[Magisk] zgfg:
I simply updated Magisk Canary to 9968af07 (24103), updated Magisk by Direct method and tested hiding/unhiding

On the stupid MIUI I had to click/allow several things (Unsecure source, Install from USB, Allow chain to start - the most irritating thing introduced with MIUI 12.5) but eventually I hid the Magisk app successfully.

And similarly unhid (I just wanted to test, I never keep the Magisk app.hidden - I use HMA and/or the Freeze app instead)

With little bit different clicks it worked both on my Xiaomi 9T (MIUI 12.5.2) and 11 Lite 5g NE (MIUI 12.5.8), both A11

On 9T it even complained about Play Protect but I chose Install anyway and made it

On 11 Lite 5g NE I did with Airplane mode, on 9T I didn't bother switching to Airplane mode (I was chatting over WA in parallel)
[Magisk] pndwal:
No... And as I said, it doesn't work with network disabled either, which should work since we got 'use local stub when download is unavailable'... 🤔 PW
[Magisk] pndwal:
Interesting, but since you only seem to have old stub (25) working for hiding, I still want to know if latest (26) works on both of your Xiaomi devices; ie, does v26 break Hiding the Magisk app for some MIUI / Xiaomi devices? ... I know old builds worked! 😆 PW
[Magisk] zgfg:
I don't know why the screenshot shows 25, but you see it was already updated to 9968af07 (24103) app (and Magisk)

And my previous version I did update from was 1a1b346c (24102).

I did the update unhidden, since I never use Hide in the real life

But after hiding/unhiding the app, it doesn't show now the stub number at all, only 9968af07 (24103) - probably that's usual, I never pay attention to
[Magisk] pndwal:
So it shows stub version used / installed, just like Magisk & App...

If un-hidden of course it doesn't show stub version as it's no longer installed... 'Latest' shows available versions as (Magisk version) (stub version), and when installed, Installed stub version should match 'Latest'...

So you are hiding w/ previous (working v25) stub... Since you say you updated w/ app un-hidden I'm guessing you somehow got old stub installed with your 'install over USB'... PW
[Magisk] Randomginger:
Good Evening, Night, Morning, Afternoon or wherever you maybe in your day.

I'm running LOS 18.1 on Razer phone with Latest Magisk and it's all sweet except 2 issues. I don't know if this can be Magisk or ROM related, Google maps goes crazy at start up, then defaults to a massive DPI on the screen, it works but everything is enlarged. My camera will not start up, it will run with blank screen, but not display anything.

When I update OTA, both camera and Maps work, as soon as I re-install My patched boot.img the problems return.

I've posted in RoM thread too to try and figure out what's causing this craziness.
[Magisk] zgfg:
Did now again on 11 Lite 5g NE, with WiFi, stub shows 26

Watch the screen-recordings:

0 byte folder on MEGA

mega.nz

Hiding takes long, be patient and watch till the end
[Magisk] pndwal:
Thanks mate! ... I'll try again; will leave it running while my plaster dries and report... Let me know how it goes on older device... PW
[Magisk] pndwal:
FWIW, Latest Unofficial vvb2060 Alpha Magisk (For Mavericks only!); Chinese translated:

# alpha changelog

## Magisk (39e714c6-alpha)

- [App] Support SharedUserId

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Compatible with Android 12L

- [MagiskInit] Refactor the processing method of two-step startup

- [App] Added crash statistics

- [Script] Support init_boot partition

- [App] Allow loading zygisk modules

- [App] Try root installation first

- [General] Fallback to rw mode after ro mount fails

### how to install?

Magisk is installed and uninstalled through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool.

By customizing Recovery is not a supported way.

# Upstream changelog

## Magisk (9968af07) (24103)

- [MagiskBoot] Support `lz4_legacy` archive with multiple magic

- [MagiskBoot] Fix `lz4_lg` compression

- [Zygisk] Fix application UID tracking

- [Zygisk] Fix improper `umask` being set in zygote

- [MagiskSU] Fix command logging when using `su -c <cmd>`

- [MagiskSU] Prevent su request indefinite blocking

- [App] Major app upgrade flow improvements

- [General] Improve commandline error handling and messaging

## Diffs to v24.1

- [MagiskSU] Fix buffer overflow

- [MagiskSU] Fix owner managed multiuser superuser settings

- [MagiskSU] Fix command logging when using `su -c <cmd>`

- [MagiskSU] Prevent su request indefinite blocking

- [MagiskBoot] Support `lz4_legacy` archive with multiple magic

- [MagiskBoot] Fix `lz4_lg` compression

- [DenyList] Allow targeting processes running as system UID

- [Zygisk] Workaround Samsung's "early zygote"

- [Zygisk] Improved Zygisk loading mechanism

- [Zygisk] Fix application UID tracking

- [Zygisk] Fix improper `umask` being set in zygote

- [App] Fix BusyBox execution test

- [App] Improve stub loading mechanism

- [App] Major app upgrade flow improvements

- [General] Improve commandline error handling and messaging

https://github.com/vvb2060/magisk_files/tree/alpha

👀 PW
[Magisk] martyfender:
Despite it not being on github, I updated it directly in the magisk app without downloading it from telegram. Also, I installed the update in the already hidden app with no problems with hiding or having 2 apps installed.

This was on my 2 Onn 8 Android 9 tablets.
[Magisk] pndwal:
Ah, thanks, you're right! It is on GitHub... edited post above...

https://github.com/vvb2060/Magisk (alpha) is still showing Feb 17 version, but https://github.com/vvb2060/magisk_files/tree/alpha is up to date w/ update JSON... PW
[Magisk] pndwal:
Well, enabled Developer 'install via USB', tried again... Still 'Hiding the Magisk app' after a half hour. 🙁

Did you succeed w/ older device (Redmi Note 9?)? ... Could be an Android 10 thing... PW
[Magisk] zgfg:
As I said, I did it also on Mi 9T. I have no other device

Actually, on Mi 9T it sometimes failed straight away, then next time worked.

Recorded two successes Hide, Hide1 and Restore and uploaded to the same share:

0 byte folder on MEGA

mega.nz

I tried that second time - I thought that maybe it finishes earlier but that some pop-up is obscured and waiting in the background - but it was not the case

Btw, I have decent WiFi 5g/Optics, 192 Mbps Download (with no Jitter and Loss) - screenshot, no reason for hiding to download so long from that side

Hence something is really strange and wrong in this new Canary now regarding to the hiding
[Magisk] pndwal:
Shana just said "This is MIUI's bug"...

https://github.com/topjohnwu/Magisk/issues/5503#issuecomment-1056264807

🙁 PW
[Magisk] pndwal:
Latest TJW public Beta Magisk:

2022.3.1 Magisk v24.2​

Maintenance release fixing various issues.

[MagiskSU] Fix buffer overflow

[MagiskSU] Fix owner managed multiuser superuser settings

[MagiskSU] Fix command logging when using su -c <cmd>

[MagiskSU] Prevent su request indefinite blocking

[MagiskBoot] Support lz4_legacy archive with multiple magic

[MagiskBoot] Fix lz4_lg compression

[DenyList] Allow targeting processes running as system UID

[Zygisk] Workaround Samsung’s “early zygote”

[Zygisk] Improved Zygisk loading mechanism

[Zygisk] Fix application UID tracking

[Zygisk] Fix improper umask being set in zygote

[App] Fix BusyBox execution test

[App] Improve stub loading mechanism

[App] Major app upgrade flow improvements

[General] Improve commandline error handling and messaging

👍 PW
[Magisk] sansanc:
Installed magisk 23.0 apk from magisk.us, but then i saw 24.2 on github, so i reinstalled using that one on both slots. And it boots only to recovery. No system :/

Oops, my phone is a oneplus 8T. Android 11.

2nd edit: I also updated magisk itself.

Any ideas?
[Magisk] pndwal:
Latest TJW debug Canary Magisk:

Magisk (7cfce9ff) (24201)​

Sync with public release

Diffs to v24.2​

None

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

👍 PW
[Magisk] zgfg:
So far Beta 24200 and Canary 24201

Did you maybe test, any better or worse regarding to Hide Magisk app (on MIUI) - supposidely, nothing for now
[Magisk] pndwal:
Yup, changed symptoms but still fails:

https://github.com/topjohnwu/Magisk/issues/5503#issuecomment-1056862809

Shana found MIUI errors in my log:

https://github.com/topjohnwu/Magisk/issues/5503#issuecomment-1056971520

vv changed the issue title from 'Hide the Magisk app' fails, to 'MIUI doesn't allow Magisk to install apk'.

It hasn't been closed, so that's a good sign... PW
[Magisk] J0nhy:
Hey there, is there a way to bypass zelle app? I've tried everything but can't get it to send money, it detects my device has been tempered in someway and doesn't work, I'm using a pixel 6 android 12 rooted, thanks in advance... btw I'm on the latest canary as of now and using shamiko instead of the enforce denylist on magisk, thanks again
[Magisk] J.Michael:
Is the appearance of Maps affected by the Android Settings Display Font Size?
[Magisk] Randomginger:
No it is not. This is the only app that has display issues, along with the camera blank screen.

I tried changing the refresh rate settings and completely lost my display at 50hz, so I've done a whole new install. Maps works, camera works, install latest magisk with latest usnf. Same results, bonkers maps and no camera.

I'm baffled.
[Magisk] Miha87:
[Help] hiding root from my banking app does not work

Hey, I have a problem with using my banking app skb. I have a Xiaomi mi 9 with evolution x rom android 11, Magisk 24.1, and Shamiko v0.4.4(106) module by LSPosed, my phone passes all the safety net checks. I also checked my banking app on DenyList, but when I launch the app, it says my device is rooted. Later I tried a different banking app, not for my bank and all worked well, I don't know what to do now. Someone's got a clue what to do.
[Magisk] pndwal:
@zgfg, MIUI Users with 'Hide the Magisk app' failure:

I now have a workaround allowing successful migration to hidden Magisk app with this pointer from vvb2060. 🙂:

https://github.com/topjohnwu/Magisk/issues/5503#issuecomment-1057286025

As I mentioned to her, 'Turn on MIUI optimisation' does not show on opening Developer options for my device w/ MIUI 12.0.4. However, I was able to see the option as follows:

By scrolling to the option 'Reset to default values' under AUTO-FILL, then clicking this 4 times, 'Turn on MIUI optimisation' is displayed as the second-last option. Nb. This process is required to display the option every time Developer options is opened.

So I have now been able to disable 'Turn on MIUI optimisation', select / complete 'Hide the Magisk app' process without issue, then go back and re-enable 'Turn on MIUI optimisation'. 👍 🎉

I commented in the issue ticket:

https://github.com/topjohnwu/Magisk/issues/5503#issuecomment-1057479843

I'll wait and see if anything more comes of this...

Hope this helps MIUI users! 😛 PW
[Magisk] J.Michael:
If you have read all the posts here and in the Zygisk-Magisk thread, maybe try the "Hide My Apps" module -- it takes some effort to set up, but there are reports of great success.

You could uninstall the Magisk Manager app -- not Magisk, just the Manager app -- to see if that helps.

You could try accessing your bank with a browser.

You could change banks.
[Magisk] pndwal:
Some basics:

- Generally no need to add playstore in denylist!

(SafetyNet process itself, in Google Play Services, will be hidden by Universal SafetyNet Fix - if you don't run USNF and MagiskHide Props Config w/ configured fingerprint as modules we can safely assume ROM integrates these fixes).

- Check you have Play Protect Device is certified in Playstore settings.

- Ensure you have cleared bank app's data AFTER adding to denylist and checking points above.

- If still failing, app may be detecting Magisk app (despite being hidden / obfuscated). An number of apps, eg S-PushTan do this by various tricks). @J.Michael's suggestion above re. HMA will likely help in this case; To test if this is happening, simply uninstall Magisk app, clear bank app's data again (need to do this every time you test in case it caches previous detection), and try it. Nb. Magisk root, settings, modules etc are preserved as stored in /data/adb, not app data...

- Install Momo app for an idea of modifications / suspicious traces (aside from apps) bank may detect; Nb. I can no longer hide 'root' from S-PushTan app on my stock MIUI device, even with HMA, presumably because we can't hide Unlocked Bootloader w/ MIUI at present... Method is still working for users of other devices where Momo can't detect unlocked bootloader... so you may just be stuck because of Xiaomi, but evolution x ROM may bypass this issue; try it!

- much more info in:

Magisk and MagiskHide Installation and Troubleshooting guide

here: MagiskHide - Hiding root and passing Safety Net

🤠 PW
[Magisk] pndwal:
So two things:

I believe LOS OTA's may not be delta (incremental) updates (full ROM?), so it may be ok to take update without restoring unpatched image(s) first ... This will generally cause havock w/ stock OTA updates though ...

HOWEVER - You say you are re-installing your patched boot.img??? ... I assume this is the PREVIOUS one!? 😬

Boot image needs to match ROM in use! ... Do you know update didn't include boot image? ... Generally this is a no-no! ... Official method is the download current ROM, extract boot image and patch / use that ... You may be able to do this with your last LOS OTA, or download matching version ... If you have TWRP, you can also take a backup of boot image immediately after OTA (not now for you though 🙃), locate and patch that. (Can rename it, but I believe it works even w/ .win extension.)

I suspect this may account for the craziness ... Many also have network / BT issues if using unmatched (older) boot images ...

Anyway, if this is what you have done, flash matching Magisk-patched image to eliminate this cause before troubleshooting further...

🤠 PW