I also had to hide magisk apk and change icon as one of my banking aps was lloking for magisk app itself
Here's another which is more recent: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
Go to Settings, Apps and Uninstall that renamed/repackaged/'hidden' Magisk app.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.
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
/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
magisk resetprop ro.debuggable 1
If the adb connection from the computer was not previously authorized, you need to run insecure.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
Code:persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
/data/adb/modules/adbguard/module.prop
Code: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 runmagisk resetprop ro.debuggable 1
I wonder such simple module does already exist?
ro.adb.secure=0
ro.secure=0
ro.debuggable=1
adb-insecure.sh
#!/system/bin/sh
resetprop -n ro.adb.secure 0
resetprop -n ro.secure 0
resetprop -n ro.debuggable 1
/data/adb/post-fs-data.d/
so it runs in early boot.Need the corresponding security date also.POCO/surya_eea/surya:11/RKQ1.200826.002/V12.5.3.0.RJGEUXM:user/release-keys
![]()
Not silly.Hi there, maybe it is a silly question
I've installed LineageOS on my Poco F1, it is based on Android 11.
Official MIUI and so official fingerprints stops at Android 10.
Until now i'm using latest fingerprint (provided by myself lol) and everything works fine. I could continue using it without issue or should i change fingerprint to one with Android 11?
Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V12.0.3.0.QEJMIXM:user/release-keys
2020-12-01
Thanks @ipdev for the clarifying answer.Not silly.
Should be no issue using an Android 10 fingerprint with a custom rom that is a newer version of Android.
I use the last stock Android 6 fingerprint for Nexus 7 (2013) running Lineage 19 (Android 12).
When custom roms are built, they use the latest (last) official build fingerprint.
For Poco F1 that would be Android 10.
Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V12.0.3.0.QEJMIXM:user/release-keys
LineageOS official builds will not include 'tricks' to match the security date so you will need to adjust it to match.
2020-12-01
If you are building an unofficial Lineage rom, let me know.
There is a way to include the matching security date when you build the rom.
Hope it helps more than confuse.
Cheers.![]()
Xiaomi/platina/platina:10/QKQ1.190910.002/V11.0.2.0.QDTMIXM:user/release-keys
2020-04-01
Xiaomi
MI 8 Lite
POCO/surya_eea/surya:11/RKQ1.200826.002/V12.5.7.0.RJGEUXM:user/release-keys
2022-03-01
Xiaomi
M2007J20CG
Hello. I've updated (dirty) a Pixel 3a and 4a from LOS 18.1 to 19 this week.It depends how your SAR looks like. You might have /vendor or /system/vendor
but eventually one must be mounted to another, that both show the same content
You could check in your case if eg /vendor is empty and /system/vendor not or vice versa, or they show different content
But for MHCP it seems that you don't have /system/xbin (or it is empty) in which case MHCP should have been chosen bin, not xbin
Or regarding to both mounts, something is wrong with the mounting in Magisk
But ok, for now you have MHCP working - be aware that updating of the module might install it again to xbin