A reference to ware the file system in oxygen lays for apps.
User app= /data/app (the folders for each user app are not labeled after what they are.)
System apps (in OxygenOS))=/system/product/priv-app or /system/product/app
It depends which type of system app you intend to make to app. Either directory works.
So I like viper4android and will use it as an example.
1 download this version ViPER4Android-FX_2_7_1_0.apk
2: install it as a user app. It should work now but need the rootless driver install in twrp for it 1st.
3: boot 2 twrp, mount all partitions (works better). Flash the zip, reboot to system.
4: verify the app functions add the Ulta low buffer module or what ever else need to be hooked to the app were Systemizing.
5: everything set use a app like Sdmaid to get the actual directory name that oxygenOS installed it to. Just the 1st two letters works for this to ID it in twrp (ware we won't be able to check.
6: boot to twrp. Mount all partitions. open a file manager it has. Go-to the app's directory under /data/app/... That apps directory. Open that directory and move the next directory to...
/System/product/priv-app or /app.
7: you don't have to but you can now use the file manager in twrp to verify that the app folder moved there and rename it to a better ID if you want. Also you better compare the app's permissions to another system app in that directory and match it up.
Reboot and if the directions were followed, you have systemized an app.
This works better than a systemized app, or a magisk/twrp module. Why cause twrp work is the hands-on management.
The droidware I recommend is.
Sdmaid (lookup apps given directory name.)
Orangefox (dual boot) cause I use it.
A file manager to check you work helps. Need root authority. I recommend the one I'll linkup.
In other roms and OSs the system directory for system app placement is just /system/app or prive-app.
Don't forget to mount the partitions before any working in twrp. I realized that about flashing and twrps modules running while I'm editing my system.
Sorry not adding links or apps good luck with it.
One other thing the boot animation.zip file for changing in located /system/product/media on Oxygen 11.
Ohh yeah theirs a app on play store called partitions manage. You can save any partition live while running you OS to a .omg file. If I do that after Systemizing some apps. It makese a system.img with them included. No more work to redo.
Well gonna go get beer or white pirate stuff. Lol
Mod edit: removed references to warez app.
Related
I created a flashab;e zip or flashing TB after a fresh install.
There are two options to create ZIP to install TB as user or system app.
I see that there is an additional file in the flashable zip when i select to install it as a system app.
/system/lib/libtitanium.so
My question is
What is the diffeence between installing tB as user/system and whats the use of the additional .so file.
.so library is a native compiled (binary) library. What is it used for? I don't know, some faster functions of Titanium. Why is it in one ZIP and not it another? Because user .apk has its libs included and they're unpacked by system automatically into its own /data/data/<appname>/lib directory, while system app is expected to have its libs with the rest of system libs, and it doesn't unpack anything.
When the app is installed in /system, it doesn't take place in /data, and (AFAIK) it automatically inherits system permissions. That's about the only difference I'm aware of.
Jack_R1 said:
.so library is a native compiled (binary) library. What is it used for? I don't know, some faster functions of Titanium. Why is it in one ZIP and not it another? Because user .apk has its libs included and they're unpacked by system automatically into its own /data/data/<appname>/lib directory, while system app is expected to have its libs with the rest of system libs, and it doesn't unpack anything.
When the app is installed in /system, it doesn't take place in /data, and (AFAIK) it automatically inherits system permissions. That's about the only difference I'm aware of.
Click to expand...
Click to collapse
Bang on, thanks
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
(Preface for noobs : /system and /data are two different partitions. Freeying up /system won't get you more intrenal memory, but /data does. Old apks rest in /system and updated versions placed in /data. You can replace the old apks using newer versions)
I heared Titanium Backup PRO does something like, but you can do this with any File Explorer with ROOT access. Its works 100% for Android Gingerbread 2.3.x , try on other versions.
### Do it on your own risk, I am not responsible for anything ###
1. Update the desired app to the latest version from Google Play Store
2. Open File Manager, Enable ROOT_ACCESS, remount /System as writable
3. Goto /system/app and backup the desired apk to sdcard
4. Goto /data/app and copy updated apk
5. Paste into /System/app
6. Note down the filename of old apk and delete the old apk
7. Rename the new apk into the old filename
8. You may encounter a FORCE CLOSE if the app was running in background
9. The updated apk in /data/app will be removed automatically
10.Restart your device, Done!
I replaced Playstore, Maps, Google Search ect..
Example: For PlayStore, updated apk will be com.android.vending-1.apk, and old apk is vending.apk
Hit thanks it it works, Thanks
thanks, nice guide! All is ok (PlayStore, Terminal Emulator), but if I merge last version of "Google Play Service", then Gmail or Maps shows the message "Unknown issue with Google Play services" when I open them... do you know how to solve? thanks in advance
p.s. configuration in signature
Better use Link2SD. It makes the integration of updates into system seamless. Rebooting the device is optional (restart only if you encounter errors).
thank you for your suggestion! I tried TitaniumBackup but it gives me the same error, then now I'm trying with Link2sd and it works well, BUT the new apk file is in system/app instead of system/priv-app, and its name is "com.google.android.gms-1.apk" instead of "PrebuiltGmsCore.apk"... can this create some problems in future?
EDIT: I tried moving to the priv-app folder and renaming the apk to be identical as before and it seems to work... for now...
It's the package name, it won't create any problems. There is no need to rename the app to match the old one. Default location when converting to system app is in /system/app. I don't know if you can change the location, but you can move it manually to /system/priv-app thru root explorer. Just restart the device afterwards to eliminate FC errors.
Ive made a few changes the the apktool for android. First off it will be installed to they system partition. The apktool data folder will also be in system partition, so don't forget to set it when you start the app. Reason being is the emulated SD doesn't allow executing of files. If you want to use the app to unpack/repack and tweak your boot.img. Make a working directory in the apktool folder and place the boot.img in it then unpack and tweak. You have to options so choose the "common" unpack and repack when it asks.
I wanted to make this a universal system install. So before you flash just mount your system partition because the script will not. Won't hurt nothing it just simply won't install unless system is mounted.
It will work on whatever ROM you're using to save any questions. here's the link flash it and modify some apps right on your phone. Its fully tested and it works great
https://docs.google.com/file/d/0B0xIhMfx77oQVlJVY0J0bHJFRFE/edit?usp=docslist_api
Sent from my One Mini
I tried installing it with both Flashify and Magisk, but both methods failed.
When I tried installing it via the included Xposed Installer, it also failed, but gave me the message:
> Error: Xposed_Framework.jar already exists in /system/framework
I'm guessing a previous installation failed, but left the file there.
My next idea is to delete that file from /system/framework and try again, but since it's in an RO directory I don't have permission.
I tried using a terminal emulator to mount the drive in rw mode, and also tried using a root file explorer, but either both methods don't work, or I just couldn't figure it out.
Anyone have an idea of how to remove or rename that file so I can try to install the .zip ?
-Thanks
Highfiverobot said:
I tried installing it with both Flashify and Magisk, but both methods failed.
When I tried installing it via the included Xposed Installer, it also failed, but gave me the message:
> Error: Xposed_Framework.jar already exists in /system/framework
I'm guessing a previous installation failed, but left the file there.
My next idea is to delete that file from /system/framework and try again, but since it's in an RO directory I don't have permission.
I tried using a terminal emulator to mount the drive in rw mode, and also tried using a root file explorer, but either both methods don't work, or I just couldn't figure it out.
Anyone have an idea of how to remove or rename that file so I can try to install the .zip ?
-Thanks
Click to expand...
Click to collapse
In the Xposed app you should be able to just run the uninstaller script. If that doesn't work, boot TRWP and delete it from there.
D3RP_ said:
In the Xposed app you should be able to just run the uninstaller script. If that doesn't work, boot TRWP and delete it from there.
Click to expand...
Click to collapse
Unfortunately, the uninstaller also fails.
It says it can't remove that file from a read only directory..
Highfiverobot said:
Unfortunately, the uninstaller also fails.
It says it can't remove that file from a read only directory..
Click to expand...
Click to collapse
flash installer or uninstaller through TWRP
wmcdrugs said:
flash installer or uninstaller through TWRP
Click to expand...
Click to collapse
Root Explorer....
This app does wonders, it allows you to modify directories in /system and other root folders. You can even change permissions of specific folders/files from read/write/read-only....etc. I've had this app since the earliest of android days and it has been my go to file explorer. Root Explorer of course requires root....but it completely unlocks your phone and allows you to modify any system file that is set to any permission. Of course there are other file explorers that allow you to modify system files, but this is the one that i have the most experience with. You should be able to access the system folder where the Xposed file remains and modify it so it can fix your problem.
djer34 said:
Root Explorer....
This app does wonders, it allows you to modify directories in /system and other root folders. You can even change permissions of specific folders/files from read/write/read-only....etc. I've had this app since the earliest of android days and it has been my go to file explorer. Root Explorer of course requires root....but it completely unlocks your phone and allows you to modify and system file that is set to any permission. Of course there are other file explorers that allow you to modify system files, but this is the one that i have the most experience with. You should be able to access the system folder where the Xposed file remains and modify it so it can fix your problem.
Click to expand...
Click to collapse
This!. I've used it for years. Not muss no fuss. It's not bloated like a certain couple others I know of. It just does what it does and does it well. Manages files. No extra garbage.Give it a try. I'd be surprised if you can't delete it with Root Explorer. If you do try it, go to the folder you want to delete the file from. Once in there, look at the top right of the screen. Somewhere up there It will say MOUNT R/W. Touch that and you should be able to do whatever you want to within that folder.
Do you have the magisk DNSCrypt module installed? If so, thats why you cant modify anything in /system. Not sure why or how it breaks it, but it does. Took me for ever to figure out what was causing it. Now that i removed the module, i can modify anything i want again.
Sent from my [device_name] using XDA-Developers Legacy app
I'm trying to convert an app to a system app by placing it in /system/system/priv-app. I'm rooted using Magisk, but otherwise running completely stock Pie, with stock recovery installed. Here's what I've tried:
1. Using Magisk's Terminal App Systemizer module. This was the first approach I tried.
2. Using ES File Explorer to move the folder and change permissions.
3. Using Link2SD to make app into a system app.
4. Booting into TWRP using Fastboot, then using TWRP's File Manager to move the app into the /priv-app folder and set permissions.
5. Following the directions here to place the .apk directly into the root of the priv-app folder.
6. Following the directions here to make a folder for the app inside of /priv-app through adb shell and placing the .apk inside that folder.
Each time I've done this, when I try and reboot my phone it hangs during the boot sequence on the G logo with a little loading bar at the bottom. After a little while, the phone will automatically reboot into recovery and prompt me to either do a factory reset or try again (trying again causes a bootloop). I can boot back into the bootloader using the hardware keys and use fastboot to get TWRP running. From there, if I delete the .apk inside the /priv-app folder my phone will boot as normal. Note that I've had to sideload the OTA image when I used Magisk/Link2SD to systemize the app, as I couldn't find the app inside the /priv-app folder at all.
I've tried 2 different APKs with the same result. I make sure to set the proper permissions before rebooting, but it would appear that I'm doing something wrong with the .apk, since the problem goes away as soon as I delete it from the /priv-app folder.
Any help? What am I doing wrong?