yashsingh1/xdaforums huggingface dataset:
[Magisk] gfrank227:
Hi everyone. I have a strange situation on my phone. I'm running a Moto G8 Plus; it's rooted. Simply enabling MagiskHide was enough to pass SafetyNet. This morning, the SafetyNet failed both basic integrity and CTS. I'm not sure why. However, the strange thing is, Netflix and Google Pay still seem to work, and SafetyNet Check and Root Checker both say that SafetyNet passes.

there is another app that gives a warning when rooted, and that warning is back and won't go away. Has anybody ever seen anything like this before? Can MagiskHide Props Config assist with this? I suppose it's not critical to fix because Netflix and Google Pay still work, but it would be nice to know what's going on so that I can determine if it's an issue that needs to be dealt with.

Thanks!
[Magisk] Didgeridoohan:
If it's an API error:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_API_error

But why are you using a Pixel 3a print? The Pixel 5 prints are available in the module...

If you've got further issues there are many tips to be found if you keep reading other parts of the above linked page.
[Magisk] Didgeridoohan:
Here are some tips on how to find it:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] Didgeridoohan:
The Android 8 print for the Galaxy A5 2017 is available in the module. As far as I can tell that's the latest available Android release for that device, so that's what you get...

Just run props, pick "Edit device fingerprint" and then follow the menu options to pick the device from the included list.
[Magisk] Didgeridoohan:
That sounds like this:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_API_error

And that's already been dealt with upstream (fix available in the Canary releases). It's purely cosmetical thoughand has no real implications...

Regarding your other app:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

The one way this module can help with that is if the device is detecting some prop value. If that's the case (I doubt it) you can change it with the custom props feature.
[Magisk] NickEspo:
Background: Magisk-rooted phone, Pixel 3 (blueline).

For SafetyNet reasons, I'd used the MagiskHide Props Config plug-in to change the device fingerprint; Although I'd intended to change it to a Pixel 3A (sargo), I accidentally changed it to Pixel 4 (flame).

However, after rebooting, I can't seem to be able to change it back to Pixel 3; the terminal emulator* can no longer find or recognize the props plug-in. I've removed and reinstalled it, but I'm wondering if changing the fingerprint to a higher-level phone somehow bolluxed things up as far as which device folders can be accessed.

Does anyone have any idea how I can fix this? Is there a way to change the phone fingerprint (through either terminal emulator or adb) without using the Props Config plug-in?

* I'd been using Jack Palevich's "Terminal Emulator for Android," but after the fingerprint change it no longer seems to work, so I switched to Fredrik Formwall's "Termux" == which reports that it cannot find the plug-in.
[Magisk] Didgeridoohan:
If you're using Termux you need to run su before props.

If you still can't figure things out, the best way to get help is to provide the module logs:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] NickEspo:
Thanks, Didge! That was indeed the solution. Managed to get everything back to Pixel 3 again. Many thanks!
[Magisk] ipdev:
Sorry all for a bit of OT. 🙃

For reference:

Custom rom can include the Universal SafetyNet Fix.

Universal SafetyNet Fix - GitHub - ROM integration - Link

As noted, including the fix into the rom build is the better option.​

I checked a few days ago and crDroid now includes the Universal SafetyNet Fix.

crDroid GitHub - Commit

They made a slight change - GitHub - Commit​

crDroid roms built prior to that commit (depending on the device), may still need to use the Universal SafetyNet Fix module.

Cheers. :cowboy:
[Magisk] jomann:
I have a Samsung S9 (G960F) running LineageOS 18.1 (unofficial - synt4x.93) and I can only pass safetynet if I use a provided certified fingerprint (menu 1,f). If I use the vendor partition (menu 1,v) the same fingerprint is shown, but safetynet fails. Any ideas about what is applied differently for the vendor partition fingerprint?
[Magisk] michaelc5047:
Hi there, I've got Moto G Stylus (sofiap) and when I pick a certified fingerprint, apparently the module does not save the new fingerprint and I fail CTS profile. Any ideas? Running latest build of OmniROM.

EDIT: Never mind -- I didn't need to pick a certified fingerprint after all, I reset to the original fingerprint and all of a sudden it passes now! Feel free to delete this.
[Magisk] Didgeridoohan:
Thought I had replied to this, but with the new achievements system rolling out the forums have been a bit quirky the past couple of days, so it might have been lost on the matrix...

If the vendor print doesn't work it's most likely caused by the security patch date not matching. Most of the time the patch date in the vendor partition will match the print, as long as the vendor partition is stock, but sometimes it doesn't.

Picking a fingerprint from the list will always use the correct patch date for that print.
[Magisk] Didgeridoohan:
From your screenshot it looks like the print applied just fine. But since you were supplying your own print, did you remember to also edit the security patch date to match the print used? If not, that's the most likely point of failure.
[Magisk] michaelc5047:
No, I didn't, but the "sofiap" fingerprint wasn't the one I chose -- I had applied (based on what people on the Telegram Moto G8 Family group were saying) the Pixel 4XL and 5 fingerprints on separate tries, but they never showed as having applied.

In any case, when I just chose the "reset" option and tested it again, it passed just fine, so it's all good :)
[Magisk] ipdev:
I have not tested yet..

Motorola moto g stylus

Pulled from recovery image.

Cheers. :cowboy:
[Magisk] jomann:
Thank you for replying.

Is it possible to "correct" the patch date in the vendor partition? If so, where is this date and how would I determine what it should be? I realize I'm trying to "fix it until it's broken", but I'd appreciate if someone could point me in the right direction which you've already done to some extent.
[Magisk] Didgeridoohan:
That sounds like way more effort than it's worth... Editing files in system partitions always have the possibility to cause issues, that's why Magisk's systemless approach is so powerful. And if you're going to be using this module to set the device fingerprint you might as well do the same for the security patch date... Just pick the print from the included list.

To find out what date to use for a specific print you'd have to either do a bunch of trial and error, but that's really tedious, or check the security patch for the build that the print on question came from. If you don't know what build that was you're out of luck... If you want to use a print from my module you can find the patch dates attached to the prints in the module list:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
[Magisk] valunthar:
It looks like in this case I was thrown off my magisk safetynet not working in the recent version. managed to get it figured out though by using a third party safetynet check, thank you for responding, got me going in the right direction.
[Magisk] korabio:
hi, can you add this device?:

HUAWEI/WAS-LX1A/HWWAS-H:8.0.0/HUAWEIWAS-LX1A/376(C02):user/release-keys

is a Huawei P10 Lite with emui 8.0.0 build: WAS-LX1A 8.0.0.376(C02) Patch 1 March 2019 (Stock rom)

Details:

ro.product.manufacturer HUAWEI

ro.product.model WAS-LX1A

ro.build.version.security_patch 2019-03-01

ro.build.fingerprint HUAWEI/WAS-LX1A/HWWAS-H:8.0.0/HUAWEIWAS-LX1A/376(C02):user/release-keys

thanks
[Magisk] hhllss:
Hello,

I am running LineageOS 18.1 (22/04/2021) on my OnePlus 8T (KB2003). I am unable to pass safetynet, since even basicIntegrity is failed (after doing props / 1 / f / 21 / 44 / reboot). It was working on the unofficial Lineage 18.1, before. I am probably doing something wrong, but could not find what.

If anybody can help :)

Thank you !
[Magisk] OhioYJ:
New Android 11 Fingerprint for Tab S5e, think this is everything:

getprop ro.build.fingerprint

samsung/gts4lvwifixx/gts4lvwifi:11/RP1A.200720.012/T720XXU2DUD3:user/release-keys

getprop ro.product.manufacturer

samsung

getprop ro.product.model

SM-T720

getprop ro.build.version.security_patch

2021-03-01
[Magisk] Darknessmatrix:
Hi this is my first time

I can't pass the SafetyNet on poco x3 nfc

12.0.8 global QJGMIXM
[Magisk] andrew2432:
Hey @Didgeridoohan I can't get my hotspot to work. Please fix immediately.

Sarcasm out of the way, I cannot for the life of me edit my build prop. Nothing I use will chmod the damn folder, nothing I use will pull or push the file and replace it, magisk grants su to every freaking app. I'm literally trying to add a single line to my build prop to see if it hides tethering.

Normally, and shell put global tethering_dun_required 0 solves my issue and has for years on sprint. Custom operating systems also solve the issue naturally. I wanted to play on stock for a bit. This time I have flashed stock, prevented any sprint or TMobile applications from downloading at setup, set global tether dun required and req it was once to 0, and it does not work. Data is not transferred to other devices. I'm not looking for VPN/hotspot/proxy app for sharing. I attempted to add net.tethering.noprovisioning=true

net.tethering.provisioning=false

To the build prop using your tool (hehe). I rebooted but I am still unable to get my hotspot to work.

Any thoughts? Through observing the log, I can see your tool is hard at work. So can I assume it added this line to build.prop? It says system.prop but it's a mirror of the original with yours added if I understand correctly?

Conversely if you can help me chmod my damn folder correctly I can at least change the build prop on a text editor and put it back. But I can't seem to figure out how to chmod the folder so I have write permissions. I also know all of the vocabulary and NONE of the commands. Then no internet when in recovery or anything so I gotta have my instructions on hand lol

Any thoughts that will point me in a decent direction will help. I wanted to get it working before going to a custom os for that alone. It's odd because the adb shell commands have fixed the network side of tethering with sprint/TMobile always. I've run into a few issues lately with it From my understanding I can add net.tethering.noprovisioning=true to the build prop in some form- pull it, edit it, push and replace it, or give up and go with lineage asap because I got 50gb in a weekend
[Magisk] Didgeridoohan:
Hard to pinpoint exactly what that could be...

First thing I'd check is if you're having an API error in the Magisk app. If so, that's a cosmetical issue and SafetyNet is most likely passing but the Magisk app just can't check it (it's been fixed upstream already).

If that's not the case, and since you're failing basic integrity as well it's unlikely to be a fingerprint issue alone (although that might be part of it). To pass CTS you'd also likely need the Universal SafetyNet fix, but for the basic integrity check it could be things like not having enabled MagiskHide, or having some mod installed that is triggering SN (EdXposed, etc).

Check here for more:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] Didgeridoohan:
See the post just above this one and if the info there doesn't help take a look in the "check here for more" link.
[Magisk] andrew2432:
Also try play store apps, magisk showed me red but all the play store apps showed good?
[Magisk] Didgeridoohan:
Sure, just jump over to my TG channel and I'll get right on it.

If you use this module (or in any way using the Magisk resetprop tool that this module is based on) the build.prop file won't be altered. It just loads the values you choose instead of the one from the file...

https://github.com/Magisk-Modules-R...uildprop-doesnt-change-after-using-the-module

Depending on your device and Android version it might not even be possible to make it writable...

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

Yeah, that's what I'm talking in the posts above (API error). It's nothing to worry about...
[Magisk] ipdev:
Besides the link Didgeridoohan provided.

Start with the instructions in the What option should I use? section.

MHPC ReadMe (How-To) GitHub - What option should I use? - Link

Since you are using a stock rom, you probably need to Force BASIC key attestation.

MHPC ReadMe (How-To) GitHub - Force BASIC key attestation - Link

Cheers. :cowboy:
[Magisk] Darknessmatrix:
Thanks for your help I missed that one

I'll try it
[Magisk] Darknessmatrix:
Thank you
[Magisk] andrew2432:
So the build prop is a whole new area. I remember this being the snag for my galaxy s5. I really had issues changing the build prop. No app will do it. Even with root it wouldn't because it wasn't writable. Android 11 pixel 5. Finally went big instead of used... Twrp doesn't fix that? We have a test twrp and a few other recoveries.

To this scope, doesn't adding a prop with your tool, I did it at the default stage, essentially do what I'm trying to do without changing permissions on the system files? Meaning it will load that line into the buil.prop on boot, causing systemwide stateless changes??

Also, I believe this trick may only enable the hotspot button once booted. This may not be a specific fix for hiding tethering usage. How it's happing now after success on so many devices makes me think there has to be a system process running that's snooping on me but I have no idea how to check thattttt ughhhhhh

Did this do what I have described to you lol I wanted net.tethering.noprovisioning=true (and maybe I wanted .provisioning=false, it's changed over the years, God how old are we, just got my GPS joystick working for Pokemon thanks to you and f0mey like yesterday I thought...) Added to my build.prop. if it did not, certainly your tool allows for that, and how would I do it lol

props
4
n
net.tethering.noprovisioning
true
y

If you're serious about helping me on telegram, I think I know enough to narrow down WHAT the issue is. Just not what the heck to do about it. there is a separate apn for "dun" which has me thinking i could change the apn settings. Or it's got to be an app or system process I need to kill. it has never happened using the adb shell commands, that's always immediately fixed it. With stock Samsung I had to use a hacky hotspot unlocked first. Now, a minimal hotspot plan comes with. With the base info if you're serious I'll get on haha other than that, the rest of my posts will be on this module, and I will run through and give you some thanks as well when I'm not spastic about my hotspot. There are fixed, wifidirect, whatever. But what can't I just edit my natural system process to change ttl packets or whateverrrrrr ok done.
[Magisk] Didgeridoohan:
@andrew2432 Doing that with this module would set the prop to true, yes. But I can't say if that's what you need to do on A11... You might have to research that in the Pixel 5 forums.

If you can manage to find my Telegram handle anywhere in the thread or in my profile you're very welcome to contact me there (hint: there isn't one, so don't bother looking :p). I'm not a fan of using Telegram for stuff that the forums are perfectly suited for... In other words, I wasn't serious at all. :D
[Magisk] andrew2432:
Haha these kids are using telegram for everything. I thought it odd...but when you said it I thought maybe he's serious. didn't realise I was getting it back, needed a laugh lol

So, since I correctly used your tool to add that line to my whatever prop, I can assume it did not work. So the culprit cannot be the build prop. Addition of the line to the build prop, system or otherwise will not hide tethering. Based on the fact that your module did the super easy thing I found complicated but your app made simple, I can confidently rule out the build prop edit as a fix for my issue...! (?)

The core issue is somehow the carrier is detecting tethering. On custom os...lineage smacking me in the face waiting to be played with anyways...it's somehow done by default. I think ,dun is in the apn? On stock phones, I have Ben able to get around it by adb shell and doing setting put global tethering_dun_required 0 and it shows hotspot data as mobile data. Forever. Did this on at least 7 different phones. I've read you can add ,dun to your apn. But I have had 0 luck. There's an adb method I'm about to brick this sucker with here soon...

I think it's the apn and idk how to change it. There's an apn called "dun" and that's always been phone as modem, tethering. There has never been a separate apn for "dun" on sprint. Maybe I can add ",dun" to my apn on the original like way back and then delete the other one?? Idk always flash back to stock lol this is the mess...just install lineage already lol
[Magisk] Didgeridoohan:
It seems like this print/security patch date combo doesn't pass CTS, unfortunately. Have you tried it yourself?
[Magisk] Didgeridoohan:
It's not unlikely that A11 changed something and that old tricks no longer works. You can find reports along those lines in the later parts of this thread:

https://xdaforums.com/t/magisk-tethering-enabler.3937427/

LIke I said, checking your device's forum might be the best option.
[Magisk] Didgeridoohan:
Fingerprints list update to v126

I've been lagging behind on keeping things updated for the past few weeks (good thing there hasn't been much action). Schools been crazy busy and I've been finishing up another project of mine (if you're interested, check my Github I've got a brand new repo on there).

Thank you @liyiecho, @ipdev and @korabio for the prints. You guys rock!

The prints list will update when you run the props command, or by using the -f option or from the "Edit device fingerprint" menu if you've disabled automatic updates.

New

Huawei P10 Lite

Motorola Moto G Stylus

Xiaomi Mi 10S
[Magisk] andrew2432:
That's old but it's the same language in using haha ok thanks. It's not unlocking it or enabling it that's the issue. It's showing mobile data instead of hotspot data that is suddenly an issue this time. It's that apn, this may have nailed it down.
[Magisk] ipdev:
Hi.

I have not looked into it too much.

Not sure if it a prop setting or something in the Network APN.

I attached a getprop dump of my Pixel 3aXL (Android 11) that Hotspot & tethering works on.

If you compare my props to yours, you may see something missing. ?

I am able to connect my Nexus 7 (2013) WiFi to my 3a XL and had no issues with internet connection.

I am running a custom rom (abc-rom) on my Pixel 3a XL, as close to Google stock as you can get without the bloat. ;)

I am running a custom rom (unofficial Lineage 18.1) on my Nexus 7 (2013).

Cheers. :cowboy:
[Magisk] andrew2432:
Delay: installed lineage, could get cell service but no data at all Had to revert full stock to get back online lol need to look through there for troubleshooting

I am not nearly as versed in this side of things but I will look through it. I did it to three different pixel XLs, stock or otherwise. Changing tether dun settings worked fine with my Samsung Galaxy S5, s3, and worked with a Galaxy note 4. I have to get to the bottom of this. I've never had an issue but I've seen others in forums unable to get a "normal" fix working.

Going through I found my code lol copy and pasted around it. How do I pull that full log there lol I don't even know how to do that haha going through the rest.

net.bt.name=Android

net.dns1=209.18.47.63

net.dns2=209.18.47.61

net.qtaguid_enabled=1

net.tcp.default_init_rwnd=60

net.tethering.noprovisioning=true

nfc.initialized=true

persist.audio.dualmic.config=endfire

persist.audio.fluence.speaker=true

persist.audio.fluence.voicecall=true

I saw a few things but nothing I could tell related to tethering other than that. Not directly at least, there were a few things. This is my internet connection I gotta get this sorted out lol
[Magisk] ipdev:
We are getting a bit OT for this thread but, since it is MagiskHidePropsConfig thread..

You can use the getprop command and point the output to a file.

getprop > NameOfFile

The output will look like this

[net.tethering.noprovisioning]: [true]

I use the sed command to format the output to be the same as a normal build prop file.

getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g' > NameOfFile

The output will look like this

net.tethering.noprovisioning=true

The getprop command is not a privileged command. You can run it as user and get the current props.

Since some of the props are privileged, you can only get them running getprop with heighten security (root).

Using my 3aXL as an example.

Running getprop as user, getprop returns 563 lines.

Running getprop as root, getprop returns 1056 lines.

If you are using adb, make sure to grant root access to adb shell.

From you computer you can run getprop as su to dump the props into a local file.

adb shell su -c "getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g'" > NameOfFile

This will create a file named NameOfFile in you currently directory on your computer.

If you open an adb shell.

adb shell
su
getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g' > NameOfFile

This will create a file named NameOfFile in you currently directory on your device.

If you are using a terminal app.

su
getprop | sed 's/\]: \[/=/g; s/\[//g; s/\]//g' > NameOfFile

This will create a file named NameOfFile in you currently directory on your device.

Note:

If you are writing the output to the device, make sure you are in a directory that is writable.

/sdcard/Download/ is a good default since it should allow write access.

Hope it helps more than confuse. :)

Cheers. :cowboy:

EDIT:

PS.

Normally you do not need to run getprop as root.

Running getprop as user is normally all you need.
[Magisk] rullydotcom:
Can I still get benefit of this module if I don't have gapps installed? (I use microG)

Is it possible to pass safety Net with microG (without gapps) ?
[Magisk] andrew2432:
Hey!!! After deleting my apn I thought was trouble, my hotspot wouldn't turn on, not allowed by carrier. I rooted, installed this, added my desired net.tethering.noprovisioning=true using this tool, and it allowed my hotspot to turn on! No data was transmitted through the hotspot, but it absolutely did what it was supposed to!!! Now on to the next steps...
[Magisk] Didgeridoohan:
As far as I know (I don't use microG) you can't pass SafetyNet with microG. Changing the device fingerprint with the help of this module wouldn't make any difference.
[Magisk] Displax:
Pixel's update:

Pixel 3=google/blueline/blueline:11/RQ2A.210505.002/7246365:user/release-keys__2021-05-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ2A.210505.002/7246365:user/release-keys__2021-05-05
Pixel 3a=google/sargo/sargo:11/RQ2A.210505.002/7246365:user/release-keys__2021-05-05
Pixel 3a XL=google/bonito/bonito:11/RQ2A.210505.002/7246365:user/release-keys__2021-05-05
Pixel 4=google/flame/flame:11/RQ2A.210505.002/7246365:user/release-keys__2021-05-05
Pixel 4 XL=google/coral/coral:11/RQ2A.210505.002/7246365:user/release-keys__2021-05-05
Pixel 4a=google/sunfish/sunfish:11/RQ2A.210505.002/7246365:user/release-keys__2021-05-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ2A.210505.003/7255357:user/release-keys__2021-05-05
Pixel 5=google/redfin/redfin:11/RRQ2A.210505.003/7255357:user/release-keys__2021-05-05

Xiaomi Mi A3

Global: Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.8.0.RFQMIXM:user/release-keys__2021-04-05

Europe: Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.6.0.RFQEUXM:user/release-keys__2021-04-05
[Magisk] Kelden:
Anybody who can post a fingerprint for

Oneplus 7T HD1903 Android 11 version?
[Magisk] TerrySpeed:
After typing `props` in Termux, I get the following error:

No command props found

EDIT: nevermind, I just had to run "su" before.