Hi,
I installed 4.0.4 manually some weeks ago. Everything worked fine for a while.
Now I get the message that there is a new release available (4.0.4 as shown) and whether I want to install it or not.
It looks like, that I got 4.0.4 now via OTA in parallel.
I've installed 4.0.4 already, so there is no need to reinstall it via OTA (I'm not sure if it would work because my phone is rooted and unlocked).
My question is now,
a) how to make these annoying OTA-Update-Message disappear ?
b) how to disable future OTA-Updates because I think that I'll updated my phone manually in future ?
regards
J.M.
You should allow it to install your 2nd 4.0.4 as there is in actual fact an update going around which is a small patch to help the phone keep signal while its asleep so your not so likely to get missed calls. Also it won't keep annoying you if you install it
Sent from my Galaxy Nexus using Tapatalk 2
doesnt work
Hi,
I tried to install it, after reboot (as requested from install procedure) all I got was a lying Android with that red triangle and a exclamation-mark.
After that I removed battery and than I could reboot as used.
But I think I've still that issue with
- missing phone calls as you mentioned them
and
- these annoying update messages
an idea how to proceed ??
Best regards
J.M.
I have the same problem - I'm running android revolution HD 3.0.0 so the update isn't going to work anyway?
Sent from my Galaxy Nexus using Tapatalk 2
Sounds like your recovery might be messed up perhaps. What have you done to your phone? Rooted, cwm, custom rom etc?
Sent from my Galaxy Nexus using Tapatalk 2
Hi
as I wrote, mine is
# unlocked
# rooted
# installed CWM
regards
J.M.
JovanniBordelli said:
Hi
as I wrote, mine is
# unlocked
# rooted
# installed CWM
regards
J.M.
Click to expand...
Click to collapse
The update won't install because your using cwm recovery. You could use a tool kit to flash back to stock recovery, install the update then flash back to cwm perhaps
Sent from my Galaxy Nexus using Tapatalk 2
Or you could just follow the instructions in the update link in my signature to install the update using CWM.
Sent from my Galaxy Nexus using Tapatalk 2
worked fine with CWM from IMM76D to IMM76I
Hi Efrant,
thank you for your proposal - worked well with CWM as your wrote.
Now I'm from 4.0.4 IMM76D on 4.0.4 IMM76I.
Great and thanks
J.M.
Related
...I downloaded the 4.0.4 update and went to install and reboot. But the phone got stuck at the screen with the android belly up and a exclamation point. Pulled the battery and rebooted and was at 4.0.2 still. Haven't gotten another OTA notification. Do I get another OTA alert or do I have to update manually.
I have a GSM Nexus, rooted but with stock 4.0.2. And I activated OTA RootKeeper before downloading the update. Any help will be greatly accepted.
Sent from my Galaxy Nexus using Tapatalk
Besides root and maybe unlock your bootloader, did you change anything in your system (install mods, different radio etc. or rename system files)? If you are not completely stock your OTA will not work and you will have to update manually or get back to Stock first.
Sent from my Galaxy Nexus using xda premium
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Well the screen you were looking at (Android belly up) is the stock recovery. If you see that: no need to pull battery. Simply push volume up + power simultaneously and you'll get into the recovery menu. Scrolling through the options can be done with the volume buttons, select with the power button.
That said: I think no one knows for sure but I myself would not wait and update myself. There are a lot of guides here on how to do that and if you flash the stock images you will have the same as anyone who had the OTA. Make a proper backup first (you allways should)! You will lose all your data if you have to unlock your bootloader.
Sent from my Galaxy Nexus using xda premium
jrodsep said:
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
stuu.f said:
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Is it possible to get the Stock Recovery Screen when you have CWM installed? Didn't think that was possible... that it would just boot into CWM recovery. That is why I didn't mention it (trying to learn here).
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Lex_Michdeandroid said:
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Click to expand...
Click to collapse
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Viridis Draco said:
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Click to expand...
Click to collapse
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Viridis Draco said:
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Click to expand...
Click to collapse
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Edit: would it be easier if I just get the stock recovery back and then try to get the OTA to turn up again?
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Viridis Draco said:
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Click to expand...
Click to collapse
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
i agree, take your time and you wouldn't regret it
I want to manually flash 4.0.4 and stay unrooted. Should I use the GNex Toolkit to flash 4.0.4 directly or do I need to flash the same version I have on my phone?
Sent from my Galaxy Nexus using Tapatalk
I had the same issue described by the OP, the belly up android when trying to update to 4.0.4 from the OTA notification. I had previously changed to 4.0.2 yakju using efrant's instructions from the first post in this thread: http://forum.xda-developers.com/showthread.php?t=1391881
However, I had skipped the optional sections. In particular step 12 to flash the recovery partition. I went back and just executed step 12 (fastboot flash recovery recovery.img) and rebooted. Then I was able to update to 4.0.4 successfully from the OTA notification.
I'm guessing I didn't have the "stock recovery" because I previously had the default Samsung version?
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Lex_Michdeandroid said:
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I had the same issue just now with my phone (unlocked, rooted, stock revcovery), but a quick reboot allowed the update to complete and I'm now on 4.0.4. Did you check the version number again after this latest attempt?
Yes, still 4.0.2.
And of course, my phone says I'm up to date. Lovely, NAAAAAT!
Sent from my Galaxy Nexus using XDA
Hey guys
I am having an issue after my nexus has been updated to the latest 4.04 release
My phone has been rooted and boot loader unlocked with the Franco kernel installed but my phone still says I need to install the update 4.04 in which it has already been installed
So I go through the install again it crashes out I then take the battery out to reboot the phone it then clears says no update required then it comes back ready to install update is there anyway to stop the update check to the device
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
steelmm said:
Hey guys
I am having an issue after my nexus has been updated to the latest 4.04 release
My phone has been rooted and boot loader unlocked with the Franco kernel installed but my phone still says I need to install the update 4.04 in which it has already been installed
So I go through the install again it crashes out I then take the battery out to reboot the phone it then clears says no update required then it comes back ready to install update is there anyway to stop the update check to the device
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You are running IMM76D (which is 4.0.4), and you are getting the update notification for IMM76I (which is also 4.0.4, but a newer build).
I would suggest you install it - but to do so, you need to flash back the stock IMM76D kernel, install it, then flash back your custom kernel.
EDIT: I can also tell you how to disable the notification, in case you don't want to install the update, but I would recommend you install it.
Hi
Many thanks for your solution
Please could I have the solution to turn off the update notification to the device I will prefer to do this time than to reinstall all my data
Thanks mark
Sent from my Galaxy Nexus using Tapatalk 2
steelmm said:
Hi
Many thanks for your solution
Please could I have the solution to turn off the update notification to the device I will prefer to do this time than to reinstall all my data
Thanks mark
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The update is an incremental update, and it will NOT wipe any of your data. You just have to flash the stock boot image (which does not wipe any data either), then accept the update, then flash back your preferred kernel.
But in any case, if you want to disable it, you need to edit a line in your build.prop file. Change the line that begins with ro.build.fingerprint to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.4/IMM76I/330937:user/release-keys
Make sure you back up your original first.
Many thanks for everything I will do this later tonite.
Sent from my Galaxy Nexus using Tapatalk 2
I got an update push today. I told it to go ahead, but it rebooted to twrp and stopped. Now Ive put back the stock recovery and everytime i hit update in settings nothing happens.
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
I got an update push today. I told it to go ahead, but it rebooted to twrp and stopped. Now Ive put back the stock recovery and everytime i hit update in settings nothing happens.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Well now you cant run an update with a custom recovery on board and since you started it there is prolly a file or the OTA server thinks you have it installed and is not offering it again.
Best thing to do on phones where you have custom recovery? Look here on the boards for the Stock ROIM of the version you want. If you wanted it un-rooted [no super user] then look in the returning to stock thread, if you want supersu (have your phone rooted) then look for a ROM of your choice based on the Android Version of your choice they range from hardly any changes [the ones that say only busybox and rooted are usually just stock ROM with just those 2 additions].
You want to use JB which Samsung has not even upgraded the T989 to yet [completely stable and I have been using it as my Daily Driver for month ].
First download ROM Manager from Market and have it flash CWM Recovery
Go to development section here and find the ParanoidAndroid thread and download the Nov 18 dated file and Gapps and flash those
Now you will have Android 4.1.2 - Jellybean! Enjoy
I have stock rooted 4.0.4 and it asked me to update. Do you think T-Mobile is releasing an update? Anyone else getting it?
I'd like to keep my wifi calling so i havent moved to a 4.1.2 rom.
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
I have stock rooted 4.0.4 and it asked me to update. Do you think T-Mobile is releasing an update? Anyone else getting it?
I'd like to keep my wifi calling so i havent moved to a 4.1.2 rom.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been receiving an update as well. Problem is every time I go to update since my phone is rooted but running the stock rom, after i reboots to start the update it sends me to Clockwork Recovery...which actually brings me to ask my question here instead of starting a new thread. I really don't want to un-root since I make use of the cracked Google Play for a couple of my apps Do I really have to un-root just to receive T-Mobiles update?
I received an update notification through OTA, and I've start the upgrade process, the device restarted to do the upgrade, but while upgrading it gave an error and hanged, I've removed the battery and start the phone, but I'm still on 4.2.2, and whenever I try to check for update it gave that there's no update.
???????
Sent from my Galaxy Nexus using xda app-developers app
Forget to tell that my device is yakju
Sent from my Galaxy Nexus using xda app-developers app
Is your phone stock? If you're rooted and made any modifications to system files (mods, build.prop edits, etc) your phone will fail during the OTA. You need to be completely stock on the latest 4.2.2 radios for your model. Basically you have to be more or less on the 4.2.2 OTA to get 4.3.... always been like that for every android version though.
Can't you fasboot flash the factory images?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
RoyJ said:
Is your phone stock? If you're rooted and made any modifications to system files (mods, build.prop edits, etc) your phone will fail during the OTA. You need to be completely stock on the latest 4.2.2 radios for your model. Basically you have to be more or less on the 4.2.2 OTA to get 4.3.... always been like that for every android version though.
Can't you fasboot flash the factory images?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Exactly what happened to me. So, I flashed factory images, received OTA for 4.2.2, cleared Google Services Framework several times, 4.3 showed up. In process of installing. Good to go.
I think flashing the image it's the easiest way, any one had the link for yakju?
Sent from my Galaxy Nexus using xda app-developers app
Also happened to me. Cleared "Google Services Framework" and tried to re-install 4.3 when it came down.
Still got an error
Any ideas?
ronsher said:
Also happened to me. Cleared "Google Services Framework" and tried to re-install 4.3 when it came down.
Still got an error
Any ideas?
Click to expand...
Click to collapse
are you on a completely stock rom? if not, it will always fail.
My friend has problem too
I rooted and install custom reovery and costume kernel for him
He got 4.3 OTA update but he get error in installing
would somebody tell me what can I do for him?
hes_luckey said:
My friend has problem too
I rooted and install custom reovery and costume kernel for him
He got 4.3 OTA update but he get error in installing
would somebody tell me what can I do for him?
Click to expand...
Click to collapse
wow.... does no one read anything? there's a thread exactly like this in Q/A, and i even said the reason it will fail not 1 post above yours... my mind is blown at the pure laziness that you have shown.
I have a i9250 gsm Galaxy Nexus, maguro. JWR66V. It used to be Yajuux but I changed this to Yakju with Wug Fresh's Nexus Tool kit. I manually updated my phone to 4.3. However, about once a week, I get a notice that my phone would like to update to 4.3. The download is only 1.7mb. Once I allow the update, the phone reset, boots up and says "installing system update" with the android mascot on the screen and a swirly atom-thing at his stomach. After about a minute a message comes up that says "error!" with the android mascot now on his back. I have to remove the battery and restart my phone, otherwise it hangs. The update notice won't come back for another week, unless I stop the google service framework app and clear the data. I'm assuming these system updates are to upgrade to JWR66Y, but I don't know why I keep having these errors. Any help/advice would be appreciated.
Figured it out
Solved. I managed to sideload the update through the Nexus toolkit. Even after updating though, it didn't show the correct version. I had to unroot by uninstalling supersu (survival mode didn't work), then doing the OTA update, then reinstalling the binaries for Supersu.
Can anyone recommend a good site/feed that keeps track of these security updates/other major updates?
And the toolkit gets the credits, even when the user still has no idea what just happened.
beekay201 said:
And the toolkit gets the credits, even when the user still has no idea what just happened.
Click to expand...
Click to collapse
braindead users win again!
No Clue..
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
dipenv said:
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
Click to expand...
Click to collapse
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for this explanation. Very helpful to braindead user like myself, and will help me know what to do for future updates.
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Does doing this wipe the phone?
Not if you only install the update. You will have to reinstall supersu after the update because you will lose root.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Zepius said:
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Click to expand...
Click to collapse
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Requesting the download link if possible. Searched the forum but couldn't found one. Tx in Advance.
Solved. Got it! HERE