HELP ME...
I have a Samsung Galaxy S2, running Gingerbread XWKDD, Android 2.3.3, Samsung's Touchwiz 4.0.
Rooted my SGS2 and got Titanium Backup, I uninstalled the clock app because I thought it was a widget and I didn't want to see alot of widget. Anyway, turns out the clock 1.0 is actually a system app by the name of com.sec.android.app.clockpackage
and titanium backup can't reinstall it, when i extract the .apk from the backup file and try manually installing, it doesn't install either, just says application not installed.
I also can't find this on Android market.
ok, so after some digging i found that com.sec.android.app.clockpackage.apk still existed in system/apps but just wasn't running. I also noticed for almost every .apk, there was a .odex. But for my clockpackage, there was no .odex, maybe that's why it's not working?
on that thought, maybe anyone here can copy their .odex files for the 2 clock .apks and send them to me? Just use Root Explorer to see the system/app folder, mount R/W if you need to, then copy the 2 .odex files and then upload them somewhere? Pls?!?
if you want root explorer, holla at me via pm
Hi,
I have the same problem with Contacts.apk (no .odex, Titanium or. RootExplorer can't install), so i can't open the number-pad to make a call.
I have tried to copy the backuped Contacts.apk manualy to /system/app, the rebooted, but it don't hlep.
Solved: I have Installed the VillainROM 1.0 and the app is back.
U tried reflashing your current rom??
Its the most clean solution... Because if you copy and paste from another device i'm sure about the system file its not going to work correctly(cache data from another device...mmm i think it will not work...)
sent from my amstrad CPC powered by LOL..(premium xda)
Is it possible to save an app that i downloaded from the market to use at a later date?
Basically I downloaded and use MyBackup Root as my backing up app for my phone which is free from the market and i would like to have that apk on my phone so i can install after i flash a new rom rather than going into the market to have to do it all the time.
Create an update zip that you can flash from recovery, there should be "how-to's"
hanging around.
If not post up your apk and me or someone else will create one for you.
Hope this helps
I always use Titanium Backup to restore apps when I flash new roms. Works flawlessly.
If you have root you can copy the .apk to external memory. If your new rom comes with any kind of file explorer, you just open it and it will install.
-----
N1; CM7.0.nightlies
I'm an Internet person, and pretty much a Linux guy as well but I don't have a lot of experience with Android yet.
Question: I have a rooted (thanks Jcase and team) HTC DNA phone. I want to know if I can just "delete an APK" to remove something that came with the phone.
Example: The carrier installed a game that keeps updating itself called Reign of Amira. CAN I just delete the .apk somewhere? Or are there implications?
Please advise. Thanks.
-Joe
Try futz.me - A Command line for the web.
You can. If it is a system app, you should be able to find it under /system/app, if not you can find it under /data/app. Before deleting, you can make a backup or instead of removing it you can rename file extension from .apk to .bak, for example. By doing the rename you are disabling the application because Android will only look for the .apk.
That is for a file that you know what it is. If you will be messing around with other files you don't know, then I highly advise to make a nandroid backup first.
Seems to work. Thanks for the confirmation.
-Joe
futz.me - Try Futz.me, A Command Line for the Web
bgcngm said:
You can. If it is a system app, you should be able to find it under /system/app, if not you can find it under /data/app. Before deleting, you can make a backup or instead of removing it you can rename file extension from .apk to .bak, for example. By doing the rename you are disabling the application because Android will only look for the .apk.
That is for a file that you know what it is. If you will be messing around with other files you don't know, then I highly advise to make a nandroid backup first.
Click to expand...
Click to collapse
Wait, there is a problem:
Anything in \system\app that I rename to .bak, will rename itself BACK when I reboot.
Also, My Google Play store "My apps" section went blank (white screen) for two reboots.
Do I need the s-off for the phone which hasn't been done yet?
bgcngm said:
You can. If it is a system app, you should be able to find it under /system/app, if not you can find it under /data/app. Before deleting, you can make a backup or instead of removing it you can rename file extension from .apk to .bak, for example. By doing the rename you are disabling the application because Android will only look for the .apk.
That is for a file that you know what it is. If you will be messing around with other files you don't know, then I highly advise to make a nandroid backup first.
Click to expand...
Click to collapse
You can try Titanium Backup for freezing, disabling and deleting apps
avkiev said:
You can try Titanium Backup for freezing, disabling and deleting apps
Click to expand...
Click to collapse
I appreciate your help, but is this a definitive method? If deleting the apk doesn't work, then can I use the "force remove" option in Titanium Backup? Or Could that hurt something? I'm just talking about removing obvious crap here like that game I mentioned, some NFL game, a few stupid verizon services, etc.
Live by this motto: "When in doubt, freeze it out". Use an application to freeze any applications you feel you don't need or want. It's best that way, and will help you avoid any problems by deleting an app and subsequently running into problems later on down the line...
ΧΔΑ Fraternity's Godfather. Read About Our History!
Freeze it. Don't delete. It might need to be restored in order to take an OTA system upgrade.
If I may:
1.) Is there some sort of app or file that calls these apps I'm going to freeze? Meaning, Can I just "freeze" (which I assume means disable) the app, and not have to worry about telling whatever file calls it to not call it?
2.) Do I need to buy that Titanium (free version doesn't freeze) or is there something else you use?
3.) Does freeze simply mean rename to .bak? Because if that's the case, I've already tried that with Root Explorer and the files rename themselves BACK to .apk upon reboot.
Thanks.
85gallon said:
Freeze it. Don't delete. It might need to be restored in order to take an OTA system upgrade.
Click to expand...
Click to collapse
commandlinekid said:
If I may:
1.) Is there some sort of app or file that calls these apps I'm going to freeze? Meaning, Can I just "freeze" (which I assume means disable) the app, and not have to worry about telling whatever file calls it to not call it?
2.) Do I need to buy that Titanium (free version doesn't freeze) or is there something else you use?
3.) Does freeze simply mean rename to .bak? Because if that's the case, I've already tried that with Root Explorer and the files rename themselves BACK to .apk upon reboot.
Thanks.
Click to expand...
Click to collapse
1) If you freeze an app using another app designed to do just that, there will be no way the app can be launched by another file or program (I believe that's what you're asking here)
2) Boat Freezer is good or Root Uninstaller is free (also good)
3) Bloat Freezer will rename the app with a .bzw file extension, and others work similarly. However, you cannot simply rename apps yourself and expect not to cause problems. This is where a good app freezer comes into play.
Also, whenever you make a change using the Root Explorer, the modified file will have a .bak extension. If you want your modified file to stick passed boot, you must delete or move the .bak file created after the editing.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Ok, I'll try that. Thanks.
Joe
Apex_Strider said:
1) If you freeze an app using another app designed to do just that, there will be no way the app can be launched by another file or program (I believe that's what you're asking here)
2) Boat Freezer is good or Root Uninstaller is free (also good)
3) Bloat Freezer will rename the app with a .bzw file extension, and others work similarly. However, you cannot simply rename apps yourself and expect not to cause problems. This is where a good app freezer comes into play.
Also, whenever you make a change using the Root Explorer, the modified file will have a .bak extension. If you want your modified file to stick passed boot, you must delete or move the .bak file created after the editing.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Click to expand...
Click to collapse
i recommend using BloatFreezer ...
it freezes(or stops) unncessary system apps..or any other app you want...
and the advantage is that you can defrost it to get it back..!
neelay92 said:
i recommend using BloatFreezer ...
it freezes(or stops) unncessary system apps..or any other app you want...
and the advantage is that you can defrost it to get it back..!
Click to expand...
Click to collapse
This is true for any app freezer, in that you can freeze/un-freeze apps as you please. Even better: running a custom ROM that's already been de-bloated and using an app freezer for any other apps you don't want running.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Can I just do this:
1.) adb shell
2.) Yay, I'm in Linux. I can now do stuff.
3.) Move the .apk files from \system\app to \sdcard\backup
4.) That's it.
Then if I need to move them back, I can.
Instead of all this "freezing", relying on a third-party app, etc.
Am I missing something here?
Please advise. Thanks.
Apex_Strider said:
1) If you freeze an app using another app designed to do just that, there will be no way the app can be launched by another file or program (I believe that's what you're asking here)
2) Boat Freezer is good or Root Uninstaller is free (also good)
3) Bloat Freezer will rename the app with a .bzw file extension, and others work similarly. However, you cannot simply rename apps yourself and expect not to cause problems. This is where a good app freezer comes into play.
Also, whenever you make a change using the Root Explorer, the modified file will have a .bak extension. If you want your modified file to stick passed boot, you must delete or move the .bak file created after the editing.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Click to expand...
Click to collapse
Question,
Can I just do "adb shell", then once I'm in Linux, I can just move the .apk files I want to stop over to another directory...so I have them?
Is "freezing" even a real thing?
Please advise, if you don't mind, whether or not the above method is as good as freezing. Then, I won't have to rely on a third-party app (regardless of how much people love these apps) to accomplish the task.
Thanks.
Apex_Strider said:
1) If you freeze an app using another app designed to do just that, there will be no way the app can be launched by another file or program (I believe that's what you're asking here)
2) Boat Freezer is good or Root Uninstaller is free (also good)
3) Bloat Freezer will rename the app with a .bzw file extension, and others work similarly. However, you cannot simply rename apps yourself and expect not to cause problems. This is where a good app freezer comes into play.
Also, whenever you make a change using the Root Explorer, the modified file will have a .bak extension. If you want your modified file to stick passed boot, you must delete or move the .bak file created after the editing.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Click to expand...
Click to collapse
commandlinekid said:
Question,
Can I just do "adb shell", then once I'm in Linux, I can just move the .apk files I want to stop over to another directory...so I have them?
Is "freezing" even a real thing?
Please advise, if you don't mind, whether or not the above method is as good as freezing. Then, I won't have to rely on a third-party app (regardless of how much people love these apps) to accomplish the task.
Thanks.
Click to expand...
Click to collapse
Yeah, but why go through all that trouble? The beauty of the app freezer is that it does what you want, right from your phone. No computer needed. If you use adb, you'll have to adb push them back to the right folder/directory of you want them again. Then, you'll have to set permissions, and is just more work. What if your computer crashed, how would you adb the apps of you ever needed them? The app freezer is all you need, right from your phone, no hassle, no worries! Trust me, that's the easiest way to go about this
ΧΔΑ Fraternity's Godfather. Read About Our History!
To the Admins, I'm not entirely sure where you guys would want this thread...troubleshooting seemed to be the most sensible.
all right everyone, I'll explain here how I fixed this, but keep in mind I have the ATT LG G2 running KitKat with TWRP 2.7.0.0 and I'm rooted. I only recommend this for advanced users. If you aren't an advanced user, well, make sure you have a backup. I'm sure there was a faster way to fix this, but my goal wasn't to find the fastest way initially, it was to find a working way. For example, you could just ADB everything. You could also, assuming you know how to use your OS to search that deep into the device files, done a rename, copy/paste etc. etc. Not all devices are made equal, so be CAREFUL! BTW, I was in debugging mode + charge only.
WARNING: I AM ONLY OFFERING THIS FOR INSIGHT TO ADVANCED USERS THAT KNOW WHAT THEY ARE DOING - I DON'T OFFICIALLY RECOMMEND THAT ANYONE DO THIS. I AM NOT RESPONSIBLE FOR ANY TRANSMUTATION FROM LG G2 TO BRICK.
Here's what I did:
1) I opened accessibility while hooked up to the debugger in Android Studio to see that it was producing a Null Pointer Exception.
2) I have a slightly modified version of the TOT file so that I can run TWRP and still be rooted in KitKat.
3) I am rooted, so I used Root Explorer to search for accessibility and found that the file is called "LGSettingsAccessibility.apk" and .odex - it's under (WITH ROOT ONLY) /system/priv-app/
4) I searched for a system dump copy online...I found this site: http://hunterspad.com/Domains/StorageCow/Xda/Users/garyd9/Extracted System/priv-app/
I found that by typing "LGSettingsAccessibility.apk" and initially found a Google Drive version but it was posted in September of 2013 - unlikely to be the odex and apk from KitKat hahaha. I used a Google Search that searched custom range between Feb 1st and today. I found 2 links, one of which is the above.
NOTE: I don't recommend anyone do the following unless you KNOW what you are doing and definitely have a backup to restore to if things go wrong
5) I sent the link for each file to myself on Google Hangouts. I used Hangouts to download the March 14th upload of the LGAccessibilitySettings.apk and LGAcessibility.odex
5.5) I copied each of the original files (.apk and .odex) from /system/priv-app/ to my /sdcard/LGBackup folder I created using the Root Explorer app.
6) I went into the app "Root Explorer" again after downloading both files (DID NOT INSTALL IT, though it probably won't let you anyway). I checked both files and copied them.
7) I went back to /system/priv-app/ and renamed the existing files to be replaced with the extension ".bak" so that the system no longer points to those files (NOTE: Root Explorer asked me to remount as R/W (read and write vs. read-only) a good feature of root explorer to be in read-only by default; dangerous territory.
8) Bottom right corner of Root Explorer it was waiting for me to "Copy Here" when arriving at the location where I wanted to copy the files: /system/priv-app/ and after copying them I decided to be a fool and install the apk and it told me something like "app not found" or something.
9) FINALLY went into Settings and touched Accessibility and VOILA! It worked! A lot of luck involved - the odexed and apk files may not have been the proper version. I could have checked with relative ease (though likely time-consuming) by using some of my android dev skills/utilities.
WARNING: I AM ONLY RECOMMENDING THIS FOR ADVANCED USERS THAT KNOW WHAT THEY ARE DOING.
Thanks to garyd9 on XDA - without your uploaded files on storage cow, I couldn't have fixed this problem!