yashsingh1/xdaforums huggingface dataset:
[Magisk] estofjlw:
the reality is . . . a TOS is a waiver of rights

[MENTION=4667597]Didgeridoohan[/MENTION]

I have a degree in Law. Surveillance is legal and not a crime - when it is waived in a contract. The grey area is a TOS is an adhesion contract - and is borderline carte blanche enforceable. If you voluntarily agree to install an app that states it does surveillance or a sort along with the TOS that states it allows it, it no longer violates Federal or State law in a criminal sense and becomes a civil matter that no one can afford to or wants to - as in any lawyer or law firm - will pursue.

They have figured this out - and since the FCC has disclaimed jurisdiction to "broadband" and since the LTE block only applies to the data - or "broadband" there is nothing anyone can do really - because one still has working phone service and text service.. Keep in mind the eavesdropping and wiretapping laws apply as in surveillance to active voice and data communications in some limited senses - it does not cover the trojan horse apps that look at apps or data on the phone - with the subscribers agreement.

The legal problem all carriers now have is that most accounts are now defined inclusive as voice-text and data all in once account for a charge that is no distinguishable in parts as a service - and so since Google is who actually owns "android" as a brand name Operating System for the device the Carriers cannot really STOP device modifications that still work and do not hamper or disturb their networks. They will block the device if it does - or they say it does. They will need to leave it up to Google to do a crack down through the OS itself but they will act on information that Google provides of a "compromised device" they will claim under the umbrella as a "security" threat to the network. Thankfully - the manufacturers are not at this time really interested in starting an Open Source war themselves and nor do they have the right to - they only provide a serve that uses a fixed product - the cell phone itself.

It is now very hard to develop a ROM that looks so much like the stock OS no one can really tell - or I should say no one is really trying to right now, though they really should be.

So the way you are thinking of surveillance does not apply and the bottom line is the customer will never be able to prove exactly what is being done unless they have worked in the industry like I have and know the trouble shooting issues that are tell-tale. The carrier will block the IMEI in a hot minute if it trips the device integrity traps. Whether it is permanent or temporary depends on the carrier and if the device is seen again in a stock configuration back like it is supposed to be. The carrier will almost never admit to this however.
[Magisk] Didgeridoohan:
The unfortunate answer I have is: I haven't got the slightest idea...
[Magisk] Didgeridoohan:
[MENTION=8483170]estofjlw[/MENTION] that's an interesting read (and an ace wall of text, 10 out of 10).

But, I believe you're talking about U.S. law, right? I'm a few km away across the Atlantic (Swedish) and our laws work differently. I'm no legal expert (although I do enjoy perusing legal texts), but from my knowledge you actually cannot waive your legal rights through a TOS here (even if some companies try from time to time), and doing any kind of surveillance require a government permit. You can't even leave a camera unattended for automatic photography in the middle of the woods (game camera, wildlife photography, etc) without a permit and people have actually been convicted and fined for this.

Doesn't stop people from installing apps that collect everything about them though... Etc.

I'm not knowledgeable enough to discuss the finer points of this or how carriers actually operate here, but I enjoy this small glimpse you've given me into a previously unknown (to me) world.
[Magisk] estofjlw:
Yes US . . . and here it is the opposite - camera and eavesdropping outside recording conversations is legal - and here people can waive rights in a contract. But as said - an adhesion - or click through online contract - one you do not actually sign or negotiate is not presumed 100 percent enforceable.

The various reasons you mention is why Google and the carriers do not take a more aggressive stance. Laws across jurisdictions - ever here in the states is a quagmire
[Magisk] GtrCraft:
Update for Poco X2:

fingerprint: POCO/phoenixin/phoenixin:10/QKQ1.190825.002/V11.0.10.0.QGHINXM:user/release-keys

security patch: 2020-04-01
[Magisk] hyborian:
I copied a PROPSCONF_CONF file from common dir, edited it to add some props, and put it in /data.

After reboot, checking in terminal shows my props are active.

However, the PROPSCONF_CONF file is no longer found in /data. I rebooted and my added props are still active in terminal, but still no PROPSCONF_CONF file in /data.

So just wondering where it is now ? i.e. where is Magiskhide Props Config getting the info now for the props I added ?
[Magisk] Didgeridoohan:
That's intended. Check the last note of the config file section in the docs:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#configuration-file
[Magisk] Ziomek64:
So i'm using Xperia 10 and have cts profile match failed. How can i provide help for you and me at the same time? :D I don't know if i have fail because of custom rom as i had fail on stock but with bootloader unlocked, will it bypass bootloader unlock?
[Magisk] Dr.][No_WaY:
Hello,

How to restore all changes done by this module to original? Or at least fingerprint?
[Magisk] Didgeridoohan:
The module doesn't hide the bootloader state, but Magisk does (for now).

You can test if a certified print will help by picking one of the included ones even if it doesn't match you device. If you then pass CTS we know it works...

If you want a print that matches your device you can find some tips here:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] Didgeridoohan:
If you can boot up your device alright you run the props script and pick "Reset fingerprint" under the "Edit device fingerprint" menu. Same for any custom props you've set, but of course under the "Add/edit custom props" menu.

If you can't boot you've got instructions in the docs:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] hyborian:
Oh, wow, I was reading that earlier and I don't know how I missed that lol. Thanks !
[Magisk] dukemagus:
I'm having problems with this module and how to report it.

The device doesn't boot if I change the device fingerprint. If I change the mode to late, the fingerprint is unchanged.

But if it doesn't boot, there's no way to collect logs on the failed boot to send (or at least I haven't found a way to save it. Suggestions are welcome)

Chainfire's Live Boot that should replace the boot Animation doesn't kick in, so it is stopping before that.

And disabling the module on orangefox makes the phone boot normally again.

I'm using a Redmi Note 7 with crDroid 6.3 (android 10) and the device stopped turning on when trying to use a fingerprint from Redmi note 7 (Android 9) and Google pixel 2 (Android 10).

Any ideas on how to collect the information necessary to ask for help?
[Magisk] Didgeridoohan:
No TWRP for that device?

If there is you can collect the logs manually (after letting the device sit on the splashscreen for a while):

https://github.com/Magisk-Modules-R...lob/master/README.md#collecting-logs-manually

If there's no TWRP you can follow this section to disable the module and then collect the logs manually:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] dukemagus:
Here's the content of the folder. Hope it helps
[Magisk] Some_Random_Username:
Hi guys, this week has been a week during which one OnePlus released stable builds for a lot of its devices, here are updated fingerprints.

OnePlus 5: OnePlus/OnePlus5/OnePlus5:10/QKQ1.191014.012/2005122320:user/release-keys__2020-04-05

OnePlus 5T: OnePlus/OnePlus5T/OnePlus5T:10/QKQ1.191014.012/2005130017:user/release-keys__2020-04-05

OnePlus 6: OnePlus/OnePlus6/OnePlus6:10/QKQ1.190716.003/2005052051:user/release-keys__2020-05-01

OnePlus 6T: OnePlus/OnePlus6T/OnePlus6T:10/QKQ1.190716.003/2005052051:user/release-keys__2020-05-01

OnePlus 7 GM1901 and GM1905: OnePlus/OnePlus7/OnePlus7:10/QKQ1.190716.003/2005132200:user/release-keys__2020-05-01

OnePlus 7 Pro GM1911 and GM1917: OnePlus/OnePlus7Pro/OnePlus7Pro:10/QKQ1.190716.003/2005132200:user/release-keys__2020-05-01

OnePlus 7 Pro NR GM1920: OnePlus/OnePlus7ProNR_EEA/OnePlus7ProNR:10/QKQ1.190716.003/2005102305:user/release-keys__2020-05-01

OnePlus 7T HD1901 and HD1905: OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/2005192100:user/release-keys__2020-05-01

OnePlus 7T Pro HD1911 and HD1917: OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/2005192100:user/release-keys__2020-05-01

OnePlus 7T Pro NR HD1925: OnePlus/OnePlus7TProNR/OnePlus7TProNR:10/QKQ1.190716.003/2005062342:user/release-keys__2020-04-01

OnePlus 8 Pro IN2021: OnePlus/OnePlus8Pro/OnePlus8Pro:10/QKQ1.191222.002/2005211243:user/release-keys__2020-04-01

OnePlus 8 Pro IN2025: OnePlus/OnePlus8Pro_IND/OnePlus8Pro:10/QKQ1.191222.002/2005190021:user/release-keys__2020-04-01

EU versions of 7 and 7T series are told to roll out later, I will post their fingerprints once they will be available.
[Magisk] Dizzy_trout:
ADB Root

Hey guys, I've been chasing how to run getevent commands over adb on my pixel 2. Long story short, the latest thing I've tried is setting the following:

ro.adb.secure=0
ro.secure=0
ro.debuggable=1

I've double check with getprop in adb cmd terminal that the values were set. But when I try to send adb root I still get "adbd cannot run as root in production builds". If I run getprop ro.build.type I get 'user'. I'm currently at a loss as what to do next. Any advice is appreciated.

This post seems to have decent info on what my situation is, but I don't quite see what path forward it suggests. Just seems like a list of pertinent facts: stackexchange why-adb-root-does-nothing (first google result)
[Magisk] cRaWnEr:
Hi. Huge thanks for this module. I was able to fix my Poco F1 to pass SafetyNET using its own fingerprint.

May I ask you, is it mandatory to keep the module activated in Magisk, or there is a way to "save" this fingerprint after applied? I tried disabling the module after changing the fingerprint, but cts failed, so I just re-enable it for now, but I was wondering if I can save this config without it just to prevent any issues with ROM updates or something like that should they appear.
[Magisk] SonOfSparda:
Will the module be able to override the fingerprint properties set through PRODUCT_PROPERTY_OVERRIDES, PRODUCT_BUILD_PROP_OVERRIDES set in lineage.mk AND property_override_dual set in init_chipset.cpp files? (Trying to compile LOS15.1, I'll skip setting these props in files if this module can't override..)
[Magisk] Sylently:
Moto Z2 Play 8.1.0 lineage 15.1

It's worked with fingerprint moto x4 9.0 PIE, thanks! :good: :silly:
[Magisk] ipdev:
Hi.

Those settings will not give you adb root.

They only enable (turn on) adb debugging and set adb to insecure.

Instead of activating the Developer options in the System(ROM) setting and turning on adb debugging. - Not having to acknowledge and allow adb access to a computer by accepting an adb key.

Traditionally user or release versions of a rom do not offer root (su) or adb root.

LineageOS I believe still does, outside to that, you will have to look into your device/ROM thread(s) to see if it is possible.

I haven't use adb root for awhile (SuperSU days.) normally I just use adb shell and grant permission in Magisk.

I'm not sure if there is a setting/permission that can be set to enable adb root by default.

Cheers. :cowboy:
[Magisk] Dizzy_trout:
Ah gotcha! I found something that might help, github pcboy adb-insecure-patcher, says it'll allow adb root. I'm not quite sure how to use it though, I think I have to run it on my phone as it's a .sh.

Another suggestion I've heard is that I can rewrite the sendevent command to not require su privileges, but I'm also not sure how to begin to do that.
[Magisk] Didgeridoohan:
Gorramit!

I seem to have messed up the boot logging when doing the final implementation. Unfortunately there's no info in the logs that could say what the problem is...

You could wait for the next release or grab a boot logcat together with the logs.

Can't promise that even that log will show anything though. There's been a few similar reports on a few GSI ROMs and I currently have no idea what the issue could be.
[Magisk] dukemagus:
At least the situation made you aware of a bug in the extension. It's a net positive.

After some research, I discovered magisk itself has a bug on v20.4 that was breaking the magisk hide for some apps (it's a bit more complicated, but that's not important right now). Ended up with a fork of the canary build just to fix the issue I was dealing with.
[Magisk] Didgeridoohan:
The module is using Magisk's systemless implementation to load new values for those props to memory. Without the module the original values will be loaded instead.

If you want to do the same edits without using Magisk's tools you'll have to go about it the old-fashioned way of editing build.prop manually. That would definitely have the potential of messing up your updates though...
[Magisk] Didgeridoohan:
Any regular prop values (such as you can find in build.prop, default.prop, etc) can be changed with Magisk's resetprop tool (which is what this module uses).
[Magisk] cRaWnEr:
Ok, many thabks for the clarification
[Magisk] Some_Random_Username:
And here they are:

OnePlus 7 GM1903: OnePlus/OnePlus7_EEA/OnePlus7:10/QKQ1.190716.003/2005132200:user/release-keys__2020-05-01

OnePlus 7 Pro GM1913: OnePlus/OnePlus7Pro_EEA/OnePlus7Pro:10/QKQ1.190716.003/2005132200:user/release-keys__2020-05-01

OnePlus 7T HD1903: OnePlus/OnePlus7T_EEA/OnePlus7T:10/QKQ1.190716.003/2005192100:user/release-keys__2020-05-01

OnePlus 7T Pro OnePlus/OnePlus7TPro_EEA/OnePlus7TPro:10/QKQ1.190716.003/2005192100:user/release-keys__2020-05-01
[Magisk] Didgeridoohan:
Hm... Need a small clarification. Here you post that IN2025 is OnePlus8Pro_IND, but in this previous post it is OnePlus8Pro and IN2021 is OnePlus8Pro_IND instead. Which is it?
[Magisk] Some_Random_Username:
Sorry about that, it was a bit late in my timezone when I posted those prints and I accidentally swapped IN2021 and IN2025.

IN2021 is OnePlus8Pro_IND while IN2025 is OnePlus8Pro.

Attached a document regarding OnePlus devices model numbers for future reference (Chinese devices run H2OS out of the box and don't have Gapps preinstalled)
[Magisk] Displax:
Pixel`s update

Pixel 2=google/walleye/walleye:10/QQ3A.200605.001/6392402:user/release-keys__2020-06-05
Pixel 2 XL=google/taimen/taimen:10/QQ3A.200605.001/6392402:user/release-keys__2020-06-05
Pixel 3=google/blueline/blueline:10/QQ3A.200605.001/6392402:user/release-keys__2020-06-05
Pixel 3 XL=google/crosshatch/crosshatch:10/QQ3A.200605.001/6392402:user/release-keys__2020-06-05
Pixel 3a=google/sargo/sargo:10/QQ3A.200605.002/6416773:user/release-keys__2020-06-05
Pixel 3a XL=google/bonito/bonito:10/QQ3A.200605.002/6416773:user/release-keys__2020-06-05
Pixel 4=google/flame/flame:10/QQ3A.200605.001/6392402:user/release-keys__2020-06-05
Pixel 4 XL=google/coral/coral:10/QQ3A.200605.001/6392402:user/release-keys__2020-06-05
[Magisk] thada2607:
Could anyone kindly contribute a fingerprint for Oneplus 7T Pro HD1910? I would be very appreciated.
[Magisk] vecino:
Google: wrong device

Hi there,

I have Mi 9SE (grus) and I am using Props Config 5.2.5. All is working perfect only Google says my device is "Mi 8" but is not true.

Can I fix it in any way?

Thanks
[Magisk] Didgeridoohan:
Did you at any point use a Mi 8 fingerprint? This can happen when using a fingerprint from another device...

I've never actually dug deeper into this, but you could try clearing data for Play Services.
[Magisk] vecino:
I have fingerprint for Grus - check my screen. I never changed FP - there was no reason. Do you think this is a ROM problem?

Edit: I tried delete data for Play Services - it did not help.
[Magisk] Some_Random_Username:
HD1910 has H2OS out of the box and doesn't have Gapps preinstalled, meaning it doesn't pass SafetyNet.

Should you still wish to get a fingerprint, you may download http://download.h2os.com/OnePlus7T ...1_OTA_011_all_2003162017_c2af040b1fbb4703.zip from OnePlus Chinese support website and look at metadata file present in META-INF -> com -> android
[Magisk] Didgeridoohan:
Yes, I saw that you are using a grus fingerprint. If you've never used another fingerprint there's nothing I can do... It's got nothing to do with this module, and I would guess that it is a ROM thing.

Edit: Well, there could be something... If it's a prop causing it you could of course change that with this module. Check by running this command:

getprop | grep "Mi 8"
[Magisk] thada2607:
Thank you, this fingerprint doesn't get rid of safety net does it.
[Magisk] ace_apr27:
I installed the module on my HD1913 but terminal emulator doesn't seem to be able to call it. How can I troubleshoot this?
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#props-not-found
[Magisk] crazyrexz:
is this module can bypass cts fail on unlocked bootloader redmi note 8 ?

i have installed but not executing yet, i have seen only redmi note 8T on option fingerprint via termux.
[Magisk] Didgeridoohan:
If MagiskHide is otherwise working and you are failing CTS because you are using a ROM/firmware that isn't certified by Google then: yes.

It's generally possible to use any fingerprint to pass CTS, but if you really want a Redmi Note 8 print you'll have to help me find one.
[Magisk] viande:
So this module has no link with the MagiskHide not working on certain apps recently ?
[Magisk] Didgeridoohan:
I would be extremely surprised if it did.

They're likely just using some of the known (and possibly unknown) ways of detecting Magisk. There are a few around. John's aware and if there's time and a way, he'll get it fixed eventually.
[Magisk] viande:
OK I see, thanks! I saw a workaround using a module-less version of Magisk, but giving up modules for an app is not really worth it.
[Magisk] nguye205:
I cant get my ctsprofile check to pass on my oneplus 8 pro IN2025. I selected the correct fingerprint but ctsprofile is still false.

Please help :(
[Magisk] Didgeridoohan:
Start by taking a look in the module docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Filo1995:
Update for Xiaomi Redmi K30 Pro (lmi)

ro.build.fingerprint : Redmi/lmi/lmi:10/QKQ1.191117.002/V11.0.22.0.QJKCNXM:user/release-keys

ro.build.version.security_patch : 2020-05-01
[Magisk] 25501317040:
Is it safe to use gpay after using this module
[Magisk] pndwal:
You may want to read these posts:

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/post81423159

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/post81501035 PW
[Magisk] sandaljrpit:
Hi...

I have a problem with Termux. When retrieving the certified stops working ( working. please wait... ) then I forcibly closed the termux and reboot my phone. I use a custom kernel on xiaomi mi4 LTE Rom miui v9.5.3 (by multirom.me).

CTS = false

Basicintegrity = false

I include the log & screenshot, If there is a desire to see. Thanks before

Edit ;

Re-enable magisk hide, CTS & basicintegrity = true
[Magisk] billhilt:
Id like to add a few lines to my build prop . Since its read only now with no way to change . Can anyone give my instructions on how this is done with this module. Im trying to get the wifi calling to work on my pixel 2 xl with visible. June update BTW Thanks for any guidance
[Magisk] Didgeridoohan:
Run the props command and pick the "Add/edit custom props" option. Follow the instructions to enter the props and values you want.

Also, note the following:

https://github.com/Magisk-Modules-R...etting-a-custom-prop-or-removing-a-prop-value
[Magisk] dmonium:
Please Update for Xiaomi Redmi Note 8 Pro - Android 10

ro.system.build.fingerprint=Redmi/begonia/begonia:10/QP1A.190711.020/20.6.4:user/release-keys

ro.build.version.security_patch=2020-05-01
[Magisk] Some_Random_Username:
[MENTION=4667597]Didgeridoohan[/MENTION] OnePlus decided to start rollout new builds for their 8-series based on 2020-05-01 patch a few days after I posted IN2021 and IN2025 prints extracted from OOS 10.5.9, here are the newest prints:

OnePlus 8 IN2011=OnePlus/OnePlus8_IND/OnePlus8:10/QKQ1.191222.002/2005301331:user/release-keys__2020-05-01

OnePlus 8 IN2013=OnePlus/OnePlus8_EEA/OnePlus8:10/QKQ1.191222.002/2005301331:user/release-keys__2020-05-01

OnePlus 8 IN2015=OnePlus/OnePlus8/OnePlus8:10/QKQ1.191222.002/2005301331:user/release-keys__2020-05-01

OnePlus 8 Pro IN2021=OnePlus/OnePlus8Pro_IND/OnePlus8Pro:10/QKQ1.191222.002/2005301332:user/release-keys__2020-05-01

OnePlus 8 Pro IN2023=OnePlus/OnePlus8Pro_EEA/OnePlus8Pro:10/QKQ1.191222.002/2005301332:user/release-keys__2020-05-01

OnePlus 8 Pro IN2025=OnePlus/OnePlus8Pro/OnePlus8Pro:10/QKQ1.191222.002/2005301332:user/release-keys__2020-05-01

I also realized I forgot to detail that the 7T Pro EEA print I mentioned at https://xdaforums.com/showpost.php?p=82718165&postcount=3498 is for HD1913 model
[Magisk] xdatin1:
How can I apply this module to work.

I installed module but ctsprofile is false.

I have Mi 9T pfone with LineageOS 17.1 installed (unofficial)

When i run props command i terminal i got message "No busybox installed" by I think I have busybox installed ::confused:

EDIT:

I did not have installed busybox.

After i install busybox everything work ok.

I choose Mi 9T Global fingerprint but after reboot ctsprofile is false again.

Is this because custom rom?
[Magisk] pndwal:
Is basicIntegrity True in Magisk manager? PW
[Magisk] zfk110:
Hi, I'm trying to change/hide magisk manager name to something else but it kept saying failed "Hide Magisk Manger Failed"
[Magisk] Didgeridoohan:
That's covered in the docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Didgeridoohan:
Not quite the correct place for that query, but take a look here:

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
[Magisk] xdatin1:
Yes
[Magisk] xdatin1:
Uncheck/check Magisk hide settings and now I have ctsprofile true ?
[Magisk] alantay11:
Just successfully installed this, ctsProfile has changed to true. However, the banking app I use still detects root even after clearing its data, setting magisk to core, disabling root etc. I realize that this problem is likely related to the safetynet 'upgrade' in March but does anyone know how to fix this?

If I'm in the wrong place please tell me.
[Magisk] Didgeridoohan:
The app detecting root has nothing to do with SafetyNet (since you're passing). Take a look here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] alantay11:
Thanks. Would specifying that the root detection happened without any app update narrow down the possibilities? It was working fine with only Magisk Hide even when SafetyNet was failed previously.
[Magisk] dlnraja:
Magisk saftery net doesn't works

There is a log as an attachment file
[Magisk] Didgeridoohan:
Not really... If it worked previously, but not anymore, that means something changed. Only you can know that that would be.

Best I can do is to provide the link I posted earlier. It contains most things you'll possibly need to hide root.