Related
[FIX][XPOSED][4.0+] Universal fix for the several "Master Key" vulnerabilities
You may be aware of recent news about several different security vulnerabilities that allow replacing code on a signed APK without invalidating the signature:
Master Key (Bug 8219321)
An issue related with duplicate entries on the ZIP / APK files.
It was patched by Google back in February 2013 and shared with OEMs, and some of the newer devices might have already received the fix in a recent stock update. At least both Xperia Z 4.2.2 and Galaxy S2 4.1.2 contain the fix; CM has also recently patched it, on this commit.
More info can be found on @Adam77Root's thread here: http://forum.xda-developers.com/showthread.php?t=2359943
Bug 9695860
This also originates in the ZIP file parsing routines, and was disclosed just a few days ago immediately after the previous one was made public. The correction has already been applied by Google to the code (this commit), but it's very likely that its rollout on stock ROMs will take a long time especially on non-Nexus devices.
You can read more about it here.
To know if you're vulnerable, use SRT AppScanner mentioned above.
Unless you're running CM 10.1.2, there's a fairly big chance that you have this issue, at least as of this moment.
Bug 9950697
It's yet another inconsistency in ZIP parsing that could be abused in very a similar way to the previous one.
This one is a bit special to me, since I was fortunate enough to be the first one to report it on Google's bugtracker
It was discovered around the time that the previous bug was acknowledged and Android 4.3 was a few days from being released, but despite the prompt report it was unfortunately too late to include the fix in time for the release; Therefore it wasn't disclosed till Android 4.4 sources came out and I had also decided not including a fix for in on this module, since it would be an easy way to learn about the extra attack vector.
Kudos to Jeff Forristal at Bluebox Security, who I learned was also working on that exact problem and helped me report it properly to Google, and also to Saurik who already released a Substrate-based fix and has written a very interesting article about it here.
Checking if you're vulnerable
You can use some 3rd party apps to test your system, such as:
- SRT AppScanner
- Bluebox Security Scanner
On Android 4.4 all these bugs should be fixed, and therefore this mod is not needed. But you can run one of these scanners to make sure you're not vulnerable.
While technically different, these vulnerabilities permit that legitimate APKs can be manipulated to replace the original code with arbitrary one without breaking the signature. This allows someone to take an update from a well known publisher (e.g. Google Maps), change the APK, and a device receiving it will happily apply the update as if it was indeed from that publisher. Depending on the apps being updated in this way, priviledge escalation can be achieved.
Google has already mentioned that all apps published on the Play Store are checked for this kind of manipulation, but those of us installing APKs from other sources aren't safe.
The universal fix
Since decompiling, fixing and recompiling the code for every possible ROM version is way beyond anyone's capability, the awesome Xposed framework by @rovo89 proves itself once again as an invaluable tool.
By creating hooks around the vulnerable methods and replacing the buggy implementation with a safe one, it's possible to patch the 2 issues on the fly without ever changing the original files. Applying the fix is as easy as installing and enabling an Xposed module.
Installation steps
1. Make sure the Xposed Framework is installed.
Follow the instructions on the thread. Root is required only during installation, it is no longer required afterwards. Only ICS or above is supported.
2. Install the Master Key multi-fix module.
3. Follow the Xposed notification about a new module being available, and on the list of modules activate Master Key multi-fix
4. Reboot
You should now see an image similar to the attached one when opening the app. The green text shows that the module is active and the vulnerabilities have been patched in memory.
Download
Grab it from Google Play (recommended, as you'll get updates) or use the attached APK. The files are the same.
Version history
2.0 - Fix bug 9950697; additional corrections taken from Android 4.4 (also supports GB, provided you have a working version of Xposed Framework for your ROM)
1.3 - Fixed problems with parsing some zips depending on the rom original code
1.2 - Added 2 additional zip entry integrity checks that were missing
1.1 - Support for additional devices with modified core libraries (e.g. MTK6589)
1.0 - Initial version
Sources
Available on GitHub
If you appreciated this fix, consider donating with Paypal.
Thanks!
FAQ
Fequently asked questions
[ 1 ]
Q: Bluebox Security Scanner still says my phone is unpatched after installing this... Any ideas why?
A: Make sure to click the Refresh entry on the app's menu and it should change to green once the mod is active.
[ 2 ]
Q: Bluebox Security Scanner says that the 2nd bug is not patched even after refreshing but SRT AppScanner says it's patched. Which one is right?
A: The scanner was mis-detecting the 2nd bug and it got fixed in version 1.5. Make sure you update Bluebox from the Play store.
[ 3 ]
Q: Does the module permanently patch the vulnerability or is it only when the module is active? If for example, I activate the module and reboot, then after verifying that the exploit is patched, deactivate the module. Would I still be patched? I guess what I'm asking is if I need to have this module active at all times to be patched? Permanent fix, or Just while the module is installed?
A: The fix is not permanent. It's applied only whenever the module is installed and active. If you remove it, after the next boot you're back with the original code from your ROM (which might have the bug or not).
Thank you, this would help a lot
Sent from my GT-I9500 using Tapatalk 4 Beta
Thank you but I don't see any link to the xposed patch app
Envoyé depuis mon LT28h en utilisant Tapatalk 4 Beta
Marsou77 said:
Thank you but I don't see any link to the xposed patch app
Click to expand...
Click to collapse
Have a look now
I needed to create the thread first in order to include the link on the app itself.
Thanks! I was just googling to see if someone had already done this before writing it myself!
XPosed is amazing sauce for Android.
The 4.1.2 update for the T-Mobile galaxy s3 is already patched.
Thanks for the info OP.
Maxamillion said:
The 4.1.2 update for the T-Mobile galaxy s3 is already patched.
Thanks for the info OP.
Click to expand...
Click to collapse
The second bug as well? Check java.util.zip.ZipEntry on /system/framework/core.jar and see if the readShort() values are properly converted to unsigned.
.....
Bluebox security still says my phone is unpatched after installing this... Any ideas why?
Sent from my HTC Sensation Z710e using xda app-developers app
Shredz98 said:
Bluebox security still says my phone is unpatched after installing this... Any ideas why?
Click to expand...
Click to collapse
No idea why it doesn't refresh automatically each time you execute the app, but access the Refresh option from the menu and it should change to green once the mod is active.
Tungstwenty said:
No idea why it doesn't refresh automatically each time you execute the app, but access the Refresh option from the menu and it should change to green once the mod is active.
Click to expand...
Click to collapse
Yeah you're correct mate, says patched when I rescanned so all good the patch does exactly what it says, brilliant work! Was beginning to think I would have to live with this security hole active on my device!
Sent from my HTC Sensation Z710e using xda app-developers app
Shredz98 said:
Yeah you're correct mate, says patched when I rescanned so all good the patch does exactly what it says, brilliant work! Was beginning to think I would have to live with this security hole active on my device!
Click to expand...
Click to collapse
Added to the FAQ (post #2)
Hey Everyone,
I've found an alternative for the blueboox app. It's called the SRT AppScanner and seems to work better than the BlueBox Scanner and it provides more functionality, too.
Since I'am a new user, i can't post links. Simply query SRT AppScanner in the PlayStore.
Best regards
Boradin
Thanks for great patch.
I've tested with SRT AppScanner and found I'm still vulnerable to bug 9695860.
How do I make sure bug 9695860 was fixed?
mnirun said:
Thanks for great patch.
I've tested with SRT AppScanner and found I'm still vulnerable to bug 9695860.
How do I make sure bug 9695860 was fixed?
Click to expand...
Click to collapse
When I initially installed SRT it was always giving me 2 greens even with the mod disabled, even though I checked the code for my ROM and the 2nd bug is there.
Now, after a very recent update, it always gives me a red on the second bug even with the mod active. I'll need to double check how they are doing the detection because it doesn't seem to be correct.
Bluebox Security, on the other hand, does reflect the change although it only detects the first bug. Running it on an emulator with a vulnerable ROM correctly said so, and after applying the mod and forcing a rescan it will change to no longer vulnerable.
SRT AppScanner has just received an additional update from Play and now appears to correctly detect the status of bug 9695860 depending on whether the mod is active or not and if your base ROM is vulnerable.
The sources are now available on GitHub (check 1st post).
Tungstwenty said:
SRT AppScanner has just received an additional update from Play and now appears to correctly detect the status of bug 9695860 depending on whether the mod is active or not and if your base ROM is vulnerable.
Click to expand...
Click to collapse
Confirmed, you patch is now detected by SRT AppScanner.
Thank you.
Tungstwenty said:
You may be aware of recent news about 2 different security vulnerabilities that allow replacing code on a signed APK without invalidating the signature:
Master Key (Bug 8219321)
An issue related with duplicate entries on the ZIP / APK files.
It was patched by Google back in February 2013 and shared with OEMs, and some of the newer devices might have already received the fix in a recent stock update. At least both Xperia Z 4.2.2 and Galaxy S2 4.1.2 contain the fix; CM has also recently patched it, on this commit.
An easy way to know if you're vulnerable is installing this app by Bluebox Security. Update: An ever better one is SRT AppScanner, which can detect both bugs.
More info can be found on @Adam77Root's thread here: http://forum.xda-developers.com/showthread.php?t=2359943
Bug 9695860
This also originates in the ZIP file parsing routines, and was disclosed just a few days ago immediately after the previous one was made public. The correction has already been applied by Google to the code (this commit), but it's very likely that its rollout on stock ROMs will take a long time especially on non-Nexus devices.
You can read more about it here.
To know if you're vulnerable, use SRT AppScanner mentioned above.
Unless you're running CM 10.1.2, there's a fairly big chance that you have this issue, at least as of this moment.
While technically different, both of these vulnerabilities permit that legitimate APKs can be manipulated to replace the original code with arbitrary one without breaking the signature. This allows someone to take an update from a well known publisher (e.g. Google Maps), change the APK, and a device receiving it will happily apply the update as if it was indeed from that publisher. Depending on the apps being updated in this way, priviledge escalation can be achieved.
Google has already mentioned that all apps published on the Play Store are checked for this kind of manipulation, but those of us installing APKs from other sources aren't safe.
The universal patch
Since decompiling, fixing and recompiling the code for every possible ROM version is way beyond anyone's capability, the awesome Xposed framework by @rovo89 proves itself once again as an invaluable tool.
By creating hooks around the vulnerable methods and replacing the buggy implementation with a safe one, it's possible to patch the 2 issues on the fly without ever changing the original files. Applying the fix is as easy as installing and enabling an Xposed module.
Installation steps
1. Make sure the Xposed Framework is installed.
Follow the instructions on the thread. Root is required only during installation, it is no longer required afterwards. Only ICS or above is supported.
2. Install the Master Key dual fix module.
3. Follow the Xposed notification about a new module being available, and on the list of modules activate Master Key dual fix
4. Reboot the device (a Soft reboot is sufficient)
You should now see an image similar to the attached one. The green text shows that the module is active and the 2 vulnerabilities have been patched.
Download
Grab it from Google Play or use the attached APK.
Sources
Available on GitHub
If you appreciated this fix, consider donating with Paypal.
Thanks!
Click to expand...
Click to collapse
Thank you for this patch, but can we install this mod over "REKEY" patch or remove rekey and enable this patch instead ??
An Xposed module to disable SSL verification and pinning on Android using the excellent technique provided by Mattia Vinci.
The effect is system-wide.
Useful for various security audits.
GitHub repository | Xposed repository
Nice module. Could this be done in Magisk?
ViRb3 said:
An Xposed module to disable SSL verification and pinning on Android using the excellent technique provided by Mattia Vinci.
The effect is system-wide.
Useful for various security audits.
GitHub repository | Xposed repository
Click to expand...
Click to collapse
Okay, but why would I want to disable it and what is pinning?
Posted from my way cool LG V20 (H910) Nougat 7.0
joluke said:
Nice module. Could this be done in Magisk?
Click to expand...
Click to collapse
Probably, but that would be very overkill. The EdXposed framework (which can load this module) is based on Magisk and passes SafetyNet, check it out.
Zeuszoos said:
Okay, but why would I want to disable it and what is pinning?
Posted from my way cool LG V20 (H910) Nougat 7.0
Click to expand...
Click to collapse
It comes into play when analyzing encrypted traffic from apps, e.g. malware. First, here's some resources that explain how to analyze traffic: https://en.wikipedia.org/wiki/Man-in-the-middle_attack, https://security.stackexchange.com/...ent-man-in-the-middle-attacks-by-proxy-server
Basically, you would need to proxy traffic to your computer and replace the server certificate with your own one (that you can decrypt). However, Android won't recognize that homemade certificate and reject it. To prevent this, sometimes you can import it in your phone's settings. But then there's certificate pinning, which forces an app to use ONLY the specified certificate and nothing else. So even if you add your hommade certificate to the trusted list, it will still be different and thus rejected. This module gets rid of both problems by making Android accept any certificate without verification. Needless to say, this is extremely insecure, but for our purposes it saves a ton of effort
Thanks you very much for this! I love it, I can see all the ssl data
not working for *.googleapis.com, any idea?
Hello vibr3,
I appreciate your great work on that script. I'm on FOS 6.0 on firetv 4k, I installed the module in xposed but running it wouldn't do anything. It seems like it's not working probably on my SDK25, android 7.1.
I've been using your awesome module (alongside Fiddler/CharlesProxy) for the past couple of weeks, and it's been working perfectly for a couple of apps that I needed to reverse engineer.
However, some apps (e.g. Instagram) won't accept the CA certificate that I use (self signed, user-installed). Is there anything I can do to be able to decrypt traffic for these kind of apps?
I use LineageOS 14.1
DRSDavidSoft said:
I've been using your awesome module (alongside Fiddler/CharlesProxy) for the past couple of weeks, and it's been working perfectly for a couple of apps that I needed to reverse engineer.
However, some apps (e.g. Instagram) won't accept the CA certificate that I use (self signed, user-installed). Is there anything I can do to be able to decrypt traffic for these kind of apps?
I use LineageOS 14.1
Click to expand...
Click to collapse
Same question for YouTube app
Is there any method to bypass certificate verification for nonroot. ?
@ViRb3
Could you advice me please? If i disable certificate pinning using your application but still don't see the requests in the fiddler where can be a problem?
What is it that when I try to use this, it says the app cannot be on the deny list. What if the app is root protected and ssl pinning enabled at the same time?
Hi, I am the author of VirtualXposed: https://forum.xda-developers.com/xposed/virtualxposed-xposed-root-unlock-t3760313
VirtualXposed can run some Xposed modules on Non-Root devices without needing to unlock the bootloader or flash any sysytem images, but it can not act on system processes.
After a lot of exploration and experiment, I found a better way to run (Xposed) modules. It can run on both root and non-root devices, and it support Android 5.0 ~ 10.0 I release the beta version in China at 2019/1/5, after many tests and improvements, it is stable enough now to introduce it for you.
The app, or framework is named TaiChi
## Introduction
TaiChi is a framework to use Xposed module with or without Root/Unlock bootloader, it support Android 5.0 ~ 9.0.
In simple words, TaiChi is Xposed-Styled Framework, it can load Xposed modules, do hooks and so on.
## Feature
TaiChi is Xposed-Styled, but it has no relation with Xposed. The only relevance is that TaiChi can load Xposed modules, the implementation of TaiChi and Xposed Framework is very different.
Here are some features of Taichi:
1. TaiChi has fully supports for Android Pie.
2. TaiChi can run in non-root mode.
3. TaiChi does not effect the android system and it does not hook all apps in system. Only the apps you want to apply Xposed modules are hooked. Other apps in system run in a completely clean environment, which means TaiChi can pass SafeNet easily.
4. TaiChi doesn't need to reboot system in most cases
5. TaiChi is hard to detect. TaiChi doesn't modify the libart and app_process, it has nearly no noticeable characteristics.
## Usage
TaiChi has two work mode: magisk mode and non-root mode. If you don't want to unlock the bootloader/flash system images, you can use the non-root mode, if you prefer more powerful functions, just try magisk mode.
### What is the different with magisk mode and non-root mode?
The only difference is that magisk mode can hook system process, so more modules are supported, such as Xposed Edge/Greenify.But magisk mode need to unlock the bootloader and install Magisk, while non-root mode just needs to install a simple app.
### Non-Root mode
TaiChi run in non-root mode in genernal, just install a simple app, all the installation is over. If you want to use Xposed modules, for example, you'd like to use SnapFreedom on SnapChat, follow these steps:
1. Click the float button in Home page of TaiChi, and then click the button : **Create App**.
2. Select the app you'd like to apply Xposed modules, such as SnapChat.
3. Click the "Create" button at the bottom and then wait the creation to finish pariently.
4. When creation finished, TaiChi tells you that you need to unstall the original SnapChat, please uninstall it, this is necessary. Because TaiChi in non-root mode needs to modify the APK file which means we have to re-sign the APK.
5. Follow the steps in TaiChi app until you installed the new app.
6. Enter the **Module Manage** activity by click the button "Module Manager" of the float button in Home page.
7. Check the SnapFreedom module.
8. Kill the process of SnapChat and the Xposed modules should work properly.(You don't need to reboot system)
### Magisk mode
Non-root mode of TaiChi has some shortcomming even though it do not need to unlock bootloader, so i develop a magisk module, this module can give TaiChi extra power to overcome these shortcommings:
1. magisk mode can hook into system process.
2. magisk mode don't need to modify the apk, and the signature keeps same.
When you flashed the [magisk module]https://github.com/tiann/TaiChi-Magisk provided by TaiChi, TaiChi app switch to magisk mode automaticly: TaiChi App + magisk module = TaiChi·Magisk. When the magisk module is disabled or removed, TaiChi app turn to non-root mode.
If you want to use magisk mode, please read the [wiki](https://github.com/tiann/Tai-Chi/wiki/taichi-magisk-beta) carefully.
## For Developers
TaiChi is a Framework, developers can wrote modules to do hooks. The TaiChi modules is fully compatible to Xposed modules, so just wrote the Xposed-Styled modules and it can run well in TaiChi, too.
But there are still some difference from TaiChi Framework and Xposed Framework, please refer [For Xposed Developers]https://github.com/tiann/Tai-Chi/wiki/For-Xposed-developer
## Discuss
- [Telegram Group](https://t.me/vxp_group)
## Contact me
(mailto:[email protected])
[B]## Other [/B]
1. TaiChi is closed-source now, it may be open-sourced in the future, but not now.
2. TaiChi can not run Xposed modules arbitrarily(it supports it in technical-speaking), it can only run specific version and specific modules now. If you want to use other modules, please fire an issue. Here is the support list: https://taichi.cool/module/module.html
3. TaiChi is compatible to Xposed modules, but it may have its own module in the future.
[B][U][SIZE="4"][PLAIN]XDAevDB Information[/PLAIN][/SIZE][/U][/B]
[SIZE=3][B]TaiChi, Xposed for all devices (see above for details)[/B][/SIZE]
[B][U]Contributors[/U][/B]
[URL="https://forum.xda-developers.com/member.php?u=8994560"]weishu[/URL], [URL="https://forum.xda-developers.com/member.php?u=8994560"]weishu[/URL]
[B]Source Code:[/B] [URL="https://github.com/taichi-framework"]https://github.com/taichi-framework[/URL]
[B]Xposed Package Name:[/B]
[B][U]Version Information[/U][/B]
[B]Status:[/B] Stable
[B]Created[/B] 2019-03-11
[B]Last Updated[/B] 2019-03-16
I noticed the magisk module today on the repo. Sounds very promising and... tempting to me.
But, regardless of how much I'd love to finally have xposed modules on pie, there's one major deal-breaker here: Closed source.
TaiChi magisk (as well as xposed) are extremely mighty - which makes it mandatory for us to see and confirm what's happening behind the curtains.
As soon as it gets open source, I'll be back and support this project.
Sent from my OnePlus 6 using XDA Labs
weishu said:
TaiChi run in non-root mode in genernal, just install a simple app, all the installation is over. If you want to use Xposed modules, for example, you'd like to use SnapFreedom on SnapChat, follow these steps:
1. Click the float button in Home page of TaiChi, and then click the button : **Create App**.
2. Select the app you'd like to apply Xposed modules, such as SnapChat.
3. Click the "Create" button at the bottom and then wait the creation to finish pariently.
4. When creation finished, TaiChi tells you that you need to unstall the original SnapChat, please uninstall it, this is necessary. Because TaiChi in non-root mode needs to modify the APK file which means we have to re-sign the APK.
5. Follow the steps in TaiChi app until you installed the new app.
6. Enter the **Module Manage** activity by click the button "Module Manager" of the float button in Home page.
7. Check the SnapFreedom module.
8. Kill the process of SnapChat and the Xposed modules should work properly.(You don't need to reboot system)
Click to expand...
Click to collapse
Thanks for this great module, its nice to know there is hope for our locked bootloader devices.
I want to use snapfreedom, but the above steps wont actually work, snapchat will refuse to log me in since the signature of the apk has changed and its been uninstalled so my data is gone. Without root access I can't figure a way to copy my user data over to remain logged in. Any ideas would be greatly appreciated!
flamery said:
Thanks for this great module, its nice to know there is hope for our locked bootloader devices.
I want to use snapfreedom, but the above steps wont actually work, snapchat will refuse to log me in since the signature of the apk has changed and its been uninstalled so my data is gone. Without root access I can't figure a way to copy my user data over to remain logged in. Any ideas would be greatly appreciated!
Click to expand...
Click to collapse
The SnapChat itself refused you to login or other app can not login by Snapchat?
In fact, TaiChi non-root mode cheats the signature of app, if it cannot cheats SnapChat, i will look into it.
Depressed T.Bear said:
I noticed the magisk module today on the repo. Sounds very promising and... tempting to me.
But, regardless of how much I'd love to finally have xposed modules on pie, there's one major deal-breaker here: Closed source.
TaiChi magisk (as well as xposed) are extremely mighty - which makes it mandatory for us to see and confirm what's happening behind the curtains.
As soon as it gets open source, I'll be back and support this project.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
In fact, I’ve been tangled for a long time whether to open source the TaiChi.
Whether it's TaiChi or Xposed-Framework, they are so powerful that it's hard to believe its security if it's not open source. But there are some reasons for me to not open source it now:
1. TaiChi is a framework, it gives the same power to modules, modules can do all that TaiChi can do. In magisk-mode, TaiChi can control your device completely(Although I didn't do that), so dose the modules. If TaiChi is open-source but some modules don't, it is not secure too. You can choose to use only open-source modules, but others may not. There are so many excellent modules are closed-source, such as Greenify, Xposed Edge, Snapchat, etc. Only open source TaiChi is far from security if some module developer are malicious.
2. Open source doesn't mean security. VirtualXposed is open-source: https://github.com/android-hacker/VirtualXposed . But if you read the XDA Thread of it: https://forum.xda-developers.com/xpo...nlock-t3760313 . There are still so many users thinks it is not safe to use
Depressed T.Bear said:
I noticed the magisk module today on the repo. Sounds very promising and... tempting to me.
But, regardless of how much I'd love to finally have xposed modules on pie, there's one major deal-breaker here: Closed source.
TaiChi magisk (as well as xposed) are extremely mighty - which makes it mandatory for us to see and confirm what's happening behind the curtains.
As soon as it gets open source, I'll be back and support this project.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
In fact, I’ve been tangled for a long time whether to open source the TaiChi.
Whether it's TaiChi or Xposed-Framework, they are so powerful that it's hard to believe its security if it's not open source. But there are some reasons for me to not open source it now:
1. TaiChi is a framework, it gives the same power to modules, modules can do all that TaiChi can do. In magisk-mode, TaiChi can control your device completely(Although I didn't do that), so dose the modules. If TaiChi is open-source but some modules don't, it is not secure too. You can choose to use only open-source modules, but others may not. There are so many excellent modules are closed-source, such as Greenify, Xposed Edge, Snapchat, etc. Only open source TaiChi is far from security if some module developer are malicious.
2. Open source doesn't mean security. VirtualXposed is open-source: https://github.com/android-hacker/VirtualXposed . But if you read the XDA Thread of it: https://forum.xda-developers.com/xpo...nlock-t3760313 . There are still so many users thinks it is not safe to use.
Depressed T.Bear said:
I noticed the magisk module today on the repo. Sounds very promising and... tempting to me.
But, regardless of how much I'd love to finally have xposed modules on pie, there's one major deal-breaker here: Closed source.
TaiChi magisk (as well as xposed) are extremely mighty - which makes it mandatory for us to see and confirm what's happening behind the curtains.
As soon as it gets open source, I'll be back and support this project.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
In fact, I’ve been tangled for a long time whether to open source the TaiChi.
Whether it's TaiChi or Xposed-Framework, they are so powerful that it's hard to believe its security if it's not open source. But there are some reasons for me to not open source it now:
1. TaiChi is a framework, it gives the same power to modules, modules can do all that TaiChi can do. In magisk-mode, TaiChi can control your device completely(Although I didn't do that), so dose the modules. If TaiChi is open-source but some modules don't, it is not secure too. You can choose to use only open-source modules, but others may not. There are so many excellent modules are closed-source, such as Greenify, Xposed Edge, Snapchat, etc. Only open source TaiChi is far from security if some module developer are malicious.
2. Open source doesn't mean security. VirtualXposed is open-source: https://github.com/android-hacker/VirtualXposed . But if you read the XDA Thread of it: https://forum.xda-developers.com/xpo...nlock-t3760313 . There are still so many users thinks it is not safe to use. When it is closed-source, users think it is insecure becuase it is not open-source, when you open source it, users think it is insecure becuase no one to review the huge and ****-source code.
3. Xposed-Framework is not open-source after Android O, too. (correct me if i am wrong)
4. Closed-source can provide security for normal users. Closed source means that TaiChi can restrict the ****ing and harmful modules run in TaiChi(it won't load unknown modules). And also, The module developer won't worry about crack( it won't load the re-signed modules).
Happy to hear from all your advices.
weishu said:
In fact, I’ve been tangled for a long time whether to open source the TaiChi.
Whether it's TaiChi or Xposed-Framework, they are so powerful that it's hard to believe its security if it's not open source. But there are some reasons for me to not open source it now:
1. TaiChi is a framework, it gives the same power to modules, modules can do all that TaiChi can do. In magisk-mode, TaiChi can control your device completely(Although I didn't do that), so dose the modules. If TaiChi is open-source but some modules don't, it is not secure too. You can choose to use only open-source modules, but others may not. There are so many excellent modules are closed-source, such as Greenify, Xposed Edge, Snapchat, etc. Only open source TaiChi is far from security if some module developer are malicious.
2. Open source doesn't mean security. VirtualXposed is open-source: https://github.com/android-hacker/VirtualXposed . But if you read the XDA Thread of it: https://forum.xda-developers.com/xpo...nlock-t3760313 . There are still so many users thinks it is not safe to use
Click to expand...
Click to collapse
I think it is a pretty weak reasoning to not make the framework open source because the modules are closed source.
Both open and closed source do not mean security, so this is not a real argument either.
So, it lets me just wondering what the real reason is to not open source.
weishu said:
The SnapChat itself refused you to login or other app can not login by Snapchat?
In fact, TaiChi non-root mode cheats the signature of app, if it cannot cheats SnapChat, i will look into it.
Click to expand...
Click to collapse
Its the login to snapchat, they have very high security around 3rd party apps and app modding. If the apk has been modified you get the "login has temporarily failed" message when trying to login.
The workaround in the past has been to login with xposed disabled, titanium backup data, flash xposed, then restore data so you remain logged in. But there is no way to achieve that without root that I can see! thanks for looking into it!
so how do i enable the Magisk module?
Just tried Taichi today and it instantly bring the good old days for me with Xposed. I need to have certain Apps to run in different locale and Xposed module is to the only way to get this done! However Xposed also stopped Google pay so I have to stop using Xposed ever since.
With Taichi I can start use Xposed again and have Google Pay at the same time... Great solution!
Unfortunately with current international politics it immediately mark anything from China as insecure. I am not sure if TaiChi is secure or not, but I guess since the day I rooted my phone I am assuming all the risk inherited.
Anyway good work! Weishu! (Just donated)
Hmm I must be high on something because I dont see the download link.
woomera said:
Hmm I must be high on something because I dont see the download link.
Click to expand...
Click to collapse
Check the magisk manager downloads section.
@weishu , I hope you can help. I've purchased xprivacylua pro from the google play store some time ago and reinstalled it on Pie. Xprivacylua pro does not seem to recognize xprivacylua is installed also. Do you have any suggestions?
dirtyreturn said:
@weishu , I hope you can help. I've purchased xprivacylua pro from the google play store some time ago and reinstalled it on Pie. Xprivacylua pro does not seem to recognize xprivacylua is installed also. Do you have any suggestions?
Click to expand...
Click to collapse
It sounds like you misunderstood something. The "Pro" app from. Google Play is just a companion app, which enables the pro features you bought. It doesn't contain the actual xposed module (and app) of xprivacy Lua.
Simply download it through the xposed repo or get the latest apk directly from the xprivacy lua website.
Sent from my OnePlus 6 using XDA Labs
Depressed T.Bear said:
It sounds like you misunderstood something. The "Pro" app from. Google Play is just a companion app, which enables the pro features you bought. It doesn't contain the actual xposed module (and app) of xprivacy Lua.
Simply download it through the xposed repo or get the latest apk directly from the xprivacy lua website.
Click to expand...
Click to collapse
Thanks for the reply. I just assumed by my post it would make sense.
I do have the taichi magisk module installed, and from there I've installed xprivacylua. And from the google play store the pro companion app. @Depressed T.Bear - are you using xprivacylua on Pie? Does the pro app recognize the main app as installed for you?
Depressed T.Bear said:
It sounds like you misunderstood something. The "Pro" app from. Google Play is just a companion app, which enables the pro features you bought. It doesn't contain the actual xposed module (and app) of xprivacy Lua.
Simply download it through the xposed repo or get the latest apk directly from the xprivacy lua website.
Click to expand...
Click to collapse
Please see screenshots.
dirtyreturn said:
Thanks for the reply. I just assumed by my post it would make sense.
I do have the taichi magisk module installed, and from there I've installed xprivacylua. And from the google play store the pro companion app. @Depressed T.Bear - are you using xprivacylua on Pie? Does the pro app recognize the main app as installed for you?
Click to expand...
Click to collapse
Then it might be due to TaiChi.
Yes, I'm using XPrivacyLua on Pie - but with EdExposed and not with TaiChi. For one simple reason: TaiChi is not open source! EdExposed and RiruCore instead are.
So it would be absolute nonsense to use an app like XPrivacyLua to protect your privacy, while using a xposed version with is closed-source and nobody can tell what it actually does.
So, I can't help you with TaiChi. Only the developer can.
All I can say is that it works flawlessly with EdExposed.
Sent from my OnePlus 6 using XDA Labs
I have edxposed but I'm thinking of trying Taichi out to see if it's more stable. Will this work with modules such as xposed edge where the module doesnt target a specific app?
Soumy1234 said:
I have edxposed but I'm thinking of trying Taichi out to see if it's more stable. Will this work with modules such as xposed edge where the module doesnt target a specific app?
Click to expand...
Click to collapse
Your question is answered clearly in the first post
Sent from my OnePlus 6 using XDA Labs
MAGISK Module which does this job:
I found a magisk module which does the same work explained in this thread.
Module Link: Download here
SOURCE:
Github Download link: HERE
Gitgub source code link: HERE
< ALTERNATIVELY IF YOU WANT TO DO IT YOURSELF, FOLLOW THE STEPS BELOW >
Pre-Requites:
a. Device rooted with magisk 19.4+
b. Teminal Emulator installed (Link)
b. SQL database editor is installed (Link)
Steps:
1. Force close Google Pay app (just in case). If you have disabled this app, enable it before continue and force close)
2. Open SQL editor and go to File explorer in the app. Navigate to /data/data/com.google.android.gms/databases
3. Open dg.db and go to main
4. You will see entries "attest" (not "ad_attest"), long press and select Edit and change value under C (which is 3rd column) to 0. Mine was showing a value of 10 in the third column for each of these values. (Column c for sqlite database editor I used)
5. Open Terminal emulator.
6. Get root access (su) (i.e type su and ENTER)
7. Now type cd /data/data/com.google.android.gms/databases and ENTER
8. Type chmod 440 dg.db ENTER. This makes dg.db read only so that it will not over written and you can continue to use Google Pay.
9. Reboot your device and enjoy Google Pay.
Note: When gms is updated, you have to change chmod value for dg.db via terminal emulator (i.e type chmod 660 dg.db) to get write permission. Now follow all the steps to change value to 0 and change chmod to 440
Thanks to @BostonDan for the thread https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Nice Man... First method that actually worked for me. I am on Android 10 Xiaomi.eu latest
Serbinhio said:
Nice Man... First method that actually worked for me. I am on Android 10 Xiaomi.eu latest
Click to expand...
Click to collapse
Hi
Glad to hear that it worked for you. I changed my phone from OP5 to this device and GPay was not working until modded as explained in OP. It is very handy that I don't have to carry my wallet all the time.
You only need to do step 8, the rest isn't required.
nahsha said:
You only need to do step 8, the rest isn't required.
Click to expand...
Click to collapse
I have never tested with attest value being 10.
Do you mean, with attest value 10 and change to write permission of dg.db to 440 makes Gpay to work?
If this is the case, I agree that only step 8 is enough.
Thanks.
Its working, thanks
Congrats
Good job man. Works well with MIUI Global 11.0.3.0 (QFAMIXM) and latest Android 10.
Thanks
I flashed MIUI 11 Beta version (xiaomi.eu version) weekly update v9.12.5. I can see that CTS profile and basic integrity passes. Also, I can see that Device certified in Google Play settings. But GPay was reporting that device is rooted hence GPay could not work.
I went through following attempts to make it work.
Attempt 1:
Flashed magisk module Safety Patcher. GPay didn't work.
Attempt 2:
Removed Safety Patcher and flashed MagiskHide Props config modules. Used certified fingerprint for xiaomi mi9. GPay didn't work.
Attempt 3:
Removed all magisk modules mentioned above. Went through the method mentioned in this thread. GPay is working now.
Though this thread is made by me, I was lazy enough to go through the steps and that's why wanted to use something readily made like Safety Patcher or MagiskHide Props config).
Hope this update helps.
Working great on latest stable Miui.eu.
Thanks!.
It works great on latest Revolution OS.
Thank You!
Instead of:
a) Uploading a single release of my module to androidfilehost (which will mean anyone using that will likely never know theres an update)
b) Link to my actual releases page, but to a specific release (which will mean anyone using that will likely never know theres an update)
c) Incorrectly linking a source link to the releases page (the source is available as a zip option alongside the module zip for every release)
d) Omitting that the module relies on an sqlite3 binary being present on the device BEFORE installing the GPay SQL Fix module (not sure if your device by default has an sqlite3 binary, in any event in my OP for my module in BostonDan's thread i offer one universal SQLite package to test for this and if necessary, install one)
e) Omitting a link to my OP in BostanDan's thread so people can see the correct install procedure (it matters), keep up to date with important info, warnings, changelogs, and things such as extra steps necessary of using say edXposed....
I would suggest (In other words, your linking is bad, and youre only passing on part of the story in referencing my module):
1) A link to my OP in BostanDans thread:
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
2) A link the releases page for my module (it will always link to the latest release this way)
GPay SQLite Fix:
release: https://github.com/stylemessiah/GPay-SQLite-Fix/releases/latest
3) A link to the SQLite3 binary module
SQLite3 Universal Binaries v1.0 (installs to /system/xbin if exists, otherwise .system/bin) here:
release: https://github.com/stylemessiah/SQLite3-Universal-Binaries/releases/latest
4) Remove the source link, its unnecessary
Cheers
73sydney said:
Instead of:
a) Uploading a single release of my module to androidfilehost (which will mean anyone using that will likely never know theres an update)
b) Link to my actual releases page, but to a specific release (which will mean anyone using that will likely never know theres an update)
c) Incorrectly linking a source link to the releases page (the source is available as a zip option alongside the module zip for every release)
d) Omitting that the module relies on an sqlite3 binary being present on the device BEFORE installing the GPay SQL Fix module (not sure if your device by default has an sqlite3 binary, in any event in my OP for my module in BostonDan's thread i offer one universal SQLite package to test for this and if necessary, install one)
e) Omitting a link to my OP in BostanDan's thread so people can see the correct install procedure (it matters), keep up to date with important info, warnings, changelogs, and things such as extra steps necessary of using say edXposed....
I would suggest (In other words, your linking is bad, and youre only passing on part of the story in referencing my module):
1) A link to my OP in BostanDans thread:
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
2) A link the releases page for my module (it will always link to the latest release this way)
GPay SQLite Fix:
release: https://github.com/stylemessiah/GPay-SQLite-Fix/releases/latest
3) A link to the SQLite3 binary module
SQLite3 Universal Binaries v1.0 (installs to /system/xbin if exists, otherwise .system/bin) here:
release: https://github.com/stylemessiah/SQLite3-Universal-Binaries/releases/latest
4) Remove the source link, its unnecessary
Cheers
Click to expand...
Click to collapse
Have been using this module for months and I can't thank you enough to make GPay work with such an automated method.
Quick suggestion - why don't you start a new post with your work instead of letting it hide in reply #176 of another thread? You can always include a link back to the original post to give credit.
Cheers ! Thanks again !!!
seemebreakthis said:
Have been using this module for months and I can't thank you enough to make GPay work with such an automated method.
Quick suggestion - why don't you start a new post with your work instead of letting it hide in reply #176 of another thread? You can always include a link back to the original post to give credit.
Cheers ! Thanks again !!!
Click to expand...
Click to collapse
I didnt invent the method, i just repackaged it to make it a little easier for those who wanted to try it...
So i didnt move it into its own thread because i felt it might be disrespectful to BostanDan, i just repackaged his and others work, seemed only right to at least keep it where it started.
At least you didnt ask why its not in the repo, i get tired of telling THAT story
Wow, stumbled on this thread and was struggling to get GPay succesfully activated using all other tricks mentioned online. This one does actually work!
Yove just made my day, thank you!
Version for Marshmallow is available here: https://forum.xda-developers.com/t/...zation-for-old-touchwiz-mm-framework.3372401/
Version for Nougat is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-n-framework.3692391/
Version for Oreo is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-o-framework.3749479/
Version for Pie is available here: https://forum.xda-developers.com/t/...-14-customize-samsung-oneui-24-05-20.3908114/
Version for Q is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-2-0-30-12-20.4044757/
Version for R is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-3-x-14-03-21.4212051/
Firefds Kit [ S ]
Xposed module for Samsung S devices.
Known working devices:
Galaxy S20
Galaxy S20
Galaxy S10
Features
The module has the following features:
Fake system status to Official
Custom advanced power menu options:
Power off
Restart
Emergency mode
Recovery (with custom text)
Download
Data mode switch
Screenshot
Switch User (when multi user is enabled)
SystemUI restart
Flashlight
Screen Recorder (requires Samsung screen recorder app installed)
Disable restart confirmation
Enable performing power menu reboot / power off actions only after unlocking secure lock screen (stock behavior)
Disable display of power menu when secure lockscreen is locked
Change default behavior of reboot to reboot to recovery
Replace Reboot to Recovery icon with system default restart icon
Enable call recording and call recording settings
Replace add call button instead of call recording and adding record by menu option
Clock Size option
Enable Call ID and spam protection option
Enable Screen Record tile and Settings options
Enable screen record while in call
Enable additional advanced hotspot settings option
Hide VoLTE icon in status bar
Hide persistent USB connection notification
Hide persistent charging notification
Enable block phrases in messages app settings
Enable native blur on notification panel pull down
Enable multi user toggle
Set max user value selector
Show seconds in status bar clock toggle
Show AM/PM for seconds on clock toggle
Show clock date on right of clock toggle
Add date to status bar clock options
Enable fingerprint unlock on reboot toggle
Enable biometrics unlock on reboot toggle
Add network speed menu to show network speed in the status bar
Data icon symbol selection (4G, LTE, 4G+, 4.5G)
Show Data usage view in quick panel
Double tap for sleep
Hide NFC icon
Disable Bluetooth toggle popup
Disable sync toggle popup
Disable high level brightness popup
Hide carrier label
Carrier label size selection
Disable loud volume warning
Disable volume control sound
Disable low battery sound
Screen timeout settings
NFC behavior settings
Auto MTP
Disable camera temperature check
Enable camera shutter sound menu
Disable call number formatting
Disable SMS to MMS threshold
Force MMS connect
Bypass exchange security (currently not working)
Disable signature check
Disable secure flag
Attention
This version was tested by the community and not by me, as I don't have an Android 12 Samsung device.
THERE COULD BE BUGS/CRASHES/BOOTLOOPS, but it's pretty stable.
Please upload any xposed logs when you encounter any issue. I can't help you without the logs!
Installation
To install this module you need the following apps and modules installed on your device:
Magisk v24.0 and above - https://github.com/topjohnwu/Magisk/releases
Option 1 - Zygisk
LSPosed Magisk Zygisk Release module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Option 2 - Riru
LSPosed Magisk module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Riru Magisk module v25.0.0 and above - https://github.com/RikkaApps/Riru/releases
Download
Directly from LSPosed Manager or from Github : https://github.com/Xposed-Modules-Repo/sb.firefds.s.firefdskit/releases
Source Code
https://github.com/Firefds/FirefdsKit/tree/S
Known Issues
A lot has changed since Android 11. Since I don't have an Android 12 device all tests have been done with various testers. THERE MAY BE UNKNOWN ISSUES!!
Some features are removed on purpose. Since GravityBox has been working on Samsung Oreo devices without much issues, I only implemented features that need special Samsung coding.
Reporting Issues
When reporting an issue, please include Xposed logs and screenshots if any. Reporting should be done through Github - https://github.com/Firefds/FirefdsKit/issues
External Libraries
The project uses the following libraries:
https://github.com/rovo89/XposedBridge
https://github.com/rovo89/XposedMods/tree/master/XposedLibrary
Samsung framework libraries which are used for compile only
EdXposed Whitelisting
Users who want to use EdXposed's whitelist feature should whitelist the following apps:
Android System - android
Call - com.samsung.android.incallui
Call Settings - com.samsung.android.app.telephonyui
Camera - com.sec.android.app.camera
Contacts - com.samsung.android.contacts
Email - com.samsung.android.email.provider
Firefds Kit - sb.firefds.s.firefdskit
Messaging - com.samsung.android.messaging
MTP Application - com.samsung.android.MtpApplication
NFC - com.android.nfc
One UI Home - com.sec.android.app.launcher
Settings - com.android.settings
Smart Capture - com.samsung.android.app.smartcapture
Software Update - com.wssyncmldm
System UI - com.android.systemui
Credits
This module wouldn't have been here without the following people:
RikkaW - Creator of Riru Magisk module, which provides a way to inject codes into zygote process
@rovo89 - Creator of the original Xposed framework APIs
solohsu and MlgmXyysd - Creators of the EdXposed Magisk module and Installer that made all of this possible
@C3C076 - Creator of GravityBox Xposed modules, which I learnt a lot from
@wanam - Creator of the original XTouchWiz module, which this module is based on.
@topjohnwu - Creator of Magisk
@AbrahamGC - For the Extended Power Menu - Pie - Odex framework Smali guide
Big thank you to @m8980 and @ianmacd for testing countless versions and sending xposed logs
Telegram
Announcements and pre release versions - https://t.me/firefdskit
This is a moded version of Wanam's XTouchWiz:
https://github.com/wanam/XTouchWiz
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
okij said:
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
Click to expand...
Click to collapse
Thanks! This looks great! I'll add it to the next version
firefds said:
Thanks! This looks great! I'll add it to the next version
Click to expand...
Click to collapse
Thanks! I'm glad you like it and look forward to the next version.
IIRC Firefds Kit 11 uses the same icons (I have been using it until I switched to Android 12 two months ago), so you might use the new icons there too.
Thanks.
All my devices now bootloop with NoClassDefFoundError: com.android.systemui.BasicRune
Any chance we could add those whitelists to LSposed "Recommended"? Exactly the most important call recording check is missing.
Btw if LSposed 1.7.2 is installed, Riru can be uninstalled? -> looks like Sui uses Riru, so no switching.
In the end, I could leave Firefds enabled if I don't change anything, luckily call recording is on by default.
Thanks for the update for Android 12. Everything working good on my A52s 5g. Hope that one day you can add the ability to adjust the height of the navigation bar. That was available in the gravitybox app but there is no upgrade for 12 yet and not sure there will be which is why I've asked here... appreciate your efforts though.
Is there an easy way to fix bootloop in case something went wrong?
donkeyman1234 said:
Is there an easy way to fix bootloop in case something went wrong?
Click to expand...
Click to collapse
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me delete it worked and I didn't have to disable lsposed modules or the magisk
Kuba1996 said:
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me it worked and I didn't have to disable lsposed modules or the magisk
Click to expand...
Click to collapse
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
donkeyman1234 said:
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
Click to expand...
Click to collapse
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root without custom recovery?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
You can look at last post here and try do something like that. Mabye try in recovery choose "update from adb" and try erase with adb command (your directory: riru-core). Or try use this but I dont think it will work
[Tool][Aroma] Magisk Manager Recovery Tool V2.5
Warning: It's not a Magisk module! Description This is a Magisk module management tool that can be used in Recovery mode. It's based on Aroma Installer. You can manage almost everything in Magisk with this tool. You can manage installed modules...
forum.xda-developers.com
Kuba1996 said:
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root witchout custom recovery?
Click to expand...
Click to collapse
I used magisk patched AP file to root. There is no twrp for s22u.
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Also You can flash in odin patched ap and rest of file but with HOME_CSC not CSC
Check this:
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Had the same issue with my s22u. I reflashed through odin. Gonna try and flash this module again with magisk bootloop protector. fingers crossed.
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Hello,
Thank you for A12 update.
So nice to have your magic on this version.
I would also love to see the ability to adjust navbar, and the possibility to move cursor with buttons in navbar like in GravityBox.
For me, Force MMS to connect isn't working on BeyondRom 4.1.
Is it working for others ?
I am using LSPosed zygist latest version and safety net 2.2.1
nishantgupta107 said:
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Click to expand...
Click to collapse
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
doggydog2 said:
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
Click to expand...
Click to collapse
Yes, some os settings did get reset. Not sure why. But now I'll wait for a stable release (I have reflashed it now 5-6 times)
Arobase40 said:
You can install Magisk Bootloop Protector module...
It will disable Magisk modules when bootloop occurs.
Click to expand...
Click to collapse
Thanks. I did install, but it did not work, the phone kept rebooting, reflash was my last resort.
Bootloop
S10 plus UI 4.1 A12
LSPosed-v1.8.0-6482-zygisk