yashsingh1/xdaforums huggingface dataset:
[Magisk] Yoshi948:
I'm completely new to using Magisk and I've recently installed it through TWRP on a Moto X Pure on stock Nougat 7.0. I heard there is supposed to be a MagiskHide setting on the left banner, but I don't see it at all. I also get the "ctsProfile: false" when doing the Safety Net Check. Is there something I did wrong and is this solvable?
[Magisk] zputnyq:
From v20.4 magisk hide must be activated first. Choose settings on that left banner, you will see option to activate it.
[Magisk] Philnicolls89:
Also read the last few pages of this thread, CTS profile is failing on many different devices for the last few days. Most likely Google doing something with there servers again and nothing we can do about it.
[Magisk] Yoshi948:
That's quite unfortunate. But is there a reason for Magisk Hide not appearing?
[Magisk] maruf8:
is there any magisk module for modifying parameters of system ui?
[Magisk] gringo80:
You probably deleted /adb folder in TWRP maybe by formatting /data after installing Magisk. Try to reinstall from the Magisk app !
[Magisk] totalz:
Android 10 - dynamic partition issue!!?

Whenever I install/uninstall magisk modules, after reboot, I got this bootloop...

Enter twrp recovery, i got this "failed to mount /system_root", so basically I cannot do anything except reflash the rom (2.7G). From github discussions, this is mainly due to the dynamic partitioning in android 10. After reflash the rom then magisk, I can use those modules without problem.

I'm just wondering if I can simplified the rom, so even if I have to reflash the rom to remedy, I can at least do it faster. After checking the scripts in the rom, I think this dynamic partition setting is rom specific, so there may be some way to load this into magisk/twrp and "fix" the issue once and for all!?

View attachment dynamicPartitionInfo.zip

* Magisk-v20.4

* TWRP-3.4.1B-0317
[Magisk] zgfg:
You didn't specify your device, firmware.

You also need to check on your device forum for the cookbook about installing Magisk there

Android 10 (MIUI 11, Xiaomi), I never had a problem at all with Magisk.

There are users here (this is general Magisk thread, not specific to some Pixel or something) with various phones who also happily use Magisk on Android 10, but procedure for installing Magisk can differ
[Magisk] AlexGtll:
Fingerprint is integrated in the device or in the room flashed? I'm curious about it ?, if someone knows???
[Magisk] AlexGtll:
Finally I got safety net again, ?, simple, just installing Edxposed and flashing hidden core module
[Magisk] cojocar.andrei:
I heard that hidden core just spoofs safety net just for magisk, not the other apps, just to feel good, so it's doing practically nothing, sorry ...
[Magisk] gringo80:
placebo effect !!! try using GPay now ... ?
[Magisk] AlexGtll:
Is true hahaha ??? **** module , do u have another solution?
[Magisk] AlexGtll:
I don't know anymore what's happening, I can use g pay ?*♂️????need help
[Magisk] gringo80:
I already said " just wait " ... there is no solution !
[Magisk] henningsieh:
Which app for checking the status is that? Thx
[Magisk] AlexGtll:
This one
[Magisk] henningsieh:
Many thanks. What's the original source?
[Magisk] AlexGtll:
Was sended to me by another developer in chat
[Magisk] AlexGtll:
He should know about it
[Magisk] henningsieh:
Rule 1: DO NEVER RUN ANY EXECUTABLE YOU DON'T KNOW.

Well... ?
[Magisk] AlexGtll:
I know but wasn't a new member, got many post so I just trusted ??
[Magisk] zgfg:
SafetyNet check, rolll back few posts and you'll find it. Actually, I posted it here many times

There is a newer version on Playstore but it is no more free so I prefer to use their older version ? - it doesn't matter, it asks your Google Play Services framework on the phone to verify SafetyNet

You can find that old version also on ApkMirror (need to dig under the old ones)

Of course, I disable automatic update in Google Playstorre for that app ?
[Magisk] henningsieh:
...love this community. Thanks a lot! ?????
[Magisk] Displax:
Actually, Google recently enabled it (look like just for little testing for now).

OK, here we go again!

Google announced new iteration (after "March boom" testing) of hardware attestation with new API back in 5 May here: https://groups.google.com/d/msg/safetynet-api-clients/lpDXBNeV7Fg/Ov2H6ZvhBQAJ

And now, they start turning it on.

How to check it?

1. Install normal SafetyNet testing app. In this case best: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

2. Start LogCat recording (as you prefer). You can use this app or ADB: https://play.google.com/store/apps/details?id=com.dp.logcatapp

3. Open SafetyNet testing app and run attest check.

4. Look into LogCat and find SafetyNet response in RAW format. You can find it by mask "evaluationtype". If hardware attestation enabled - the value be "BASIC,HARDWARE_BACKED", if not - just "BASIC".

Check via ADB (no ROOT needed)

https://xdaforums.com/showthread.php?p=82964687#post82964687
[Magisk] @kitokit:
Have you find a way to make it work? I'm having problem with this app too
[Magisk] akhil093:
checked twice. Both time I got Basic Hardware Backed. That means Google enabled hardware attestation. Android 10 (Samsung M30) Security patch- 1 May 2020. Maybe someday topjohn will think about a workaround for this as he always overcome previous challenges & obstacles made by Google safteynet.
[Magisk] Damianek420:
I know Google killed the magisk hide for good, but I'm going through a verification. Only with the xposed module does it get false. Can I fix this somehow?
[Magisk] xa0082249956:
Same issue here.

I have uploaded the original boot.img file to https://mega.nz/file/9X53gBaD#StIeiFJ3g2_I2ooFEXtrC3A1xGFMqA79Q5kn_Zb5y8A.
[Magisk] Yoshi948:
After doing a direct install and rebooting from the app, it still does not appear.
[Magisk] amk316:
no

stc pay 1.4.12 don't catch canary

but 1.4.13 do catch the latest canary 0850bca9

so i use canary and stop updating stc pay to 1.4.12 until some one solve this:(
[Magisk] zgfg:
Screenshots from two phones:

1) Rooted Xiaomi Mi 9T (stock Android 10) with CTS profile failing, using just BASIC,HARDWARE_BACKED evaluation type

2) Not rooted (bootloader originally locked) Huawei Mate 9 (stock Android 9) with CTS profile passing and using just BASIC evaluationtype

Btw, interestingly, on that Mate 9 (EMUI 9.1) I was able to grant android.permission.READ_LOGS to the Logcat4u app, thus enabling logcat without rooting the phone (tried on few other not-rooted phones, it didn't work)
[Magisk] JudgeDread11:
Read the post above the one you replied.
[Magisk] zgfg:
Can you please run on your phone getprop commands from Terminal Emulator and provide me results

getprop ro.build.fingerprint
Xiaomi/davinci_eea/davinci:10/QKQ1.190825.002/V11.0.5.0.QFJEUXM:user/release-keys

getprop ro.build.version.security_patch
2020-??-??

Suggested answers are included?

You can send me by PM - Thanks

Edit: No need, tested with QFJEUXM v11.0.1 (predefined in MHPC), didn't help - still CTS Profile failing
[Magisk] Yoshi948:
Just to update here, I've restored the stock ROM, it appears that it's an issue of having an unlocked bootloader, as I dont have root as of right now.
[Magisk] Philnicolls89:
Yes google is most likely testing their hardware key attestation again, which you will automatically fail with an unlocked bootloader.

For now the play store is still certified so I can live with cts profile not passing safety net as all my apps still work.

I think it will be a while before google fully roll out the attestation as it will effectively kill all custom roms (and google have said many times that they support custom roms so long as they aren't shipped with GAPS).

When the do fully roll out key attestation hopefully there will be a way to pass with an unlocked bootloader. But for now its simply wait and see.
[Magisk] zgfg:
Is there anybody with stock (rooted) Android 10 and unlocked Bootloader who can pass SafetyNet CTS Profile?

If so, on which device?

Tried various Android 10 fingerprints by MHPC, always failing
[Magisk] stathis95194:
Yeap...my Xiaomi Mi 8 Pro with magisk canary 20416 pass safety net and gpay still works

Edit: you added stock later :) I'm not stock, I'm on xiaomi.eu rom
[Magisk] zgfg:
Ok, please what are yours (run in Terminal emulator):

getprop ro.build.fingerprint

getprop ro.build.version.security_patch
[Magisk] stathis95194:
:/ $ su

:/ # getprop ro.build.fingerprint

Xiaomi/dipper/dipper:8.1.0/OPM1.171019.011/V9.5.9.0.OEAMIFA:user/release-keys

:/ # getprop ro.build.version.security_patch

2020-06-01

:/ #
[Magisk] guest4711:
This is a leftover from MagiskHidePropsConfig. You may delete it.

But your problem may be caused by another module which installs something into system startup folders, e.g. into /data/adb/ post-fs-data.d and service.d

Rename these folders in TWRP.
[Magisk] zgfg:
This looks like fingerprint for Android 8.1.0, not for Android 10
[Magisk] stathis95194:
And it's for dipper not equuleus but why do I care? I pass SN and GPay works
[Magisk] zgfg:
I wanted to see if fingerprint for Android 10 with unlocked Bootloader can pass - maybe Google forces BASIC,HARDWARE_BACKED for all Android 10 phones
[Magisk] zgfg:
Btw, I put now the fingerprint as yours (see the screenshot) and CTS Profile is still failing on my Xiaomi Mi 9T hardware
[Magisk] alex.do:
afaik changing fingerprints no longer helps once google already applies hardware backed attestation check on your devices. as OP mentioned multiple times its google server sided, theres nothing we can do abt it.

mine running stock rooted android 10 got cts failing few days ago, downgrading / upgrading fw (fingerprint as well) doesnt help.
[Magisk] zgfg:
Unfortunately yes.

I have Huawei Mate 9 (not rooted, Bootloader locked) and ofc SafetyNet is passing, and it uses BASIC

Now I put its ro.build.fingerprint and ro.build.version.security_patch to my Xiaomi Mi 9T but CTS Profile is nevertheless failing and indeed it uses BASIC,HARDWARE_BACKED

Edit:

Btw, this is all in accordance to (scroll down to the Table 1):

https://developer.android.com/training/safetynet/attestation#use-response-server

- With unlocked Bootloader, CTS Profile should fail but not Basic Integrity

- With compromised integrity (like root) both CTS Profile and Basic Integrity should fail

Magisk still hides root and only CTS Profile is failing.

However, turn Magisk Hide off and both will fail

Apparently, custom ROMs are excluded from the ongoing Google's test (enforcing hardware backed CTS Profile attestation)
[Magisk] MoL_82:
"and google have said many times that they support custom roms so long as they aren't shipped with GAPS"

Does that mean that when you are on Lineage or anything, you will have full support? You can add GAPS later in the process, but will that end support from Google's side?
[Magisk] Philnicolls89:
Sorry for the confusion, my wording could have been better.

I just meant that google have said they will allow people to use custom roms and will not try to stop the use or development of them.

If google fully roll out hardware key attestation in its current form (which seems to make any device with an unlocked boot loader fail safety net) then they will effectively be killing the custom rom scene. Google seem to be ok with people installing GAPS on roms such as lineage so long as they don't actually come pre loaded.

So there is still hope that we will be able to find a way to pass safety net with unlocked bootloaders when google finally rolls this thing out!!
[Magisk] MoL_82:
Thank you. I am not a developer, but the first idea that comes to mind is to let the Config Props module add Lineage fingerprints.
[Magisk] @kitokit:
What version of magisk canary you use?

Do you have a link to stcpay 1.4.12?

Any other specific steps that I should be aware of to make this stc app work?
[Magisk] pndwal:
Well, not sure Google view it quite like that; they see SafetyNet as a potential means to alert apps/app devs to modified environments that may violate their security model so they can choose to prevent their code from executing if security model is breached ('potential' because such devs are aware SafetyNet pass is unreliable / easily spoofed at present).

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82211559 (More on the motives / rationale here.)

Thus, it seems they view SafetyNet pass as a trade-off for those running custom mods. They will continue to support custom ROMs/mods, but will give 3rd party developers the control to determine if their security-centric and other apps are allowed to run in these environments.

Right. Since Google hit Steve Kondik (Cyanogenmod) with a cease-and-desist order for including proprietary GApps with his ROM he thought and posted that CM was dead and almost ditched the project, but Google seemed to realise they were SHOOTING THEMSELVES IN THE FOOT and clarified that they would still allow GApps to be sideloaded by end custom ROM users (but not packaged with custom ROMs) in short order.

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

Well John Wu doesn't think so:

Could be well worth trying though. There's a $1M bounty!

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82204891 PW
[Magisk] dreamland2000:
I'm currently on magisk 20417 and I'm having trouble with modules not installing either through the app or in recovery, is antofagasta else having this issue?
[Magisk] Didgeridoohan:
SafetyNet's hardware backed key attestation has nothing to do with the device fingerprint.

As has already been stated many times, this method of detecting the unlocked bootloader is very likely impossible to circumvent.
[Magisk] Shtiff1:
LG-G820UM, 10,Verizon
[Magisk] martyfender:
Yes, I am having the same issue on my Onn 8 Android 9 tablet after updating to 20417. I replied on github under someone elses bug report and provided a magisk.log.
[Magisk] simonk206:
Hey [MENTION=4470081]topjohnwu[/MENTION]

Since latest Canary update 20417 I'm not able to see my installed modules in Manager 286, but the modules are working fine. I already tried magisk uninstaller and installed all modules again. But i got the same, modules are working but not shown in Manager 286. When i install old Manager 285, i see my installed modules, so i dont think its me.

Device: Samsung Note10+ N975F Android 10 latest official Firmware
[Magisk] wbedard:
Same here. Manager 286 logs show modules loading properly, just not listed in main GUI. Able to download and install modules from main GUI, they just don't show as installed.

Device: OnePlus 6T w/ current Android 10 firmware
[Magisk] Damianek420:
1)What are the advantages of bypassing SafetyNet except Google Pay, snapchat, magdonalds? Revplut also requires the correct SafetyNet?

2)Also i pass SafetyNet so that means this it not implemented yet correctly on my device? But if i run xposed module it fails. Can I get this avoid somehow? How its looks like :
[Magisk] Philnicolls89:
Thats basically it, some apps won't work or even let you download them from the play store if safety net doesn't pass.

This screenshot doesn't show safety net passing, you need to use magisk manager or even better a safety net checker from the playstore, as magisks results can be spoofed by modules.

Edxposed has had a problem with breaking safety net for months now. Nothing you can do except uninstall it.
[Magisk] professorbil:
Can't update magisk from 20.4

I haven't been able to upgrade to canary at all tryed 20415 20416 20417 but never works. I do direct install method and everything seems ok then reboot and after that I'm stuck on my boot logo till I force restart my phone. Then phone boots fine and I'm on 20.4

I'm on Android 9 btw
[Magisk] Wolfcity:
Try to patch the boot.img by Fastboot or TWRP. With some devices you've got more success that way.
[Magisk] HippoMan:
Maybe the time has come for us to start getting much more serious about microG. Lots of popular software won't work out of the box with microG, but perhaps enough developers could be persuaded to release microG-enabled versions of their apps, or for new microG-based apps to be written.

.​
[Magisk] JudgeDread11:
How has that anything to do with the safety net situation?

Or Magisk for that matter.
[Magisk] zgfg:
Indeed, Magisk Manager 286 showing no module installed

Also, per Changelog, Safe mode was removed (indeed, there is no more Safe/Core only mode option in Manager 286 Settings)?!

Hence keeping Magisk Canary 20417, but rolling back to Manager Canary 285

- Uninstalling Magisk Manager (286)

- Downloading and installing Magisk Manager 285:

https://github.com/topjohnwu/magisk_files/raw/fc1d06a02f7f5be7ac5f480c8b0ee41238a654bc/app-debug.apk
[Magisk] geokilla:
I haven't been able to update any of my apps for 2 weeks now via Google Play. At first I thought it was Magisk and my phone not passing SafetyNet. Tried removing Magisk and got the same results. Could my phone be blacklisted by Google? Had it for two years now.
[Magisk] dcarvil:
Did you clear cache for play services?
[Magisk] zgfg:
The following usually helps for Playstore issues:

- Airplane mode on

- Settings/Apps and wipe cache and data for Google Play Store, Google Play Services, Google Services Framework, Google Play Services for AR

- Reboot and Airplane off

If Playstore then shows no app installed:

-Install some application that you know is from Playstore, but install it from local apk file (e.g., download it from ApkMirror)

- Lave the phone some time ( it can take an hour or more for Playstore to sync) and check the Playstore again
[Magisk] geokilla:
I've tried doing that again, this time with Airplane mode on and wiping cache and dalvik cache. Then sideloaded Groupon. Still no go. It says "waiting for download" in Google Play. Going to see what happens an hour later but I don't think it's gonna work.

Edit: Well I got it working finally. It was one of the adblock sites I blocked...
[Magisk] martyfender:
This works until you try to hide magisk manager then it downloads 286:

Magisk Manager

Upgrade to full Magisk Manager to finish the setup.

Download and install?
[Magisk] HippoMan:
My assumption is that with microG and apps that are written to utilize it, nothing from Google will be in the picture, so SafetyNet will be a moot point.

Am I misunderstanding something?

.​
[Magisk] agungpraja:
Bug Module Not Show Magisk Manager (286)

Report :

After update magisk manager to new version (286) magisk module not show at all.
[Magisk] martyfender:
Yes, it is a bug (at least for some) in the latest version and has been reported in the issue area of github.
[Magisk] JudgeDread11:
Apps that won't work without safety net passing will for sure not work without Google services. So it wouldn't help anybody directly.

Custom ROMs and root is used by a minority of the Android users and within that minority it's only a minority that uses microG. Even if all root users would use microG it would be a number too low to have any influence on the companies making use of safety net. So indirect it wouldn't have the desired effect either.

In the end it will boil down to choose between using root and/or custom ROMs and not pass safety net or use pass safety and use stock.

Unless we can find ways to gain root without unlocking the device.
[Magisk] professorbil:
No luck same problem had to restore my boot back up -_-
[Magisk] zgfg:
Yeah because with Update channel to Canary it points to the latest Manager 286 - and for hiding Manager it will download that version

Before hiding, you should have changed the Update channel to specific version 285: https://raw.githubusercontent.com/t...2f7f5be7ac5f480c8b0ee41238a654bc/release.json

After hiding Manager, switch the Channel back to Canary (to be able to see future updates)

How to find a json for particular past version (since 285/20416 release and debug Canary are the same, pointing to debug) was discussed in posts #40180-#40182, everything was summarized in:

https://xdaforums.com/showpost.php?p=82758783&postcount=40181
[Magisk] alex.do:
If im not wrong years ago we were able to achieve root with locked BL on these or those devices. but as new security patches keep coming, its no longer easy to exploit. this makes rooting without unlocking BL impossible, sadly.
[Magisk] napster113:
I can't believe how easy it was to create my own debloat module, it even installs my custom bootanims.:D
[Magisk] Aakash Kaushal:
Please share that module....i want to debloat my s7 edge..as you know package disabler pro dont work in custom roms..please share the module:D
[Magisk] ken2802:
isntalled the update via app and it seems to have worked but now the manager force closes after a few seconds. [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Rhoban:
You can always make a nandroid backup. What's the big problem?

What modules are you talking about? If you want Xposed then you have to flash that one too, systemless.
[Magisk] Heyabhay1127:
Did not work for some reason

I did a full unroot with supersu and flashed it again and magisk still gives me the root not properly installed. Is there anything else I could do
[Magisk] käsebr0t:
It's the same for me. After installing Magisk-v7, SuperSu disappeared from the AppDrawer (root-access is working fine, though). As a workaround, I used the app "Activity Launcher" from the Play Store to create a custom shortcut, that launches SuperSu.
[Magisk] TheSaiyan:
My recovery (Philz Touch, latest version) is not generating any logs, there is no "clockwrokmod" folder and I can't find any log file, however I can transcript the text in the recovery, hope this helps.

--Installing: /storage/sdcard1/Magisk-v7.zip

Finding update package...

Opening update package...

Installing update...

**************************

Magisk v7 Boot Image Pa

**************************

- Mounting /system(ro), /cahce, /data

- Device platform: arm

! Unable to detect boot

E: Error in /storage/sdcard1/Magisk-v7.zip

(Status 1)

E: INstallation aborted.

Press any key to continue.
[Magisk] alroger:
Well, "! Unable to detect boot" is what matters. Do you have any info on your device and rom's threads? as in non-standard boot.img or it's location? And shoulnd't you be using TWRP? The reason your're not might be the answer to the first.
[Magisk] PliskinCat:
I currently have Magisk V7 installed along with the latest phhSuperuser. I am looking to use FlashFire to flash the latest factory image to my Nexus 6P (NBD90X) and the latest SuperSU.

Do I need to uninstall Magisk first (i.e by flashing the uninstall ZIP) or can I just run FlashFire which will inject SuperSU in anyway?

And will I need to remove the phhSuperuser in any way before installing SuperSU?
[Magisk] mathy007:
I was once in your shoe since the beginning of magisk but I get tired of asking but to my surprise v7 flash successfully without any problem but u have bootloop will provide some log or boot.emmc.win here to get help on that
[Magisk] edale1:
From the Magisk v7 thread's known not working devices:

What does this mean by "BUMP your boot image", and how do I do it?
[Magisk] TheSaiyan:
My device is a M4 SS4045, which is a very unknown phone, so there is very little support out there. The only thing I know is that it has a MTK 6582 chip. I'm using a ported CM 12.1 rom. I don't know where is the boot.img location. I cannot install TWRP, I always get bootloops.
[Magisk] alroger:
Looks like you need specific help for your device. Have you tried talking about it with the devs from your ported ROM or your recovery? Might not be in XDA at all.. some hardwares have better forums elsewhere.

Wish you luck!
[Magisk] TheSaiyan:
Yeah, I tried, but there has been no response. I'll try to port TWRP and see what happens, if i can't get it to work, I'll look forward for alternatives.

Thanks.

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

I thing it must be the recovery. I'll flash another to see what happens.
[Magisk] Nomelas:
it seems magisk no longer installs busybox? how do I get busybox now with this method?
[Magisk] Rhoban:
Busybox comes pre-installed with most custom ROMs. Otherwise downloaded the Busybox app or flash the zip through recovery.
[Magisk] WeirdSoup:
You can fine busybox in /data/busybox. I have no problem with busybox.