Since Magisk won't let me install terminal systemizer, i decided to make my own module template that'll install any apk of your choice as a system app. Instructions to customize it are in the zip file (i made them as easy as possible lol)
Just let me know if y'all have any problems with the module and I'll get back to you ASAP
Related
very good friends. some tutorial to install "RRO Layer Theme" in my Motorola Nexus 6 has installed Android 6.0 stock rom. My device is root.. Thanks in advance
Create /system/overlays folder (all lower case)
Download Layers Manager from Play
Download any Layers theme from play.
Open the theme from app drawer and follow instructions.
Ultimately, all layers manager does is take the individual apk themes (packged up in the apk you install from play) and put them in /system/overlays. So in theory, you could open the apk from play store with a zip / archive application and extract all the apk's inside it and put them there. Set permissions and reboot.
To add to the above, you may also need to do a couple other things if you haven't already.
I am pretty sure Layers Manager requires Busybox, so you may need to install that. The app may inform you if it needs it or not.
If you are indeed on 100% stock you may need to free up some space on your system partition. Marshmallow takes up a lot of space on the partition, which can make it impossible to install a theme since it installs to /system/overlays.
I found this Xposed module (https://github.com/Frazew/VirtualSensor/releases/) which can emulate a gyroscope using data from the accelerometer and compass.The problem is that I cannot install Xposed / root since it will break apps which use CTS like Android Pay (systemless won't work too).So I need to inject the module into the APK by editing the code so it calls the modified modules.
Is there any tool like this or can you create one
Does anyone know how to edit tags for a post on XDA ?
I'm planning to install the latest Magisk Manager on a fresh install, now that Google has removed it from the play store.
I have a zip file that I flash after installing my ROM, which adds and modifies some personal files.
I wanted to add the latest Magisk Manager APK into this zip, so I can flash it after flashing Magisk 12.0, and not have to update the app manually. However, I'm not actually sure where the initial installation of Magisk Manager ends up. I don't see it in /system/app or /system/priv-app. Does anyone know where it would be, or if this is even possible?
the magisk manager is included in latest beta zip
JohnHorus said:
I'm planning to install the latest Magisk Manager on a fresh install, now that Google has removed it from the play store.
I have a zip file that I flash after installing my ROM, which adds and modifies some personal files.
I wanted to add the latest Magisk Manager APK into this zip, so I can flash it after flashing Magisk 12.0, and not have to update the app manually. However, I'm not actually sure where the initial installation of Magisk Manager ends up. I don't see it in /system/app or /system/priv-app. Does anyone know where it would be, or if this is even possible?
Click to expand...
Click to collapse
It's not installed as a system app. It's in /data/app.
While we're waiting for the next release (with the app bundled into the zip) you should be able to replace the stub in the Magisk zip with the proper apk. It's in the common folder in the zip.
Didgeridoohan said:
It's not installed as a system app. It's in /data/app.
While we're waiting for the next release (with the app bundled into the zip) you should be able to replace the stub in the Magisk zip with the proper apk. It's in the common folder in the zip.
Click to expand...
Click to collapse
OOOhhhh, so the very initial installation from the zip goes into /data. I guess that makes sense, as systemless is the entire point. Derp! Shoulda thought about that a little more.
Putting the newest manager into the Magisk 12 zip would be ideal, though. Do I just replace [Magisk-v12.0.zip/common/magisk.apk] with the Magisk Manager 4.3.3 apk from the main thread, and rezip? Thanks so much for your help! = )
JohnHorus said:
OOOhhhh, so the very initial installation from the zip goes into /data. I guess that makes sense, as systemless is the entire point. Derp! Shoulda thought about that a little more.
Putting the newest manager into the Magisk 12 zip would be ideal, though. Do I just replace [Magisk-v12.0.zip/common/magisk.apk] with the Magisk Manager 4.3.3 apk from the main thread, and rezip? Thanks so much for your help! = )
Click to expand...
Click to collapse
Should be working if you swap APK from zip
Envoyé de mon m8 en utilisant Tapatalk
I am customizing a Amlogic TV Box ROM and I would like to install Xposed as well as a home-made module in it. I can't edit the Java source code directly because I don't have access to it, so the only solution I have is editing smali code (no thx) and Xposed.
I have access to the system partition content of the ROM, and nothing much more. My module will be installed as a system app, but I can't find a way to have the Xposed framework pre-installed. I tried to simply extract the ZIP in the system partition folder, but it doesn't work : the Xposed Installer says that the Framework is installed but not active. If I install the Framework using the Installer afterwards, it works fine. What am I doing wrong ? Is there some procedure to follow after unpacking the files ? Is it even possible to have it packaged with the system and not installed ?
I still need to enable the module once the framework is installed, how may I do that ? The modules list is located into /data, which is not packaged with the ROM (and is not factory-reset proof) what would be the most elegant way of having the module enabled by default ? I thought of writing to the modules list file at each boot with the Init.rc but I think there's a better solution.
Thanks for the help
I think what's theoretically happening is:
Imagine a PC - you install an app via the normal wizard, goes through and installs registry keys etc. which stores all file paths etc. and the app opens after the wizard finishes.
What's happening here is you're just taking the files and placing them onto the PC yourself, in this case, your box.
Remember this is a SYSTEM app, not something you can drag and drop on.
You haven't flashed anything in order for the System to know Xposed is installed, for it to point to this, point to that.
You're essentially running a broken, portable Xposed which'll say installed only because you placed it there.
I'd say you have to probably play about with that ROM on somewhere you can install Xposed via custom recovery then play about with nandroid backups and restore them on your box?
That's my only assumption. This is a difficult one.
That was my guess too, but I looked at the flashing script that Xposed Installer executes and I feel like it only checks for the version/api/abi and copies files, creating backups for uninstallation. All the files are present in the system partition in my packaged ROM files so I thought that they would just work out of the box if I copied them. Well, it doesn't, I must be missing something that the installer does.
In the meantime I've put a dirty installer in my launcher : it checks for the xposed.prop file each time it's opened (uuugh) and if it's not installed it'll just run the flash script and reboot. That's not elegant but it works.
Hello, I have a rooted smartwatch, Ticwatch Pro 4G, with a custom ROM. It has a NFC module, which I wanted to use with app called "NFC Card Emulator". It works on my phone, but NFC module on it broke, so I am forced to use it on my watch. That app tries to edit file
Code:
/vendor/etc/libnfc-hal-st.conf
but it has no RW permissions, app suggest reboot but it doesn't work. I cannot also manually mount /vendor.
So, here is where I need help:
I have no idea if this is possible, but how can I create a module, that will allow that app to edit that file? Is there a way that I can "route" it or something to a place where it can be edited by the app?
I have no experience with making magisk modules, or android programming.