yashsingh1/xdaforums huggingface dataset:
[Magisk] soder:
If you read some posts before posting, you will find that:

a) you don't toggle root any longer

b) you need SuperSU+suhide or pph's root+hidesu to hide root from apps (not all)

/Söder
[Magisk] danilo_scala:
thanks for update, now work xperia z5 premium ?
[Magisk] b.eslabon:
if the new magisk is working again, how did you uninstall phh supersu suhide r266? tnx
[Magisk] Captain_Throwback:
What new Magisk? I was talking about the future release.

EDIT: Updated my post to make that more clear.
[Magisk] ericotena:
[MENTION=1162986]Captain_Throwback[/MENTION] After I followed the guide to install supersu, magis and suhide, magisk manager always fc and supersu asks to update binary but always failed. What supposed to be the problem? Honor 4x user here.
[Magisk] ashyx:
There seems to be a bug with the Magisk manager v2.

Without root every time Magisk manager is started it force closes. Once the device is rooted then Magisk manager works fine.

The problem is, if I disable the Supersu helper module via Magisk manager this disables root at next boot. To re-enable I need to start Magisk manager, of which I cannot do anymore as it will just force close because I no longer have root, meaning I can't re-enable the supersu helper module. Catch22.

I then have to delete the magisk.img and start over again.
[Magisk] ericotena:
This also happens to me. Always force closes. Supersu even asks to be updated but always fail.
[Magisk] Dalamar666:
Hi all

I want to full unrot due to CTS verification fail... but in TWRP i can see that there is a folder (/supersu) that persists...

I unrooted with supersu apk, the phone reboots and now, if i reinstall supersu apk, it said that I haven't root

If I deleted the folder, the net reboot still here...

Any ideas? Thanks
[Magisk] grep_i:
Because that's built in from TWRP custom recovery.

You don't have to remove that as long as you never click on flash SuperSU from TWRP during a reboot to/system.

If you need SuperSU than flash it yourself never confirm the question to let it automatically being installed by TWRP.

This also means that you are already fully unrooted.
[Magisk] Dalamar666:
Thanks for your answer. I remember this issue. I had it time ago, but now my TWRP doesn't ask me to install supersu binaries, and the folder still here xD and safety test fails
[Magisk] Captain_Throwback:
Make sure you're not flashing them all in the same recovery session. You have to reboot after flashing SuperSU, and then you can boot back to recovery (or use Magisk Manager) to flash Magisk.

Just use the Mount Magisk zip from the modules thread to mount the magisk.img while in TWRP and delete the "disable" file in the zzsupersu folder. That'll re-enable the module until the app is fixed.
[Magisk] twcobra:
Anyone try to go simple. I unistalled Magisk 7. Removed the Magisk app. Flashed the PHH's superuser-r266-hidesu.zip

Pokemon now works again. I have not had the chance to try Android Pay but who cares. LONG LIVE POKEMON XD
[Magisk] ericotena:
How to delete the disable file in zzsupersu folder? Sorry but I'm noob about this. Can you tell where is that zzsupersu folder? My problem is basically similar w/ [MENTION=4899305]ashyx[/MENTION].
[Magisk] Captain_Throwback:
Flash the zip to mount the magisk.img. Using the TWRP File Manager, navigate to /magisk/zzsupersu and select the "disable" file and choose delete.
[Magisk] ericotena:
Where can I font the r266-hidesu? But can xposed work along side PoGo with this setup?
[Magisk] royaLred:
Nope xposed dont work with PoGo.

Gesendet von meinem SM-G935F mit Tapatalk
[Magisk] twcobra:
Its in PHH's forum.

http://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394/page107

Post #1063

I don't use xposed so I would not know if it works. My guess is that xposed would not work.
[Magisk] Keksdroid:
I am using SuperSU 2.78 SR1 right now with suhide. Can I just flash the PHH's hidesu ontop?
[Magisk] milestone97:
Does Magisk still have issues with Android 11 GSI Roms?
[Magisk] dope77:
so after flashing latest canary my phone no longer charges when it's powered off.

i was lucky that it had 1% remaining to boot to recovery and plug it in charger...
[Magisk] zgfg:
Did you test with modules disabled - specially if you have acc or similar
[Magisk] dope77:
honestly i don't have any kernel/charging tweaking modules installed,

i'll try to charge it with core only enabled (just waiting for it to be fully charged)
[Magisk] Didgeridoohan:
Maybe related to this:

https://github.com/topjohnwu/Magisk/issues/906
[Magisk] xNotta:
I found out how to do safe mode correctly, power on, vol - when the Google animation starts (I was doing Vol+ and power like the old days).

It just continues to bootloop.

After manually rebooting, I get sent back to bootloader with the "Enter reason: no valid slot to boot" message. Reflashing stock boot.img allows it to boot again.

It's got to be something wrong with the patched magisk boot.img but I don't know where to begin with finding out what.
[Magisk] AndreM962:
So I tried doing what it said there, but Magisk gave me a magisk_patched.img file instead. Am I supposed to compress it? I tried compressing it into .tar with 7zip, but then the download started and never went anywhere.

My phone is a Galaxy M31, running Android 10. The information Magisk Manager gives me about it is A/B No, SAR Yes. I'm patching the boot.img. Anything else?
[Magisk] Lownita:
Where to find uninstaller.zip for magisk? It's gone from the thread.
[Magisk] dcarvil:
https://github.com/topjohnwu/Magisk/releases/tag/v20.4
[Magisk] Didgeridoohan:
It doesn't sound like it's a module causing your issues then...

There's been several reports like this since the Magisk v21.0 beta was released (maybe with a slight emphasis on the Pixel 3 family of devices), but equally many that have no issues rooting their A11 Pixel devices. I've seen some reports claiming success if you flash the stock boot image and then use "fastboot boot" (rather than "fastboot flash") to boot with the patched boot image. Once up and running you can then use the direct install option in the Manager to make root permanent. Worth a shot I guess...
[Magisk] Didgeridoohan:
In the GitHub issue you write that it output a magisk_patched

.tar

file. I'm assuming that's a typo and you meant .img... I know very little about Samsung, so I'm not much help here. Maybe you're converting the file to .tar wrong. Have you checked your device's forum if anyone there knows anything? Like this thread, as an example: https://xdaforums.com/galaxy-m31/help/m31-root-method-t4172891

Good luck...
[Magisk] AndreM962:
Yeah, it was a typo. Thanks for pointing it out, I've corrected it now.

I vaguely recall doing something very similar when I rooted my previous phone with Magisk. Perhaps I posted that solution here somewhere. If not, it can't hurt to ask other people who've done it.
[Magisk] xNotta:
Your safe mode suggestion gave me an idea that fixed it.

I had the stock boot flashed and booted safe mode by long pressing the "shutdown" button on the power off screen.

I then held Vol Down while it restarted so it booted into bootloader instead of normal start.

I flashed the patched magisk boot.img then selected start.

The phone booted successfully into safe mode using the magisk boot.img.

Modules were disabled from safe mode and i was able to delete them from the magisk app.

Maybe this can help you help someone else.

Thank you!
[Magisk] PistolSlap:
Hello thank you to you all , I havent' had an opportunity to try but I will try these suggestions when I get a chance. :)
[Magisk] dr4go:
Thanks for your comments and time.

Ad 1a) Thanks for pointing that out - somehow I didn't realize, that this statement is only valid for priv-apps.

Ad 1b) Unfortunately you speak for devices with fully working Magisk where there is no way to boot unrooted. Samsung broke the S10 in that sense, that it's a sar device without initramfs (at least until Android 10, I hope they change that for 11) - so Magisk resides in recovery for close stock configurations.

I mention that, because I had big troubles with Vanced if disabling the stock Youtube app and installing Vanced. If (accidentally) booting unrooted, Vanced is no longer present and all settings are gone... sometimes I even needed to remove and to reinstall it, which is exactly the reason why I want to debloat the rom beforehand (i.e. that I remove it from the flashing img / tar AP so that it's gone under any circumstances).

Ad 2a, 3) Your module looks really nice, I'll give it a go for sure if there is an initramfs present in A11 or I'm no longer with the S10.

I'm very familiar with the replace var technique and I like your approach for debloating quite a lot.

Ad 2b) - Usually it's in system/app for the S10. But as being mentioned, I don't have one.

- Wrong conclusion from myself. My SafetyNet had never failed because of mount binds.

- Not the case for S10 (/system/app/).
[Magisk] MajicDroidPirate:
Canary issues this morning

I opened my canary manager and it doesn't show the latest version on the updates, (im just using the built-in Canary channel in Canary manager), it also fails to check safety net which was an issue I previously had and it crashes when I go to my list of modules. Last time I had to fully uninstall magisk which in turn caused a bootloop, then i had to reflash my rom (luckily a dirty flash did the trick so I didn't lose any data) then redo the custom magisk boot img and reflash and it fixed all the issues but this was only weeks ago. I can do it again but I'm really hoping there's a better way it's really tedious if I have to keep doing it. Yes I know I'm on Canary I'm not complaining I'm just asking if anyone else is experiencing the same problems and has a solution
[Magisk] J.Michael:
Have you tried the procedure described in [MENTION=4470081]topjohnwu[/MENTION]'s installation notes?

give AP.tar from stock ROM to Magisk

use resulting magisk_patched.tar in AP slot in Odin

fill other Odin slots with .tar files from stock

It's important for Magisk to patch boot, recovery, and vbmeta images -- these are all in AP.tar.
[Magisk] AndreM962:
Yes, I followed the procedure exactly.
[Magisk] abun880007:
I get the same issue with flashing a kernel or patching recovery on My Note 10+ 5G while running a Android 11 GSI. As soon as I flash anything with Magisk 21 in it the phone boots straight to download mode. No matter what i try. Anyone else having this issue and now how to fix it
[Magisk] AndresOrue:
Sorry to ask here guys , Anyone who has magisk 21 installed and es file explorer . Is root option in es file explorer working fine ? I got this error: root access is not installed.... Uninstalled it multiple times and revoked root in magisk too.

My phone has android one 10 ( Motorola one vision) and I did't install other mods or anything similar
[Magisk] pndwal:
If you do have root, please check ES is on internal memory.

Doubtful you have this, but root permission fails if on adopted memory. PW
[Magisk] zgfg:
New thread opened:

https://xdaforums.com/mi-9t/how-to/magisk-module-systemless-debloater-t4180083
[Magisk] prot-:
Does anyone have any more updates on the freezing issue on Google pixel 3 /xl with systemless hosts enabled.

It's really bad .
[Magisk] supachris:
No. Is still broken. I'm using private dns for now to block ads. Works okay so far.
[Magisk] mentalis:
So i tried flashing 21.0 with the new manager and noticed the recovery mode option was gone, i asumed that meant that the new one detected the kind of img file i trew at it

but as my phone has been bootlooping for 6h till the battery died im kinda doubting that was the case.

i cant enter fastboot as i cant get the menu where you select it to open i also tried sp multi download tool to flash a older recovery image but with no luck as it said it was done but the result is the same

kinda in a bind here as it was a pretty expensive phone and i doubt this stuff falls under warranty
[Magisk] Goncalo29:
I'm facing a little problem. I can't hide the Magisk Manager by changing its name. So some apps detect I have rooted my phone (eg Mcdonald's), even if I hide them with MagiskHide.

I'm using the last version (20.4)
[Magisk] razrielsch:
boot loop after magisk 21.0 was installed via twrp

Hi,

i installed the new 21.0 version via TWRP but now my S5 mini stucks in a boot loop.

Is that know and know someone a way to step out of this ?

looks like the vol+ home pwr button doesnt step into TWRP

razri
[Magisk] wbercha:
Guys, i am unable to install one of my banking app, i have hidden magisk and everything and when i go to google play store it says this app is not compatible with this device anymore. Please help because i have been searching a lot fot it and still no luck.
[Magisk] pote2639:
Goddamnit, can you for once just focus on stability and not some silly UI change? After since I upgraded my manager to the new ones I can't open my old hide magisk manager anymore.
[Magisk] asrar73:
Unable to use banking apps

Root detected?

Help

Using Migisk 21
[Magisk] BillAdama:
Hi

I'm having some troubles rooting my Pixel 4a. I unlocked it and I flashed the rooted boot image with success (I think) but Magisk Manager at "Installed" says N/A.

I already tried with flashing the stock image and restarting from scratch, locking and unlocking again the bootloader and also using Magisk Canary.

What can I do? Can you please help me? I used the boot image found here.

Is there a way to check if the boot image is really rooted?
[Magisk] Spartacus500:
Give a link to this app in Google Play store.
[Magisk] dope77:
Did you enable magisk hide from the settings?

Did you hide root from the banking app?

Also try repackaging the manager, sometimes it help hide root detection

---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------

Not sure about your case, but on some devices (like mine) magisk would partially work or would be completely blocked due to some security in the kernel. You might have to flash a custom kernel to be able to root your device.
[Magisk] pndwal:
Actually, compatibility, hiding etc are pretty much what John does concentrate on.

Viktor ([MENTION=9815783]diareuse[/MENTION]) did / does the UI overhaul / maintenance for a number of not-silly reasons.

Moreover, this UI is no (recent) change for many users here as it's been around since January in Canary builds (although it's only recently hit Public Stable/Beta).

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83637567

Nb. Custom mods like TWRP are languishing (this is still incompatible with devices shipping Android 10 w/ no accross-the-model-range solution in sight), whereas Magisk, which is still pretty much a 2 man operation, still gets fixes constantly, is adapted to a plethora of new Android architectures as they emerge, and is compatible with every Android OS since... way way back:

I reckon it's pretty good value for our money, even if we have to fight with inevitable problems if we take updates... Otherwise, 'if it ain't broke, don't fix it' I guess.

More Magisk history:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83707709 PW
[Magisk] 73sydney:
Are you in here, again, not causing grief but actually being helpful?

Its beginning to be a pattern with you :)
[Magisk] JudgeDread11:
Without showing respect not many will be willing to help you.

The 'new' UI had been available and tested for many months in the canary branch.

Problems you are experiencing are most likely specific to your device/setup.

So instead of cursing, being respectful and giving information about your setup and steps taken would more likely get you some help.

Everybody else, please provide more information.

Device, Android version, Magisk version, stable or canary, steps taken.

And even then logs might be needed to analyze your issue.
[Magisk] zgfg:
If you have a problem with Manager after upgrade (did not really understand what was your problem), follow what's been suggested to others similarly: uninstall Manager (not Magisk) and install from the apk again.

Not sure about 8.0.2 but for Canary it worked
[Magisk] J.Michael:
Did you change the device fingerprint?
[Magisk] BillAdama:
I followed the guide here on xda and it doesn't say to flash a custom kernel. I'm not sure if I made something wrong have I got any way to check? Like dumping the boot image from the phone and checking it with md5\sha256?
[Magisk] FOREST37:
Forgive me asking the obvious = but have you actually tried using a file explorer to access System root to see if you can view restricted files - that would show whether you were rooted or not wouldnt it?
[Magisk] BillAdama:
Don't worry, I tried and I cannot access anything, I see only the folder structure under /system, no files or anything. Also X-plore it's not prompting for root access nor Root checker.
[Magisk] zgfg:
Delete explorer from MM Superuser - long tap and Revoke

For explorer, in Settings/Apps, Clear Data, and then try to open /system again

Btw, you can try with MiXPlorer
[Magisk] BillAdama:
I cannot even open the section for enabling Superuser in MM, it says that Magisk it's not installed.

I tried cleaning the Cache for MM but the situation is the same.
[Magisk] FOREST37:
I'm not familiar with the Pixel - but is it a dual partition phone? Do you need to fastboot using a patched boot image and then install magisk using a patched boot image via the manager once the phone has rebooted? That's what I had to do with my Mi A2 Lite and when i do OTA updates I have to select reinstall to inactive slot post OTA reboot to retain root status.
[Magisk] BillAdama:
Yes, it's an A/B device. You have to unlock it, flash the rooted boot image and then install Magisk Manager. Now I'm running on slot B, if I switch to slot A it doesn't boot.
[Magisk] FOREST37:
This is what I have to do - When a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates".

When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!

Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update.

After the update is downloaded, a two-stages update will begin. When both stages of the update process completed, it will ask to restart: DON'T DO IT!.

Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".

If I dont do this i assume that the phone will boot to the other slot and i will lose Magisk and root - which sounds like your problem, and I then need to reflash Magisk using the fastboot commands and a temporary patched boot image as i did to original install magisk.

Glad you got it sorted in the end of sorts

Just a thought - have you tried flashing the original boot image to the slot that doesnt boot?

Flash directly the vanilla (original, unmodified, untouched) boot.img using those commands:

fastboot getvar current-slot

fastboot flash boot_? boot.img

the first command will tell you what is the current slot in use (a or b), the second command will flash the original boot into the phone, but you have to change the "?" in the command with a or b (i.e. the current slot that the first command provided).

If it's boot - you can then do the magisk patch flash and install?
[Magisk] BillAdama:
I don't think this is my situation, I'm rooting a new devices, not updating it.

I also tried with

fastboot boot rooted_boot_image.img

my phone booted but Magisk Manager still said it was not rooted.

EDIT: was posting before the edit, I'll try this, thanks!
[Magisk] FOREST37:
This is what i had to do once I had unlocked the bootloader - Install Magisk Manager - APK to phone

You need the original boot.img to patch - After you get the boot.img, copy it to the phone memory (via USB or microSD)

You can use a program called payload_dumper to extract the boot image from the fastboot fiirmware image which you'll need to find on the internet

Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you got from the firmware.

Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, where your adb folder is.

adb reboot bootloader

fastboot boot magisk_patched.img

If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button.

Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.

Sounds like you just need to do the last Open and install stage once you've rebooted.
[Magisk] amajamar:
I just got notification from Google that my contactless pay won't work cause possibly rooted. Checked Magisk and I failed CTS portion of Safety net. What would cause this out of the blue? Nothing new installed or anything like that.

Running 20.4 Magisk on stock rooted pixel 3 android 10.

Thanks in advance.
[Magisk] sakeyo:
Hi! I have a redmi 8 with MIUI 11 and Android 10. I install Magisk via TWRP and it works correctly for two, sometimes three days, then it freezes and when restarting it starts the bootloop. Has it happened to someone else? If so, any solution?

PS: If I try to remove the modules by the TWRP file manager, the directories are shown encrypted and when I try to flash magisk uninstaller it gives me error 1.
[Magisk] Lughnasadh:
I noticed you also have a post in this thread. https://xdaforums.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773

That is a good guide to use. Instead of using the boot image you got from another thread you mentioned, try using your own boot image to patch. Also try switching the update channel to Beta before patching your own boot image instead of using Canary. People on your phone are having success using the Beta version to patch their boot image.

If doing that with using the guide in that thread doesn't work, you may have to start fresh by flashing the latest factory image and then using that guide.

Also, there is no need to lock you bootloader again (you mentioned unlocking and then locking and then unlocking again). If you lock your bootloader while not completely on stock you could brick your device. Best to just leave it unlocked.

EDIT: Also, make sure you are using the latest platform tools... https://developer.android.com/studio/releases/platform-tools
[Magisk] zgfg:
Please search for CTS in this thread (MHCP module, force Basic attest, unlocked Bootloader - there were lot of posts).

Better, look directly to MHCP thread, and read MHCP GitHub docs about forcing CTS Basic attest to hide that Bootloader is unlocked

---------- Post added at 04:13 PM ---------- Previous post was at 04:08 PM ----------

Then your problem is not in (unstable) Magisk Manager but Magisk/root installation itself

If you have A11, you needed to switch to Magisk Canary (or Beta), there were tons of posts what and how to go
[Magisk] BillAdama:
Mistery solved, thanks to everyone especially [MENTION=6207099]FOREST37[/MENTION]

How I fixed:

1) Installed Magisk Manager Canary

2) Copied the original boot.img into the device

3) Patched boot.img with MM

4) Copied magisk_patched.img on my PC

5) Booted via ADB with

adb boot magisk_patched.img
6) Permanently rooted the phone using MM and "Direct installation"
[Magisk] J.Michael:
If you "don't do this", and you realize soon enough, can't you still boot from the "original" slot and still have Magisk? So not have to reinstall Magisk before trying again to "do this"?

To clarify, re: fastboot commands: Isn't "?" the letter that was *not* "current-slot"?