yashsingh1/xdaforums huggingface dataset:
[Magisk] hamid3pnn:
i tried both, even with magisk hide option or full uninstall, still banking apps could detect, it seems i have to return from lineage17.1 to old stock rom, thanks alot for guides @pndwal @Didgeridoohan
[Magisk] pndwal:
So have you got full SafetyNet pass in Magisk, ensured MagiskHide is toggled on in Magisk settings and Google Play Services is selected in MagiskHide list (toggling off, then on again in Settings often fixes issues), toggled on your bank app in MagiskHide list also and rebooted BEFORE CLEARING BANK APP'S DATA, then tried bank app again?

If it still detects 'root', there are many other suggestions in @Didgeridoohan's Wiki that have helped where apps employ additional detection methods:

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot# 👍 PW
[Magisk] bradical711:
I have, I'm currently running April release right now on my P4XL w/ kirisakura kernel & 9 other modules. Are you using latest magisk 22.1? I've never had any issue flashing a patched boot.img on Pixel before as it's stock android. This may be obvious but is your Bootloader unlocked.? There's only so many things it could be.
[Magisk] zgfg:
Off-topic but maybe of use. Sorry if you already knew

Usually you want to search through the thread but likely not by (ir)relevance than rather by date (from the most recent)

To do that, go to to your Account, Preferences:

https://xdaforums.com/account/preferences

scroll to Search and instead of Default, opt for Most recent and then Save

It applies to Search through the thread from XDA app
[Magisk] hamid3pnn:
thanks for help, i did these: hide google play services and banking apps and hide magisk app, still didin't work,

then installed supersu and used full unroot button , Surprisingly banking apps worked, and still device was rooted, but i couldn't find main problem for hideing root,

safety check in v22.1 can't download proprietary extension and gives api error but i used safetynet test and it passed , it seems v22.1 has bug for safety check
[Magisk] pndwal:
The data wipe may be key.

Strange thing to try... Perhaps App's cached SN fail result got reset at this stage without data wipe?

Yes, API key was revoked. If you read back you'll see it's already fixed in Canary builds. PW
[Magisk] ipdev:
Since xda is so big, unfortunately sometimes things are lost in different threads or forums.

This will not help issues with backup scripts not running properly.

You and others might find these posts interesting.

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

xdaThread - Post 2,974 - Link

[TOOL] A QUICK Android OTA payload dumper

xdaThread - Post 6 - xdaThread - Link

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

xdaThread - Post 2,971 - Link

Cheers. :cowboy:
[Magisk] esi2121:
i have oneplus 7 pro , oos11.02

i did patched boot image from magisk manager and make fastboot boot *.img to root my phone but i actually not working ,,i did update magisk manager to 22.1 and try again and again no success .

make new boot patched image again and flash via fastboot( flash boot_a /boot_b or fastboot boot *.img ) again and phones got root but my sim network greyedout and disabled .(intersting!!!)

for fixing network problem i got to go fastboot and make fastboot flash boot ( the file that i was patched first time and on that network was ok but no success on rooting )

now i confuesd what i did wrong..

how i can gettting root????
[Magisk] Wesley_NL:
hey guys, i upaded magisks trough the app , and now my safety net dont pass on both my devices,

sm-g920f (g920fxxu6erg1)

and sm-g965f (offical rom ppr1.180610.011.g065fxxu7csj1)
[Magisk] pndwal:
Public Stable/ Beta build? What does evalType say?

SafetyNet API key revoked. Read back here. You probably have known Magisk SafetyNet CHECK issue only. Confirm using 3rd party checker app or use Magisk Canary App.

Already fixed in Canary builds... PW
[Magisk] pndwal:
Seems you need latest stable build's recent fixes to achieve Magisk root w/ A11.

Re. SIM issues:

Did you leave any Magisk modules installed from before taking oos update?

If so, try disabling them and rebooting.

This may help, particularly if you have mods like OOS Native Call Recording module, which may no longer be compatable in A11.

Universal SafetyNet Fix module can also cause similar issues on some devices.

As above 😜

Additionally, you could try latest debug Canary build which includes a few more recent fixes (including SafetyNet Test fix which is nice!). PW
[Magisk] esi2121:
No I don't have any module ,as I mentioned it's interesting 1 of the patched boot image doesn't work and don't affect to sim network and with (same boot image source)another patched image make network disable... Let me checkout with canary build from GitHub...thanks
[Magisk] pndwal:
There's been quite a few commits & fixes between last public build with Manager (was yours 21.4?), and 22.1!

https://topjohnwu.github.io/Magisk/changes.html

Other (longshot) fixes you may have considered:

- Factory Reset (backup data first 😬).

- Problems with root w/ SIM locked to network. PW
[Magisk] esi2121:
I was on latest manager 22.1
[Magisk] XenonF-Dev:
TL;DR: MM 7.5.1 - M20.3, updated MM, didn't detect M20.3 installed, (re)installed (dumbly) Magisk clicking on install buttom, selecting both checkboxes that appeared, got a bootloop since. Trying to figure out what to do to recover the phone, without wiping if possible.

Phone: Cat S60 (2016, Android 6)

MM: Magisk Manager

M: Magisk

After some days I'm still lost, I have found some people with the same problem as me (github issue #4219), but he wasn't as dumb as me as to proceed to re-install magisk on an already "Magisked" phone. I can access TWRP (many thanks to all the people on the S60 Root thread, which info was invaluable to root my phone when I got it), but I have no idea what is the best approach to fix the problem I'm in (Never ever let yourself fiddle with this kind of stuff with sleep-deprivation, I learned it the hard way :cry:).

I had SafetyNet working, so I can assume magisk hide was on and Magisk manager app was hidden. I had a couple of modules which were working correctly, I can access TWRP and list the folders if that can help into solving this issue (I hadn't touched Magisk after a week or so since I rooted it, so I have vague memories of what I did back then).

I read about renaming the Magisk.zip to Uninstall.zip to uninstall and test if the system works, but since I got into a quite unique (and dumb, I will be honest 😅) situation, I would like to ask first before I do anything that could cause even more damage than what I have already done.

Thanks in advance for everything, and have a good day.
[Magisk] pndwal:
Yes, but you said you patched unsuccessfully, then UPDATED to 22.1 before patching succeeded. 😉 PW
[Magisk] esi2121:
Yup ,but trying with latest 22.1 patching boot and no success.. I wonder what's the problem ?!

I had my first patched boot image that no harm to sim and no root working ...

Patching again make root working but sim disabled
[Magisk] caiejay:
Hi,

I have this banking app that keeps knowing that the phone is rooted. I tried magisk hide, hide the magisk app, change the twrp folder name and even installed the magiskhide build props module. i attached the magisk log.

The banking app is called bank muscat
[Magisk] HippoMan:
Sadly, a number of banking apps do their own checking that goes beyond standard SafetyNet checking, and they report "root", even if it's hidden from SafetyNet checks by MagiskHide. Magisk can't do anything about these particular banking apps, since they use their own internal procedures to check for root or other non-standard items that might have been installed.

I don't know about muscat, but I have this same problem with the app for my own Chase bank.
[Magisk] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84936057 PW
[Magisk] pndwal:
Seem to be a number of devices (especially on Android 6, 7?) with app detection issues on recent Magisk, like this one:

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

and others with problems installing latest Magisk builds like the one you cited.

Don't change advanced options unless you know what they do! But normally, reinstall is fine. That's why it's there.

Easiest / least fraught way to recover device:

If you did 'nandroid' backup (Twrp backup) of partitions before you rooted, simply do TWRP Restore of boot partition. (If you ever tried Direct Install with Recovery mode selected -should NOT be used on your device - you may need to restore recovery also, or just reflash TWRP.)

If not:

Get ADB working on a PC

Download full ROM package from OEM.

Extract boot.img

flash from PC using 'fastboot flash boot boot.img' ADB command.

MagiskHide on for SafetyNet - yes

Hidden / renamed Manager - not necessarily

To re-root, ensure you have uninstalled ANY Magisk Manager or App (especially renamed instances). See release notes re changed hiding methods / incompatibly:

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

Try re-rooting with latest Magisk App. Recommend Patching Image method, but can rename apk to zip to flash from custom recovery.

In the (likely at present) event of issues with your device, re-flash UNPATCHED boot.img, download older (working) Magisk zip installer, and flash from TWRP. If Manager is not installed in that process, install the corresponding Manager for that build, not newer App.

Also, be sure to read official Installation Instruction page:

https://topjohnwu.github.io/Magisk/install.html 🤠 PW
[Magisk] esi2121:
I tried a solution ,try that patched with working root(no sim working) to making root after that and confirm root is available I tried install 11.02 again and after it install magisk after ota .. and reboot...boot it up and nothing sim not working and root available ...

Back to the same patched image that working sim
[Magisk] pndwal:
Just looked back at your first post, and I'm not sure which ROM you extracted boot.img from...

Did you update to oos11.02 via full ROM, or OTA?

And is the boot.img file from the oos11.02 update package? or other?

Also, I may be wrong, but it seems you are restoring a boot image with failed patch... Why not Restore UNPATCHED boot image? PW
[Magisk] devgb:
Hi all! Thank you John Wu for this support/discussion thread. I'm sure it's helped many folks.

I was wondering if there exists a version of TWRP for Android 10 devices, specifically the H96 Max TV box (specs are here: https://www.amazon.ca/Android-LONGY...=1&keywords=H96+Max+2gb&qid=1620071209&sr=8-6).

Here's a bit of context: while in the recovery interface (the built-in one, not TWRP), I tried rooting the device by applying an update from sd card using the latest Magisk version (in .zip format) but it gave me an error saying signature verification failed. I figured it is because recovering with TWRP is preferred, but it seems like TWRP does not support my device ... Any ideas of workarounds/alternative solutions ?

Cheers :)
[Magisk] sk8223:
Haha yeah, that was supposed to be boot.img 🤦‍♂️

Yeah, countless times. Never worked...

Thanks for the info, I was on that page throughout Saturday though. Weird that unofficial LOS doesn't let you boot without Gapps, isn't the point of LOS to let you use the OS without Google? lol Anyway I'm sticking to MindtheGapps even if it's too bloaty for my liking. Seems like this package is best for LOS. Fingers crossed that with the next LOS nightly this method continues working and doesn't throw some weird errors at me... I miss the old days of Android when we didn't have to deal with Safetynet or A/B partitions
[Magisk] sereksim:
I have some questions regarding the new installation method... The "old" method (flashing a zip via twrp) is not recommended anymore, right?

I have got a Xiaomi Mi 9T Pro with MIUI 12.6 (xiaomi.eu 21.4.29), A/B No, Ramdisk No, SAR Yes.

What file(s) do I need to install Magisk correctly (where do i get "recovery.img"? Is ist just twrp?)

Thanks in advance :)
[Magisk] digger16309:
Sorry if this has been answered. I did search but it wouldn't stay in this thread. On Pixel 5, I've been completely uninstalling Magisk before the monthly update. I'm on 22.1 stable. When I press "uninstall Magisk", I get the dialog to "restore images" or "complete uninstall". I've always chosen complete uninstall but now that does nothing, even on reboot, and even after uninstalling all modules.

Should I now be choosing restore images instead? When was this changed?
[Magisk] zgfg:
Don't patch recovery.img but boot.img (in fact, their ROM zip does not contain recovery.img but who cares, the ROM itself must be installed through TWRP and for Magisk you only need boot img).

When you download 21.4.29 from SFN or AFH, extract boot.img from the zip.

Install Magisk.apk from Github, run, take Install (Magisk), patch, select file, keep Recovery mode unchecked (!) and patch.

Flash the patched img to Boot partition from Fastboot (or from TWRP, the latest 3.5.2)

I have Mi 9T, also running Xiaomi.eu 21.4.29 (and Magisk Canary 22104)

PS: The fastest way to download the ROM (for future weekly updates) is from System Updater - much faster than from SFN or even from AFH (even faster than downloading from AFH by using Advanced Download Manager)
[Magisk] sereksim:
Are you sure? In the installation guide it explicitly says you need the recovery.img if there is no ramdisk.

? I assume you just mean I download the latest version of the ROM from xiaomi.eu and extract the recovery.img/boot.img?

Thank you very much so far, I will try it tomorrow :)
[Magisk] zgfg:
Of course I am 100% sure, I have Mi 9T and patch the boot.img from the end of 2019, through all the official MIUI updates (Android 9 and 10) and Xiaomi.eu Android 11 since Nov of 2020

Btw, it has been posted in this thread MANY times that despite Ramdisk =No, that still (for most Xiaomi devices) you have to patch boot.img (not recovery.img)
[Magisk] Mew:
I'm using phh's su (http://xdaforums.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921)
[Magisk] Captain_Throwback:
Is it working for other apps? Including Magisk Manager?

If so, the issue is the app. In fact, I recall Unicon being one of those apps that hardcodes the su binary location, which would explain why it doesn't work.
[Magisk] Mew:
Yes, but not SELinuxChanger or Unicon

It's super frustrating D:
[Magisk] Captain_Throwback:
See my edit above your last post.

The apps are the problem.
[Magisk] Mew:
Ahh ffs D:

I guess I have to downgrade to Magisk v6

I looked earlier in bed on my phone but couldn't seem to find it

can you find it?
[Magisk] shinobi26:
Feature Request

I'd like to request the ability to download the modules through the Magisk Manager without installing them. I keep running into an issue where the Download+Install fails with "The zip is not a Magisk Module!!" and then the zip is immediately removed. I am able to successfully flash zips in TWRP, so if I could just get at the zip after it's downloaded that would be great.
[Magisk] Battery03:
I think that the zip remains in your phone when you download it from Magisk app. Check into your folders and you will see one called Magisk or something like that and there may be the zip.
[Magisk] shinobi26:
The zips are downloaded to MagiskManager directory, but as I stated after the install fails they are immediately removed from the disk.
[Magisk] Turbopuschel:
If you know how, why not explain it? Of course, if the honest answer to that is that if I don't know already it is most probably too complicated to explain for me and/or would be far too much to reasonably type, I accept that as a totally valid answer.
[Magisk] Captain_Throwback:
You'd have to compile it, either using the Android NDK or the Android build system.

P.S. I don't have to compile it, since I'm one of the people testing it ;)
[Magisk] Turbopuschel:
I see, thanks for the answer.
[Magisk] davenull:
Hello, I have been attempting to get magisk running again after a factory reset. I factory reset my nexus 6, and reinstalled magisk manager. After that, it crashes on open, and even after a factory reset, a full wipe, and updating to nexus pure, It still has the same behavior. Any ideas of where to look for the issues?
[Magisk] Captain_Throwback:
You have to be rooted to use Magisk Manager.
[Magisk] brickhayabusa:
http://xdaforums.com/showpost.php?p=68739461&postcount=2710

What about this workaround for cm xperia devices?
[Magisk] davenull:
So, even though the instructions say to flash magisk v7,

I will have to flash phh's systemless?
[Magisk] Papote3:
I'm trying to make a magisk module that replaces an app in the system folder.

Problem is the app comes in 4 flavors (arm, arm64, x86, x86_64).

Is there a way to make a magisk module that chooses the right app flavor for your architecture?
[Magisk] Captain_Throwback:
This is what the instructions say (I'm guessing you read them wrong):
[Magisk] davenull:
Right on, I flashed the newest systemeless phhs's and everything is perfect!
[Magisk] grandpajiver:
Hiya,

I have a HTC M9 running Venom Rom, M10 port with sense 8 and other fun addons.

I got Unicon (and ES File Explorer) (and other apps that use root incorrectly) to work by:

1. Uninstall SuperSU app (which didnt do much)

2. Flash unSu in TWRP

3. Open the terminal in TWRP

4. echo > "SYSTEMLESS=true" /data/.supersu

5. echo >> "BINDSYSTEMXBIN=true" /data/.supersu ( >> means append to the file)

6. Flash SuperSU-2.78sr1.zip

7. Boot into the OS

8. Install SuperSU from the play store (I didnt have an interface otherwise). Configure it and reboot.

9. Install suhide gui from the play store.

10. Install Magisk7 apk and flash it or whatever, along with Magisk Manager 7. reboot.

11. Install suhide-55.zip. reboot.

10. Install Xposed Material apk if you wish.

11. Open Magisk Manager (86.6), install xposed 86.6 if you want.

Android Pay works (for the first time ever for me), Pokemon Go works (although I cannot mock any locations, *shrug*), and V4A works. Unicon works, Gravitybox works, Titanium Backup works, Rootcloak (which is now probably not needed lol) works, Greenify works, old-as-hell xposed modules (XuiMod, SoftKeysFadeMod, App Settings/BootManager) works...

I'm impressed.

Chainfire mentioned that in one of the suhide versions (52 or 53, I think) that he got the BINDSYSTEMXBIN compatible mode that he dislikes working... so I dont know how the hell systemless and that value works together, but hey, it did ;) That was the solution on Unicon's G+ page... and somehow it still works.

Android is weird. I love it.
[Magisk] Alxoom33:
Does anyone know how to check if the internal Busybox is mounted and working. With the prior Sterickson BusyBox Pro that I had been using there was a dialog when loading busybox and a toast when it has been mounted.
[Magisk] XenonF-Dev:
Indeed, I was thinking on what I had done back in the day, since I try to be as safe as possible in these things, my bad for not saying it 😅.

I have checked the phone and both PCs in which I know I did the rooting steps looking for any kind of backups, without avail. Only OEM version I found is 31.02, and then the subsecuent updates for the firmware, which only contains boot.img.p.

I'm not sure if I should try to just use the stock 31.02 boot.img, since I can't remember which firmware version I had before the bootloop (Yeah, I will never do this kind of stuff without writting everything down, learned it the hard way ...)

tusch00101 backups from the upgrading progress are sadly offline too. Would be safe to use the stock (31.02) boot.img with twrp recovery?

I still have the Magisk manager and Magisk .zip versions I used a year ago as last resort, although I would like to know if using current Magisk.apk renamed to Uninstall.zip on TWRP could help on fixing the bootloop in case the boot.img I have is risky to use, and if doing so what I would loose or have to be wary off (Deleted folders, OS overwriting recovery partition, etc) to prepare ahead.

Thanks again for everything, I'm starting to see the light after the tunnel 🙂
[Magisk] pndwal:
Very much doubt you'll have TWRP for that; these are device specific, and would need to be compiled from released source code...

However, that is not needed apparently.

W/ Android 10, you have special 'loader' in Developer options, and this is reported to work to flash image files. Guess you could extract / patch boot.img yourself and flash, but one is provided (with method) here:

https://xdaforums.com/t/h96-max-rk3318-android-9-0-rooted-with-su.3965598/post-84029309 All best! 😋 PW
[Magisk] pndwal:
Depends what you mean by safe! You can generally recover by flashing back a previously working boot.img in case of problems.

Really, you need to ensure boot.img matches current ROM. That's why you unroot (restore images), upgrade, patch LATER boot.img, then flash that to re-root.

You mentioned "subsecuent updates for the firmware, which only contains boot.img.p." Do you mean OTA update?

This seems to indicate that boot.img has been updated from 31.02. You should be able to determine current ROM from Settings, About device.

If it is later, and you can't find a complete ROM package (Nb. You may be able to extract from OTA update, but if it's a space-saving incremental update this may not be possible as it may simply be binary-patch for existing images on your device), after Update and before to rooting, you could make a TWRP backup incl. boot.img, rename resulting boot.emmc.win file to boot.img and try patching / flashing that. No guarantees, but usually works. PW
[Magisk] pndwal:
In Search, click settings cog, click Everywhere, change to This Thread. 👍

Haha, yes!

It's all that is needed for updating, and means all Magisk Settings, modules etc will remain (in /data/adb) and save setting up again when Magisk is restored... These survive Magisk Uninstall this way, as well as App Uninstall...

However, it does seem Complete Uninstall is actually broken ATM at least for some, while Restore Images apparently still works:

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

Hope it's fixed soon! 😏 PW
[Magisk] pndwal:
Yes, Installation Instruction page may actually be misleading and could use some clarification, but John does actually cover this in a document linked from that page.

Click link for "(P.S.2 If you are interested in how Android boots and how it affects Magisk, check out this document)" at the end of the Getting Started section. The last paragraph in the linked Android Booting Shenanigans doc mentions that Type III devices including Xiaomi models may still accept initramfs (ramdisk) in boot.img.

And here's a (pull) request for clarity on this:

https://github.com/topjohnwu/Magisk/pull/4130 🤠 PW
[Magisk] sereksim:
Okay ,thx

So, just to be clear: I download the zip-file from xiaomi.eu, extract boot.img, choose Magisk -> Install -> *not* Recovery Mode -> Select and Patch File -> Let's Go, boot to fastboot/twrp and flash the modified boot.img, right?

Is it necessary/recommended to uninstall the old Magisk version manually first, or is it okay to just install the new one?
[Magisk] zgfg:
If the old Magisk Manager (or Magisk apk - depending what was your previous version) was hidden, then you may have problems that Magisk apk will not recognize that Magisk was installed (once you patch and flash).

Some have the same problem even without hiding Magisk Mngr/apk - in that case, find Magisk mngr/apk (or renamed) in Settings/Apk and uninstall

I hope you didn't try to patch/flash Recovery - in that case restore your TWRP (I don't know where to find original recoveey for Xiaomi.eu, but you need TWRP anyway)

Otherwise - I don't see how could you have Magisk installed if you didn't patch/flash boot img yet, and while (first time) switching to Xiaomi.eu you had to Format Data, hence you could not have the old Magisk db on Data either
[Magisk] Uluru25:
I don't know if your phone behaves different to mine (Redmi Note 8T) in this regard, but since it was delivered initially with Android 9 and since I was able that time to flash magisk as a zip-file from the TWRP recovery I also tried this for magisk v22.1 (renaming the. apk file to. zip) and it worked perfectly.