Related
For reasons I won't go into (mainly because they're boring) I deleted Google talk.apk from Root Explorer (I was following instructions to update the app but those didn't work) and now I can't get it back. I've factory reset the phone to no avail. I have Google Voice installed, but can't seem to get talk back. If anyone could help, it would be greatly, greatly appreciated. Thanks!
BTW, I did a search before posing the ?, but the only solution I found was for a different phone, and when I ran those steps, when I tried to open Talk, it would just FC.
libracolo said:
For reasons I won't go into (mainly because they're boring) I deleted Google talk.apk from Root Explorer (I was following instructions to update the app but those didn't work) and now I can't get it back. I've factory reset the phone to no avail. I have Google Voice installed, but can't seem to get talk back. If anyone could help, it would be greatly, greatly appreciated. Thanks!
BTW, I did a search before posing the ?, but the only solution I found was for a different phone, and when I ran those steps, when I tried to open Talk, it would just FC.
Click to expand...
Click to collapse
Have you tried snagging the files from another Photon and installing? Can you post what steps you have already taken please?
Yes....factory reset won't restore system apps. You can flash Juggs update.zip and that will restore for you. Then would have to root again of course but is easy enough.
Just download a custom rom , unzip it and copy the required app to your device.
faria said:
Just download a custom rom , unzip it and copy the required app to your device.
Click to expand...
Click to collapse
+1
I should of said that instead of grabbing it from another phone. Thanks faria.
CCallahan said:
Have you tried snagging the files from another Photon and installing? Can you post what steps you have already taken please?
Yes....factory reset won't restore system apps. You can flash Juggs update.zip and that will restore for you. Then would have to root again of course but is easy enough.
Click to expand...
Click to collapse
Thanks for the info. If I flash Juggs update, will it hurt anything (since I already am on the latest OTA)?
faria said:
Just download a custom rom , unzip it and copy the required app to your device.
Click to expand...
Click to collapse
I will try that as well. When I did a search, I found where someone had posted the talk.apk.zip file which I copied to my sd card, unzipped and then copied to system/apps (through Root Explorer), but that is when I started getting FC's. I then installed it (from Root Explorer) even with the same result. It may be that it wasn't the right version maybe? So if I extract it from a Rom, do I just copy it to the System/Apps folder (using Root Explorer)? Sorry for the confusion, and thanks much for the help.
libracolo said:
I will try that as well. When I did a search, I found where someone had posted the talk.apk.zip file which I copied to my sd card, unzipped and then copied to system/apps (through Root Explorer), but that is when I started getting FC's. I then installed it (from Root Explorer) even with the same result. It may be that it wasn't the right version maybe? So if I extract it from a Rom, do I just copy it to the System/Apps folder (using Root Explorer)? Sorry for the confusion, and thanks much for the help.
Click to expand...
Click to collapse
you need to delete the talk.odex file from system apps othewize you get fcs.
faria said:
you need to delete the talk.odex file from system apps othewize you get fcs.
Click to expand...
Click to collapse
I don't (and didn't) have that file, only talk.apk (which of course was deleted). Isn't the odex like the cache? If so, would it have been removed when I ran App Cache Cleaner?
libracolo said:
I don't (and didn't) have that file, only talk.apk (which of course was deleted). Isn't the odex like the cache? If so, would it have been removed when I ran App Cache Cleaner?
Click to expand...
Click to collapse
Correct.
Well short of getting the apk from the very same rom version ,you will have to reflash he rom.
ps.
there the new google talk with video here in the forum, that probably would fix your problem.
Here
http://forum.xda-developers.com/showthread.php?t=773272
http://forum.xda-developers.com/showthread.php?t=716888
faria said:
Here
http://forum.xda-developers.com/showthread.php?t=773272
http://forum.xda-developers.com/showthread.php?t=716888
Click to expand...
Click to collapse
Hey faria, thanks! I did the top link last night (that was the one that I copied the talk.apk.zip (2.2) over to my SD card, extracted, and then copied to /system/apps/. I installed from there (btw, I did change to R/W first), but all I got was FC's on talk. I'm thinking I needed to reboot after installing, maybe? I'm not really sure why I would need to reboot though, but if that is all it takes, I'm happy. I will try that when I get home tonight (don't have a spare cable with me right now). Thank you sooo much for your help.
libracolo said:
Thanks for the info. If I flash Juggs update, will it hurt anything (since I already am on the latest OTA)?
Click to expand...
Click to collapse
If you still end up having problems.....
Juggs update.zip is just the latest OTA with a few minor modifications. So basically it will restore all to pretty close out of the box and restore any system apps.
However, you can also flash the sbf which is the actual newest OTA exactly like the one pushed from Motorola/Sprint. This requires using rsd and isn't quite as easy as the update.zip which can just be flashed via bootstrap recovery.
Any one of these methods will require you to root the phone again.
CCallahan said:
If you still end up having problems.....
Juggs update.zip is just the latest OTA with a few minor modifications. So basically it will restore all to pretty close out of the box and restore any system apps.
However, you can also flash the sbf which is the actual newest OTA exactly like the one pushed from Motorola/Sprint. This requires using rsd and isn't quite as easy as the update.zip which can just be flashed via bootstrap recovery.
Any one of these methods will require you to root the phone again.
Click to expand...
Click to collapse
Yeah, I'm gonna flash the sbf, I just downloaded it and installed the drivers and stuff, but I think I'm gonna wait until tomorrow night (only because it's been a really long day, started at 4 am MST just ending), so I think my brain is fried. Thanks for all your help today, I'll let ya know tomorrow how it goes. What a freakin pain in the arse this talk.apk has become....haha
Update: I flashed the sbf, re-rooted, and everything is great now, have Talk back. Thanks for all the help!
OK, I'm a noob and made the noob mistake of deleting (rather than freezing) some system apps after rooting. Won't make that mistake again.
I do not have backups nor am I completely sure which apps are missing. As a result of these missing apps I cannot complete the latest OTA update.
I downloaded a system dump and noted a few apk files in it that were not on my system though I believe that there are other apk files missing which are not in the system dump (MyLibrary, WebStorage etc) so I am not sure the particular system dump I got is up to date.
Copying the apk files to my system\app folder did not help, the update still fails.
I seem to recall seeing instructions somewhere for manual installation via power/down volume which would allow you to see a text dump of the update with reports of missing files or mismatched CRC's. I cannot find this again but such a thing would help me determine what is missing so that I can then attempt to find replacement apk files.
Sorry for being such a noob. Can anyone help?
Thanks
Made the same mistake when upgrading to ICS from Honeycomb...
If you get the previous update (the one your running now) from the Asus website, extract the update file and place it in one of the folders on the tablet, (I forgot which folder, sorry...) reboot and the tab will recognize it and prompt you to update. Once that update is finished installing, you should have all your bloat back. Delete the update file from the tab since you don't need it anymore, and then try to update to the most recent OTA Update.
Just do a search in the TFP forums and you should find complete instructions on how to do this.
I'm just assuming this will work for ICS to ICS... because it worked for me when I updated to ICS to Honeycomb...
Hope this method works for you.
I had the same issue.
Download:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/US_epaduser9_4_2_11UpdateLauncher.zip
Once downloaded, extract the contents of the zip file (yes, its another zip file of the same name inside) to your MICRO SD. put your micro SD in your TF201 (or eject and re-insert if you copied via cable)
Once the card is mounted you will see a triangle with an "!" in the notification area. Touch the notification and it will open a dialogue to install the manual update.
You will lose root, even with OTA Rootkeeper.
Re-root your device. Install OTA Rootkeeper if you have not already. Run Voodoo OTA Rootkeeper. Protect your su.
Check for updates. Install .13 OTA.
$$$
Should be a lesson learned. Stop messing with system apps. Always causes problems one way or another. The apps included are nothing to even be considered bloat. I still have everything installed n prime super fast. If anything just freeze the apps, never delete them unless u always want to have failed OTA.
demandarin said:
Should be a lesson learned. Stop messing with system apps. Always causes problems one way or another. The apps included are nothing to even be considered bloat. I still have everything installed n prime super fast. If anything just freeze the apps, never delete them unless u always want to have failed OTA.
Click to expand...
Click to collapse
I agree completely, and my lesson is learned. But why on earth would a freaking E-reader app be a system app?
That was my hangup. AsusReader a/k/a the My Library app.
And mine was backed up with Titanium, which obviously bungled it since it would not restore.
phree1 said:
I agree completely, and my lesson is learned. But why on earth would a freaking E-reader app be a system app?
That was my hangup. AsusReader a/k/a the My Library app.
And mine was backed up with Titanium, which obviously bungled it since it would not restore.
Click to expand...
Click to collapse
I went through the same thing on my Atrix phone. Rooted n went messing around deleting at&t bloatware. It killed my OTA updating. That's why now I'm still on froyo on it. Never bothered to manually update it. Still works great on froyo though. But I learned my lesson from that.
demandarin said:
I went through the same thing on my Atrix phone. Rooted n went messing around deleting at&t bloatware. It killed my OTA updating. That's why now I'm still on froyo on it. Never bothered to manually update it. Still works great on froyo though. But I learned my lesson from that.
Click to expand...
Click to collapse
Your still on froyo... why not just flash a sbf file to return to stock? Or better yet, unlock the boot loader and get yourself CM7 already.
Messing with system files isn't a big deal, as long as you have a backup.
Sent from my Transformer Prime TF201 using xda premium
Yep, this did the trick. Thanks very much.
Lesson learned, don't mess with the system apps.
If you have safestrap go into the app, select the uninstall feature and re try the install. No need to download anyones utility or no need to factory reset.
do you happen to know the download path of the ota? Due to safestrap mine failed.. hate to download it again..
Should be in setting/ about phone/ updates
yeah thats to download it again.. i was hoping it would just install it if the system saw the file there. oh well at 55% i can wait a little longer..
After the phone reboots, if the install takes really really slow then ur on the right path
What if I have installed BootStrap recovery????
kanagadeepan said:
What if I have installed BootStrap recovery????
Click to expand...
Click to collapse
I dont have bootstrap but from what im gathering unistall that as well
then uninstall it.. my install failed with it. That is what the OP is saying you will need to uninstall them for the update to install
mine failed for a second time :/
Did you use voodoo ota and temp unroot? You need to do that as well i just figured that was a given by now
cheatthepocket said:
Did you use voodoo ota and temp unroot? You need to do that as well i just figured that was a given by now
Click to expand...
Click to collapse
Arrgh i swear i did.. While i was doing tb backups it slipped my mine i reckon.. really wish i could find the dl path for the update... hopefully third time will work!
Whether uninstalling the "Razr BootStrap" using "Managa Applications" is enough... Or I have to do some extra steps too????
Please help me... I don't care much about root, as the update usually unroots it and I can root again easily...
Bootstrap may be a dif problem. Like i said i used safestrap. I dunno what else you have done to urvphone. You might need the dev team to help you. I never used roms so i was stock i also never froze any bloatware.
Ummm. You're welcome....
Sent from my DROID RAZR MAXX via XDA Premium
I think i thanked you last night lol.
arrgh 3rd time failed no bloat removed just stock rooted.. temp unrooted safestrap uninstalled.. any ideas? guess i might need to restore back to stock..
Sounds like you have something breaking the install. I know ive done very little to my phone. Factory reset may be your option but i would get hold of a tech here b4 u do anything
kanagadeepan said:
Whether uninstalling the "Razr BootStrap" using "Managa Applications" is enough... Or I have to do some extra steps too????
Please help me... I don't care much about root, as the update usually unroots it and I can root again easily...
Click to expand...
Click to collapse
You need to first uninstall the razr bootstrap app through "manage apps" (look under the all apps tab - clear data first while you're there).
Then, with root explorer or such, go to the /system/bin folder, mount r/w, and delete the following files:
hijack
logwrapper
Then, rename logwrapper.bin to simply logwrapper (just remove the .bin)...
Reboot, and it should be all cleaned out.
I would also recommend using voodoo ota rootkeeper to backup your root, then temporarily un-root (hide root) before doing the OTA install.
If you still get ota install errors, then you probably removed some system apps that are verified before installation... check /cache/recovery/last_log for errors.. then either replace those apk/odex files, or flash the fxz..
Sent from my phone's mind
alteredlikeness said:
You need to first uninstall the razr bootstrap app through "manage apps" (look under the all apps tab - clear data first while you're there).
Then, with root explorer or such, go to the /system/bin folder, mount r/w, and delete the following files:
hijack
logwrapper
Then, rename logwrapper.bin to simply logwrapper (just remove the .bin)...
Reboot, and it should be all cleaned out.
I would also recommend using voodoo ota rootkeeper to backup your root, then temporarily un-root (hide root) before doing the OTA install.
If you still get ota install errors, then you probably removed some system apps that are verified before installation... check /cache/recovery/last_log for errors.. then either replace those apk/odex files, or flash the fxz..
Sent from my phone's mind
Click to expand...
Click to collapse
Thanks so much for the info. That logwrapper file was withholding me from updating.
I tried deleting and renaming the files with no success updating. I eventually just ended up doing a factory wipe and using Matt's Utility and flashing back to stock. It was a little frustrating, but the Verizon backup utility combined with Google services saved me. I guess i need to learn how to use Titanium backups. lol
this thread should be titled "How I got my Safestrapped RAZR to install ICS OTA successfully", as your issue was more to do with safestrap then specifically just being rooted.
I searched the forum but was not able to find this answer. Is there an .apk that can be renamed once rooted that will prevent OTAs from being downloaded?
I came from a Droid X and this is something that we had to do when we were rooted. On Verizon-Samsung devices.... does the OTA auto download and install? or do you have to accept it?
If you have Titanium Backup , you can just freeze "AT&T Software update" if I'm not mistaken that would do it.
That didn't work for me, at least on sprint. What DID work was letting it try to update and once it fails, it doesn't reappear for a long time (assuming you're on a custom recovery).
Sent from Sprint's 3rd Blazed ICS Galaxy
I'd like to know this as well...
I guess the biggest concern I have is being able to decline the OTA. Is this possible? I have rooted, loaded CWM, and I have removed some system .apk files that I had no use for (i backed them up to sdcard though).
If the OTA is automatically accepted... it would fail due to CWM, correct?
Okay, first, I have tried googling and came up with no answers. Second, I tried looking through xda and came up with no answers. The closest thread I found anywhere was here. Here is my situation.
I have the EVO 4G LTE and I am running stock and rooted. Over last weekend I became s-off. So, now I am s-off with a stock recovery and would like to install the OTA update that is out. Please don't tell me not to in this thread and just wait for a rooted ROM and the like. I know the risks involved and what potentially could happen.
Ultimately, when I try to apply it I get the red triangle. When I hold the volume up and power on it goes into the stock recovery and here is what it says.
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying to fotaBoot to /data/system for customize reload...
Verifying current system...
assert failed: apply_patch_check("/system/app/SoundHound_Freemium.odex","66f464f0ac1689b294f72c9006532b66195ca2ae", "798feb0102e51071f4634f784b740e168507f4")
E:Error in /internal_sdcard/Download/OTA_Jewel_CL_ICS_40_Sprint_WWE_1.22.651.3-1.13.651.1_release_268385t21cg6sjfe2o8g14.zip
(Status 7)
Installation aborted.
So, what this tells me is that soundhound is preventing me from installing the update. I didn't even have soundhound installed when I tried the update. Also, I looked with root explorer under /system/app and there was nothing listed for soundhound or the like. I thought just deleting the file would maybe solve my problem. I also tried installing it from the market. I think I must have accidentally restored this file from a different backup on accident and don't have that backup anymore.
So, this leaves me to my quandary. What can I do to install the OTA? Does anyone have any thoughts or insight? Thanks in advance.
Okay, I have tried this as well. I flashed the most current TWRP recovery and wiped cache and dalvik cache. Then I flashed a stock recovery and tried the update again. I received the same error as last time with the stupid soundhound.odex file. Does anyone have a soundhound free file with the apk and odex file? I figure if I had that I could place it in the proper location with root explorer or adb install it to get the update to apply. Still, any thoughts could be helpful.
It might be a way for HTC to prevent rooted phones to update as how u explained it soundhound isn't installed but when u purchase this phone it comes with sound hound preinstalled into system directory which u cannot uninstall without root privlages
Sent from my EVO using xda premium
I appreciate the input. I guess I forgot that soundhound comes preinstalled on the phone. I just checked the RUU and looked at the rom and you are right. It is there. So, now I have the .apk and .odex files from the stock rom. My question is now how do I install it so that it looks like it was there from the beginning as a system file?
Thanks again for reminding me it came with the phone. I feel I am closer to being able to install the update.
DONE AND DONE!!!!
First thing is that I changed the title because it was not SoundHound's fault at all. It was my idiot self that uninstalled a system app. I don't remember doing that but I won't deny that somehow I did.
Now to the meat of how I solved this.
I got the correct system files (both .apk and .odex) and placed them on my sd card
I mounted /system/media as r/w with root explorer and copied both files into the /system/media directory (must do this first before putting them into /system/app)
I changed the permissions to rw-r--r-- as were all the other apps in the /system/app directory
I copied both files over to /system/app
I rebooted the phone
Once the phone rebooted I updated the app in question and opened it
I rebooted again just to be safe
Then I downloaded and installed the update
SUCCESS!!!!!
Anyway, just wanted to share for everyone in case you run into a similar problem when trying to update. Reach out to me if you need any help with any of the steps. Thanks to such great people and developers on xda.
Some threads are saying that even if you're S-Off, the new HBOOT won't let you flash Superuser and TWRP. Were you able to reroot?
For various reasons, I'd like to just take the OTA and reflash SU and TWRP (I'm S-Off, rooted, stock recovery right now).
bpdamas said:
DONE AND DONE!!!!
First thing is that I changed the title because it was not SoundHound's fault at all. It was my idiot self that uninstalled a system app. I don't remember doing that but I won't deny that somehow I did.
Now to the meat of how I solved this...
Click to expand...
Click to collapse
greyopaque said:
Some threads are saying that even if you're S-Off, the new HBOOT won't let you flash Superuser and TWRP. Were you able to reroot?
For various reasons, I'd like to just take the OTA and reflash SU and TWRP (I'm S-Off, rooted, stock recovery right now).
Click to expand...
Click to collapse
I was able to reroot. However, first I had to install the lazy panda hboot and flash TWRP through fastboot usb. I then flashed a su zip once I booted into TWRP. Hope this helps. I am trying to make a new thread for this right now.
I had the same issue but with a different problem. I had rewritten my build.prop to incorporate the application associations as they should be (thanks Crapple!). As a result, the OTA was failing to install. Volume UP + Power showed me the error. Restored the original build.prop I had backed up and OTA fired off. A few more steps and I'll have your S-OFF OTA rebuild complete. Thanks!