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
Hi there, I tried to upgrade to ICS OTA, but got locked at the Samsung logo, but thanks to this forum I managed to reflash using Odin and then upgrade using Kies.
The thing is, the space I cleared (about 3 Gb or so) for the files is still in use, I assume by the downloaded files. How can I get rid of these and free up my space again?
Thanks,
Mark
As far as i know, the OTA update files are stored in cache. To get rid of them, go into recovery and select "Clear cache" option, that should do it.
If you're on stock ICS - remember not to use factory reset. Just clear cache.
Alternatively, if you're rooted - you could simply browse to system root, go into /cache and delete those files manually.
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.
Some of my apps, like goldendict and rootexplorer, can't detect my sdcard, but my phone do detect. In fact, poweramp can read and play songs from it. Already tried resintalling those apps. Problem persist.
I'm on stock firmware 4.3 rooted and with doomlord dual recovery
i'm having a similar problem.
it's not like they don't detect it, they don't go there automaticly, whatsapp didn't look for backups there, bsplayer won't load movies from there, apps-backup don't look for backup files on the sdcard.
but if i try to manually tell any of them to go there some of them find it.
strange thing.. didn't happen in 4.2.2, i use iHackers rom 2.0
Did you tried the apps i said? How do i manually them? They don't have this option.
I'm thinking in going back to 4.2 what's the difference between them? Also, i can't mount /system is this a 4.3 problem or 4.2 have it to?
ffp. said:
Did you tried the apps i said? How do i manually them? They don't have this option.
I'm thinking in going back to 4.2 what's the difference between them? Also, i can't mount /system is this a 4.3 problem or 4.2 have it to?
Click to expand...
Click to collapse
4.2 can mount /system as R/W because if you root it, you get full root but currently on locked bootloaders on android 4.3 you get only partial root.
I have root explorer and it can detect my sd card. Are you sure you are going to the right directory? /sdcard1 or /storage/sdcard1
Regards,
~J2C
But i have unlocked bootloader, what i got wrong? And you don't understand, root explorer don't even open. Goldendict open and says that i have no sdcard, then it closes...
SOLVED!! I just disabled Xprivacy from xposed and now everything works. I didn't configured yet, so it may work. I'll try to enable and configure it to have both working.
Shteren, do you use xprivacy too?