Anyone with stock ROMs, would you be able to get stock device fingerprint from your devices?
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Much appreciated.
Taken from my S7+ non rooted
~ $ getprop ro.build.fingerprint
samsung/gts7xlwifieea/gts7xlwifi:10/QP1A.190711.020/T970XXU1ATK3:user/release-keys
Here's mine (tab s7 regular wifi)
samsung/gts7lwifixx/gts7lwifi:10/QP1A.190711.020/T870XXU1ATK4:user/release-keys
I rooted before but flashed stock. I hope mine is still useful if not ignore
legokangpalla said:
Anyone with stock ROMs, would you be able to get stock device fingerprint from your devices?
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Much appreciated.
Click to expand...
Click to collapse
Try using my app VD INFOS, you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
Including fingerprint.
And then you can fix what needs to be fixed.
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com
Related
Hi,
I've been doing some interesting reverse engineering work and came across this Xposed module:
http://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2783480 to disable signature checking.
This is a an awesome module, but didn't quite do what I needed in that I wanted to have the system believe that my patched APK was 100% original. To this end I built an Xposed module to spoof the JAR verification at a very low level, which allows for all sorts of interesting possibilities.
This is a research tool and should be used accordingly, as with any such subversion of system behaviour, this is not something you want to leave enabled!
I've added a UI based on the same mechanism of the DisableSignatureCheck module to enable / disable the spoofing behaviour.
The module source can be found on my GitHub page:
https://github.com/sweetlilmre/JARVerificationSpoofer
Comments and criticism are welcome, I hope that someone finds this useful.
-(e)
Thanks I will look at this, sounds promising.
Hope you find it useful.
Where the apk. Or did i miss something
Source is on github.
Awesome work!
@sweetlilmre I am developer of DisableSignatureCheck (now XInstaller) and it is open source. Maybe you would like contribute this feature to this module also?
Sounds like a good idea. Where is the source?
https://github.com/pylerSM/XInstaller here
Thanks. I will try to send a pull request soon.
Isn't it the same as the first patch in Lucky Patcher? It would be awesome to implement all its patches as xposed modules.
Thanks for the pull, it's now integrated in the Xinstaller 3.0 modul. ?
CHEF-KOCH said:
Thanks for the pull, it's now integrated in the Xinstaller 3.0 modul. ?
Click to expand...
Click to collapse
Hi,
I see that this has been added to XInstaller, but as "afterHookedMethod", not "beforeHookedMethod".
The original method will throw a "invalidDigest" exception, if executed i.e. not desired behaviour.
I have submitted a pull request to fix this.
-(e)
This overlay APK is "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Bond power profile.
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your BND over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that doesn't belong no more in /system
I have XYZ device with ZYX firmware can I use it?
As long as you're on a BND-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have BND, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Overlay configs (aka "what does dis do, ser tell pl0x"):
Allows all rotations;
Configs autobrightness levels;
Configs autobrightness Lcd values;
Configs BLE;
Sets Doze Component;
Sets Doze After screen off;
Configs autopowermodes (doze related);
Configs power management on:
screen off due to proximity sensor interaction;
decouple on suspend state;
Configs brightness doze value;
Configs Intrusive led;
Configs dual band wifi support (where available);
Configs hotswap (where available);
Configs Color Transform on HWC;
Configs VoLTE available (even tho it needs support on GSI side);
Configs WFC over IMS;
Configs wifi background scanning support.
Installation Instructions
Download the overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-BND.apk
It's here, it's finally here
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Bond power profile.
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your BND over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that doesn't belong no more in /system
I have XYZ device with ZYX firmware can I use it?
As long as you're on a BND-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have BND, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-BND.apk
Click to expand...
Click to collapse
Im a lil bit confused , i have the honor 7x (BND-AL10) and i just wanna know what this will exactly do
Martobhai said:
Im a lil bit confused , i have the honor 7x (BND-AL10) and i just wanna know what this will exactly do
Click to expand...
Click to collapse
Do you mind not quoting the entire original post? Makes for a very long post and makes your problem hard to read.
This enables battery usage info and some device-specific features.
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .:
Click to expand...
Click to collapse
Hi mate. Just a request, can you make also for vicky (huawei p10+)? Thank you in advance
v0ne said:
Hi mate. Just a request, can you make also for vicky (huawei p10+)? Thank you in advance
Click to expand...
Click to collapse
Please join the telegram group in the my signature for that.
I'd need a couple of things from VKY.
Thank you.
UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD
#freedil3mm4
#freedil3mm4
@Dil3mm4 Hi, could you provide an overlay like this for moto e5? If you need files, I can send them.
Do I need this if I use phu truss on aosp? Thx
Hey man, I'd like to have a better experience on Descendant on my Honor 6X, in fact at the moment i can't see battery stats, per-app usage, ecc. - I'd like to know if you're still providing overlays for specific Huawei devices on Telegram group. Last request here in the thread is dated 2018 by what I can see, so... Thanks in advance and keep on.
optionalmgrr.la said:
Do I need this if I use phu truss on aosp? Thx
Click to expand...
Click to collapse
hi anyone?
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Victoria power profile and it's compatible with P!
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your VTR over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a VTR-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have VTR, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay [/URL]
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-VTR.apk
Thank you very much!
It seems like there is already a huawei vtr overlay included in phh's aosp pie. Can you tell if there are any benefits in applying this on top?
Of
Sent from my LDN-LX2 using XDA Labs
nabihaharyono said:
Of
Click to expand...
Click to collapse
same
Hi all,
I'm working on a port of Android 11 (AOSP) for the OnePlus 5. The ROM works pretty well, but I'm having issues with the Google Apps. In particular, the Google Wellbeing is not working and it is crashing with the log attached when started.
I've already spent a lot of hours trying to understand why: it works fine on LineageOS but there is no particular commit for Wellbeing, and everything seems the same from a permissions point of view.
Is this the right place to ask for help?
Thanks!
It doesn't seem to be improving your wellbeing...
blackhawk said:
It doesn't seem to be improving your wellbeing...
Click to expand...
Click to collapse
It does not
Hi, I found and fixed the issue. This is the fix:
SettingsExtra: do not declare REQUEST_LISTENING as protected · roberto-sartori-gl/[email protected]
This fix Wellbeing not working on Android 11. SettingsExtra does not need this, it was a leftover from development. Signed-off-by: Roberto Sartori <[email protected]>
github.com
I didn't think a manifest from an application could break stuff in a different app, however it does (this is a system app). I didn't need that declaration, so I just removed it
robertogl said:
Hi, I found and fixed the issue. This is the fix:
SettingsExtra: do not declare REQUEST_LISTENING as protected · roberto-sartori-gl/[email protected]
This fix Wellbeing not working on Android 11. SettingsExtra does not need this, it was a leftover from development. Signed-off-by: Roberto Sartori <[email protected]>
github.com
I didn't think a manifest from an application could break stuff in a different app, however it does (this is a system app). I didn't need that declaration, so I just removed it
Click to expand...
Click to collapse
It was one of the first apps I deep sixed on my 10+... fixed
Full Guide and Download, on GitHub, HERE.
This is for a ROOTED version of Windows Subsystem For Android with the Google Play Store, Services and framework installed. Essentially giving you a rooted android device inside you Desktop. Great for DevOps, CyberSec & DefEng. (Defense Engineering)
Key Points:
-For best results fork and clone.
-SHOULD also work by simply downloading.
-Uses Magisk by @topjohnwu for root.
-Uses The Open GApps Project for playstore.
-Your system MUST support Hyper-V.
-Simple Installation process.
-Working ADB.
-Open-Source (yes, if you want to help, please do - just go check out the Github.
TO-DO:
-System UI
-Allow for replicating Device-Specific Set-Ups (I.e, Mocking a particular devices' security framework, for instance, emulating KNOX, Google FRP, QTI, Etc.)
-VPN Fix
-Cellular network (for this who want to test their apps on live networks)
- Make it self-updating.
Please Post any issues on the github or here and be as detailed as possible and include screenshots. May take some time for a response but will do my best.
Good luck -
-k0mrad3
Never mind, my bad
Hack & install method is so dirty
Repo removed by Github. Might want to find another host