[Q] Q. Why my system says up to date but its not??? - Nexus S Q&A, Help & Troubleshooting

I have a rooted NS4G with custom kernel Matr1x #5. Im currently on 2.3.4 and have not added any roms or updates. I kept recieving the OTA updates every 1/2 hr. im assuming for the 2.3.5. OTA was 22mb.
I was holding off for a while to not to update but finally gave in. I went to install OTA and my phone turned off and look as tho it was going to update my system. I let 15-20mins go by and I was still at a screen where there was a triangle with an exculmation and the android.
I thought it shouldnt take that long to update so I pulled the battery. I rebooted my phone and it still has 2.3.4 as my android version but when I click on system updates it says my system is up to date which is not the case.
If anyone install this OTA how long did it take for the whole process??
How do I fix this is with my system saying its up to date but clearly its not since im on 2.3.4???
I no longer get the notification to install a OTA. I would like to install an OTA instead of doing it manually.
I still want to be able to receive updates OTA when the are released. Im afraid I messed something up
Any assistance would be greatly appreciated
Thanks

http://forum.xda-developers.com/showthread.php?t=1185812
Flash this in clockworkmod it should update u and u keep root.
Sent from my CM7 powered Nexus S 4g using XDA Premium App

Rooted phone + OTA = fail

You need a stock recovery to install an ota....
Sent from my Nexus S 4G using xda premium

Related

[Q] Rooted phone updating

With a phone that is rooted will I still be receiving future android updates or will i have to go through xda or dev of the kernel in order to receive them. Total n00bian ? I know. Btw I got HTC Evo.
You will if you are just rooted but otherwise Stock. Once you've gone as far as flashing a custom recovery the OTA will fail during install.

[Q] Will I be able to update my NEXUS OTA after rooted with MoDaCo GRI40 SuperUser?

Hello everyone.
I am a happy owner of NEXUS S and I wanted to ask if I will ever receive future official updates OTA, has I've unlocked and rooted the same with the superboot MoDaCo (Even used Rom Manager to donwload ClockWorkMod)
Thank You very much
You will receive the update notifications as long as you don't flash a custom rom that has it disabled (which most do). In your current state, you will receive the update but if you choose to accept it, you will lose root and clockwork and will need to re-root again. The best way to update is to wait for a flashable update release on xda where you could update without losing root.
Sent from my Nexus S using XDA App
you will receive the update being rooted long before you would if you were stock and never rooted. when the next OTA comes out, it will be on the forum in the first 3 seconds and you will flash it. but if you were stock you'd be waiting 1 week for the rollout to hit your device.
and you can alwyas go back to stock ROM if you REALLY want to sit there and wait for google to push the update to your phone the official way. otherwise, everybody just manually updates as soon as the link is released.
just ignore the OTA update, as it will usually break the custom ROMs if you try to install them.
wait for the custom ROMs to include the OTA update into their next build
thank You very much for support.
only one question even if it is OT
After manually updated my nexus 2.3.2. to original stock 2.3.3 I've seen that there is an app called BOOK of 0kb that can't be uninstalled. Why? How can I remove it?
that is Google books
it is build in part of the stock ROM
that means it is not using any storage space
thank You very much.

[Q] OTA updates on rooted Xoom 4g

I am rooted using the Universal Xoom Root method. I am still running stock, only with SU and apps which require SU. Why can I not accept an OTA update? It seems like the worse that could happen is it overwrite the SU.apk and I need to re-root.
Thanks in advance.
I was wondering about this as well. I am rooted and am running Rogue kernel. I guess I'll just update and see what happens. Worse comes to worse, I will have to re-root.
Seems like the Xoom forums are quiet...did a lot of people abandon the device for the Galaxy Tab 10.1...When previous OTAs happened, the forums were chock full of chatter about to or not to accept the update.
Yeah, I just tried an OTA update and it wouldn't work. Got the Droid with exclamation point. Up + power put me back where I was.
Sent from my Xoom using XDA App
same here. No dice on the update, just stuck at the install screen. On a positive note, the update notifications are gone. Damn those were annoying.
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
place your unrooted backup on, take update and reroot.
if you don't have one, their are some around.
I keep a backup that isn't rooted with all my apps installed, then when update comes, it is real quick to restore, update and reroot ....
jerrycycle said:
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
Click to expand...
Click to collapse
Yeah, diddo here with it not bothering me about OTA updates anymore after trying. It didn't put me in a boot loop, just the pretty droid screaming (exclamation point)
I have a backup from before I rooted, but what the heck, it didn't hurt anything, and I was just playing around.
Thanks for everyone's input.
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
flippingout said:
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
Click to expand...
Click to collapse
Yeah, diddo. Mine started again about three days after I tried to install. I too am looking forward to ICS.
Sent from my Xoom using XDA App

TMobile SG2 Update notification

I am currently running Boot Rom Juggernaut 3.7 on my SG2 with Tmobile service. This morning I got a notification that Tmobile released a new update and my phone wants to update. What should I do?
I'm having the same issue. Problem is, even you accept the update, it just reboots into CWM. If you choose to reboot it just prompts you to accept the update again. Any ideas for a solution?
Sent from my SGH-T989 using XDA App
Yea I tried taking the plunge and going on with the update, but yea, it just reboots into CWM. I am currently doing the 4.1 update that they have released. Once I complete the update I will let you know if the Tmobile update still comes up.
So I just updated to the 4.1 version, still getting the update message...anyone?

OTA failed 4.1

Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Tbalon said:
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
try to flash CWM via fastboot then update via a zip file throw cwm.
if not u can get ur phone back to clean stock using adb and then u will receive again the ota and u can try to update again
Tbalon said:
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
It is not necessary to flash in order to get the OTA update again. Instructions to force another OTA update are here (basically: clear data on the Google Service Framework app, this resets the time the phone last checked for an update).
However, I'm facing the same problem and even after re-downloading the 4.1 update on my stock Nexus S, the update still fails. The phone reboots and starts to install the update then shows the dead droid with red exclamation before rebooting to 4.0.4.
I've seen other suggestions to get the device back to stock so I guess that's my next course of action (and likely yours).
Are these instructions appropriate? http://forum.xda-developers.com/showthread.php?t=1785672
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
That is what appears to have happened. I was just confused regarding this and assumed my previous update was to 4.1.
I tried several times to "checkin" and eventually I got the update to 4.1.1 which, unlike the update I did a few days ago,
took longer ( about 10minutes ) to update. I now have 4.1.1 JRO03E , very snappy
Thanks !
No problem, man! Us I9020A's gotta stick together!
Sent from my Nexus S using xda app-developers app

Categories

Resources