Wechat Share Editor is a module for Wechat that allows you to change the sharing content or even create a custom share in Wechat. This includes share link, share logo link, share title and others...
Features
Change the Sharing Content of Wechat.
Requirements
Your phone must be rooted
Xposed framework must be installed first repo.xposed.info/module/de.robv.android.xposed.installer
Wechat Required
Instructions
Install the module
Run Xposed Installer and enable the module Wechat Share Editor
Reboot the phone
Open the module in Launcher or Xposed, and set up the content you want to share.
Open Wechat to share someone else’s Moment, and check the result
Permissions
network
Limitations & supported devices
I developed this module based on Wechat 5.3 source code and tested only on my RedMi device with Wechat Version 4.51 and 5.3. I expect it to work also on Wechat 4.0-latest.
Credits
I used XLED’s SettingsHelper class, hope you don’t mind.
Supports & troubleshooting
If you want me to add support for other Wechat version, please send me the following:
Xposed log file
Your device model
Android, ROM, Wechat version
Source code
You can find source code for this module from github.com/diwulechao/WechatShareEditor
hi, can you be specify more or provide a short video clip for some intro about it? im still having some confusing about this...
Sent from my GT-I9300 using Tapatalk
i love this apps.. can you update it for latest wechat apps?? tq
Sent from my GT-I9100G
Google introduced new SafetyNet API for app developers to check "device compatibility". Basically, if your device is rooted/modified, this check will always return "false" and then app would disable some of its features, if not all. This module changes this device compatibility check and now it always returns "true" so app "thinks" it runs on unmodified, unrooted Android device and all features are available.
Download:
http://repo.xposed.info/module/com.pyler.nodevicecheck
Tested, does not work.
Thread closed and link removed per OP's request.
Hi!
This module may be mainly interesting for developers. This module alone does nothing if not properly used together or within another app. Only use it if you know what you are doing.
Overview:
I created a Xposed module which overrides the Access Rule Checks within the SIMalliance Open Mobile API. These checks normally determine which app is allowed to access a SIM-card based Secure Element (SE) and which is not. Normally within the Secure Element (SIM card) there exists a special "Access Rule File" (also called "ARF") or a special card applet called "Access Rule Application Master" (also called "ARA-M") which has the AID A00000015141434C00) and (basically) contains application signatures and according access rules. So the maintainer of the Secure Element can define (and also update) the access rules with these mechanisms: which app is allowed to access the SE and which not. (see reference [1] for details below).
So while the access rules are securely stored in the hardware module (SE) the enforcement of these rules is done in software (within the Open Mobile "SmartcardService.apk"). And this is where this Xposed module hooks into. By using this module (or by integrating it into your app) you may access the SIM-card-based Secure Element with your app, even if the access rules within the SE would not allow it.
Here's the code:
https://github.com/johnzweng/XposedOMAPIOverrideSEAccessRules
This module does not globally disable the access rule checks but instead only grants full access to a single package name (app) which you manually have to define in code as TARGET_APPLICATION_PACKAGE_NAME.
More details and background story:
A few months ago the banks here in Austria started to roll out NFC-based tap'n'pay solutions which allow you to pay with your Android smartphone worldwide at every NFC-capable payment terminal. In contrast to Android Pay this is not a cloud-based software solution (using Host Card Emulation) but instead really uses a hardware-based secure element (like the chips used within EMV (chip'n'pin) plastic NFC banking cards). Austrian Banks decided to use Secure Elements located within the SIM-card (which is basically the same technology as your banking-card chip) so they don't need cooperations with all the phone manufacturers (and also not with Google), but only with the three mobile network operators (MNOs) here in Austria (which control all the SIM cards).
Unfortunately Google has not included an API in current Android which allows accessing SIM-card-based Secure Elements from an app (I guess they don't want banks and MNOs to develop their own independent payment solutions but instead want to push Android Pay). For this reason one of the largest smartcard manufacturers (Giesecke & Devrient - G&D) started to work on a third-party system API which is nowadays known as SIMalliance OpenMobile API (OMAPI). The SIMalliance is a group of industry players which want to push the use of Secure Elements in mobile phones. See also: Members of SIMalliance.
As this API is not part of official Android API the phone manufacturers (OEMs) have to include this API additionally on the phones. A lot of manufacturers do this already. You can check on your phone if this 3rd-party API exists by looking for these files:
/system/etc/permissions/org.simalliance.openmobileapi.xml
/system/framework/org.simalliance.openmobileapi.jar
/system/priv-app/SmartcardService/ (which hosts "SmartcardService.apk")
(and optionally in newer versions: /system/priv-app/UiccTerminal/)
As Google currently doesn't support this type of access to the SIM-card Secure Element you will not find this API on the Nexus phones. One exception was the Nexus 6 running Lollipop where Google included the SIMalliance Open Mobile API because they supported the Softcard (formerly Isis Mobile) wallet. After Google has acquired Softcard in 2015 they removed again the OpenMobile API from Nexus 6 in Android 6.
As I personally used a LG Nexus 5 and now use the Motorola Nexus 6 I started to work on integrating the Open Mobile API myself (which should be possible now on every phone since Android Lollipop (API level 21) as the TelephonyManager system class has got a few interesting new methods including one for sending APDUs over a logical channel to the SIM card: iccOpenLogicalChannel(String AID). As every phone running Android 5 or newer must implement this API you now can get the OMAPI working on every phone running Android 5 or newer (with minor restrictions). (Also the phone needs to have a special hardware wiring between the SIM card and the NFC chip - see "Single Wire Protocol" for details - to get a NFC payment working). But this is a different story which doesn't belong in this thread. For the interested, look at my Github repo which contains a fork of OMAPI working on unmodified Android versions (and two pre-built releases for OMAPI 2.05 and OMAPI 3.0 under the "releases" section - including a short How-To). This worked for me on a Nexus 5 and a Nexus 6.
But back to this topic:
After I had worked out the integration of OMAPI into Android 6.0.1 I finally was able to use tap'n'pay with my Nexus 6 using the banking card within my SIM card Secure Element. But as I am curious I was also interested in exploring my banking-card within the SIM Secure Element using a self-written app. This was when I realized that there is some kind of access control within the Secure Element which blocks my own test-app but not the app of my bank. (See reference [1] for details on these access rules.) To circumvent this I wrote this Xposed module and voilá, now we also have the possibility to talk with the Secure Element over OMAPI.
Final notes:
This Xposed module will only work if your device has the SIMalliance Open Mobile API (OMAPI) installed
This Xposed module may not work if the OMAPI on your device has been compiled using code obfuscation or was modified otherwise by your phone OEM (as the OMAPI is not part of official Android, every OEM may include its own version)
This Xposed module also may not work on other versions of OMAPI (it was tested with OMAPI v2.05 and should also work with OMAPI V3.0)
I hope this might be useful for someone. Have a nice day.
References:
[1] GlobalPlatform Device Technology - Secure Element Access Control (PDF)
[2] Open Mobile API specification - V2.05 (PDF)
[3] Open Mobile API specification - V3.0 (PDF)
[4] my Github repository for this Xposed module: XposedOMAPIOverrideSEAccessRules
[5] my Github repository with OMAPI fork for working on unmodified Android 5 or newer
I'm very impressed! Love your 'investigations'
I installed OMAPI 2.05 with adb on my xperia sp with cyanogenmod 13 (android 6.0.1).
After that I installed the elba-pay app, but it's not working. May you help me?
polo_joe said:
I installed OMAPI 2.05 with adb on my xperia sp with cyanogenmod 13 (android 6.0.1).
After that I installed the elba-pay app, but it's not working. May you help me?
Click to expand...
Click to collapse
Hi polo_joe:
This doesn't directly match the topic of this thread. But send me a PM then we can continue to communicate on a different channel (email, etc.). Most interesting would be a output of "logcat":
On your computer enter the command: "adb logcat -v time > logcat_debug.txt" in a terminal window then try to start the ELBA Pay app and afterwards look in the "logcat_debug.txt" logfile for errors.
john
androcheck said:
Hi polo_joe:
This doesn't directly match the topic of this thread. But send me a PM then we can continue to communicate on a different channel (email, etc.). Most interesting would be a output of "logcat":
On your computer enter the command: "adb logcat -v time > logcat_debug.txt" in a terminal window then try to start the ELBA Pay app and afterwards look in the "logcat_debug.txt" logfile for errors.
john
Click to expand...
Click to collapse
thanks, will do!
Android Faker
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its a simple Xposed module which will help you to spoof your device ids so you can save your real ids from malicious software and prohibit malicious software from accessing mobile phone data.
Disclaimer:
The Author and Contributors of Android Faker take no responsibility for any loss of data or damage to your device or any other consequences that arise as a result of using this application Use it at your own risk.
Compatibility:
This Module will Support Android 8.1+
Features:
-> Edit\Random Value.
-> Random All Value by 1 Click
-> Beautiful Material Design UI
-> Backup/Restore Feature
Module Can Spoof These Ids:
-> Imei
-> Hardware Id
-> Mac Address
-> Mac Bssid
-> Mac Ssid
-> Bluetooth Mac
-> Android Id
-> Sim Serial Id
-> Sim Sub Ids
-> Mobile No
-> GSF ID
-> MediaDrm ID
-> Advertisement ID
REQUIREMENT
-> Rooted Device
-> Xposed Framework Installed
Credits:
@Mikanoshi -help me make preference readable.
@C3C076 -for teach me about Selinux security.
@Massi-X - Thanks for helping me with the donation package.
@DE - For inspired me for this module.
@Lsposed Team - For their efforts.
@VD171 - for his app VDInfo which will help to check spoof values.
Current Version:
V1.8.3
Download: Download from the GitHub release
Support:
Coding and supporting this project cost me a lot of my precious time. If you find this project useful, you are more than welcome to support its development via purchasing a donation package and you will get some premium features as a bonus. Thanks!
Info about premium features:
there are three premium features for now:
- Backup/restore of settings.
- GSF ID.
- MediaDrm ID.
- Theme
Donation by Bitcoin:-
12eai5UkUtBe1gzNYvBvjTNTDvqVBFbQzy
How to Activate the premium feature?
Go inside -> Android Faker -> Settings -> Verify License.
Changelog:
Code:
v1.8.3
- Add VIP for access premium features without playstore
- Refactor all codes into kotlin
- Fixed sim operator crash issues
- More bug fixes
V1.8.2
- Fixed crash while selecting the USA in sim operator.
V1.8.1
- Added Sim Operator Spoof (Beta)
- Fixed RemotePreference bug
- New option for verifying the license
- Fixed crash on boot in Android 12
- Some more bugs fix
V1.7.2
- Removed new Xshared.
- Added RemotePreferece.
- Fix manual add value not change.
V1.7.1
- Fixed mobile no random generate.
- Fixed GSf default set true.
V1.7
-Bug fixed for premium features.
V1.6
-Added MD3 style
-Added Backup & Restore in a more stable
-Added One plus device support
-Added a new icon
-UI Changes
-Bug fix Random boot loop
-Using new Xshared for more device compatibility
-much more.
V1.5
- Redesign all UI now module look better
- Removed some features coz they cause a boot loop in some devices
- Fixed some bugs
V1.4
- Fixed License Verification issue now you can purchase a pro app from the play store
- Fixed Bugs
V1.3
- Added Backup/Restore Feature
- Added GSF ID
- Added MediaDrm ID(close android faker to see changes)
- Added Advertisment ID
- Added Android Version
- Added Manufacture
- Fix Some Bugs
V1.2
-Bug Fix Android Id Not Changing
-Fix Some More Issues
V1.1
-Added Both Imei Change
-Fix Some Bug
V1.0
-Initial Release
Know Bug:
-Some user report module did not work in Oneplus OOS I can fix it but I don't have to own a one plus device for testing so fix for this bug take time.
-Bootloop in some devices after applying in exposed or exposed you can fix it just don't spoof the Wifi mac address(untick the wifi mac address) it will fix in the next update.
Want to Contribute?:
If you have some fix for a bug and you want to help me with fixing that then you can contact me Sure I will give credit.
Issues :
If you face any issues in using Android Faker Contact me
Email:- [email protected]
Test :
You can use this app to test whether is Android faker working or not
Download
About feature requests and bug reports:
The goal is to have a tool that can protect the privacy of users However, it isn't paid work, so I do whatever I like whenever I like it.
You can request features in this XDA forum. I will read them, but maybe I will not respond to all of them and they might or might not be implemented.
You can report any problem by creating an issue on GitHub
Telegram
Announcements and pre release versions - https://t.me/androidfakerofficial
Note:- This Module never changes real ids or physical device ids so don't ask Stupid Questions Can I spoof my service providers and do anything wrong or right don't use this app for any illegal purpose or cheat any program this module just for spoof device non-resettable id for better privacy.
Discussions about donation packages are not allowed here, please contact me via email instead.
Privacy policy & Term Condition Updated
Thank you for trying this module, if you like don't forget to press thanks
Hi, can you add MCC/MNC ???
I want use an app witch need a specific sim operator.
Hello,
Is it possible to change Android version per app? Some apps have different behaviour dependind on wich android version they run.
adamantem said:
Hi, can you add MCC/MNC ???
I want use an app witch need a specific sim operator.
Click to expand...
Click to collapse
Yes i will adding it in next upcoming Update but which sim operator is it? Need
Borchuck said:
Hello,
Is it possible to change Android version per app? Some apps have different behaviour dependind on wich android version they run.
Click to expand...
Click to collapse
I will try to add such kind of feature in next update if possible btw i will hook sdk and you can use this module in Lsposed so you can apply specific sdk(Android version) for a specific app
AndroidX said:
I will try to add such kind of feature in next update if possible btw i will hook sdk and you can use this module in Lsposed so you can apply specific sdk(Android version) for a specific app
Click to expand...
Click to collapse
Thank you very much!
AndroidX said:
Yes i will adding it in next Update but which sim operator is it? Need
Click to expand...
Click to collapse
In the app Moto Voice for Alexa, my sim card is not compatible, it say that need a sim card compatible, I wanna spoofed the operator for that app
adamantem said:
In the app Moto Voice for Alexa, my sim card is not compatible, it say that need a sim card compatible, I wanna spoofed the operator for that app
Click to expand...
Click to collapse
Ok i will add it in next update if possible
AndroidX said:
Ok i will adding it in next update
Click to expand...
Click to collapse
Thank you very much!
AndroidX said:
Android Faker
View attachment 5325267
I started work on it try to learn things how xposed framworks works then after learning i made this app its a simple xposed module which will help you to spoof your device ids so you can save your real ids and its also work some case when a app blocked you on device ids base like imei , hardware id, etc.
Compatibility:
This Module will Support Android 5.0 +
Features:
*Edit\Random Value.
*Random All Value by 1 Click
*Beautiful Material Design UI
Module Can Spoof These Ids:
->Imei
->Hardware Id
->Mac Address
->Mac Bssid
->Mac Ssid
->Bluetooth Mac
->Android Id
->Sim Serial Id
->Sim Sub Ids
->Mobile No
!!..REQUIREMENT..!!
-> Rooted Device
-> Xposed Framework Installed
Special Thanks:
Mikanoshi -for help me and make preference readable.
C3C0 -for teach me about selinux security.
Note :- This Module never change real ids so don't ask Can i spoof my service providers and do anything wrong or right and they will never trace you.
Version:
1.1
Download : Android Faker
Bug Report : Github Issue Request
Click to expand...
Click to collapse
Please add suport for eth0 mac and suport for proc/cpuinfo changer serial
dorianndamon said:
Please add suport for eth0 mac and suport for proc/cpuinfo changer serial
Click to expand...
Click to collapse
As i knw i already hooked all macs and Can uhh explain me more what kind of cpu info?
hello developer
thanks you for make this perfectly app
but the version 2 doesn't change device id ever
but version 1 changed perfectly
i back to pervious version and changed the device id
my device version : Android 10
custom room (Reloaded os)
device name : Redmi note 8
root: Magisk v 23 Lastet
Yusef_LBN said:
hello developer
thanks you for make this perfectly app
but the version 2 doesn't change device id ever
but version 1 changed perfectly
i back to pervious version and changed the device id
my device version : Android 10
custom room (Reloaded os)
device name : Redmi note 8
root: Magisk v 23 Lastet
Click to expand...
Click to collapse
Thanks i appericate you used my module and know me about bug i just see you are right new version not hooking android id and just now i fixed that issue and tomorrow i will upload new version with fix.
AndroidX said:
Thanks i appericate you used my module and know me about bug i just see you are right new version not hooking android id and just now i fixed that issue and tomorrow i will upload new version with fix.
Click to expand...
Click to collapse
thanks you so much sir
----New Version Update----
V1.2:
Changelog:
- Bug Fix Android Id Not Changing
- Fix Some More Issues
AndroidX said:
New Version Added
Changelog:
- Bug Fix Android Id Not Changing
- Fix Some More Issues
Click to expand...
Click to collapse
thanks you sir
it's working perfectly now
thanks you very much
you can add more features like
android device version
fingerprints
google advertising id
Yusef_LBN said:
thanks you sir
it's working perfectly now
thanks you very much
you can add more features like
android device version
fingerprints
google advertising id
Click to expand...
Click to collapse
Yah thanks for your suggestions i am working on advertising id along with Backup/Restore feature so user can make backup of these id and letter restore it when user want to use same values .
Hello , may you can add change from this xposed module https://repo.xposed.info/module/zone.bytesreverser.xposeddeviceidmaskerlite
Manufacturer Serial
Brand
Manufacturer
Model
Device
Product
Hardware
Board
Bootloader
Fingerprint
ID
Incremental
Host
felix_thecat said:
Hello , may you can add change from this xposed module https://repo.xposed.info/module/zone.bytesreverser.xposeddeviceidmaskerlite
Manufacturer Serial
Brand
Manufacturer
Model
Device
Product
Hardware
Board
Bootloader
Fingerprint
ID
Incremental
Host
Click to expand...
Click to collapse
I can add all of this but i was thinking now days people dont need these ids and in some case its cause to bootlope if we will hook SDK_INT or Android Version so thats why i dont add these till now but if lots of people request for this then i will add it definately
AndroidX said:
I can add all of this but i was thinking now days people dont need these ids and in some case its cause to bootlope if we will hook SDK_INT or Android Version so thats why i dont add these till now but if lots of people request for this then i will add it definately
Click to expand...
Click to collapse
iam got a testing a version with this. and bootloop is easy fix if Android Faker module for lsposed
Do the (F-Droid) Kaltura and Evozi device id developer tools report a different Android ID for you as they do for me?
If so, why?
Kaltura XDA thread
Kaltura F-Droid tool (named "kDI Device Info system permission")
Evozi XDA thread
Evozi Google Play Store tool (named "Device ID")
Note: There is a Kaltura Google Play Tool named "Kaltura Device Info" which is not being discussed here.
Note: The actual ID's are obfuscated where the GSF ID's match between the two tools, but not the Android Device ID.