yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Working for me with no problem, on first attempt:

- Latest Magisk Alpha 23016 (could be Canary 23016 as well)

- Zygisk enabled, DenyList properly configured, IndOASIS added to DenyList

- However, Enforce DenyList is disabled since I'm using Shamiko (Magisk module)

- Zygisk-LSPosed (Magisk module) installed and Hide My Apps = HMA (LSPosed module) installed

- In HMA I have a template to hide Magisk app and all the LSposed manager apps

- In HMA, that template applied to IndOASIS to hide the given apps from IndOASIS

- rebooted

- only then starting IndOASIS for the first time

This is s heavy artillery and maybe not all that stuff (Shaniko, hiding in HMA all those mngr apps) are really needed, but that's my working environment and a way I hide the root from all suspicious apps

Additional info: Xiaomi, A11

Since my ROM is certified for Google, I don't need to spoof the fingerprints hence I don't need to use MHPC (the module as in this thread)
[Magisk] AserLaser:
Yes it didnt attach the files. Now they should be there. Couldnt find "propsconf_install.log" and "propsconf_latefile.log" are they in cach aswell?
[Magisk] Didgeridoohan:
Any reason why you're using an almost month old version (that's why you're not seeing some of the logs)? Could you try the current version instead? And provided the new logs of it still doesn't work...
[Magisk] AserLaser:
Oh sorry. Yes there is a reason i tried the newest one and it didnt work. So i thought may an older one works. Same issue. Can provide the New logs aswell of course.
[Magisk] Didgeridoohan:
Yes please, particularly the propsconf_install.log would be interesting to see.
[Magisk] AserLaser:
New one
[Magisk] Didgeridoohan:
Thank you. The issue is that Magisk is having problems mounting the script to /system/xbin. Why, is the important question...

I'll investigate more when I have an opportunity. I'll get back to you...
[Magisk] AserLaser:
Okay no hurry. Thanks so far for your patience and help :)
[Magisk] Didgeridoohan:
Ok... Let's try to figure this out... The installation script detects that you have an xbin folder, but there's an error when Magisk tries to mount the module xbin folder over the system one, because it can't find it (or something like that). :confused:

Could you run the following command in a terminal emulator and return with the output:

su -c find / -name 'xbin' 2>/dev/null

It'll look like nothing is happening for a few moments, but just wait and it'll eventually finish.
[Magisk] Kapiljhajhria:
add fingerprnt for whyred

can you please add fingerprint for redmi note 5 pro india, redmi note 5 global, redmi note 5 chinese.

all three are whyred.

this is the fingerprint which i used on ROM which was failing safety net and it now passes safety net. So i know it works.

ro.build.fingerprint

xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.6.0.OEIMIFA:user/release-keys

please add it to your database.
[Magisk] AserLaser:
okay because I don't know much about terminal commands I type just all what happened
[Magisk] Didgeridoohan:
Ok. You're having a Magisk issue rather than a module issue... The system mirror isn't mounted properly.

Here's a few things to try:

Check it installation of other modules work. Modules that also mount stuff to system. Good ones to test would be Busybox, Greenify, etc. Check those by seeing if the busybox command works or if Greenify is a system app. The magisk_debug.log (it's in /data/adb) would be interesting to see after you've installed those modules and tested if they work.

Revert to Magisk v16.0 and see if the problem persists.
[Magisk] AserLaser:
Okay, i've installed them, and am not quite sure how to test if they work :confused: still, i think they dont work. I haven't the information of priviled greenify in its options. AS attachment the Log. Some days ago i've tested it and it didnt work. But I will try again. Ah and the other modules cant access to the folders neither (its empty?). Has it somethi g to do with this in the Magisk.log? 05-21 15:35:50.354 234 234 E Magisk : mount /dev/block/platform/msm_sdcc.1/by-name/system->/sbin/.core/mirror/system failed with 16: Device or resource busy, and if yes some idea how to fix it? :confused:
[Magisk] AserLaser:
V16 same issue
[Magisk] AserLaser:
Okay finally I fixed it. Clean Installs of the Rom didn't do I, had to flash stock and make a clean install afterwards and now it works. Don't know why but doesn't matter :D
[Magisk] Didgeridoohan:
[MENTION=4048340]Kapiljhajhria[/MENTION] I'll add it. When I have time...
[Magisk] Jvirg:
i have a samsung galaxy sm-g530w and i tried one of the samsung fingerprints and nothing. My phone booted up as normal. I'm using an unofficial lineage 15.1 right now and i know that previously with 14.1 it passed safetynet and showed certified in google play. I can't seem to figure out how to extract the fingerprint from that build and use it.
[Magisk] Didgeridoohan:
There's been other reports of failure to pass the CTS check on unofficial Lineage ROMs. I'm not sure why... Do you have a link to the ROM in question?

And about getting the fingerprint from the previous working ROM, check the documentation for tips on that. There's an index in the OP.

Edit: Oh yeah... And don't forget to provide the logs mentioned in the OP (under "Issues") when reporting about problems.
[Magisk] manuele16:
Hi guys, I installed magisk 16.4 on HW P9 + on first boot Safety Net ok, cts and basic is true, but after a few hours, they went wrong. Only Safety net is OK.

I tried to change the fingerprint with the Props module, but it remains false.
[Magisk] Didgeridoohan:
You're in the wrong thread...

Post this, with your magisk_debug.log in the General Support thread.
[Magisk] russel5:
2All who had a problem with lineage-15.1 and ctsprofile.

First, setup this module, ie choose your fingerprint, improve hiding, etc. Do not reboot!

Last, go to /magisk/.core/service.d/ and move "propsconf_late" to /magisk/.core/post-fs-data.d/

Reboot.

Profit.
[Magisk] jcmm11:
If I run getprop I show 3 fingerprints. Doing a grep on "keys" (because it shows a few more items) I get

[init.svc.keystore]: [running]
[ro.bootimage.build.fingerprint]: [google/bullhead/bullhead:8.1.0/OPM6.171019.030.E1/4805388:user/release-keys]
[ro.build.description]: [bullhead-user 8.1.0 OPM6.171019.030.E1 4805388 release-keys]
[ro.build.display.id]: [validus_bullhead-userdebug 8.1.0 OPM6.171019.030.E1 6988b98924 release-keys]
[ro.build.fingerprint]: [google/bullhead/bullhead:8.1.0/OPM6.171019.030.E1/4805388:user/release-keys]
[ro.build.tags]: [release-keys]
[ro.vendor.build.fingerprint]: [google/bullhead/bullhead:8.1.0/OPM6.171019.030.E1/4805388:user/release-keys]

so I show 3 fingerprints (which in my case are all the same). The only way to know for sure is to have someone with a problem and a vendor partition check.

I suspect that checks are only looking at ro.build.fingerprint
[Magisk] Didgeridoohan:
As far as I know, the check is only for ro.build.fingerprint. But, the module actually already changes all three of those fingerprints you have, just in case.
[Magisk] inigoml:
Hi [MENTION=4667597]Didgeridoohan[/MENTION]!

Another fingerprint already tested (in my device) for Xiaomi Mi Mix 2 (without S):

Xiaomi/chiron/chiron:8.0.0/OPR1.170623.027/V9.5.4.0.ODEMIFA:user/release-keys

It's from previous Xiaomi stable release because newest one is 9.6.1.0. I will try to get from original ROM...

Got it unpacking ROM

ro.build.fingerprint=Xiaomi/chiron/chiron:8.0.0/OPR1.170623.027/V9.6.1.0.ODEMIFD:user/release-keys
[Magisk] Samrat Sengupta:
Hi Didgeridoohan,

I managed to get the fingerprint with some research, I hope this would work, could you please add to the prop config list. Thanks in advance.

post-build=Z00T-user 5.0.2 LRX22G JP_user_1.16.40.1338_20160324 release-keys
[Magisk] Samrat Sengupta:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

Please update if this has been added. Thanks.
[Magisk] Didgeridoohan:
Right... I forgot to reply to you about that. That's unfortunately not the build fingerprint, it's the build description. It has almost all the information I need to piece together the fingerprint, except the ro.product.device property. If it had been any other device than Asus it likely wouldn't have mattered, but with Asus I can't guess that prop from the build description.

To clarify:

What I need is the prop ro.build.fingerprint. You've given me ro.build.description.

If you can get me that I'll add it to the list as soon as I have an opportunity.
[Magisk] Samrat Sengupta:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

asus/WW_Z00T/ASUS_Z00T_63:6.0.1/MMB29P/JP_user_21.40.1220.2170_20170719:user/release-keys

Please check if this works out, thanks for being so informative.
[Magisk] Didgeridoohan:
That looks right. I'll test it out and add it to the list when time permits.
[Magisk] Samrat Sengupta:
Please keep me updated and thanks for being such cooperative and making a noob like me a little knowledgeable.:good:
[Magisk] VincentJoshuaET:
Can you set every property regarding the build description and fingerprint? From the previous posts, did I understand correctly that some props like the ones from vendor aren't changed? Maybe you can change them too (if they exist), just for consistency. And maybe Google will check the others too in the future (but right now I'm just being OC about it :3). Thanks!
[Magisk] Didgeridoohan:
The module already changes the most common fingerprint props:

ro.build.fingerprint

ro.bootimage.build.fingerprint

ro.vendor.build.fingerprint

I have a plan to also let the module change ro.build.description, but for now that is not necessary for the device to pass the CTS test. I might add it at some point, but it isn't likely to happen unless it turns out to be necessary after some change from Google.
[Magisk] VincentJoshuaET:
I just tried the latest Global Stable 9.6.3.0 for Xiaomi Redmi Note 5. Can't pass ctsProfile. Reverted to working stock. Not sure if the fingerprint is already added to the index (I made a fingerprint list file). Just fyi. Not sure if it's a problem on my end or Xiaomi's, global stable ROMs are supposed to pass SafetyNet.
[Magisk] teddy0209:
Global Stable should pass SN as it is...

How did you flash it? What was your previous rom?
[Magisk] VincentJoshuaET:
I'm running Pixel Experience 8.1.0 right now. The stock 9.5.11.0 fingerprint included in this ROM works. But the latest Global Stable 9.6.3.0 doesn't. Basic integrity passes on both.
[Magisk] deepu458:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

I am really thankful for this mod. I already got benefited from this mod once on my tab for passing CTS profile. But now on my Phone Essential Ph-1 currently with custom OS AICP(based of Lineage) is having this issue and i tried changing the fingerprint and all the relative parameters to match with the current stock fingerprint (which is Android Pie 9)& made sure all the other props that's needed are all good. But still no luck. I tried contacting ROM OP, but he said he couldn't figure it out what's the cause.

Before this hassle of Google api change it used to work. and then it stopped and never working with latest

So is there any other things i can do or any other params thts needed to pass CTS.
[Magisk] Didgeridoohan:
Are you passing basicIntegrity?

Logs might show something...
[Magisk] deepu458:
Thanks for looking into this issue.

Yes it does pass basic integrity. Attached are the logs.
[Magisk] deepu458:
[MENTION=4667597]Didgeridoohan[/MENTION]

After looking at the logs one thing I noticed was the script can't see the build.prop file.

As the file is located in /system/build.prop but the script is trying to look under /system/system/build.prop. is this going to be any issue.

But the hide props are all properly configured.
[Magisk] Didgeridoohan:
Saw that too, but it shouldn't have any kind of consequence on the issue at hand.

I did a quick test with the fingerprints from your logs (both the 8.1.0 and 9) and couldn't get either of them to pass the ctsProfile on my test device. :confused: I've actually not yet been able to get any Android Pie fingerprint to pass when testing... Not even the stock Pixel prints. :eek: Unfortunately I have very limited spare time to experiment at the moment.

I'm currently working on an update for the module, so I'll make sure to fix the build.prop issue as well (I actually already have on my side). Hoping to get the update out sometime next week, because after that I will be swamped with real life stuff for a long, long time.
[Magisk] jcmm11:
You're confused. THIS is real life. What you think is real life is just illusion. Take the red pill and get your priorities in order ???
[Magisk] rick james b1tch:
Hi i have had magisk all set up on my s9+ running 10 for about a year. For some reason it no longer passes safetynet check

Basic intergrity is tick

Ctsprofile is not

Eval type is now hardware

I have universal safetynet fix 2.0 and magiskhide props config 6.1.2 installed

I have tried installing the New magisk hide toolkit by teamfiles (lsposed, riru and the xprivacy app) this did get eval type showing as basic but didnt fix the cts profile. I have now removed these profiles.

Does anyone know of a way to fix this
[Magisk] zgfg:
What Magisk version are you using (that's crucial)?

If still on the old Stable v23, you must be using USNF (Universal SafetyNet Fix) 2.1.3, NOT 2.2.x

Also, LSposed, Riru, XPrivcyLua, whatever, will not help you for SafetyNet
[Magisk] rick james b1tch:
Both my magisk and app are 23.0 latest version however i only updated to them due to safetyNet failing. I think google has added s9+ to hardware check recently.

Thanks i reinstalled Riru and updated to USNF 2.1.3 and now passing SafetyNet
[Magisk] ipdev:
Took me a little bit to figure this one out. 🙃

Long story short.

Normally I default to using the ro.bootimage.build.fingerprint.

This time it was the wrong print to use. ;)

Motorola moto g(7) plus (from custom list)

motorola/lake_retail/lake:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

SafetyNet

Basic integrity Pass

CTS profile match Fail​

This time ro.build.fingerprint was different and the certified print.

Motorola moto g(7) plus (from custom list)

motorola/lake_n/lake_n:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

SafetyNet

Basic integrity Pass

CTS profile match Pass​

Stock fingerprints.

Note: The ro.build.fingerprint was not listed in the prop files dumped from the build.

As far as I can tell, you can only get the value if props are dumped from a running device.

ro.bootimage.build.fingerprint=motorola/lake_retail/lake:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.build.fingerprint=motorola/lake_n/lake_n:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.build.thumbprint=10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.build.version.preview_sdk_fingerprint=REL

ro.odm.build.fingerprint=motorola/lake_retail/lake:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.system.build.fingerprint=motorola/lake_retail/lake:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.vendor.build.fingerprint=motorola/lake_retail/lake:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

When run with this module, it will set all the fingerprints to the same.

Note: This does not seem to be an issue.

ro.bootimage.build.fingerprint=motorola/lake_n/lake_n:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.build.fingerprint=motorola/lake_n/lake_n:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.build.thumbprint=10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.build.version.preview_sdk_fingerprint=REL

ro.odm.build.fingerprint=motorola/lake_n/lake_n:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.system.build.fingerprint=motorola/lake_n/lake_n:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

ro.vendor.build.fingerprint=motorola/lake_n/lake_n:10/QPWS30.61-21-18-7-12/b1002:user/release-keys

Hope this helps others that are trying to find fingerprints to add to the list. :D

So here it is.

Motorola G7 Plus

lake or lake_n (Depending on the prop, device is called both.)

Also called lake_retail in some props.​

Model

moto g7 plus

Model Number

XT1965-T

There is no 'XT' prop value that I could find, only shows under one of the about screens in the settings menu.

Edit: Found it.

ro.boot.hardware.sku=XT1965-T

Cheers all. :cowboy:
[Magisk] ecvarts:
Do modules work with last versions of Magisk? I flashed it via recovery but I still can't see how to install or use modules in Magisk manager... Just like the hide list it seems gone? Can anyone please clarify?
[Magisk] zgfg:
Modules must be usually installed through Magisk app, not through TWRP (although some modules can still be installed through TWRP)

In the Magisk app, open Modules and on top you have BIG BUTTON: Install from local storge - then navigate to the downloaded zip file and install

However, TJW discontinued support for Modules store. Instead, google for:

Github Fox Magisk Module Manager (Fox Mmm)

Install that app, grant it root and voilla. You will have access to their new Modules store. Read more about on their Github page
[Magisk] ecvarts:
Ah! A straight answer finally. Thank you so much for this!

Somehow I had managed to make hiding work by installing an older version of Magisk manager (7.x) on my older Redmi Note 5 pro, but I've been trying the same on this new Redmi 9 to no avail.

It's confusing because everyone seems to be using the latest version of Magisk even if support for the hide list and modules has been really dropped by the author. I couldn't figure how everyone is making use of this anymore other than for just rooting.

So there's a different manager app that helps at least with the modules. Hopefully can keep a list of apps to be hidden from too. That explains it all, but I swear I haven't found a reference to this app in the last one or so week I've been browsing the forum.

Well, thanks again. I'll give this a try now.

Edit: LOL as soon as I reinstalled the module in Fox Mmm and rebooted, the stock rom was offering me official updates again, which never did since I unlocked the boot loader. However it still didn't pass CTS. I'll try changing the fingerprint now through props command.
[Magisk] ecvarts:
I set the fingerprint for the only Redmi 9 available, the China version. But after a reboot it still won't pass CTS. So I enabled the rest of things under device emulation and I got some sort of bootloop that would first appear that is booting then reboot into the recovery. Wiping dalvik and cache fixed everything.

Is it possible to pass CTS on Xiaomi Redmi 9 global?
[Magisk] zgfg:
There is another thtead here on XDA, Magisk General - questions like that have been discussed there

In short:

- Supposing you want to use the latest Canary 23016

Make sure you use both the Magisk app and Magisk of the same version, not some old Magisk app/mngr and new Magisk (flashed) or vice versa

- In Magisk (Canary) app, Settings page, enable Zygisk and reboot

- Again in Settings, enable Enforce DenyList

- Right below, open Configure DenyList.

Enable Show System apps.

Find Google Play Services and checkmark com.google.android.gms and com.google.android.gms.unstable

Reboot

If on stock you should not need (not sure for MIUI CN stock 12.5+) to spoof fingerprints (this MHPC module) but you will most likely need USNF 2.2.1 module (another thread) to pass SaferyNet

Since SN checker is removed from the new Magisk (Canary) app, download from PlayStore YASNAC (Yet Another SafetyNet Attestation Checker)
[Magisk] ecvarts:
Thank you for your support and detailed instructions (y)
[Magisk] piyush_nagpal:
POCO X3 Pro India

Can you add Poco X3 Pro India to fingerprint list?

ro.product.manufacturer = Xiaomi

ro.product.model = M2102J20SI

ro.build.fingerprint = POCO/bhima_in/bhima:11/RKQ1.200826.002/V12.5.5.0.RJUINXM:user/release-keys

ro.build.version.security_patch = 2021-11-01

Android Version - 11
[Magisk] void0error:
I tried like you did. Still IndOASIS finding that its rooted. :/
[Magisk] lukjod:
I also had to hide magisk apk and change icon as one of my banking aps was lloking for magisk app itself
[Magisk] lukjod:
View attachment 5505257
[Magisk] Some_Random_Username:
Hi folks, below are fingerprints for OnePlus devices, mind some supersede those I posted last month.

As always, OnePlus/OnePlus7/ fingerprint is for GM1901 and GM1905 / OnePlus/OnePlus7Pro/ fingerprint is for GM1911 and GM1917 / OnePlus/OnePlus7T/ fingerprint is for HD1901 and HD1905 / OnePlus/OnePlus7TPro/ fingerprint is for HD1911 and HD1917.

Spoiler content hidden.

Here's also an Android 11 fingerprint for the 6T T-Mobile:

OnePlus/OnePlus6TSingle/OnePlus6TSingle:11/RKQ1.201217.002/2111231412:user/release-keys__2021-11-01
[Magisk] kjpern:
hi, is this compatible with realme GT 5G?
[Magisk] shi-no_tenshi:
Here's an Android 11 fingerprint for the Poco M3 Pro 5G Global Version:

Redmi/camellia/camellia:11/RP1A.200720.011/V12.5.2.0.RKSMIXM:user/release-keys__2021-09-01
[Magisk] shi-no_tenshi:
Here's another which is more recent:

Poco M3 Pro 5G Global Version (Android 11)

Redmi/camellia/camellia:11/RP1A.200720.011/V12.5.3.0.RKSMIXM:user/release-keys__2021-12-01
[Magisk] Demon27:
I messed up and can't figure out how to fix it. I have Canary 23016 installed on my P6P and went into the settings and selected "Hide Magisk app". I renamed the app that was working and a second Magisk icon appeared. I open that one and it only gives me an option to reinstall Magisk and boot img. The old renamed icon that was working just keeps force closing and won't open when I select it.
[Magisk] zgfg:
Go to Settings, Apps and Uninstall that renamed/repackaged/'hidden' Magisk app.

And install the Magisk app again

You will not loose Magisk, modules, root grants, etc
[Magisk] pessip:
Mi 11 lite 5g EEA (A11)

Xiaomi/renoir_eea/renoir:11/RKQ1.201112.002/V12.5.6.0.RKIEUXM:user/release-keys__2021-10-01

ro.product.manufacturer Xiaomi

ro.product.model M2101K9G
[Magisk] Displax:
Pixel`s update

Pixel 3a=google/sargo/sargo:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 3a XL=google/bonito/bonito:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 4=google/flame/flame:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 4 XL=google/coral/coral:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 4a=google/sunfish/sunfish:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 4a (5G)=google/bramble/bramble:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 5=google/redfin/redfin:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 5a=google/barbet/barbet:12/SQ1A.220105.002/7961164:user/release-keys__2022-01-05
Pixel 6=google/oriole/oriole:12/SQ1D.220105.007/8030436:user/release-keys__2022-01-05
Pixel 6 Pro=google/raven/raven:12/SQ1D.220105.007/8030436:user/release-keys__2022-01-05

Xiaomi Mi A3 EU

Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.15.0.RFQEUXM:user/release-keys__2021-12-01

Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.17.0.RFQMIXM:user/release-keys__2021-12-01
[Magisk] MrHomebrew:
Option 9 and 10 are disabled when testing a custom fingerprint. Disabled as in the option to even enable them is gone and they are not there for selection.

I need option 10 to properly check the device keys I have been obtaining. Is there any way to allow this option with custom profile?

View attachment 5510959
[Magisk] zgfg:
Xiaomi 11 Lite 5G NE (aka Lisa)

Android 11

MIUI 12.5.8 EEA

ro.product.manufacturer=Xiaomi

ro.product.model=2109119DG

ro.build.version.security_patch=2021-12-01

ro.build.fingerprint=Xiaomi/lisa_eea/lisa:11/RKQ1.210503.001/V12.5.8.0.RKOEUXM:user/release-keys
[Magisk] alecxs:
Q: What would be the minimal module structure for enable usb-debugging systemless-ly from TWRP without installing MagiskHide Props Config module?

(reasons: broken screen, boot-looping devices, ...)

I have something like this in mind

/data/adb/modules/adbguard/system.prop

persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

/data/adb/modules/adbguard/module.prop

id=adbguard
name=adb guard
version=0.1.0
versionCode=010

but these properties do not work on some devices, so maybe it's more universal way to run magisk resetprop ro.debuggable 1

I wonder such simple module does already exist?