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.
Related
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.
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 cannot get JB still. I bought the phone from rogers and just use it on Telus.
Always when I try it gets stuck on bootloop.
Could I just borrow somebodies sim from rogers or fido and let them get the OTA?
not really sure how to get JB. Nothing has worked so far.
The OTA has absolutely nothing to do with what SIM you have in your device.
martonikaj said:
The OTA has absolutely nothing to do with what SIM you have in your device.
Click to expand...
Click to collapse
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Mackie011 said:
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Click to expand...
Click to collapse
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
martonikaj said:
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
Click to expand...
Click to collapse
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
And that is pretty much where I am at right now.
Not really sure how to make it work.
Mackie011 said:
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
Click to expand...
Click to collapse
Likely didn't wipe properly, chose the wrong ROM, or tried to switch between ROM makers unsuccessfully.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
Click to expand...
Click to collapse
When you flashed back to stock it didn't flash properly, or missed part (like recovery, bootloader or radio), so the OTA won't install properly.
If you want stock 4.1.1, just flash it completely. Stop trying to mess with an OTA.
This is the only guide I'd recommend: http://forum.xda-developers.com/showthread.php?t=1626895
Factory images... including 4.1.1 are right here: https://developers.google.com/android/nexus/images
As well, some have reported issues trying to flash JB if they had an old bootloader. Make sure you flash the LC03 bootloader before trying to flash a JB ROM. (It's already part of the guide mentioned above.)
Sent from my Galaxy Nexus using Tapatalk 2
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
Hey guys,
I have searched the forums for a while but I can not find the exact answer or procedure to help me out. I just rooted my phone yesterday for the first time and early this morning I received a notification to update my system. Can someone please respond in a helpful way to guide me in actually installing the new system updates and remaining rooted with the rom I am running. I understand this may not be possible without going back stock from what I have researched on the forums but any clarity in the situation would be appreciated.
I have the SPRINT GN2 SPH-L900 running Android 4.1.2 L900VPAMC2 and MacksROM Allstar! 3.5 MA7
I would like to install system updates if possible. If it is not explain why. If I can, how I do that and keep rooted with roms I like.
Thanks
If you're running MC2 Baseband, there's nothing you can update until Mack pushes out an MC2-built ROM. Consider the update notification a phantom and ignore it.
I'm running macks 3.5 w/MC2 and kept getting the update system notification and read to just install it and it would go to your recovery (twrp in my case) and it would fall to install. So that's what I did and didn't get the update since then, a few days now. I flagged another rom lady night and now just got the update message again. I will just accept it and it should disappear again. Hope I helped.
redrob820 said:
I'm running macks 3.5 w/MC2 and kept getting the update system notification and read to just install it and it would go to your recovery (twrp in my case) and it would fall to install. So that's what I did and didn't get the update since then, a few days now. I flagged another rom lady night and now just got the update message again. I will just accept it and it should disappear again. Hope I helped.
Click to expand...
Click to collapse
Back when I was on stock with a custom recovery and root. There was a different method that has been mentioned in the forums before, however if I would try to hit restart & install it would just sit there at 0 seconds and never would be able to actually go into the custom recovery. So I just finally decided to go back to stock in update to mc2 and then redo the whole custom recovery and root process.
Sent from my SPH-L900 using xda app-developers app
Well I tried to accept the update but this time it just stayed at the system will reboot screen but nothing ever happened, it never went into recovery or anything like that, however, I haven't got a update message since then.
redrob820 said:
Well I tried to accept the update but this time it just stayed at the system will reboot screen but nothing ever happened, it never went into recovery or anything like that, however, I haven't got a update message since then.
Click to expand...
Click to collapse
Are you trying to take the ota recovery?
Sent from my Amazing Galaxy Note 2!