using xposed frameworks for long time now, I have a lot of old versions of my modules on phone
where are this module versions stored?
how can I delete this old versions I never will reuse/reinstall again?
Frank
Not sure it will help, as you surely noticed that before. Anyway.... In the "Modules" section of Xposed, a long press on the module you want to get rid of will bring you the option you're looking for.
To add to what Roudier said, modules are just like normal apps and can be uninstalled the same way.
I think everyone misunderstood the question.
I think he's asking where the old versions of each module are stored, as it's possible to uninstall the latest version of a module and install an older version that you had installed without downloading it again.
Basically, where are the downloaded files stored?
kingvortex said:
I think everyone misunderstood the question.
I think he's asking where the old versions of each module are stored, as it's possible to uninstall the latest version of a module and install an older version that you had installed without downloading it again.
Basically, where are the downloaded files stored?
Click to expand...
Click to collapse
That's handled by the download manager, it's usually cleared after a reboot if I'm not mistaken.
Doesn't sound like that's what he's asking about, though.
GermainZ said:
That's handled by the download manager, it's usually cleared after a reboot if I'm not mistaken.
Doesn't sound like that's what he's asking about, though.
Click to expand...
Click to collapse
That's how I read it.
[email protected] said:
I have a lot of old versions of my modules on phone
where are this module versions stored?
how can I delete this old versions I never will reuse/reinstall again?
Click to expand...
Click to collapse
He's seems to be specifically asking about old versions of modules there.
In any case, I actually wanted to know where old versions of installed modules were stored so I could delete them and your reply provided the required information. They were all in the download manager and were not deleted after a reboot, so I manually deleted the specific old versions of modules that were no longer required. Thanks.
kingvortex said:
That's how I read it.
He's seems to be specifically asking about old versions of modules there.
Click to expand...
Click to collapse
you absolutly right.
I want to remove my old versions of modules.
kingvortex said:
In any case, I actually wanted to know where old versions of installed modules were stored so I could delete them and your reply provided the required information. They were all in the download manager and were not deleted after a reboot, so I manually deleted the specific old versions of modules that were no longer required. Thanks.
Click to expand...
Click to collapse
@kingvortex,
can please told me, where download manager is storing this modules
[email protected] said:
you absolutly right.
I want to remove my old versions of modules.
@kingvortex,
can please told me, where download manager is storing this modules
Click to expand...
Click to collapse
I deleted them via the download manager.
Enter it via "Downloads" in your app drawer, then long press any item you want to delete and a trash icon should show up to allow you to delete them (at least that's how it works on my device).
Hi,
that's easy
I must confess that I rarely used the App Drawer and the download app I've never particularly noticed
This is about to change, thanks for the hint :good:
Frank
You're welcome.
Related
Updated XposedInstaller 3/sept
As you all want to save your photos/videos to your external card (like I wanted), I give you my solution for this problem.
The solution is based on these two threads:
- Pictures2SD: http://forum.xda-developers.com/showthread.php?t=2408880
- XposedFramework: http://forum.xda-developers.com/showthread.php?t=1574401
Thanks to davisNT and rovo89
After some research here is my short method to make your Google Edition saving photos/videos to external card:
1. I attached two files, you have to download them to your phone
2. Install de.robv.android.xposed.installer_v18_e88d8b.apk
3. Launch the Xposed Installer, give it root, and click on "Install/Update"
4. Reboot your phone
5. Install Pictures2SD_102.apk
6. Launch Xposed Installer, go to the modules page and select the checkbox for Picture2SD
7. Reboot and it's done
I hope I don't forget anything, and I'm sure you can do it yourself if I missed something.
Tuningszocske said:
As you all want to save your pictures/videos to your external card (like I wanted), I give you my solution for this problem.
After some research here is my short method to make your Google Edition saving photos/videos to external card:
1. I attached two files, you have to download them to your phone
2. Install XposedInstaller.apk
3. Launch the Xposed Installer, give it root, and click on "Install/Update"
4. Reboot your phone
5. Install Pictures2SD_102.apk
6. Launch Xposed Installer, go to the modules page and check Picture2SD
7. It's done
I hope I don't forget anything, and I'm sure you can do it yourself if I missed something.
Click to expand...
Click to collapse
I get the following when trying to open "Modules" cannot read/data/xposed/modules.whitelist
Get the same error when installing Pictures2SD
Did you installed Xposed properly inside the installer? (the big button at the center with long text...)
Tuningszocske said:
Did you installed Xposed properly inside the installer? (the big button at the center with long text...)
Click to expand...
Click to collapse
Not sure why, but my phone will not boot after the install. I installed per directions and did use the large button. I rebooted and it is now not getting past the Google screen. I will wipe phone and try again. Anybody else tried this out yet?
I am sure I did something wrong, not sure what it is.
Wait a minute, it finally rebooted after 5 tries. I will see what happens now.
Nope, still has same error and will not load P2SD
Thanks for sharing. However this is not your work, so I think in your OP you should give credit to the people that created Pictures2SD and Xposed Framework.
- Pictures2SD: http://forum.xda-developers.com/showthread.php?t=2408880
- XposedFramework: http://forum.xda-developers.com/showthread.php?t=1574401
muoino said:
Thanks for sharing. However this is not your work, so I think in your OP you should give credit to the people that created Pictures2SD and Xposed Framework.
- Pictures2SD: http://forum.xda-developers.com/showthread.php?t=2408880
- XposedFramework: http://forum.xda-developers.com/showthread.php?t=1574401
Click to expand...
Click to collapse
I didn't say it is my work. I created this thread with my own words without copying anything, because a lot of people wrote in Galaxy S4 sections that Google Edition ROMs haven't got this function and cannot be solved. I also needed this, and made a research, and it was not fast. And because those threads you mentioned are far from the Galaxy S4 sections, and not completely understandable seperately for almost everybody, I finalized and simplified here as the real solution. Cheers!
wilbarger said:
Not sure why, but my phone will not boot after the install. I installed per directions and did use the large button. I rebooted and it is now not getting past the Google screen. I will wipe phone and try again. Anybody else tried this out yet?
I am sure I did something wrong, not sure what it is.
Wait a minute, it finally rebooted after 5 tries. I will see what happens now.
Nope, still has same error and will not load P2SD
Click to expand...
Click to collapse
Did you select the checkbox of the P2SD on the module page?
Tuningszocske said:
I didn't say it is my work. I created this thread with my own words without copying anything, because a lot of people wrote in Galaxy S4 sections that Google Edition ROMs haven't got this function and cannot be solved. I also needed this, and made a research, and it was not fast. And because those threads you mentioned are far from the Galaxy S4 sections, and not completely understandable seperately for almost everybody, I finalized and simplified here as the real solution. Cheers!
Click to expand...
Click to collapse
Your still going to have to credit the work your posting that someone else created and developed. Please update your OP.
You need to credit davisNT and rovo89 they Developed the work your linking.
We appreciate your efforts in finding a way to get pics to SD.
Thank you
Sent from my GT-I9505G using Tapatalk 2
Tuningszocske said:
Did you select the checkbox of the P2SD on the module page?
Click to expand...
Click to collapse
I still get the error when selecting the module page. I did a total reinstall and get the same error.
Which ROM you use?
Thank you for updating OP!
Sent from my GT-I9505G using Tapatalk 2
Tuningszocske said:
Which ROM you use?
Click to expand...
Click to collapse
CM10.2 latest nightly.
Uninstall the XposeInstaller I attached first. Try the updated installer (de.robv.android.xposed.installer_v18_e88d8b.apk) from the first post!
Tuningszocske said:
Uninstall the XposeInstaller I attached first. Try the updated installer (de.robv.android.xposed.installer_v18_e88d8b.apk) from the first post!
Click to expand...
Click to collapse
I just edited the system folder to add media r/w permissions and it works that way. Thanks for taking the time to work on this. It is easier than editing the system folder (and probably safer), but I have done the edit and will just use it that way.
everything went smooth
open up camera app and its asking me to install an SD card into phone before using camera.... i have a 64Gb card...
formatted SD card as well.. still no change
Anyone solved this challenge for CM10.2?
Would love to use CM10.2 for a while but the lack of pic to SD makes that a bigger pain than it should be.
thepktrckt said:
Anyone solved this challenge for CM10.2?
Would love to use CM10.2 for a while but the lack of pic to SD makes that a bigger pain than it should be.
Click to expand...
Click to collapse
Send me a PM and I will give you a link. Don't want to hijack this thread. The OP has worked hard on this and I respect what he has done.
WhiteSRT69 said:
everything went smooth
open up camera app and its asking me to install an SD card into phone before using camera.... i have a 64Gb card...
formatted SD card as well.. still no change
Click to expand...
Click to collapse
Try to reformat the card...
Tuningszocske said:
Try to reformat the card...
Click to expand...
Click to collapse
already did that as stayed in my original post. no go
Try format ext4 with computer, if doesn't work, try to format with the phone!
This has been fixed xda postNote: 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.
Ive read that Xposed for Lollipop has issues with Sygic.
Is this true??
UPDATE 2015 10 10: rovo89 has taken a personal look at the problem and it seems to be fixed in later versions of Xposed. Here is his comments thruout this thread if you don't want to read the entire thread (like I had to do):
rovo89 said:
Could you try this test build please? It fixes a problem that results in crashes (dump contains "art::Field_get"). It also disables Xposed's resource hooking mechanisms inside the Sygic process, as they have implemented something very similar which also replaces resources at low level.
Click to expand...
Click to collapse
rovo89 said:
Forgot to mention that after flashing this, you have to clear the Dalvik cache or reinstall Sygic. Obviously, tests only make sense if you're using the original/unpatched app and experience crashes with Xposed v70.
Click to expand...
Click to collapse
rovo89 said:
That's totally correct, but for the average user, it's a much simpler to simply delete the whole cache or reinstall the app.
Cool, thanks for testing! So I'll publish an official update soon with these fixes and also commit and push them to GitHub. I'm pretty sure that the authors of unofficial versions will quickly pick them up.
Click to expand...
Click to collapse
rovo89 said:
There's already an option that disables resource hooking completely for the whole ROM. That's useful in case the ROM itself comes with resource-modifying code. Sygic is the first application I'm aware of that "hacks" the system code at such a low level. So I don't think such an option would be required, and in most cases, people wouldn't know exactly when to use it, which would result in strange bug reports for modules which stop working if you disable the wrong thing.
Click to expand...
Click to collapse
rovo89 said:
Are you referring to my comments above? I just said they're modifying resources. Didn't check what they do with that in details, maybe replacing drawables/texts on the fly? I haven't checked whether they do any changes to GPS.
Click to expand...
Click to collapse
rovo89 said:
Not crashing for me with the (expired) trial. Maybe you block access to contacts with some app or module?
Click to expand...
Click to collapse
rovo89 said:
Sygic is working fine for me with v71 - as much as I could test without buying premium. If you still have issues, please send me the logcat of the crash. I can't exclude that there are still issues, but I can't look at them without the log.
Click to expand...
Click to collapse
rovo89 said:
I can't make any sense out of this. It's looking for the class com.flurry.android.FlurryAgent and can't find it. It doesn't seem to use the app's class loader though but the system class loader, so maybe that's a bug on their side. Then again, this might not even be the root cause, as it only tries to load this class because something in Android_ContactsReadNext seems to have failed. If you use any kind of privacy app or ROM feature that might block access to contacts, that could be the reason. It might also be a contact with invalid or too long fields. Have you tried if the same issues appear without Xposed?
Click to expand...
Click to collapse
rovo89 said:
You probably mean the general issues with Sygic that I've fixed with v71. There seems to be an (individual?) issue where the app still crashes when going to the contact selection, but works fine otherwise.
Click to expand...
Click to collapse
Sygic 15.2.2 works with Xposed on my Galaxy S5 with LP
godmode1970 said:
Sygic 15.2.2 works with Xposed on my Galaxy S5 with LP
Click to expand...
Click to collapse
Downgrading to 15.0.4 works. Anything else just fails.
Im sure it is NOT a Sygic problem, its Xposed interfering with Sygic.
@alemtro
How can i delete xposed (to get back SYGIC working) and fix the messaging app crash ( 8.1.1) ??
Same here on One M8 with stock lollipop 5.0.2 ROM. Sygic works only till 15.0.4.
Sygic crashes with Xposed for Lollipop on Moto G 2014
On Moto G 2014
... crashes on Motorola Stock ROM 5.0.2
... crashes on CM12.1 (5.1.1)
Sygic version: 15.1.15
(works fine with Xposed on KitKat)
rabah5 said:
@alemtro
How can i delete xposed (to get back SYGIC working) and fix the messaging app crash ( 8.1.1) ??
Click to expand...
Click to collapse
Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:
Go into /system/bin/ and delete app_process32 and app_process32_xposed
Rename app_process32_original to app_process32
Delete dex2oat and rename dex2oat.orig to dex2oat
Repeat the above step for oatdump and patchoat
Go up a directory and then into the lib directory
Delete libart.so and rename libart.so.orig to libart.so
Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
Delete libxposed_art.so
Go up a directory and delete xposed.prop
Go into framework directory and delete XposedBridge.jar
Reboot your device.
Yeah, Sygic is completely broken with Android 5.0 and Xposed.
Any fix to sygic 15.x.x on android 5 + xposed?
Thanks all!!!
AFAIK, Sygic is working on this problem, but it is a low priority issue for them, so they didn't wrote any ETA.
Well. That's a big problem. I've been waiting patiently for xposed and now that it works I cannot use Sygic (btw it costed me 15€ Eur+Russia). How can I get back to the version that works with xposed? Legally, I mean. Or can anybody try that module which hides root for a specific app? I don't remember its name. Please.
ciccio83q said:
Well. That's a big problem. I've been waiting patiently for xposed and now that it works I cannot use Sygic (btw it costed me 15€ Eur+Russia). How can I get back to the version that works with xposed? Legally, I mean. Or can anybody try that module which hides root for a specific app? I don't remember its name. Please.
Click to expand...
Click to collapse
Legally, you should try to search and download an official apk of version 15.0.4, install it and disable auto update in Play Store.
The app you search for is called RootCloak but it does not make any difference.
Sent from my NotePRO 12.2 LTE using Tapatalk.
Well. To be onest with you I found only modded apk. And it bothers me because I don't wanna use a cracked app when I paid for it. Thanks anyway. No xposed for now.
Can someone give the 15.0.4 package. The support gives me only the 15.0.9 package which is crashing at start too..
Thanks
I'm running Sygic 14.7.4 on my device with Xposed and it's fine with 2014.09 TA maps. 15.x.x does not work-crashes.
Same issue here, tried to find 15.0.4 as well, but only cracked versions laying around which I don't want. There are basically two options:
- disable xposed, reboot, use Sygic, then enable xposed, reboot (time consuming)
- use another navigation (Copilot, Tomtom,..)
_mysiak_ said:
Same issue here, tried to find 15.0.4 as well, but only cracked versions laying around which I don't want. There are basically two options:
- disable xposed, reboot, use Sygic, then enable xposed, reboot (time consuming)
- use another navigation (Copilot, Tomtom,..)
Click to expand...
Click to collapse
Disable xposed? How? Did you try disabling all the modules? The problem is that if you want to disable xposed completely it is a long process. I mean I cannot wait 20 minutes every time. And I don't wanna use a very old version of the app. There should be a workaround.
Surely, this is Sygic 15.0.4 original (official) version:
Link for download
ciccio83q said:
Disable xposed? How? Did you try disabling all the modules? The problem is that if you want to disable xposed completely it is a long process. I mean I cannot wait 20 minutes every time. And I don't wanna use a very old version of the app. There should be a workaround.
Click to expand...
Click to collapse
Create an empty file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
For example from TWRP or terminal type this command and reboot:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
You can create flashable file, or terminal shortcut to speed up the process. To enable Xposed again, just delete the "disabled" file (through file manager or from terminal again).
Source
I've tried 15.0.4 it's working but crashing during navigation, the moment you start navigation it'll crash. Checked with Nexus 7 DU 5.1.1 and Xiaomi Mi3 Mokee 5.1.1.
Exist an easy way to export magisk module list? Export and import?
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Didgeridoohan said:
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Click to expand...
Click to collapse
only the one i have installed. full list for backup / reinstall purpose. installed and not active. xposed ha a function to export /import list. I like it.
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
simona70 said:
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
Click to expand...
Click to collapse
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Thanks. Providential.
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Where are the ZIP files located, in case I just want to backup those rather than the img?
oroboros74 said:
Where are the ZIP files located, in case I just want to backup those rather than the img?
Click to expand...
Click to collapse
Zip files are not saved. It gets extracted in to the location as mentioned in this thread. But each time you flash a module the zip file is downloaded in to Download folder of your internal storage. Save it for future use.
Now /data/adb/magisk.img is no more used... What folder must I backup?
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
Hi how can i find data/adb/magisk/img
Sk7007 said:
Hi how can i find data/adb/magisk/img
Click to expand...
Click to collapse
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Didgeridoohan said:
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Click to expand...
Click to collapse
How to backup now then?
Sent from my motorola one power using Tapatalk
Always wondered the same..
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
rodken said:
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
Click to expand...
Click to collapse
I actually havent tried it since the change from the img method
I can tell you i do backup and restore the magisk.db file....i have a Galaxy Active2 Watch, and if it even sniffs root i have to reset the watch and start over to get Samsung Pay working. So i flash the ROM/GApps, then Magisk, reboot and setup the ROM and Magisk, set my Android ID back to the previous one (to avoid having to reset the Watch, and have it connectable in Gear app) then copy the magisk.db to /data/adb, then reboot. Then enable MagiskHide, and hide Magisk Manager. When i restore my apps the Samsung ones are already in the MagiskHide list and Samsung Pay works as before, once i reconnect the watch.
Next time i flash ill try copying back the /data/adb/modules and let you know
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
73sydney said:
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
Click to expand...
Click to collapse
Thanks for the update.
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: