[OBSOLETE] Disable OTA update notification - Nexus 7 General

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

Related

OTA Update Issue

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).

Problems getting OTA ICS on Rooted Droid 4

I've looked and I couldn't find a direct solution, so I'm going to give birth to this thread.
Problem: I want (and have problems downloading) the OTA Ice Cream Sandwich update on my rooted Verizon Motorola Droid 4
I rooted my phone awhile back. Just today I received a message that the system update was available.
-I am able to download the update.
-I am able to begin installing the update.
-During the installation process, the yellow progress indication bar fills about 1/8 of the way, then I get the ! warning sign above the little android figure.
Here's what I've done so far to try and correct this problem:
-Restarted my phone
-Restarted my computer
-Downloaded and installed the latest Motorola drivers from the official Motorola website.
-I attempted* to un-root my phone using the Droid 4 Utility 0.4.
--I should note that in the log, there was a like that read:
rm failed for /data/app/com.noshufou.android.su-1.apk, No such file or directory
Click to expand...
Click to collapse
-Restarted my phone again
-Tried installing the update with still no luck
*It appears that all the Droid 4 Utility did was remove Superuser, though I could be wrong. However, if this is the case, I still have a rooted device.
Once again, I'd prefer to have the OTA update, and not a leaked/rooted version of ICS. There's a possibility I didn't unroot my phone all the way. Am I doing this right?
Thanks in advance for the help.
ICS hasn't been officially released for the D4 yet.
This morning when I woke up I received an "Update available" notification. I am able to download an update for my phone. After downloading the update, I receive another notification:
"Install update
Update (6.13.219.en.US) has been downloaded and is ready to install.
Installation will take up to 10 minutes. Upon completion the phone will power off than back on.."
So it absolutely did not occur to you that this is the "219" update which can be found in this (General) section as well as in the Android development section .
Please do take a look in the topics mentioning "update" or "219". You will find topics for rooted and stock phones regarding the 219 update and how to proceed.
Die Bruine said:
So it absolutely did not occur to you that this is the "219" update which can be found in this (General) section as well as in the Android development section .
Please do take a look in the topics mentioning "update" or "219". You will find topics for rooted and stock phones regarding the 219 update and how to proceed.
Click to expand...
Click to collapse
Thanks for your help. I'm slightly inexperienced. I was so excited when I saw the system update that I suspected it to be ICS. Albeit, my hunt continues.
it failed because u altered system files of some kind... its happening to me too. i downloaded the stock system app zip from here in hopes to replace the system apk's so the update will go through but i dont know how to replace the system files... is it as simple as copy and paste, do u have to copy it to the sd card then use a file explorer to copy and overwrite over the files? i dont want to mess something up
I did modify the build file in root/system in order to install a certain APP from the Google Play Store, but I made sure I went and reversed all of the changes I made. Could you please post where you got this file from?
http://forum.xda-developers.com/showthread.php?t=1608866&page=3
Stensin said:
I did modify the build file in root/system in order to install a certain APP from the Google Play Store, but I made sure I went and reversed all of the changes I made. Could you please post where you got this file from?
Click to expand...
Click to collapse
The original post has also been updated with a link to the original files, as well as more complete instructions.
http://forum.xda-developers.com/showthread.php?t=1608866
omniuni said:
The original post has also been updated with a link to the original files, as well as more complete instructions.
http://forum.xda-developers.com/showthread.php?t=1608866
Click to expand...
Click to collapse
but how do u copy those files from NOTE 2? i downloaded the file, extracted the files but i cant copy them to the system folder
copy them to your phone via usb, make sure you are rooted, and CAREFULLY COPY them using a root explorer. You can get a good one from AntTek for free on the Play Store.
I tried that.. copied the files to the sd card. I can see them when i browse the sd card via the computer but when i unplug the cord they arent there anymore. Would replacing the stock boot animation via rom manager have anything to do with the fail?
Sent from my DROID4 using XDA
remember that the "sd card" the computer sees is the phone's internal storage. your actual sd card, as the computer sees it, is referred to by the phone as "sd-ext" or "external sd card" usually.
I did the samething, I changed two files and got help from this forum to get the originals. I use es file explorer in root and copied the files to where they need to be. I checked the permissions and rebulit the checksum for each file. After that I used voodoo to save my root. I rebooted instal from sdcard and it worked. hope this helps.
well it wasnt an app that i deleted.. i was reading somewhere about the build.prop file being messed up from using rom manager so i downloaded a new copy and pasted it over the old one and the update went through! thanks everyone!
Montecarlo97z said:
well it wasnt an app that i deleted.. i was reading somewhere about the build.prop file being messed up from using rom manager so i downloaded a new copy and pasted it over the old one and the update went through! thanks everyone!
Click to expand...
Click to collapse
I tried doing this, but it didn't work. Could you post the build.prop file that you used?
EDIT:
I was copying my build.prop file incorrectly. More details here.

[Script] Removing stupid useless apps from stock

Hi,
When I got my Droid, I couldn't believe all the stuff that came preinstalled with the phone, so I started deleting everything that seemed unnecessary. Given the fact that I already reflashed the phone 20 times in the last week, I made a little script to help me out. I thought I would share it with you in case it comes handy to someone.
BIG NOTE 0: There's a system part that Motorola uses to get stuff from your phone. It's called Data Collector. Whenever any app crashes, it makes quite a big dump, with your network carrier, signal level, applications installed, applications running and a lot of stuff that isn't opt-in. In fact, one of the scripts (/system/bin/bugtogo.sh) can take screenshots of your phone. I don't like being spied, so I tried to remove it all. Cannot be certain though, but I would recommend you to remove, if you like your privacy, at least, the DataCollector apks, and to empty the bugtogo.sh script from /system/bin
BIG NOTE 1: I don't use this phone in the US, so I don't know if I'm breaking part of the CDMA support. It still shows up in every settings and I don't have any reason to think it won't work, but since I can't test it in anything except GSM/UMTS, I can't know it for sure.
BIG NOTE 2: The script will install Apollo (Music Player), Nova Launcher (homescreen replacement), and Cyanogenmod's Gallery app. If you don't want them and want to keep Blur and the default gallery (the script doesn't remove the music player just in case it's needed by some other app), then don't use this script, or modify it as you wish.
BIG NOTE 3: I am not responsible for anything if this causes a mess. Worst case scenario you'll need to flash back the system partition (fastboot flash system system.img), and then reroot your phone. You have been warned.
This is what it removes:
Code:
/system/app/DataCollection.apk
/system/app/DataCollection.odex
/system/app/DataCollectorProvider.apk
/system/app/DataCollectorProvider.odex
/system/app/DataCollectorService.apk
/system/app/DataCollectorService.odex
/system/app/blur-services.apk
/system/app/blur-services.odex
/system/app/blur_facebook.apk
/system/app/blur_facebook.odex
/system/app/blur_flickr.apk
/system/app/blur_flickr.odex
/system/app/blur_kaixin001.apk
/system/app/blur_kaixin001.odex
/system/app/blur_lastfm.apk
/system/app/blur_lastfm.odex
/system/app/blur_orkut.apk
/system/app/blur_orkut.odex
/system/app/blur_photobucket.apk
/system/app/blur_photobucket.odex
/system/app/blur_picasa.apk
/system/app/blur_picasa.odex
/system/app/blur_youtube.apk
/system/app/blur_youtube.odex
/system/app/vzw_vnav_DROID4.apk
/system/app/vzwapnpermission.apk
/system/app/MyVerizon.apk
/system/app/VerizonSSOEngine.apk
/system/app/MotoVzwAtCmdPlugin.apk
/system/app/MotoVzwAtCmdPlugin.odex
/system/app/VzwController.apk
/system/app/VzwController.odex
/system/app/VzwDeviceSetup.apk
/system/app/VzwDeviceSetup.odex
/system/app/VzwEntitlementService.apk
/system/app/VzwEntitlementService.odex
/system/app/VzwPhoneService.apk
/system/app/VzwPhoneService.odex
/system/app/VCast.apk
/system/app/VCastStub.apk
/system/app/VCastTones.apk
/system/app/VCASTVideo.apk
/system/app/VmmGallery.apk
/system/app/com.motorola.android.server.ims.apk
/system/app/com.motorola.android.server.ims.odex
/system/app/com.motorola.android.settings.aplogd.apk
/system/app/com.motorola.android.settings.aplogd.odex
/system/app/VmmBackupManager.apk
/system/app/VmmBackupManager.odex
/system/app/VmmGallery.odex
/system/app/SmartActionFW.apk
/system/app/SmartActionFW.odex
/system/app/SmartActions.apk
/system/app/SmartCarDock.apk
/system/app/SmartDock.apk
/system/app/ZumoService.odex
/system/app/ZumoService.apk
/system/app/WelcomeWebtop.odex
/system/app/WelcomeWebtop.apk
/system/app/WeatherWidget.apk
/system/app/VZWInstaller.apk
/system/app/Vvm.odex
/system/app/Vvm.apk
/system/app/VSuiteApp.apk
/system/app/VRDClient.apk
/system/app/VMMServiceInterface.odex
/system/app/VMMServiceInterface.apk
/system/app/VideoSurf.apk
/system/app/Videos.apk
/system/app/VideoCalling.apk
/system/app/Swype.apk
/system/app/SocialShare.odex
/system/app/SlingBox.apk
/system/app/SocialShare.apk
/system/app/SlackerRadio.apk
/system/app/RichLocationVzW.apk
/system/app/Protips.odex
/system/app/Protips.apk
/system/app/PlusOne.apk
/system/app/PhotoEditor.odex
/system/app/PhotoEditor.apk
/system/app/OnlineAlbum.odex
/system/app/OnlineAlbum.apk
/system/app/NflMobile.apk
/system/app/Netflix.apk
/system/app/MusicStore.apk
/system/app/MotorolaAccountSetup.apk
/system/app/MotorolaAccountSetup.odex
/system/app/MotoEmailConfig.apk
/system/app/MotoDockHelperService.odex
/system/app/MotoDockHelperService.apk
/system/app/MotoConnect.odex
/system/app/MotoConnect.apk
/system/app/MotoCastDashboard.odex
/system/app/MotoCastDashboard.apk
/system/app/motoactv.apk
/system/app/MotMusic.apk
/system/app/MotGallery.apk
/system/app/MCDownloadManager.odex
/system/app/MCDownloadManager.apk
/system/app/Kindle.apk
/system/app/JunosPulsePlaceholder.apk
/system/app/IlsVzW.apk
/system/app/HuxVmmSetting.odex
/system/app/HuxVmmSetting.apk
/system/app/HuxSnCClient.odex
/system/app/HuxSnCClient.apk
/system/app/GuidedTours.apk
/system/app/GuidedTours.odex
/system/app/HelpCenter.apk
/system/app/FileManager.apk
/system/app/FileManager.odex
/system/app/Facebook.apk
/system/app/DockService.odex
/system/app/DockService.apk
/system/app/DlnaSystemService.odex
/system/app/DlnaSystemService.apk
/system/app/DLNA.odex
/system/app/DLNA.apk
/system/app/DemoMode.odex
/system/app/DemoMode.apk
/system/app/ContactIce.odex
/system/app/ContactIce.apk
/system/app/Cmas.odex
/system/app/Cmas.apk
/system/app/BuaContactAdapter.odex
/system/app/BuaContactAdapter.apk
/system/app/BlurUpdater_VZW.odex
/system/app/BlurUpdater_VZW.apk
/system/app/BlurChooser.odex
/system/app/BlurChooser.apk
/system/app/BackupRestoreConfirmation.odex
/system/app/BackupRestoreConfirmation.apk
/system/app/BackupAssistanceClient.odex
/system/app/BackupAssistanceClient.apk
/system/app/ArcVideoEditorLite.apk
/system/app/android-syncservice-app.apk
/system/app/OutOfBox.odex
/system/app/OutOfBox.apk
/system/app/FriendFeed.apk
/system/app/FriendFeed.odex
/system/framework/com.motorola.MCDownloadLibrary.services_lib.jar
/system/framework/com.motorola.MCDownloadLibrary.services_lib.odex
/system/framework/com.motorola.motoconnect_lib.jar
/system/framework/com.motorola.motoconnect_lib.odex
/system/framework/com.motorola.vzw.vmm.helper.jar
/system/framework/com.motorola.vzw.vmm.helper.odex
/system/framework/com.motorola.vzw.vmm.util.jar
/system/framework/com.motorola.vzw.vmm.util.odex
/system/framework/com.scalado.android.photoeditor.jar
/system/framework/com.scalado.caps.jar
/system/framework/com.verizon.phone.jar
/system/framework/com.verizon.phone.odex
/system/framework/com.vzw.android.gex.jar
/system/framework/com.vzw.android.gex.odex
/system/framework/com.vzw.android.hux.jar
/system/framework/com.vzw.android.hux.odex
/system/framework/com.vzw.android.jar
/system/framework/com.vzw.android.odex
/system/framework/com.vzw.android.smart.jar
/system/framework/com.vzw.android.smart.odex
Instructions:
1. Root your phone if you haven't already
2. Install Busybox from Google Play if you haven't already
2. Uncompress the zip into your internal sdcard. You should get this:
Code:
/sdcard/removecrap/Apollo.apk
/sdcard/removecrap/Gallery2.apk
/sdcard/removecrap/com.teslacoilsw.launcher-1.apk
/sdcard/removecrap/remover.sh
3. Run from a terminal on the phone, or from adb (always as root)
sh /sdcard/removecrap/remover.sh
4. Wait until the phone reboots
5. 200 extra Mb of system and a lot more free ram for your apps. Oh, and Motorola won't get another bug report from you
EDIT: Ooops, Reupdated the zip file, it was deleting one extra file (motosignature inside the framework folder)
EDIT2: Didn't catch Carrier IQ's qer binary on /xbin. Unfortunately we can't touch those binaries since they're in the randisk, so I updated the script so it removes the logfile qe generates and replaces it with a folder so it can never write the scan results again (thank you bofh.bug for the links!)
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
highlandsun said:
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Probably OTAs will fail after running the script, but fixing it is as easy as reinstalling the system partition with fastboot and then applying the OTA
Sent from my DROID4 using xda app-developers app
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
arleslie said:
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
Click to expand...
Click to collapse
Were you able to fix the script so it works for CDMA users? Or, do you know what apps breaks it?
Very nice script, thanks. Easy way to run it by using Root Browser: open as script. But as for me QuickPick is better than ICS Galerry
Sent from my DROID4 using xda app-developers app
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Tanzior said:
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Click to expand...
Click to collapse
I did again the script for the jelly bean update. This time it removes less crap, since it seems Motorola left a bit less than on previous versions. This will remove the annoying "Foreign card" warning when you boot the phone with some non-verizon sim, the acoustic warning when you turn up the volume, smart actions and so on.
IT WON'T REMOVE THE APPS. It will leave them here:
Apps: /system/app/oldapps
system binaries: /system/bin/oldbin
Framework: /system/framework/oldframework
If you encounter any problem, you can simply move back the files through adb and the phone will be like before applying the script.
NOTE: Only tested on GSM. Probably won't work on CMDA since it's missing most of the Verizon stuff. If you can identify which apps are needed for CDMA to wokr again tell me and I'll update the script accordingly.
I run the script from ADB and worked like a charm. Been using it for 24hours and no problems so far, but you never know, so use at your own risk
Code:
[email protected]:~/Documents# adb push removecrap2.sh /sdcard/removecrap2.sh
[email protected]:~/Documents# adb shell
[email protected]_maserati:/ $ su
[email protected]_maserati:/ # sh /sdcard/removecrap2.sh
It works great, thank you. Good work.
Sent from my DROID4 using xda app-developers app
Hi to all, i found two app : ModemPanicReporter.apk and ModemStatsService.apk. What they are doing ? Maybe it is necessary to remove they too ? Removing these applications will improve battery life.
Sent from my DROID4 using xda app-developers app

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

Block OTAs? (possible upcoming 4.4.4)

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

Categories

Resources