Question for OTA - Moto X Q&A

Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app

kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.

Thanks for your answer. I will just unfreeze freezed apps once 5.0 is available.
Sent from my XT1053 using XDA Free mobile app

kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Click to expand...
Click to collapse
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
aviwdoowks said:
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.
Click to expand...
Click to collapse
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.

Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app

KidJoe said:
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.
Click to expand...
Click to collapse
+1

kenosis said:
Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't used that app. Best thing to say is take an app that you know what the apk name is, use Android Tuner to freeze it, then use a root capable file explorer to look for the apk. If it's still named correctly and located in the original place on the phone, then you should be ok.

Related

Need help: Attempting to restore DLNA/System Service after Uninstalling

Prior to rooting, I reformatted my phone and afterwards I backed up all system apps and bloatware with Titanium Backup Pro. I then uninstalled all bloatware that I knew was safe to uninstall. No problems whatsoever.
However, just to be on the safe side, I decided that I'm going to restore all uninstalled apps, unroot, reset, reroot, and use Pete's script bloatware remover/renamer.
All bloatware has been reinstalled successfully except for DLNA. Whenever I try to restore DLNA or DLNA System Service 1.0, Titanium Backup simply stays on "Restoring App+Data" forever, unless I reboot the phone. I have tried reinstalling DLNA first then I tried reinstalling DLNA System Service first. To no avail. It just gets stuck on "Restoring App+Data."
Any ideas?
Hmm, strange...same thing is now happening with Flickr Authenticator. Perhaps TI is bugging out now. I just don't get it. Really hope to hear some input soon.
i restore all removed apps with this: www.psouza4.com/Droid3
once U download unzip n place in a subfolder named restore
I had a similar thing happen to me when using Titanium, but with different apps. I'm not sure what causes the bug, nor am I certain about how to fix it. It's part of why people have been recommending that we freeze apps as opposed to backing them up (with Titanium) and then deleting them.
However, you can get the apps back by going into the system dump and copying the necessary files back into /system/app. You can find the system dump here:
http://forum.xda-developers.com/showthread.php?t=1164736
Just take the DLNA and DlnaSystemService apks and odex files, place them on your SD card, and then copy them over to /system/app using whichever method you prefer (Root Explorer, ADB, etc). Hope this helps
mrcastillo said:
i restore all removed apps with this: www.psouza4.com/Droid3
once U download unzip n place in a subfolder named restore
Click to expand...
Click to collapse
I don't think Psouza's Script can restore apps that are uninstalled. Only if they are renamed or frozen by TI. Please someone chime in and correct me if I'm mistaken.
RandomEncounter said:
I had a similar thing happen to me when using Titanium, but with different apps. I'm not sure what causes the bug, nor am I certain about how to fix it. It's part of why people have been recommending that we freeze apps as opposed to backing them up (with Titanium) and then deleting them.
However, you can get the apps back by going into the system dump and copying the necessary files back into /system/app. You can find the system dump here:
http://forum.xda-developers.com/showthread.php?t=1164736
Just take the DLNA and DlnaSystemService apks and odex files, place them on your SD card, and then copy them over to /system/app using whichever method you prefer (Root Explorer, ADB, etc). Hope this helps
Click to expand...
Click to collapse
That's fantastic, thank you my friend.
You are wrong.
When I was updating from 5.5.959 to 5.6.890, one of my apps was gone. Deleted. Idk how, but I searched my system for 10 minutes, it was called Fota.apk
I used psouza4s tools (he helped me) and restored the missing app, and then I got to update to 5.6.890
Sent from my DROID3 using xda premium
kshen1 said:
You are wrong.
When I was updating from 5.5.959 to 5.6.890, one of my apps was gone. Deleted. Idk how, but I searched my system for 10 minutes, it was called Fota.apk
I used psouza4s tools (he helped me) and restored the missing app, and then I got to update to 5.6.890
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Wonderful, I'll give that a shot right now then. Thanks man.

[Q] Installing Apps as System Apps on Rooted Phone

I am wondering if OTA updates will still work if I install apps as system apps. For example, Avast (anti-theft app, successor to theft aware) has an option to install as a system app on a rooted phone, thereby enabling the app to survive a factory wipe. The way I believe it does this is install in the root directory. My understanding was that OTA updates will check to see if the root directory is a recognized stock directory before installing, so this would imply at installing other apps to root will cause this check to fail. However, I believe superuser is installed to root directory as part of the rooting process, and I have been able to perform OTAs on phones with superuser installed.
Anyone have any experience with updating OTA with apps installed to the root directory?
I believe that it moves them from /data/app to /system/app, thus changing how the phone sees the app.
Rlin5741 said:
I am wondering if OTA updates will still work if I install apps as system apps. For example, Avast (anti-theft app, successor to theft aware) has an option to install as a system app on a rooted phone, thereby enabling the app to survive a factory wipe. The way I believe it does this is install in the root directory. My understanding was that OTA updates will check to see if the root directory is a recognized stock directory before installing, so this would imply at installing other apps to root will cause this check to fail. However, I believe superuser is installed to root directory as part of the rooting process, and I have been able to perform OTAs on phones with superuser installed.
Anyone have any experience with updating OTA with apps installed to the root directory?
Click to expand...
Click to collapse
Usually the system apps are only updated individually with patch files. If there were extra files under /system, I don't think the patch would fail (or even care about it). I don't have any experience with it though, but that would be my logical guess.
Sent from my XT860 running ICS
AFAIK any changes to system changes cause OTA to fail. But I could be wrong. Never tried
Sent from my XT860 using xda premium

Contacts.apk

Can we use contacts.apk from cyanogenmod in stock rom?....if we can,anyone please upload it for our phone.I don't like the stock contacts.My phone is at&t model and Android 4.1
Sent from my MB886
No help for me.....why? Did I asked something wrong?
Sent from my MB886
SanthosneoV said:
No help for me.....why? Did I asked something wrong?
Sent from my MB886
Click to expand...
Click to collapse
I think u posted in wrong place. Btw, why dont u take it from cm10 and try then let us know whether it works or not.
Sent from my MB886 using xda app-developers app
SanthosneoV said:
Can we use contacts.apk from cyanogenmod in stock rom?....if we can,anyone please upload it for our phone.I don't like the stock contacts.My phone is at&t model and Android 4.1
Sent from my MB886
Click to expand...
Click to collapse
Have fun.
penser said:
Have fun.
Click to expand...
Click to collapse
On the stock AT&T firmware for the AHD (4.1), you only need to root the phone and remove the vendor apps and the AT&T Addressbook and Yellow Pages apks from the phone and Contacts will load up without any carrier reference. It's actually pretty cool to see how easy it is to remove carrier customizations from this build and look somewhat vanilla.
It should work...make sure you clear cache before you install. And you cant just install it, you have to copy with a root explorer and set permissions correct...
wamsille said:
On the stock AT&T firmware for the AHD (4.1), you only need to root the phone and remove the vendor apps and the AT&T Addressbook and Yellow Pages apks from the phone and Contacts will load up without any carrier reference. It's actually pretty cool to see how easy it is to remove carrier customizations from this build and look somewhat vanilla.
Click to expand...
Click to collapse
I try with root browser but appears uninstall unsuccessful. What I did wrong?
Need change permissions?
Need another program?
I don't find vendor apps.
My phone is only root.
If you are running the stock ROM with root access, you need to download and install Root Explorer. It isn't a free app but I'm all for supporting development. (Note: I am in no way affiliated with any paid apps on the Play Store)
Open Root Explorer and navigate to System\Vendor. There is a directory \apps that you can just delete, which will elminate most of the pre-installed applications. Root Explorer will ask for root permission, which will open up your SU app. Grant permissions, then Root Explorer will warn you that you are still in R/O mode and confirm that you want R/W access to delete or move the files. Grant access again and the operation will be complete. You aren't done though, as the rest of the apps are loaded in System\apps, so go up a folder back to \System then open up \apps. You want the AT&T phonebook sync, Ready2Go and Yellow Page apps for starters to be deleted. Caution, you will see a lot of force closures but this is to be expected. You'll have leftover entries listed on downloads in App Manager, which you can delete manually one at a time.
If you don't want QuickOffice, you can remove the apk for it and any other preinstalled application that came with the phone. Keep in mind that you will need to be conservative in what you remove because one wrong move/delete could cause you to lose functionality. You should notice a much cleaner app drawer for starters, plus the Contacts app looks like Jelly Bean / ICS without the Yellow Pages icon.
At this point you should have a fairly clean 4.1.1 stock install on the Atrix. What I would like to do at some point is make a 4.1.1 based ROM using the AT&T update, just removing Blur and making everything vanilla. After that make a vanilla 4.0 ROM that is compatible with the Lapdock. I may have moved onto the Nexus 4 but something has to be said for this phone's build quality.
Thank You.:good:

Verizon apps removing??

hi to all
i flashed a Verizon firmware on my moto x but i see that are containing the Logo from Verizon and some preinstalled app
there is any way to remove that apps and to remove the Verizon logo?
thank u
Root your device and after that install "root browser" - dele all vzw (verizon wireless) apps in folder system/apps & system/priv-apps
q173242 said:
Root your device and after that install "root browser" - dele all vzw (verizon wireless) apps in folder system/apps & system/priv-apps
Click to expand...
Click to collapse
That's a good way to break things and cripple your phone.
What "things"? Using my two moto x's for two months now with these "settings".
curious. I have some apk's with the Vzw prefix. Are these verizon? and if so why are they on my phone if I'm not a verizon customer?
ForSquirel said:
curious. I have some apk's with the Vzw prefix. Are these verizon? and if so why are they on my phone if I'm not a verizon customer?
Click to expand...
Click to collapse
what firmware u have??
look at info if u have verizon firmware
danger2u said:
what firmware u have??
look at info if u have verizon firmware
Click to expand...
Click to collapse
it's a uscellular firmware but I have 2 apps listed with Vzw
VzwController and VzwPhoneService
ForSquirel said:
it's a uscellular firmware but I have 2 apps listed with Vzw
VzwController and VzwPhoneService
Click to expand...
Click to collapse
it s unlocked?
maybe u put in some Verizon sim and it instaled this apps
nhizzat said:
That's a good way to break things and cripple your phone.
Click to expand...
Click to collapse
I have read conflicting information on this topic. Is it okay to delete the apk from the system app folder for VZ Navigator and NFL Mobile and the Caller ID apk from the system priv-app folder? I am not sure if this will be a problem later. I have heard other people claim you should never delete any bloatware apks but instead freeze them using Titanium Backup.
Not sure if there is a definitive answer or what the downside would be to deleting those 3 apps.
danger2u said:
it s unlocked?
maybe u put in some Verizon sim and it instaled this apps
Click to expand...
Click to collapse
nope. it's been the exact same since I brought it home from the store. That's why it confused me to see the VZW apps on a USCellular phone
i would not delete them for FC issues i would just install Titanium Back up and Freeze the apps you dont want.
by doing this you should never have any FC issues and if you do you can unfreeze them.
that would be the safest route to remove them
dray_jr said:
i would not delete them for FC issues i would just install Titanium Back up and Freeze the apps you dont want.
by doing this you should never have any FC issues and if you do you can unfreeze them.
that would be the safest route to remove them
Click to expand...
Click to collapse
i ll let in with this apps untill Motorola release a european retail firmware
on 14 january seems that they have a presentation of Moto x in UK
i know that removing system apps can harm the phone
KLRTN said:
I have read conflicting information on this topic. Is it okay to delete the apk from the system app folder for VZ Navigator and NFL Mobile and the Caller ID apk from the system priv-app folder? I am not sure if this will be a problem later. I have heard other people claim you should never delete any bloatware apks but instead freeze them using Titanium Backup.
Not sure if there is a definitive answer or what the downside would be to deleting those 3 apps.
Click to expand...
Click to collapse
Usually OTA updates will look for certain files to be present on your phone and verify their size and check sums (MD5 or the like) before the OTA update will install. If files are missing or changed, the ota update will fail.
By deleting apk's of pre-installed apps from your phone, you risk needed files not being present which could prevent OTA Updates from installing. You could manually rename each APK now (VZNAV.APK to VZNAV.APK.BAK) and rename it back prior to taking OTA. This way you don't have to hut for them, but with the possibility of so many VZW APK's to rename, you could have a hard time remembering all of them to rename for the next OTA.
So,the easiest two suggested alternatives has been to use the Phone's App Manager to disable apps (they can stay disabled, even during an OTA update), or Titanium Backup to Freeze apps (you must unfreeze before taking OTA).
KidJoe said:
Usually OTA updates will look for certain files to be present on your phone and verify their size and check sums (MD5 or the like) before the OTA update will install. If files are missing or changed, the ota update will fail.
By deleting apk's of pre-installed apps from your phone, you risk needed files not being present which could prevent OTA Updates from installing. You could manually rename each APK now (VZNAV.APK to VZNAV.APK.BAK) and rename it back prior to taking OTA. This way you don't have to hut for them, but with the possibility of so many VZW APK's to rename, you could have a hard time remembering all of them to rename for the next OTA.
So,the easiest two suggested alternatives has been to use the Phone's App Manager to disable apps (they can stay disabled, even during an OTA update), or Titanium Backup to Freeze apps (you must unfreeze before taking OTA).
Click to expand...
Click to collapse
Thanks! That has been the clearest explanation I have seen on this topic.
Sent from my XT1060 using Tapatalk
I rooted my phone and deleted 3 verizon apps (without backing them up) prior to learning what the consequences would be in deleting. Rookie mistake on my part but I was coming from a Nexus and was never concerned with OTA updates or bloatware.
Now I am trying to figure out if I can download the apks for the deleted files and push them back to the system folder on the phone. I have done a bit of searching and have not found anything or anywhere to download the correct files.
KLRTN said:
I rooted my phone and deleted 3 verizon apps (without backing them up) prior to learning what the consequences would be in deleting. Rookie mistake on my part but I was coming from a Nexus and was never concerned with OTA updates or bloatware.
Now I am trying to figure out if I can download the apks for the deleted files and push them back to the system folder on the phone. I have done a bit of searching and have not found anything or anywhere to download the correct files.
Click to expand...
Click to collapse
HERE u have the vzw files and apks
i extracted from my moto x
hope helps u
https://drive.google.com/file/d/0BwTULBGmnkwqR0ZoQUxpSDd0aGs/edit?usp=sharing
danger2u said:
HERE u have the vzw files and apks
i extracted from my moto x
hope helps u
https://drive.google.com/file/d/0BwTULBGmnkwqR0ZoQUxpSDd0aGs/edit?usp=sharing
Click to expand...
Click to collapse
Thank you very much. That was exactly what I needed.

Detaching apps from market

Like many others I don't always like the updates to some of my installed apps. Yet it is a hassle to avoid accidentally installing an unwanted update. It is so much easier to click on "update all" in Google Play instead of going through each app's update individually.
Yet I have not found a way to make an installed and purchased app safe from updating. Titanium backup's "detach from market" does not work.
May I suggest a module that would prevent an app from updating? Maybe by making its app files write only?
I think a package like that would be useful. But an easy workaround in the mean time would be to go to Google play store settings and change the automatic update to never.
I already don't allow automatic updates but it is still a nuisance to have to pick through and avoid the persistent update notifications.
I currently use Changelog Droid to accomplish this, although I'd certainly welcome a module to replace it.
Yes, that will tell me what the update changes. I'm looking for something that would "prevent" the update.
this would help me a lot as well. im sure there is a module somewhere that will detach an app from the market and it would just stop showing in the pay store updates.
I think it would help a lot of users. Titanium backup has had that feature for years but it hasn't worked for years. Every time the play store refreshes it reattaches the app.
I am not a programmer but it seems to me that if a tool made an installed app's main files "read only" any attempted update would simply fail, which would solve the problem. Wouldn't that work?
Right now, I try to avoid certain updates but if I accidentally update I use titanium backup to restore the previous backed up version. But it would be nice if it could be simpler. I don't understand why the play store insists on forcing updates.
maybeme2 said:
I think it would help a lot of users. Titanium backup has had that feature for years but it hasn't worked for years. Every time the play store refreshes it reattaches the app.
I am not a programmer but it seems to me that if a tool made an installed app's main files "read only" any attempted update would simply fail, which would solve the problem. Wouldn't that work?
Right now, I try to avoid certain updates but if I accidentally update I use titanium backup to restore the previous backed up version. But it would be nice if it could be simpler. I don't understand why the play store insists on forcing updates.
Click to expand...
Click to collapse
There is some kind of workaround for this issue.
You can use Raccoon to download .apk files from the Play Store to your computer (you can also download previous app versions, search the thread for it). Afterwards, use the app ZipSigner to sign the downloaded .apk with your own key. If required, uninstall the official app version, reboot, install the newly signed .apk and reboot again. Now the update notification from Google Play Store should be gone as the app isn't signed with the same key as the official one from Play Store.
Thank you. I'll try that. Thanks for taking the time to help.
orville87 said:
There is some kind of workaround for this issue.
You can use Raccoon to download .apk files from the Play Store to your computer (you can also download previous app versions, search the thread for it). Afterwards, use the app ZipSigner to sign the downloaded .apk with your own key. If required, uninstall the official app version, reboot, install the newly signed .apk and reboot again. Now the update notification from Google Play Store should be gone as the app isn't signed with the same key as the official one from Play Store.
Click to expand...
Click to collapse
thanks for the workaround. can i use titanium backup to restore the data of the app after download and signing it?
+1
resitm said:
thanks for the workaround. can i use titanium backup to restore the data of the app after download and signing it?
Click to expand...
Click to collapse
maybeme2 said:
+1
Click to expand...
Click to collapse
Yes, you can That's one huge advantage of the described method :good:
Google Play Store checks for the sign code, whereas Titanium Backup depends on the package name (which isn't changed during signing process).
orville87 said:
Yes, you can That's one huge advantage of the described method :good:
Google Play Store checks for the sign code, whereas Titanium Backup depends on the package name (which isn't changed during signing process).
Click to expand...
Click to collapse
I signed the apk and ended up with a zip file, so i flashed that and got the attached error. What am i doing wrong? Got the apk from the developer website which might be causing the issue.
resitm said:
I signed the apk and ended up with a zip file, so i flashed that and got the attached error. What am i doing wrong? Got the apk from the developer website which might be causing the issue.
Click to expand...
Click to collapse
You can select if you want to sign the .apk as .zip or as .apk file (.apk files are .zip files, just with another file type). Don't flash them via recovery. If you can't find the option to sign the .apk as .apk, just sign it as .zip and rename it to .apk afterwards.
orville87 said:
You can select if you want to sign the .apk as .zip or as .apk file (.apk files are .zip files, just with another file type). Don't flash them via recovery. If you can't find the option to sign the .apk as .apk, just sign it as .zip and rename it to .apk afterwards.
Click to expand...
Click to collapse
Thank you very much, i didnt know i could change the output to apk. The app no longer appears in the play store.

Categories

Resources