Requirements:
a. Titanium Backup
b. File Explorer (with root capability)
Rooted:
1. Install 3rd party keyboard APK to your KF as usual.
2. Using file explorer, navigate to /data/data/com.<keyboard name>/lib
3. Copy libxxxxxx.so file/s to /system/lib
4. Change permission of the *.so files by ticking READ (Owner, Group, All) and WRITE (Owner).
5. Now using Titanium Backup PRO, convert/move <keyboard>.apk to system app.
6. Reboot.
============
If no Titanium Backup:
5.a Using File explorer, navigate and CUT /data/app/<keyboard name>.apk
6.a Go to /system/app and PASTE <keyboard>.apk here and change permission to by ticking READ (Owner, Group, All) and Write (Owner).
7.a Reboot KF.
=============
Extra: I think this can work on Stock (unrooted) device, given you can give
ADB commands such as install, move, chmod.
Sorry to necropost, but I've tried everything, including this, and I can not got Swype to work on my Fire. At all. Anyone have any ideas?
vertcam9 said:
Requirements:
a. Titanium Backup
b. File Explorer (with root capability)
Rooted:
1. Install 3rd party keyboard APK to your KF as usual.
2. Using file explorer, navigate to /data/data/com.<keyboard name>/lib
3. Copy libxxxxxx.so file/s to /system/lib
4. Change permission of the *.so files by ticking READ (Owner, Group, All) and WRITE (Owner).
5. Now using Titanium Backup PRO, convert/move <keyboard>.apk to system app.
6. Reboot.
============
If no Titanium Backup:
5.a Using File explorer, navigate and CUT /data/app/<keyboard name>.apk
6.a Go to /system/app and PASTE <keyboard>.apk here and change permission to by ticking READ (Owner, Group, All) and Write (Owner).
7.a Reboot KF.
=============
Extra: I think this can work on Stock (unrooted) device, given you can give
ADB commands such as install, move, chmod.
Click to expand...
Click to collapse
Thank you very much! I now have swiftkey goodness on my 1st gen Fire!
Related
I've read about this here a bit but it's not really well documented or tutorialized.
So, how can someone change stock launcher to whatever launcher he/she wants ?
I know this is done via adb console, this is not the issue. But dunno what needs to be taken out and replaced; if something needs to be renamed or not. Where can the apk files be found for newly installed software ? and also what needs to be removed from the stock launcher ? odex & apk ? I know where to find the apk, but not the odex. and are any more files "bound" to the stock launcher except the apk and the odex file ? If say i use a filemanager to locate my desired launcher (having said launcher installed), will pushing it into the /system/app folder do the trick or do I have to rename it ? That means that basically the system/app folder is like a folder for apps that are launched automatically when phone starts.
Can someone help me & shed some light on this ? Thanks !
as few ways to do this. isntall launcherpro (or what launcher you want).
use root explorer to move com.fede.launcher.apk from /data/app to /system/app
change the name to launcherpro.apk
change the permissions to read for user, group and others. write for user only.
reboot
once you select launcherpro, use root explorer, go to /system/app, and delete launcher.apk or home.apk or whatever your rom uses as stock home/launcher.
or, use adb
Code:
abd push launcherpro.apk /system/app
Thanks man, though I have some questions:
Q1: how do I do
change the permissions to read for user, group and others. write for user only.
Click to expand...
Click to collapse
Q2:
once you select launcherpro, use root explorer, go to /system/app, and delete launcher.apk or home.apk or whatever your rom uses as stock home/launcher.
Click to expand...
Click to collapse
Don't I have to rename launcherpro.apk to home.apk in order for it to work @ startup time ?
Instead of deleting home.apk, perhaps moving them to the sdcard might be better (just in case).
ldq said:
Thanks man, though I have some questions:
Q1: how do I do
Q2: Don't I have to rename launcherpro.apk to home.apk in order for it to work @ startup time ?
Instead of deleting home.apk, perhaps moving them to the sdcard might be better (just in case).
Click to expand...
Click to collapse
you can use root explorer to change permissions. just long press the apk and a submenu will pop up with permissions being an option.
whether or not you need to change the name of launcherpro will depend on your rom/device. you can leave launcherpro as is and leave home.apk in there, reboot. when it boots, it should have a popup asking which you'd like to use as the launcher.
or, install launcherpro like normal, select it to be the default launcher and it should always launch at boot.
thanks a lot ! will try this out !
How to change stock launcher with any launcher
Victory !
Step by step:
1. Backup original launcher
Code:
adb pull /system/app/Launcher.apk Launcher.apk.bak
2. Backup installed launcherpro/adw/golauncher apk's to either HDD or SDcard
2a. Use root explorer mount r/w to copy corresponding file to SDcard & after that
rename the file to Launcher.apk or whatever your stock launcher is. ( user installed apps can be found in /data/app)
2b. Pull file to HDD
Code:
adb pull /data/app/Launcher.apk Launcher.apk
3. Push file to /system/app
Code:
adb push Launcher.apk /data/app/Launcher.apk
4. Reboot & Enjoy
I flashed Cyangenmod 7.1 RC, flashed Frank's Mod to remove all CM7 apps, flashed dark launcher theme.
I copied DSPManager.apk to SDcard prior to flashing Frank's Mod. But it says it can't be installed.
Is there a way to install DSPManager again?
Thanks!
You have to install it back to system/app folder and set permissions if using root explorer or adb push it back. Just hitting install will not do it.
jerrycycle said:
You have to install it back to system/app folder and set permissions if using root explorer or adb push it back. Just hitting install will not do it.
Click to expand...
Click to collapse
Thanks for the reply.
But how do I do that?
I moved the apk file to system/app, changed Permission (selected RWX for owners) but it still won't install.
It won't let me change permissions at all inside sdcard.
Instructions for installing apk with root explorer:
1. navigate to file and copy apk
2. navigate to system/app
3. tap on r/w at the top
4. paste all apk
5. change permissions to match the other apks's in the system/app directory.
6. Reboot
This fixed it for me, and was a better option than re-flashing. I would put this up in the dev forum, but I don't have enough posts.
1. Use Titanium Backup to uninstall "[PLAYLIST] Media Storage 3.1-124251"
2. Grab "MediaProvider.apk" from the Tiamat Rom 1.1 zip file (/system/app)
3. Use adb to issue the following commands:
adb remount
adb push MediaProvider.apk /system/app
4. Use ES File Explorer and navigate to the /system/app folder. Click on MediaProvider.apk and re-install the package
5. Reboot your xoom.
Thanks to nakasun for finding the app causing the issue. I believe the issue is caused when you restore MediaProvider from Tiamat 1.0 using titanium backup.
Works great. Just a nit, but now I don't have any duplicate folders but I do have a dozen "Local Disk" icons at the bottom of Windows Explorer. They all display as having 0 bytes.
Thanks for posting this
The easiest way, at least for me, to get an app into /system/app is to use Root Explorer to copy the apk into /system/app.
To do this:
In Root Explorer, copy the apk file you want to put in /system/app
Navigate to the /system/app directory
Tap the Mount R/W button on the top right
Tap Paste
Scroll down to the pasted apk, long press on it and select Permissions (you'll see 9 check boxes when you do this)
Check the Read and Write buttons for User, and only the Read boxes next to Group and Others, then tap OK (once you're done, the read/write permissions under the app name should be the same as all the other apps listed (rw-r--r--))
Reboot.
If anybody want any system app,i have backup of all the stock rom apps...let me know if somebody want...
This is the first release of TiB that has not been able to locate my TitaniumBackup_license.txt file. I am using a Nexus 6 on MRA58K (M) with SuperSU 2.52 and TiB 7.2.4. Stock with the exception of a modified stock kernel. (http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958)
Here is what I did to get it working:
If you have a proper key file named "TitaniumBackup_license.txt" try this:
1. Copy TitaniumBackup_license.txt to root of your device (/) using ES File Explorer with root permissions enabled.
2. After you copy the file to the root of your phone (NOT SDCARD root!), from the root directory of your phone, hit home button while in ES File Explorer. This basically leaves ES File Explorer running and in the proper place for this trick to work.
3. Go to Chrome browser and download any random image, use save! Long press an image and do save image. Hit home button.
4. Go to notification shade and open the now downloaded image with ES File Explorer ONCE (do not set as default). This step assumes you do NOT have a default image viewer. If you DO have a default image viewer it needs to be ES File Explorer OR nothing. Ex. If Google Photos opens, then you need to clear defaults for Google Photos.
5. Once image is loaded in ES File Explorer, hit back button and it should put you at root of ES File Explorer. This is the exact same place you left ES File Explorer in step 2.
6. Navigate to /storage/emulated/legacy this directory should be strangely empty. It will not be your typical SDCARD contents. You might only see titanium backup folder that is empty or some other random folder. THIS odd empty directory is where TB looks for the key file!
7. Navigate back to / and copy TitaniumBackup_license.txt to /storage/emulated/legacy
8. Restart Titanium and it should be good to go for registered key!
9. DELETE the TitaniumBackup_license.txt file from / as it or any other random file should NOT be here in your system ROM.
As a senior member, you should know your way around the site.
XDA Assist is here to help navigate the site, not for questions or information. Please post this in an appropriate area. Assist is not that. :good:
Thread closed.