yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
PSA - General announcement

Ok everyone. I've been letting the discussions go on the past couple of days, but now it's time to move on.

This thread is about the MagiskHide Props Config module, so from now on I want to keep the OT out of here. We know now that Google is tightening down SafetyNet and the CTS profile check. They're checking for the unlocked bootloader, which Magisk no longer can hide.

Older devices and devices without a proper implementation of keymaster (OnePlus, as an example) will still be able to pass CTS it seems, but it's just a matter of time before Google starts implementing tighter restrictions.

For all your information needs about this, take a look at the following links:

https://twitter.com/topjohnwu/status/1237656703929180160

https://twitter.com/topjohnwu/status/1237830555523149824

https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/

I'm sure some of you will be wondering if I will continue working on it, and the answer to that is yes. There's more useful features than just passing CTS (and as mentioned above there still will be devices that can). I likely won't be updating the fingerprints list much anymore though...

This thread will now go back to it's original contents of discussing the MagiskHide Props Config module. Please keep any further discussions of CTS workarounds in their own threads or the General Magisk discussion thread.
[Magisk] phelite2015:
lol that solution by flashing persist.img from stock rom claimed by poco tele channel is from xiaomi.eu devs lol
[Magisk] Nothex:
Thank you!!!
[Magisk] njtony:
Thank you for your work and hope to continue to update. Now cts passed, Google crazy :angel::angel::angel:
[Magisk] alex.do:
Second!!!

I just went sadly press the button expecting to see a red and a green. But all are insanely green!

Who else?
[Magisk] CSX321:
Same here!
[Magisk] pndwal:
A number of us in Magisk General Support / Discussion thread:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/ PW
[Magisk] Didgeridoohan:
And since this new development doesn't have anything to do with this module, please keep that discussion in the Magisk general support thread. A heads-up that suddenly CTS seems to be passing again is fine; a bunch of "+1" is not.

Just a friendly reminder (and a wish for keeping the thread somewhat free of clutter from now on). :good:
[Magisk] fgprodigal:
hmmm, my phone pass ctsprofile automatically too
[Magisk] phelite2015:
i also try to check mine at this moment

and YES it now PASS cts profile

and Phone is Now certified in Playstore

does google update there server?
[Magisk] Didgeridoohan:
[MENTION=10175111]fgprodigal[/MENTION] [MENTION=5823295]biikman[/MENTION] [MENTION=10177293]phelite2015[/MENTION]

Come on guys... It's not even an hour since I asked to please keep the "it's passing for me too" posts out of this thread.
[Magisk] biikman:
Then feel free to delete, apologies.
[Magisk] matrixios01:
How?

Στάλθηκε από το Pixel 2 XL μου χρησιμοποιώντας Tapatalk
[Magisk] matrixios01:
And meView attachment 4970703

Στάλθηκε από το Pixel 2 XL μου χρησιμοποιώντας Tapatalk
[Magisk] OhioYJ:
I'm trying to use the printslist so I can change my tablets over to match what they actually are. However I must not have something right, as the module seems to act like there is no list present. It's in the root directory of internal storage. Do I have something not formatted correctly? I tried with and without the "device name" at the beginning. The file was created in Linux, so it should have unix line endings.

https://www.cdmfabrication.com/logcats/printslist
[Magisk] wangdaning:
This is too far out of hand. Please close this thread and clean it. Some of us actually use the module.
[Magisk] Didgeridoohan:
I intentionally let the OT run the for a while (CTS passing is a large part of what this module is about, after all), but put a stop to it yesterday. Since then things have calmed down.

Most of the posts from the past week has been pretty useful and informing so no need for cleaning (IMHYCO).

I'm currently testing some new prints and since Google only seem to have flexed their muscles I won't be abandoning that part of the module for now.

Back to normal.
[Magisk] Didgeridoohan:
The syntax is not quite right. This is what you would want if you'd want the full benefit of the module features:

Samsung Tab S2 SM-T813 (7.0):samsung:SM-T813=samsung/gts210vewifixx/gts210vewifi:7.0/NRD90M/T813XXS2BSJ3:user/release-keys__2019-08-01
Samsung Tab S5e SM-T720 (9):samsung:SM-T720=samsung/gts4lvwifixx/gts4lvwifi:9/PPR1.180610.011/T720XXS1ASL3:user/release-keys__2020-01-01

I'm currently testing some prints (including those) and should be able to push a new list version later today (CET).
[Magisk] OhioYJ:
Greatly appreciate the response. I tried that exactly although it still seems to be ignoring it evening after a reboot. They should just appear in option number "4. Add/edit custom props" right? Not a huge deal, I can update them later.
[Magisk] Didgeridoohan:
No, they'll appear in the fingerprints list ("Edit device fingerprint - Pick certified fingerprint"), under the "Custom" option.
[Magisk] Nothex:
When I am prompted to choose an option, do I use wifi_scan_interval, or wifi.supplicant_scan_interval ?

I have tried both, and neither return a set value.

Thanks in advance!
[Magisk] Didgeridoohan:
In that case the prop currently doesn't exist on your system. No worries... Just pick the value you would like it to be and reboot and the module scripts will set it for you.

Try both and see what happens...
[Magisk] Nothex:
Thank you!!!?
[Magisk] fgprodigal:
My Xiaomi Mi 10 Pro

Xiaomi Mi 10 Pro(10):Xiaomi:Mi 10 Pro=Xiaomi/cmi/cmi:10/QKQ1.191117.002/V11.0.8.0.QJACNXM:user/release-keys__2020-02-01
[Magisk] hyborian:
I use wifi_supplicant_scan_interval, on late stage boot. You can try both boot types, remember to go back to props and check if it was set. It is only set for me if i use late stage.
[Magisk] Didgeridoohan:
Interesting things happening in the Magisk world lately. Google flexed their muscles and showed us that they're perfectly capable of giving us Android modding enthusiasts a hard time. We seem to have a short respite though, since the hardware key attestation bootloader check in SafetyNet was reversed. Possibly just because some OEMs (*cough* OnePlus *cough*) messed up their implementation of the key attestation... No matter why Google reverted the change and let us pass CTS for a time again, we know they're gonna shut us down soon once more.

Until then though, here's a new update to the fingerprints list. Thank you to [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=3536232]yazakachka[/MENTION], [MENTION=3720814]OhioYJ[/MENTION], [MENTION=10582015]Lfly[/MENTION], [MENTION=601351]bagdas[/MENTION], [MENTION=10175111]fgprodigal[/MENTION] and [MENTION=7141309]simonsmh[/MENTION] for the prints provided.

New

Moto X Play

Samsung Galaxy Tab S2

Samsung Galaxy Tab S5e

Xiaomi Mi 10

Xiaomi Mi 10 Pro

Updated

OnePlus 5

OnePlus 5T

Xiaomi Mi Mix 2S

Xiaomi Mi Mix 3
[Magisk] nri_tech1183:
Where did dev said so ??? any valid link?

---------- Post added at 03:50 PM ---------- Previous post was at 03:45 PM ----------

Well its just Green for the sake its not actually true. Its a fake green.

I tried hiddne moduelk and other stuff and got cts true but apps still fail to work.

Will the poco trick of flashing "stock persist.img" work ok Redmi note 7 pro as well? [MENTION=4667597]Didgeridoohan[/MENTION] any thoughts?
[Magisk] garylawwd:
Just look at topjohnwu's Twitter. This is common knowledge now for the past week. Have a read back through the magisk threads and also back through this thread.
[Magisk] OhioYJ:
This has been unfolding for a little while now.

See this Github change.

This twitter thread is a good one (topjohnwu, Magisk's maintainer / creator).

He's got a Q/A on his Twitter thread, he's a good one. (Q6)
[Magisk] nri_tech1183:
So the best sense right now is to stick to stock till some months down or a year till some foolproof idea comes regarding safetynet and security back to good...

Avoiding unlocking BLs and custom roms is the best thing.

Getting back to boring **** Miui rom...
[Magisk] Didgeridoohan:
No idea. I haven't looked into that yet.
[Magisk] PixelPro:
Just remember that if you flash persist.img you will likely lose Widevine L1 DRM functionality on your device, and be permanently downgraded to Widevine L3. To the best of my knowledge, the downgrade is irreversible, and there is no fix for this. Just a friendly reminder. :)
[Magisk] nri_tech1183:
Ok and if I reflash stock rom everything will come back as earlier right?
[Magisk] wrongway213:
No. The post you're quoting says the exact opposite. They're saying it's permanent, meaning nothing you do will revert the L1 status loss.
[Magisk] theCroh:
If I understood correctly, at least on Mi 9T Pro, the persist.img includes device-specific keys that are needed for L1. At least in theory, it should be possible to reverse the change if one has a backup of the original persist.img from that exact device.

This might be very device-specific. At least on one Poco device, unlocking the bootloader irreversibly changes L1 to L3 so I guess you can't get a functioning backup on every device.

---------- Post added at 05:06 PM ---------- Previous post was at 04:58 PM ----------

Do we know if OnePlus can fix the implementation via a software upgrade? If not, then this might hold Google back for a while since banking and some other apps breaking on totally stock new devices would probably not make users very happy.
[Magisk] nri_tech1183:
I dont think so as the original stock rom does contains the default img so reflashing original rom shall bring everything back to normal.
[Magisk] alex.do:
Then its One*cough* we should be thankful for. Lets pray they aint going to fix it any time soon haha. One*cough* devs, you know what, theres something you can do for the community: do nothing.
[Magisk] wrongway213:
You replied to a comment asking for clarification, and although it wasn't my comment, I clarified for you because I understood what the commenter was saying. I'm not sure why you asked the question if you already believe you know the answer, but I can't say for certain what actually happens, as I was just attempting to clarify what the post you were quoting said and not speaking from experience. The post you originally quoted was very clear in saying that flashing the persist.img very possibly permanently breaks L1 widevine status, so I wouldn't advise it unless L1 is unimportant to you. I hope that helps.
[Magisk] theCroh:
At least on Mi 9T Pro devices the persist.img contains device-specific keys and flashing persist.img from any other Mi 9T Pro device breaks L1. There is no generic image that can fix it if you don't have a backup from your specific device.
[Magisk] siroga825:
Besides netflix and other video streaming apps, is there any reason to want L1?
[Magisk] hyborian:
After trying it out, on the Poco F1, reflashing ROM does not bring back L1, nor restoring the backup persist made before the flashing.

It is even easier to bring it back though, and instructions were given in the notes about flashing the fix. To get back L1, go to settings and download the L1 certificate again, and you'll have L1 back.
[Magisk] Didgeridoohan:
The OT is getting rampant again...

Could we keep this thread about the MagiskHide Props Config module? Please?
[Magisk] hyborian:
Will do ...
[Magisk] Nothex:
I just tried that string and set it to a value of 300 seconds, or 5 minutes (and also late stage). I checked after reboot, and the new value stuck! Thank you!!! ???
[Magisk] hyborian:
np ... i actually learned that from the dev - https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post79429272#post79429272
[Magisk] heyitsj0n:
I see. Why did you edit the other prop string values?

Also, I just realized that I did wifi_supplicant, and not wifi.supplicant.

Did the script create a random new string and set an arbitrary value for it? Or did I do the correct one?
[Magisk] hyborian:
I don't remember, that was some time back. Nowadays, I only have just one prop, wifi supplicant prop.

Just delete the wrong one and add in the correct one, should be fine.
[Magisk] Some_Random_Username:
OnePlus 7 Pro 5G Sprint GM1925 Android Q fingerprint: OnePlus/OP7ProNRSpr/OP7ProNRSpr:10/QKQ1.190716.003/2002281825:user/release-keys__2020-02-01
[Magisk] awesomeo3000:
I have a Pixel 2XL running Android 10 (version QQ2A.200305.002). I have root and Magisk and Magisk Manager are both up to date. I also pass SafeNet Check fine. I installed MagiskHide Props Config and Busybox for Android NDK from the Magisk Downloads. When I open up terminal and type busybox, I get a lost list of commands. When I type props to run the script, it says that busybox doesn't seem to be installed. It's clearly installed. I've rebooted many times, and redownloaded and reinstalled many times. How do I get props to run? Please help!
[Magisk] Didgeridoohan:
The module logs would be a good start.
[Magisk] awesomeo3000:
I followed the directions in your documentation and ran props -l. There's nothing in the root directory that looks like a packaged log file. What would the exame name of this file be? When I go to /root/data/adb/mhpc, there are 10 files there. Do you need all those files? What is the easiest way to upload them here? (I can only select max of 4 files when uploading them here, and emailing the files to myself from the phone to the computer so I can attach them here doesn't work). Magisk log is attached.
[Magisk] Didgeridoohan:
For module issues I would need all those files, yes. Easiest way to upload them all would be to make a zip. But, from your Magisk log it doesn't seem to me a module issue since I can see that you have tried to install Busybox NDK but for some reason that didn't work. It isn't loaded by Magisk.

When you ran the Busybox command earlier, what version does it show as (says at the top), and what output do you get if you run this command:

which busybox

Are you by any chance using Termux?
[Magisk] awesomeo3000:
I'm using Termux and Terminal, with same results in both. When I run 'which busybox', I get a blank line. But I also installed BusyBox from the Android Play store. After installing the Play one (need to re-install after every reboot because basic version), and typing 'which busybox', it says /sbin/busybox.*How do I create the packaged log file that's all zipped up, and where do I find it?

All I'm really trying to do is just execute echo "net.tethering.noprovisioning=true" >> /system/build.prop, but it looks like on Android 10 they changed the structure, and I get the error "can't create /system/build.prop: Read-only file system". I've tried 'mount -o rw,remount /system', but it says " '/system' not in /proc/mounts." I hope after all this pain, that props will at least be able to make the build.prop change that I need to make. If you know easier way to do the simple change I need to do, I'm all ears. Please let me know.
[Magisk] Didgeridoohan:
Getting a blank line when running which busybox means there isn't one installed. But you said you did get an output when running the Busybox command... What version was that reported as?

After having installed a Busybox from the Play store, did you try running props again? Since you now could detect a Busybox binary, it should work.

You should be able to use any root capable file explorer to get the files and put them in an archive. I always use FX File Explorer and recommend it, but there are many others. Once you have them zipped up you can post that file here.

Since you have a Pixel there's no possibility to do it the old-fashioned way of editing the file directly (look up Android logical partitions of you want details on that). Magisk to the rescue.

Of course, I would very much appreciate if you could work with me here and try to figure out why you can't get the module to work. It's perfectly possible there's a bug and that I've messed something up along the way.

You have a few options though.

You could still use the module, but instead of using the props command and the terminal UI you just the configuration file to set everything up. Simply add net.tethering.noprovisioning=true to the CONFPROPS variable, put the file in the root of your internal storage and reboot. See the docs I linked and the file itself for more instructions and details.

Another option is to just use a simple boot script. Put the following in a file (doesn't matter what you name it) in /data/adb/service.d:

#!/system/bin/sh
resetprop net.tethering.noprovisioning true

Give it execution permission (chmod 755 is usually the goto) and then that prop will be set at each boot. If it doesn't seem to work, put the script in /data/adb/post-fs-data.d instead.

But like I said, before you do that, please help figure this out.

One other thing you could do is to try to install Busybox from the Magisk downloads again and save the install log. That might also show some hints as to why things doesn't seem to have worked. And do you happen to have this directory, from the previous install: /data/adb/modules/busybox-ndk

If you do, what's in it?
[Magisk] awesomeo3000:
When I run busybox_M (the module installed from magisk), I get an error that busybox is not found. After I install busybox_P (the app from the Playstore), and run busybox, it says it is v1.30.1.

Yes, tried running props again and it still says "no busybox found", even after running busybox in the terminal and getting the version and the full list of available busybox commands.

When I try FX File Explorer, I don't see a /data/adb folder. When I use Solid Explorer, I see everything fine but when I try to archive a folder or the files, it gives me an error that I don't have permission to archive anything, and then all the root files disappear until I reboot the phone!

Thank you so much! You're a life saver. I was desperate to get my hotspot working, and I was able to get it using your instructions in modifying the propconf directly. And I will definitely work with you to figure this out. I'd like it to work seamlessly next time we all update our phones :)

I do have that directory, but it is empty. I've attached some log files. When I attach them from my phone, this webpage errors out when I try to upload any of the logs from root.
[Magisk] Didgeridoohan:
I can't reproduce any of the issues you are seeing... I've tested with different terminals and busybox installs on my end and everything works as expected, so there's something wrong on your end that we need to figure out. When working with or trying to upload any of the module logs and files, first copy them from /data/adb/mhpc to your internal storage. That should make things work as expected.

The Busybox installation from the Magisk repo failed miserably and it seems like you have a magisk.img file on your device that shouldn't be there. I would suggest that you do a full uninstall of Magisk and then install again, to make sure that there are no leftovers of previous installations laying around and causing issues (which it currently seems like there is).
[Magisk] Didgeridoohan:
Fingerprints list update to v82

Quick update to the fingerprints list (v82). Thank you to [MENTION=8234677]Some_Random_Username[/MENTION] and SyberHexen over @ GitHub for the prints.

New

Motorola Moto G7 Play

Updated

Motorola Moto G7

Motorola Moto G7 Power

OnePlus 7 Pro NR Spr
[Magisk] akerenyi:
Busybox not detected

Hi!

I have a similar problem as [MENTION=4407595]awesomeo3000[/MENTION]. Trying to use Props to pass ctsProfile on my Poco F1 with LineageOS 16.0, Magisk 20.3. Installed Busybox 1.31.1 from the Module list and then MagiskHide Props Config. When I run props from Terminal Emulator, I get No Busybox Found error. which Busybox returns nothing. Tried with the PlayStore Busybox app as well but the same error.

I have copied the Busybox module installation log below. The contents of /data/adb/modules/busybox-ndk which is only one module.prop file.

Thank you for your help!

- Copying zip to temp directory

- Installing UPDATE-Busybox.Installer.v1.31.1-ALL-signed (1).zip

Archive: /data/user/0/com.BOJv.RKti1xEA.UC/cache/flash/install.zip

inflating: install.sh

Busybox Installer Script

by osm0sis @ xda-developers

Mounting...

mount: can't read '/etc/fstab': No such file or directory

mount: can't read '/etc/fstab': No such file or directory

mount: can't read '/etc/fstab': No such file or directory

Extracting files...

Archive: /data/user/0/com.BOJv.RKti1xEA.UC/cache/flash/install.zip

inflating: META-INF/com/google/android/updater-script

inflating: META-INF/com/google/android/update-binary

inflating: README.md

inflating: busybox-arm

inflating: busybox-arm64

inflating: busybox-mips

inflating: busybox-mips64

inflating: busybox-x86

inflating: busybox-x86_64

inflating: install.sh

inflating: module.prop

inflating: META-INF/MANIFEST.MF

inflating: META-INF/CERT.SF

inflating: META-INF/CERT.RSA

Installing...

Using architecture: arm64

umount: can't unmount /dev/tmp/magisk: No such file or directory

mount: can't setup loop device: No such file or directory

mknod: /dev/block/loop0: File exists

Using path: /dev/tmp/magisk/busybox-ndk/system/xbin

Cleaning...

Creating symlinks...

Unmounting...

umount: can't unmount /system: Device or resource busy

umount: can't unmount /data: Device or resource busy

umount: can't unmount /cache: Device or resource busy

Done!
[Magisk] Didgeridoohan:
Yeah, you've got similar installation issues (but not quite). No idea what that could be about. Any other Busybox should work though, so again I have no idea what that's about.

As previously stated, I would need more logs to even have a chance of figuring this out, so please provide your module logs: https://github.com/Magisk-Modules-R...lob/master/README.md#collecting-logs-manually
[Magisk] akerenyi:
Here is a link to a zip archive with the requested logs.

Thank you in advance for your help!
[Magisk] Didgeridoohan:
I'm not seeing anything that stands out... And like I wrote previously I cannot reproduce the issue.

All I can suggest now is to maybe try doing a clean install of the new Magisk beta release (v20.4) and see if that changes anything.
[Magisk] Born<ICs:
??? for Didgeridoohan

Terminal

props

?

I've just rooted a new 4 Xl and need to get the tethering hotspot setup and working for Verizon grandfathered unlimited.

Magisk latest stable and Busybox installed. Module MagiskHide Props Config and Busybox for Android NDK installed.

In terminal emulator do I simply enter ...

props, 4 and then net.tethering.noprovisioning true

I'm not too savvy with terminal etc so fool proof instructions would be most helpful.

Thank you

EDIT>>>>>>>>

I found these instructions but for a 3XL

Are these steps correct?

Terminal

su

props

4	custom prop

n	new prop

net.tethering.noprovisioning

set type?

true

confirm?

y

confirm reboot?

y

After reboot

Terminal

su

settings put global tether_dun_required 0

exit terminal

reboot
[Magisk] Didgeridoohan:
[MENTION=4924608]Born<ICs[/MENTION] That should do it. Those settings are (as far as I know) generally not device specific.
[Magisk] Born<ICs:
OK thank you much, I'll give it a go with those settings.

Edit:

Hotspot up and running, thank you much.