yashsingh1/xdaforums huggingface dataset:
[Magisk] jcmm11:
That's an unauthorized site. You should really only download from github (although you can also find Manager on apkmirror, which is the only other place I'd consider trusting. A hacked version of Magisk would have free reign over your phone)
[Magisk] jesterpaul:
Hi folks.

Sammy Galaxy S20 Ultra 5G user. Run stock firmware bit I have unlocked the bootloader so the knox fuse has been tripped.

I have magisk canary installed. I hide magisk manager and use magisk hide on numerous apps.

My device started failing safety net when Google updated it to using hardware attestation (as is inevitable).

I have installed magic props config magisk module and run the force basic attestation props command, and with this my device passes safety net again.

I am successfully running several apps that would not work on rooted devices with this set of workarounds.

ThreeNow (New Zealand TV app)

Ramco Unify

Microsoft Authenticator

McDonald's app

However I cannot fool Intune Company Portal, meaning I can't use any apps that allow me to connect to my work Office 365 accounts and services, such as Outlook for my work email, Skype for Business, Microsoft Teams and others.

Has anyone found a way to cloak root for Intune Company Portal?
[Magisk] nidico100:
After hiding the Manager (8.0.0 / 8.0.1 / 8.0.2) I can't open Magisk Hide without crash. Also since this morning my Safteynet fails. Anyone else with this problem? Did a fresh install and cleared caches and so on.
[Magisk] zgfg:
What's failing for SafetyNet. If it says CTS Hardware, please it was mentioned here countless times during the last months (and maybe yesterday again to somebody), MHCP module, option 2, Force CTS Basic...

This is something Google turns on/off/on again per device models and if your phone was not affected yet, now probably becomes

For the crash don't know about 8.0.x (Canary Manager is newer and with additional fixes) but you can try to clear data from Settings/Apps
[Magisk] nidico100:
Both were failing CTS and basicIntegrity, I did not change anything. Did not update any module or anything else. On a stock ROM OnePlus 6T. Google changed something to detect things. Reducing my modules to YouTube Vanced passes safetynet, but I still have to look what exactly is triggering safetynet to fail and why it started just today.
[Magisk] pndwal:
What exactly is the error message?

Could be unable to use this if you selected default option for MagiskHide Props Config Force Basic Attestation as I imagine you'll be spoofing an old device (as this was thought to be required initially). Check what model shows in settings.

If an old Sammy device shows here, or in terminal as current device for Force Basic when running 'props', try choosing a late / closely related Sammy device using Manual 'f' option ('Full on experimental mode' / 'Fun times for Power Users' :D ).

Try S20+ 5g for example, and Basic Attestation will still be forced (as you only need to use a model prop that differs slightly from the actual model to cause the mismatch that triggers fallback to Basic), but device specific functionality will be better.

This will be a long shot if it's actually detecting root, but could be worth a shot even in this case.

You'll likely also need to clear data for intune after setting model prop manually, or uninstall and reinstall to make it work.

Hope it helps, PW
[Magisk] Spartacus500:
Hello, some new applications detect root via the process

"tmpService"

"/proc/%d/mounts"

Is it possible to hide this in Magisk hide for all applications? This would solve the root detection issue for applications where Magisk hide does not help. One more thing, in the Magisk manager 7.5.1 version you can hide all system applications such as NFC, and in the latest version of Magisk manager 8.02.307 the NFC application is not visible at all.
[Magisk] zgfg:
Two weeks ago there was a similar discussion why Xiaomi Security app is no more visible for Magisk hide. You could find something applicable to your case

E.g., it is still possible to control through Terminal, code was given in the post from Oct 15:

https://xdaforums.com/showpost.php?p=83718633&postcount=42158
[Magisk] zzz2002:
Have you enabled show system spps in the magiskhide list.
[Magisk] Spartacus500:
Of course, on the latest version it doesn't display all system applications.
[Magisk] zgfg:
Did you please see my answer three posts above

Anyway, certain apps are now 'hidden' from the Magisk hide list (don't ask me why, some new and intentional changes with v21) but you can still manually add e.g. com.android.nfc to the hide list from Terminal, with su:

>> magiskhide add com.android.nfc

Then, you can see the new list:

>> magiskhide ls

By magisk hide rm you can remove it from the list
[Magisk] mbruska1281780:
moto g power

magisk following boot not recovery method.

go to flash the boot it fails guide says if that happens just do the recovery method.

so i being oh so clever decide ill just type the recovery cmd but i nvr changed the boot to recovery. so i used the same magisk_patched.img from the first "boot.img" method to do the magisk_patched.img "recovery" method. i nvr made a recovery patched file only the boot patched file for both methods. i hope someone understands what im saying
[Magisk] wilsonhlacerda:
This is really weird. I'd say even a bug. Doesn't make any sense hide that on GUI and be able to do it with command line....in a tool that is towards advanced, niche users, as Magisk is.

If it was a broader usage app, for Android users in general and that a "danger" settings, ok; but it is completely the way around.

Maybe it deserves an issue on Magisk Github.

---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------

On the Inter bank app for now it is just a warning, but saying that they will complete block in a few days (I believe on November, due to a new online realtime payment system that is being implemented in Brazil).

In fact they have already blocked it (root and/or custom ROMs) a few weeks ago, but then reverted to the warning only meanwhile.

This will be really a problem. Inter bank is the main online only Brazilian bank, with some million users, lots of them were early adopters (tech people, that tends to use custom ROMs and/or root more than people in general).

And in Brazil all banks - also Inter - uses mobile apps also as 2FA for web/phone transactions. Typically without an working mobile app you are completely locked out of the bank account (can only do transactions on physical branches....that Inter and C6 banks for instance don't have).
[Magisk] zgfg:
Magiskhide command works (and did work) for all apps and the tool is documented in Magisk Guide on GitHub

It's not about Magisk v21 (it still reads whatever apps it finds in DB as listed for Magisk hide and hide itself from)

but about new Manager (it filters out some apps, not showing them even if they are already in DB for Magisk hide)

If you did have NFC listed in your Magisk hide list with Manager 7.5.1, it will be still in the list and new Magisk will still hide from, you just won't see NFC in the list in new Manager (you can see only by the magiskhide command and you can remove it from the list by magiskhide command)

You can report to GitHub, I'm interested to see what will TJW do with the reported ussue?

I did report for another app, he actually gave me the hint that I can use magiskhide command but he closed the issue saying that changes in new Manager (only!) were intentional and that if I do it by the magiskhide command for those apps that new Manager does not want to show, that I'm hiding Magisk from those apps on my own risk and that it's not for general use

Btw, I don't use e.g. Gpay, but from reports of other people (and a thread about making GPay to work) I didn't see that it would be necessary to enlist NFC for Magisk hide, to be able to make paying by NFC to work
[Magisk] Spartacus500:
Everything understands how to add a new app in Magisk hide where the latest version can't see these apps but I have another question how to add the corresponding process of the given app to magisk hide? Let's stay with the NFC application, Magisk manager 7.5.1 sees 3 processes to hide, but the application itself has 4 processes, this is just an example, and the question is how to add other processes of 1 application to hide magisk, where Magisk manager 7.5.1 or the latest (example NFC) does not see them at all to hide? Is it even possible?
[Magisk] zgfg:
As said, magiskhide tool is described in Magisk Guide on GitHub.

Also, type magiskhide in Terminal and you will get short instructions.

You will find the answer yourself, it is pretty simple and logical - for process use the second argument.

Please read and try things before asking
[Magisk] J.Michael:
You do not say what state device is in now. Does it boot? Can you boot to recovery?

Have you tried flashing stock ROM? Then follow correct procedure.
[Magisk] McGrady:
I have magisk 21.0 with manager 8.0.2 and also with magisk 20.4 I had a problem. Manager did not hide. whenever I rename it an error occurs. Any idea
[Magisk] guest4711:
Perhaps no internet connection for MM. Or invalid update channel.
[Magisk] McGrady:
Hi,

i tried it with wlan and lte... no change

and i tried on update channel Beta and stable.

the same error :(

---------- Post added at 07:06 AM ---------- Previous post was at 07:06 AM ----------

Hi,

i tried it with wlan and lte... no change

and i tried on update channel Beta and stable.

the same error :(
[Magisk] zgfg:
Sorry, no idea without your proper details:

- Your phone make (and model, ROM, Android version)

E.g., for Xiaomi, you must enable Install via USB in Developer options

- What "error occurs"?

E.g., you give MMngr name for the repackaged Magisk Manager.

Does it create the ugly icon (oversized, generic Android icon - not ' standard' Magisk Manager icon) with the name MMngr or not?

If it creates that MMngr icon (stub for the repackaged Manager), does it fail to open it to continue installation?

Or something else?
[Magisk] parkerlreed:
So this worked back then but installing now never shows up. Is there something that has to be updated?
[Magisk] Didgeridoohan:
If you take a look in that repo, you'll see that it was last updated in 2017... So yes, the module installation scripts definitely needs to be updated to be able to install on any current Magisk release.
[Magisk] amajamar:
After figuring out how to use mhpc, it was the changing of the attestation to basic that fixed the safety net issue... Temporarily, I suppose.
[Magisk] McGrady:
Hi,

I should have written that the data in my signature is still current.

But your hint worked :) and DKB Banking App is running again.

Thanks and have a nice weekend
[Magisk] Muledeer:
OTA update question

I've successfully installed Magisk (21005) and two modules (systemizer and MHCP) - systemizer doesnt quite work on Android 11 (Pixel 3) because of the App folder name.

But my question is simply can I still update OTA in my current configuration. I've read that I may have to upload the stock boot rom to install the OTA. I'm not really sure if any instructions are current enough for my present configuration. I have used MHCP to change my prop desc to Nexus 5 in order to pass safety net.

I've received a lot of information and help on this site - XDA totally rocks as a forum.

I will probably refrain from updating until I find instructions for updating from my (android 11 Oct) update - If anyone can point me to instructions that may work I would truly appreciate it

thanks

Mule
[Magisk] dcarvil:
You can uninstall Magisk (Restore images) instead of flashing the stock boot rom. You will have to re-root after the OTA. You may not even see the OTA update in System Updater until you uninstall Magisk.

The method I use is:

Download the new factory image, and patch boot.img

Uninstall Magisk (Restore images)

Either take the OTA via System Updater, or flash-all with -w removed. Not much difference in either method.

Reboot - this will cause loss of root. Wait for update to complete.

Flash patched boot image.

Reboot - this will restore Magisk

I don't have any Magisk modules installed. If you want to be super safe, either disable or remove the modules before starting, and restore them afterwards.
[Magisk] :
Hi, I have a problem with my Motorola G7 Play. To root stock, I patch the boot.img but after flashing the image it doesn't work, nothing or root appears

Can anyone help?
[Magisk] RandomPooka:
Have you unlocked your bootloader?
[Magisk] pndwal:
Seems yours might be a strange one.

If you haven't found these threads, they may help, but some contradictory info there:

https://xdaforums.com/g7-play/how-to/magisk-g7-play-xt1952-4-installed-t3975477

https://xdaforums.com/g7-play/how-to/magisk-twrp-gsi-wont-stock-t4128789/

May actually have root, but need to boot to recovery, may need simply to flash both a & b slots w/ patched boot image, may be something else.

I'm interested to know Ramdisk, A/B, SAR, Crypto configuration for G7 Play as shown on Magisk Manager Home page, and evalType shown after Check SafetyNet... With this information, I, or someone else, may be able to offer tailored suggestions. PW

Edit: seems your device is A/B, SAR, no Ramdisk, so official method is to patch and flash Recovery image extracted from ROM, NOT boot image:

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

Note the startup options in Magisk in Recovery section.

I'd be trying this using latest Magisk Manager. If Stable doesn't work, Download Canary to access Canary channel.

If that fails, check methods in threads above (but they seem more confusing to me).

Here is a method using TWRP (if all else fails):

https://www.androidinfotech.com/root-moto-g7-play-android-10-channel/

Nb. Modified DTBO (device tree blob overlay) image is needed to make TWRP work:

https://xdaforums.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
[Magisk] Cygnust:
Please help !

Hi guys,

i'm pretty lost.

I installed LineageOS 18.0 with twrp on my OP6 enchilada.

Decided to give a go to magisk, followed the patch boot method and when I rebooted my phone is stuck on "phone is starting"

When rebooting to twrp, it asks for a decryption password but mine does not work.

Please help ..

Update :

Made an adb logcat and it gives me "Failed to find provider info for com.android.contacts (user not unlocked)"
[Magisk] pndwal:
A possibility:

Many have found they must have stock Recovery when flashing Magisk w/ Android 11. Incompatibility is likely your problem.

Nb. NO TWRP is compatible with devices launched with Android 10 or above. The last version was made compatible with devices updating to Android 10 but retaining old file system structure.

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

My understanding is that the file system structure generally didn't change on devices updated to Android 10, but may well have on moving to 11.

Nb2. Many are still able to use TWRP functions if needed by booting only (not flashing) through ADB fastboot. It is generally not needed for patch boot image method however; fastboot flash is officially endorsed method. PW
[Magisk] Cygnust:
Hi,

thanks for your answer.

I flashed magisk_patched with fastboot and not with twrp.

My problem is that now, my phone is stuck with "phone is starting" endlessly

I tried to acces my data with adb and I can't find it anymore.

When I reboot in twrp recovery, it asks for a password but none works.

When I reboot in Lineageos Recovery, no password is asked and data is encrypted.

I'm pretty lost. and have no backup aside from online backup which is dated. Almost everything is on my sdcard.
[Magisk] zgfg:
8

Don't you have boot image before you patched, to flash from Fastboot to be able to boot again to LOS

Even if on SD card (but removable), you could move it temporarily to another phone and then transfer to PC
[Magisk] Cygnust:
I extracted boot image from payload.

Still the same.
[Magisk] pndwal:
Yes, but as I said, 'Many have found they must have stock Recovery when flashing Magisk w/ Android 11' (Irrespective of how Magisk is installed) as reported in this thread.

Just having custom recovery present is reported to cause bootloops w/ Android 11 and Magisk on many devices, although some (eg Mi Pad 4) are able to use TWRP/Magisk/11.

Not sure what this means, but can't you flash unpatched image to revert (as suggested)? (Failing this, you may need to flash stock.) PW
[Magisk] Cygnust:
Hi PW,

no when I tried to flash back the boot.img extracted from my payload.bin, it made nothing.

My issue now is that my phone is totally encrypted and no matter how, I can't decrypt it anymore, I guess that's why the phone is stuck with message "phone is starting" .

When I try to decrypt from twrp, it says my password is incorrect. When I reboot from original lineageos recovery, it doesn't even asks for a pin.

I don't know if problem if problem comes from Magisk, LineageOS, TWRP or probably 3 at the same time.

All I can say is that it worked before flashing the magisk_patched.img

Almost all my data is currently on my sdcard and I would like by all means to avoid formatting it.

If anyone can provide direct assistance or debug I think we can manage to understand why it happened and it could benefit the community. I'll let my phone aside for 1 day or 2 if anyone wants to help don't hesitate to DM me.
[Magisk] pndwal:
I still don't understand payload bin. :( Official method is to extract boot or recovery image from ROM to patch and flash. Should still be simple to extract original from LOS zip used, and flash that. I'm guessing it will then boot as it did unless you did more than patch original boot image... PW
[Magisk] Cygnust:
In LineageOS, you have to extract boot.img from payload.bin file which is in the lineageOS update zip file.
[Magisk] pndwal:
Interesting. My lOS 17.1 boot.img is in to root of zip, as has been for all LOS ROMs I've had since 14! PW
[Magisk] Cygnust:
I just checked a lineageOS 17 file and no boot.img in the root of the zip, maybe it's because my device is an A/B device ..

Still doesn't explain how patching the file can screw encryption at this point.

I'm really lost. .. maybe [MENTION=4470081]topjohnwu[/MENTION] could help ?
[Magisk] Didgeridoohan:
[MENTION=1098052]Cygnust[/MENTION] Was your device encrypted before installing Magisk? It definitely seems to have to do with the encryption, judging from your log:

11-01 12:29:57.051 595 595 E Cryptfs : cryptfs_get_password not valid for file encryption

Without knowing the exact steps you took and seeing the Magisk install log it's gonna be very hard to say exactly what happened. But there's a big chance that your data is lost (if the encryption has somehow failed).

Nowadays (Manager 8+) Magisk won't let you (easily) mess with the encryption or verity flags on devices where it's unnecessary/risky, so it's unlikely that you messed something up there (unless you went tinkering further than the default settings).

I'd say that your best bet at finding help is in your device's forum and the ROM thread. That's where you'll find people that know your device best.
[Magisk] Cygnust:
Thanks ..

All I can say is that I removed pin lock before upgrading.

My device was still stating as encrypted but clicking on encrypted didn't make anything.

Thanks for having taken time to check my logcat.
[Magisk] pndwal:
Could be why.

Still, if that image doesn't allow boot, seems it must have been bad in the first place. You need to find original unaltered (working) boot image which you had when it booted! Perhaps other LOS 18 users of your device could supply...

I was also going to suggest restoring stock Recovery (only), but doubtful this will work as both 'original' and patched boot images are likely corrupt/defective... It may be your extraction method I guess...

Is your SD formatted for adopted storage? If not, at least that data should be accessable on another device.

And if it is 'adopted', you can save the encryption key (in /data/misc/vold) and restore it after a clean install of IDENTICAL OS on IDENTICAL device, and it should decrypt / see adopted data again. PW
[Magisk] bluwolf024:
Magisk and Samsung Galaxy Tab S7+

After extracting boot.img (J4 oct update) and patching using magisk(20.4 (20400) (, then flashing using odin3 v 3.14.1_3B_PatcheD and odin3 v 3.14.4 ) I lose the ability to use samsung dex wirelessly.

anyone else have this issue with samsung galaxy tab s7+ (wifi model)
[Magisk] Cygnust:
Thanks a lot for the time you took.

I was talking about my internal SD (which is 256GB Size .. :( )

[MENTION=7550078]pndwal[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION] my analysis at the moment is that the phone doesn't ask for pin when not booted from fastboot.

That's why any os boots endlessly.

When booted from fastboot twrp asks for a pin lock but none works ..

This really arrived when installed magisk_patched :/
[Magisk] Didgeridoohan:
[MENTION=1098052]Cygnust[/MENTION] Could have been a combination of flashing Magisk while having TWRP installed (as already stated, TWRP isn't fully compatible with A11 yet), or something else entirely. No idea... But, at the moment it does seem like your device is unsalvageable. :(

If you do find a solution, give a shout-out.
[Magisk] J.Michael:
If you can download a new factory image, why take OTA update? Why not just flash new stock image?

If flashing stock image, why uninstall Magisk first? Won't stock image replace boot and recovery?

---------- Post added at 13:00 ---------- Previous post was at 12:42 ----------

Did you ever try reinstalling the operating system that was working before you tried to install Magisk? The file you used when you first installed LineageOS, the procedure you used.

What do you mean "clicking on encrypted"? What do you hope that will do? What do you mean "didn't make anything"?
[Magisk] Cygnust:
Yes I tried to reinstall. It boots endlessly.

In some tutorials I saw that clicking on encrypted allowed to decrypt the data
[Magisk] dcarvil:
I tried the OTA method just to see if there was any advantage over flashing a new stock image. There is no advantage I could see.

I uninstalled Magisk first because there were quite a few issues with Pixel 3 updates reported on GitHub. Restoring the stock boot image seemed to resolve those issues. It may not be necessary to uninstall Magisk first, but I know that method works, so I stay with what I know works. Also, my System Updater tells me there is no update until I uninstall Magisk.

Please let me know if you find it is not necessary to uninstall Magisk first.
[Magisk] pndwal:
That's a good thought. Not sure why this doesn't work either...

Another long shot: Have you tried flashing Magisk uninstaller? I'd use latest. This may just clean boot image...PW

Edit: What exactly happens when flashing unpatched boot.img from fastboot?
[Magisk] J.Michael:
Where is it that you click on "encrypted"?

How did you install Magisk? I thought the standard procedure required wiping data before allowing the system to boot. Were you able to install Magisk the first time without losing your data?

---------- Post added at 00:49 ---------- Previous post was at 00:43 ----------

I think I'm just hung up on the semantics: To me, "Uninstall Magisk" is removing Magisk, otherwise leaving system intact; flashing stock is blasting everything. Yes, flashing stock results in no more Magisk; if you used to have stock + Magisk, it is like uninstalling Magisk. Except, not quite: I expect uninstalling Magisk to do something about the data Magisk has scattered, I don't expect flashing stock to change the data partition.

*I* will not be finding whether it is not necessary to uninstall Magisk first -- I got my device rooted, and I will never accept an update from anyone, ever again.
[Magisk] pndwal:
John is facing same problem that has stalled TWRP development currently.

https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/

https://mobile.twitter.com/topjohnwu/status/1323014048468754432

But he can do it, I'm sure. PW