yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Thanks.

Yes, John seems to be resigning to let Hide Bootloader issues etc go due to futility of fixing this dead-man-walking (doomed) feature. However, he has remarked himself that hiding root etc in userspace (which is failing for you) is a separate matter / function of MagiskHide:

[MENTION=4667597]Didgeridoohan[/MENTION] may have some ideas too (that's a big log).

However, if you've tried all obvious measures, it may still be worth raising an issue... PW

---------- Post added at 06:10 AM ---------- Previous post was at 05:10 AM ----------

Thanks.

I knew, as I said initially, that flashing MagiskSU or boot/recovery images in TWRP booted only from fastboot is working for some.

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

However, others have had no such success when it has been flashed (stock recovery replaced), including other Pixel 2 XL users.

Please can you verify that you have been able to successfully flash MagiskSU or Magisk modified images with custom recovery installed (stock recovery absent), and that system is stable with custom recovery? :good:

If that is confirmed, it would not only suggest that mileage varies depending on device, but that TWRP may still actually be useful as an on-device Custom Recovery, at least for some devices, despite only being officially compatible with Android 10 and lower!

This would be welcome news for some... PW

Edit:

Latest TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10. See XDA article:

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

There's been no further versions.

As noted, TWRP still does not support devices that shipped with Android 10:

I'm betting it follows that TWRP doesn't support devices shipping with Android 11 either.

I don't know enough about the AOSP implementation changes in Android 11 to say for sure that TWRP 3.4.0 won't work with some devices that originally shipped with Android 9 or earlier and are upgraded to Android 11. I wouldn't be counting on it however.
[Magisk] cshlcsh:
Thanks for your very helpful hint! After few dirty flash finally I got it worked.

I inferred it is blamed on some unsupported modules. And I tried to run the "adb shell magisk --remove-modules " command while boot looping but it just led an instant reboot in that situation.

At last I made my poor P3 enter Safe Mode by holding vol down key when the Google animation starts. Then restart, all the modules have been removed automatically and magisk works normally.
[Magisk] randomaccess0:
Thank you very much for looking into the issue and reposting the boot.img. Misleading error messages are so annoying... why don't they just tell people to login? :confused:
[Magisk] Rexionas:
Is there a bug with magisk and obb files that prevents Store and other apps of installing them? And, I don´t know why exactly, but the only way to avoid bootloops is unticking "Magisk Hide" before a power off or reset... My phone is a Moto G7 Plus with Android 10 and all up to date.
[Magisk] Didgeridoohan:
That pinned Github issue is so that John doesn't have to deal with a ton of "this or that app is detecting root" posts in the repo issues.

Posting about a possible bug, describing it properly (make sure to note that not only apps added to the Hide list crashes) and providing a logcat showing the instabilities is another matter. Worst that could happen is that the issue will be closed with no further comment...
[Magisk] Hyflex:
Hi,

I updated to Android 11 on my Pixel 2 XL and of course lost root/magisk so I did the following:

1. Installed TWRP 3.4.1

2. Installed Canary version of Magisk Manager

3. Switched release channel to Canary

4. Downloaded a copy of my ROMs "boot.img"

5. Patched it with Magisk Manager

6. Installed magisk_patched.img as my boot image... Nothing happened, Magisk wasn't being detected as flashed.

7. Downloaded the latest Magisk zip installer via the Canary Magisk Manager.

8. Installed Magisk-e66b0bf3(20425).zip via TWRP.

9. Phone kept booting into the bootloader...

10. Used TWRP to installed Magisk uninstaller to remove three bootloop.

What am I doing wrong? I can't see what I've done wrong to cause bootloops.
[Magisk] Never_Sm1le:
If anyone want to disable addon.d creation, just delete the addon.d.sh in the 'common' folder of the magisk zip. The install log still print "add addon.d survival script" but no script will be installed.
[Magisk] Didgeridoohan:
Change 1 to "boot TWRP". Having TWRP installed when using A11 is known to cause incompatibilities with Magisk.

If things still doesn't work after that it could of course also be issues with a module that you still have installed, and that isn't compatible with A11.

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

On the Canary releases, instead of enabling Core Only Mode, you can boot to Android's Safe Mode to disable modules (I'm going to add info on that to the guide when the next stable release drops).
[Magisk] Alxoom33:
Yeah, I agree with the comment above. TWRP and Magisk are incompatible in A11. You need to boot TWRP, not install it. Then you can flash Canary Magisk zip. I think 26 is latest version. Keep the TWRP image in your fastboot folder to boot when needed.
[Magisk] pndwal:
Not sure TWRP is incompatible only if Magisk is installed on Android 11!

As noted, latest TWRP still does not support even devices that shipped with Android 10 (irrespective of presence of MagiskSU), let alone 11, as "TWRP 3.4.0 does not yet bring support for dynamic/logical partitions, which is required to support devices that launch with Android 10..."

So, at least for recent devices, there is simply no TWRP support.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83494999 (scroll to 'Edit' at end.)

Latest Canary MagiskSU is still ver. 20425 w/ Magisk Manager ver. 299 afaics... But you got my hopes up! :p PW
[Magisk] Hyflex:
Before I remove modules with that command is there a way to get a list of currently used ones?
[Magisk] 73sydney:
Heres one of many ways....from TWRP or other recovery terminal

find /data/adb/modules/ -type d -maxdepth 1 | sort > modules.txt
[Magisk] monicaONxda:
Can I install TWRP after (!) Magisk (rooted) on Android 10 ??

Can I just ADB "fastboot flash recovery twrp-xxxx.img" ?

Wouldn't it overwrite Magisk, which is installed on recovery also?

Will it work with encryption (already encrypted with screen password)?

Which TWRP image (link?) do I exactly need for a Galaxy Note 10+ (Exynos) ?

Thanks in advance!
[Magisk] zgfg:
Nice command but if TWRP is available, one can simply use its File Manager, go to /data/adb/modules and disable one by one of them (to find a culprit) by putting an empty file named disable to each modules subfolder

If TWRP is not available, you can use Android Safe Mode method to disable all modules (hence they won't be wiped)
[Magisk] Flyhighorflyhome:
Is there a Magisk module that disables the annoying copy protection and forced screen locking that comes with managed work profiles?

Seriously, all I want to do is copy some text between two apps and the damn InTune crap won't let me. The forced pin entry everytime I turn my screen off drives me up the wall. I ended up just never allowing the screen to turn off.

It's funny, phones are so much more locked down than personal laptops.
[Magisk] Hyflex:
Thanks guys! You were all spot on, it was TWRP that was the problem.

Interestingly the "patch boot image" option isn't working (doesn't appear to be patching anything because magisk never gets installed with it.), only the downloadable zip is working.
[Magisk] pndwal:
Guessing you tried both methods using TWRP (booted only). I'm sure all TWRP methods will have limited success as it's not fully supported in Android 11 on any device.

I think the "patch boot image" option is still most likely work directly from fastboot (fastboot flash Magisk-patched boot or recovery image). This is the official method to utilize Boot Image Patching. (TWRP image flashing is not mentioned suggested in official Installation Instruction.) PW
[Magisk] Hyflex:
Yeah when TWRP was flashed it wasn't working so I removed TWRP.

The fastboot route did not work, the patched image that magisk created was written but wasn't detected by Magisk as patched...

I simply downloaded the zip archive, booted into TWRP and flashed the zip. This worked perfectly.
[Magisk] LebHouseBeatz:
Does the bootloader need to be unlocked on the Samsung S20 ultra snapdragon version sm-g988w in order to flash magisk Or boot into recovery mode?
[Magisk] zgfg:
Generally, locked Bootloader is protection from flashing - therefore it must be unlocked for flashing Magisk, TWRP, custom ROMs

Btw, for the general questions like unlocking Bootloader, Recovery/TWRP or so, please consult XDA Q/A, Guides for your device
[Magisk] :
Hi,

Is [org.microg.gms.droidguard/com.google.android.gms.unstable] a default APP in MagiskHide list?

When I checked the log of Magisk, it showed up to me.

Because I never downloaded any microG module in to my phone,

I'm worried about that is some malware made it or not...

Thanks
[Magisk] 73sydney:
I was responding exactly to the question posted :)

Why quote me and then make it look like i didnt know what i was doing?

One of the rare times i was 1000% on topic....
[Magisk] zgfg:
Qouted you bcs I liked your command (btw, tried to play with to include info if particular module is disabled or scheduled for uninstalling, it would need some grep options in the pipe, but gave up)

And I quoted back the original question for the big picture bcs the guy maybe asked about saving at lest the list if all modules, if removing all of them by adb command would be his only way to get rid of the bootloop.

So telling him (maybe he didn't know about and therefore did not formulate in his question) that there are less invasive ways

E.g., if I would have a bootloop due to e.g. Systemless hosts, I would be very unhappy to loose all my 6-7 other modules, since for some of them it would be a pain in the ass to configure the things all over again (e.g. settings in the V4A app).

And keeping just a list of all the lost modules wouldn't make me happy a lot

So sorry if you think I did something inappropriate, but if you think so, you can report my post to the moderators

Edited: removing a duplicate due to the XDA app connectivity issues

PS: Sticking exclusively to his original question, simple screenshot from TWRP would also do?
[Magisk] 73sydney:
Dude, its all good, i put a smiley in the previous reply, so i wasnt serious, but sometimes context is lost on here :)

Sorry you felt you had to justify things, and then write it out!

And its always good people are made aware of the disabled trick!

Top tip: If im serious, i wont put a smiley in

As for V4A settings, if youre using the apk version from here save your presets and then copy the /sdcard/Android/data/com.pittvandewitt.viperfx/ folder somewhere safe, and copy back if you need to reinstall or after a ROM flash

Hehe why do what you can with a simple screenshot, when you can do it with a long command in a terminal :)

Addendum, the command youre looking for to find disabled or other files under a tree is

find /data/adb/modules/ -name "disabled" | cut -d "/" -f 5

- will work with least amount of typing

find /data/adb/modules/ -name "disabled" -type f -maxdepth 2 | cut -d "/" -f 5

- more correct syntax and with subdirectory limit
[Magisk] Rana.ravinder99:
Paytm first games detect root i tried all method (hide magisk , prop configuration, rename magisk) but nothing working pls anyone help how paytm first games detect root and what solution
[Magisk] pndwal:
A quick simple XDA search turned up threads like this:

https://xdaforums.com/moto-g5s/help/help-paytm-app-forces-users-to-t4059381

Not sure that one's the game, but the information on isolating apps / using contained space may help.

Detecting root is complicated by Devs not relying on SafetyNet attestation, but using their own customised detection means. Therefore, searching for information regarding a specific app and it's use with root on XDA is often better than asking here. :D PW
[Magisk] simo6:
hi there i am using latest canary e66b0bf3 (20425), hidden with random name, hided the app (Nexi Pay), even tried conteinment using storage isolation, but it keeps detecting root and doesnt start. Any other ideas what i should try? or is it a known issue?

thanks in advance
[Magisk] vangry2020:
Do apps require superuser always? Or can i disable them in magisk when im not using them?

Example: Warden does it block trackers permanently or it has to be running with super user access always?
[Magisk] ch3mn3y:
When MAGISK patches the boot imagedoes it resign it with different key?

I'm trying to root my Unisoc tablet, but avbtool won't allow me to sign the patched boot.img using my key (had to be same as ne added to vbmeta).

Unfortunately other users reported that after flashing magisk patched boot Unisoc tablets (at least with same SoC mine have) doesn't boot at all.
[Magisk] logitechor:
Hi. Thank you for Magisk. I successfully have it installed on Essential phone with Android 11. Even installed a module. Much appreciated.
[Magisk] NeverTooYoung:
I have received a notification concerning Google Play System, telling me that it is ready to install, and offering a button to do it now, or at 1:00 AM.

I am a OP 7Pro, OOS 10.3.4, magisk rooted with xXx No Limits. Using my Playstore App/Installed Apps, I see that Google Play System is showing as not installed.

My Caution Detector is ticking! A search among these pages doesn't tell me exactly what to do, or if I should be especially worried. Do any of you know anything about this please?
[Magisk] fdl_chris:
I'm using LineageOS 15.1 February 2020 (last version) on Huawei Nexus 6P (Angler) with no Google Play services (Gapps, microG, etc.). There are no further LineageOS releases for this device. AddonsSU is not installed at this point.

I use Rootbeer Sample to test whether the device is rooted or not.

For quite some time, I'm unable to get Magisk to fool Rootbeer Sample into thinking the device is not rooted.

So, I've removed Magisk and Magisk Manager to start a fresh. I've documented the result of Rootbeer Sample throughout the re-configuration.

1) After uninstalling Magisk v20.3 and Magisk Manager, I run Rootbeer Sample and it displays "rooted", failing on the following:

- DANGEROUS PROPS

- SELINUX FLAG ENABLED

2) After installing Magisk Manager (via the .apk) and Magisk v20.4 (via TWRP), Rootbeer Sample displays "rooted", failing on the following:

- ROOT MANAGEMENT APPS

- SU BINARY

- SU EXISTS

- DANGEROUS PROPS

- ROOT NATIVE

- SELINUX FLAG ENABLED

3) I then installed the AddonSU for LineageOS 15.1 (https://mirrorbits.lineageos.org/su/20190709/addonsu-15.1-arm64-signed.zip) via TWRP.

Rootbeer Sample fails with the same as above.

4) Enabling 'Hide Magisk Manager' and renaming the app:

- SU BINARY

- SU EXISTS

- DANGEROUS PROPS

- ROOT NATIVE

- SELINUX FLAG ENABLED

5) Enabling 'Magisk Hide' and selecting 'Rootbeer Sample':

- ROOT NATIVE

I am now left with just 'ROOT NATIVE' failing.

I have no modules installed at this point, and I'm a complete novice when it comes to which modules to select. Will the installation of a module help at this point?

I disabled developer options on the device. This didn't solve the issue.

The bootloader is unlocked. Will locking this help?

How can I resolve the 'ROOT NATIVE' failing?

Readings:

https://www.xda-developers.com/how-to-install-magisk/

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] Vinnom:
I'm not sure if magisk 20.4 has this feature, but you can try change magisk manager name in its settings. If it is not possible, change magisk update channel to canary update and try again.

I find it hard that a module will help with this as hiding its a magisk feature, but ofc I could be wrong about this. Also, before doing this canary thing, backup your boot.img on your twrp.
[Magisk] Didgeridoohan:
Why did you do this? If your goal is to hide root, don't install stuff that Magisk cannot hide... Magisk can only hide itself and it's modules (unless they do silly stuff).
[Magisk] Ch3vr0n:
Google play (security) updates are independant updates, and themselves don't give a damn about being rooted or not. It's the Google safetynet API that tells the play store and aps relying on it if you're device is certified.

I'm rooted, zero issues installing those.
[Magisk] zgfg:
Instead of postponing for (5), you had to check (and to enable) Magisk Hide first/after you installed Magisk 20.4

Root native at point (2) was Magisk, because you didn't enable Magisk Hide.

But Root native at point (5)is likely your AddOn SU from (3) - and btw, what for do you need that, Magisk gives you root and su

Btw, I don't see in any Readings you put to the bottom that installlation of AddOn SU was suggested.

Googling shortly, that AddOn SU is LOS add-on to provide root - if you wanted that root, then you didn't need Magisk (but with that root I doubt you would ever pass RootBeer, or more importantly SafetyNet)

I have no Sammy and don't use LOS but I would suggest you to start from scratch (making sure there is no Magisk and no AddOn SU with no remainings whatsoever).

Then install Magisk 20.4 or Canary and immediately enable Magisk Hide.

If you like RootBeer, then additionally Hide Magisk Manager and voila
[Magisk] fdl_chris:
If you are referring to changing the name of the Magisk Manager app, as mentioned in my earlier post, I already did that and it did significantly improve things. But thanks for confirming.

In regards to the update channel, in Magisk Manager v20.4 now has the options 'Stable', 'Beta' and 'Custom'. I presume 'Canary' was 'Beta'? I will give it a try, but after trying some other options first. I am not expecting the update channel to have an impact on whether I can change the result of 'ROOT NATIVE'.

I can now see that addonSU would be the same type of root management apps, which is stated that Magisk cannot hide, found here: https://www.didgeridoohan.com/magisk/MagiskHide

But I thought the purpose of Magisk was to be able to root the device (which is what addonSU does for LineageOS) and hide the fact that the device is rooted from other apps? Wouldn't removing addonSU defeat the purpose of using Magisk in the first place? After all, in my earlier post, during step 1 (before both Magisk and AddonsSU were installed), I wasn't receiving a failure in Rootbeer Sample for 'ROOT NATIVE'. It appeared in step 2, as a result of having Magisk installed (but still no AddonSU).

Thank you pointing that out. I will check and confirm.

Indeed. My understanding was that in order to root my device, I required AddonSU, and that I required Magisk in order to conceal the fact that the device was rooted from specific apps. So Magisk is also able to root the device _as well as_ hide the fact that it is rooted also?

Thanks. I did attempt starting from scratch, but I do now realise that Rootbeer Sample remained on my device before re-installing Magisk. I will also try these reproduction steps also.

EDIT / UPDATE: Removing AddonsSU allowed Rootbeer Sample to pass (as expected) and the app now sees the device as 'Not rooted'. From what I understand, based on the replies to my post, Magisk will root the device (without the use of AddonsSU), as well as hiding that fact from other apps (via Hide). Thanks for your help. I'm still a root/Magisk novice so it was somewhat difficult to get my head around initially.
[Magisk] Didgeridoohan:
Magisk is the full package. Root, root management and root hiding. For most cases you don't need anything else.
[Magisk] Strephon Alkhalikoi:
And, if I recall correctly, the LineageOS root package is discontinued anyway; they recommend Magisk.
[Magisk] zgfg:
And framework for its modules ?
[Magisk] pjbeee:
Lost some time here, and a tense moment or two as well because I wasn't aware of the Magisk/Canary channel. Pixel 2XL in bootloop.

Reflashing boot.img wasn't enough. Needed to reflash the OTA zip but that got me back to no-root status, no data or configuration loss. It was only then that I found the references to Canary. Confusion reigned, as initial searches found Canary on Chrome. Nitpicky maybe but perhaps Magisk could have warned me of Canary from within the app.

Anyway my Pixel 2XL + Android 11 + Magisk-Canary did the trick. Magisk still rocks, of course!
[Magisk] rc0n:
Im having trouble finding an install/uninstall option in Magisk Manager now for some reason. I have had Magisk and Magisk Manager installed for months, but under the Manager section, where it says latest, it just has the text "Loading..." forever. I don't have an install or uninstall option, and I'm not sure why. I've rebooted my phone a few times and nothing seems to fix it. I need the uninstall option to install an OTA update. Any ideas?

Update: It seems like changing the update thing from Canary to Stable fixed it
[Magisk] ipdev:
A note in case someone else runs into it on another device.

MagiskHide is breaking adb for me on an older (arm) device.

Nexus 10. Unofficial LineageOS 17.

This is a stable but broken rom, call it a first/second stage beta.

ADB is insecure. SELinux is ignored/permissive.

Modules work fine, including systemless hosts.

MagiskHide works, save for breaking adb.

With MagiskHide active (enabled) I pass SafetyNet.

MagskHide inactive (disabled).

List of devices attached

R32CC022X8T	device

MagiskHide active (enabled).

List of devices attached

R32CC022X8T	unauthorized

When MagiskHide is active (enabled) I am unauthorized and can not connect to the device.

Android debugging is still enabled under Settings-> System-> Developer options.

If Debugging notify is enabled, I get a notification USB debugging connected

This version of LineageOS offers a Rooted debugging option.

The Rooted debugging option disappears from Settings-> System-> Developer options.

Ran out of time for testing.. Still need to test some more..

For now I will just disable MagiskHide and reboot if I need an adb connection.

Cheers. :cowboy:

EDIT:

Sorry forgot to mention.

Magisk 20425

Manager 299 (Repackaged/Hidden.)
[Magisk] jdubu420:
Hello everyone!

First of all I would like to thank the devs and everyone who has contributed to Magisk Manager. As someone who has been using custom roms & rooting since the Galaxy S2 was around, I must say this is the most elegant option for rooting I've seen. Quite a step forward I must say.

Now onto the reason for this post... I recently tried rooting an XT1995-5 (US Factory Unlocked) with Android 10 with the latest stable Magisk 20.4.

Everything seemed to work fine except for updating of the apps and some apps were behaving strangely. In the playstore I could no longer download pokemon go without the playstore crashing. Also 6 other apps (Chrome & Google VR were among them, can't remember others unfortunately) refused to update.

Now it's important to mention that I had created & successfully applied the smali patcher module with the default options. Magisk Hide was also enabled and hidden from the playstore services. I passed all safety net checks. I was not using any other modules.

Another strange thing I maybe should mention is that I was able to install PoGo by downloading the APK from a mirror site. The app seemed to work fine aside from the icons inside the app being mysteriously gone (the pokeball / binoculars.) But I could move around with GPS Joystick.

On the same device with android 9.0 I didn't have any of these issues and it all worked perfectly so I assume this must be related to Magisk / Smali & android 10.

Re-flashing the stock android 10 rom & re-locking the bootloader did fix all the issues.
[Magisk] dcarvil:
The "R32CC022X8T unauthorized" message means you have to authorize the connection on your phone. You should have a message displayed on the phone screen with the authorization button. The message is displayed for only a short period, so you have to be fairly quick.