Standard Disclaimer... your device, your brains, your hands, your responsibility!
1. Those on pure stock rom without root can skip to step 4
2. Ask yourself if you want to unroot and reflash to bloated VZ rom.
3. Get back to stock. Multiple methods exist, I found using the program found in the below posting to be the easiest.
Many thanks to vabeachfc3s!
http://forum.xda-developers.com/showthread.php?t=1743939
http://db.tt/HTJRnSyl download link
4. Force OTA update. There seem to be a dozen variations on HOW to trigger the OTA. The below instructions are from my own successful experiences with the five Nexi my family members have. If followed correctly it should work.
Make sure your Wi-Fi is OFF; your network data is ON. This means you should see signal bars AND the signal descriptor (3g, 4g)
Go to settings>apps and select the ALL category. Find and select Google services framework. Force stop then data/cache.
Back out to your settings. Select About Phone at the very bottom. Go to system updates. You should now see a "last update 12/31/1969" if done correctly. Select check now.
You should now see a notification about the system update being available only thru Wi-Fi. Pull down system tray, select options, and turn on Wi-Fi.
Go back to the settings>about phone>system update option. With Wi-Fi enabled, you should now see horizontal progress meter filling.
The update should complete downloading and you will be prompted to install now.
Done. Feel free to add your own experience with this method. After hearing about the release of the official rom from Verizon I tried the framework trick fifty times without success. I determined that although Wi-Fi was needed to download the update, it should be enabled after clearing the framework and checking for system update under normal network conditions. Some other postings online are stating that the mobile data connection must be disabled to be prompted for the OTA. I have found the data connection must be enabled. I hope one of the methods out there works for you. I've played with many many roms (BAMF, Viscious, JBSourcery, CM10) but I still love the simple, smooth feel of the new update.
All I did was clear the framework and then checked for updates. I did not make any other changes at all and it updated just fine.
Related
I jump between roms pretty often (new features and capabilities are often a siren-call for me) so I wind up reloading and reconfiguring apps pretty frequently. I had a few roms in the past that automatically reloaded all my apps after I installed the rom. I think they required me to sign into the Android Market, and thereafter the applications started popping up by themselves in the app list without my intervention at all.
This feature is absolute extract of awesomeness, but I don't know how it is referenced. What do you call that? Also, I haven't seen it in some time (since February or so) and I've used probably a dozen roms since then; is it no longer a working process?
Maybe because you're not clearing data? Idk, shot in the dark
Posted by some phone named the Epic.
It's a feature of Gingerbread that some have incorporated into their ROMS in the past.
Its because everyone disables their setup wizard... if that was enabled or even optional, it would download all your apps back for you... before you load the rom, go into the zip, go to the build prop and go to the bottom, then change setup wizard from "DISABLED" to "OPTIONAL".
BThomas22x said:
Its because everyone disables their setup wizard... if that was enabled or even optional, it would download all your apps back for you... before you load the rom, go into the zip, go to the build prop and go to the bottom, then change setup wizard from "DISABLED" to "OPTIONAL".
Click to expand...
Click to collapse
I'll give this a try.
RESULT: My most recent rom has the setup wizard enabled, and it didn't reload the apps. If the initial "Touch the Android to begin" setup wizard is the one you're talking about, I've run through it on several roms and not gotten an automated app reload.
It will usually, but its not instant. It actually takes about an hour... and it will only reinstall apps that the online market recognizes your phone as having had installed
Sent from my SPH-D700 using XDA App
I know... it's tethering, not teething, lol.
SHG-I747 AT&T
Installed JB 4.1.1 via Kies
Installed CW Recovery - pulled batter - installed Team Epic Root
All Good
Installed Titanium Backup Pro
Uninstalled Tethering Provision (to disable check for AT&T Tethering Plan)
Unisntalled Bloatware per list in first post of this thread: http://forum.xda-developers.com/showthread.php?t=1728126
Not realizing the Tethering toggle was built-in to Settings > Advanced > Tethering I downloaded WiFi Tethering for Root, wouldn't show up on network selecting Auto and S3 profiles.
Try a couple others (supposedly not requiring root), one crashed "stopped working" when launching but SSID showed up on network and blue tether icon showed up in status bar. Another launched without crashing, blue icon in status bar. Both I can connect to via my Windoes 8 computer but get a status of "Limited" with no Internet access. Apps on phone show the computer is connected.
Here's the major problem. If I just uninstall all the tethering apps and go into Settings > Advanced > Tethering and try to toggle wifi or USB tethering the settings app itself crashes "settings app has stopped working"
I did a TB backup of the apps prior to all this, but then did another TB backup late last night. So that tethering provisioning things can't restored as it appears, at least default, the TB backup overwrites the previous backup instead of making an incremental backup.
I'm at a loss what to do. This is my first Android device. The Sys Admin gut in me says I need to start from scratch (reinstall stock ROM, reinstall CW recovery.. bla bla bla.) But not sure how to even do that (can I even use Kies now that CW recovery is on there or do I need to find the stock rom file and copy to the internal memory and use CW recovery or use Odin to flash stock ROM - hoping I don't need to reflash ROM, will take forever to reinstall my apps and settings in trying to solve Tether crash!)
In desperate need of some advice.
Soultion is a newer hacked version of Wifi Tether for Rooted user that is not on the Play Store and the apk has to be downloaded directly. Current version is here:
http://www.androidfilehost.com/?fid=9390195663897100406
YouTube Video on it here:
http://www.youtube.com/watch?v=ztsZH6Xj7A0
What a pain in the ass it took to finally find this. The problem is all the posts and methods out there essentially became defunct when the JB 4.1.1 update came out a few days ago yet you still have users unknowingly recommending the same methods because they were still on ICS. Guess that's the price you pay when you are brand new to Android and an OS update comes out two weeks after you got your phone and you install it the day it comes out. Sigh.
Ugh. Got too excited too quick. You can't toggle Wifi back on after shutting down tethering without restarting phone! Guess it's going to be a few more days until some good developers come out with a simple one-app solution without issues. It was WAY easier to get free tethering on the jailbroken iPhone that this. I'm shocked this is so hard right now on Android JB 4.1.1. But I have to remember the OS update just came out.
Not getting notifications like you're suppose to?
I've recently talked to T-mobile about this issue and they directed me to do a few simple steps. I was amazed how easy it was.
How do you know that you have the problem? Well certain apps; such as, Facebook, Snapchat, Twitter, and Instagram, are supposed to send notifications notifying you that something has happened (a photo of yours was liked, you have a new tweet, etc.).
WHAT IS IT: Some people receive notifications late or they may not even get any. I'm here today to tell you how to fix that.
CAUSE: The T-mobile representative told me a common cause of the notification issue. If you clear your cache (of applications) daily, or on a normal basis, it can cause increase traffic for your notifications. Not sure if that's right or not, but I was clearing cache every night so it was just a big coincidence that he said that.
Warning: I am not responsible for any damage to your phone. Please read carefully and then do the steps correctly afterwards. These steps were tested on my phone (model: M919) , and my brother's S4 (which is also the same model). Both are UVUAMDL models.
If you have any questions, please ask.
HOW TO FIX IT:
This does not take away root, your custom recovery, or your custom recovery.
One common fix, that doesn't work for everyone is to install the app through the playstore and to not restore it using titanium backup. This didn't work for me unfortunately, but you can try to clear data,cache, and force stopping it to see if that'll work before you do this. Also, try to uninstall it and reinstalling the applications. These are some solutions I found while I was researching how to fix it. None of those worked for me. So here's my method.
(1) Back up all of your internal storage somewhere safe.
(2) Go to settings.
(3) Click on the "Accounts" tab.
(4) Scroll all the way down to "Backup and reset" and click it.
(5) Make sure "Back up my data" and "Automatic restore" is checked.
(6) Click on "Factory data reset". This will reset all setting and delete all of your apps and data on your device. That's why backing up is step #1.
(7) Click "Reset device".
(8) Click "Delete all".
(9) Your phone should reboot by itself and the boot up time should be around 3 to 5 minutes.
(10) Leave your phone to rest for about 2-3 minutes. It should feel like you just brought the phone, leaving you to set up your personal accounts and such.
(11 ~ OPTIONAL) I flashed the original T-mobile kernel, since I was previously running ktoonsez kernel. I just did it because I wanted it completely stock with root.
IMPORTANT: not restore your previous applications until 24 hours have gone by. That means, un-checking the resotre option in the set up. Although, you can download and install a few apps on the playstore to see if notifications are working.
Also: If you're having bad battery life, do these steps. Pay CLOSE attention to the apps you install on your phone. I know that my battery increased by doing the steps above. I only restored the apps I needed and used from titanium backup!
Hey just wanted to say this helped fix my facebook notification and snapchat issue thanks
I'm trying to stop notifications from interrupting my Pandora music! .....................….......
Fix_ toggle sound to mute in notifications panel.
Pp.
Factory reset help
HI, i tried the factory reset and this fixed my snapchat notification issue, however after a certain amount of time it just goes back to not receiving notifications again. What should i do?
Are you on AT&T, rooted with CWM or TWRP recovery, and don't want to update to the new, currently un-rootable ROM, or take the chance that AT&T will push the FOTA update to your phone and attempt to install it without your knowledge? Here's one way to block it:
1. Download Autorun Manager from the Play Store.
2. Run Autorun Manager, give it SU privileges, and enter its Recommended Advanced Mode.
3. Go to Settings, check both "Show system entries" and "Enable system app disable", and return to the list of apps.
4. Scroll down to "Google Services Framework" and open it.
5. Scroll down the list until you see "com.android.gsf.update.SystemUpdateService$Receiver" (mine was at the bottom of the list). Uncheck this to Disable it.
6. Exit Autorun Manager.
That's it. FOTA updates are now blocked.
This info is available in various places here on XDA, and other places on the web. I'm just reposting it here for those that don't want to be bothered with the problems that can be caused by AT&T's pissy little update.
visionlogic said:
Are you on AT&T, rooted with CWM or TWRP recovery, and don't want to update to the new, currently un-rootable ROM, or take the chance that AT&T will push the FOTA update to your phone and attempt to install it without your knowledge? Here's one way to block it:
1. Download Autorun Manager from the Play Store.
2. Run Autorun Manager, give it SU privileges, and enter its Recommended Advanced Mode.
3. Go to Settings, check both "Show system entries" and "Enable system app disable", and return to the list of apps.
4. Scroll down to "Google Services Framework" and open it.
5. Scroll down the list until you see "com.android.gsf.update.SystemUpdateService$Receiver" (mine was at the bottom of the list). Uncheck this to Disable it.
6. Exit Autorun Manager.
That's it. FOTA updates are now blocked.
This info is available in various places here on XDA, and other places on the web. I'm just reposting it here for those that don't want to be bothered with the problems that can be caused by AT&T's pissy little update.
Click to expand...
Click to collapse
F#$K man. This is great...
I have been hit three times in a row by the latest little update from AT&T, and have each time ended with CWM Recovery loop. This is so effing wrong !! I have a post here on how to get out of the recovery loop
http://forum.xda-developers.com/showthread.php?t=2603454&page=7 post #70.
EDIT: This did not completely remove the painful notification and for somereasoon I could not delete the downloaded in "/system/cache". So I applied the update, then used adb to recover from the CWM loop and delete the Fota.img, rebooted. Then I also installed the FOTAkill.apk app here
http://forum.xda-developers.com/showthread.php?t=2249350
Now the update is dead !!
chappatti said:
F#$K man. This is great...
I have been hit three times in a row by the latest little update from AT&T, and have each time ended with CWM Recovery loop. This is so effing wrong !! I have a post here on how to get out of the recovery loop
http://forum.xda-developers.com/showthread.php?t=2603454&page=7 post #70.
Click to expand...
Click to collapse
Damn right it's WRONG! Deliberately borking folks that don't follow the master's rules. Especially those folks that have had the update pushed and automatically attempted install without their consent. Pure crap!
chappatti said:
EDIT: This did not completely remove the painful notification and for somereasoon I could not delete the downloaded in "/system/cache". So I applied the update, then used adb to recover from the CWM loop and delete the Fota.img, rebooted. Then I also installed the FOTAkill.apk app here
http://forum.xda-developers.com/showthread.php?t=2249350
Now the update is dead !!
Click to expand...
Click to collapse
Good! Whatever works for you. My own experience with Android has been that a given "cure" will not necessarily work for everyone. As for the method I mentioned above I've gone 72+ hours without any data transfer related to the update. So far, so good.
Official OTA's aren't pushed out to those using an unlocked AT&T version on other carriers right?
Update FYI - 10 days now since making the adjustment in the OP and still no indication of my phone attempting any update.
I am unrooted and trying to find a way to keep from getting this notification. It downloaded
on its own-didnt do that with 2 previous updates. do i have to just keep ignoring it?
I have searched forums and net to no avail. btw, update and/or root not an option either.
thx for any ideas.
r, john
jb40 said:
I am unrooted and trying to find a way to keep from getting this notification. It downloaded
on its own-didnt do that with 2 previous updates. do i have to just keep ignoring it?
I have searched forums and net to no avail. btw, update and/or root not an option either.
thx for any ideas.
r, john
Click to expand...
Click to collapse
Not sure what version you're running, but you should be able to go to Setting, Applications (Applications Manager) whatever you have.
Find Samsung Update, stop it and uncheck notifications.
Sorry, I thought it was assumed. Im on ver 4.1.2
Also, the update comes from att. Greyed out in
App manager. Now what?
jb40 said:
Sorry, I thought it was assumed. Im on ver 4.1.2
Also, the update comes from att. Greyed out in
App manager. Now what?
Click to expand...
Click to collapse
With root not an option, not too sure....
I have ideas....
I'm really not sure if download has really been completed. You should have been prompted multiple times to accept the update, and the download.
Same goes for installing it, it requires multiple prompts and you must say continue.
So, the download gets saved in the /cache directory. If I'm right, and I should be, you should be able to power your phone down,
Then boot into stock recovery and clear cache which will delete the downloaded cache update file.
Boot into stock recovery (HOLD VOL UP+HOME+POWER)
Picture of stock recovery
http://galaxys2root.com/wp-content/uploads/2011/10/att-galaxys2-unroot-11-690x404.jpg
You want to choose wipe cache partition.
Then when you boot back up, race over to Settings, Applications again and stop the update service. I'd leave notifications turned on for now just to watch what the update process is attempting.
The dl started on its own. Finished too I would bet. Tried killing dl by reboot.
No joy.att must really want us to have this-I had to fetch the 2 previous updates
As I mentioned. Now I have cont/pp dialogue every 8 hrs. Process for notification is
Com.wssyncmldm -afraid to use stock recovery- I dontknow that it wont goof up
Something else-and my cache directory shows empty. (Using es explorer)
jb40 said:
The dl started on its own. Finished too I would bet. Tried killing dl by reboot.
No joy.att must really want us to have this-I had to fetch the 2 previous updates
As I mentioned. Now I have cont/pp dialogue every 8 hrs. Process for notification is
Com.wssyncmldm -afraid to use stock recovery- I dontknow that it wont goof up
Something else-and my cache directory shows empty. (Using es explorer)
Click to expand...
Click to collapse
You have to be root to really see what's in /cache.
Stock recovery really is harmless, for the most part. If you choose data/factory reset all of your installed apps (ones that you have downloaded and installed) are torched and your settings, like Google account info, mail setup etc.
Cleaning out /cache is a good thing.
Maybe someone else will stop by and have another suggestion, but since you said root is not an option, I can't think of another way right now to stop it from bugging.
Well, i suspected there was nothing i could do without root. something simple. the greyed out att update process
along with the attempt to force feed the update to me speaks volumes. to me. I've seen way too much of things i
don't like with this 4.3 silliness(improve my hardware, ok). they're going to have to do better than bug me every
8 hours to get me to install it....
thanks for the suggestions,
r, john
jb40 said:
Well, i suspected there was nothing i could do without root. something simple. the greyed out att update process
along with the attempt to force feed the update to me speaks volumes. to me. I've seen way too much of things i
don't like with this 4.3 silliness(improve my hardware, ok). they're going to have to do better than bug me every
8 hours to get me to install it....
thanks for the suggestions,
r, john
Click to expand...
Click to collapse
You are wise to avoid that locked down bootloader with Knox...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...