Here is a Dump from the System Apps for those who accidentally deleted some of them and can't update to OTA2. I deleted some apps, you won't need for OTA2 to make the package smaller.
Remember before updating to OTA2 to protect your superuser by downloading and applying OTA root keeper.
After the update you have to download Superuser then just reactivate root by using ota root keeper.
PW for the archive is:
tptsystemappsdump
When I rooted ,I backup and delete some some flexT9 input file, then I find out I can not recive SMS after root .
So I unroot ,now I get OTA update but it's says error about I miss some flexT9 file.I can not restore file without root.
Now I can never root again ,and I can not even UPDATE OTA because system fille ar change.
What can I do NOW ?
My TPT is rooted (Titanium Backup shows it as rooted and RomManager also) but when I try to reinstall the Browser App it says could not install the app. Also Insallation via adb didn't work.
Can I somehow copy the files manually and what files need to be copied?
Thank you for this, one of our tablets unistalled the lenovo app market while trying to update itself, only want this for the notesmobile update but your dump helped greatly and meant i didn't have to faf about pulling it from my tpt
@Atom2007:
you will have to put the Browser.apk and Browser.odex into /system/apps with i.e. Root Explorer.
delete post
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
I have 2.2 and would like to upgrade to 3.0. I have Safestrap.
Also would like to update CoreDroid 2.0 to 3.0...
Just confused...
rosystreasures said:
I have 2.2 and would like to upgrade to 3.0. I have Safestrap.
Also would like to update CoreDroid 2.0 to 3.0...
Just confused...
Click to expand...
Click to collapse
You will need to apply the latest update .905 to your phone heres how I did it.
Your first step is that you need to return back to your unsafe side and go to Google Play and download OTA Rootkeeper. Open that app up and backup your Root status. Also go into safestrap and uninstall it within the app. Make a backup directory on your external SD and back up both apps so that you can reinstall both after the update completes. Using Root explore or any ES File explore with root access gude to ./data/app and copy what ever apps you want to keep on your unsafe side to the new directory on your external sd storage. Now as long as you haven't changed anything on your unsafe side the .905 will complete without issues, example used TB to freeze bloat apps or even deleted bloat apps. If you have done any of those thing you will need to FXZ the .902 system back on your phone heres the link with instructions. http://forum.xda-developers.com/showthread.php?t=1507798
Now that you have prepared your device go to settings/about phone/System Update. The offical OTA update is out so it should be availible to you. After update is complete the OTA rootkeeper app should still show in the app drawer, but if not you have it backed up on your external to install. Regain root and also reinstall safestrap. Now your backup of your unsafe side through safestrap is useless now so go ahead and delete it or move it so that you don't apply also the data also. I just went ahead and deleted the whole safestrap folder that was on my sd storage since I started all over. The choice is yours. Now with .905 update applyed to your device you can flash 3.0. God Speed.
I have a rooted droid 4 and after much reading about the jb issues, I decided not to upgrade. I have frozen apps in Titanium backup and I still have OTA rootkeeper from the ICS update.
Anyway, this morning I woke up to the phone merrily downloading the update! Argh!!! I turned off data and wifi to stop the download, but I can't find a way to stop it altogether. What do you guys recommend?
I'm not remembering if ics gave me the option to install at my convenience after it downloaded... but I'd like to set the phone not to check for updates on its own. Recommendations?
TIA gang!
Diana
Eta: I cleared cache then installed ES File explorer and renamed update files per instructions I'm unable to link to. it seems to have stopped the download. When I look for a system update, it does say it'sstill in progress, but it hasn't continued. I'll post an update if anything changes
Rename /system/app/BlurUpdater_VZW.apk to BlurUpdater_VZW.apk.bak. Rename /system/app/BlurUpdater_VZW.odex to
BlurUpdater_VZW.odex.bak.
rename FOTA.apk and odex to......
reboot, wipe cache
Sent from my MILESTONE3 using xda premium
Worked like a charm!! Thanks for your expertise!
My friend who also has a moto x just got the software update for sprint. When it was downloading it turned off and whenever he turns it back on , after about 30 seconds it powers back off. Any ideas on how to fix it ???
Please help!!!
Sent from my XT1058 using xda app-developers app
KNiGHTx4 said:
My friend who also has a moto x just got the software update for sprint. When it was downloading it turned off and whenever he turns it back on , after about 30 seconds it powers back off. Any ideas on how to fix it ???
Please help!!!
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I read something about clearing cache earlier but I can't find it now. I am looking to see if I can find it because I am not sure if that is actually what this person did.
Do a factory reset in recovery
Sent on my Moto X
In case anyone was wondering he fixed it with a ROOT browser (has to be root) and going into the root directory (/ not /root) and then going into cache and deleting the OTA. Still not sure how he is going to get the ota. And also it wouldn't even let him factory reset so that doesn't work
Sent from my XT1058 using xda app-developers app
He is probably rooted using PwnMyMoto. This hijacks the stock recovery. That's what's keeping the OTA from installing. He will need to flash the stock recovery via fastboot and then take the OTA.
Sent from my XT1058 using Tapatalk 4
I have this same problem. Stupidly installed the update today without realizing how it would work with pwnmymoto root.
Now the phone just reboots every 30 seconds. I'm not sure where to go from here. Any advice would be appreciated.
KNiGHTx4 said:
In case anyone was wondering he fixed it with a ROOT browser (has to be root) and going into the root directory (/ not /root) and then going into cache and deleting the OTA. Still not sure how he is going to get the ota. And also it wouldn't even let him factory reset so that doesn't work
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
How did he do this while his phone would reboot every 30 sec?
a17o17ymous said:
How did he do this while his phone would reboot every 30 sec?
Click to expand...
Click to collapse
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
Thank you for the quick reply!
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
mar5hal said:
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
Click to expand...
Click to collapse
So, essentially you could just boot to fastboot and run:
Code:
fastboot erase cache
?
Sent from my XT1058 using Tapatalk 4
I had the same problem on a rooted AT&T device. Had to quickly delete the zip file in the cache folder before the device rebooted itself.
Anybody know how to get the update installation done?
vr3690 said:
I had the same problem on a rooted AT&T device. Had to quickly delete the zip file in the cache folder before the device rebooted itself.
Anybody know how to get the update installation done?
Click to expand...
Click to collapse
Use rsdlite or my python script to go back to 100% stock. Then do the update. Just remember, you cannot downgrade after you update!
Sent from my XT1058 using Tapatalk 4
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
I can't even explain how much I appreciate this. I managed to get mine working again following your steps.
Ah! OK. I get it now! The hack to enable root was flashing the kernel image to the recovery partition. Since they used the same signature. Recovery mode in aboot doesn't protect /system so you can mount it read/write.
If you are bootlooping, try just flashing the stock recovery to the recovery partition from fastboot. Next boot, the update will apply. Then flash the pwnmymoto recovery to the recovery partition again after the update and you should be good to go!
In other words... The kernel image does not have the recovery ramdisk. So flashing the stock recovery image allows recovery mode to flash the update. Then switch back to the kernel image on the recovery partition.
If you already had root, this should keep it.
Sent from my XT1058 using Tapatalk 4
mar5hal said:
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
Click to expand...
Click to collapse
Thanks for this information, I appreciate it. I almost entirely forgot about Root Explorer. That was already installed. Crisis averted.
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
Thanks for the advice. I tried this but I don't see any files in the /Cache folder! Any other suggestions?
THANK YOU, sheesh!
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
LIFE saving. Stupid me. That'll teach me to root my phone for particular reason.
A little tip to get Root Browser installed: go through another device to GPlay and install it to your Moto X. During the next loop, it should download, and then install on the following loop. One more pass to enable su privilege, and one more to find the dang file in cache and terminate with prejudice.
Exhale.
mar5hal said:
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
Click to expand...
Click to collapse
the above steps saved my arse, so thank you. I kept letting the update go, but someone used my phone today and said "oops I think I hit update".
Argh....
rockcreek_md said:
LIFE saving. Stupid me. That'll teach me to root my phone for particular reason.
A little tip to get Root Browser installed: go through another device to GPlay and install it to your Moto X. During the next loop, it should download, and then install on the following loop. One more pass to enable su privilege, and one more to find the dang file in cache and terminate with prejudice.
Exhale.
Click to expand...
Click to collapse
I typically use a PC to go to the play store. easy peasy to get anything installed.