[GUIDE] Merging updated system apps with old one, GET MORE FREE MEMORY!! - Android Software/Hacking General [Developers Only]

(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.

Related

[Q] pushing app to system

so it seems its a system limitation when using dialer apps where the missed call notification doesn't get cleared when opening the dialer app.. the stock phone app needs to be opened in order to clear it...
i'm running cm7.1 on nexus s 4g.. just installed touchpal dialer.. i read on this site
http://stackoverflow.com/questions/2007024/push-my-apk-to-system-app
that you could push the app into the system folder and that would address the problem.. i downloaded the app from the market so no idea how to get the apk..
i assume if i could get a hold of the apk.. i could use root explorer to change the persmissions, then move the file into system/app and then install the app??
any help would be appreciated.
p.s. all i really want is the search feature of these apps which stock dialer doesn't have.. which is a big oversight by google not to have this.. so if any other solutions are available.. great.. love to hear them
The apk should be somewhere in /data/app, there are also apps that let you backup apk files to sdcard.
Afterwards remount /system to read+write and push the apk file to /system/app.
do i need to uninstall the app from /data/app after? or should i leave that file in there
Using Root Explorer, find the apk in /data/app, long-press and select move. Navigate to /system/app, mount r/w (by pressing the button at the top), and paste. Long-press the apk again, select permissions and set to rw-r--r--, then mount r/o and reboot.
Voila! Your user app is now a system app. You can also use Titanium Backup to convert a user app to system app and vice versa. As I have the paid version I'm not sure if this feature is available in the free version.
Sent from my Evo + MIUI using Tapatalk!
thanks.. seems to work now.. i'm surprised apps can't automatically install in that way to notifications can be dealt with.. guess they don't have permissions to install into system?..appreciate the help.. all works now!!
so seems doesn't like to work like that.. every time i reboot i get a force close popup... then i have to delete the app and restart.. had permissions set correctly and everything

[Tutorial] Install problematic APKs in /system (or /preload)

You may have tried to move some APKs to /system/app/ and end up with continuous crashes, usually resulting in abandoning your plan to save some otherwise wasted space (or preventing to accidentally uninstall all keyboards...)
This is often said to be a permissions issue, yet that's not enough for some packages: those with external libraries.
Copy the APK to /system/app/, then `chmod 644` it as usual.
You can also install to /preload and symlink to system
On your computer (easier but not required), open the APK (as a renamed ZIP).
Go to ./lib/{architecture}/, where on the Ace2 this is lib/armeabi-v7a.
Extract all the (.so) files here and put them in /system/lib.
There's no step 5!
Ryccardo said:
You may have tried to move some APKs to /system/app/ and end up with continuous crashes, usually resulting in abandoning your plan to save some otherwise wasted space (or preventing to accidentally uninstall all keyboards...)
This is often said to be a permissions issue, yet that's not enough for some packages: those with external libraries.
Copy the APK to /system/app/, then `chmod 644` it as usual.
You can also install to /preload and symlink to system
On your computer (easier but not required), open the APK (as a renamed ZIP).
Go to ./lib/{architecture}/, where on the Ace2 this is lib/armeabi-v7a.
Extract all the (.so) files here and put them in /system/lib.
There's no step 5!
Click to expand...
Click to collapse
Thank you very much :good:
All of the above is still true if you want to package apps in CWM format, but people who just are tight on /data (and don't want to repartition) can just use the convert to system app in Link2SD, which now actually works on apps with libraries

[Q] Put app in system

Can anybody tell me how to install apk from phone as system app
first move apk from /data/app to system/app
then move library files to /system/lib
what next???
I need full guide
Then reboot. If the app doesn't appear in your app drawer, go back to /system/app and install the apk like usual from that folder. Reboot again and see if it works.

PlayStore or Market Force Close(FC) Fix!!

Hi there,
If anyone still encountering FC/not dowloading apps for Playstore or market, it might also be the cause of new partition or something like that, you can try this another option freely other than fixing permission of vending.apk on /system/app/..
This might help you guys on a Custom ROM or not? .
1. check if cache folder has "download" folder inside it, if it no download folder then create one inside /cache, e.g. mkdir /cache/download.
2. then chmod the /cache folder to 777, also make sure the com.android.vending folder is present inside /data/data/ folder.
3. You can achive it through shell terminal.
Hope this helps you guys fix the FC(Force close or not downloading apps on playstore or market).
Thanks
~imon

Oxygen OS 11-, Systemizing with twrp.

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.

Categories

Resources