LSPosed Xposed Framework [8.1-13.0]. Simple Magisk Module

What Xppsed Framework are You Using??

  • Total voters
    1,567
Search This thread
By:
Advanced…
J

jons99

Senior Member
Nov 5, 2019
347
382
amritpal2489 said:
Guys... I am facing an issue. When I install the LSPosed magisk module.. the status bar notification is shown but when I touch it nothing opens.. I think the manager app crashes... Same with ussd code. When I install the app from playstore or /data/adb the manager is visible in the applist and is functioning correctly but banking apps stop working as they detect the lsposed manager app. What can I do to resolve this?
Click to expand...
Click to collapse
try this
github.com

GitHub - adrianmmiller/Hide-My-Applist-Guide: A brief guide to using Hide My Applist

A brief guide to using Hide My Applist. Contribute to adrianmmiller/Hide-My-Applist-Guide development by creating an account on GitHub.
github.com github.com
 
S

Schroeder09

Senior Member
Nov 6, 2017
1,161
230
Google Pixel 7 Pro
heinhuiz said:
Are you going to ask this every month? Since the beginning of XPrivacy nobody ever had any problem after a monthly update with any phone.
Click to expand...
Click to collapse

digger16309 said:
I wish I could like this post 100 times. What would break LSPosed in a monthly update?
Click to expand...
Click to collapse
What lovely people. How dare I come to a public forum that exists for sharing software, discussing it, and troubleshooting it and ask a question. How stupid of me.

If you don't have an answer keep moving. You're toxic, snide people. Grouches.
 
  • Like
  • Haha
  • Wow
Reactions: HippoMan, heinhuiz and digger16309
R

ReMiOS

Senior Member
Mar 13, 2021
62
16
Is it possible to temporarily disable LSposed from TWRP when the phone is in a bootloop ?
Phone is Samsung S10+ / Android 12 / OneUI 4.1 / Magisk 26.1 / LSPosed-v1.8.6-6712-zygisk-release

I've tried to get in Safe mode with key combo, but didn't work

I've tried (but seems to have no effect)
touch /cache/disable-magisk
and
touch /cache/.disable-magisk
 
rodken

rodken

Senior Member
Jan 11, 2010
1,919
886
ReMiOS said:
Is it possible to temporarily disable LSposed from TWRP when the phone is in a bootloop ?
Phone is Samsung S10+ / Android 12 / OneUI 4.1 / Magisk 26.1 / LSPosed-v1.8.6-6712-zygisk-release

I've tried to get in Safe mode with key combo, but didn't work

I've tried (but seems to have no effect)
touch /cache/disable-magisk
and
touch /cache/.disable-magisk
Click to expand...
Click to collapse
Enter in TWRP.
Advanced > File Manager.
Go to "/data/adb" and delete the folders of the specific magisk module.
Reboot.

-- or
  1. Flash Magisk
  2. Reboot
  3. adb wait-for-device shell magisk --remove-modules while the device is booting.
 
  • Like
Reactions: jons99
R

ReMiOS

Senior Member
Mar 13, 2021
62
16
I have tried removing all modules one by one starting with LSposed, but did not recover from the bootloop.

With adb i could not get a connection
adb wait-for-device shell magisk --remove-modules

Flashing Magisk made the bootloop worse (only Bootlogo and no "Samsung" starting screen)
 
rodken

rodken

Senior Member
Jan 11, 2010
1,919
886
ReMiOS said:
I have tried removing all modules one by one starting with LSposed, but did not recover from the bootloop.

With adb i could not get a connection
adb wait-for-device shell magisk --remove-modules

Flashing Magisk made the bootloop worse (only Bootlogo and no "Samsung" starting screen)
Click to expand...
Click to collapse
Remember, turn off the device
Open a shell and type: adb wait-for-device shell magisk --remove-modules
Boot with Magisk enabled.
Your device should reboot and in the next boot you should have a clean magisk with out modules.

-- or
  • Connect the phone to PC using a solid cable. Then type adb shell. With this command, you will enter the root of system.
  • Then type rm -rf /data/adb/modules and press enter. This command deletes all modules in your phone. If you know what module causing bootloop, you can to indicate that module’s folder.
 
Last edited:
  • Like
Reactions: digger16309
R

ReMiOS

Senior Member
Mar 13, 2021
62
16
I could not start an adb shell (also the adb wait-for-device command gave no connection)
I removed all modules one by one starting with LSposed using the TWRP File manager

The magisk log states zygote could not be started properly

/cache/magisk.log
three times the following:
umount2 /system/bin/bu failed with 22: Invalid argument
umount2 /system/bin/appwidget failed with 22: Invalid argument
** zygote restarted
zygisk64: replaced com/android/internal/os/Zygote#nativeForkAndSpecialize
zygisk64: replaced com/android/internal/os/Zygote#nativeForkSystemServer
zygisk32: replaced com/android/internal/os/Zygote#nativeForkAndSpecialize
zygisk32: replaced com/android/internal/os/Zygote#nativeForkSystemServer
 
rodken

rodken

Senior Member
Jan 11, 2010
1,919
886
ReMiOS said:
I could not start an adb shell (also the adb wait-for-device command gave no connection)
I removed all modules one by one starting with LSposed using the TWRP File manager

The magisk log states zygote could not be started properly

/cache/magisk.log
three times the following:
umount2 /system/bin/bu failed with 22: Invalid argument
umount2 /system/bin/appwidget failed with 22: Invalid argument
** zygote restarted
zygisk64: replaced com/android/internal/os/Zygote#nativeForkAndSpecialize
zygisk64: replaced com/android/internal/os/Zygote#nativeForkSystemServer
zygisk32: replaced com/android/internal/os/Zygote#nativeForkAndSpecialize
zygisk32: replaced com/android/internal/os/Zygote#nativeForkSystemServer
Click to expand...
Click to collapse
I refuse to get into the ins and outs of why you cannot start ADB Shell but, consider using Magisk Manager for Recovery Mode; courtesy of XDA Member VR25 - to ensure that you have indeed removed all modules.

You should uninstall Magisk and reflash the stock boot image from your ROM/firmware package/factory image.

If you can get ADB to function - you have to be in the bootloop and then enter the aforementioned command. I suppose that you already removed your modules with TWRP, but then remove the .disable_magisk file that is in the cache/ folder. It is a hidden file (starts with a dot) so your root file explorer will need to be set to show hidden files.
 
Last edited:
rodken

rodken

Senior Member
Jan 11, 2010
1,919
886
Gordietm said:
I'm on A14 Beta 3 with a 7 Pro. With the LSPosed zygisk module I'm getting the message " Process system is not responding" everytime I reboot. Once I dismiss the message, everything is fine. But is there a way to get rid of this message?
Click to expand...
Click to collapse
  • Reset App Preferences
  • Clear System UI Process Cache
  • Set Background Process Limit to None
 
  • Like
Reactions: Gordietm
Xperi.a

Xperi.a

Senior Member
Oct 9, 2012
97
5
Is there any method to use LSposed without enabling Zygisk or Riru?

I'm trying KernelSU but I want to use LSposed without enabling Zygisk.

I'm using KSU 0.5.7 and OOS 13 with Stock rom.
 
  • Haha
Reactions: drnightshadow
You must log in or register to reply here.

Similar threads

rovo89
  • Locked
Xposed - Legacy thread. Don't panic, Xposed is still here.
Replies
12K
Views
8M
rovo89
rovo89
rovo89
  • Locked
  • Sticky
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
Replies
49
Views
7M
rovo89
rovo89
rovo89
[DISCUSSION] Xposed for Lollipop
Replies
13K
Views
4M
lenoid
lenoid
romracer
[UNOFFICIAL] Systemless Xposed for Android 5.1/6.0 - v86.1 / 20160928 / SDK22/SDK23
Replies
7K
Views
3M
D
Deleted member 11604687
T
[2019.5.1][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27)
Replies
8K
Views
3M
Nergal di Cuthah
Nergal di Cuthah

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 3
    simplepinoi177
    simplepinoi177
    rodken said:
    Maybe, you can try a script to completely remove LSPosed from said device.
    Code: 
    #!/bin/bash

# Check if Magisk Manager is installed
if [ ! -f "/data/adb/magisk.apk" ]; then
  echo "Magisk Manager is not installed."
  exit 1
fi

# Uninstall LSPosed
adb shell pm uninstall com.lsposed.module

# Clear the cache and data for the Magisk Manager app
adb shell pm clear com.lsposed.module

# Boot the device into recovery mode
adb reboot recovery

# Wipe the cache partition
adb shell wipe cache

# Reboot the device
adb reboot

    This script will first check if Magisk Manager is installed. If it is not, the script will exit with an error message. If Magisk Manager is installed, the script will then uninstall LSPosed. Next, the script will clear the cache and data for the Magisk Manager app. Finally, the script will boot the device into recovery mode and wipe the cache partition. Once the cache partition has been wiped, the script will reboot the device.

    Afterwhich, you can try LSPosed v.1.9.1 (6994) - zygisk-release.
    Click to expand...
    Click to collapse
    Thank you! What a clever idea(s)! I'll be sure to try it.

    It really makes me wish I could make any heads or tails or "headway" with figuring out what the logs are saying that's causing the issue that most modules launch and work fine enough, unless they have to read & write a config/pref file; no matter how many times I uninstall & re-install LSPosed & Magisk. Hopefully your idea of clearing the cache for Magisk and the partition will help reset it properly.


    I really do appreciate any & all (of your) help!
    View
    3
    rodken
    rodken
    simplepinoi177 said:
    I made a text file, copied your code, and renamed it remove_lsposed.sh and placed it in the platform-tools folder (which holds the adb.exe file). I navigate to the folder through the "cd" command. When I run the ./remove_lsposed.sh, i receive the following errors
    Code: 
    ./remove_lsposed.sh: line 2: $'\r': command not found
./remove_lsposed.sh: line 17: syntax error: unexpected end of file
    and even if I remove the "if" lines checking for Magisk Manager -- since I know for sure that it is installed and not hiding -- it comes out as
    Code: 
    ./remove_lsposed.sh: line 2: $'\r': command not found
./remove_lsposed.sh: line 4: magisk: command not found
./remove_lsposed.sh: line 5: $'\r': command not found
./remove_lsposed.sh: line 8: $'\r': command not found
./remove_lsposed.sh: line 10: adb: command not found
    Click to expand...
    Click to collapse
    In some cases ./remove_lsposed.sh: line 2: $'\r': command not found means that the script contains a line ending that is not recognized by the Linux shell. The \r character is a carriage return, which is used in Windows text files but not in Linux text files.

    In order to correct the error, you need to remove the carriage returns from the script file. You can do this using a text editor or a command line tool like tr.
    -- Open the script file in a text editor.
    -- Search for the carriage returns (\r).
    -- Replace all carriage returns with newline characters (\n).
    -- Save the file.

    Steps to fix the error using the tr command:

    -- Open a terminal window.
    -- Run the following command:
    Code: 
    tr -d '\r' < remove_lsposed.sh > remove_lsposed_fixed.sh
    This will create a new file called remove_lsposed_fixed.sh that contains the script with the carriage returns removed.

    You can try running the script again.

    I’m sorry I couldn’t be more helpful.
    View
    2
    rodken
    rodken
    simplepinoi177 said:
    Any of you looking for a challenge; can any of you experts help me out?
    I’ve included a verbose LSPosed log (barebones, with only the Magisk module and none of my usual Magisk & LSPosed modules), as I am having a very difficult time making heads or tails out of it and what could possibly be going wrong.
    One is “release” version, one is “debug”.

    My LSPosed does not seem to be implemented right. I’m finding that while LSPosed modules seem to work well enough to a degree, functionality seems to be limited, incomplete, or doesn’t execute properly. For instance, apps that are LSPosed modules seem to not be creating & writing relevant, needed preference/config files.

    Relevant information on setup; I’m using a Pixel 7 Pro, stock ROM, August firmware version, Magisk stable version, no custom kernel, using Zygisk-LSPosed version 1.9.1 (6990). Magisk modules are only USNF-MOD, AOSP Mods, and Systemless Hosts – on top of Zygisk-LSPosed Magisk module, of course.

    I have 2 Pixel 7 Pros (wife’s), set up in the exact same way. All apps & modules were able to be launched & was working perfectly. I had to uninstall Magisk. I uninstalled it using inside the Magisk Manager app. After everything seemed to be removed, I re-installed the Magisk Manager app, patched the stock init_boot.img, fastboot flashed it, and regained root. I installed all modules (4), including Zygisk-LSPosed. After LSPosed got re-installed, I activated the Pixelify GPhotos module – AOSP Mods was already activated. While AOSP Mods seemed to work just as before, GPhotos was not correctly spoofing like it should. After 3 days of doing everything I could to get it to work – constant uninstalling & reinstalling both module & LSPosed, manually searching & removing any remnants or anything referring to LSPosed or GPhotos (“balti”) – I found out that the preference file that GPhotos refers to did not exist in the folder it stated in the logs. I took a copy of the same preference file from my wife’s phone and manually put it in my phone and lo-and-behold, the module worked as it did before/should! I’ve been trying to use some other modules, and I’m finding (through looking at logcats) that many aren’t working right seemingly because them not being able to load the preference/config files that are supposed to help run things. Apps/Modules like AOSP Mods, HideMyApplist, or a “Patcher” (that also shares the title as the name of a Jason Mraz and Colbie Caillat song) work as it normally has – although I believe it’s because they store their data & configuration/preference in a different way than others.
    Specific examples: XPrivacyLua, AndroidFaker, IAmNotADeveloper, Geergit, IMEI Masker.
    What’s frustrating is that these all work perfectly on my wife’s phone (who, again, should have the same exact set up), but not mine! And I looked at the attached LSPosed verbose log and I can’t figure out why!
    From the little I can glean, there is a mention of “unable to open…daemon.dm”; I can confirm there is a file named “daemon” at the folder location, but it doesn’t state daemon.dm with “.dm” as a specific extension. In any case, I checked my wife’s phone, and it seems to be the same setup with all modules working as expected.
    Also, it seems that LSPosed can’t really get proper access to dexoat – both in mounting (dexoat64) or getting denied “enable dexoat wrapper”.
    • I’ve uninstalled & reinstalled Zygisk-LSPosed
    • After uninstalling LSPosed, I’ve gone in a root browser and manually deleted any remnants of LSPosed.
    • Completely uninstalled Magisk again, this time flashing stock init_boot.img myself instead of relying on app to restore.
    o I’ve also run it with no other modules (to possibly conflict)
    • Removed all modules through adb command adb wait-for-device shell magisk --remove-modules before uninstalling & reinstalling Magisk.
    • I’ve deleted LSPosed manually through root browser (/root/data/adb/lspd & /root/data/adb/modules/zygisk_lsposed)
    • I’ve tried using 6992.
    • I’ve tried using LSPosed-v1.9.1-6992-zygisk-debug version
    • I’ve tried using LSPosed-v1.9.1-6990-zygisk-debug version

    If no one can figure it out from the LSPosed log, does anyone know how to completely remove LSPosed to completely reset it?
    Also, I can upload a log with modules running, if seeing it run barebones is not showing why things aren’t being implemented properly.


    I'd appreciate if any of you can help out in any way! Thanks in advance!
    Click to expand...
    Click to collapse
    Maybe, you can try a script to completely remove LSPosed from said device.
    Code: 
    #!/bin/bash

# Check if Magisk Manager is installed
if [ ! -f "/data/adb/magisk.apk" ]; then
  echo "Magisk Manager is not installed."
  exit 1
fi

# Uninstall LSPosed
adb shell pm uninstall com.lsposed.module

# Clear the cache and data for the Magisk Manager app
adb shell pm clear com.lsposed.module

# Boot the device into recovery mode
adb reboot recovery

# Wipe the cache partition
adb shell wipe cache

# Reboot the device
adb reboot

    This script will first check if Magisk Manager is installed. If it is not, the script will exit with an error message. If Magisk Manager is installed, the script will then uninstall LSPosed. Next, the script will clear the cache and data for the Magisk Manager app. Finally, the script will boot the device into recovery mode and wipe the cache partition. Once the cache partition has been wiped, the script will reboot the device.

    Afterwhich, you can try LSPosed v.1.9.1 (6994) - zygisk-release.
    View
    2
    rodken
    rodken
    simplepinoi177 said:
    I really do appreciate the help you're giving me. And I hope you continue to have patience with me as I work this out...

    So, from what I learned a bit from the first post you made for me, I learned to use Cygwin, correct?
    I made a text file, copied your code, and renamed it remove_lsposed.sh and placed it in the platform-tools folder (which holds the adb.exe file). I navigate to the folder through the "cd" command. When I run the ./remove_lsposed.sh, i receive the following errors
    Code: 
    ./remove_lsposed.sh: line 2: $'\r': command not found
./remove_lsposed.sh: line 17: syntax error: unexpected end of file
    and even if I remove the "if" lines checking for Magisk Manager -- since I know for sure that it is installed and not hiding -- it comes out as
    Code: 
    ./remove_lsposed.sh: line 2: $'\r': command not found
./remove_lsposed.sh: line 4: magisk: command not found
./remove_lsposed.sh: line 5: $'\r': command not found
./remove_lsposed.sh: line 8: $'\r': command not found
./remove_lsposed.sh: line 10: adb: command not found
    I apologize if I'm doing something wrong or I don't have Cygwin64 not properly set up.
    Also, I wanted to note that, at least in my setup, the lsposed folder under modules can be seen in my root explorer as /root/adb/modules/zygisk_lsposed -- if that means anything

    Again, thanks for the patience and the assistance!
    Click to expand...
    Click to collapse
    Option 1​
    Code: 
    #!/bin/bash

# Stop LSPosed
adb shell stop lsposed

# Remove LSPosed modules
adb shell pm uninstall -k --user 0 lsposed*

# Remove LSPosed framework
adb shell rm -rf /data/data/de.robv.android.lsposed

# Reboot the device
adb reboot
    Another script, save it as a file with the name remove_lsposed.sh and then run it in a terminal window.

    This script should first stop LSPosed, then remove all LSPosed modules, and finally remove the LSPosed framework. After the script has finished running, your device will reboot.

    Option 2​
    Code: 
    #!/bin/bash

# Remove LSPosed
rm -rf /data/data/com.lsposed.manager
rm -rf /data/system/priv-app/LSPosed
rm -rf /system/priv-app/LSPosed

# Reboot the device
reboot
    -- Save the script as remove_lsposed.sh.
    -- Make the script executable by running the following command:
    Code: 
    chmod +x remove_lsposed.sh
    -- Run the script by running the following command:
    Code: 
    ./remove_lsposed.sh
    Just another option to remove LSPosed from your Android device completely.
    View
    1
    simplepinoi177
    simplepinoi177
    Any of you looking for a challenge; can any of you experts help me out?
    I’ve included a verbose LSPosed log (barebones, with only the Magisk module and none of my usual Magisk & LSPosed modules), as I am having a very difficult time making heads or tails out of it and what could possibly be going wrong.
    One is “release” version, one is “debug”.

    My LSPosed does not seem to be implemented right. I’m finding that while LSPosed modules seem to work well enough to a degree, functionality seems to be limited, incomplete, or doesn’t execute properly. For instance, apps that are LSPosed modules seem to not be creating & writing relevant, needed preference/config files.

    Relevant information on setup; I’m using a Pixel 7 Pro, stock ROM, August firmware version, Magisk stable version, no custom kernel, using Zygisk-LSPosed version 1.9.1 (6990). Magisk modules are only USNF-MOD, AOSP Mods, and Systemless Hosts – on top of Zygisk-LSPosed Magisk module, of course.

    I have 2 Pixel 7 Pros (wife’s), set up in the exact same way. All apps & modules were able to be launched & was working perfectly. I had to uninstall Magisk. I uninstalled it using inside the Magisk Manager app. After everything seemed to be removed, I re-installed the Magisk Manager app, patched the stock init_boot.img, fastboot flashed it, and regained root. I installed all modules (4), including Zygisk-LSPosed. After LSPosed got re-installed, I activated the Pixelify GPhotos module – AOSP Mods was already activated. While AOSP Mods seemed to work just as before, GPhotos was not correctly spoofing like it should. After 3 days of doing everything I could to get it to work – constant uninstalling & reinstalling both module & LSPosed, manually searching & removing any remnants or anything referring to LSPosed or GPhotos (“balti”) – I found out that the preference file that GPhotos refers to did not exist in the folder it stated in the logs. I took a copy of the same preference file from my wife’s phone and manually put it in my phone and lo-and-behold, the module worked as it did before/should! I’ve been trying to use some other modules, and I’m finding (through looking at logcats) that many aren’t working right seemingly because them not being able to load the preference/config files that are supposed to help run things. Apps/Modules like AOSP Mods, HideMyApplist, or a “Patcher” (that also shares the title as the name of a Jason Mraz and Colbie Caillat song) work as it normally has – although I believe it’s because they store their data & configuration/preference in a different way than others.
    Specific examples: XPrivacyLua, AndroidFaker, IAmNotADeveloper, Geergit, IMEI Masker.
    What’s frustrating is that these all work perfectly on my wife’s phone (who, again, should have the same exact set up), but not mine! And I looked at the attached LSPosed verbose log and I can’t figure out why!
    From the little I can glean, there is a mention of “unable to open…daemon.dm”; I can confirm there is a file named “daemon” at the folder location, but it doesn’t state daemon.dm with “.dm” as a specific extension. In any case, I checked my wife’s phone, and it seems to be the same setup with all modules working as expected.
    Also, it seems that LSPosed can’t really get proper access to dexoat – both in mounting (dexoat64) or getting denied “enable dexoat wrapper”.
    • I’ve uninstalled & reinstalled Zygisk-LSPosed
    • After uninstalling LSPosed, I’ve gone in a root browser and manually deleted any remnants of LSPosed.
    • Completely uninstalled Magisk again, this time flashing stock init_boot.img myself instead of relying on app to restore.
    o I’ve also run it with no other modules (to possibly conflict)
    • Removed all modules through adb command adb wait-for-device shell magisk --remove-modules before uninstalling & reinstalling Magisk.
    • I’ve deleted LSPosed manually through root browser (/root/data/adb/lspd & /root/data/adb/modules/zygisk_lsposed)
    • I’ve tried using 6992.
    • I’ve tried using LSPosed-v1.9.1-6992-zygisk-debug version
    • I’ve tried using LSPosed-v1.9.1-6990-zygisk-debug version

    If no one can figure it out from the LSPosed log, does anyone know how to completely remove LSPosed to completely reset it?
    Also, I can upload a log with modules running, if seeing it run barebones is not showing why things aren’t being implemented properly.


    I'd appreciate if any of you can help out in any way! Thanks in advance!
    View
  • 85
    ayush.gl
    ayush.gl
    Developers: LSPosed Developers
    Homepage: GitHub
    ✱ Requirements:
    • Magisk 21+
    • Android 8.1-13

    • Riru(NOT NEEDED) USE ZYGISK
    Description:     Riru module providing ART interception framework (natively for Android Pie) that provides consistent API -interfaces with OG Xposed, using YAHFA (or SandHook) interception environment, supports Android 8.1 ~ 11.
    & Installation:
    • Install Riru 23+
    • Install Riru - LSPosed via Magisk Manager
    • Install LSPosed Manager app (Note: No Saparate App and Zip, App Will be Installed Automatically)
    • Reboot your device.

    Download:
    For stable release, please go to Github Release page For canary build use telegram.
    Go to second post for latest version Download

    Notes:    I'm just sharing this from github, I'm not responsible if you bricked your device.

    GPay and other banking apps working fine without any issue so this xposed alternative is worth trying and safer.

    Note: If anyone facing bootloop issue, don't panic, hard reboot again and it will work.

    Screenshot:
    View
    31
    ayush.gl
    ayush.gl
    Download:
    Flash zip file through magisk and then install LSPosed Manager app

    Update 1 March 2021
    V1.2.0

    V1.3.7 Updated 15.May.2021
    (Note: No Saparate App and Zip, App Will be Installed Automatically)


    For Newer Version Changelogs and Downloads:
    LsPosed Github




    Changelog

    • Fix manager white screen
      [*]Support split-apk modules (LSPosed will choose only one apk with xposed_init to load)
      [*]Fix manager crash when launching an uninstalled module from notification
      [*]Load modules with SharedMemory (it can speedup app cold launch) 2
      [*]New manager icon
      [*]Fix incorrect update notification in the first installation
      [*]Fix some apps not showing in the scope list in some rare cases
      [*]Show notification of module uninstallation
      [*]Prevent modules from hooking inner methods (methods from XposedBridge's classloader)



    Note:

    Previously LSPosed only recognize modules from the primary user. However, this strategy is not good and leads to some problems: some modules require getting installed app lists for configuration but they cannot do so across users; some require reading themselves from the hooked apps but they cannot do so from non-primary users; some users want to configure modules differently on different users which is not feasible previously. Thus LSPosed now requires every module to be installed to the user on which the apps they want to hook are installed. Some devices restrict modules from installing onto some users. In such a case, you can install them from the manager (but it's recommended).

    1: For some weird devices that prevent installing apps from the root user, please install the manager from /data/adb/lspd/manager.apk or manager.apk from the zip file manually.

    2: Some modules get modules' apk path using reflection of its classloader, it's not recommended and unstable since the apk path from classloader no longer exists when using SharedMemory to load modules. Please use the documented way (from IXposedHookZygoteInit.StartupParam.modulePath) instead.
    View
    18
    ayush.gl
    ayush.gl
    QkiZMR said:
    Why it's safer than EdXposed?
    Click to expand...
    Click to collapse
    I didn't say it's safer than edxposed. I meant xposed alternatives like taichi etc.
    All banking apps works, no system slowdown, i got more free ram etc.
    In edxposed the hooked apps take time to open, no such issue with LSPosed.
    That's why i thought it's worth trying and safer.
    View
    17
    F
    Fif_
    Fif_ said:
    I was considering that until I made an Automate flow to automatically add newly installed apps to select Xposed modules' scope.
    Click to expand...
    Click to collapse
    By popular request, this is my setup for automatically adding newly installed packages to some user-defined LSPosed scopes.

    [EDIT:] These instructions have been updated on February 1, 2022 and the zip file has been updated on November 14, 2021.

    Requirements:
    Caveats:
    • LSPosed won't pick up the changes until the device is rebooted.
    Instructions:
    1. Unzip the attached LSPosed-Auto-Add.zip
    2. Create the /sdcard/usr/bin directories.
    3. Move lsposed-scopes-add from step 1 file to /sdcard/usr/bin. The file full path must be /sdcard/usr/bin/lsposed-scopes-add
    4. Move xposed-modules-status from step 1 file to /sdcard/usr/bin. The file full path must be /sdcard/usr/bin/xposed-modules-status
    5. Launch Automate, go to settings and change the Superuser command from its default of
      Code: 
      su
      to
      Code: 
      su -mm
      .
    6. Import LSPosed Auto Add.flo in Automate.
    7. After the flow is imported, grant all needed permissions.
    8. In the imported flow, start Configure. You should see a list of active LSPosed modules like the one seen on the attached screenshot.
    9. Toggle the modules as needed. If shown with a check mark, any newly added package will be added to the module's scope.
    10. Press Cancel to exit from the module list.
    11. Make sure that Automate is set to start at boot (in Automate settings).
    There should be two automate fibers running in the flow. If it stops for whatever reason, just start the Init flow.
    You can add and remove modules at any time by launching the Configure flow.

    Changes:
    • 2021-11-01: Provide missing script.
    • 2021-11-08: Force running scripts in / in Automate flow.
    • 2021-11-14: Also support parasitic manager.
    • 2022-02-01: Add "su -mm" instructions for newer versions of Automate.
    Thanks to @Open.Orange, @spawnlives and @randomwordhere for testing.
    View
    14
    shadowstep
    shadowstep
    InContext said:
    I have it working on the Poco X3 NFC, running RR, loaded and runs without issue, I used the YAHFA option, has updated without issue.

    Thought I should add that I can't get SafetyNet on, but I've never been worried about that, I think I've only ever had it working once on one of my devices years ago. The one app that refused to play nice I just used MagiskHide on, and it's not a problem now.

    In saying that I only have one module loaded, I haven't had time to go looking for the below answers, to install any others.

    The only thing I haven't figured out yet is what apps need to be picked with what modules, sure some are obvious as they are named after the apps, but is there anything else that needs to be picked with them? For example, do I need to pick the framework app with everything, I'm sure I don't, but how do I know?
    Click to expand...
    Click to collapse
    I'm using YAHFA myself, even though I was using SandHook earlier with EdXposed. Also, I'm passing SafetyNet without an issue and Play Store shows certified as well, so that's nice.

    Coming to your question about "scope", basically for a module, you have to select the apps that are hooked by the module. This is pretty straightforward for modules that hook a specific app, for example, if you're using WATweaker, you have to select WhatsApp in its "scope". Similarly, another example, if you're using Instaprefs, you have to select Instagram in its "scope". However, for more systemwide module (like GravityBox, for example), multiple apps have to be selected in the "scope" as the module is more global in nature, so to speak.

    The only way to figure out which apps need to be added in scope for a module is to ask the module developer or by trial and error. Taking GravityBox as an example, you'll find the list of apps that need to be selected for its scope in the first post of its thread (under apps that need to be whitelisted; "whitelisted" term being used in context of EdXposed, since when the post was written, LSPosed wasn't a thing).

    Also, modules can auto-add recommended apps to their scope, but the responsibility of making that happen lies with the module developer. Once again, taking GravityBox as the example, if you install GravityBox in LSPosed, you don't have to select apps manually in its scope. They're auto-selected since the developer has added support for LSPosed and auto-selection of scope apps.

    I know the reply is long-ish, but I hope it helps you and the others who had similar questions. :)
    View

New posts