Heya guys. I couldn't find much info on this for the X, and certainly not anything about this particular update.
I'm not too fond of jumping on board a new ship before I get a good look at it.
Has anyone before successfully blocked an incoming OTA update? I'm particularly interested in VZW moto Xs, though any info is helpful.
In a nutshell, I'm aiming to block the 4.4.4 OTA on a non-dev, non-rooted VZW moto X.
I'm sure it may not be possible without root, but I'm interested in opinions.
Just hit no when it tells you havê a new update
Sent from my XT1058 using XDA Free mobile app
chrisp6825 said:
Heya guys. I couldn't find much info on this for the X, and certainly not anything about this particular update.
I'm not too fond of jumping on board a new ship before I get a good look at it.
Has anyone before successfully blocked an incoming OTA update? I'm particularly interested in VZW moto Xs, though any info is helpful.
In a nutshell, I'm aiming to block the 4.4.4 OTA on a non-dev, non-rooted VZW moto X.
I'm sure it may not be possible without root, but I'm interested in opinions.
Click to expand...
Click to collapse
using titanium backup or some program like it just freeze Motorola ota that should stop all ota notifications
kelvinmorcillo said:
Just hit no when it tells you havê a new update
Click to expand...
Click to collapse
Ah, I wasn't aware OTAs on this phone were optional. Some devices force them ASAP on a boot-up if available. Good to hear, and I hope it stays true.
adm1jtg said:
using titanium backup or some program like it just freeze Motorola ota that should stop all ota notifications
Click to expand...
Click to collapse
I'm not able to do this. Otherwise, I would. Root free, dev free, that's the life for me... for the time being at least...
chrisp6825 said:
Ah, I wasn't aware OTAs on this phone were optional. Some devices force them ASAP on a boot-up if available. Good to hear, and I hope it stays true.
I'm not able to do this. Otherwise, I would. Root free, dev free, that's the life for me... for the time being at least...
Click to expand...
Click to collapse
To stop the updates, this will do it but you will have to redo this everytime you reboot until you are rooted in stone not temp like Pie.. but this will stop any updates from coming to the phone and stop you from forcing an update. the two files Ive changed the name of the first two in the pic, it's the root / system / pri apps folder, I added .bak to the name, you have to do both of them.
If you don't rename them after every boot when you lose Pie they revert back to original and you will get the notice again and you might accidentally hit install when the notice pops up.. so just re Pie and change them.. I use FX explorer with root addon. It's a great app and free and takes less than a minute to rename the files.
Looks like the OTA reached me. It creates a permanent notification from the MotoOTA app.
Without write-protection enabled, you can't disable this app permanently. Most likely in a temp-root instance, freezing it in titanium backup may not take effect on the app til reboot, or possibly a hot-reboot.
I just un-enabled notifications for the app, though I'm hoping it won't auto download during idle.
And apparently (I'm) not able to freeze it. See screen shots.
tapa'd on my moto x
chrisp6825 said:
Looks like the OTA reached me. It creates a permanent notification from the MotoOTA app.
Without write-protection enabled, you can't disable this app permanently. Most likely in a temp-root instance, freezing it in titanium backup may not take effect on the app til reboot, or possibly a hot-reboot.
I just un-enabled notifications for the app, though I'm hoping it won't auto download during idle.
And apparently (I'm) not able to freeze it. See screen shots.
tapa'd on my moto x
Click to expand...
Click to collapse
It won't install automatically...almost guaranteed.
But why can't you freeze it? You should be able to click it, opening up a menu with a freeze option. My guess is that it will revert back to 'unfrozen' after the next reboot, but I HAVE seen a post or two that suggests otherwise (not sure how reputable, if at all).
I have several system apps frozen (mostly the google play music/movies/games/etc. bloat, along with a couple others). The fact that it is red just indicates it is a system app. You might have to mount /system r/w in order to be able to freeze it, but once again, I've read some posts suggesting that mounting r/w was tricky with the temp-root (and of course, will revert all changes upon reboot).
I would give you more definitive answers, but since I'm unlocked, its difficult for me to test...
Good Luck! If you can just put up with the nag, you'll be fine. As you well know, once you accept it, it's game-over for root.
Chris forget about that freeze crap do what I said to do and you won't have any issues I did it yesterday.. rebooted the phone lost towelpie got the 4.4.4 notice started downloading because wanted to know what it was.. than ran towelpie, went to a root/system/priv-apps and deleted the 3c ota files and it stopped that download as it was downloading. i wanted to download it to see what it was so i had to reboot the phone to get rid of towelpie and that got the 3c ota files back and then it rebegan the download I don't use Titanium Backup I just manually delete. I did it Verizon 4.4.2 non dev locked boot
now after I downloaded 4.4.4 and rooted with towelPie.. it did cause the root to act kind of funny I went into FX root explorer tried to rename the 3c ota files after mounting Fx Explorer in write mode it still told me the files were not writable that must have had something to do with the new download.. so my corrective action was to go into fx root explorer cashe folder send that new update into outerfreakin space then reboot the phone retowelpie and then mount fx Explorer in write mode again and deleted 3c ota files and had no problem after rebooting.. but once you download that file it permanently does something to your phone until you delete it from the cashe folder and reboot.
samwathegreat said:
It won't install automatically...almost guaranteed.
But why can't you freeze it?
Click to expand...
Click to collapse
In that screen shot, I had just attempted to freeze it 3 times. It's as if I haven't even tried though.
As long as it won't auto download, I'm cool with it. Kit Kat or jelly bean introduced the option to disable notifications from apps, so that gets it out of my way.
tapa'd on my moto x
Once you delete the 3c_ota.apk and 3c_ota.odex files your phone is NOT capable of checking for or downloading an OTA.
And towelPie root allows you to delete these files if you use FX explorer with root add-on, its available in playstore, and explains how to mount in write mode allowing you to rename or delete any file, it takes all of 10 seconds.
FX file explorer
https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
Root add-on for for FX explorer to access root files
https://play.google.com/store/apps/details?id=nextapp.fx.rr&hl=en
Right, but this is something that obviously has to be done every boot, and I imagine may need to be soft-rebooted after to take effect, so the app won't load during boot.
I may do that our write a quick script to take care of it each rooted boot for me in a while. Thanks for the info
tapa'd on my moto x
So I just renamed the system files... So much for not trying to auto update. Then next screen after I hit later asked me to select a time of day for the next reminder.
Silly.
I'll see if I still get this after the files are renamed.
tapa'd on my moto x
Renamed my files. So far, no notification. Thx.
chrisp6825 said:
So I just renamed the system files... So much for not trying to auto update. Then next screen after I hit later asked me to select a time of day for the next reminder.
Silly.
I'll see if I still get this after the files are renamed.
tapa'd on my moto x
Click to expand...
Click to collapse
you have to go into system root cashe folder and send the downloaded file to kingdome come than you wont get the install prompt. the phone is not capable of downloading the update if you rename the files
the file in cashe is that the Verizon ghost zip?delete then re name the other ota in priv folder?
Thanks
gmmurphy said:
the file in cashe is that the Verizon ghost zip?delete then re name the other ota in priv folder?
Thanks
Click to expand...
Click to collapse
that is it. either delete it, rename it, or move someplace else (like /sdcard)
I froze MotorolaOTA 1.0 in Titanium Backup using Towel Root. (Also works using Pie Root). Blocks of obedience obnoxious update requests.
Sent from my Nexus 7
Related
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
u need to rsd the swu.zip in order to get the update
OK, where can I get the swu.zip?
lacesout said:
OK, where can I get the swu.zip?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
mrcastillo said:
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
Click to expand...
Click to collapse
Thank you, this work!
lacesout said:
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
Click to expand...
Click to collapse
lacesout, had the same experience. Used one-click method to root, then used psouza4's bloat script to remove, then restore apps when the update became available. These were my only mods. Went to /system/app and all app's are back with the proper apk extension. Update downloads fine, then hangs at 1/4 to 1/3 of install. Anyone else with similar experience or thoughts as to what's hanging the OTA install?
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
nu2droid said:
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the reply and the tip on root explorer, it's an elegant tool, more intuitive to use than the freeware apps.
All the file extensions in /system/app are either .apk or .odex with the exception of Fota.apk.bak, and Fota.odex.bak. As the first time I heard of nandroid was your post, I unfortunately didn't use it, so I don't know if these were the extensions before I used psouza's bloat removal script. Fota was not on the list of scripts to remove/rename in his original post.
As Fota is the "firmware over the air" app, it is suspicious that it's the only one with a .bak ext. I am using root explorer to rename both, removing the .bak, and then will attempt another update.
Success! "Your phone has been upgraded to 5.6.890.en US version". Have lost root, at least for the moment. Will deal with that tomorrow. Last thing to do before going to bed is find the "Thanks" button. Thanks for setting me on the right path. P.
Unable to root after OTA to .890
One click root not longer works. After clicking "run_to_root_your_droid3.sh" on PC (Ubuntu 10.04) I get no prompts on screen, but phone does reboot twice. No su privileges after boot. Busybox is installed in /system/xbin and there is nothing I can do about it as I can't mount r/w. Using Root Explorer and Script Manager as tools.
I realize I'm going to have to increase my learning curve here. Would appreciate any links to relative threads on this topic, or suggestions on what to try next (I have searched, but need some direction).
I ... may have bricked my Droid 4. I won't go into details unless somebody asks, but I don't think it's necessary. I AM able to get to the recovery mode though, I just have nothing to recover from.... I misplaced my back-up.
So, I need SOMETHING to flash my phone to. 4.0/2.0/I don't care, I just need any rom/SBF to make this bad boy boot again. Anybody have anything?
I saw and downloaded the first thing that shows up when you google "droid-4-system-dump-wallpapers-ringtones.html" (link doesn't work because I'm new) But, I was unable to make anything of it.... What do I do?
Just to help others avoid the same fate can you please let us all know what you did?
zeroibis said:
Just to help others avoid the same fate can you please let us all know what you did?
Click to expand...
Click to collapse
Well, in hindsight it was kind of dumb. I rooted it, and began to remove all of the VZW sponsored apps. Once I did that, it cleared out a lot of memory (storage AND ram) but seemed to come with the downside of preventing my "settings" activity opening up. As in, whenever I hit "menu" then "Settings" from the main launcher, it would force close behind the scenes (logcat showed the stack trace for the settings activity).
I spent the next day trying to fix that issue, copying "settings.apk" from that link I mentioned earlier to my root director, but that didn't fix it. So, I went and tried copying entire folders over. This is the embarrassing part... I hit a 'delete' button on the "system/apps" folder, got about 30 force close windows, and am now stuck in a bootloop.
Doing the "power + both volume buttons" still gives me the recovery menu, but I don't have anything to recover to, as I was stupid and didn't think to make a backup.
Dwebtron said:
Well, in hindsight it was kind of dumb. I rooted it, and began to remove all of the VZW sponsored apps. Once I did that, it cleared out a lot of memory (storage AND ram) but seemed to come with the downside of preventing my "settings" activity opening up. As in, whenever I hit "menu" then "Settings" from the main launcher, it would force close behind the scenes (logcat showed the stack trace for the settings activity).
I spent the next day trying to fix that issue, copying "settings.apk" from that link I mentioned earlier to my root director, but that didn't fix it. So, I went and tried copying entire folders over. This is the embarrassing part... I hit a 'delete' button on the "system/apps" folder, got about 30 force close windows, and am now stuck in a bootloop.
Doing the "power + both volume buttons" still gives me the recovery menu, but I don't have anything to recover to, as I was stupid and didn't think to make a backup.
Click to expand...
Click to collapse
No files are floating around at this time. You really screwed yourself over on this one. Go back to Verizon and beg. You chose to void your warranty.
Dwebtron said:
Well, in hindsight it was kind of dumb. I rooted it, and began to remove all of the VZW sponsored apps. Once I did that, it cleared out a lot of memory (storage AND ram) but seemed to come with the downside of preventing my "settings" activity opening up. As in, whenever I hit "menu" then "Settings" from the main launcher, it would force close behind the scenes (logcat showed the stack trace for the settings activity).
I spent the next day trying to fix that issue, copying "settings.apk" from that link I mentioned earlier to my root director, but that didn't fix it. So, I went and tried copying entire folders over. This is the embarrassing part... I hit a 'delete' button on the "system/apps" folder, got about 30 force close windows, and am now stuck in a bootloop.
Doing the "power + both volume buttons" still gives me the recovery menu, but I don't have anything to recover to, as I was stupid and didn't think to make a backup.
Click to expand...
Click to collapse
I'm curious about this too - I deleted a bunch of vzw garbage. I did make a copy of of everything with titanium backup first but when I tried re-installing one of them it just hung while another re-installed fine.
I had a similar issue with one app - I had to go into /system/app and change it form RO to RW. Once Read/Write was enabled, Titanium was able to restore the app.
I have been playing it safe and only freezing the apps, not deleting them. I have had no FC or any odd behavior. I figured with an allocated 3 gb to applications, at this time gaining an extra 100MB of storage space is superfluous...especially with no SBF available.
As mentioned above, try going to the VZW store and getting an exchange. I'm certain an .sbf will be released at some point but it could be weeks/months before that happens.
And for future reference/anyone else reading this thread...never delete system apps! Just freeze them. Yes they will still be taking up space, but they won't be using any memory and they won't show up in your launcher so it's basically the same thing...except with freezing it is 100% reversible and will still allow you to receive updates.
Can someone upload these files from D4:
/system/build.prop
/system/default.prop
Freeze Apps
SGMD1 said:
As mentioned above, try going to the VZW store and getting an exchange. I'm certain an .sbf will be released at some point but it could be weeks/months before that happens.
And for future reference/anyone else reading this thread...never delete system apps! Just freeze them. Yes they will still be taking up space, but they won't be using any memory and they won't show up in your launcher so it's basically the same thing...except with freezing it is 100% reversible and will still allow you to receive updates.
Click to expand...
Click to collapse
What is the best way to freeze apps? I know you can do this with Titanium Backup. Do you need the pro version in order to do this? Are there other apps out there that also allow you to freeze apps?
kwyrt said:
What is the best way to freeze apps? I know you can do this with Titanium Backup. Do you need the pro version in order to do this? Are there other apps out there that also allow you to freeze apps?
Click to expand...
Click to collapse
You do need the Pro version of Titanium Backup to freeze apps I believe. There are free apps that will do it (i.e. Bloatware Killer) but I am not really familiar with them.
Skrilax_CZ said:
Can someone upload these files from D4:
/system/build.prop
/system/default.prop
Click to expand...
Click to collapse
http://db.tt/LymDelkf
That zip contains the 2 files you asked for. Anything else you need just ask and I can pull it for you. I havent done a dd of all the partitons yet but will be doing that as soon as I can.
cellzealot said:
That zip contains the 2 files you asked for. Anything else you need just ask and I can pull it for you. I havent done a dd of all the partitons yet but will be doing that as soon as I can.
Click to expand...
Click to collapse
The link that I was referring to in the first post SHOULD have every file from the D4.
I meant if he needed any of the other partitions besides the system.
I wanted to give him exactly what he asked for because he is avery sharp guy who may help us out with this device.
Unfortunately I did the same (though not as bad...I just can't open any of my contacts). I changed the permissions for /system/apps but I still am hanging at restoring in Titanium Backup. Are there any other directories that should have changed permissions to get some of these apps restored?
Also, lesson learned....freeze no uninstall
mattlgroff said:
No files are floating around at this time. You really screwed yourself over on this one. Go back to Verizon and beg. You chose to void your warranty.
Click to expand...
Click to collapse
Yeah so what? Why do people feel the need to post condescending comments for no reason? Its because of mistakes and screwups that the community progresses. There will be files floating around by the weekend, I'm sure.
I'm in the same boat... I bricked by droid 4... now waiting for a sbf file... someone said go to vzw and beg... has anyone ever tried that, after bricking your phone? what did you say? and did it work?
I'm just trying to figure out how to get vzw to replace this phone.
---------- Post added at 09:05 PM ---------- Previous post was at 08:56 PM ----------
reigndropz said:
Yeah so what? Why do people feel the need to post condescending comments for no reason? Its because of mistakes and screwups that the community progresses. There will be files floating around by the weekend, I'm sure.
Click to expand...
Click to collapse
The files will be released by the weekend? YAY... how do you know?
Also what does it take/what has to be done for someone to release these sbf files?
jgardner said:
Unfortunately I did the same (though not as bad...I just can't open any of my contacts). I changed the permissions for /system/apps but I still am hanging at restoring in Titanium Backup. Are there any other directories that should have changed permissions to get some of these apps restored?
Also, lesson learned....freeze no uninstall
Click to expand...
Click to collapse
That's the only path I had to change. Do you recall if you happened to have moved an app to a different path (perhaps to the sd-card) then removed it?
Are there multiple apps you are trying to restore? If so, have you tried restoring them one at a time?
im going to wait for the sbf files before any major modifications to my phone, then we can all start the fun
i just froze apps to prevent them from running, im not worried about space since i put in a 32GB SD card
I think it's very wise to wait for the firmware to be released, but it's worth noting that the term SBF is a mistaken reference to the old format for firmware files and that all dual core Motorolas have fastboot support now and RSD Lite has been modified to support this and uses xml.zip files that are sets of signed images rather than the Single Binary File(SBF).
This is a very important distinction to be made as the new format and boot menu provide many more options for controlling the flash process for the end user and it is ultimately much safer and more flexible.
When an OTA update becomes available, there is a recurrent notification prompting to upgrade.
The below method tricks the OS into thinking that it is already at the latest version, in effect stopping the update notification from appearing.
I am not responsible for anything you do with your device.
Pre-requisite
Device must be rooted
Steps
Download FOTAKill apk
Put the apk in "/system/app"
Set proper file permissions (644, or rw-r--r--) for the apk
Clear "/cache" (e.g. boot into CWM and clear cache)
Reboot
Check "Settings > About tablet > System updates" and it should show "up to date" now.
Note that after rebooting there may still be a notification to update, after clearing no further notification will appear.
Rollback
To re-enable OTA update notification, delete the apk and reboot!
iamelton said:
lately since Android 4.2 OTA update became available for my device, there was a recurrent update notification prompting me to update..
as i dont want to upgrade yet due to app incompatibility issues not being resolved, i asked for help and was given a solution after searching and reading some posts..
it worked for me and i would like to share it here as i found that there were other users looking for a solution like i did..
ur device needs to be rooted to follow the steps below..
steps:
(1) download FOTAKill (firmware over-the-air kill) apk
(2) put the apk in "/system/app" with a file explorer
(3) set proper file permissions (644) for the apk
(4) clear "/cache" (i booted into CWM and cleared cache there)
(5) reboot
(6) check "Settings > About tablet > System updates".. should tell you "up to date" now..
note that after rebooting i still got a notification on update, but after clearing it there was no further notification since then..
Click to expand...
Click to collapse
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date
Worked great, better than messing around with Google services framework.
Another possibility to get rid of OTA updates reminders on 4.1.2:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
OR... download Autorun manager from the Play store and disable the following in Services( must enable system settings in preferences)
Receiver com.google.android.gsf.update.SystemUpdateService
Requires root access
wilx said:
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date
Click to expand...
Click to collapse
Same here thank you iamelton!
andro54 said:
Same here thank you iamelton!
Click to expand...
Click to collapse
Same here didn't need to clear cache. The whole thing took about 30 seconds.
Thank you
Sent from my Nexus 7 using xda app-developers app
the clear cache part is for those who might have already downloaded the update package file (which is about 80MB) by the ota service.. it removes this file and frees up some cache space..
What does FOTAkill actually do to your system?
Sent from my Nexus 7 using Tapatalk 2
ExploreMN said:
What does FOTAkill actually do to your system?
Click to expand...
Click to collapse
That's a GREAT question.
iamelton do you know the specifics? It would also be interesting to know what permission if any are effected with this method.
Sent from my Nexus 7 using xda app-developers app
sorry but i have no idea what it actually does to the system, apart from the obvious function of stopping the OTA service..
from this page, it requires the following permissions..
Code:
android.permission.RECEIVE_BOOT_COMPLETED
com.google.android.providers.gsf.permission.WRITE_GSERVICES
com.google.android.providers.gsf.permission.READ_GSERVICES
It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.
datorprofessor said:
It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.
Click to expand...
Click to collapse
afaik it should stop any future OTA updates regardless of android versions..
and granting permission 755 is more than the needed 644, but that does no harm..
i thought 4.2 was the version with multi-user support, but then im not on 4.2 yet so cant tell much about it..
What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app
gelhack said:
What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i think removing the apk from /system/app/ should allow OTA notifications to show again, though i have not tried it yet..
btw, we have the same reason as why not to upgrade..
I used this from other thread, forgot where it is.
"Install Autostarts app.
Go to "After Startup"
Scroll down until you see "Google Services Framework"
There should be several of them. For me it was the third one. Touch it and read the bottom of the popup to find out. It will say "Receiver com.google.android.gsf.update.SystemUpdateService. ....(you get the point)
Disable it. Done..."
Peaceful on 4.1.2.
There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
helloterence said:
There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
Click to expand...
Click to collapse
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..
iamelton said:
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..
Click to expand...
Click to collapse
Nope. I'm still on 4.1.2 and haven't gotten any notification about 4.2.1.
I'm assuming that updates to 4.2 and 4.2.1 are incremental, and as such you couldn't install or get a notification for 4.2.1 until you installed 4.2. So any method that stopped 4.2 notices would also stop 4.2.1 notices.
Sent from my Nexus 7 using xda app-developers app
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Version 7.3.0 is out. Here are the specs from the Amazon page:
"Support for X-Ray for Textbooks
Explore the “bones” of your textbook, and access all the most important terms and concepts, with glossary definitions and links to relevant textbook pages.
Simplified Chinese Support
In addition to the other languages offered, you can now change your device language to Simplified Chinese.
Track your reading progress with Time To Read
Kindle Fire HD 7” calculates your reading speed to let you know when you’ll finish a chapter or book.
Support for Kindle Editions with Audio/Video
You can now read books that contain audio and/or video clips.
Print Replica Textbook Enhancements
Scroll through thumbnails at the bottom of the screen to preview pages and jump quickly between chapters, and mark important notes and highlights in your Notebook for easy reference."
None of this seems overly important, but then again I do like to have the latest version as long as there is no harm to the root.
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Anything you install as a system apk will be deleted. When amazon sends an update it typically sends system.img, recovery.img and boot.img.
That is why the lmt launcher will not work because it has to be installed as a system.apk to work, same with root access since su binary is placed within the system files.
if you want to install the 2nd bootloader, you should not update. Amazon have fixed the bootloade with the update and so it dosn't work for now. i don't know, if it perhaps work with soupkit, because the insallation is a little bit different, but the resultat is the same (I could install kinelogy 1.1 after doing that).
I'm still on 7.2.1, found Wi-Fi performance/range considerably better than on 7.2.3, unless 7.3.0 improves it I won't be updating for quite some time.
This explains why I lost root and Go Launcher HD yesterday. Regained root with the same Noob Simple guide here with little more than annoyance. The file to prevent the OTA update had been moved per the guide (otacerts.zip) but think I deleted it in a cache cleaning frenzy... that will learn me
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
EDIT: OK, I was able to re-root the same way I did before (used the tools in prokennexusa noob threads!) All back to normal!
markbc01 said:
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
Click to expand...
Click to collapse
Same root method worked, system feels about the same with tweaks installed and benchmarked similarly (7344 vs 7444 with AnTuTu)
I just can't get my launcher off of the stock one. Nothing will take.
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
macbranson said:
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
Click to expand...
Click to collapse
Which method did you use to root again ?
Nop update here istill in 7.2.3
Damn just got the damn update like 5 min go
Sent from my Nexus 7 using Tapatalk 2
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
geeibara said:
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
Click to expand...
Click to collapse
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
quan_1986 said:
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
Click to expand...
Click to collapse
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
geeibara said:
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
Click to expand...
Click to collapse
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
#3Clara said:
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
Click to expand...
Click to collapse
haha yah I noticed that too, I had files like appappappappappappapplauncher lol. Thanks this helped a lot
modmyphone said:
I just can't get my launcher off of the stock one. Nothing will take.
Click to expand...
Click to collapse
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Gah.. I actually tried to deactivating the manual update and some how the update still pushed through.. which really sucks cause I hard my set up perfect..hope all I have to do is reroot.. ..all that time spend for nothing
Sent from my KFTT using xda app-developers app
BmanCV-60 said:
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Click to expand...
Click to collapse
Actually, I tried 3 different ways.
1) I reluctantly attempted ProKennexusa's method via the KFFFirstAide tool. I say reluctantly since I'm pretty much a Nova snob. I guess luckily for me, it wouldn't take.
2) I then moved onto downloading Nova from the store. The store claimed that both installs went good, but had no option to change my launcher. Upon inspection, the Nova launcher file was nowhere to be found on the device. The pro unlocker could be found, but no the launcher.
3) Since I had a couple of older copies in Dropbox, I figured I'd try those. Usually I could install straight from Dropbox. Not last night. I could launch the install, but the Kindle wouldn't allow me to press the install button. I then just saved the file to the device and still couldn't get it to install. It wasn't until moving it to system/app that I was able to actually install it. But still, no option to set it as my launcher.
This morning, in a bit of Kindle rage, I literally rebooted the device 23 straight times pausing between boots to see what happened. On the 23rd reboot, it finally asked me which launcher to set as default. So now I finally have gotten away from the freakish kindle launcher and am back at home with Nova.
Just got my Verizon MotoMaker Moto X in, rooted it, and am trying to remove the ****-ton of horrible, bloated system apps.
Unfortunately, it seems like every time I delete the .apk's from /system/app (using root adb or TitatiumBackup) the damn things come right back after reboot.
Is there some backup directory copies of the .apk's are stored in to get restored?
I seriously need to figure out how to zap these apps, or I am just going to send this phone right back - I'm not paying $400 for a device that is completely compromised right from the start.
PityOnU said:
Just got my Verizon MotoMaker Moto X in, rooted it, and am trying to remove the ****-ton of horrible, bloated system apps.
Unfortunately, it seems like every time I delete the .apk's from /system/app (using root adb or TitatiumBackup) the damn things come right back after reboot.
Is there some backup directory copies of the .apk's are stored in to get restored?
I seriously need to figure out how to zap these apps, or I am just going to send this phone right back - I'm not paying $400 for a device that is completely compromised right from the start.
Click to expand...
Click to collapse
Has nothing to do with the phone , its an issue with your root method slapmymoto, you need to have the system set as r/w AFAIK
Sent on my Moto X
flashallthetime said:
Has nothing to do with the phone , its an issue with your root method slapmymoto, you need to have the system set as r/w AFAIK
Sent on my Moto X
Click to expand...
Click to collapse
I've been lying in bed, staring at the ceiling, thinking the same thing. Gave up on sleeping, so now I'll have another run at this.
Figure I'll flash back to 4.2.2 and follow the steps to upgrade to 4.4 and then root. Hopefully I will have better luck.
PityOnU said:
Just got my Verizon MotoMaker Moto X in, rooted it, and am trying to remove the ****-ton of horrible, bloated system apps.
Unfortunately, it seems like every time I delete the .apk's from /system/app (using root adb or TitatiumBackup) the damn things come right back after reboot.
Is there some backup directory copies of the .apk's are stored in to get restored?
I seriously need to figure out how to zap these apps, or I am just going to send this phone right back - I'm not paying $400 for a device that is completely compromised right from the start.
Click to expand...
Click to collapse
You need to make sure you are in r/w mode. Reboot to recovery first.
mjphillips1981 said:
You need to make sure you are in r/w mode. Reboot to recovery first.
Click to expand...
Click to collapse
This was the issue. This is my first experience with a firmware lock on a file system. Now I know!
Thanks for the help all!