yashsingh1/xdaforums huggingface dataset:
[Magisk] sarruman1:
The message you get is present in my case too...

"An 'su' command that does not belong to magisk is detected. Please remove the other unsupported su."

That drives me nuts...

In my case, rom is freshly rooted, and other root apps work flawlessly. Also, the device is new, so I never tinkered with it before, just wanted root for the (otherwise) stock Rom.

If only I could get rid of the message..!

Please help!
[Magisk] Didgeridoohan:
If there is another su on the device, then that message is normal. But, if on the other hand there isn't another su (as @sarruman1 says) I wouldn't expect that messae to appear. Maybe a bug?

If there's a bug, grab a logcat when the message appears (and save the Magisk log as well) and open a GitHub issue. Just make sure to be on the latest Canary release and to follow the issue template.
[Magisk] Didgeridoohan:
You definitely cannot use a boot image meant for another ROM or Android version. That would result in a device that doesn't boot...

But you do not quite say what your issue is. You just say:

What does it mean when you say that Magisk v22.0 doesn't work?

A few things to note:

Magiskv v22 have had issues on some devices. A lot has been fixed upstream in the current Canaries, so either you could give those a go or wait for a future beta/stable release.

There are often incompatibilities between Magisk and GSIs. Chech the GSI thread for info.

And lastly, normally the Ramdisk=no should mean that you need to patch the recovery image for Magisk to be installed. But depending on the manufacturer (XIaomi is a prominent example), this might not be the case. If you're interested in how this works there are plenty of details in John's documentation:

https://topjohnwu.github.io/Magisk/boot.html
[Magisk] Didgeridoohan:
Scroll to the bottom and expand the "Assets" section.
[Magisk] Didgeridoohan:
In theory you should be able to restore your stock boot image and then just reinstall Magisk with the installer zip in TWRP.

The backup you've found is the stock boot image that you could use for the above. Just unpack it and flash it to your device.

If TWRP complains that the zip is an unsupported image, are you sure that you have the install screen set to "Zip" and not to "Image"?
[Magisk] Xentiran:
Oh that is the stock backup?

When I first did it all, I followed these steps:

and im not sure if that is my actual stock image? As I downloaded something and im guessing flashed it onto and wrote over whatever there was on my phone.

Sorry if im not used to the regular terms and thinking regarding this, im pretty new.

And yes, im 100%. Because it starts with unpacking the file and then tries to boot it, but spits out the error.

So im thinking that I might have to just start over from the beginning and redo from the same guide, with the same method.

Cause im assuming when you're talking about "Just unpack it and flash it to your device." it would be done the same way I did it when I first unlocked the phone or?

Also thank you for the fast reply, very much appreciate the time you're taking to help me with this 😊
[Magisk] gruby_grubas:
Hi guys. I forgot to unhide manager before updating and I broke the app. It tells me to manually re-launch it. All modules are working fine. Is there a quick fix for that?

Thanks
[Magisk] Didgeridoohan:
That is the stock boot image that Magisk compresses and saves whenever you run the Magisk installer. As I said, in theory you should be able to get up and running again by just flashing that to your device (although you'll be without root). How exactly that is done on your device I can't say, since I don't do Samsung...

After that you could follow John's installation instructions for installing Magisk fresh. There shouldn't be any need for running the uninstaller first, probably.

If you have issues in TWRP it's generally a good idea to save the recovery log, since it'll have a lot more information about what is going wrong.
[Magisk] Didgeridoohan:
Uninstall both the regular app and the hidden one and then install the apk manually. That should hopefully get you up and running again.
[Magisk] Xentiran:
No worries about not knowing the ins and outs of Samsung 😁 Your insight has been most helpful and im gonna try some things (I backed up the boot image just in case).

Thank you!
[Magisk] krkhaha:
Hi guys. After I flash magisk in magisk manager I can't use WiFi. Did someone have a similar problem? You check logcat. You can check logcat. Thank you for any reply. Op8
[Magisk] me_droid:
Ok, after trying various steps to enable "hide magisk manager", including disabling play protect (thanks Didgeridoohan), it works. However, in the process it seems I had to update to magisk manager 22.0 (22000) (18), which is now installed. I think that my earlier reported issues may have come from canceling the download/update option that seems to be required to have hide magisk manager work. That makes sense as though I never chose to update manager via the button in the app or any other means, I did try to use hide magisk manager whcih essentially requires a download and update.

I'm still running magisk 21.4 (21400) alongside manager 22 and everything appears to work - root, hide, etc. First question is can I just leave it this way or is there any reason that I MUST update magisk to 22? Based on the many horror stories (bricked, wonky phones) I'm reluctant to do that.

If I choose to update, then I understand that I have to unhide magisk manager again. Do I also have to disable magisk hide for apps, disable modules (I only have systemless hosts and universal safetynet fix 1.1.1 installed)? Is it better to delete the modules rather than just disable them?

Final question, after doing all that can I just press the blue update button in magisk manager or would that be inviting trouble? This is on a pixel 2, stock Android 10.

Sorry for all the questions and thanks for all the advice given here.
[Magisk] JohnE2:
Thanks for the guidance Didger.

I did some further seaching myself before returning to this thread, and discovered that I needed the payload_dumper-win64.zip tool to extract the boot image from my ROM's payload file. This is not explained at all on Magisc's website, or in any of the how-to videos I've found, and would be useful to add.

Up and running now thanks, with a now fully functional LOS 17.1 phone with Microg.
[Magisk] ineedroot69:
much safer to unhide magisk manager and uninstall all modules then on magisk manager click "complete uninstall magisk" 21.4 then download magisk 22.0 on github then install as usual then just download again the modules you are using
[Magisk] dope77:
updated magisk to v22005,

manager still doesn't detect magisk and shows N/A as installed.
[Magisk] mia.backkind:
Hey there,

im a bit confused: first, after patching to v22 it seems all to work nice (root granted, permissions on apps that needs root granted, magiskapp says yeah its rooted). but then i found out, that my modules arent loaded. after several tests, like install a font to check modulefunction, i have to say: no modules will load.

i found in the magisk-log something like i havent read here before. at line 516-540 from my log it seems like that the magisk-daemon started 2 times

i asked my flatmate to check his magisklogs at 2 different smartphones. none of them have the magisk-daemon started 2 times.

additionly magisk tries to load a module that isnt installed at all (was in the past) - check line 526 "03-16 18:38:44.726 241 241 I : post-fs-data.d: exec [Greenify4Magisk-ramdisk.sh]"

maybe something was wrong before the update, but modules worked before update to v22

so, im just asking the safest way (like all here :3) to get magisk with working modules w/o loosing data

please delete this post if its asked before, im sorry, but let me a link to read to get all working - THANK YOU :)
[Magisk] me_droid:
Thanks - do you mean by as usual to install from within the app or to do it by the boot.img method?
[Magisk] ineedroot69:
you know the usual stuff grab stock boot.img and generate magisk_patched.img on magisk app 22.0 then "fastboot flash boot" it then 3pcs garlic cloves in check for doneness! You want an internal temp of 165°F then boom you have ultra-juicy, succulent poached chicken
[Magisk] ineedroot69:
At least it's not bootloop
[Magisk] MattP410:
Just coming back here to update. Switching to Canary channel did fix my problem on one device but not the other, strangely enough. Just wanted to come back and thank you for the advice!
[Magisk] crismarsf:
Got into an error while opening up an app “the app will be terminated because a security policy violation has been detected [code 00000034]". Now I've updated to latest and both checks pass, hid magisk and renamed it, added the app and still. It's on a s7 edge.
[Magisk] J.Michael:
Maybe you have a script left over from when you *did* have that module installed. Maybe the order of executing scripts changed, and now the script referring to a non-installed module is interfering with "starting" all modules.
[Magisk] rxk:
Need help.

Unable to connect my Galaxy Watch Active 2 to my Galaxy S21 Ultra after rooting.

I've done factory reset, installed latest stock firmware, Galaxy Watch Active 2 connected as normal. After I root using Magisk V22, Tried to connect but stuck on Finishing pairing.... I tried uninstall/install Galaxy Wearable and Plugin but still no luck.

I sure their is no problem with my watch because it is connected without root on both S21 Ultra and S20 Ultra.

Please help.
[Magisk] jeffshead:
New Pixel 4a (5G). Fresh update to latest Android 11 and then unlocked and rooted with Magisk 22. Everything works so far except for root explorer in ES File Explorer File Manager v4.2.4.4. I get the following error when I toggle that setting in the explorer app:

Root access is not installed, functions are not available now.

The ES Explorer app does have SU when I check in Magisk manager. I have the same app installed on an old Pixel XL with Magisk 20.4 and it works just fine. I can also gain root access with Solid Explorer and Total Commander but I really don't like those or any of the other file manager apps.

Any ideas on how to troubleshoot and fix?
[Magisk] Didgeridoohan:
Don't use ES File Explorer... It's golden days are long gone and from what I've seen reported I wouldn't trust it on my device. There are many wonderful and capable apps right here on XDA. I always use FX, but others have their favourites.
[Magisk] jeffshead:
Thanks! I've tried many other apps. I can't remember if I've used FX but I will check it out.
[Magisk] Lord Sithek:
Or MixPlorer: https://xdaforums.com/t/app-2-2-mix...-file-manager.1523691/page-1785#post-84673643
[Magisk] me_droid:
Didn't try your poached chicken recipe but did finally get 22 installed. Nuked old version of magisk after backing up all data, reflashed stock 10 image, then proceeded to the 22 install. I installed it as an apk then patched (not poached!) boot.img and flashed that. All is well. Not sure on A11 as my pixel2 won't get any updates to that beyond last December - 10 does everything I need for now.
[Magisk] unibombz:
Anyone know why when magisk manager is hidden and you go to enter the app it says "upgrade to the full magisk manager to finish the setup" you select OK to download and install

It then states to manually re-open the app, and repeats the same process? (as stated above)

EDIT:

Uninstall Magisk Manager 8.0.7 (latest)

Install Magisk Manager 7.3.5 (from releases page on GitHub)

Rename Magisk Manager 7.3.5 from within Magisk Manager

Undo rename, this will automatically update to latest (8.0.7 for me)

Rename Magisk Manager 8.0.7 from within Magisk Manager

It magically worked this time.

This seems to fix it.

Any idea how or why magisk hide will not find Cisco Meraki SM or work profile apps to hide them?

Meraki Systems Manager - Apps on Google Play

Mobile Device Management with Cisco Meraki.

play.google.com

I would like to hide this app but magisk does not find it ... any ideas?
[Magisk] Parideboy:
Hi all,

I can't update my whyred to the latest stable magisk version.

Those are the steps I took in order to update:

I went in magisk manager and disabled 'hide magisk'

Installed the new version and rebooted

Now I'm stuck in a boot loop. Things that I tried:

Dirty flashing the same version of the rom (LineageOS)

flashing the bare stock image from the rom in the boot partition

All my stuff is still present in the data partition. At this point I don't care about magisk, I just wish I could boot again to my phone. Does anyone have any further suggestions?

Thanks in advance for your time
[Magisk] ineedroot69:
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot erase userdata
fastboot format userdata
fastboot erase cache
fastboot format cache
fastboot reboot

bring back my dead device but i had to sacrifice dm-verity lmao
[Magisk] Parideboy:
Thanks for the quick reply!

I was really hoping for something less... painful, so to speak lol

Right now I'm backing up my data, I'll try something else before pulling the trigger for good
[Magisk] ineedroot69:
you said " I just wish I could boot again to my phone. " :whistle:
[Magisk] unibombz:
It seems these apps are pushed by meraki. Anyone know how I can install or allow magisk to see these apps so I can hide them completely with magisk hide ?

They are on a 'work' profile

I attempted enabling:

Choose User-independent option in Multiuser Mode Settings of Magisk app

not sure how to install magisk on this account or 'area'
[Magisk] Parideboy:
Yeah, without losing data, that is :D If I really have to start from scratch, I will.

It was mostly referred to magisk, I don't care about root at this point lol
[Magisk] bluedrink9:
I have a question that I haven’t seen answered anywhere in the docs. My Samsung A30 (stock ROM) has Magisk installed into recovery. Does this mean I can no longer install a custom recovery (like TWRP) over the top of it?

Would it work to just re-flash the magisk patched images over the top after installing TWRP? Or would that then break TWRP?
[Magisk] rxk:
Anyone experienced like this? I tried all possible solution i can find online but nothing works. If i tried connecting via Bluetooth settings, it will briefly connect for 1-2 seconds and disconnect again.

I tried clear cache, uninstall and even re-flashed stock then root. It only connects after flashing stock, after rooting same problem, stuck on "finishing pairing".

I will try again, rooting using magisk canary version. Hopefully this will solve the problem. For the main time I will pair my Galaxy Watch Active on my spare Galaxy S20 Ultra, just to use S-Health functions.

Need help. Please.
[Magisk] DiamondJohn:
I have no experience with connecting a watch, but the first port of call to get more details of what is going wrong on an android device is a logcat.
[Magisk] ext23:
How can I uninstall or remove Magisk from my ROM? It is built-in but I don't need it.
[Magisk] vaah:
So I just did direct installation method in magisk v22. After it reboot. my S6 would just stuck on TWRP no matter how many time I reboot it. So it seems magisk direct installation messed something, anyway fix this? I prefer not to reinstall a fresh rom if possible.
[Magisk] pndwal:
Latest Canary Changelog, including Release Notes:​

Magisk (f152b4c2) (22005)​

[General] Fix log writer implementation (yet again!)

[MagiskInit] Fix sepolicy.rule mounting strategy

[App] Cleanup fragment navigations

[MagiskBoot] Properly strip out data encryption flags

Diffs to v22.0​

[App] Prevent multiple installation sessions running in parallel

[App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images

[General] Proper cgroup migration implementation

[General] Rewrite log writer from scratch, should resolve any crashes and deadlock

[MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images

[MagiskBoot] Properly strip out data encryption flags

[MagiskInit] Fix sepolicy.rule mounting strategy

Sorry I'm late to the party. PW
[Magisk] mia.backkind:
still the same issues at canary 22005, magisk daemon starts 2 times

is there a way to modify the script to get my correct orders?
[Magisk] Ayan Chakraborty:
I opened a Magisk issue in GitHub. It was automatically closed by a bot without realising the gravity of the situation😏. Request @topjohnwu and @osmosis to please check

Magisk hide needs an update · Issue #4057 · topjohnwu/Magisk

Since it's magisk hide issue, I know it isn't that a priority but it's still a pretty useful feature without which using rooted phones will be a struggle. I am no newbie and had been using magisk s...

github.com
[Magisk] J.Michael:
Do you have a script named Greenify4Magisk-ramdisk.sh?

Have you tried removing that script?

Have you looked at /data/adb/modules to see if there is a directory for that module?

I have seen references to deleting the Magisk database, but I do not remember what problems that might fix, or what horrible things might happen if that is done under the wrong circumstances.
[Magisk] J.Michael:
Have you contacted the distributor of the custom ROM?
[Magisk] J.Michael:
There are people with both TWRP and Magisk. There are people who cannot have both.

You could try going back to stock, then try to install Magisk in boot partition. If it works, great. I expect it will take some work -- the normal procedure for a Samsung probably doesn't give you a choice of whether to install in recovery, it just patches several files in the AP.tar according to what has worked best in the past. I don't know if anyone has succeeded in patching boot instead of recovery. Check to see if there is a forum/thread dedicated to your device.

If you can install TWRP without Magisk, you might then be able to use TWRP to install Magisk.
[Magisk] J.Michael:
Have you tried following the template?
[Magisk] Ayan Chakraborty:
I have given all the needed information, it still got closed by bot because it's regarding root detection in banking app. Please see urself
[Magisk] Didgeridoohan:
You did not follow the template, which is why the bot closed it.

And there's of course also this:

https://github.com/topjohnwu/Magisk/issues/1152

Which basically means that unless you can show how and why the app detects root the issue will be closed anyway.

You're just gonna have to wait until John has time to work on his zygote injection implementation of MagiskHide rather than using ptrace (no ETA, of course). Or you could check out the Riru enhanced MagiskHide module for improved hiding (in case the app is using isolated processes):

https://github.com/vvb2060/riru-unshare

Or maybe the app is using some other known detection method:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] rxk:
Hi @DiamondJohn ,

Sorry to ask this. Where can I find the logcat?
[Magisk] DiamondJohn:
do a web search and you will find 000's of instructions on how to get the logcat. Its not in a place, its a process of retrieving it.
[Magisk] io2345:
I try to install Magisk 22.0 on a custom ROM. Ramdisk=yes. I select the boot.img (copy on the SD-Card), Terminal opens and says:

-Device platform: armeabi-v7a

-Installing : 22.0 (22000)

-Copying image to cache

|Process error

|Installation failed

The ROM was pre-rooted with systemless SuperSU. I removed SuperSU, but cannot restore original boot.img, as there is none.

Anything I can do?
[Magisk] ineedroot69:
dude reading this give me headache :LOL: you are using google translate?
[Magisk] io2345:
No, but english is not my native language
[Magisk] ineedroot69:
how did you select boot.img on magisk but you said cannot restore original boot.img, as there is none. ...

it's confusing what boot.img you have?
[Magisk] Didgeridoohan:
If the ROM comes pre-rooted with systemless SuperSU you're probably out of luck. If the ROM on the other hand comes with the SuperSU zip included and just flashes that as part of installing the ROM you can use the ROM boot image without any problem (probably).

"Process error" could mean that you haven't given the Magisk app storage permission.

More details here:

https://www.didgeridoohan.com/magisk/Magisk#hn_Prerooted_ROM

https://www.didgeridoohan.com/magisk/Magisk#hn_Process_error
[Magisk] io2345:
Thank you @ineedroot69 and @Didgeridoohan for your replies. Of course there is a boot.img contained in the ROM, but I doubt if it's original, as the ROM has been ported to Ridon OS (a CM derivate) in order to get a more modern android version.

But thinking longer about Didgeridoohan's comment, it indeed might be the case, that the SuperSU-part is just flashed "on-top" after the ROM installation. The reason is, that I deleted the SuperSU installation in the setup routine and had installed Magisk 20.4 instead (ZIP installed from TWRP). This version was functional - just wouldn't let me update to 22.0. That's why I uninstalled it now.

Going back to the current problem: I read the page "https://www.didgeridoohan.com/magisk/Magisk#hn_Process_error" but couldn't find the lines about giving Magisk storage permission. Has that to do with the copy of boot.img, that Magisk tries to write to /data, or has it something to do with reading from the SD-card?

EDIT: SOLVED - used a boot.img from a older ROM-Version, where I didn't fiddle around with, and this one worked fine. Now I will flash the new boot.img and hope to get all done. Thank you for giving me the idea!
[Magisk] io2345:
Sorry to disturb again

@Didgeridoohan: I could flash the new boot.img and now I have the new option in the Magisk app "direct installation (recommended)". But when I start the installation it says:

...

- Unpacking boot image

! Unsupported/unknown image format

! Installation failed

Is it of any help to upload the boot.img so you could check the format?
[Magisk] Didgeridoohan:
That is probably a known regression that I think have been fixed upstream (but my memory is not the best at the moment). You could try installing the Canary apk (you'll find the download on GitHub) and see if that works.
[Magisk] io2345:
Thank you for trying to help me.

Did it, and installed Canary version 22005, but error message is the same.

Upload boot.img anyway? Or wait for next app version?
[Magisk] Didgeridoohan:
Is there any extra information in the installation log? That should be the first thing to upload... If you want to upload the boot image as well it wouldn't hurt.
[Magisk] io2345:
Here is the log (took me some headache to get it copied). Is it the right one?

Also attached is the boot.img (patched by Magisk)

Thank you for taking your time to check it.
[Magisk] Didgeridoohan:
That's not the install log, unfortunately, but the Magisk log (and it looks pretty normal).

The install log you can save after trying to do the install. There will be a small disk icon in the upper right.
[Magisk] io2345:
Found it, but there isn't much more in it than we already know:

- Target image: /dev/BOOT

- Device platform: armeabi-v7a

- Installing: 22.0 (22000)

nanddump: MEMGETINFO: Not a typewriter

- Unpacking boot image

Parsing boot image: [boot.img]

! Unsupported/Unknown image format

! Installation failed

That's all...
[Magisk] Didgeridoohan:
But that's using the stable release... Was it the same for the Canary 22005 build?
[Magisk] Noob9496:
How to flash magisk on x96 air TV box?
[Magisk] io2345:
You're right, sorry for that. Now here the installation log for canary-version:

- Target image: /dev/BOOT

- Device platform: armeabi-v7a

- Installing: f152b4c2 (22005)

nanddump: MEMGETINFO: Not a typewriter

Parsing boot image: [boot.img]

- Unpacking boot image

! Unsupported/Unknown image format

! Installation failed
[Magisk] RobbieRobski:
I don't have xposed installed.
[Magisk] rxk:
Hi @DiamondJohn ,

I done a web search and manage to find a way to extract logcat from my Galaxy S21 Ultra

See attached logcats, 1. stock firmware no root 2. rooted using canary 3. rooted using stable Magisk V22.

I paired successfully when using stock firmware and no root. Both Canary and stable Version V22 pairing stuck on Finalizing Pairing screen.

I hope I provided enough information to help me resolve my problem.

logcats