yashsingh1/xdaforums huggingface dataset:
[Magisk] J.Michael:
If you truly do not understand anything, then I question whether you should continue to pursue this project.

If you ask a specific question, you might get an answer.

If you have succeeded in getting a version of Android to run in an emulator, then from there on the emulator should be behaving like a phone (assuming you configured the emulator to behave like a phone). I would expect that from that point, you just follow the instructions you have found for doing things to the phone, but you use your emulator.

I'll admit, I do not know what you should do when the instructions say "hold the Bixby button" and there is no Bixby button on the emulator. Maybe at that point you should take another look at the choices you already made, and start looking for information pertaining the device you are actually emulating. Or rebuild the emulator configuration to emulate another device. Maybe after reading some of the posts in this thread to see if particular phones have particular problems doing what you are trying to do.
[Magisk] -Happy Feet-:
Hello,

Strange things happen on my Google Pixel 6 Pro.

I updated the custom ROM, after that I patched with Magisk 25.1 the boot.img.

But magisk wont detect root. Then I tried to flash the latest Radioactive Kernel with Ex Kernel Manager. During the flash the log tells me that the current kernel is patched with Magisk.

It seems that magisk can't detect the patched image.

Here some logs.

What can I do, without wiping the phone?
[Magisk] huskydg:
Magisk logs when no root is useless, please attach dmesg, logcat and magisk logs (if /cache/magisk.log exists)
[Magisk] -Happy Feet-:
It seems the logcat reader has root.

https://cloud.dasnetzundich.de/s/D67o5BRfs3P3MTo
[Magisk] huskydg:
Don't see any useful thing, please check if `/sbin/su` or `/system/bin/su` exists
[Magisk] -Happy Feet-:
/system/bin/su there. It seems it's an symlink to ./magisk
[Magisk] -Happy Feet-:
It seems magisk can't detect root.

Apps like termux, AFWALL+ has root. But apps fresh installed can't get root.
[Magisk] zgfg:
It's not 'strange'. There have been hundred of similar posts - and solution(s)

So please take time and read through this thread
[Magisk] -Happy Feet-:
Got it fixed. I uninstalled magisk with adv uninstall then downloaded the latest canary build. Patch the image again und suddenly it works.

But why it works now, I don't know. Only different is the adb uninstall command.

🤷
[Magisk] martyfender:
More than likely you had 2 managers installed, one not hidden and one hidden. The one hidden is named settings by default, unless you renamed it.
[Magisk] -Happy Feet-:
Maybe
[Magisk] Pandemic:
On xperia 1 iii with android 12 with magisk 25.1 we have constant a pop up we have an update of Android but we have the latest update and with magisk 24.+ We didn't have that, so why we get that ?
[Magisk] czerwinski76:
Hi !

Since Yesterday, Sunday 17th of July, Pokemon Go, Ingress, Pikmin Bloom, Mario Kart Tour, Pokemon Masters EX and Dragalia Lost can't be use with the latest version of Magisk with Android 11/12.

Games of broken with a rooted phone @topjohnwu.

Notice that Niantic games are playable on a rooted device with Android 7.
[Magisk] martyfender:
@huskydg Updating to the latest debug in your update channel resulted in recents missing. Running the direct install method a second time solved it. Do you have any idea why?

Onn 8 1st gen, Android 9.

Thanks
[Magisk] pndwal:
Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (f42c089b) (25102)​

[MagiskInit] Fix a potential issue when stub cpio is used

[MagiskInit] Fix reboot to recovery when stub cpio is used

[General] Better data encryption detection

[General] Move the whole logging infrastructure into Rust

Diffs to v25.1​

[MagiskInit] Fix a potential issue when stub cpio is used

[MagiskInit] Fix reboot to recovery when stub cpio is used

[General] Better data encryption detection

[General] Move the whole logging infrastructure into Rust

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

👍 PW
[Magisk] ionuutzuu:
Hello, I used magisk + debloat module to uninstall some of my unwanted apps and somehow I removed something useful for the system and now my phone is in bootoop. The model is Poco F2 Pro and I don't have any official twrp so it booloops too, tried custom vbmeta.

Any ideas how to fix it? I have lots of things on it and I don't want to loose them. My os is official miui V13.0.4.0.SJKEUXM

Thank you very much...
[Magisk] J.Michael:
On the off chance that your problem involves a Magisk module, you could try booting into Safe mode. If that works (or if having tried to do that, the next boot works), you might get control long enough to permanently disable all modules until you can figure out the problem. (I'm recommending booting into Safe mode to try to disable Magisk modules; if you are suddenly able to boot, that's an indication that the booting problem is related to a module.)
[Magisk] pndwal:
Latest Official TJW public Stable (release) Magisk build:

Magisk​

2022.7.20 Magisk v25.2​

Maintenance release fixing various issues.

[MagiskInit] Fix a potential issue when stub cpio is used

[MagiskInit] Fix reboot to recovery when stub cpio is used

[MagiskInit] Fix sepolicy.rules symlink for rootfs devices

[General] Better data encryption detection

[General] Move the whole logging infrastructure into Rust

Full Changelog: here​

https://topjohnwu.github.io/Magisk/releases/25200.html

🎉🎊 PW
[Magisk] pndwal:
Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

Magisk (9b61bdfc) (25201)​

Sync to public release

Diffs to v25.2​

None

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

👍 PW
[Magisk] pndwal:
State of the Magisk (master) Mind July 2022

www.twitter.com/topjohnwu/status/1549232442258513920

On ya mate! - you're a trooper. 😛 PW
[Magisk] pndwal:
... What's on the Magisk-mind / Current Agenda

www.twitter.com/topjohnwu/status/1549232443906936832

www.twitter.com/topjohnwu/status/1549448200741720064

👍 PW
[Magisk] zgfg:
Again, Magisk GitHub, Wiki - three methods are described how to disable Magisk module(s) - if debloating was Systemless, when you disable the module, all debloates apps will be there again

Those three methods involve TWRP or Android Safe mode or adb command - there is a chance that one will be applicable and work on your device
[Magisk] m0han:
An 'unofficial third-party fork' of Magisk has a few extra options. These could come in handy, I guess.
[Magisk] samhhmobil:
Hi,

I just want to go a few days back, it was discussed here, but I didn't see a solution here.

S-Check (in the PlayStore known as Security Check) results in "root detection not passed".

My configuration:

Xiaomi Mi10T lite (gauguin)

Bootloader unlocked

LineageOS 19.1

MindTheGapps-12.1

Magisk 24.3,

shamiko

USNF

MagiskHidePropsConfig

results in Playstore certified

SafetyNet passed

CTS passed

but S-Check detected root.

Changing Magisk to "Magisk Delta 25.1"

with MagiskHide enabled (again) results

in exactly the same, even with zygisk and shamiko, and even without zygisk/shamiko.

What's to do now, that root will no longer detected? Any new idea?

Many thanks, samhhmobil
[Magisk] huskydg:
Set sys.oem_unlock_allowed to 0. Use "resetprop -n" instead of "setprop" for safety!
[Magisk] samhhmobil:
Thanks, you're great! That works. Now everything is "green".

But after each reboot it's set back again to 1.

Nevertheless...

the german health insurance app TK even now detects root (the tests are done after successful login in the app, not when starting the app).

Magisk (Delta) App is hidden, and even freezing the (hidden) Magisk does not help. No TWRP installed on this phone.

Is someone here, who got it working? I don't have any new ideas... I don't know, where are the traces that are detected.

Thanks again, samhhmobil
[Magisk] NeutralKaon:
Hi there!

First off, thanks for Magisk and associated – they're brilliant, useful apps and I am so very grateful they exist.

I have Magisk 22 installed on an Android 10 rom on my "daily driver" phone. A banking app complained about this, and I used MagiskHide to both rename the app (required) and hide it. Unfortunately, the renamed binary manager doesn't work – it appears on my launcher, but not if I do `pm list` and if I tap on the launcher I don't get a result – nothing happens, although the shortcuts are there.

In adb shell, the binaries are still there -- I can su and call magisk/magiskhide -- but I can't get the manager to reinstall. Installing the apk doesn't seem to work (it installs but can't detect the su binary) and I can't seem to give permissions to anything - the UI overview has stopped working and 'su' in termux just hangs.

I think I've got three options to proceed:

– (1) Disable magiskhide with the command line, reinstall the latest magisk apk from github and then use an sqlite command to manually give privs to it (help!) to get root.

– (2) Reinstall the appropriate version 22 apk and do the above

– (3) Flash "something" from twrp

Any advice very welcome. I've also written an SO post about this (link) so sorry if that counts as cross posting!
[Magisk] huskydg:
If you use delta, use the latest
[Magisk] pndwal:
Bit confused by "A banking app complained about this, and I used MagiskHide to both rename the app (required) and hide it."... Guess you mean used MagiskHide to hide root from bank app, and Hide the Magisk App to obfuscate Magisk App... (Nb. There is no Manager in 22.0+, only App! - Manager existed before single-package apk-archive Magisk. - https://topjohnwu.github.io/Magisk/...agisk-manager-is-deadlong-live-the-magisk-app )

Anyway, sounds like you have both full Magisk app and hidden stub app competing; updating with App hidden often fails resulting in dual apps... Locate all instances in device settings, Apps (stub app is sometimes not visible in launcher view. Hidden App will be 'Settings', or whatever you named it...) and remove one or both... Reinstall one if necessary...

Hope it helps. 👍 PW
[Magisk] huskydg:
@pndwal You can build Magisk app with custom name and label as you want
[Magisk] pndwal:
Sure... But why? PW
[Magisk] NeutralKaon:
That helped hugely. Thank you for giving me the confidence to boot the stub app – after uninstalling it and running magiskhide disable in a shell magically the (newest) magisk apk was able to detect it and "come back to life". I guess magiskhide successfully hid magisk from itself >_<.

Thanks! Hopefully this story is useful to someone else too.
[Magisk] samhhmobil:
Same behavior with Delta 25.2

Sigh...

TK again detects the phone as "unsecure (f.e. rooted)". Maybe it's the existence of TB on the phone? Can one app see the existence of others? Or the unlocked bootloader? How to avoid that?

samhhmobil
[Magisk] pndwal:
Generally you never need to download stub; it will be called/installed by unhidden app when taking Hide the Magisk App.

But updating is fraught / various problems arise trying to update with it stub in place /App hidden. Works smoothly on my device perhaps 3 times in 10 (and it's not a new issue; seems it may always have been that way)... Easy to fix if aware of what's happening though...

Tip: For your sanity, take Restore the Magisk app before updating Magisk App...

You'll need to add obfuscated app again (even if you choose the same name) in HMA if you use it, but you'll need to do that if things go awry updating w/ app hidden anyway...

Well no, but the Hide the Magisk app function did this due to update glitch...

Did you update to latest Magisk?

Please don't confuse MagiskHide with Hide the Magisk App. - These were always two different things... MagiskHide is also now gone in 24+ (sunsetted by John as it circumvents device state detection by spoofing/altering/manipulating non-Magisk related signals and traces), but some MagiskHide code lives on in DenyList ("Bye MagiskHide. Long Live MagiskHide").

New MagiskHide is available through 3rd party modules, Shamiko being the defacto solution now...

This is one of the most common issues fielded here!

Glad it got you sorted... 😛 PW
[Magisk] huskydg:
MagiskHide is still effective to hide root from banking apps. It's not dead if you don't care about safetynet stuff.

Shamiko is taking off your panties on the basic of MagiskHide. So MagiskHide is still better.

You believe Shamiko too much, It can't really hide zygisk, only fix the zygisk detection of Momo. However, I can't blame it because that was the nature of zygisk and it will never be fixed.
[Magisk] pndwal:
Still not sure what you're trying to tell me...

I think we agree on most of this stuff (except your apparent impression that Shamiko Devs have some sort of sexual agenda, or that it's users are somehow prone to 'self abuse'... I won't use the other term either...).

If you think I have misrepresented any facts regarding Magisk, Shamiko or other, please say it plainly... I think what I provided for the sake of clarity was accurate... 🙁 PW
[Magisk] gorman42:
I've updated my OnePlus 6T to LineageOS 19.1. Previously I had Lineage 18 and Magisk installed, with root. Magisk was hidden and I forgot to "unhide" it while updating (don't know if this is relevant but I try to provide complete info).

So I followed instructions on LineOS page, updated firmware to the latest, as suggested, installed the new build of Lineage, installed new build of Gapps. Phone reboots and all is working. Then it's a matter of getting root again, as I've done tens of times, after each system update.

I go to Magisk, select LineageOS original boot.img, get patched version in Download folder.

Got to fastboot mode, run "fastboot flash boot patched_boot.img" and get the usual

fastboot flash boot magisk_patched-25200_9g8Xz.img

Sending 'boot_b' (65536 KB) OKAY [ 1.405s]

Writing 'boot_b' OKAY [ 0.297s]

Finished. Total time: 2.573s

Reboot the phone and... Magisk states it's still not installed. No root. I search the internet and I find people suggesting to delete the "hidden version" that I in fact find on my phone, with the name I chose back then. I uninstall it and repeat the whole process, no luck.

What can I do? What am I missing?
[Magisk] zgfg:
After uninstalling that old, previously hidden version of Magisk app, did you check that you really only have this new app now?

From Terminal, test:

magisk -c

It will tell you do you have Magisk (not the app).installed and which version

Provide also the screenshot of your Magisk app, main window, showing the versions/NA for Magisk and the app
[Magisk] gorman42:
Hmmm... I have Termux installed but "magisk -c" gives me " no command magisk found". Maybe I don't know what you're referring to by "terminal", sorry for my ignorance.
[Magisk] gorman42:
This is the screen you requested.
[Magisk] rodken:
Termux

-- su
-- enter
-- magisk -c
-- enter
[Magisk] zgfg:
Termux should be ok but I remember that some users had problems with path (Termux is very powerful but maybe requires some familiarity - there are other Terminal apps that usually work out-of-the-box) and it also did not found Magisk although Magisk was installed

You could also try:

su

but its actually symlinked to Magisk, hence it will be the same result

Have you ever used Termux and did then su comnand work for you?

Do you have any app that you know it requires root, and you previously granted it root - then test with that app does it still work now with root privileges or not (like root explorer like, eg.MiXplorer or so)

It could be that you do have Magisk but the app does not see, or that you really don't have if you flashed the patched img to the wrong boot_[a/b] partition in case your device is A/B or something
[Magisk] gorman42:
That's ok, I downloaded a different terminal emulator.

Output of magisk -c is:

25.2:MAGISK:R (25200)
[Magisk] zgfg:
This means you do have Magisk v25.2 Stable (and I suppose you really did flash that)

Uninstall Magisk app (only app), reboot, install Magisk app and check does it see
[Magisk] gorman42:
Ok, this is interesting.

Both CF.Lumen (nowadays it works only with root) and MiXplorer (I am browsing root now) appear to be working as if root is installed.

I was trusting Magisk info and RootChecker (that states "Sorry! Root Access is not properly installed on this device"). Even AdAway successfully modified the hosts file after updating one of the sources....

What the hell... I should check a new app that would request root privileges to see whether the SU request is handled correctly.
[Magisk] zgfg:
See my post right above yours
[Magisk] gorman42:
Did that. Installed still N/A. Problem is apps that refuse root are not working now. Since I have no access to the functionality to hide it from them.
[Magisk] zgfg:
And you are absolutely sure that there is no more another/old magisk app/mngr (or only it's stub) still installed?

You can manipulate DenyList from Terminal:

su

magisk --denylist ls

magisk --denylist add (pkg-name and optionally process)

But su will ask to grant root (and if Magisk app does not see/handle it will not work, but try)

You can even manipulate DenyList in Magisk.db by MiXPlorer (it already does have root)...
[Magisk] gorman42:
Unfortunately "su" from terminal gets permission denied.

I can't believe what's happening to me... :-(

Where's magisk.db located?

And also, at this point, what would be the good solution to adopt to backup the phone while restoring it to factory status? I've never managed to find an easy one. Like I restore to factory and then redo the whole process from scratch but at least with the ability to restore the backup with my apps and configurations...

Else... where to look in order to clean completely magisk?

Because I tried uninstalling the app, installing the regular boot.img and rebooting. What happened was apps depending on root claiming the phone was unrooted and apps previously on the denylist claiming that the phone was rooted.
[Magisk] zgfg:
Swift Backup from Playstore is good but it needs root grant - you cannot give now (you could by editing magisk.db from MiXPlorer)

If you have custom Recovery like TWRP, you could rename magisk apk to uninstall.zip and flash - it should uninstall Magisk

By use of MiXPlorer, go to /data/adb

and open magisk db (some screenshots attached)

You will see the structure, with MiXPlorer you can do changes (add/remove to DenyList and to the list of apps granted root)

I used to do it (make a backup like magisk_db.bak but you will be more comfortable if you have TWRP that you could restore from that db bak file in case of bootloop or something)

If you delete the whole adb folder from /data, you will loose all modules, etc - on next reboot Magisk will recreate magisk.db and hopefully your Magisk app will see Magisk then)
[Magisk] gorman42:
Forgot to say: don't know how to check for this. The app is not in any list, there's just regular Magisk. But I don't know what a stub would be.

I am on LineageOS recovery. Tried sideloading from ADB the renamed magisk.apk (to uninstall.zip), it went through the process but, when the smartphone rebooted, Magisk app was still there. I uninstalled it through regular Android interface and it was gone. I reinstalled and rebooted... still root N/A.

I'll try to check the other things you mentioned.
[Magisk] gorman42:
I don't see /data/adb under root. Also you mentioned screenshots but I don't see any. Thanks for all your help, kinda desperate by now.
[Magisk] zgfg:
Flashing uninstall.zip had to uninstall Magisk, not the app - after that you really don't have Magisk (try again from Terminal or with MiXPlorer and so)

Also, you don't have /data/adb now...

Now you have to install Magisk from scratch 😁
[Magisk] 73sydney:
hehe i, as you, used to backup magisk.db from the beginning, then the fork wars happened and the database schema started to be fooled with and that became risky, so i decided to make the magiskhide/deny list backup tools in my signature...

*Shameless Plug*
[Magisk] gorman42:
did all that, flashed uninstall.zip, uninstalled the Magisk app, flashed the original boot.img from LineageOS payload.bin...

End result: root apps don't have root, "secure apps" (banking, etc.) complain about the phone being rooted.

Example: CF.lumen stating "Could not aquire root access". But then the banking app is claiming the phone isn't secure and closes. Same for a State ID certification app I use.

This is a disaster.
[Magisk] zgfg:
Some shots from MiX
[Magisk] zgfg:
With Magisk uninstalled and original boot you have no more Magisk

But you don't pass SafetyNet (bcs your Bootloader is still unlocked and you still run custom ROM and you are no more hiding it by eg using Magisk module USNF), hence banking apps do complain about 'root' (they probably don't say "root" or use the meaning vaguely)

If you want to get rid of Magisk and with that you want to pass SN and banking apps, you would need to go back to stock and relock the bootloader
[Magisk] gorman42:
Under root/data I only have app, data and user folder.

There must be something, somewhere, that remains from previous Magisk installs, I don't know what else could be happening.
[Magisk] zgfg:
Read my post right above - you just uninstalled Magisk by flashing uninstall.zip

No more root, no more /data/adb, MiXPlorer cannot use root to browse anymore, etc

And bcs of your Bootloader isunlocked and you're running custom ROM, your banking apps see that you device is not "safe" environment. Run SafetyNet check and both Basic Integrity and CTS will of course fail

You are too fast to do things before understanding what it is.

When I told you to flash uninstall.zip it was the answer to your question how to uninstall Magisk (not Magisk app)

You must distinguish Magisk from Magisk app/mngr (friendly UI Manager for Magisk - nothing else)

All that (specially about flashing uninstall.zip) is described on Magisk GitHub, Documentation and assumed that users are somehow familiar with the basics)

Nevertheless, you can install now Magisk from scratch (I'm not talking about installing Magisk app but the Magisk itself)
[Magisk] 73sydney:
because magisk has been removed

you have 2 choices from here, as zgfg said, you could relock the bootloader (and depending on phone *might/worst case scenario* include a data wipe), or install magisk properly

every magisk user should have this bookmarked

Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com
[Magisk] 73sydney:
The sign of things to come.....

Google's getting rid of SafetyNet Attestation, but the root and ROM crowd shouldn't celebrate yet

The new Play Integrity API is taking over for SafetyNet in the next two years, and it does all the same things (and more)

www.androidpolice.com
[Magisk] researchscum:
[ Install to Inactive Slot (After OTA) ]

can i use this with MIUI ?

i want to do an upgrade from miui 12 to 13.

but my recovery not custom it's miui recovery.

can i do an OTA update without losing root?

after some searching i plan to

1. download update let miui updater to verify and finalized it.

2. after all of it complete, open magisk press install and select method [ Install to Inactive Slot (After OTA) ]

3. wait until the process complete and reboot button show up.

4. press reboot.

if i do like i imagine will my miui os updated and root still available?

thx.
[Magisk] gorman42:
I'm sorry you got the impression I was doing things without understanding or reading beforehand. I followed all instructions precisely, I forgot to unhide Magisk, unfortunately.

I am pretty sure I found myself in the same condition I am now previously. Magisk/root removed, app uninstalled. I will try once more, re-reading everything. In any case I thank you for the help, I will report back in either case.
[Magisk] zgfg:
Previously you did have Magisk but Magisk app did not see it (when we started this conversation)

Now you do not have Magisk at all - hence you are not in the same situation

No matter do you have Magisk app installed or not (you can take any Android phone, with Bootloader locked, and install Magisk APK - it will open, show Magisk not installed and will be of no use there)