Database Develop

[WORKAROUND][Xposed for Android 5.1] Make ~99% of modules work.

This has been fixed xda post​Note: This is a temporary solution until someone fixes this in Xposed. Also I use my module "SnapColors" as a example throughout this post but this fix should for work any module. I've tested it with other modules and it works. If the module did not previously work on 5.0 then ignore this post and continue on with life.
TL;DR Version:
I found a temporary solution of getting modules to work on 5.1 for modules that worked on 5.0 but don't work on 5.1.
Non-TL;DR Version: Backstory and how I found his temporary solution
So a couple days ago I decided to start working on bring my module(s) to Xposed running on 5.1. In doing so what I noticed with a lot of the modules they seem to crash the app without throwing any kind of error whatsoever. Take for example one of my modules "SnapColors", if SnapColors was enabled in Xposed Installer SnapChat would always crash without throwing any error it wouldn't even say anything along the lines of "process has stopped unexpectedly" it would just close the app. So because of this behavior it led me to believe something was wrong with Xposed and not with my module(s). So I went thought what could be broken in Xposed thats causing this because 5.0 is just one up to 5.1 so the changes couldn't be that big. I went though the things that could cause this and came across "dalvik-cache" I remember reading somewhere Xposed makes some changes to the cache file (.dex) thats created during the creation of dalvik-cache files. So then I thought what if in 5.1 a small change was made to the process of making the dalvik cache files and thats what is causing the problem. So I decided to delete the dalvik cache file for SnapChat which is what my module was hooking into, then I tried opening SnapChat again but it crashed so I tried opening it again and what do you know it opened without any problems with my module fully working without any problems. The fix was kind of a guess too.
The fix/Solution
Note: If you reboot your device you have to do the fix again. Also you are deleting the dalvik cache so you won't benefit from it any more for the app(s) you delete it for. Unless you reboot then everything gets reverted.
What you have to do is delete the dalvik cache file for the app the module is for.
Example: SnapColors a module for SnapChat, so we have to delete the dalvik cache file for SnapChat.
What you need:
1) A file manager with root access, or terminal knowledge.
2) Package name example for SnapChat its "com.snapchat.android". How to get the package name look below theres a how to.
Steps for deleting the cache file:
Make sure the app is not running in the background close it if it is.
Method 1) Via terminal command:
Code:
cd /data/dalvik-cache/arm/ && rm [email protected]@"package name here without the quotes"*
Example command for SnapChat would be don't forget the "*" at the end:
Code:
cd /data/dalvik-cache/arm/ && rm [email protected]@com.snapchat.android*
Method 2) Via file manager: Navigate to /data/dalvik-cache/arm/ look for a file starting with the name [email protected]@"package name here without the quotes".apk delete this file and thats it.
Now try and open the app if it doesn't work close the app then try opening it again. make sure that apps not running in the background before trying again.
Getting package name
Via terminal command:
Code:
ls /data/data/ | grep "the app name here without quotes"
Via app: Install https://play.google.com/store/apps/details?id=com.electricsheep.asi
Open it-> Apps tab-> Tap the app-> look for "Package name:" should be the first thing.

Great job figuring that out! I hope @romracer takes a look at it and releases an update with permanent fix

mmamedov said:
Great job figuring that out! I hope @romracer takes a look at it and releases an update with permanent fix
Click to expand...
Click to collapse
Yup. I wish I could help but my knowledge of c++ is limited.

Why are apps on 5.1 creating this dalvik file if the runtime is ART?

r25txe said:
Why are apps on 5.1 creating this dalvik file if the runtime is ART?
Click to expand...
Click to collapse
The files are used by art despite the name of the folder "dalvik-cache". I think don't quote me on that.

Subscribed
sent from your moms phone

Can I get gravitybox to work?
Sent from my Nexus 5 using XDA Free mobile app

Programming4life said:
Yup. I wish I could help but my knowledge of c++ is limited.
Click to expand...
Click to collapse
Enough knowledge to help me out on twitter ALLLL the time! Lol

Great Finding. Thanks for the info.
Any chance of getting work Xposed GEL setting with CM12.1 Android 5.1
Thanks

lolzas said:
Can I get gravitybox to work?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For module related stuff post on there thread. Getting modules to work is on the dev of the module.

mjrifath said:
Great Finding. Thanks for the info.
Any chance of getting work Xposed GEL setting with CM12.1 Android 5.1
Thanks
Click to expand...
Click to collapse
For module related stuff post on there thread. Getting modules to work is on the dev of the module.

Another step into 5.1 with xposed.. Only needs rovo magic Touch.. Thanks for it...

Programming4life said:
For module related stuff post on there thread. Getting modules to work is on the dev of the module.
Click to expand...
Click to collapse
So can you tell us what are those 95% modules for xposed on Lolli 5.1?
Can you give us some examples what modules are working on your smart phone with your metods?
Thanks...

spaxon said:
So can you tell us what are those 95% modules for xposed on Lolli 5.1?
Can you give us some examples what modules are working on your smart phone with your metods?
Thanks...
Click to expand...
Click to collapse
I said ~95% because some modules need to be updated strictly for lollipop and won't work no matter what. Its more like 99% but 95% just in case.

Programming4life said:
The fix/Solution
Note: If you reboot your device you have to do the fix again. Also you are deleting the dalvik cache so you won't benefit from it any more for the app(s) you delete it for. Unless you reboot then everything gets reverted.
Click to expand...
Click to collapse
Something I dont understand, for almost every module in xposed on every version of android, you must enable that module in xposed and reboot smartphone to get it work... is it true?
I have tried Gravitybox LP and some more modules like Flat Style Bar Indicators, with deleting them in /data/dalvik-cache/arm/ but they dont work at all, i have tried couple of times starting them.
Also I tried deleting them in twrp file manager and I have bootloop (but no worries I deleted those modules and started the phone )
Am I doing something wrong?

spaxon said:
Something I dont understand, for almost every module in xposed on every version of android, you must enable that module in xposed and reboot smartphone to get it work... is it true?
I have tried Gravitybox LP and some more modules like Flat Style Bar Indicators, with deleting them in /data/dalvik-cache/arm/ but they dont work at all, i have tried couple of times starting them.
Also I tried deleting them in twrp file manager and I have bootloop (but no worries I deleted those modules and started the phone )
Am I doing something wrong?
Click to expand...
Click to collapse
After installing a module you must enable it and then do a reboot/soft reboot yes that is true. Gravitybox LP and Flat Style Bar Indicators both modify the android system itself so theres nothing we can really do until someone fixes this bug in Xposed's code.

What if we modify the permissions or the file itself so we don't have to constantly delete it upon reboots?
Sent from my Nexus 5 using Tapatalk

Youtube background playback don`t works with that method

FuMMoD said:
What if we modify the permissions or the file itself so we don't have to constantly delete it upon reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Android doesn't like it when the permissions are changed for a cache file so it'll just fc the app.

jabarel said:
Youtube background playback don`t works with that method
Click to expand...
Click to collapse
Worked for me you may have a out dated version of YouTube or YouTube background.

[Dev Help] Is it possible to run an "uninstall script" when removing a module?

[Dev Help] Is it possible to run an "uninstall script" when removing a module?
Hey all. I'm working on a module, and I'm planning on using the late-start service to make some changes to the system to detach the app I'm including in the module from the Play Store to prevent accidental updates or a persistent update nag. This part is working fine. The part I'm having troubles with is the uninstall portion. When removing the module, the changes persist since they weren't systemless. So, my question is this: is it possible to have Magisk run an "uninstall script" when it has been marked for deletion? I've done some digging through the documentation and haven't found anything indicating this is possible, but I'm hoping it's either an undocumented feature or somebody will know a way to achieve the same effect.

You could let the module also install a boot script in post-fs-data.d or service.d (service.d is preferred, but if that doesn't work try post-fs-data.d). Let that script look for the module folder in /magisk. If it isn't found, let the script revert the changes and then delete itself.

Didgeridoohan said:
You could let the module also install a boot script in post-fs-data.d or service.d (service.d is preferred, but if that doesn't work try post.fs.data.d). Let that script look for the module folder in /magisk. If it isn't found, let the script revert the changes and then delete itself.
Click to expand...
Click to collapse
You mean in Magisk's core? Yeah, that's a good idea, and probably easily implemented.

Ssayerr said:
You mean in Magisk's core? Yeah, that's a good idea, and probably easily implemented.
Click to expand...
Click to collapse
Yes, in /magisk/.core. It's quite simple, but it works... :good:

Didgeridoohan said:
Yes, in /magisk/.core. It's quite simple, but it works... :good:
Click to expand...
Click to collapse
Cool, I'll give it a shot. Any tricks to getting stuff to run in the core, or do I just drop it in?

Ssayerr said:
Cool, I'll give it a shot. Any tricks to getting stuff to run in the core, or do I just drop it in?
Click to expand...
Click to collapse
Don't forget to set the correct permissions on the script or it won't execute... Other than that it's just to drop it in service.d or post-fs-data.d, whichever one fits your needs.

Didgeridoohan said:
Don't forget to set the correct permissions on the script or it won't execute... Other than that it's just to drop it in service.d or post-fs-data.d, whichever one fits your needs.
Click to expand...
Click to collapse
Great, I'll see what I can do with it. Many thanks for the advice!

You could check the file called "remove" in the module folder.

Deic said:
You could check the file called "remove" in the module folder.
Click to expand...
Click to collapse
Unless the "remove" file itself can be set up to run a script, that wouldn't work. If that file is present, the module as a whole would be gone before my script would run. I'm currently planning on just having a script check for the existence of the module itself, once I have time to mess with it some more.

Ssayerr said:
Unless the "remove" file itself can be set up to run a script, that wouldn't work. If that file is present, the module as a whole would be gone before my script would run. I'm currently planning on just having a script check for the existence of the module itself, once I have time to mess with it some more.
Click to expand...
Click to collapse
Must keep in background a loop to check the existence of that file obviously. So in your module script for example:
Code:
background function() {
while :; do
[ -f /magisk/$MODDIR/remove ] && {
#here the stuff you want to do
break
}
sleep 1
done
}
background &

Ssayerr said:
Hey all. I'm working on a module, and I'm planning on using the late-start service to make some changes to the system to detach the app I'm including in the module from the Play Store to prevent accidental updates or a persistent update nag. This part is working fine. The part I'm having troubles with is the uninstall portion. When removing the module, the changes persist since they weren't systemless. So, my question is this: is it possible to have Magisk run an "uninstall script" when it has been marked for deletion? I've done some digging through the documentation and haven't found anything indicating this is possible, but I'm hoping it's either an undocumented feature or somebody will know a way to achieve the same effect.
Click to expand...
Click to collapse
Didgeridoohan said:
You could let the module also install a boot script in post-fs-data.d or service.d (service.d is preferred, but if that doesn't work try post-fs-data.d). Let that script look for the module folder in /magisk. If it isn't found, let the script revert the changes and then delete itself.
Click to expand...
Click to collapse
My Unity (Un)Installer has this includes.
Essentially you can run a .core service.d script to delete any left over files such as scripts if the conditional says that the specified mod folder does not exist, and then have the script delete itself once done.
https://github.com/therealahrion/Audio-Modification-Library
This isn't just for AML or audio projects, as it uses the Unity Installer.

Deic said:
Must keep in background a loop to check the existence of that file obviously. So in your module script for example:
Click to expand...
Click to collapse
It doesn't have to be that complicated.

ahrion said:
It doesn't have to be that complicated.
Click to expand...
Click to collapse
Sure, the Unity stuff (Copyrigth © 1337 Canonical Ltd.) is lesser complicated than a few basic command lines in the module script.
Sarcasm intended.

Deic said:
Sure, the Unity stuff (Copyrigth © 1337 Canonical Ltd.) is lesser complicated than a few basic command lines in the module script.
Sarcasm intended.
Click to expand...
Click to collapse
That was not my intention. Lol I knew that was gonna happen. Unity has a lot of features that allows people to make quick edits without having to touch the update-binary.
I was using the /common/moddid-service.sh as an example.
Here's a more refined example minus Unity mumbo jumbo:
if [ ! -d /magisk/$MODID ]; then
rm -f /magisk/.core/service.d/$MODID.sh
fi

ahrion said:
My Unity (Un)Installer has this includes.
Essentially you can run a .core service.d script to delete any left over files such as scripts if the conditional says that the specified mod folder does not exist, and then have the script delete itself once done.
https://github.com/therealahrion/Audio-Modification-Library
This isn't just for AML or audio projects, as it uses the Unity Installer.
Click to expand...
Click to collapse
I do the same on a couple of my own modules. Post-fs-data.d or service.d scripts that doesn't run if the disable file is present in the module folder and cleans up and deletes itself if the folder isn't found, etc. It's really handy...

Can't uninstall modules in Magisk

Hello...
Dont use magisk manager that much...
Now I tried to delete some modules. But when I go on the bin to uninstall them, nothing happen...
Also all the modules say, the will be actualized when reboot.
Rebooted many times... Nothing changes
Someone know what to do?

I have this problem too.
All the modules have 'this module will be updated' and I can't uninstall certain modules like xposed sdk25.

What version or Magisk are your guys running? That sounds like an old bug that supposedly was fixed...
The solution would be to manually navigate to /magisk with a root capable file explorer, deleting the module folders and then reboot.

Mine is Magisk Manager 5.4.0 and Magis 14.0
Isn't it the actual version?
And what do I do because of the update message?

aleccino said:
Mine is Magisk Manager 5.4.0 and Magis 14.0
Isn't it the actual version?
And what do I do because of the update message?
Click to expand...
Click to collapse
Manually remove the modules, like I said in my last post. And then try again...

Confirmed. Above-mentioned solution worked. Magisk v14 has the problems with deleting modules inside the app.

Darayavahus said:
Confirmed. Above-mentioned solution worked. Magisk v14 has the problems with deleting modules inside the app.
Click to expand...
Click to collapse
Glad to hear it works. I spend so little time on the stable release that I forget what bug was fixed when. :laugh:

Didgeridoohan said:
What version or Magisk are your guys running? That sounds like an old bug that supposedly was fixed...
The solution would be to manually navigate to /magisk with a root capable file explorer, deleting the module folders and then reboot.
Click to expand...
Click to collapse
Many thanks for that!! I was stuck on boot loop after new module installation and couldn't get rid of it with couple of mentioned methods here.
Finally deleting module's folder via twrp worked.
Thank you again
Settings whole system up again wasn't an option at this time for me

deleted

Didgeridoohan said:
What version or Magisk are your guys running? That sounds like an old bug that supposedly was fixed...
The solution would be to manually navigate to /magisk with a root capable file explorer, deleting the module folders and then reboot.
Click to expand...
Click to collapse
Where is the /magisk folder?
---------- Post added at 01:52 PM ---------- Previous post was at 01:48 PM ----------
akhil51183 said:
Where is the /magisk folder?
Click to expand...
Click to collapse
Sorry, found it!

Where is the /magisk folder??? Not able to find it.

Dhruvsaija said:
Where is the /magisk folder??? Not able to find it.
Click to expand...
Click to collapse
In case you haven't figured it out yet (and for any future people trying to find the same info), the /magisk folder hasn't been used for a long time.
All Magisk files (including modules) can now be found in /data/adb.

Didgeridoohan said:
In case you haven't figured it out yet (and for any future people trying to find the same info), the /magisk folder hasn't been used for a long time.
All Magisk files (including modules) can now be found in /data/adb.
Click to expand...
Click to collapse
Clutch! :good:

can't R/w even with rooted phone

rooted with magisk and i'm trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail. Anyone else?

Make sure AVB verity is unchecked in magisk then reinstall from the app

qman66 said:
rooted with magisk and i'm trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail. Anyone else?
Click to expand...
Click to collapse
If the pixel 4 is any like pixel 3 with its logical partitions you'll have to use magisk to add to system. Easy way download a magisk module. Then go to /data/adb/modules then the module you installed if u need to add to /system/app you might have to add the /app set permissions then add what is wanted set permissions then restart. easy way without having to make your on module you can always go to magisk thread an learn to make a module as well either way only way I've been able to do it on Android 10 which I reverted back to pie so much better in my opinion

virtyx said:
Make sure AVB verity is unchecked in magisk then reinstall from the app
Click to expand...
Click to collapse
It's always been unchecked

billyt1 said:
If the pixel 4 is any like pixel 3 with its logical partitions you'll have to use magisk to add to system. Easy way download a magisk module. Then go to /data/adb/modules then the module you installed if u need to add to /system/app you might have to add the /app set permissions then add what is wanted set permissions then restart. easy way without having to make your on module you can always go to magisk thread an learn to make a module as well either way only way I've been able to do it on Android 10 which I reverted back to pie so much better in my opinion
Click to expand...
Click to collapse
Ok I'm willing to do this. What module do I download exactly?

qman66 said:
It's always been unchecked
Click to expand...
Click to collapse
Strange
That's the only thing I know that could cause you're issue

Android 10 requires you to so any system changes through Magisk in a "systemless" manner. As mentioned above, it needs to be in a module. If you can't do it yourself, ask for help from one of the devs. If it is a common task that others could benefit from, create a thread with the request and I am sure someone will come through...

CyberpodS2 said:
Android 10 requires you to so any system changes through Magisk in a "systemless" manner. As mentioned above, it needs to be in a module. If you can't do it yourself, ask for help from one of the devs. If it is a common task that others could benefit from, create a thread with the request and I am sure someone will come through...
Click to expand...
Click to collapse
ok does anyone know?

bump

qman66 said:
ok does anyone know?
Click to expand...
Click to collapse
What exactly is the question?

trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.

qman66 said:
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
Click to expand...
Click to collapse
I think it needs to be done "systemless" with a magisk module. Maybe if you ask @Tulsadiver nicely, he might be able to give you a template or even make you up what is needed. If so and it's possible others might have used for it you could share it.

qman66 said:
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
Click to expand...
Click to collapse
You are welcome to try this. Put your file in the vrtheme/system/bin folder. Leave the system folder alone. This is untested.

qman66 said:
Ok I'm willing to do this. What module do I download exactly?
Click to expand...
Click to collapse
BusyBox is the module I always use

Downloaded a module from magiskroot.net - safe?

So like a total dumbass I didn't check the source and downloaded a module (fde.ai) from magiskroot.net . Seemed to install fine, boot took a bit longer than usual, after boot the module was not listed in Magisk manager.
Is that site safe?
Thanks!
PS I guess I'm asking opinions about the specific site...

I would investigate and open the zip and look what it changes? Did you install it in recovery or in magisk?
I don't know that site.

McFlypants said:
I would investigate and open the zip and look what it changes? Did you install it in recovery or in magisk?
I don't know that site.
Click to expand...
Click to collapse
In Magisk. I'm trying to search for added files in the system right now, nothing found so far. I have also opened the zip (just before your reply) but I'm not sure I'll be able to decipher...

krakout said:
In Magisk. I'm trying to search for added files in the system right now, nothing found so far. I have also opened the zip (just before your reply) but I'm not sure I'll be able to decipher...
Click to expand...
Click to collapse
a magisk module wouldn't change system files it'll just create a folder in data/adb/modules so look there for strange folders

jons99 said:
a magisk module wouldn't change system files it'll just create a folder in data/adb/modules so look there for strange folders
Click to expand...
Click to collapse
Only the few, known modules there. Should I assume I'm ok then?

krakout said:
Only the few, known modules there. Should I assume I'm ok then?
Click to expand...
Click to collapse
not sure it might have done something else like put a script that magisk run on boot or something maybe send me this module in pm and I'll look at what's in there

Sure thing, thanks. Also, here is the Magisk log:
jons99 said:
not sure it might have done something else like put a script that magisk run on boot or something maybe send me this module in pm and I'll look at what's in there
Click to expand...
Click to collapse
Sure thing, thanks. Also, here is the Magisk boot log: