TD Fuzzer
This is a simple Xposed module designed to help those that utilize Nitrodesk's Touchdown to connect to their Exchange Activesync systems. Some EAS implementations prohibit certain device types/models from connecting, or if you'd rather present an alternate device when provisioning, this module can help with that. Keep in mind, if your IT staff/Info Security Office discover that you're circumventing their security controls and/or policies, I can't be held accountable if you get reprimanded and/or fired. This module won't circumvent specific policy requirements, such as device or sdcard encryption, strong password requirements, or disabled feature sets (disable IR, disable BT, etc). All it does is replace device-specific information that is collected during device provisioning, and also during each Activesync session (User-Agent header).
A picture is worth a thousand words, or so the saying goes:
{
"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"
}
The device on the top is my HTC One (m7) running Touchdown 8.4.00082 on KK 4.4.2, and the one beneath it is an actual iPhone 5s. The only discernible difference is the Device ID (which can't easily be changed in TD without breaking stuff).
This module should work on most devices running most ROMs. It only hooks the Touchdown package, and has been tested on TD 8.1.x, 8.4.x, and the latest 8.5.00086 against Exchange 2010 SP1 (Activesync v14.1) and Office 365 (Exchange 2013).
Install/Configuration
Install Xposed Framework
Activate Xposed app_process
Install this module and enable in Xposed Installer
Open TD Fuzzer settings and configure options
Reboot or soft-reset
Open Touchdown and provision device (or if already provisioned, go to TD Settings, Connection, ActiveSync button, Refresh ActiveSync Settings)
Source
You can find it on my github
Alternate Install
Also available in the xposed repo
@cities516 can you add to your module index?
Until I get around to adding some device presets into the module, here are some examples straight out of OWA:
iPhone 4S
Phone friendly name: Black iPhone 4S
Device Model: iPhone4C1
Phone OS: iOS 7.0.4 11B554a
Device Operating System Language: en
User agent: Apple-iPhone4C1/1102.55400001
SAMSUNG SGH-I747 (AT&T GS3)
Phone friendly name: d2uc
Device Model: SAMSUNG-SGH-I747
Phone OS: Android
Device Operating System Language: English
User agent: SAMSUNG-SGH-I747/101.403
SAMSUNG SGH-I317 (AT&T GN2)
Phone friendly name: t0lteatt
Device Model: SAMSUNG-SGH-I317
Phone OS: Android
Device Operating System Language: English
User agent: SAMSUNG-SGH-I317/100.40102
Great Work!
I've been search for a solution for this for ages and must I say that your xposed module is by far the only and most effective solution. Big congrats and very much obliged, man.
Because without this, although Touchdown can spoof a device name, the OS, protocols during the Activesync provisioning process will still be "Android 4.4.x" and "Touchdown x.x.x". So from the admin's side, it is still able to identify the spoofing by looking at the OWA mobile log.
Three questions:
1. How does it work? Modifying provisioning communication packets between Touchdown and ActiveSync server? I'm asking this because I want to know if future versions of Touchdown can be supported.
2. Will you consider supporting Android 5.0?
3. Will you consider supporting AOSP email apps, (preferably the apks with Exchange Security byPass working for 4.4.4 and 5.0)
Again, many thanks to you for the great work!:laugh:
XDAAdvocate said:
1. How does it work? Modifying provisioning communication packets between Touchdown and ActiveSync server? I'm asking this because I want to know if future versions of Touchdown can be supported.
Click to expand...
Click to collapse
I've replaced the writeDeviceInfo() method, which builds the provisioning XML object (com.nitrodesk.wbxml.WBXMLSerializer object, to be precise). This should be compatible with any version of TD; it's more specific to the Activesync protocol version (14.1 in this case). If MS changes how devices send provisioning data, then it would have to be updated. Also, there's information that's passed to EAS in the User-Agent header, which this module replaces.
2. Will you consider supporting Android 5.0?
Click to expand...
Click to collapse
Sure, once I have a device running Android L and the Xposed Framework.
3. Will you consider supporting AOSP email apps, (preferably the apks with Exchange Security byPass working for 4.4.4 and 5.0)
Click to expand...
Click to collapse
I've run across at least one xposed module out there that bypasses the AOSP email security restrictions for EAS. Since I don't normally run AOSP roms, it's much harder for me to do any sort of debugging/dev work.
agentdr8 said:
......
I've run across at least one xposed module out there that bypasses the AOSP email security restrictions for EAS. Since I don't normally run AOSP roms, it's much harder for me to do any sort of debugging/dev work.
Click to expand...
Click to collapse
Can you tell me where to find the modules to bypass these security restrictions for EAS. There are indeed some modules to bypass the mandatory PIN for example. But no module to bypass and change the device provisioning data.
This is what I needed thanks will try and report
yooidje said:
Can you tell me where to find the modules to bypass these security restrictions for EAS. There are indeed some modules to bypass the mandatory PIN for example. But no module to bypass and change the device provisioning data.
Click to expand...
Click to collapse
You're right; I don't think any of the ones I've seen can modify the device provisioning data, only bypass the PIN/lockscreen restrictions.
agentdr8 said:
You're right; I don't think any of the ones I've seen can modify the device provisioning data, only bypass the PIN/lockscreen restrictions.
Click to expand...
Click to collapse
Is there any possibility that you can also support the AOSP email apps, perhaps?
**please :angel:
yooidje said:
Is there any possibility that you can also support the AOSP email apps, perhaps?
**please :angel:
Click to expand...
Click to collapse
If I have some free time I'll see what I can do on my TF700 running CM11.
agentdr8 said:
If I have some free time I'll see what I can do on my TF700 running CM11.
Click to expand...
Click to collapse
:victory: I am more than willing to test any developments
In case anyone is wondering, this module still works on LP with the latest Xposed Framework.
Still working on the latest Xposed Framework for Marshmallow. Also tested against O365, and works just fine.
agentdr8 said:
Still working on the latest Xposed Framework for Marshmallow. Also tested against O365, and works just fine.
Click to expand...
Click to collapse
Hi, can you confirm if this works with the latest version of touchdown available currently, 8.5?
randallstevens said:
Hi, can you confirm if this works with the latest version of touchdown available currently, 8.5?
Click to expand...
Click to collapse
Yes indeed. I'm running 8.5.00086 with the module just fine. I'll update the OP.
EDIT: Looks like I had already updated the OP with that info. [emoji3]
Related
{
"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"
}
XPrivacy
After weeks of research, development and testing I proudly present the ultimate, yet easy to use, privacy manager: XPrivacy.
XPrivacy can prevent applications from leaking privacy sensitive data. XPrivacy can restrict the categories of data an application can access. This is done by feeding an application with no or fake data. There are several data categories which can be restricted, for example contacts or location. For example, if you restrict access to contacts for an application, this will result in sending an empty contact list to the application. Similarly, restricting an application's access to your location will result in a set location being sent to the application.
You can use the successor XPrivacyLua on Android 6.0 Marshmallow and later.
Features
Simple to use
No need to patch anything (no source, no smali or anything else)
For any (stock) variant of Android version 4.0.3 - 6.0.1 (ICS, JellyBean, Lollipop, Marshmallow)
Newly installed applications are restricted by default
Displays data actually used by an application
Option to restrict on demand
Free and open source
Free from advertisements
Read more on GitHub
Description
Features
Restrictions
Limitations
Compatibility
Installation (quite easy!)
Upgrading
Usage
Permissions
Frequently asked questions
Support
Changelog
Similar solutions
News
Contributing
License
The download link is in the installation instructions
You can also use the XPrivacy Installer as an aid to install XPrivacy.
This forum is for questions only. See here for bug reports and feature requests.
Please post messages related to privacy only.
XPrivacy is not intended to make other application do things they are not supposed to do.
There is only support for the latest official XPrivacy version.
XPrivacy was a lot of work, so please support this project
If you want to donate, see here for all options.
Use at your own risk !
The latest version from a while ago still works properly up to Android 6 Marshmallow, if Xposed works properly on your device
(you can ignore any internal error report of XPrivacy, since these are known to be harmless)
XDA:DevDB Information
XPrivacy, Xposed for all devices (see above for details)
Contributors
M66B
Source Code: https://github.com/M66B/XPrivacy
Xposed Package Name: biz.bokhorst.xprivacy
Version Information
Status: No Longer Updated
Current Stable Version: 3.6.19
Stable Release Date: 2015-07-01
Created 2014-08-03
Last Updated 2018-02-08
Wow! :good:
Can't wait to take this for a test run!
And see what else can be added, of course
Tungstwenty said:
Wow! :good:
Can't wait to take this for a test run!
And see what else can be added, of course
Click to expand...
Click to collapse
Please report about your experiences.
Contributions are more than welcome to make it a better mod.
Thanks a lot. I always missed PDroid as i am on stock Samsung ROM.
BTW, the patches also work on Stock Rom ? ie : even if i don't use CM10, i need to install the CM10_4.1 patch isn't it ?
Tanks again
Looks awesome.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Namoi said:
Thanks a lot. I always missed PDroid as i am on stock Samsung ROM.
BTW, the patches also work on Stock Rom ? ie : even if i don't use CM10, i need to install the CM10_4.1 patch isn't it ?
Tanks again
Click to expand...
Click to collapse
Yes, the fixes should work on stock ROM too, but I didn't test it.
M66B said:
Yes, the fixes should work on stock ROM too, but I didn't test it.
Click to expand...
Click to collapse
I will try ASAP and report
Im using this since version 0.3 and think it is really a great Mod!
Thank you very much for your hard work!
I'd really like to contribute, but since I'm pretty limited in terms of coding the only thing I can offer is to translate Xprivacy to German if you like.
I already got some experience in app translating (though it has been some time since then), so just PM me, if you want me to translate it
Gesendet von meinem Xperia Mini Pro mit Tapatalk 2
Wow, this application is gone so far from 0.1! :good:
M66B said:
Yes, the fixes should work on stock ROM too, but I didn't test it.
Click to expand...
Click to collapse
So If I'm on a sense based 4.2.2 rom I also need to install the CM 4.2 fix? (just installed the latest version of Xprivacy .11)
the app has improved greatly, its very usable now.
some suggestions/details:
app/usability:
1. the app is usable when it is not enabled, there should be a check on app launch if it is enabled in xposed.
2. some sort of loading indicator instead of just directly jumping into the batch edit category after a wait.
3. search for apps.
4. app filtering
2,3,4 are already implemented in xposed app settings, perhaps you could look at that code.
ui stuff:
1. all the activities except the main one should have menu items and the navigation action http://developer.android.com/guide/topics/ui/actionbar.html#Home
2. the blocked apps/ apps with the particular permission should be sorted above the rest.
i'd say blocked apps->apps with permission but not blocked-> rest of them
3. scroll bar in batch edit
4. action bar spinners or a viewpager like the xposed app separating the batch edit and the list of all apps. (AB spinners would save space though)
these are suggestions, i love the app as it is,
graffixnyc said:
So If I'm on a sense based 4.2.2 rom I also need to install the CM 4.2 fix? (just installed the latest version of Xprivacy .11)
Click to expand...
Click to collapse
Yes, else not each data type will be restricted.
M66B said:
Yes, else not each data type will be restricted.
Click to expand...
Click to collapse
TY Sir
hmm odd. I have everything installed (Xposed 34, xprivacy .11 and the fix) I don't see an Xprivacy button in manage apps like in the 2nd screen shot.
graffixnyc said:
hmm odd. I have everything installed (Xposed 34, xprivacy .11 and the fix) I don't see an Xprivacy button in manage apps like in the 2nd screen shot.
Click to expand...
Click to collapse
First the most obvious: did you reboot? did you enable XPrivacy in the Xposed installer?
Which ROM do you use?
Do you see orange triangles if you start XPrivacy and browse apps?
M66B said:
First the most obvious: did you reboot?
Which ROM do you use?
Do you see orange triangles if you start XPrivacy and browse apps?
Click to expand...
Click to collapse
Yes, I rebooted twice. I'm on TrickDroid 4.2.2 (sense based) on the HTC One. I do see the orange triangle on some apps when I open up Xprivacy but not on all (going into the different categories)
a have a request. The application is really great, but I would much rather like to get notification(and then I can open XPrivacy by just clicking on it) when new application is installed instead of just popping up. I hope you understand me
graffixnyc said:
Yes, I rebooted twice. I'm on TrickDroid 4.2.2 (sense based) on the HTC One. I do see the orange triangle on some apps when I open up Xprivacy but not on all (going into the different categories)
Click to expand...
Click to collapse
If you see orange triangles XPrivacy is in any case working.
Maybe your settings layout is different, so that XPrivacy cannot hook into it.
This is not a big problem, because you can access all settings from the app too.
You can do me a pleasure by sending a logcat, starting from the moment your device boots, so I may be able to figure out why this (not) happens.
kv1dr said:
a have a request. The application is really great, but I would much rather like to get notification(and then I can open XPrivacy by just clicking on it) when new application is installed instead of just popping up. I hope you understand me
Click to expand...
Click to collapse
Please create an issue and I will realize this.
gandhar said:
the app has improved greatly, its very usable now.
some suggestions/details:
app/usability:
1. the app is usable when it is not enabled, there should be a check on app launch if it is enabled in xposed.
2. some sort of loading indicator instead of just directly jumping into the batch edit category after a wait.
3. search for apps.
4. app filtering
2,3,4 are already implemented in xposed app settings, perhaps you could look at that code.
ui stuff:
1. all the activities except the main one should have menu items and the navigation action http://developer.android.com/guide/topics/ui/actionbar.html#Home
2. the blocked apps/ apps with the particular permission should be sorted above the rest.
i'd say blocked apps->apps with permission but not blocked-> rest of them
3. scroll bar in batch edit
4. action bar spinners or a viewpager like the xposed app separating the batch edit and the list of all apps. (AB spinners would save space though)
these are suggestions, i love the app as it is,
Click to expand...
Click to collapse
Thanks for your feedback, gandhar.
Could you please create issues for these, so I can easily track things?
Loading apps in an async task + spinner has already been realized (will be in version 0.12).
Updated 01312014
Update: I have the core code done for the revamped Utility. I have changed 70% of the UI and will continue to add controls for 1 click functionality. Next Release as soon as I get all the code and design together.
Hello Fellow Max owners.
I have been working on a HTC One Max Utility that originally was going to be solely used for Changing the Bootloader Flag(Scotty1223's Fix for the Flag) and Removing the Tampered Flag on Verizon and Sprint phones(Again Scotty1223's fix for the Tampered Flag). This utility is Windows Based and provide a GUI instead of having to use the Terminal commands.
First let me thank the following users for there invaluable help during this project.
Credit:
Scott1223 XDA
Beanups XDA
Strace XDA
regaw_leinad XDA (Creator of AndroidLib.dll)
Prerequisites:
Windows 7 or 8 Machine (If your using XP it will most likely work but you should at least upgrade to 7 as XP support is expiring)
.Net Framwork 4.5 or 4.5.1
USB Cable
SuperUser Installed on your HTC One Max
Your have to be S-OFF (Rumrunner or other method)
A Sprint or Verizon Variant of the HTC One Max with Stock Rom (International support is in development)
What the program does:
This is essentially a Front end GUI for the commands that already exist in the following Threads:
[how to] lock/unlock your bootloader without htcdev(s-off required) (Scotty1223)
http://forum.xda-developers.com/showthread.php?t=2540004
and
[how to] remove your "tampered" banner (Scotty1223)
http://forum.xda-developers.com/showthread.php?t=2540024
My program on Start will Check for a HTC One Max Variant (Verizon or Sprint) that is STOCK (I am adding Other Rom Support but I need data still)
Once the phone is detected it will check to make sure you have the HTC Drivers Installed
Once the Drivers are detected it will check to make sure you have .Net 4.5 or 4.5.1 installed (yes those specifically)
At this point the application will ask you to agree to the terms of use and verifiy you have S-OFF on the phone (click agree to all button)
You you have agreed it pulls the device's Build.Prop File to populate the needed information about your phone (This is STOCK Verizon and Sprint Specific at the moment)
Your information will load and populate on the HTC picture to the Left of the program.
The program will then allow you to Change the Bootloader Flag to Locked (Null) or Unlocked (HTCU)
Once complete you can use the Boot to Bootloader button to verify the change. (Tool does not work in Bootloader Mode Yet)
Additionally you can Remove the Tampered Banner if it is showing from the bootloader. This is based on the Carrier Flag in the Build.Prop
V.1.1 Beta
Added Detection for HTC Drivers and .Net 4.5 and 4.5.1 Frame Work
Cleaned up Code and streamlined implementation.
Added Graphics and Build.Prop Pulls for Stock Verizon and Sprint Roms
Verified on Verizon Branded model that Lock and Unlock Flag Changed Accordingly in Bootloader.
Verified Tampared Flag Removal on Verizon Branded model with Stock Rom.
Basic Troubleshooting:
[Q]
Your application just crashed on Launch
[A]
Did you see a error windows or Debug Screen?
Typically this is due to not meeting the prerequisites required to use the program.
[Q]
The application says it can not detect my phone?
[A]
If you have meet the prerequisites and the program reports the phone not found trying starting and stopping the ADB damon.
Adb start-server
Adb kill-server
Press the Update Device Information Button to see if the device is detected now.
[Q]
The application loaded fine but crashes with a unhandled exception.
[A]
Please provide me with the Error code and diagnostic information in a Private Message.
[Q]
The program loads but when I accept the Terms some of the Phone information is not loading.
[A]
If you are using a Stock Verizon or Sprint Rom please dump your build.prop using the following command:
Code:
adb shell getprop > "%USERPROFILE%\Desktop\prop.txt
Send me the txt file for evaluation.
[Q]
Are you going to support international versions of the phone.
[A]
Yes eventually however I am currently collecting the information I need to code. Stay Tuned.
Screenshot:
{
"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"
}
Additional Features Coming Soon:
Another UI Overhaul
More code consolidation and clean up (Making app smaller)
Device State monitoring (Fastboot, Normal boot or Recovery boot States)
Sideloading Applications
PC to Android Apak installations (Direct installations to Android device)
Recovery installation TWRP and CWM (Thanks for permission Flyhalf)
Rom flashing
Download Link:
HTC One Max Utility V1.1 (Dev-Host)
Change Log:
V 1.1 Beta (Launch Bug Fix issue Corrected)
V 1.0 Beta (Original)
nice work!
I'll be watching for when it works on viper 1.01...
wase4711 said:
nice work!
I'll be watching for when it works on viper 1.01...
Click to expand...
Click to collapse
Working on this now.. I aquired the Build.Prop dump from the dev. Going to see what I can manage.
wase4711 said:
nice work!
I'll be watching for when it works on viper 1.01...
Click to expand...
Click to collapse
I am trying to identify build.props that are common to all models and roms but it seems they varies based on the dev cooks fancy for their build. I can programatically account for all the variations unless the key values are changed again in future builds.
well, thats always a problem; I guess when ever you release a tool, you have to specify what versions it works on, and warn people to not try it unless they are on that version
Preview for Beta Build 2:
Sorry guys got pulled at work for some programming jobs and it's been taking away from my app. Hopefully I can push out a updated version in the next week. Sorry for the delay.
Software Not Working
DeadPhoenix said:
Sorry guys got pulled at work for some programming jobs and it's been taking away from my app. Hopefully I can push out a updated version in the next week. Sorry for the delay.
Click to expand...
Click to collapse
I tried to run the program from the link you gave. It says I need .Net framework 4.5 when I already have it installed. Any deadline on 2.0 will be released?
GothicGeek502 said:
I tried to run the program from the link you gave. It says I need .Net framework 4.5 when I already have it installed. Any deadline on 2.0 will be released?
Click to expand...
Click to collapse
I have a very updated version but unfortunately I haven't been able to work on the bugs that are in it at the moment. I have had 3 big programming jobs at work that are occupying my time for the release of the next version.
The application requires .net 4.5 framework be installed on the machine. It checks the registry for the key to confirm it's installed.
I suppose I can release a version without the software checks if you feel you have the system requirements. I have to find the bloody source first. lol
Or you can just install .Net 4.5.1 Framework and that should fix your wagon.
Already installed
DeadPhoenix said:
I have a very updated version but unfortunately I haven't been able to work on the bugs that are in it at the moment. I have had 3 big programming jobs at work that are occupying my time for the release of the next version.
The application requires .net 4.5 framework be installed on the machine. It checks the registry for the key to confirm it's installed.
I suppose I can release a version without the software checks if you feel you have the system requirements. I have to find the bloody source first. lol
Or you can just install .Net 4.5.1 Framework and that should fix your wagon.
Click to expand...
Click to collapse
I already have 4.5.1 installed I have ALL the required .Net Frameworks I work on computers and also .net frameworks need to be installed to run Wireless Workshop, So yes I have the right stuff installed and it keeps saying I don't.
GothicGeek502 said:
I already have 4.5.1 installed I have ALL the required .Net Frameworks I work on computers and also .net frameworks need to be installed to run Wireless Workshop, So yes I have the right stuff installed and it keeps saying I don't.
Click to expand...
Click to collapse
Is your Locate Language English?
This was written for US Copies of Windows. When the program searches for the Registry Keys for the .Net Framework all words are in english. That is the only thing I can Think of why it would not work.
Yes
DeadPhoenix said:
Is your Locate Language English?
This was written for US Copies of Windows. When the program searches for the Registry Keys for the .Net Framework all words are in english. That is the only thing I can Think of why it would not work.
Click to expand...
Click to collapse
Yes I am from the US, I am using a fully legal paid for from Walmart Win7 Home Prem
SIM Number SetterSIM Number Setter is a small Xposed module that invokes normally unused Android System code to set the "subscriber number" on the device's SIM card. This is the number displayed in the system settings, and used in apps such as Google Messages, as well as being available to third party apps with sufficient permissions.
The number is not always set by carriers (leaving "Unknown"), or can be lost or invalid after porting a number to a different SIM.
This small app allows you to fix it, permanently, using a rooted device with Xposed.
If you don't have a rooted device, or don't want to root your main device, you may wish to consider rooting an old device, and temporarily putting your SIM into that device, using this app, and then putting it back in your main device - the fixed number will travel with it
There are some older Xposed modules that do similar things to this, but they are all abandoned and use methods that will no longer work with changes to the platform since then. This module should keep working regardless as it does not store the number locally at all, instead immediately invoking the change - allowing the app to be uninstalled after use too.
Important NoticeChanging the SIM number is semi-permanent: the number change will survive reboots, uninstalling this app, even switching the SIM to a different device, but can be changed again at any time using this app.
SIM Number Setter does NOT:
Change your actual phone number, no matter what you enter. You must contact your carrier if you wish to port your number or switch network.
Unblock a network blocked SIM.
Give you free data or calls.
Change your IMEI.
SIM Number Setter uses the built-in Android methods to write data to the SIM. The app nor the developer are not responsible for issues with the process, including any damage to the SIM or network issues.
Screenshots
DownloadDownload from the GitHub releases page
Source Code
GitHub
It works perfectly fine with LSposed too!!
Thanks a lot!
Ohh, FFS! If you have dual SIM, just switch them, change its number and switch them back! Not a big deal!
@Quinny899 Thanks for this! Is there a defined format in which the phone number should be entered? For example, +[Country Code][10 Digit Mobile Number], or 00[Country Code][10 Digit Mobile Number], something like that?
shadowstep said:
@Quinny899 Thanks for this! Is there a defined format in which the phone number should be entered? For example, +[Country Code][10 Digit Mobile Number], or 00[Country Code][10 Digit Mobile Number], something like that?
Click to expand...
Click to collapse
Anything should work, so long as it's 20 chars or less and uses only numbers or +
works perfectly as described, in case of dual SIM just temporarily change the position to SIM1
brenosnt said:
works perfectly as described, in case of dual SIM just temporarily change the position to SIM1
Click to expand...
Click to collapse
I concur! working wonderfully on Android 12 Beyond Rom (Note 20 Ultra)!!
Quinny899 said:
Anything should work, so long as it's 20 chars or less and uses only numbers or +
Click to expand...
Click to collapse
Doesn't work for me, unfortunately. Could be because of OxygenOS (read all the issues, open and closed, in your GitHub repository and checked everything) but I'm not sure. Thanks nonetheless!
rgavioli said:
It works perfectly fine with LSposed too!!
Click to expand...
Click to collapse
Can u help me, I'm getting failed to connect to the Xposed service.
Already have LSposed zygisk installed and I enabled module.
Running android 12
fardeenah said:
Can u help me, I'm getting failed to connect to the Xposed service.
Already have LSposed zygisk installed and I enabled module.
Running android 12
Click to expand...
Click to collapse
Which Android 12 firmware on what device?
Quinny899 said:
Which Android 12 firmware on what device?
Click to expand...
Click to collapse
Running AEX aospextended on redmi note 5 pro
fardeenah said:
Running AEX aospextended on redmi note 5 pro
Click to expand...
Click to collapse
There's a report on GitHub of someone with a phone that came with MIUI doing the same thing, I suspect there's something different on those devices. Not a lot I can do without having the device to debug, as the logs don't show anything.
F
Quinny899 said:
There's a report on GitHub of someone with a phone that came with MIUI doing the same thing, I suspect there's something different on those devices. Not a lot I can do without having the device to debug, as the logs don't show anything
Click to expand...
Click to collapse
I really wish I could change that sim number. Man....
Such a bummer.
Make sure the module is enabled on LSposed.
Also, make sure Phone services is selected at the module.
Reboot your device and try again.
{
"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"
}
rgavioli said:
Make sure the module is enabled on LSposed.
Also, make sure Phone services is selected at the module.
Reboot your device and try again.
View attachment 5543693
Click to expand...
Click to collapse
I did but it's not working for me.. What device are you running btw? Are u using the latest version of LSposed
fardeenah said:
I did but it's not working for me.. What device are you running btw? Are u using the latest version of LSposed
Click to expand...
Click to collapse
I've tested on Samsung S20, Xiaomi Mi11i and it works fine.
LSposed 1.7.2 (6379)
You could try cleaning the data from this app.
Thank you for this. I just ported my Mobile Number to another network and got a unknown number on about phone.
Just a question. Is the write procedure single use?
Can you re-write the field if you transfer numbers, or misstype, or, or or?
AndStuff said:
Just a question. Is the write procedure single use?
Can you re-write the field if you transfer numbers, or misstype, or, or or?
Click to expand...
Click to collapse
You can rewrite it as many times as you like, though I'd recommend trying to keep usage low as I doubt SIMs are designed for this data to be rewritten often. If you make a typo you can fix it though.
{
"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"
}
MACsposedHistorically, setting a custom MAC address on Android was very easy for rooted users. Starting with Android 12, however, Google's implementation of MAC address randomization has made it impossible, as the MAC address is always changed when the network state is altered. If you have encountered this problem, then you need MACsposed! MACsposed is an Xposed module that blocks the MAC address randomizer on Android 12 and 13 and allows you to once again make use of your favorite tools for setting your MAC address. Simply install MACsposed, enable it, and go back to randomizing your MAC address using your favorite tools for doing so!
WARNING: MACsposed is intended for rooted devices running Android 12 or 13 and requires Xposed. The recommended Xposed variant to use is LSPosed. Other Xposed variants may work, but have not been tested. Additionally, this module cannot be guaranteed to work on all devices. In the worst case, it can cause a bootloop. Use at your own risk.
To use MACsposed:
Install LSposed. This requires your device to be rooted with Magisk. Installation instructions for LSPosed are available here.
Install MACsposed.
Activate the MACsposed module in the LSposed user interface.
Reboot your device and sign in.
Open the quick settings panel. The MACsposed tile will appear.
Toggle the MACsposed tile on or off to enable or disable it.
Use your favorite tool for setting a custom MAC address!
MACsposed is now open source on GitHub! - https://github.com/DavidBerdik/MACsposed
Reserved.
Reserved.
Does this work on Android 10?
I owned a Xiaomi Redmi 9 running Android 10
Ace_Cole said:
Does this work on Android 10?
I owned a Xiaomi Redmi 9 running Android 10
Click to expand...
Click to collapse
The changes that Google made to prevent setting custom MAC addresses from working were only introduced with Android 12, so this app is actually not necessary if you are on Android 10.
Is it working with the last version of Lineageos?
m3m0rx said:
Is it working with the last version of Lineageos?
Click to expand...
Click to collapse
I have not tested this app on LineageOS 19, so I cannot say for sure that it will work, but since LineageOS 19 is based on Android 12, I believe that it probably will work. If you decide to try it, please let me know what your experience is like!
David B. said:
I have not tested this app on LineageOS 19, so I cannot say for sure that it will work, but since LineageOS 19 is based on Android 12, I believe that it probably will work. If you decide to try it, please let me know what your experience is like!
Click to expand...
Click to collapse
I am happy to let you know that I am writtimg on a changed MAC. It is working on Lineage 19-20220720-NIGHTLY-beyond2lte, G975F. The thing is that I had to switch to the Mac app I saw in your pictures, mine did not work.
m3m0rx said:
I am happy to let you know that I am writtimg on a changed MAC. It is working on Lineage 19-20220720-NIGHTLY-beyond2lte, G975F. The thing is that I had to switch to the Mac app I saw in your pictures, mine did not work.
Click to expand...
Click to collapse
That's great! I'm happy to hear that! Thank you for letting me know.
As for the app you used for changing the MAC address, I have found from my own experimenting that many of the MAC address changer apps that are available out there tend to be rather hit-or-miss in terms of how well they operate. Some of them were built for older versions of Android and haven't been updated in a really long time, and so, they were broken even before Android 12. Either way, I'm very happy to hear that it works for you!
MACsposed v1.1.0 with support for Android 13 is now available to download on GitHub. As of this posting, the update is still pending approval on the Google Play Store.
Hello! Can I tweak the module to run on Android 11? Tired of fighting! Wi-Fi is disabled in the settings and disabled in the developer menu. But the dastardly Techno Spark 7 still plays with the MAC.
AndryK111 said:
Hello! Can I tweak the module to run on Android 11? Tired of fighting! Wi-Fi is disabled in the settings and disabled in the developer menu. But the dastardly Techno Spark 7 still plays with the MAC.
Click to expand...
Click to collapse
Certainly! If you get it working, please consider submitting a pull request so I can expand the range of supported devices.
I should warn you that if your phone OEM has tweaked the Android code enough to randomize MAC addresses, it may not be easy to implement the change, as they've likely deviated from AOSP.
The current version just didn't start.
AndryK111 said:
The current version just didn't start.
Click to expand...
Click to collapse
Well the current version is only intended for Android 12 and 13, so I'm not surprised to hear that. If you're lucky, you may be able to get it working by just dropping the minimum SDK version, but honestly, I doubt it. Might be worth trying though.
I do not know how to do it.
offtopic ..... can some read-only file be marked?
AndryK111 said:
I do not know how to do it.
Click to expand...
Click to collapse
Do what? Modify the code?
AndryK111 said:
offtopic ..... can some read-only file be marked?
Click to expand...
Click to collapse
I don't understand the question.
David B. said:
Do what? Modify the code?
I don't understand the question.
Click to expand...
Click to collapse
David B. said:
If you're lucky, you may be able to get it working by just dropping the minimum SDK version
Click to expand...
Click to collapse
I don't know how to reset the minimum version of sdk
AndryK111 said:
I don't know how to reset the minimum version of sdk
Click to expand...
Click to collapse
Oh that's actually pretty easy to do!
Change minSdk 31 to minSdk 30 here: https://github.com/DavidBerdik/MACsposed/blob/master/app/build.gradle#L11
David B. said:
Oh that's actually pretty easy to do!
Change minSdk 31 to minSdk 30 here: https://github.com/DavidBerdik/MACsposed/blob/master/app/build.gradle#L11
Click to expand...
Click to collapse
go to https://github.com/DavidBerdik/MACsposed
"code" => Download ZIP => edit file => what's next? just rename Zip to APK?
{
"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"
}
Let Me DowngradeAndroid's app installation system does not allow users to downgrade to an older version of an app when they already have a newer version installed. Let Me Downgrade is an Xposed module for Android 12 and 13 that enables users to bypass this restriction. As an added bonus, Let Me Downgrade provides a Quick Settings tile to easily enable and disable the downgrade block.
WARNING: Let Me Downgrade is intended for rooted devices running Android 12 or 13 and requires Xposed. The recommended Xposed variant to use is LSPosed. Other Xposed variants may work, but have not been tested. Additionally, this module cannot be guaranteed to work on all devices. In the worst case, it can cause a bootloop. Use at your own risk.
To use Let Me Downgrade:
Install LSposed. This requires your device to be rooted with Magisk. Installation instructions for LSPosed are available here.
Install Let Me Downgrade.
Activate the Let Me Downgrade module in the LSposed user interface.
Reboot your device and sign in.
Open the quick settings panel. The Let Me Downgrade tile will appear.
Toggle the Let Me Downgrade tile on or off to enable or disable it.
Reserved.
Reserved.
Nice work! I assume this does not have backward compatibility, i.e. it won't work on older Android versions, and only supports Android 13? Also, consider submitting it in the Xposed-Modules-Repo.
shadowstep said:
Nice work! I assume this does not have backward compatibility, i.e. it won't work on older Android versions, and only supports Android 13? Also, consider submitting it in the Xposed-Modules-Repo.
Click to expand...
Click to collapse
Thank you! Unfortunately, this does not have backwards compatibility with older versions of Android. Adding support for allowing downgrades on Android 5 through 12 would actually be pretty easy, but adding support for the quick settings tile to toggle the module on and off would not be, and I do not really think that it is worth the effort of doing so considering that anyone using Android 5-12 will probably already be using XDowngrader.
I should also note that the developer of XDowngrader actually published an update to support Android 13 soon after I published this module, however I would recommend that Android 13 users opt for my module instead because:
Let Me Downgrade is open source but XDowngrader is not.
Let Me Downgrade allows you to toggle the module's functionality on and off without rebooting your phone through a Quick Settings tile. This is useful for if you want to temporarily allow app downgrades, but would prefer to leave app downgrades disabled in most other cases.
As far as publishing on the Xposed Modules Repo is concerned, I have actually done that! The repo entry for this module is available here.
Could you add support for android 11 and 12. That would be pretty nice!
Lucky_069 said:
Could you add support for android 11 and 12. That would be pretty nice!
Click to expand...
Click to collapse
I can add support for Android 12 pretty easily, but anything older than that, I don't think so because the Quick Settings tiles may not work and I don't have a phone to test it on.
For the convenience of users who prefer to not use the Google Play Store, I am pleased to announce that Let Me Downgrade is now available on F-Droid!
Let Me Downgrade | F-Droid - Free and Open Source Android App Repository
Add support for downgrading apps on Android 12 and 13
f-droid.org
Several users have requested support for Android 12. I am pleased to announce that Let Me Downgrade v1.0.2 adds this support.
Now I follow all steps but how I can start the downgrade?
xerel89 said:
Now I follow all steps but how I can start the downgrade?
Click to expand...
Click to collapse
After enabling the module, the downgrade process is no different than the installation or update process that you use when sideloading an app. You can use ADB to do it or you can use a file explorer app to install the older version of the app.
Not sure I get it... If I want to go back to an older version of an app, can't I just clear it's cache and uninstall the new ver. then install the old one?
Zaxx32 said:
Not sure I get it... If I want to go back to an older version of an app, can't I just clear it's cache and uninstall the new ver. then install the old one?
Click to expand...
Click to collapse
You can, but that would mean you would lose your app settings. If you use Let Me Downgrade, you'll be able to install the old version on top of the old one and retain your settings. Please note however that just because you downgrade your app in place does not mean things will work if the newer version has made internal structural changes to how the data is stored.
Gotcha!
Any way you could add the ability to disable signature verification as well?
bobpiesz said:
Any way you could add the ability to disable signature verification as well?
Click to expand...
Click to collapse
It would probably be more appropriate for me to make that be a separate module, but yes, it is possible.
@David B.
I'd be more than willing to donate towards having disable signature verification, as I'm not finding any publicly available tools for A13
bobpiesz said:
@David B.
I'd be more than willing to donate towards having disable signature verification, as I'm not finding any publicly available tools for A13
Click to expand...
Click to collapse
Doesn't Core Patch support this?
GitHub - LSPosed/CorePatch: Disable signature verification For Android
Disable signature verification For Android. Contribute to LSPosed/CorePatch development by creating an account on GitHub.
github.com
David B. said:
It would probably be more appropriate for me to make that be a separate module, but yes, it is possible.
Click to expand...
Click to collapse
Lord Sithek said:
Doesn't Core Patch support this?
GitHub - LSPosed/CorePatch: Disable signature verification For Android
Disable signature verification For Android. Contribute to LSPosed/CorePatch development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Core patch isn't working with A13
bobpiesz said:
@David B.
I'd be more than willing to donate towards having disable signature verification, as I'm not finding any publicly available tools for A13
Click to expand...
Click to collapse
When time permits, I can and will research this. Unfortunately, I'm preoccupied with other things at the moment and have had to set aside doing Xposed module development work. If you or anyone else wants to experiment and submit a PR for it, that would be greatly appreciated.
Lord Sithek said:
Doesn't Core Patch support this?
GitHub - LSPosed/CorePatch: Disable signature verification For Android
Disable signature verification For Android. Contribute to LSPosed/CorePatch development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
bobpiesz said:
Core patch isn't working with A13
Click to expand...
Click to collapse
Thank you for sharing Core Patch. I wasn't aware of its existence. Even though it doesn't work on Android 13, it might be able to serve as a good resource for me to figure out where I need to hook.