Hi
I accidently removed dialer 2.2.2 from the device using Titanium Backup, and i need to restore it in order for my phone calls to work.
I tried downloading some froyo Phone.apk but i cant install. It stops fast and syas "Application not installed" when i click it.
I put it in /system/app/ using adb. I didnt work either to install it through adb. It said cannot find file.
I need a original copy of Phone.apk and maybe some explanation of how to install it as it were before i removed it.
http://forum.xda-developers.com/showthread.php?t=960374 has a complete dump of 2X global version. You can find the dialer in there.
There are several threads about the joys of reinstalling system apps (usually ppl killed the launcher) among them are http://forum.xda-developers.com/showthread.php?t=992945
EDIT: next time freez in stead of uninstalling... frozen apps will be restored by a simple factory reset. uninstalled won't.
Thx I am downloading and hoping it will work with the original Phone.apk
vivet said:
Thx I am downloading and hoping it will work with the original Phone.apk
Click to expand...
Click to collapse
it should work.
I downloaded the package and pushed the Phone.lnk to the /system/app/ directory. After that i went to a file browser on the phone and tried to execute the Phone.apk file.
It came with the same message. Do i need to install through adb or hard reset?
vivet said:
I downloaded the package and pushed the Phone.lnk to the /system/app/ directory. After that i went to a file browser on the phone and tried to execute the Phone.apk file.
It came with the same message. Do i need to install through adb or hard reset?
Click to expand...
Click to collapse
You don't need to install apk when putting in /system/app.
Copy apk to sd, download and install rootexplorer copy apk forom sd with rootexplorer go to system/app push button “mount R/W“ paste apk and reboot the phone. Done
Well isnt that the same as using adb.
I have the Phone.apk from the optimus 2x dump in the /system/app/ folder now, but i doesnt fix the problem. It doesnt seem to get installed when rebooting.
How can i see if its installed. I checked Titanium Backup, which still shows the Dialer 2.2.2 grey with strike-through (Data backed up, with no possiblity of restore).
How do i force it to "reinstall" upon reboot.
I tried restoring a widget that i removed, and that worked, so maybe the phone.apk is installed after i pushed it to /system/app, but something else is wrong.
What could be the problem? Missing data or something, which i need to restore somehow?
Isn't there a way to reflash the device with original rom?
Any ideas?
I downloaded the Global System.zip from this forum. I successfully went to the android recovery menu on the phone. I can choose to update the phone using System.zip on sdcard.
Is that the way to go?
have solved the problem?
Is possible to edit the phone.apk? the stock "incall" app is simple orrrrrrible
i too am missing my dialer app. whenever i touched the phone icon it would crash and go to home screen i thought if i uninstalled it and reinstalled it with titanium pro it would fix it. but it now wolnt let me reinstall. ive been searching the forum and trying different ways to fix the issue but nothing is working so far ... how can i get this is work?
Phone.apk
Did you guys figure this out? I installed
I accidently deleted my Phone.apk on my Captivate. I tried using the stock Phone.apk from the SDK but that does not work.
Version 2.2
Build FROYO.UCKB1
If anyone can provide or link that would be awesome.
Download cognition, pull phone from rom package. Use root explorer or abd to drop in system/app. Reboot. Should do it
mcord11758 said:
Download cognition, pull phone from rom package. Use root explorer or abd to drop in system/app. Reboot. Should do it
Click to expand...
Click to collapse
Yea!!! About phone has a Baseband again!!!!! Thanks, didn't even think doing it that way
!
Deleted Phone.apk from my Dell streak
I had done the same thing, deleted phone.apk, settings.apk, and contact.apk.
I found a new update on the internet that has ICS look and feel so I deleted the apks my self trying to copy the new ones. That was it. the phone did not stop crashing FC and I could not do anything no matter what I do. Finally I had to do a full factory reset and everything was fine.
Hi,
My ROM came without the email apk/s and I was wondering if anyone had them from stock .254
I have the gmail apk, I need the stock email one for other email services like hotmail
Cheers
EDIT: please read through the rest of the thread, the issue has progressed but not been solved.
Zorigo said:
Hi,
My rom came without the email apk/s and I was wondering if anyone had them from stock .254.
I think the two APKs I need are exchange.apk and SEMCemail.apk. I have the second and was wondering if someone could provide me with exchange.apk from .254?
Click to expand...
Click to collapse
(Odexed )See below:
mrjraider said:
(Odexed )See below:
Click to expand...
Click to collapse
You lad!
Cheers!
mrjraider said:
(Odexed )See below:
Click to expand...
Click to collapse
When I go to install the apk like a normal apk, by opening the apk in my file explorer and installing, it goes through the install screens, but then finishes by saying "Application not installed"
Unknown sources is checked and I have side loaded apks like this before successfully, what's the problem?
OOhhh, maybe it's because that's an odexed file. My rom is deodexed.
ignore, double post
Zorigo said:
When I go to install the apk like a normal apk, by opening the apk in my file explorer and installing, it goes through the install screens, but then finishes by saying "Application not installed"
Unknown sources is checked and I have side loaded apks like this before successfully, what's the problem?
Click to expand...
Click to collapse
System apps are not installed like normal apps. You need to root your device, put it in system/app and permissions rw-r-r- reboot to see it
(I'm already rooted)
Well here's something weird. I copied the files, went to system/app and it turns out the files are ALREADY there!
I check out the permissions and they're both correct. So I rebooted and it still won't show up. I opened Titanium Backup and looked through the apps list again there, there's no sign of it being on the system.
The files are there but apparently they're not!
Strange, move those file to data/app rw-r-r- and reboot and see what happens
mrjraider said:
Strange, move those file to data/app rw-r-r- and reboot and see what happens
Click to expand...
Click to collapse
Just did that, and still nothing!
bump (if that's allowed, I can't remember)
I'm trying to fix the "daemon started successfully" problem, but I don't think I'm uninstalling and re-installing the driver correctly, I just uninstall the device from device manager, then plug the phone back in and let it install.
That must be wrong because it's not working. The program I'm trying to use is xUltiamte2.4 to deodex my phone.
Astralogic said:
I'm trying to fix the "daemon started successfully" problem, but I don't think I'm uninstalling and re-installing the driver correctly, I just uninstall the device from device manager, then plug the phone back in and let it install.
That must be wrong because it's not working. The program I'm trying to use is xUltiamte2.4 to deodex my phone.
Click to expand...
Click to collapse
If anyone has had this problem and fixed can you please tell me how you did it?
Astralogic said:
I'm trying to fix the "daemon started successfully" problem, but I don't think I'm uninstalling and re-installing the driver correctly, I just uninstall the device from device manager, then plug the phone back in and let it install.
Click to expand...
Click to collapse
Why is that a problem? You want the "daemon" to start successfully, ADB won't work if it doesn't... If it stays stuck on that, maybe you have some program interfering/using ADB. Maybe you have some other ADB program open (flashtool) or maybe you use Bluestacks; check your running processes for a running "adb.exe" process and kill it, then try again.
Removing the drivers should should work as you're doing it already, but before connecting your phone, you should reinstall the drivers first. Or, once it's installed, manually update the drivers through the Windows "Device Manager", by locating the "sa0105adb.inf" file manually.
It can be extracted from the drivers installer (the one that comes with Flashtool) with 7zip, or you might find it still in your temp folder.
Antiga Prime said:
Why is that a problem? You want the "daemon" to start successfully, ADB won't work if it doesn't... If it stays stuck on that, maybe you have some program interfering/using ADB. Maybe you have some other ADB program open (flashtool) or maybe you use Bluestacks; check your running processes for a running "adb.exe" process and kill it, then try again.
Removing the drivers should should work as you're doing it already, but before connecting your phone, you should reinstall the drivers first. Or, once it's installed, manually update the drivers through the Windows "Device Manager", by locating the "sa0105adb.inf" file manually.
It can be extracted from the drivers installer (the one that comes with Flashtool) with 7zip, or you might find it still in your temp folder.
Click to expand...
Click to collapse
Nothing works, isn't there a better way of deodexing then using this stupid program?
Edit: I have a better question. The only reason I want to deodex is so that I can debloat using this guide, that thread already gives me the list of bloatware, isn't there a way I can just go in and manually delete the bloat? Without have to worry about deodexing in order to get the debloat script to run?
Astralogic said:
Nothing works, isn't there a better way of deodexing then using this stupid program?
Edit: I have a better question. The only reason I want to deodex is so that I can debloat using this guide, that thread already gives me the list of bloatware, isn't there a way I can just go in and manually delete the bloat? Without have to worry about deodexing in order to get the debloat script to run?
Click to expand...
Click to collapse
Actually you can also debloat your rom while its odexed. At least as long as the framework is not changed.
Just do a backup, then get a root file manager and delete the safe to remove apps and their odex files. Reboot afterwards.
The only reason why the debloat script doesn't support odexed roms ia that the odex files are not deleted during the script. (However, it would be easily possible to add these lines)
WhiteNeo said:
Actually you can also debloat your rom while its odexed. At least as long as the framework is not changed.
Just do a backup, then get a root file manager and delete the safe to remove apps and their odex files. Reboot afterwards.
The only reason why the debloat script doesn't support odexed roms ia that the odex files are not deleted during the script. (However, it would be easily possible to add these lines)
Click to expand...
Click to collapse
Could you tell me what folder those files are in that I should delete?
Astralogic said:
Could you tell me what folder those files are in that I should delete?
Click to expand...
Click to collapse
Well, if you were following that guide you would have seen that practically everything it's deleting is in /system/app:
delete("/system/app/FBCalendarSync.apk"
Click to expand...
Click to collapse
The odex files are in the same folder, and have the same name aside from the .odex extension.
Then again, that program sometimes has issues; you could always copy the files from /system/app and /system/framework manually without using ADB to the corresponding folders, after starting the program open the Windows Task Manager and kill of the "adb.exe", and the program will continue running and let you deodex the files. Then you'd just have to figure out how to copy them back which is not hard.
Or you could also try a different deodexing program such as Universal Deodexer V4. I've never used any of those since I've deodexed my ROM with dsixda's Rom Kitchen, for which you'd just need to follow the instructions and then copy the resulting files manually (as you'd have to do in the above mentioned example anyway).
Antiga Prime said:
Well, if you were following that guide you would have seen that practically everything it's deleting is in /system/app:
The odex files are in the same folder, and have the same name aside from the .odex extension.
Then again, that program sometimes has issues; you could always copy the files from /system/app and /system/framework manually without using ADB to the corresponding folders, after starting the program open the Windows Task Manager and kill of the "adb.exe", and the program will continue running and let you deodex the files. Then you'd just have to figure out how to copy them back which is not hard.
Or you could also try a different deodexing program such as Universal Deodexer V4. I've never used any of those since I've deodexed my ROM with dsixda's Rom Kitchen, for which you'd just need to follow the instructions and then copy the resulting files manually (as you'd have to do in the above mentioned example anyway).
Click to expand...
Click to collapse
I don't mean I want to manually deodex, I mean I want to manually debloat, deleting the appropriate APK and ODEX file from /system/app seems easy enough, but what would I delete (if anything) from the /system/framework folder?
Astralogic said:
I don't mean I want to manually deodex, I mean I want to manually debloat, deleting the appropriate APK and ODEX file from /system/app seems easy enough, but what would I delete (if anything) from the /system/framework folder?
Click to expand...
Click to collapse
I know, I'm just giving you a solution since that program you're using has always given me issues, and even now, knowing that ADB works, it still get's stuck on that "starting ADB daemon" message.
I'm not trying to be rude, but if you're following the guide you'd have noticed that nothing gets deleted from the framework folder. All it tells you are which apps are safe to remove; whichever apps you do end up removing are up to you. I think the Google Talk app is garbage, but someone else might use it, so debloating is also subjective.
Also, you could just as easily do this with Titanium Backup and actually just freeze the app first in case you're not sure about deleting it.
Astralogic said:
I don't mean I want to manually deodex, I mean I want to manually debloat, deleting the appropriate APK and ODEX file from /system/app seems easy enough, but what would I delete (if anything) from the /system/framework folder?
Click to expand...
Click to collapse
I know, manually deodexing that way would cause a bootloop because of missing classes.dex files in every system app.
Some people that dont like the preinstalled Sony apps prefer getting rid of all the bloat and remove SemcGenericUXPRes.apk from framework folder.. And some (or most) of the framework jar files beginning with "com.sony..."
This will of course bring noticeable smoothness increases, but is very likely to cause bugs when not done by experienced users.
And it could cause a bootloop on odexed builds as the odex files in system/app do no longer fit to the framework.
Just for information.
WhiteNeo said:
I know, manually deodexing that way would cause a bootloop because of missing classes.dex files in every system app.
Some people that dont like the preinstalled Sony apps prefer getting rid of all the bloat and remove SemcGenericUXPRes.apk from framework folder.. And some (or most) of the framework jar files beginning with "com.sony..."
This will of course bring noticeable smoothness increases, but is very likely to cause bugs when not done by experienced users.
And it could cause a bootloop on odexed builds as the odex files in system/app do no longer fit to the framework.
Just for information.
Click to expand...
Click to collapse
I'm just gonna use titaniums backups freeze feature, I never knew it could do that.
I don't suppose someone somewhere has listed which of the com.sony*** files are safe to disable have they?
Astralogic said:
I'm just gonna use titaniums backups freeze feature, I never knew it could do that.
I don't suppose someone somewhere has listed which of the com.sony*** files are safe to disable have they?
Click to expand...
Click to collapse
TiBu's freeze doesnt help against some apps. They keep running in background but are no longer shown in Settings or Greenify.
Nope, but you might check any flashable "Xperia Media App port" zip. The more complete, the better.
The files that are included in framework folder are usually safe to remove. :good:
WhiteNeo said:
TiBu's freeze doesnt help against some apps. They keep running in background but are no longer shown in Settings or Greenify.
Click to expand...
Click to collapse
I have yet to see this happen. Maybe you can point me to one example, since I'd like to test this?
Antiga Prime said:
I have yet to see this happen. Maybe you can point me to one example, since I'd like to test this?
Click to expand...
Click to collapse
OmniSwitch.
Add it to Greenify first, then freeze it and reboot. Check Greenify main activity and you'll see.
Was getting on my nerves for two months, till I finally decided to uninstall it.
WhiteNeo said:
OmniSwitch.
Add it to Greenify first, then freeze it and reboot. Check Greenify main activity and you'll see.
Was getting on my nerves for two months, till I finally decided to uninstall it.
Click to expand...
Click to collapse
Well, don't know why you would add it to Greenify first, makes no sense, but nonetheless, you're right. But then again, this might be due to the way OmniSwitch is integrated into OmniRom in order to use it for the Recent Apps switch. I don't remember this happening on Carbon, which also has OmniSwitch without that integration. I'm on Omni right now so I can't verify this.
In Titanium Backup some apps are red, any idea why?
I'm going to disable two of those com.sony things every morning, but most of them are red.
Astralogic said:
In Titanium Backup some apps are red, any idea why?
I'm going to disable two of those com.sony things every morning, but most of them are red.
Click to expand...
Click to collapse
Most of the framework stuff cannot be disabled, it has to be uninstalled because Dalvik cache would have to be rebuilt when its gone.
I suggest trying doenen's heavily debloated 4.3 rom. Or at least having a look at its apps and framework to see what he has removed. :good:
Astralogic said:
In Titanium Backup some apps are red, any idea why?
I'm going to disable two of those com.sony things every morning, but most of them are red.
Click to expand...
Click to collapse
Titanium Backup has a help section which explains the colors. A red colored app means it's a System Service. I'm sure you can open the help section and check out what the other colors mean.
And as @WhiteNeo said, having a look at some other debloated ROM will help you decide what you can remove or not; don't disable or uninstall something just for the sake of disabling it. Find out what it's for and then decide if you need it, or if your Rom needs it in order to function properly.
If it's of any help you can use this as a reference. I made that back when I used to use Stock ROMs .
WhiteNeo said:
TiBu's freeze doesnt help against some apps. They keep running in background but are no longer shown in Settings or Greenify.
Nope, but you might check any flashable "Xperia Media App port" zip. The more complete, the better.
The files that are included in framework folder are usually safe to remove. :good:
Click to expand...
Click to collapse
Antiga Prime said:
I have yet to see this happen. Maybe you can point me to one example, since I'd like to test this?
Click to expand...
Click to collapse
WhiteNeo said:
OmniSwitch.
Add it to Greenify first, then freeze it and reboot. Check Greenify main activity and you'll see.
Was getting on my nerves for two months, till I finally decided to uninstall it.
Click to expand...
Click to collapse
Just confirming that @WhiteNeo is right. Even on Carbon Omniswitch's process is still active even though it's frozen/disabled. It doesn't consume RAM as far as I can tell, but this is odd behavior.