yashsingh1/xdaforums huggingface dataset:
[Magisk] bmwbasti:
Hi guys, just a quick question.

I updated from 20.4 to 21.4 yesterday (got no update message whatsoever) and I noticed, that the ctsprofile now gives a missmatch. It's a while ago that I was performing the test so I don't know if this would be related to the update or to Google's changes.

Is there a way to get ctsprofile to pass again?

I'm running a Mi 9t Pro with newest 12.0.4 global Rom.
[Magisk] zgfg:
Yes, things have changed on G side and there is now a new module SafetyNet-fix to handle the CTS. Link was posted also here but you can search for the XDA thread for that module- there, you will find download link from its Github
[Magisk] nowster:
Following up the previous person's reply:

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Magisk] pndwal:
General:

Release notes:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84359513

👍 PW
[Magisk] dipseeet:
:)

i tried

/system/bin/sh (works)

/bin/sh (works)

/data/data/com.termux/usr/bin/sh (works)

:)

I think i found a solution to have

Magisk 21.4 with Manager 8.0.7

installed and everthing working.

Iam so happy :)

I'll explain it in my next post ^^
[Magisk] dipseeet:
haha (:

Iam so sorry ...

I think my main problem was not Termux itself.

It was working well but i myself did a mistake.

I think my main problem was (not anymore now :)) that when i fresh installed Magisk it was working ... i can grant root apps access and i get those toasts everytime when a root app is working.

But after reboot it didn't worked anymore.

No toasts anymore and to add another root app to grant access was not possible too anymore.

Nothing could tell me what is causing this issue.

I thought it's not happening in Magisk 21.3 but it did.

So for now i know

*what* cause my Magisk (no matter what version is installed) not to get work anymore correct but

*why* i don't know.

Next post i'll explain *what* :)
[Magisk] Ghisy:
Anyone please?
[Magisk] dipseeet:
are u trying to patch in Magisk Manager

or in TWRP?
[Magisk] Ghisy:
I'm just trying to update Magisk through the manager, using "direct install". It usually works, not this time :/
[Magisk] CSX321:
FWIW, ElementalX and stable channel Magisk is still good on my Pixel 3 with A11 January patch. Systemless hosts and everything else working, passing, and certified. It's been 4 days now, so I think this is a working combo.
[Magisk] dipseeet:
*what*

2 or 3 weeks ago i wrote another script to change 1-2 values in my build.prop.

I tried it in the Kernel Manager app to change it and to start at boot

but after reboot no change.

I copied my build.prop and edited it with Terminal

but after reboot no change.

That's why i tried out my script to start at boot

and after reboot it worked.

But this little script was the reason why i got problems with Magisk.

I start this script and my Magisk stops with sending me Toasts and popups to grant a new root app.

I got so p!ssedoff the last 2 weeks that i almost lost hope ... really ... sometimes it worked and then suddenly it didn't.

I could not realize (until today) that Magisk always stoped working until i execute this little script.

My buildprop.sh:

#!/system/bin/sh

su -c setprop dalvik.vm.heapgrowthlimit 256

prop0=$(getprop dalvik.vm.heapgrowthlimit)

echo "dalvik.vm.heapgrowthlimit: $prop0"

wtf why?? :(

Now i have

Magisk 21.4

Mananger 8.0.7

and i never run this script anymore

and it works!! :)
[Magisk] dipseeet:
:(

does a new install of Magisk work?
[Magisk] zgfg:
Yes - did you read several posts today about successful installation of 21405
[Magisk] Ventus32X:
good I have used the magisk application having it in 21.4 there was a new update, I proceeded to update it In the following images we can see that the update was completed correctly but the problem appears when reading "not installed" I wait for your answer patiently PS: I am Spanish and viper4android keeps asking me to install its module when it is already installed
[Magisk] stollysoft:
Hi all, I have a problem with fingerprint sensor authentication.

I have a rooted Samsung Galaxy Note 9.

Before all ok, then I updated Masisk and got the safetynet error. I installed the props component (indicating the right fingerprint file for my phone) and the safetynet fix too (as above) and now it passes the test in basic authentication method.

Problem is that from this moment, my in settings registered fingerprint authentication does not work, in detail:

- apps neglect registered fingerprint from settings

- apps state failure in using fingerprint authentication and ask directly for password

- in apps, trying to activate fingerprint authentication method states fail

- in settings, ticking on the option "unlock by fingerprint" the phone freeze and reboot

I tried to remove fingerprint and to register it again in the settings (there all work fine: fingerprint is saved after recognition and verify procedure) but nothing changed with apps. I wiped the cache, nothing changed with apps. I am out of option. Before I get the fingerprint authentication request in apps and worked flawless, now the apps appears to not request (ignore) or state a failure in using this method of authentication...

Somehow I believe that the new magisk+fix setting do spoil to the phone a spoofed KNOX status (due to root) on which the fingerprint authentication relies, and thus the phone recognizes this as "untrustable authentication error" but perhaps I am wrong here. Or in the system there remain some old certificate that went void after magisk and props installation due to the new fingerprint file of the Note9 and the new/the old signatures do not correspond. I know this because on my online bank account I had to register my phone again, as it was another device than before.

Thank you for much for advise and help in advance!!
[Magisk] J.Michael:
Do you have any modules other than ths Safetynet-Fix?

Confirm that if you disable all modules, the fingerprint authentication works.

If it does, enable only Safetynet-fix, and try again.
[Magisk] Didgeridoohan:
@stollysoft The Universal SafetyNet Fix is known to break the fingerprint authentication on Samsung devices (and some others). Check the module's thread and GitHub for current workarounds (there are user modified versions of the fix available that works properly on Samsung devices).
[Magisk] pndwal:
...Also, do you mean MagiskHide Props Config module here? If so, altering fingerprint prop may be causing your problem (although Universal SafetyNet Fix is still the likely culprit as mentioned above).

MHPC is only needed to pass ctsProfile if using uncertified (Chinese etc) stock, or Custom ROMs. Generally for Samsung on stock, you shouldn't need / use this module at all, but other fix (USNF for Hardware Key Attestation) is likely needed. PW
[Magisk] pndwal:
Like your Lollipops, Marshmallows, Nougat and Oreos?

We're impressed John! PW
[Magisk] Ghisy:
Follow-up: I ended up flashing the Magisk-patched boot image and all is well! Just in case someone is stuck like me on 20.4 and can't update using Magisk Manager. Shoutout to @i5lee8bit!
[Magisk] stollysoft:
Hi all again.

Forgot to say that my Note 9 is Chinese, therefore the props is needed. As well as safetynet fix.

I followed advice from github, they suggest to change the hex string timestamp in the system/bin/keystore file, but I do not find in my file the same hex combinations reported there.

I wish not to surrender, but it appears to me that as stated by you all both filestamp from props and the safetynet fix bother the fingerprint authentication, and moreover, not being able do safely hex-edit my keystore file, I have to stop before disaster (bootloop, brick) happen.

I will maintain securenet verify but have to surrender fingerprint authentication :( a pitty that fingerprint authentication cannot be replaced by my working iris recognition in those 3rd party apps...

Thank you very much!
[Magisk] prot-:
I have been getting the same system freeze that I'd expect with systemless hosts enabled on my Google pixel 3 xl. However I don't have systemless hosts enabled. It's only happened since latest magisk 21405 I think.

Hoping updating the universal safety net to from 1.0 to 1.1.1 just now has fixed it . But that's not expected right?
[Magisk] CSX321:
Make sure you actually removed the systemless hosts module, not just disabled it. On my Pixel 3 I kept having the freezing problem until I removed it (and rebooted again, of course). As I noted in an earlier post, I'm now using the ElementalX kernel, and it's been rock solid for almost a week now with systemless hosts reenabled and everything working, passing, and certified.
[Magisk] nowster:
Where did you get the current release of ElementalX?
[Magisk] CSX321:
I just let EX Kernel Manager retrieve and install it. Version 3.12, which is newer than what was linked on the EX site itself.
[Magisk] nowster:
Ah, I hoped I wouldn't need the app.
[Magisk] Wolfcity:
I'm no pixel user but a Google search for "elementalX pixel 3xl" brings up a lot of results:

ElementalX Pixel 3XL

Maybe not the latest kernel but a working one?
[Magisk] Gregbmil1:
I have a question. I fail SafetyNet Check but why should I care? Lol, I only say this because there is nothing i can't do on my newly rooted Note 10. Well, my Huntington Bank app. I can use it just fine except the Zelle section of it.
[Magisk] prot-:
Google pay
[Magisk] daffy1234:
I'm having an issue trying to get Magisk to work on my Likebook Mars (T80D). When I try flashing the patched boot.img, it just says No Command with the broken android logo. The tablet is using android 8.1 and is based on a rockchip RK3368. Here's its device tree if that helps. Any ideas?
[Magisk] stollysoft:
Hi all again,

struggeling again with my Note9, I have checked some comments.

indeed fingerprints in the props for Note9 are Android10, but I have a Android9 OS installed.

Is this a problem? In case, where can I find a proper fingerprint for older OS versions?

Thank you
[Magisk] Didgeridoohan:
As long as you can pass CTS it shouldn't matter if you use a fingerprint that doesn't match the Android version you're using. If you really want to get an Android 9 print I've described how to find prints in the MagiskHide Props Config docs:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

I don't think I have every seen anyone reporting about having fingerprint authentication issues after changing the device fingerprint (but my memory is notoriously fickle), but I've seen lots of report about it as a result of using the new SafetyNet Fix... Work is being done on mitigating that though (check the module thread and Github repo for progress).
[Magisk] Didgeridoohan:
That's very likely the f2fs bug and it's not directly related to systemless hosts and can be triggered by other things as well... As mentioned already, a kernel that has the bug fixed is necessary. Details here:

https://github.com/topjohnwu/Magisk/issues/3171
[Magisk] kiwigi:
I made a fool of myself the other day on my sm-g930f (Galaxy S7) and tried to install Magisk through ADB, unfortunately unsuccessful.

Now I like to ask if anyone of you has installed the TWRP app, then installed TWRP recovery from the app and thereafter flashed Magisk through the TTWRP recovery?

Is that an option? Thanks
[Magisk] zgfg:
Methods to install Magisk are described in the Magisk Docs / Installation (available from Github) but also discussed here - please follow them

For the newest Canary 21405 it's little different (regarding to flashing through TWRP), but it is also described in its Changelog

Sorry I don't recall I ever heard of installing through ADB (IMO, it could only work, if, for Magisk Manager), and have no idea of potential consequences if somebody experimented on his own that way

IMO, TWRP app can properly work only if root (therefore Magisk) is already installed.

Anyway, this is thread about Magisk, you should better ask/search in your device forum about specifics for TWRP
[Magisk] kiwigi:
Thanks@zgfg
[Magisk] loopypalm:
in Magisk v21.4 and Magisk v21.3 , edxposed apps don't work
[Magisk] Uluru25:
... with which versions (riru, riru core, edxposed)?
[Magisk] Sergei-Alekseev:
Hello!

Is it possible to install magisk on the device with dm verity?

I can execute commands as root using ./su -c but i cant remount partitions r/w.

Device is LG Q7.
[Magisk] zgfg:
If SAR is read only, you could not get write permission

You could check /vendor/etc/fstab.* how your /system or / (root) are defined - ro means read only
[Magisk] MoL_82:
I had the same issue, EdExposed modules would not load. Deleted and reinstalled Riru and EdExposed including manager. That did the trick.
[Magisk] nowster:
Bother bother bother!

I'm trying to build the stock Pixel3a kernel using the instructions on https://source.android.com/setup/build/building-kernels

But none of the /vendor modules are loading, so no touch screen or WiFi support. This is a preliminary step to building with the f2fs lockup patch applied.
[Magisk] zgfg:
Just updated Canary to today's 21406 and patching the boot.img, everything ok
[Magisk] nowster:
With the new Manager-only versions, it seems that after an upgrade, MagiskHide is silently off (but shows as on) for the first boot (which means a basicIntegrity fail). Then on a second boot it correctly shows as off, and I can then toggle it on and everything's OK again.
[Magisk] pndwal:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84366073

Changelog below. PW
[Magisk] pndwal:
Latest Canary Changelog incl. Release Notes:

Magisk (6fb20b3e) (21406)

NB: RESTORE THE HIDDEN MAGISK APP BEFORE UPGRADING IF RUNNING LOWER THAN ANDROID 9.0

[App] Support hiding the Magisk app with advanced technique (stub APK loading) on Android 5.0+ (it used to be 9.0+)

[App] Disallow re-packaging the Magisk app on devices lower than Android 5.0

[App] Also download to external storage when upgrading the app

[MagiskSU] Fix root on Android 7.1 and lower

How to Use the APK for Recoveries

In general, it is recommended to install and uninstall Magisk through the Magisk app. However, if you insist to use custom recoveries, rename the Magisk APK's .apk file extension to .zip. TWRP should then be able to directly flash the zip file. If you have trouble renaming the file extension on PC, rename the file with TWRP's built-in file manager. To uninstall in recovery, rename the zip file to uninstall.zip before flashing it.

Diff from v21.4

[General] Magisk and Magisk Manager is now merged!

[App] Rename the app "Magisk Manager" to "Magisk"

[App] Support hiding the Magisk app with advanced technique (stub APK loading) on Android 5.0+ (it used to be 9.0+)

[App] Disallow re-packaging the Magisk app on devices lower than Android 5.0

[MagiskHide] Fix a bug when stopping MagiskHide does not take effect

PW
[Magisk] pndwal:
Not for me! (Xiaomi Redmi Note 8T, Stock.)

Used direct Install, then checked SafetyNet status immediately after first reboot: Full Pass, all settings preserved and active.

I'm guessing second reboot will be needed for devices invoking additional setup steps (Samsung), and possibly others. PW
[Magisk] pricechristian68:
Apologies for being kinda new to reaching out for help. I have been playing around with properties and command lines <termux> for a little while and can navigate the root files pretty well. For the last few months I have been using a Verizon Note 20 rooted with Magisk, and at first, everything worked just fine and I noticed no issues. However I haven't been able to get twrp AND Magisk to coincide. I can either have root with Magisk, or I can have twrp recovery and stock rom. I chose to go with Magisk and for about a month and a half now I have been experiencing small tweaks im not familiar with, properties I didn't write, img files inside firmware <such as a super.img and dqmdbq.img> , I get an error in recovery mode when clearing cache that says: ([E]:no_PDP scenario [lstat /c____/b____] no file or directory exists) or something to that effect. I'll catch an overlay at certain times that cause app icons to appear "laggy" like they have a tracer effect when swiping. I'm not 100% versed in the stock note 20 root files and permissions and properties to be able to point out what doesn't belong. My main question is for anyone that might be able to have a look at my props and whatever else I can provide and help find out if this is normal and possibly caused these issues on my own or if I didn't guard myself well enough and got hacked. I would post some screen shots but don't have a clue where to start and what's not relevant. Thanks in advance.
[Magisk] macic:
Hi,

i m totally noob with this. So i need help. I have this andorid box.

I have problem with local aplication they add some protection and becouse of that my new device cannot run some programs i get this message:

So i explore and find that i can instal magisk and hide root from that application.

After install app i dont know what to do i cannot find where i can hide app i dont have that option. Also i download magisk hide props config and nothing. You can see on pictures all:

Please help me :(
[Magisk] dcarvil:
You are seeing only the top half of the Magisk screen. The tool bar that gives you access to the Magisk Hide settings is at the bottom of the screen. You will need to scroll down on the main Magisk Manager screen and select the shield icon on the floating tool bar. On my Amazon FireStick, scrolling down requires a mouse. You may also need a mouse, or an app that provides mouse functionality.

Edit: You might have better luck with Magisk 20.4 and Magisk Manager 7.5.1. The hamburger icon that gives access to the Magisk Hide settings is at the top of the screen in that version.
[Magisk] zgfg:
Till 2018, Huawei phones used to be very popular for rooting. Huawei had their own portal for unlocking Bootloaders, process was free and instantinous.

Then they closed their portal and soon therafter terribly hardened their bootloaders - for all new models coming and even by OTA for previous models that were still under support

Over time, certain Telegram and similar (relatively obscure) services (here and there, up and down) provided (pretty expensive) bootloader unlocking for most of the new Huawei models

Now, since two weeks ago, a well known player for unlocking modems, bootloaders, etc, expanded their tool and they support again Huawei bootloaders (for the new phones and new EMUI firmwares):

Unlock modems, routers and phones with DC-unlocker software

DC-unlocker is universal, fast and easy to use unlocking tool. Supports Huawei, ZTE, Sierra Wireless and other modems, routers and phones.

www.dc-unlocker.com

Supported Huawei models & features

Credits amount needed for operation with basic user account

Credits for users who don't have a dongle needed for one operation

www.dc-unlocker.com

It's still pricey (19 Eu) and mostly requires to open the phone to reach Test points, but better than how it used to be the last two years

However, taking into account the other issues with Huawei phones (US ban), not sure could it help to popularize the rooting of Huawei phones again
[Magisk] macic:
Thanks man i found it. I hide it but i have same message again -.-

Maybe some solution?
[Magisk] dcarvil:
Did you clear cache on the app you are trying to run? @Didgeridoohan has a list of things to try at:

Hiding root and passing Safety Net:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com
[Magisk] zgfg:
Just having MHPC installed does nothing.

You must configure the props you want to change (by a terminal app) - search for the XDA Magisk Hide Props Config thread, there in the OP post #1 you will find instructions how to use it
[Magisk] madaopul:
I believe I messed something up. Magisk was working just fine until I recently updated to the newest version which changed magisk manager to simply "magisk". After the update when I try to open magisk the grey loading bar comes up in the middle of the screen with the loading circle on the left side and stays there for a few seconds before going away. When it goes away nothing else will happen. Before updating I forgot to unhide the manager and I am wondering if that had something to do with it? It appears as though I am still rooted but I can't open the app. Any help on which direction to go or what I need to do would be greatly apprectiated. Thanks.
[Magisk] theelderstatesman:
Magisk Canary (b1dbbdef) (21404) and later versions: I want to have the download as a zip function back ... I know, I can rename the apk, but that's not the same ...
[Magisk] FredjePretje:
Hi all,

About a year ago I flashed my Galaxy Tab 3 (P5210) to Lineage. A couple of weeks ago my daughter wanted to play Pokémon Go on this Tab, but after all Nintendo games can't be played on rooted devices.

Yesterday I flashed the tab back to stock ROM but unfortunately I still can't download the game in Playstore. After all I flashed the tab with Magisk 21.4, I thought everything went well because rootchecker says OK and SafetyNet passes. I wanted to hide by using Magisk Hide, but after enabling it, it disabled by itself. How come?

Does this sound familiar to someone? Can't figure out what's wrong, please help me out.

Thanks!
[Magisk] Homeboy76:
Why isn't it the same ?

The latest is Magisk 21406.
[Magisk] theelderstatesman:
It's not the same, more work, less comfortable. I'm using 21406. Within the app, there's no more download as a zip function and that's a regression ...
[Magisk] Homeboy76:
The changes the topjohnwu made to it removes the necessity of having a zip file. If you want a zip file copy the apk and rename it zip. Then you will have a apk and a zip. :)
[Magisk] theelderstatesman:
Thanks, I know that. It's a regression. One day, he'll put it back, you'll see ...
[Magisk] zgfg:
While updating, you needed to read the Changelog - it required to unhide the old Magisk Manager before proceeding with the update

Go to Settings, Apps and try to find your old hidden/renamed Magisk Manager and uninstall that app. Probably you should also uninstall the new Magisk app. Then install the new Magisk app again, hoping to fix the problem

If not, you could try further by deleting /data/adb/magisk.db
[Magisk] madaopul:
I know I should have read the changelog and it is honestly this was the first time I did not. When you say install the new Magisk app, you are speaking of Magisk Manager correct?
[Magisk] Gasperino:
Hi I wanted to report that my gear s3 46 mm does not pair with my samsung ultra sm-g988b since two three magisk updates I have tried everything nothing to do. By removing Magisk it works regularly. Are there any solutions? Thank you
[Magisk] zgfg:
Now the app is renamed to Magisk, it is no more Magisk Manager (41406)
[Magisk] Homeboy76:
:oops:

I don't think so.
[Magisk] macic:
Try same not work :(
[Magisk] Gasperino:
attached my version of magisk. If not ok I can just replace magisk manager or rerun full install Thank you
[Magisk] daffy1234:
Still having trouble with magisk on my likebook mars T80D. It doesn't boot after flashing the patched boot.img to the boot partition. Any ideas or things to try?
[Magisk] Gasperino:
good morning everyone, kindly where can I download Magisk Manager (41406) thanks
[Magisk] Didgeridoohan:
As always, on GitHub:

https://github.com/topjohnwu/Magisk
[Magisk] theelderstatesman:
Maybe, you're right ... Time will tell ...
[Magisk] jaum20:
Tried to install (patching images method) and got stuck on boot screen. My device is a Moto e5 pettyl. I had not errors through the instalation. A stange thing that happened was the name of the patched images was magisk_patched_VuZIP.img instead of magisk_patched.img

the command and result:

fastboot flash boot magisk_patched_VuZIP.img

target reported max download size of 245366784 bytes

sending 'boot' (10507 KB)...

OKAY [ 0.351s]

writing 'boot'...

(bootloader) Image signed with key

(bootloader) XXXX-XXXXXXX-XXXXXX-XXXXXXX-XXXXXXXXX

OKAY [ 1.074s]

finished. total time: 1.455s
[Magisk] truelies1:
How to unhide the magisk? No unhide inside the setting icon. This is so confused.