yashsingh1/xdaforums huggingface dataset:
[Magisk] Paulkw:
Thanks, I'm gonna try that, am I right to say that this shouldn't touch any data?

Edit: done, flashing boot image fixed it, thanks!
[Magisk] J.Michael:
Whether data is touched is hard to guarantee.

Some operations force you to factory reset / wipe data.

I believe some people, some times, are able to flash a full ROM without losing data. Of course, the more different the new ROM is from the current ROM, the less likely that you will get away with it.

There are lots of reports about people flashing just the boot image and not losing data. Sometimes that's a mixed blessing. Try that first.
[Magisk] Paulkw:
Yeah it worked, just flashing boot image and everything is there. I guess I was lucky with this one but it was close.
[Magisk] olivercervera:
Hi, I have a friend with a Zenfone 6 running OmniROM (Android 13), I installed there Magisk and PlayIntegrityFix.

He can use Google Wallet and passes Play Integrity Attestation.

However, some apps still refuse to work as they detect the device as rooted.

The same apps, on my OnePlus 8T running Nameless (Android 13), work perfectly, with the same Magisk setup.

- Magisk 26.4

- Magisk App is hidden

- Play Integirty Fix as module

- Deny list is enabled, all required apps are there

- Developer options are disabled

- ROM Props are correct (release keys and this kind of stfuff)

I can't understand what's going on. I don't think these apps are using Safetynet/PlayIntegrity and are detecting Magisk, but they work on my Magisk device!

If there's a troubleshooting step that I missed please let me know.
[Magisk] HRX1016:
Can't seem to install magisk (latest version, 23, or even older ones) to my Mi 11x (Alioth). It's on MIUI 14.0.5 (Global).

I have tried flashing zip / apk renamed to zip, and patching boot image as well.. After flashing i load into the system and there's just no Magisk like as if nothing happened. Installing the app manually also detects no Magisk installed. I've flashed it to both A and B partitions at this point to see if something works.

Magisk used to work without any issues a couple of months before, I do not know that happened. It could be since the Android upgrade for this phone.

I flashed using OrangeFox recovery for my device after decrypting my internal storage (using my lockscreen pin)

And for the patched boot image I used Minimal ADB/Fastboot on my PC.

It's a problem cause I don't have zygisk and yet some apps keep saying "This app is not supported on rooted devices"
[Magisk] J.Michael:
When you had Magisk installed and working, did you hide / rename the Magisk manager app?

Go through your app drawer. If you find any other Magisk manager apps, uninstall them.

Look up, install, and run TBChecker. It can supposedly detect hidden Magisk manager apps.

Maybe this has nothing to do with your problem. Another stumbling block is some systems suddenly reorganized their partitions so instead of patching the boot partition, you need to patch the init_boot partition. Search this thread for a clue to whether your system has this quirk.
[Magisk] HRX1016:
Yep it was hidden when I had it installed. But I can't find it in my list of "all apps" anymore... There are indeed two settings apps (com.xiaomi.settings and com.android.settings) but they have the same icon.

In trying to solve the problem I uninstalled magisk as well by using the latest .apk and renaming to uninstall.zip and flashing that.

Also I looked up TBChecker, naturally my play integrity fails but I don't know what the root checker results mean.

And I don't have init_boot
[Magisk] J.Michael:
I have never used TB Checker.

Somewhere in this thread I think there are posts of screenshots illustrating this mysterious ability to find renamed Magisk apps even after the owner has forgotten the name he chose or at least agreed to.

My first guess: the summary is backwards from what a root-hiding person thinks, so "Magisk specific checks: FAIL" means you failed because it did detect something. Try tapping on that to see if it gives more information -- I'm sure the screenshots of which I spoke showed clearly which app.

I do not think any amount of uninstalling Magisk, whether by pushing a button in the manager app, flashing an uninstall.zip, or flashing an unpatched boot image, will remove any Magisk manager app, whether hidden or not. Wiping data will remove a hidden manager app. Short of that, the only way you will ever be rid of it is by explicitly uninstalling it.

If you still have root capability, or if your TWRP has a file manager facility and can access /data, you can search all installed packages. The ones whose names appear to be gibberish are likely candidates for "hidden Magisk manager app".

If you can: run a terminal emulator, and use the "pm" command to list all packages.

From TWRP, try to examine the names of the directories under /data/data.
[Magisk] m0han:
Check these screenshots of my results on TBChecker.
[Magisk] J.Michael:
It doesn't seem to detect Magisk on your machine. I'm assuming the "Pass" with "com.topjohnwu.magisk" means it didn't find it.

The object of the exercise was to illustrate how TB Checker is able to find packages a user can't remember the name of. I think someone posted a screenshot of such a detection.
[Magisk] Giorgi-geo:
Yes I can use qfil to flash partitions. I needed fastboot to do "fastboot oem unlock", after that fastboot is not needed and I'm using qfil to flash modified images and such, I also tried flashing magisk modified boot image with fastboot but the result is the same.

I have not flashed complete rom, I haven't looked if it's available. I will try that. Flashing original rom and try again.
[Magisk] J.Michael:
What is "original ROM" that you do not consider it to be a "complete ROM"?

I got the impression that you had to modify several partitions to make fastboot available. Then you had to restore some of them before you could boot Android. I wanted you to flash the entire ROM package, which I assume will restore every partition on the device, just in case the problem was that one of the partitions had not yet been restored to its original state.
[Magisk] Giorgi-geo:
Nothing, I thought you meant to flash back to my original firmware and try again. What did you mean by complete rom?

Yes to get into fastboot I have to flash different bootloader and erase laf partitions. After I'm done with fastboot, to actually boot into android again I have to restore the bootloader.

I don't know what you mean by entire rom package. I do have all 100 individual partitions of my phone backed up, if that's what you mean. I can try and restore all of those, but the only ones I ever modified were the boot, abl and laf partitions, and I've restored them all.

To be clear about my problem, android boots and works fine, but as soon as I flash magisk modified boot image, it bootloops and I have to go back to original boot image to get into android.

Thank you for your responses by the way
[Magisk] J.Michael:
I was under the impression that most ROMs are distributed as a set of files to be flashed all at once to "install" the ROM. For my Samsung tablet, I downloaded a giant ZIP file. The ZIP file contained four tar files. Flashing the four tar files resulted in my tablet now being some Android version, some country code, etc.

I'm not convinced I found exactly what came on the tablet, but what I found was a complete system. I flashed it just to be sure I knew how to flash. (I flashed the French ROM so I could see the interface language change, reinforcing my belief that I was really flashing. Then, I flashed the English ROM back.)

The point of all this is so, no matter what I screw up, I can reflash the whole thing to restore the tablet.

I did not mean for you to change your ROM for the sake of changing it. I just hate the thought that you were downloading a few partitions from that thread, and had no way to make sure that all of the partitions were as they should be.

Did you manually save each of 100 partitions? I don't trust that. Was there nowhere that you could download the entire bundle?

On the other hand, I misunderstood your situation. If every time the device won't boot you can recover by flashing just one partition, the boot partition you tried to patch with Magisk, then maybe there's no reason to worry about the integrity of the other partitions.

It may be that you need a Magisk manager patching option that is not being set by default and that is not being offered in the UI. There have been words in this thread like "dm-verity" -- I never seemed to need them, I never learned what they meant.

Maybe you should be using an older version of Magisk. Does the thread that told you how to do all this mention a specific version? Try that, no matter how old it is.

Ask in the other thread whether your phone is right for those instructions.

Are you sure your bootloader is still unlocked? There are some pretty stupid interpretations of a few English words, like "bootloader" and "unlocked". It is conceivable that you are free to modify partitions, and that the bootloader then refuses to boot. One Samsung series could have Magisk installed; but not after taking the update that improved the bootloader to v4.
[Magisk] dimm0k:
getting a notification to update to 26402, but when I acknowledge it attempts to download and then I get the message "Error downloading file". any suggestions?
[Magisk] Nergal di Cuthah:
Looks like something with the server mine stays trying to find the latest version

Maybe temporary server overload?
[Magisk] Nergal di Cuthah:
Download it from the github worked for me. Distrubution server seems busy
[Magisk] final_triumph:
Hey, I've also got Xiaomi Mi 9T Pro with global stable MIUI 12.5.2 / Android 11. I experienced the exact same issue after upgrading Magisk from 25.2 to 26.4 using the direct method and unchecking recovery before (otherwise it would give me an installation error). Could you please tell me what steps I need to follow to revert to Magisk 25.2 and retain all data? I don't have TRWP installed (just default MIUI recovery) but I'm able to access fastboot and safe mode. In addition to that, I have 2 Magisk modules installed. Thank you very much.
[Magisk] Nergal di Cuthah:
Unroot (fully uninstall from big pink button) reboot then uninstall magisk app, then install old and reroot
[Magisk] final_triumph:
Sweet, thanks a lot!
[Magisk] mkcs:
Try long press the POWER button for around 10 seconds, this would force reboot your device. While it starts to reboot, long press the VOLUME DOWN button without release would bring you to the fastboot mode. You may flash back the stock boot.img and patch it with old Magisk.

Alternatively, you may switch to KernelSU for better root hiding:

[KERNEL][MIUI] KernelSU for Raphael (Xiaomi MI 9T Pro/Redmi K20 Pro+Premium)

/* I'm not responsible for any damage on your device, anything you did is at your own risk */ 20240529: Upgrade to ksu_11871 Integrated the latest KernelSU to Bool-X Kernel, built with neutron clang 19 Source...

xdaforums.com
[Magisk] final_triumph:
Really appreciate it, thanks!
[Magisk] gpvecchi:
Me too, any link to latest canary app, please?
[Magisk] pndwal:
The BIG one...

Latest Canary and Debug Magisk builds:

Magisk (1dcf3255) (26402)​

[Zygisk] Introduce new code injection mechanism

Diffs to v26.4​

[Zygisk] Introduce new code injection mechanism

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

BTW, it's native bridge loaded Zygisk... 👍 PW
[Magisk] Nergal di Cuthah:
Get it from the magisk github
[Magisk] J.Michael:
Isn't it worth trying to install desired Magisk as module before giving up root?

I do think he should disable all modules before changing Magisk (whether by uninstalling or installing different version).
[Magisk] xcl1pse:
I suspect him using inbuilt OG zygisk magisk which is broken on MIUI and such. Atleast he can try new canary version since commit for fix that problem already pushed by Wu
[Magisk] sawdoctor:
Trying to update through magisk app always stops halfway through the download. Downloaded the app from GitHub and tried to install but nothing happened, can't see it installed anywhere and it didn't show as an update either just a new app that isn't showing anywhere
[Magisk] xcl1pse:
Maybe the workflow is half finish?

I tested the link and it show that (see the image)

I also download the failed workflow and it's indeed bigger than usual..
[Magisk] J.Michael:
Who said "configured limit"?

browser? web site? download manager?
[Magisk] manjaroid:
For 'Error downloading file' try emptying your hosts file and/or pausing your ad blocker.
[Magisk] sawdoctor:
Unfortunately still getting the "error downloading" message when updating through the app unfortunately
[Magisk] Nergal di Cuthah:
Get it from the github, works fine
[Magisk] manjaroid:
Sometimes it's an error's error and the file was actually downloaded. If so you can tap install instead of cancel. If that doesn't help I don't know what does except wait it out. These two solutions helped me last couple times I saw that error.
[Magisk] badabing2003:
The issue is the file size limit configuration at cdn

The link is the following:

https://cdn.jsdelivr.net/gh/topjohnwu/magisk-files@7235d30bc73c16c953b1bc16e41bad1c962878c9/app-release.apk

And you get the following error:

File size exceeded the configured limit of 20 MB.
[Magisk] Nergal di Cuthah:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk

Also, this works
[Magisk] sawdoctor:
When i install that i don't get the message "install" rather than update. It installs but then disappears and doesn't show as being installed anywhere, can't find the app but I do get a popup about something being denied su privalgies
[Magisk] Nergal di Cuthah:
Did you unhide magisk before trying?
[Magisk] michasssxdd:
Works. Does Google Wallet Need to be Added to the Deny List? Hide from root?
[Magisk] zgfg:
No, it will not help to anything

Only GMS goes to DenyList
[Magisk] Utini:
This is still an issue after updating A14 to December build!

It only seems to happen right after the update but not with any further reboots after that.
[Magisk] J.Michael:
Do you have "Automatic Response" set in Magisk manager app Settings?

Do you recognize all the apps listed under "Superuser"? Both those enabled, and those disabled.

(I have a very old Magisk. The "shield" icon at the bottom of the first page took me to a page labeled "Superuser" and listing only three apps, two enabled, one disabled.)
[Magisk] Utini:
Automatic Response is set to "Prompt" but I didn't get a prompt.

Under Superuser are only 3 apps which I recognize and which are also all allowed to use root.

The weird thing is that in the logs (where you can see which app has been granted / denied root) all apps are listed with their corresponding name except the one that was denied which is just called [UID] 10348.
[Magisk] zgfg:
Longer press on that app in the list and take then Revoke (delete) - not disabling but removing from the list

Then launch, it should popup to ask for root grant
[Magisk] Utini:
On my list are only three apps which all can correctly get root when opened.

None of them is causing the log entry.

Logs -> Right Bottom Icon -> Opens log which lists the app that allowed/denied root access in the past

Everything looks normal unless this one entry which has no app name.
[Magisk] Nergal di Cuthah:
Out of curiosity what's in your denylist. Maybe the no name is hiding there.
[Magisk] Utini:
Oh good idea..:

com.android.systemui.plugin.globalactions.wallet

banking apps

2 factor auth apps

Firefox

Google (com.google.android.googlequicksearchbox

Google play protect service

Google play services for AR

google play store

google safety center ressources (com.google.android.safetycenter.ressources)

google services framework (com.google.android.gsf)

google support services (com.google.android.apps.helprtc)

.... all of the "sub processes" that are listed under the packages I just listed are also denied.

This should all be fine?

Again, seems to only happen on the first boot after flashing a build update.
[Magisk] philippe734:
Using Magisk since many years with success.

Today, my banking app refuse to start because my device is rooted.

Please, could you tell me how to do to continue using banking app with root?
[Magisk] zgfg:
When you long press, you don't have options like on my screenshot?

By using MiXPlorer you can open and edit

/data/adb/magisk.db

Ofc, MiXPlorer must be granted root.

Under Policies tab, long press on UID and Delete - 2nd screenshot

Or you can edit that db by sqlite3
[Magisk] Nergal di Cuthah:
It's a cat and mouse game with google, but you need Play Integrity Fix module, and maybe shamiko and/or Hide My Apps lsposed module.
[Magisk] J.Michael:
See which directory in /data/data is owned by the corresponding user

ls -l /data/data | grep -i u0_a348
[Magisk] pulpf:
Hello, I'm on the Canary channel and Magisk is offering me the December 04 update, which refuses to download.

Do you know why?
[Magisk] sawdoctor:
Yes the file is too large so fails to download. Download the apk from GitHub and update that way
[Magisk] zgfg:
I can't believe they didn't fix this download?!
[Magisk] philippe734:
You're right !

I updated Magisk, enabled Zygisk and installed the module "Play Integrity Fix" to fix SafetyNet.

Now my banking app works fine.

Thanks!
[Magisk] sawdoctor:
Make sure to follow the thread you linked and definitely pay attention to the OP. Pretty soon you'll probably have to find your own fingerprint to keep using PIF
[Magisk] pulpf:
Thanks, can I install over it or do I have to uninstall first?

Do you have the link to the right apk?

No I went to the github I clicked on magisk canary I have an apk that downloads but there is no version number.I'm not sure if it's the right one and it doesn't install over it so I don't know if I need to uninstall first.

Do you have a solution?
[Magisk] bombadier:
The version downloaded from github canary should be the correct version, do you have the magisk app hidden? If so unhide before installing, I didn't have to uninstall to update the app
[Magisk] sawdoctor:
Yep that was my mistake, not unhiding before trying to install the update
[Magisk] DF5JT:
Hello,

OnePlus 9 Pro with LE2125_13.1_0.591 worked fine with Magisk, but since updating to 592 as an OTA, Magisk refuses to work. What I tried:

Patching the image provided by https://xdaforums.com/t/guide-magisk-unlock-root-keep-root-oos-13-1-0-591.4252373/post-89187760 --> installed with fastboot, no errors, installed in slot _a, phone boots, but no root

Checked the logs of the patching process (https://pastebin.com/9hKk9RRs)

OS_VERSION [12.0.0] but OS_PATCH_LEVEL [2023-11] OS version definitely is 13, latest OxygenOS

cp: can't preserve ownership of 'busybox': Operation not permitted - (Last lines in log) I don't understand what it means and whether this might be the culprit

MD5 sums of unpatched and patched image are different, size, however, is exactly the same (201326592 kB) in both patched and unpatched

So I tried the alternative way: Found a working TWRP for the device that supports decryption, so I did

fastboot boot boot-twrp.img

and installed

Magisk-v26.4.zip Installation went through fine (supposedly), but phone boots without root

I am pretty much out of things I could think of. Read all the installation instructions thoroughly, did an insane amount of googling and xda-ing, alas, without any result.

Please help...
[Magisk] BillGoss:
Try using Magisk to manually patch a copy of your new boot image. Then, in bootloader mode, run fastboot boot <Magisk-patched image>

And, if you have root access after booting, use Magisk to do a direct install.
[Magisk] DF5JT:
I should have added that I have of course tried this. No, no root access, no installation option in the Magisk app.

Edit: Halleluja! I went back to installing Magisk V 24.3, after unsuccessfully trying the latest beta as well, which also changed the update channel to beta.

Well, installed 24.3 through TWRP recovery, installation went fine and it finally booted with root! Magisk app immediately complained about the outdated version and suggest a direct install of the latest version. I went along, thinking I might always be able to ignore this as long 24.3 works for me.

Nope, it now works. Magisk is now on version 26402, obviously the latest beta.

Me happy, but completely clueless what actually went on the whole time.
[Magisk] Nekromantik:
currently got magisk alpha and will start to use kernel su.

how do I change from magisk apha to kernel su on alpha? or do I need stable?
[Magisk] Nergal di Cuthah:
Neither of thos apps are covered by this thread (magisk alpha is a fork of magisk and has it's own thread, and kernalSU is a whole different creature). AFAIK both you need to unroot before switching to another.
[Magisk] zgfg:
For KSU, make sure that your kernel is compatible with.

You will need to fully uninstall Alpha - just like to uninstall Magisk, instructions can be found elsewhere and btw observe a big Uninstall button in the Magisk app.

For instructions about flashing KernelSU, check on their site
[Magisk] ipilcher:
Root on Android 13 without Magisk?

I know this is a weird question for this forum, but hear me out.

I've managed to mess up my Magisk configuration (combination of enabling MagiskHide module & disabling Zygisk), and my phone is now unable to run any apps when Magisk is installed. Attempting to start any app causes the UI to freeze until I return to the launcher.

I have temporarily restored some functionality by using fastboot to flash a Magisk-less boot image. However, this means no root access, so I am unable to run the (hidden) Magisk manager or access /data/adb.

I do not have access to /data from LineageOS recovery, and TWRP is not available for this device.

Thus, if I could get root in some way other than Magisk, I could remove the problematic module, and then I could reinstall Magisk.

Is there any other root solution for Android 13? SuperSU seems long dead, and Google searches all just point me to Magisk.

Any other ideas?
[Magisk] zgfg:
If you have root enabled for ADB, you can execute from PC while booting the phone:

adb wait-for-device shell magisk --remove-modules

Or once you boot, you can mark modules for disabling/removing (reboot afterwards)

adb shell su c- touch /data/adb/modules/<module folder>/disable

adb shell su c- touch /data/adb/modules/<module folder>/remove

Also, check on Magisk GitHub Documentation, about booting once to the Android Safe mode and then reboot normally - it should (but not working on all phones) disable all modules
[Magisk] ipilcher:
Unfortunately, adb root is disabled.

I will check the docs for the safe mode technique.

Thanks!
[Magisk] iXeNIV:
Hello,

I have Poco X3 NFC MIUI 12 Custom ROM (Xiaomi EU), was working fine on Magisk 26.1, I updated it to 26.4 after the reboot my phone bricked all I can do is unlock screen lock and nothing works or appears all black, can't read sim, how to fix that without wiping data, because I have a lot there.
[Magisk] Nergal di Cuthah:
I believe the instructions in the post two ahead of yours will fix

Magisk General Support / Discussion

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread

xdaforums.com
[Magisk] iXeNIV:
I tried 'Disable All Modules" for Magisk from TWRP, doesn't help, my phone connects to wifi after boot and unlocking screen, I can explore files using TWRP, so I am looking how to fix it without losing data what should I install and how? something like boot.img from stock rom or what should I do?
[Magisk] zgfg:
That command is for Magisk:

adb wait-for-device shell magisk --remove-modules

You call magisk to execute

If you boot to TWRP, there will.be no magisk to execute, hence no use of the command
[Magisk] iXeNIV:
Well I used stock rom boot.img to fix boot and it worked, now I can't use WiFi doesn't turn on, looked for V12.5.5.0.RJGMIXM_v12-11 Xiaomi eu rom to use its boot.img, can't find a mirror. Any help please.