I tried today to OTA update my phone and it said I had the current version even though i DID NOT update to GB before. Does anyone know why? I restored the stock, but did not unroot nor nvflashed to stock. I wanted to check for update first and afterwards to unroot and revert nvflash...
krekabl said:
I tried today to OTA update my phone and it said I had the current version even though i DID NOT update to GB before. Does anyone know why? I restored the stock, but did not unroot nor nvflashed to stock. I wanted to check for update first and afterwards to unroot and revert nvflash...
Click to expand...
Click to collapse
I'm back on froyo ATM and I get the same message. They could be releasing it from coast to coast, from east to west. Pushing the update to all G2X users at once would slow the network down drastically.
Sent from my LG-P999 using XDA Premium App
I'm on the east, didn't get mine yet....
I get an authentication error with mine.
same here, "authentication failed".. does this mean we wont be able to get the update?
To me, it seems all so clumsy...
anyone that got an authentication error managed to get the ota gb update?!?!?!?!
Related
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
When my G2x was stock unrooted it always failed authentication when checking for an OTA update. I had always assumed this was because I'd done a desktop install of the LG Gingerbread update. After I rooted my phone I tried installing the stock Froyo ROM to test my theory and it still failed.
No problem, I thought, because I'm gonna install CM7. Well now I'm running CM7 and when I go to the section to register the phone for push update notifications I get the message "Registration failed."
Are these two issues connected and what might the problem be?
Once you're rooted, I don't think you can get OTA... when I had my rooted Mytouch 3g I was told to not accept ota or phone might mess up. Plus CM7 is better than stock
kompheak said:
Once you're rooted, I don't think you can get OTA... when I had my rooted Mytouch 3g I was told to not accept ota or phone might mess up. Plus CM7 is better than stock
Click to expand...
Click to collapse
The failed authentication to connect to T-mo's servers was before I rooted. I'm not so concerned about that as I am about the phone failing to register for push notifications of CM updates. The only reason I mentioned the authentication error with T-mo is because I ws wondering if they might be related.
Been trying it for two days, says no software update available..Does anyone know if this has been pulled back?
When I called AT&T about the update, I was told that the new update was only for selected devices that needed it based on the IMEI. Don't know if true but doesn't sound far fetched. Seems like only certain people have it while others do not.
Ive been trying for weeks with no luck, when i called att the rep told me that i had to wait for the notification from att to show up, going to settings and update software wont work at all. So i was told. I wish we could get some solid information about what happened to our update.
Sent from my Transformer TF101 using xda premium
Yes, unfortunately or fortunately I had the update bugging me for 2 days, back in Nov. I had CWM recovery then, so the update failed, now of course it says that no updates are available. So I am not sure about the IMEI theory as I cannot get it anymore, as I went back to Stock recovery hoping I could do it.
When I was on the Samsung Moment they pushed an OTA update that was only for the first 1000 phones that downloaded it. They were using their customers as beta testers.
Izmir Stinger said:
When I was on the Samsung Moment they pushed an OTA update that was only for the first 1000 phones that downloaded it. They were using their customers as beta testers.
Click to expand...
Click to collapse
Sounds likely, esp with CIQ installed!
I got it about 2 days after getting my phone, then I had to flash back to stock with ODIN to 2.3.5, it now says no update aval. Not sure it's IMEI based...
Were there any noticeable changes anyhow?
If you want 2.3.6 and you can't get the 2.3.6 OTA update, why don't you flash the stock 2.3.6 zip in the Development section using CWM? (posted by silver03wrx).
When we called into Samsung last week about some browser questions (pinch reflow) we also asked about the update. We were informed it was pulled because of issues and to watch for further updates.
Sent from my SAMSUNG-SGH-I727 using XDA App
I received the update on day one...can't tell if there is any actual change in the device...other than the one-click riot methods NOT working. Which is really frustrating. Lesson learned: don't be quick to update.
Sent from my SAMSUNG-SGH-I727 using XDA App
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
I unfroze all the apps I had frozen and tried the OTA and it still failed.
I am rooted with just the stock ROM.
Anything I am missing here?
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
No OTA updates will work on a rooted phone. If it somehow does work it will likely break your root privileges
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Plunkyxda said:
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
Click to expand...
Click to collapse
You can do a OTA with root but you will just lose it. If you altered some system files it will fail or if you run a custom recovery it will fail.
I've had similar issues, on other devices, with ota updates not working because of root, and more specifically I believe, cwm recovery. Unfortunately I've had to use kies to update.
Sent from my SCH-I535 using xda premium
kendive said:
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Click to expand...
Click to collapse
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Yea I agree... I did not really need the OTA and I plan on installing CleanROM 5.6 tmr.
I just froze all that bloat back. I can't stand all that S***T running in the back ground.
Plunkyxda said:
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Click to expand...
Click to collapse