All this comes from "luminoso" user , (I don't know whether responsable or irresponsible explained) Who explain us we can move Storage app to SD card via magisk module folder binder, because I have a big issue with Whatsapp, so far I have 10GB in the folder.
To truth is after reviewing the steps, I follow strictly the process, first paying 20 euros to xperifix, and after magisk installation and folder finder.
I execute the module via emulator :
Fbind -a
And I add this lines
from_to WhatsApp WhatsApp
It does not Work!
Also I installed Exsdcard access enabler
It does not work
Any expert from here can help me out
Thanks
!!
reckfield said:
All this comes from "luminoso" user , (I don't know whether responsable or irresponsible explained) Who explain us we can move Storage app to SD card via magisk module folder binder, because I have a big issue with Whatsapp, so far I have 10GB in the folder.
To truth is after reviewing the steps, I follow strictly the process, first paying 20 euros to xperifix, and after magisk installation and folder finder.
I execute the module via emulator :
Fbind -a
And I add this lines
from_to WhatsApp WhatsApp
It does not Work!
Also I installed Exsdcard access enabler
It does not work
Any expert from here can help me out
Thanks
!!
Click to expand...
Click to collapse
Have you made a folder called Whatsapp on the SD card?
Nop. I didnt make folder
I just introduce fbind -mb
And automatically the files are move and folder was created
Related
Hi.
I have been emailed an APK file for an App and need to install it.
I have transferred to the root directory of the phones SD card, but am stuck from there.
Any ideas?
have you tried just going into your files and selecting it. Usually it will prompt you to install the .apk and thats about it. You might need to allow non market apps, but it again should prompt you to do all this. There is probably another way, but i've never had to do any other extra steps.
scott2ride said:
Hi.
I have been emailed an APK file for an App and need to install it.
I have transferred to the root directory of the phones SD card, but am stuck from there.
Any ideas?
Click to expand...
Click to collapse
Download Easy Installer from the market. It is free and will install from internal or external memory.
Thanks. Mucy appreciated
I usually have defaulted to easy installer but have had an eye opener with system apps because they are not that easy. I guess sys apps you need to push with adb or need a root file explorer co copy and paste the app within a specific directory file
I had trouble installing the Xposed framework on the 4.3 leak with the app, so I looked through the source code for it and installed it manually. This will be a guide to help anyone who wants to get the framework on 4.3 and the Xposed framework app will not install it.
This should work on any 4.3 device, such as our Nexus 4 or the GPE devices
EDIT: Still works on release 4.3 (JWR66V)
What you will need
1) The Xposed framework installer app (http://forum.xda-developers.com/showthread.php?t=1574401)
2) A root file explorer of your choice (Solid explorer was not working for me for some reason, so I used ES File Explorer)
3) Root (4.3 root by Chainfire floating around the forums)
4) BusyBox (If you have root, you probably already have it, if not https://play.google.com/store/apps/details?id=stericson.busybox)
*Optional* If your file explorer does not show you any numbers when setting permissions (ES does not), google "CHMOD calculator"
Steps
1) Download the Xposed installer on your phone and install it
2) Navigate to the directory you downloaded the Xposed installer to in your file explorer
3) Rename the installer from "XposedInstaller_x.x.x.apk" to "XposedInstaller_x.x.x.zip"
4) Open the file you renamed, and it should open like any other zip file. Navigate to /assets/armv7-a
5) Copy app_process_xposed_sdk17 to internal memory
6) Open the file again, navigate to /assets/
7) Copy XposedBridge.jar to internal memory
8) Close the .zip, rename .zip back to .apk, we are done pulling files from the app now
9) Go to your internal memory and rename "app_process_xposed_sdk17" to "app_process"
10) Mount /system as read/write if your file explorer does not automatically do so (ES does not do it automatically, Solid Explorer does)
11) Navigate to root, then /system/bin/
12) Rename "app_process" to "app_process.orig"
13) Copy app_process from your internal memory, and paste it in /system/bin/ (So that it replaces the file you just renamed)
14) Long press app_process, click on properties, and change the file permissions to 755 (This is where the CHMOD calculator comes in handy)
15) Change the file Owner and Group of app_process to "root" and "shell" respectively (Also in properties)
16) Go to /data/ and make a folder called xposed
17) Long press the folder, hit properties and set the permissions for the folder to 755
18) While in properties, set the Owner and Group of the folder to "root" and "shell" respectively
19) Go back to where you copied XposedBridge.jar in step 7 and copy it to /data/xposed/
20) Long press it, click on properties, then set the permissions to 644
21) Stay in properties and set Owner and Group to "root" and "shell" respectively
22) Open the installer app, then open Terminal Emulator
23) Type in
Code:
ps
I recommend holding the phone sideways for this
24) Look for de.robv.android.xposed.installer on the right side. Once you find it, write down the first 6 characters of that line (Should be something like u0_a[number][number]) If it doesn't look like that, check the line directly above.
We will call this "$6char"
25) Open the file explorer again, and go to /data/xposed/
26) Make 2 files, name one
Code:
modules.list
and the other
Code:
modules.whitelist
27) Long press on modules.list, hit properties, set the permissions to 644, and change Owner and Group to "$6char" and "shell" respectively
28) Long press on modules.whitelist, hit properties, set the permissions to 644, and change Owner and Group to "$6char" and "shell" respectively
29) Reboot
30) Open the Xposed installer and check if it sees the install. If so, it should be working. Done!
Subscribing to the topic because I want to find out when the original framework gets modified to install properly on 4.3
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Installed? Yes. Working? I can't say. Well, I can say that it isn't working the a Hack Connectivity 1.2 thing I use for tethering my tablet to my laptop. It does show that the framework is installed, but there may be more to be done.
Great work but this is still the SDK17 (JB4.2.2) version of things. Tungstwenty posted updated compiles for SDK18 (JB4.3) last Thursday with a link to a simpler manual install procedure:
http://forum.xda-developers.com/showpost.php?p=43923460&postcount=2249
I then automated that in a flashable zip:
http://forum.xda-developers.com/showpost.php?p=44013064&postcount=2308
dsp4774 said:
Installed? Yes. Working? I can't say. Well, I can say that it isn't working the a Hack Connectivity 1.2 thing I use for tethering my tablet to my laptop. It does show that the framework is installed, but there may be more to be done.
Click to expand...
Click to collapse
Some modules don't play nice with SDK 18, most do in my experience.
osm0sis said:
Great work but this is still the SDK17 (JB4.2.2) version of things. Tungstwenty posted updated compiles for SDK18 (JB4.3) last Thursday with a link to a simpler manual install procedure:
http://forum.xda-developers.com/show...postcount=2249
I then automated that in a flashable zip:
http://forum.xda-developers.com/show...postcount=2308
Click to expand...
Click to collapse
Nice!
Working fine, although I didn't have to install it on the app, and if I tried, the same error would pop up, but it shows that app_process is 34 and XposedBridge.jar is 2.1.4, but no errors at all.
I've been a lurker on XDA for 3+ years now, but this post finally compelled me to register an account.
THANK YOU SO MUCH FOR THIS. I thought I was going to have to go back to 4.2.2 or use the default icons. You saved my phone from being an antique/hideous.
:laugh:
Hey guys,
i tried these steps but i get this tooltip: cannot write /data/xposed/modules.whitelist :/
Hope you guys can help me. I am on PA 3.99 Nexus4.
I'm getting the same error - n4 with latest cm12 nightly (23rd Aug build) :'(
Sent from my Oric-1 micro
Does not work on my HTC One S with odessey rom (jb 4.3). I tried several times, but it always stocks on boot screen. So if anyone - maybe with an HTC device - has got this working and has any suggestion, please let me know.
HTC_HDD said:
Hey guys,
i tried these steps but i get this tooltip: cannot write /data/xposed/modules.whitelist :/
Hope you guys can help me. I am on PA 3.99 Nexus4.
Click to expand...
Click to collapse
I see some things wrong:
You don't have the .jar installed
If it complains about the whitelist file, try running:
Touch /data/closed/modules.whitelist
Then change the permissions to match what the instructions said (755 and root:root )
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
osm0sis said:
Great work but this is still the SDK17 (JB4.2.2) version of things. Tungstwenty posted updated compiles for SDK18 (JB4.3) last Thursday with a link to a simpler manual install procedure:
http://forum.xda-developers.com/showpost.php?p=43923460&postcount=2249
I then automated that in a flashable zip:
http://forum.xda-developers.com/showpost.php?p=44013064&postcount=2308
Click to expand...
Click to collapse
I installed the new app and update and installed it and works fine, i was able to activate the keepchat module also, however when I use snapchat it doesn't save snapchats opened??
Can you please help...
Thanks
I've done everything using adb on my Nexus 7 running CyanogenMod 4.2 nightly 20130824, and it worked like a charm! Finally I'm able to use the "Xposed App Settings" module again.
Thank you!
Erwin
EDIT:
Although I'm wondering what will happen if I update my nightly...
Installing another ROM will overwrite the app_process file. Also, if the xposed framework app won't install without doing the steps I wrote in the first post, try updating super su in recovery.
Sent from my Nexus 4
i fixed it like this
I just copied from another phone the files found in the
Data/xposed and it fixed the error (cannot write data/xposed /modules......)
i want framework for android 4.4
help
yes i have same problem now... my phone is tucked at the boot screen .. i think wipe
yes i have same problem now... my phone is tucked at the boot screen .. i think wipe data or factory rest may help .,. but i will lose my pictures and rest of media .. i donot have any backup:crying:
Is aviable and stable on lollipop?
Hello Fellow Users,
Let me start with the fact that I have zero experience of making flash modules (TWRP/Magisk) and am just dabbling around.
Some background, I found a TWRP flash zip file which makes changes to vendor partition of Redmi Note 7 Pro (violet) running MIUI OS (Android Q) - this is a sound mod.
Now, with TWRP file the issue is that if it doesn't work or has any issues, we need to dirty flash ROM all times (or atleast dirty flash the vendor partition). There is no one-click remove option.
Hence I thought why can't the same be done via Magisk systemless and dabbled around a bit. Below is my experience of the last 2 days.
Now, coming to the original TWRP file - it copies/replaces three folders with included files to vendor partition. Path of folders is following
Code:
/vendor/etc
/vendor/lib/soundfx
/vendor/lib64/soundfx
These 3 folders and similarly named files within them already exist by default in the phone prior to flashing.
Now basis the Magisk guides I saw around and wiki from @Zackptg5 I did the following changes to the default template:
1) Edited customize.sh to define folders to be replaced
Code:
REPLACE="
/vendor/etc
/vendor/lib/soundfx
/vendor/lib64/soundfx"
2) Since Magisk will always look for the vendor under the system folder and so I moved the vendor folder under system folder
Basis same, created attached module and flashed and it installed.
But then three queries in my mind:
1) Are the new files actually replaced systemless and in-use? My concerns as don't see any intended change in sound
2) Is there a way to check if new files are being used o available to system?
3) Is this method of putting replace under customize.sh file the way out? While studying some similar modules making changes to vendor partition, I found that they have default (no change) customize.sh but rather make changes to common/post-fs-data.sh etc
So, looking forward to feedback from users experienced in making Magisk module. Thanks in advance for your time and efforts!
PS: attached is the WIP module which I wrote and also got installed in Magisk Manager
TLDR: How to make a Magisk Module using TWRP files to ensure systemless modification of folder/files in the vendor partition
1 - The REPLACE variable is used to replace the directories you specify with empty folders, not with what you want to add systemlessly. You might want to follow the advice written in the customize.sh file and read the documentation (@topjohnwu has everything explained there):
https://topjohnwu.github.io/Magisk/guides.html
Edit: If you do want to first "remove" (systemlessly, of course) everything in those folders, then keep them in the REPLACE variable. I just realised that it's a little unclear if that's what you want to do or not...
2 - That's the correct procedure. If all you want to do is to add or replace some files to your device, the only thing you need is to put those files in the /system directory of your module. That's it. The customize.sh file is used if you want to customise the installation logic of your module (not necessary if you're just adding files to your device) and post-fs-data.sh and service.sh are boot scripts to run code at boot (again not necessary if you're just adding files systemlessly to your device, see the linked docs for details).
Right now your module isn't adding anything, since the directories in the module's system folder are all empty. There's nothing to add. All it does is to replace those directories with empty ones (see #1 above). I'd say that using MMT is way overkill for such a simple module...
One you've installed a module Magisk will mount that modules files over your existing ones at boot. If the file under the real system path matches the one found in the module directory (under /data/adb/modules) everything is working as it should.
@Didgeridoohan Thanks for taking our time to give detailed reply and guidance
Finally was able to successfully install the module (named AudioEngine) and I do see files under /data/adb/modules but I have the following issue:
All these new files are under:
/data/adb/modules/AudioEngine/system/vendor folder and not under
/data/adb/modules/AudioEngine/vendor folder
Is that ok? If yes, why do we see /data/adb/modules/AudioEngine/vendor separately too?
Attached is final module as well as the screenshot of /data/adb/modules/AudioEngine/ as seen in file manager.
The /vendor folder is a symlink to /system/vendor, created by Magisk. That's just how Magisk works...
From your screenshot it looks like things are working as they should.
That uninstall script looks unnecessary though. The module isn't placing or altering anything outside the module folder, so when uninstalled there won't be any leftovers anyway.
im also try to do something similar with some audio libs in vendor partition for poco f2 with miui12 however if i add any libs to go into vendor/lib, for some strange reason, i lose wifi. theres no issues if vendor/lib/soundfx or vendor/lib64 is occupied with files just the lib directory only. the actual files that are going into lib are not replacing anything but are new files
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
DanHoliday said:
Hello,
I'm trying to create my own Magisk module based on working modules and referencing the module instructions. Before getting too far, I wanted to make sure that the compression process worked correctly.
So, I downloaded a .zip module from the Magisk app (e.g. Wifi5ghzdisabler), moved .zip to my Ubuntu 20.04 PC using Google Drive, extracted the .zip (using Extract Here in Files context menu), compressed the module folder back to a .zip file (using Compress... in Files context menu) and then moved the new .zip back to the phone using Google Drive. No changes to any files were made. Then, I tried to install it from storage in the Magisk app (v23.0) on a OnePlus Nord N100 running Android 10, but I encountered the following error.
Installation Failed!
- Copying zip to temp directory
! Unzip error
Is this a compression issue or a permissions issue on the phone? I'm probably missing something simple. Thanks in advance.
Click to expand...
Click to collapse
You should upload your zip.
Thanks for the reply.
I've attached the original WiFi5GhzDisabler-v1(1).zip module downloaded from inside the Magisk app.
I've also attached WiFi5GhzDisabler-v1(1)-re-compressed.zip after downloading, extracting and re-compressing the original module it as described in my first post. I didn't make any changes to the files/folders themselves. I did notice they are different sizes (6.1KB original versus 8.6KB re-compressed).
I'm trying to learn more about the correct compression process/tool for these modules. I searched the forum and found a thread with a similar issue. Basically, the OP shared a .zip file that didn't work and another member did something and uploaded a "fixed" version with minimal insight into how it was done.
[HELP] This zip is not a Magisk Module
I would assume there isn't anything wrong with the files in the original module since it was probably reviewed before it was hosted in the Magisk app. It is also strange that the .zip file downloaded from the github repos for various modules don't work for me either, but that may be a separate issue.
Any ideas? The instructions do not include how to compress the module.
Take a close look at the original zip again, and compare it to the one you recompressed. You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Didgeridoohan said:
You've put all the files in a directory inside the zip, in comparison to putting them directly in the root of the zip...
There's your problem.
Click to expand...
Click to collapse
You're exactly right. I was incorrectly zipping the module folder itself rather than the files inside the folder. As you correctly pointed out, this creates a folder inside the zip that adds an extra layer between the files and the root of the zip.
Wow, what a simple mistake. With your help, the recompressed module installs fine now. I was able to install my own module too!
Thank you so much for your help. My issue has been resolved.
I have an LG V60 phone and I would like to put the phone in "high impedance mode" all the the time for more power to the earphones even if they are less than 50 ohm impedance.
In LG V40/50, it was very simple by rooting the phone and making some modifications in the one of the files that was in the "vendor/etc" directory. The problem with LG V60 is it does not allow any write access to the vendor folder at all.
So the only feasible option that I can think of is to create a Magisk module that replaces the original file with the modified one. My biggest disadvantage is not knowing anything about writing codes including Magisk module ones. So I was wondering if anyone could create a Magisk module that would replace the original file through Magisk?
ADDTIONAL INOFRMATION:
I am running Magisk 25 on a fully rooted LG V60.
The file that needs to be changed is mixer_paths.xml and it resides in the "vendor/etc" folder. I have created the modified file.
So if someone is able to develop a module to accomplish this, I will place the modified file in the "system/vendor/etc" folder of the Magisk module, as I understand it.
Many thanks for your support!
You can use this template system in future as its super easy
The template itself is here
GitHub - Zackptg5/MMT-Extended: Magisk Module Template Extended
Magisk Module Template Extended. Contribute to Zackptg5/MMT-Extended development by creating an account on GitHub.
github.com
click the Code button, then download zip
then extract the zip into a folder and rename the folder "MMT-Extended-master" to the something more meaningful, like the name of your module
Read the wiki and docs here to go step by step to create your first module:
Home
Magisk Module Template Extended. Contribute to Zackptg5/MMT-Extended development by creating an account on GitHub.
github.com
Notably the heading:
How do I make a MMT Extended mod?
The steps for a simple file addition/replacement module, which are simple, should be steps 1-4, then 8. Then zip up the modules (as a zip) and test.
For you, if you read along (in Step 3) you will need to create a folder vendor, under the existing system one, and then a further etc folder under vendor, and put the necessary file (mixer_paths.xml in there.
If you try and fail, post back and someone will assist. But we prefer people to at least read the documentation and try first, ideally...this is the way the great didgeridoohan mentored myself and many others, he was not big on spoonfeeding
Imagine the satisfaction you might get finding out youre capable of such feats...i promise its not rocket surgery
Feel free to PM even, if you get stuck and think you have a silly question - of course knowing me, and i do, you'll probably get an even sillier, and off topic answer as well...
hint: you can knock out this basic module in far far less time than it took me to write all this
Thank you!
So my changes look like this:
1. Put the modified file in the system/vendor/etc folder of the Magisk module.
2. Made the needed changes to the customize.sh as attached.
Royaltiger said:
Thank you!
So my changes look like this:
1. Put the modified file in the system/vendor/etc folder of the Magisk module.
2. Made the needed changes to the customize.sh as attached.
Click to expand...
Click to collapse
Yes, though you'll need to uncomment (remove the leading #) from the set_perm lines to make them active, also you only really need the 2nd one
Royaltiger said:
Thank you
73sydney said:
Yes, though you'll need to uncomment (remove the leading #) from the set_perm lines to make them active, also you only really need the 2nd one
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So I made the module with the suggested changes in customize.sh and put the modified mixer_path.xml file in the system/vendor/etc folder of the module. Module installs fine with Magisk but when it reboots, the device hangs on the initial LG screen and does not go anywhere from there.
I am attaching the customize.sh snapshot. Also, attached is the module file.
See here under "Disabling/uninstalling modules manually" if youre not able to boot
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
I am assuming that it is not possible to accomplish what I wanted to achieve.
Royaltiger said:
I am assuming that it is not possible to accomplish what I wanted to achieve.
Click to expand...
Click to collapse
mixer_paths files have been replaced for years, long before magisk even...i did it back as far as the Galaxy S2 from memory, so im not sure why this didnt work for you, was the mxer_paths file specifically for your device? i have no clear idea why it hasnt worked for you
this thread has a guide to making /system RW, so you could manually copy the file and overwrite it, but id really consider how much you want to replace mixer_paths before i set out to do that
V60 Bootloader Unlock and Magisk Root
Earlier today I was alerted to https://www.cnblogs.com/yanhua-tj/p/15525593.html which has the actual firehose and steps to unlock! However it seems to be in Simplified Chinese so I'll translate it here for you. The firehose is attached below...
forum.xda-developers.com
73sydney said:
mixer_paths files have been replaced for years, long before magisk even...i did it back as far as the Galaxy S2 from memory, so im not sure why this didnt work for you, was the mxer_paths file specifically for your device? i have no clear idea why it hasnt worked for you
this thread has a guide to making /system RW, so you could manually copy the file and overwrite it, but id really consider how much you want to replace mixer_paths before i set out to do that
V60 Bootloader Unlock and Magisk Root
Earlier today I was alerted to https://www.cnblogs.com/yanhua-tj/p/15525593.html which has the actual firehose and steps to unlock! However it seems to be in Simplified Chinese so I'll translate it here for you. The firehose is attached below...
forum.xda-developers.com
Click to expand...
Click to collapse
Actually I had no problem in editing the mixer_tavil.xml file in LG V40/50. But when it comes to LG V60, the file is read-only. There is no way to edit it due to dynamic partition. Hence, I was seeking the only option available i.e., via Magisk module.
Royaltiger said:
Actually I had no problem in editing the mixer_tavil.xml file in LG V40/50. But when it comes to LG V60, the file is read-only. There is no way to edit it due to dynamic partition. Hence, I was seeking the only option available i.e., via Magisk module.
Click to expand...
Click to collapse
So, I encountered the same problem and found what you did wrong. I was able to write my own Magisk module and it works wonderfully. It took so much time to understand how to do it because there is no proper tutorial.
If you are still active and trying to know how to do it the right way, here comes the explanation:
The Replace = " /system/vendor/etc/ " must not be written as it completely wipes the actual folder from your phone. This is why you were not able to turn the phone on. It should be like this:
Replace = " " (That part must be blank)
The rest of the code is good. If you try it like this now, you will see it will work, just like mine did.
Cheers
Does not work. May I see your module? Please upload it here as attachment.
I even put my edited file under /data/adb/modules/<my directory>/system/vendor/etc. It shows up in Magisk as a module and the file loads (as it is not visible in file explorer) but there is no change in volume. So the thing is not working.