yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
For the newer versios of TWRP you don't need to rename to zip, TWRP will recognize that the package is flashable zip file for TWRP

Besides, apk file is actually a special 'subformat' of zip - take any apk file, rename to zip and open as any regular zip file on your PC and find inside the archived files and folders

Also, YT and similar guides might be helpful (but sometimes also inaccurate or so). It's better to read official Magisk (installation) guides/docs available on the Magisk GitHub page (this trick with the APK renamed to zip is mentioned there). Only, users, and specially newbies never go to read first
[Magisk] pndwal:
Yup, old zip install can still work well for many... Can't work for some devices, eg many A-only Legacy SAR devices, however...

Temporary boot can be good to test patched images as mentioned, but nb. (= note 😉) mismatched boot images will still often boot fine but have comms, BT, WiFi and many other issues... Your symptoms seemed to suggest image you used might not be from the exact version is OS you currently run... Many have such issues if take OTA update, then flash back previous patched boot.img..

.zip installation always uses device boot image so avoids this user error... Nb. w/ late TWRP builds you can flash as .apk... Don't even need to change file extension...

BTW (by the way), without is abbreviated to w/o, so with becomes w/... And PW is just my initial as you likely knew...

🤠 PW
[Magisk] Captain_Throwback:
Um, no - it's from Magisk, FOR SuperSU.

It's what keeps Magisk installed when updating SuperSU.
[Magisk] Tikerz:
Oh ok, I couldn't install SuperSU because it failed at a ramdisk step so once I deleted it I could install. Thought it was from SuperSU.
[Magisk] harpin14789:
So just flash the zip you attached in recovery?
[Magisk] 4RK4N:
yes. its the same as from the manager app. same files directly from the magisk git repo.
[Magisk] Tikerz:
Couldn't Magisk just be renamed or put in a different location to hide from SafetyNet :D How can we know how Google is "detecting" it?
[Magisk] harpin14789:
So any magisk zip can be flashed in recovery if it doesn't work through manager?

I got Google assistant to work with home button longpress. I trained my voice but it won't come on when I say OK Google though.
[Magisk] 4RK4N:
yes. everything from the magisk manager can beflashed directly in recovery. just dl a modules repo from git, unzip it, go into the unzipped folder and create a new zip of everything in that folder. that new zip can be flashed in twrp.

here is what magisk manager offers https://github.com/Magisk-Modules-Repo

edit: on the ok google issue: is ur google app a system app? i read ok google doesnt work that well if its a user app. aside from that i cant help much on that. i use my watch for ok googling. phone has it disabled to prevent double activation.
[Magisk] harpin14789:
Yes, it's system app. Should I wipe data for Google app after flashing the module?
[Magisk] 4RK4N:
if assistant comes up when u hold the home button then u alrdy did a data wipe for the google app.

u can try to set the language to english canada or some other language u can speak, train ok google with it, switch back to ur native lang and retrain ok google. some users reported it fixed their ok google issues.
[Magisk] return.of.octobot:
build.prop assistance

Got a question that I'm hoping someone here may be able to enlighten me on.

The common example given in regard to magisk build.prop modification entails using the setprop command to alter a preexisting line.

I would like to know the syntax required to add a new line to build.prop using post-fs. I understand the concept and implementation as far as the module is concerned, what I'm lacking is the proper code/command itself.
[Magisk] Captain_Throwback:
It's the same.
[Magisk] knpk13:
So does that mean if we use microG or go gapps free, safety net won't check for anything?
[Magisk] Captain_Throwback:
You tell me.

I don't use those things, so I don't know. But conceivably, yes.
[Magisk] mobileman88:
Safety net has been updated to look for Magisk

---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------

Flash the stock boot image. That will remove all traces
[Magisk] G U C C I:
Yup I did that. All good and am passing SafetyNet now!
[Magisk] CrazyCypher:
I read in this thread that SafetyNet is looking for Magisk so you cannot pass with Magisk.. Is there any way to add Magisk on suhide list like systemless xposed 86.2? As far as I know suhide hides systemless xposed so its not traceable, could it do the same for Magisk?
[Magisk] DawoodSahi:
Magisk never successfully hid root or disabled it temporarily, never been able to pass safety net with the 'hidesu' from magisk manager. After I reboot, root is still there and it's basically the same as before (with hidesu option unticked)

Edit 1: I had it enabled just to check what happens after a while and apparently it's just broke and now root is not totally functional and I've tried disabling suhide option but after reboot, it just is enabled

Root isn't functioning properly, I tried uninstaller magisk then reflashing v8 and then modules (including phh su, systemless xposed, v4a)

Help please.
[Magisk] Captain_Throwback:
Magisk is detected by SafetyNet (currently), so you won't be passing it until there's an update to Magisk.
[Magisk] DawoodSahi:
Thing is my root is screwed because I had hidesu enabled and now it's just not working. I've tried uninstalling magisk and reinstalling twice.
[Magisk] NEOVerse!XChara:
ok now i have to unroot my device, how to do it?
[Magisk] NEOVerse!XChara:
hould i rename magisk.apk to uninstall.zip to uninstall it?
[Magisk] rodken:
Fully unrooting is pretty straight forward.

There has to be a bona fide reason as to why you are not utilizing the power of the search engine to get you question(s) answered regarding the many intricacies of Magisk.

-- Notwithstanding the fact that you should delve into the well written troubleshooting guide.
[Magisk] NEOVerse!XChara:
ok, i have uninstalled magisk via magisk app, it rebooted my phone, but, by some reason it booted into recovery mode, so, i flashed magisk 25.2 but nothing changed, the phone keeps loading into recovery, what i should do? mayabe format data, or wipe data? or i should dirty flash, or mayabe clean flash?
[Magisk] Kingdavid337:
Hey guys, hoping to get some help troubleshooting.

I'm trying to root my Note 10 using Magisk.

I've enabled bootloader, installed Magisk 25.2 and used ADB to push my stock AP file onto the phone.

I then used Magisk to create the patched file which I pulled via ADB onto my PC

From this point, trying to use Odin to flash the patched AP file stays stuck on USERDATA for several hours.

I was able to reflash the unpatched stock ROM and get the phone working again.

Currently I've tried:

Older releases of Magisk

Older versions of Odin

Does anyone have any idea what I can do to get this working?
[Magisk] xabier-bo:
In my case (Xiaomi Lisa, Android 13 stock) what worked was:

- download fastboot stock ROM

- fastboot

- run the flash all execept storage file (or myflash if it's your case and you prefer)

- then the mobile boots fine

- patch boot image with Magisk apk

- boot in fastboot mode again

- fastboot boot the patchedboot.img

- fastboot continue

- adb wait-for-device shell magisk --remove-modules (this removes all modules and lefts "just" a device with root

- now you should be able to enter your temporary rooted device and finish the standard routing procedure (direct install)

(Again in my case) there was a module causing the reboot, and yet don't know why the bootloop saver couldn't handle it
[Magisk] zgfg:
It should have probably worked easier with Android Safe mode:

Xiaomi Mi 11 Lite Safe Mode - Android Settings

<strong>How to enter safe mode on Xiaomi Mi 11 Lite ?</strong> Safe mode by monitoring device performance, you can see the effects of your last installed third-party applications on your system and uninstall these apps if necessary.

www.androidsettings.net

Keep the Magisk installed with the boot.img patched by Magisk

Boot once to Android Safe mode. Then reboot normally

System should boot with Magisk in the Core only mode - only root will work but all modules will be disabled (making it possible to boot when you had a problem with some modules) and Zygisk will be also disabled

Open Magisk app, go to Modules and manage them (enable those you wish, uninstall or keep disabled the others).

Re-enable Zygisk and check your other Magisk settings - disable Core only mode (if that explicit setting is available in your Magisk app)

Then reboot - now Magisk will boot now normally but without the modules you kept disabled or you just uninstalled

See the official Magisk GitHub page, Wiki, chapter Disabling/uninstalling modules manually, paragraph about the Safe mode:

Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

---

Some time ago I tested successfully the procedure on my Lisa but with Xiaomi.eu MIUI 13 / A 12 and Magisk Delta
[Magisk] crypticc:
Hey there.

While mucking about trying to get a single banking app to work on my Pixel6Pro I uninstalled ice box and then it lost the hidden Magisk app. Reinstalling the original Magisk app then Magisk didn't have access to root itself, the app felt Magisk was itself not flashed when it was.

Long story short I've now re-installed Feb stock update inc boot img patched with Magisk but still Magisk app thinks device isn't rooted with Magisk. The options in Magisk say :

Installed : N/A

Zgist : No

Ramdisk : Yes

But I know Magisk is installed, both because I patched the boot.img and flashed it myself, but also because my other root apps I successfully get root, e.g. x-Plore, and so on.

Play Integrity checker and Safety net integrity, etc. all show passing so even the USNF and Shamiko modules must be running.

It is like every app that needs root can get root, except magisk itself.

I've both re-tried doing fastboot boot (patched img), I've also tried re-installing the magisk apk. (Edit : when I do so the app gets the non-standard icon like it was hidden even though named correctly)

Clearly there's some traces of the previously hidden apk somehow preventing the unhidden apk from gaining root and spotting that boot image is actually okay. I'm now stuck for ideas so would appreciate any help you can give.

Thank you

Chris
[Magisk] crypticc:
Edit : Now when I uninstall and reinstalled Magisk APK it won't even open. I've disabled play protect temporarily as advised elsewhere. Device still passing PI and Playstore and Wallet still showing device as compliant so Magisk itself and the modules etc. still doing the job in the background, just that without APK I cannot configure anything.
[Magisk] xabier-bo:
Agree (in fact you know better 😅), but in my case, safe mode didn't help.

So just in case @crypticc had similar issues I shared what worked for me
[Magisk] crypticc:
Nope - no dice

What is odd - not in the list above - is that even after unstalling Magisk and reinstalling after each reboot it offers to "update" rather than "install" the app. And the Magisk logo is from the stub, even though I uninstalled that.

Finally using the links you put above I tried deleting the data/adb/magisk.db and now the Magisk boot.img won't give root to the apps that used to have root.

TLDR I'm stuffed.

Here's the error when attempting to start that faulty icon:>

Spoiler content hidden.
[Magisk] crypticc:
Edit II:

Actually, I tried installing another Magisk APK that I had in my download folder, the one with Magisk-<number>(25206).apk that I believe Pixel Flasher placed there.

I now have Magisk back with original icons, and with the steps performed above with no modules etc. installed and blank deny list. RE-starting the config from scratch now.
[Magisk] NEOVerse!XChara:
guys help me :(
[Magisk] J.Michael:
Reinstall the operating system -- flash the stock ROM.

If that gives you a working phone -- you can boot into Android -- then install Magisk again, being careful to use the boot image from the newly installed OS.

If you have fastboot, consider testing the patched boot image before flashing:

fastboot boot patched-image
[Magisk] rscrmm:
What method is used to check the "policy" database, when an application requires to execute a root command? The only one that makes sense is the class "PolicyDao" suspend fun fetch(uid: Int): SuPolicy?, but it doesn't.
[Magisk] crypticc:
Hi.

Do u mean when Magisk checks data/adb/0 files? That's very technical so you might be better off asking in the Magisk github thread and giving details of what you're fixing.

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Regards

Chris
[Magisk] pndwal:
Are you following the Installation guide and flashing all four binaries, not just patched AP? And very importantly, used ADB pull, NOT mtp to transfer files?...

Also, I believe Galaxy note 10 is 'ramdisk = no device'... Did you patch AP with Recovery mode selected since you apparently need Magisk in recovery ramdisk?... 👀 PW
[Magisk] Kingdavid337:
Sure did. All 4 binaries.

First attempt was MTP, then read somewhere it corrupts the file, next 4 attempts were using ADB pull.

I did keep recovery mode ticked.
[Magisk] pndwal:
Symptoms are for classic case of DCA Syndrome* which is a terrible scourge resulting in an andriod device displaying the nondescript personality of an iPhone despite being jailbroken...

Nah... Kidding... Just results in Magisk Installed = N/A and other symptoms like asking for superuser permission for Magisk...

*Nb. DCAS = Dual Conflicting App Syndrome...

So I suspect you'll find an old stub app is still installed (Nb. this is really a tiny app container, and either loads current Magisk binaries/updated into data from full package before uninstalling or calls GitGub repos for these after installation)... Often this will disappear from app drawer/launcher, but search for its blank icon or original names you may have assigned in Device settings, Apps list...

I don't know much about 'ice box', but I'd say uninstalling it may have restored a (different?) hidden app that overrode the current one and also conflicts with your newly installed full app... Or something similar... Or completely different...

Anyway, check Device settings, Apps list carefully... 🙂 PW
[Magisk] pndwal:
Interesting...

What do you mean by 'enabled bootloader '?... Did you follow the whole unlock procedure for Sammy?... Does Key Attestation app say 'Bootloader is unlocked' right at the top?... PW
[Magisk] Kingdavid337:
Developer options > checked "OEM unlocking" > power off > download mode > unlock phone > automatic factory reset

I don't have key attestation, but every time I reboot my phone, I get a warning message saying:

"This phone's bootloader is unlocked and it's software integrity can't be verified. Any data..."

and asks me to press the power key, so I assume it's unlocked properly.
[Magisk] crypticc:
Hi. I actually fixed this thanks. It did relate to uninstalling icebox while magisk was still renamed. In did that because I thought with trying just in case CItI was testing for Ice box. It made no difference.

The stuff about CItI predates that and I think more related to their own update 3 Feb which sees through magisk, USNF, and Shamiko somehow. Either that or my device is now blacklisted with that TMX component.
[Magisk] zgfg:
Procedures for unlocking BL vary among vendors. I don't know for Samsung, maybe it's that simple as you described (do some googling to make sure how to unlock BL on Samsung, particularly your phone)

But from what you described (warning on boot), BL is probably unlocked.

You can also check by Fastboot command (hopefully it would work for Sammy):

fastboot oem device-info

Btw, with the locked BL, any flashing in Fastboot will be blocked
[Magisk] pndwal:
Apparently it can be unlocked but still controlled by VaultKeeper...

Per official instructions for Sammy, did you check:

😶 PW
[Magisk] Kingdavid337:
This was the solution. I needed to set the date back a month and restart the phone for it to release the bootloader.

I was able to flash the patched ROM via Odin.

Now I've boot looped myself...

I'll have to do some research tomorrow
[Magisk] pndwal:
So it was VaultKeeper?

Please report what you did...😝 PW
[Magisk] Kingdavid337:
Yes it was VaultKeeper. Stupid software.

Ah I was silly and didn't wipe the phone after my failed attempts at flashing. I've since reflashed my stock ROM, wiped data partition just in case, and then flashed the patched version which has worked so far!

Device is currently rebooting for additional setup from the magisk app xD
[Magisk] NEOVerse!XChara:
finally, i recovered my devices and root workin, i just formatted data and installed magisk app, it asked for reload, i accepted devices booted as usual and root check showed that i have rooted my device! thanks everyone who helped me anyway :|
[Magisk] aariss:
Hi

I'm on magisk v25.2 with safetynet v2.40 and shamiko v0.6

I got 1 app frm playstore that failed to open although has been added into denylist

No issue to open that appl on non-magisk device

How to rpt this to dvlpr so they can test it ?
[Magisk] pndwal:
Please say device, ROM, hiding employed for Magisk app, app that detects modified environment etc. so we can help...

We can't be repeating every fix for 'blue car won't start' w/o knowing anything about it... Does it run on petroleum?... Did you put some in?... Did you check the fufu valve???

Also, Magisk dev won't help you with hiding issues in general as these involve manipulating/spoofing expected device signals... Magisk will no longer do this... PW
[Magisk] aariss:
Sorry due to less info

Device is xiaomi 12t pro

Rom is xiaomi.eu miui 13.0.10.0 slfcnxm

App is here

Thought in magisk got log where we can share to them
[Magisk] zgfg:
For me the app works (I have no acc to login) on Magisk Delta, with the app checked in MagiskHide

Xiaomi Lisa, MIUI 13, but first make sure you're passing Basic and Device Integrity (Strong Integrity will not pass and it's not needed) for PI API:

Play Integrity API Checker - Apps on Google Play

Get info about your Device Integrity through the Play Intergrity API

play.google.com

Read about and install USNF module if needed:

[MODULE] [MOD] Universal SafetyNet Fix

Universal SafetyNet Fix [MOD] Magisk module Hello. This is my modification [FORK] of the original Universal SafetyNet Fix module from @kdrag0n. Created for the (temporary?) restoration of working capacity in the conditions of constant change...

xdaforums.com

---

Generally you will need to play yourself. Magisk devs are not reading XDA and on the GitHub they don't accept issues that some app detects Root or so

Even for the Magisk forks like Alpha or Delta, devs will also ignore that kind of questions or 'issues'
[Magisk] aariss:
Great. Issue resolved with M.Delta but api checker failed for device n basic.

I'll check with M.Delta forum later
[Magisk] netra3441:
Hello Forum,

I run my Samsung Galaxy S7 (herolte) with LineageOS 19.1, another S7 with LineageOS 20.0.

Need to know how to install Magisk in its newest version, also were to download it from.

After reading here for a few hours, I do not find a safe installation guide for the Samsung Galaxy S7 (herolte).

(Maybe its because I do not find the wood among all those trees, as we say here in Germany... its really a littlebit difficult to find here on XDA the needed informations, because its sooo much information) ;)

I would be very grateful for a link...

Thank you in advance!
[Magisk] zgfg:
Make sure you're on the Net when attesting

You have a button top-right to read the JSON response
[Magisk] zgfg:
GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

From Downloads probably take Canary and read the Installation instructions for Samsung
[Magisk] pndwal:
Better use this USNF fork / brand new build to pass deviceIntegrity consistent as official 2.4.0 is still broken:

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88149053

Also, official and older 2.4.0 unofficial builds conflict with custom ROMs w/ integrated prop spoofing/SFN like Xiaomi EU... Apparently (changelogs indicate) this limitation is fixed in newest @Displax build...

eWallet opens fine for me with setup mentioned here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-87873291

No real need for Delta fork AFAICS, but I needed app hiding using HMA LSPosed module...

🤠 PW
[Magisk] netra3441:
@zgfg

Thank you very much for your quick response.

I just read the installation guide for Magisk and for Samsung.

But I dont understand the order how to install.

Actually I have installed the latest TWRP 3.7.0_9-0-herolte and LOS 20.0. LOS 20.0 runs fine.

But no problem to do a new install - but in wich order?

Where I have to put in the Magisk?

Shoud I install Magisk with TWRP before LOS 20.0 or after that?

Thanks in advance!

SOLVED! (y)
[Magisk] netra3441:
Ok, had worked fine. Thank you! (y)
[Magisk] aariss:
Issue resolved
[Magisk] huskydg:
@Andy3153 try type su and enter, what happen?
[Magisk] Andy3153:
$ > adb shell
OnePlus6:/ $ echo $USER
shell
OnePlus6:/ $ su
Permission denied
13|OnePlus6:/ $ exit
$ > adb root
restarting adbd as root
$ > adb shell
OnePlus6:/ # echo $USER
root
OnePlus6:/ # su
OnePlus6:/ # echo $USER
root
OnePlus6:/ # exit
OnePlus6:/ # exit

But, again, Magisk as a binary exists

$ > adb shell
OnePlus6:/ $ magisk
Magisk - Multi-purpose Utility

Usage: magisk [applet [arguments]...]
or: magisk [options]...

[...]
[Magisk] huskydg:
It looks like normal apps don't have permission to execute su. You are using vivo device?
[Magisk] Andy3153:
As I said in the main thread:
[Magisk] huskydg:
Show me the permission of su?

ls -ld /system/bin/su
[Magisk] Andy3153:
OnePlus6:/ $ ls -ld /system/bin/magisk
-rwxr-xr-x 1 root root 247168 1971-05-11 23:57 /system/bin/magisk

So owner, group and others all have the execute flag. I don't think it's a matter of executing it, or Unix permissions, after all `su` is a link to `magisk`:

OnePlus6:/ $ ls -l /system/bin/su
lrwxrwxrwx 1 root root 8 1971-05-11 23:57 /system/bin/su -> ./magisk
[Magisk] zgfg:
You should be prompted to grant a root to adb, and then to authorize your PC, otherwise su over adb won't be permitted

But use Terminal emulator from the phone, not adb/PC and try directly su

Grant a root when prompted and try then like magisk -c

It shall print the Magisk version installed

Btw, Magisk app itself shows on the main screen if Magisk is installed and which version

You can enable Systemless hosts, install like AdAway root, reboot and test does it block ads

Or install a root explorer like MiXplorer, try to open root, it should ask you to grant a root and then you should be able to read/write on /data and read /system and other partitions (writing to /system depends on other conditions, out-of-scope here/now)

You say you installed some modules, you can test do they work (although, some modules may not work on the particular phone/ROM, modules generally do not install apps what to expect and how to see if a particular module works)
[Magisk] huskydg:
How about:

ls -dZ /system/bin/magisk
[Magisk] Andy3153:
OnePlus6:/ $ ls -dZ /system/bin/magisk
u:object_r:magisk_exec:s0 /system/bin/magisk
[Magisk] Andy3153:
To make a TLDR of my issue: apps that had root permissions granted to them still have it, but newly added ones don't. This, and the fact that the Magisk Android app doesn't 'see' that Magisk has been patched into the boot partition, as I showed in my attached screenshot
[Magisk] huskydg:
Try typing su in Terminal not adb shell or adb root?
[Magisk] Andy3153:
As I said previously, apps that got granted root permission still have it, like Termux here

But newly installed apps that didn't make a root permission request before this all stopped working don't