Hello. I have a Galaxy Nexus on Verizon's network and it keeps giving me a pop up notification that there is a system update available, the IMM76K update. However, my phone is already on Android version 4.0.4. I am rooted, running the Axiom ROM (Axiom Crossbreed Monolith B1), and have Clockwork Mod Recovery. I can't get the notification to go away, and it obviously fails if I try to hit update. I've read some similar threads about problems people have had when they try to install the update, but my problem is different because I'm pretty sure it doesn't actually need the update, I just need to get rid of the pop up. Can anyone help me?
All the OTA does is check to see if your footprint is proper (via build.prop check) to get the update, then pushes it. It doesn't really care if you're on a custom ROM so you can still receive the OTA when you don't actually want it (that's where you're at now).
Basically what's going on is the custom ROM maker isn't blocking OTAs (they should be) and you're gonna keep getting bothered by it until they fix that or integrate the OTA code into their new release.
Great. So basically I should check to see if there is a more updated version of the ROM or I should try getting a new ROM which is blocking the OTAs?
jfinfin said:
Great. So basically I should check to see if there is a more updated version of the ROM or I should try getting a new ROM which is blocking the OTAs?
Click to expand...
Click to collapse
Yes. This seems to be a recurring issue and I'm not sure why these ROM makers aren't integrating an "FOTA kill" service.
jfinfin said:
Hello. I have a Galaxy Nexus on Verizon's network and it keeps giving me a pop up notification that there is a system update available, the IMM76K update. However, my phone is already on Android version 4.0.4. I am rooted, running the Axiom ROM (Axiom Crossbreed Monolith B1), and have Clockwork Mod Recovery. I can't get the notification to go away, and it obviously fails if I try to hit update. I've read some similar threads about problems people have had when they try to install the update, but my problem is different because I'm pretty sure it doesn't actually need the update, I just need to get rid of the pop up. Can anyone help me?
Click to expand...
Click to collapse
I ignored the pop-up and it expired after 2-3 days. But don't initiate the update or you might end up with a bricked phone or be stuck in a boot loop. If you don't want to wait for the dialogue to disappear, you can search for FOTAKill.apk and install.
Related
My phone has been prompting me to install 4.0.4 update as of late. I was running a stock 4.0.4 flash w/ root and about 2 weeks after installing it via CWM it prompted me to install. The installation failed so I yanked the battery and it successfully booted back into the phone. After this it won't prompt again until after the phone is rebooted again.
I just flashed to the 4.1 Jelly Bean release figuring that would alleviate the problem and it still exists. My phone is constantly telling me to update the phone (even though now a 4.0.4 "upgrade" would infact me a downgrade). This is driving me crazy...is there any way to stop this from happening?
DKNUCKLES said:
My phone has been prompting me to install 4.0.4 update as of late. I was running a stock 4.0.4 flash w/ root and about 2 weeks after installing it via CWM it prompted me to install. The installation failed so I yanked the battery and it successfully booted back into the phone. After this it won't prompt again until after the phone is rebooted again.
I just flashed to the 4.1 Jelly Bean release figuring that would alleviate the problem and it still exists. My phone is constantly telling me to update the phone (even though now a 4.0.4 "upgrade" would infact me a downgrade). This is driving me crazy...is there any way to stop this from happening?
Click to expand...
Click to collapse
Let me guess, you are running a custom ROM?
This will fix it: edit the line that starts with ro.build.fingerprint in your build.prop file to read like this:
ro.build.fingerprint=google/takju/maguro:4.1/JRN84D/392829:user/release-keys
I wish I could say I was talented enough to create my own ROM, however I'm just flashing ROMS from the forums here.
The Jelly Bean ROM i just flashed is the one located HERE
DKNUCKLES said:
I wish I could say I was talented enough to create my own ROM, however I'm just flashing ROMS from the forums here.
The Jelly Bean ROM i just flashed is the one located HERE
Click to expand...
Click to collapse
By custom, I meant NON-stock, like that one. Do what I posted above.
No love I'm afraid. That's actually what's already in the ro.build.fingerprint...
Any other suggestions?
DKNUCKLES said:
No love I'm afraid. That's actually what's already in the ro.build.fingerprint...
Any other suggestions?
Click to expand...
Click to collapse
Hmmm. Strange. That used to fix it for older versions. Anyway, maybe re-flash Jelly Bean, and use the stock ROM this time: http://tinyurl.com/JRN84D
I cleared the data in the Google Services Framework, restarted the phone and the notification has not popped up since.
I'm headed to NYC tonight and will have little access to the internet but I will report back.
Thank you for your help efrant!
Clearing the data from the Google Services Framework seems to have done the trick. Almost a week and no prompts to install an update.
I have a rooted nexus on 4.1 and I keep getting the OTA update every few mins and its so annoying. I tried to do the update but I get the android lying down and have to do a battery pull to get my phone back up and running. When I first rooted my phone I remember doing something with the date somewhere to get the 4.1 OTA update but it wouldn't work and I flashed a rom. What do I need to do to either do the update or get the annoying pop up to stop?
tsunawmi said:
I have a rooted nexus on 4.1 and I keep getting the OTA update every few mins and its so annoying. I tried to do the update but I get the android lying down and have to do a battery pull to get my phone back up and running. When I first rooted my phone I remember doing something with the date somewhere to get the 4.1 OTA update but it wouldn't work and I flashed a rom. What do I need to do to either do the update or get the annoying pop up to stop?
Click to expand...
Click to collapse
Best option is to flash the Google 4.1.1 images, if you can manage.
Other option is to flash the stock recovery stock radio of 4.1 and than the ota will flash, retaining all your stuff.
tsunawmi said:
I have a rooted nexus on 4.1 and I keep getting the OTA update every few mins and its so annoying. I tried to do the update but I get the android lying down and have to do a battery pull to get my phone back up and running. When I first rooted my phone I remember doing something with the date somewhere to get the 4.1 OTA update but it wouldn't work and I flashed a rom. What do I need to do to either do the update or get the annoying pop up to stop?
Click to expand...
Click to collapse
Read the first and second posts in the "update" link in my signature.
So I've rooted my SGH-i317M (Rogers)and now I'm not sure if I should go back. I've noticed OTA update says the device has been modified and software updates are not available. Not sure if this has always been like that, since usually updates for samsung devices are done via Kies. However when I plug into Kies, it also says the device has been modified.
Should I revert back to original? I mean Samsung is terrible with their updates and something tells me that by the time Rogers releases and update, we'll be on Android 34 Chicken Soup or something. I figure custom roms will be springing up in no time.
What's your guys take?
I also noticed that Learning Hub stopped working after root, and I'm not sure what else may be affected. This plus the stock browser and email screen dimming, I'm not sure if this is all because of root.
Thanks for your suggestions.
So, I had kept my S3 on ICS up until earlier this evening. For the past week, my phone would pop up with a 387.38mb downloadable update that it would only do on WiFi.
I assumed this was Jelly Bean, so I just went ahead and downloaded Kies, because my PC can download the update much faster.
I had downloaded the update before, but the fact that I was on custom recovery and rooted caused it to fail every time. I went and unrooted, and reinstalled normal recovery, just so I could update. I did the JB update, then rerooted and reinstalled custom recovery.
I'm still getting the notification and download prompts for the previously mentioned update.
Does anyone know what it is? I feel like an idiot for asking, but I have Google searched and found nothing. in fairness, I am tired and have had long day, so its highly likely I missed something. Please inform me. Thanks in advance.
Majin Kaioh said:
So, I had kept my S3 on ICS up until earlier this evening. For the past week, my phone would pop up with a 387.38mb downloadable update thuld only do on WiFi.
I assumed this was Jelly Bean, so I just went ahead and downloaded Kies, because my PC can download the update much faster.
I had downloaded the update before, but the fact that I was on custom recovery and rooted caused it to fail every time. I went and unrooted, and reinstalled normal recovery, just so I could update. I did the JB update, then rerooted and reinstalled custom recovery.
I'm still getting the notification and download prompts for the previously mentioned update.
Does anyone know what it is? I feel like an idiot for asking, but I have Google searched and found nothing. in fairness, I am tired and have had long day, so its highly likely I missed something. Please inform me. Thanks in advance.
Click to expand...
Click to collapse
What is your current baseband version? Possibly your update did not flash correctly. I would backup your phone, make a nandroid, wipe data/factory reset, wipe cache, download and flash stock JB via odin and wipe data again. There are 2 JB versions available in the Android dev thread. One is stock with root injected and the other will require you to root again after flashing if you want.
I'm on Baseband i747UCDLK3, which as far as I know is the latest update.
My solution was to go in to Titanium, find the app that handles updates (in this case its called "AT&T Software update V4_1_1210_2_2"", and freeze it. No more annoying nags about an update, so far.
I'll have to see how well it works. It's only been disabled for about ten minutes, but if I don't get nagged anytime by tomorrow, this thread can be considered closed, since I'll have figured out the solution.
EDIT:
Its been more than 24 hours without the nag. This solved the issue, so this thread can be marked as answered and closed.
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
I really hope someone helps with this, because oddly enough, I just had the exact same problem!
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I suggest you should go check out the Sprint Samsung s3 forum under the Android development section the check out for the stock rom, try using the 1 click Odin or check out in there the proper way to restore your device, then continue reading the forums to check out when or how is the proper way to apply that update it could be that its bugged or that your device lost some permissions so best way to solve it should be to restore it to its original state.
Sent from my SPH-D710 using xda app-developers app
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You cant install an OTA update unless you have the official stock rom and the stock recovery because custom recoveries will install it and I believe im correct when I say that to flash an OTA update you have to odin to stock and then do the update.
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Most custom touchwiz roms will allow updates, but you have to flash stick recovery 1st. The 157mb update is for mb1. You could just change your build prop to get the notification nag to go away
sent from my GS3 using XDA app
If you're on stock rooted with no apps removed, do what I did. Plug phone into odin, flash stock recovery, update, flash custom after update done, re root, done.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
tazfanatic said:
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
Click to expand...
Click to collapse
Yup, if you just wanna make it go away, go into your build.prop and change all instances of "LJ7" (or "MA6" ) to "MB1"
CNexus said:
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Click to expand...
Click to collapse
That's all I do. Once an update comes out I just head over to Freezas page and update my rom. Stock look and feel with the root in place.
Sent from my stock rooted Galaxy S3
Any update on this? I have the same issue.
Thanks
coderaja said:
Any update on this? I have the same issue.
Thanks
Click to expand...
Click to collapse
There's several ways to fix this issue posted on the other page. Use one of them.
D