yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Please guys, before asking, do some basic search and read.

There is a search icon top-right, type in SafetyNet, it will show you literaly hundreds of posts in this thread already about SafetyNet. Same questions, same answers, repeating all over

Shortly, e.g. (most common case) if SN fails with Basic Integrity ok, CTS Profile failing by taking Hardware attest (new Magisk Manager nicely shows all these important details), then use MHPC module, Force CTS Basic option (hint, search here also about MHPC, CTS, hardware attest, basic attest)

If case of custom ROM (another important detail, not just SN failing), you would probably need to fake device fingerprint (also by use of Magisk Hide Props Config =MHPC module)
[Magisk] K4KKBNO1:
The ctsprofile is failing. What should i do.
[Magisk] zgfg:
Again it's not only about CTS Profile failing but is it failing with HARDWARE attest mode - in that case you need to install MHPC and set its Force CTS Profile BASIC option

As stated, search in this thread (or use Google to directly search for: MHPC module, its XDA thread, its Github guide) and particularly about using its Force CTS Profile Basic (although it is pretty straightforward once you install MHPC - from Magisk Manager Modules tab, and run props in Terminal)
[Magisk] pndwal:
Not sure how we've ended up with MHCP, MHPS, as well as MHPC... a little dyslexia? Non-English designations? :laugh:

Anyhow, searching for MHPC or MagiskHide Props Config module produces more hits as you might expect. ;) PW

Reminder to self: Pobodies nerfect.
[Magisk] Hopie:
Anyone use Targobank App?

With new app update, Magisk hide not wirking.

Delete new Targobank App and restore previous version all ok
[Magisk] Radityaargap:
version 8.0.3 is a little buggy. pop up windows don't show any options. [IMG="v8.0.3"]https://xdaforums.com/attachment.php?attachmentid=5138953&stc=1&d=1605908691[/IMG]
[Magisk] guest4711:
This may be caused by theming overlays. Do you use substratum?
[Magisk] Radityaargap:
i don't have any modules installed. no modification of anything. the only thing i use root for is my file explorer. previous version worked fine.
[Magisk] Spartacus500:
Work for me
[Magisk] MrMuscle:
I have OnePlus 7. I was going to install Oxygen OS 10.0.9 OTA. Before doing this I thought that my TWRP version is pretty old and decided to update it.

Downloaded new version, booted to twrp recovery and flashed the version 3.4.0-0. TWRP told me that I am not rooted anymore.

Booted succesfully to OS and looked up what Magisk says. Under Magisk read "Installed: N/A".

Downloaded new Magisk version 20.4, booted to twrp recovery and flashed the new version.

Boots succesfully to OS. Now I have two Magisk shortcuts, one named Manager (this is the previous version) and another thats named Magisk Manager. Neither one can be opened.

Could someone educate me what went wrong and how to get Magisk working again? Should I have updated TWRP through Magisk at first place and not through twrp? Do I need to remove magisk completely and install it fresh to get it working?

Oxygen OS it not yet updated. I only updated twrp and magisk both through twrp!

Added more information: Device had unlocked bootloader and root before this
[Magisk] zgfg:
First of all, uninstall both Magisk Managers (from Settings, Apps) - one hidden/repackaged and the other not hidden/repackaged/renamed

Then install Magisk Manager again and check does it work
[Magisk] MrMuscle:
Uninstalled both Manager & Magisk Manager.

Downloaded new .apk 8.0.3 from here and installed it.

Screenshot of Magisk Manager current state is attached.

Still need to do something?

......

Think I made mistake updating twrp through twrp. Because of this root was lost, or at least Magisk Manager thought it was lost. Should I have updated it through Magisk at first place?

I've used this guide 2. UPDATE when running ota update. At point 4. I've used TWRP A/B Retention script. Somehow I thought that in point 4 you can't flash new version of twrp and that's why I did it from twrp itself. I Think that was wrong decision and twrp can in fact be updated during this process. Correct me if Im wrong!

edit: Oxygen OS is not yet updated. Waiting for feedback if everything is Ok and what exactly went wrong.
[Magisk] zgfg:
Now I see that Manager shows Magisk is installled and that looks ok.

However, you are on the old Magidk v204 - if you have Android 11, you must switch to Beta or Canary v21.1

Generally about OTA, TWRP, etc, consult/ask in your device Forum threads. Things differ from device to device and it makes no sense that in this Magisk thread e.g. LG user gives advises to One+ user how to update OTA, install TWRP, or Pixel user to Samsung, etc
[Magisk] REAL6:
Does anyone know if it's possible to upgrade with using an apk and keeping root. My magisk manager keeps crashing everytime I try and open it and i don't want to delete the app.
[Magisk] webipsum:
Hi.

I installed Magisk in a Tanix TX6S Allwinner H616 box with Android 10.

With stock firmware:

The Magisk app is installed normally and installs Magisk at boot.

But MagiskHide DOES NOT WORK.

With the firmware of a TX6S clone, the T95:

The Magisk app is installed normally and installs Magisk at boot.

The MagiskHide WORKS.

I compared the 2 Magisk installation logs and apparently they are the same and all steps have been completed.

In the stock firmware, which is what I use and will continue to use, as the T95 firmware on my TX6S has an accessibility permission bug:

I did the test to turn Magisk on and off, as instructed in the FAQ, and the log shows the logs on and off and etc ..., but MagiskHide does not work.

Any tips and congratulations on the app: Magisk - The Magic Mask for Android.

Thanks.
[Magisk] Thanos Atha:
RecMe support on Magisk?

Please make Magisk Android 9 compatible with RecMe & GLTools......

I've rooted my Android 9 with Magisk, I successfully enabled InternalAudioPlugin for RecMe using the systemize command, I set it not-optimized for battery optimization from apps settings & developer options, but it crashes and sometimes does not recognize the audio plugin at all.....!

Also GLTools with Magisk needs a plugin which I installed, but it doesn't work either.....!

Please give an update on Magisk for RecMe Screen Recorder & GLTools support......

(I asked the app developers to update, too)
[Magisk] Didgeridoohan:
Clear app data or uninstall the Manager and install it again. All Magisk settings (superuser permissions, modules, MagiskHide...) will remain since they're stored in the Magisk .db and are not affected by whatever you do to the app.
[Magisk] Didgeridoohan:
Might be that something's missing in that stock firmware.

Try the Canary build and post the Magisk log after having tested MagiskHide on an app. Maybe something will show...
[Magisk] Didgeridoohan:
If an app doesn't work with Magisk it's the app that needs to be updated, not the other way around...
[Magisk] webipsum:
[MENTION=4667597]Didgeridoohan[/MENTION]

Please:

Just uninstall the application or uninstall via Magisk Uninstaller within the Magisk application?

I don't need to return the device to the factory default, correct?

I am grateful for the speed of your response!
[Magisk] Didgeridoohan:
You shouldn't have to uninstall anything... Just install the Canary apk, switch the channel and update.
[Magisk] J.Michael:
What app do you not want to delete?

If Magisk Manager: If it "crashes" every time you try to open it, uninstalling and reinstalling is usually a good idea. I don't believe uninstalling Magisk Manager will have any effect on whether Magisk is installed. I think if you uninstall Magisk Manager, you will still have root.

(I assume when you say "delete", "uninstall", "install", you mean Android level, like Android Settings -> Apps -> mumble -> Uninstall.)

You might need to use a different version of Magisk Manager.

Can you describe what you changed since the last time you were able to open Magisk Manager?
[Magisk] webipsum:
[MENTION=4667597]Didgeridoohan[/MENTION]

I installed Canary (app-debug.apk).

The app continues to detect the root.

Message:

Error

The device is routed.

Magisk log right after the app detects root:

--------- beginning of main
--------- beginning of system
11-23 04:24:55.512 1814 1814 I Magisk : Magisk 20.4(20400) daemon started
11-23 04:24:55.512 1814 1814 I Magisk : * Device API level: 29
11-23 04:24:55.568 1814 1815 I Magisk : ** post-fs-data mode running
11-23 04:24:55.571 1814 1815 I Magisk : * Initializing Magisk environment
11-23 04:24:55.644 1814 1815 I Magisk : * Mounting mirrors
11-23 04:24:55.645 1814 1815 I Magisk : mount: /sbin/.magisk/mirror/vendor
11-23 04:24:55.645 1814 1815 I Magisk : mount: /sbin/.magisk/mirror/product
11-23 04:24:55.645 1814 1815 I Magisk : mount: /sbin/.magisk/mirror/data
11-23 04:24:55.646 1814 1815 I Magisk : link: /sbin/.magisk/mirror/system
11-23 04:24:55.647 1814 1815 I Magisk : * Setting up internal busybox
11-23 04:24:55.684 1814 1815 I Magisk : * Running post-fs-data.d scripts
11-23 04:24:55.689 1814 1815 I Magisk : * Running module post-fs-data scripts
11-23 04:24:55.690 1814 1815 I Magisk : * Loading modules
11-23 04:24:55.711 1814 1823 I Magisk : * Starting MagiskHide
11-23 04:24:55.711 1814 1823 I Magisk : hide_policy: Hiding sensitive props
11-23 04:24:55.712 1814 1823 I Magisk : hide_list init: [com.hbo.broadband.br/com.hbo.broadband.br]
11-23 04:24:55.729 1814 1823 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
11-23 04:24:55.734 1814 1823 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
11-22 17:24:57.606 1814 1955 I Magisk : ** late_start service mode running
11-22 17:24:57.606 1814 1955 I Magisk : * Running service.d scripts
11-22 17:24:57.607 1814 1955 I Magisk : * Running module service scripts
11-22 17:25:16.568 1814 3245 I Magisk : ** boot_complete triggered
11-22 17:27:24.551 1814 1823 I Magisk : proc_monitor: [com.hbo.broadband.br] PID=[8950] UID=[10096]

Difference of the alternative firmware in relation to the stock firmware: the alternative (T95) has a root on / off switch and the stock firmware does not.

When installing Magisk on TX6S with alternative firmware to work, I had to turn the key on before installing Magisk and after installation I had to turn off the key for Magisk to work well.

But the stock firmware does not have such a key, although it is routed from the factory.

Sorry, I'm new to Magisk, didn't I understand your explanation about changing the channel? You could talk a little more about it.

Tks and best regard.
[Magisk] Didgeridoohan:
[MENTION=5543915]webipsum[/MENTION] By channel I meant that you should have changed the setting for the update channel in the Manager to Canary, so that we could get better logs.

You don't have to do that anymore though, because if the system comes prerooted there's nothing Magisk can do about that. MagiskHide can only hide Magisk, not other root solutions...
[Magisk] webipsum:
[MENTION=4667597]Didgeridoohan[/MENTION]

I understand.

For this Android TV Box TX6S I tested 3 firmwares:

Stock: MagiskHide does not work.

Clone Transpeed: I was unable to install Magisk and gave up because there are other problems.

Clone T95: MagiskHide works.

The implementation of Android 10 in these boxes, although clones, are different, especially the root. So I conclude that MagiskHide is working and that the app is detecting items related to the root that came from the factory.

I took the log with the Canary Channel. It is much more complete, but as you said, it does not work due to the rooting of the factory.

A good week and grateful to clarify these issues!

Now, I'm a little more than a newbie! (smile).
[Magisk] pndwal:
Something Strange?

I've been using my stock Redmi Note 8T for some time now, and have had Magisk Manager (Canary) installed also.

With bootloader locked, whenever I've checked SafetyNet, basicIntegrity ✓, ctsProfile ✓, evalType HARDWARE has been returned.

I've just unlocked bootloader (no root yet) and reinstalled stuff incl. Magisk Manager (Canary), and interestingly SafetyNet now shows basicIntegrity ✓, ctsProfile X as expected, but evalType now returns BASIC. :confused:

Not sure if some anomaly is causing a fallback to BASIC key Attestation after bootloader is unlocked (with no other intervention), of if Google just happened to exempt RN8T from Hardware key Attestation at this (same) time... Any thoughts?

FWIW, just took update to new MIUI 12 OS (which means an update from Android 9 to 10 for this device), and SafetyNet was still returning basicIntegrity ✓, ctsProfile ✓, evalType HARDWARE before unlocking. PW
[Magisk] J.L.C.:
Does anyone have a way to get around

"no valid slot to boot"

I have a stock Pixel 4XL and just tried to upgrade to Android 11 with the latest images from Google.

I tried to patch the extracted boot image with Magisk and when I try to boot, I'm stuck in fastboot mode with "no valid slot to boot"

I then tried to recover to unrooted stock using an edited flash-all.sh script

./fastboot flash bootloader bootloader-coral-c2f2-0.3-6648663.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-coral-g8150-00063-200702-b-6648947.img
./fastboot reboot-bootloader
sleep 5
./fastboot --skip-reboot update image-coral-rp1a.201105.002.zip

I see the "G" logo and the progress bar cycles a couple of times, then I'm back in fastboot mode with "no valid slot to boot"

Is there any way to recover the device?
[Magisk] pndwal:
I have no idea if damage may have been done by flashing bootloader. Hope it's an unmodified stock image.... not sure why you would do that...

Normally, you'd recover simply by flashing unmodified boot.img from fastboot. Now, however, probably best bet is to try to flash full stock from fastboot... Unless you messed bootloader up, but seems can still boot to fastboot mode. Inability to use fastboot would require researching method using Emergency Download mode, etc. Either way you'd be best to read procedures in your device's forums.

Did you patch boot.img using latest Magisk Manager 8.0.3 (314) or Canary (315) with public Beta or Canary channel selected (so public Beta Magisk 21.1 (21100) or latest Canary (21101) is used to patch? And from Android 11 environment? (NB. public Stable 20.4 is incompatible with Android 11.)

Also, did you keep Stock Recovery? (NB. no TWRP is Android 11 compatible!)

If not, once you can boot Android 11 unrooted (w/ Stock Recovery), install Magisk Manager and patch using 21000 series Magisk (SU). Then flash boot image from ADB Fastboot. PW
[Magisk] ipdev:
All I can say is, I still get Basic on my Stock Pixel 3a XL.

No Mods. Only Google stock ROM and Magisk (canary).

[ Temp boot patch boot image, then use direct install for permanent root. ]

I know others report Hardware on 3a XL after Google update.

I never got it but, I am signed up for a lot of Google's Beta(s) so might be in Google's Stable channel. ¯\_(ツ)_/¯

Ran it to it a month ago on my 3a XL.

My data partition some how became f'd. (fastboot -w failed when I tried to clean install.)

After more than few attempts [ and finally a booting version with a broken userdata partition ].

Yep, complete loss of userdata..

I was able to fix it by using the stock recovery.

- Install the Full OTA build. (Link below.)

- Factory reset. (This fixed userdata.)

Do not remember if I had to flash it to both slots or if fixing userdata was all I needed.

Just remember fast boot failed to format userdata no matter how I did it.

Full OTA Images for Nexus and Pixel Devices Link

Once I had it back up and running.

- Patched the boot image with Magisk manager.

- Fastboot booted the magisk patched boot image. (Temp root.)

- Then used the Direct install option in Magisk manager to patch the installed boot image with Magisk.

Hope it is that simple for you. :fingers-crossed:

Cheers. :cowboy:
[Magisk] Alxoom33:
Interesting. In October I flashed an alpha version of LOS 18 on my Pixel C tablet. I lost the ability to use fastboot with the tablet. I was able to recover and flash a beta LOS 18 version and TWRP recovery, but am not able to use fastboot. Is there a way to fix this tablet so it is readable by fastboot? Is it as simple as flashing the stock bootloader.img file, or is there something else? Thank you in advance.
[Magisk] Sanzium:
Hello!

There is a "modded" version of Magisk which is used to flash it on every android 11 rom made to Cepheus (Xiaomi Mi 9). As it is such a delicate piece of software to take from anywhere, I would like if anyone knows anything about it? Why doesn't official canary or beta 21 work directly (actually we have to flash the modded, boot into the rom, and then flash official canary or 21, if we flash directly, it causes bootloop).

Thanks in advance!
[Magisk] pndwal:
That's likely, but I don't know for sure. Pixel users may. But I'd say the most likely fix is to flash full stock.

Aside: Does fastboot just not work, or can you not boot to it? Have you tried enabling advanced restart in LOS Developer Options, and restarting to Bootloader from LOS? PW
[Magisk] Alxoom33:
I can boot to fastboot but my windows 10 computer didn't recognize it as a fastboot device. ADB works, though. In contrast with my Pixel2 XL which I can flash or boot with fastboot.

BTW, no advanced Restart available in LOS 18.0 Developer Options.
[Magisk] J.L.C.:
I flashed the stock images with the stock script, all I did was remove the -w flag. It's a Pixel 4 XL (Coral).

Yes, I kept stock recovery because there is no recovery partition, so stock is the only option.

Is there any way to recover data from fastboot? ADB isn't working.
[Magisk] JudgeDread11:
Then it's possibly a driver incompatibility issue. Or fastboot version issue.
[Magisk] zgfg:
How is it called?

I've seen similar for Mi 9T (davinci), to root Xiaomi.eu Android 11 beta builds, they use certain MagiskR.zip and then Magisk Canary (screenshot with instructions from the corresponding Telegram group)

I've tried to search about but everybody just cooy/pastes the same instructions, I could not find where the MagiskR originates from (maybe 4pda.ru)

I didn't install Android 11 beta builds, hence I don't know is it really necessary or that MagiskR is just a workaround since they (as many people still do - not being aware about that other way of installing Magisk or what?!) insist on flashing Magisk through TWRP instead of simply patching the image and flashing
[Magisk] Sanzium:
For cepheus it's called "magik-debug (2).zip", when you flash it says modded.

I am actually feeling very dumb right now, didn't know about patching the image and flashing :silly:

Thank you for the tip, will try once I decide to try android 11 again!
[Magisk] zgfg:
magisk_debug.zip could be just official Canary version from Github

Patching and Flashing is described in Magisk docs, few additions for Xiaomi:

- download recovery/zip package for the same/corresponding MIUI region and version (same you would flash to install that MIUI)

- extract boot.img

- install Magisk Manager (for A11 you must use Canary or Beta, latest), it can be the same phone (you already installed MIUI but didn't root yet) or even any other Android phone

- in Magisk Manager choose Install Magisk but Patch the image method

- leave Recovery option unticked and navigate to boot.img

- Patch and copy to PC Magisk_patched.img from Downloads

- Flash to your MIUI phone by Fastboot (to boot), Magisk Manager will show you that Magisk was insttalled

You can use the same method to update Magisk. I used always since MIUI 10/A9 till MIUI 12/A10 but didn't try A11
[Magisk] Sanzium:
I see, thank you.

I don't know if I will try it soon, A11 custom roms are still too buggy for daily usage, even TWRP does not support A11 decryption yet.
[Magisk] Hopie:
For me not.

Magisk 20.4 / App 8.0.3
[Magisk] Appreciative:
Hi guys.

I'm on a OnePlus 7T Pro 5G McLaren. Magisk and all that good stuff is fine.

I was using a module called Tethering Enable. That allowed me to get full speed on hotspot instead of 600kbps throttled hotspot speeds. I'm taking OTAs with the OTA fixer script in the McLaren 5G forum. At some point, my hotspot bypass module stopped functioning right. I am now throttled to 600kbps again.

My question is if someone knows for sure if it was indeed an OTA change that caused this. Or if you know another solution to try. Some have suggested editing things in build prop but I figure I should ask here first.

My phone is Read Only so everything must be done with magisk.

Magisk 20.4 / 8.0.3

TMobile 7T Pro 5G McLaren 10.0.40 OTA

Tethering Enabler 11.0 by Stangri & Fox8091

I've looked in the module before and if I remember right, it was a single edit in prop.

Anyway, all suggestions and help is appreciated. I need fast hotspot more than I need security patches. If it's a patch by the OTA, I may just revert. But if it's bypass able again, I'd appreciate the help. If you prefer to keep it private, I am open to PMs and can tip in btc lol.

Thanks
[Magisk] g000n:
How do I disable modules in Magisk like EdXposed so it allows me to login to Snapchat?
[Magisk] dope77:
Open magisk manager then go to modules, you will see a toggle on the right of installed modules' names. Tick the one you want to disable then reboot
[Magisk] noodlenoggan:
Repackage random name hung up...now Magisk is shown not installed

Hi all

I have a Oneplus7T with magisk installed and somewhat working properly. The device appears to still be rooted but Magisk does not indicate it's installed?

It all started when I ran the random name repackage function in an attempt to hide it from the Fetch Rewards app. After I provided the new name, MagMan, it appeared to be processing it but it turned out to eventually hung. After each reboot, a pop-up... MagMan: Magisk was denied SuperUser rights is displayed momentarily. I'm not sure if the package rename worked but Magisk Manager does not recognize it. I still have root on the device. Safetynet passed. I installed a root check and confirmed the device is still root. Attempting to run Fetch Rewards is stopped by their Root Detection message and the app is closed.

Possibly a bug in the random name repackaging function? Any help is greatly appreciated! Thanks!
[Magisk] lividhen99:
Try uninstalling magisk manager then reinstall and repackage it again.
[Magisk] zgfg:
Don't worry about root, SafetyNet, modules and so - Magisk is ok, problem is only in Manager

You can always uninstall that renamed MagMan or how you named (and Magisk Manager if you have both) and then install Magisk Manager again - everything will be ok

I don't know how renamng/repackaging of Manager works now for the Stable channel with new Manager (314) and old Magisk (v20.4). Also don't know about your OnePlus

But the problem is known (and I had/saw the same but on Canary and Xiaomi): Check in Settings (probably Developer options) if you have an option like Install via USB, enable and renaming/repackaging of Magisk Manager shall work. Maybe, it will similarly work on your OnePlus

Btw, you have strange comments in your post ("not sure if the package rename worked but Magisk Manager does not recognize it")

- please distinguish Magisk Manager (renamed or not) and Magisk itself. First is only the managment application, second is the root service/framework (core). Magisk will continue to work even if you uninstall Manager (only, you won't be able to grant new root rights because Manager app is the one who has to display the popup to ask you)

Hence, you can try:

- enable that Install via USB (if you have something like that on OnePlus), open the renamed MagMan and maybe it will continue/finish renaming/repackaging

- delete the renamed MagMan and try to rename/repackage again, once the Instal via USB is enabled

- delete renamed MagMan (maybe also Magisk Manager if you have both and install Magisk Manager again) and continue using Magisk Manager without trying to hide/rename/repackage the Manager