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
Related
Info Can be found here, http://support.vzw.com/system_update/droid_2_global.html
Confirmed on Verizons Twitter feed that the Gingerbread release has been rolling out since the end of August.
Do a 'checkin' (*#*#checkin#*#*) on your phone then Settings > About Phone > System updates. Keep trying if none is found.
System Version: 4.5.607.A956.Verizon.en.US
Android Version: 2.3.3
Baseband Version: N_01.79.00R
Kernal Version: 2.6.32.9-gb092e69 [email protected] #2
Build Numbe: 4.5.1_57_D2G-37
ERI Version: 5
PRL Version: 52341
3G signal has been improved with this radio and speeds are more constant and faster.
You will have to go back to stock before you will even be notified of the update. When I had my droid 1 it took a week after the release before I received the update to 2.2
Sent from my DROID2 GLOBAL using Tapatalk
Whats the best way to revert back to original rom?
Try this
http://www.droidforums.net/forum/showthread.php?t=153973
D2G
60lpsdf250 said:
Try this
http://www.droidforums.net/forum/showthread.php?t=153973
D2G
Click to expand...
Click to collapse
A great write up, but darn my windows machine and Linux in-experiences
http://technology.gather.com/viewArticle.action?articleId=281474979452576
here is another news story on it.
Anyone updated yet
I have tried on 2 stock roms (rooted) and neither say there is an update available - before going back to stock via the 11 step process, has anyone actually updated their device yet - or am I just not patient enough and the update is actually rolling out slowly and not available manually? Any help is appreciated, since I would hate to blast phones to get the update (i would rather wait on a rooted version, but would love to get a better experience than the current ROM provides!)
davrodg said:
I have tried on 2 stock roms (rooted) and neither say there is an update available - before going back to stock via the 11 step process, has anyone actually updated their device yet - or am I just not patient enough and the update is actually rolling out slowly and not available manually? Any help is appreciated, since I would hate to blast phones to get the update (i would rather wait on a rooted version, but would love to get a better experience than the current ROM provides!)
Click to expand...
Click to collapse
I too would rather wait for a rooted version but I'm too excited to use Gingerbread. I will roll back my rom to the original tonight via Moto RSD Lite and then try the update, I will report back if all goes well... or not, hehe.
davrodg said:
I have tried on 2 stock roms (rooted) and neither say there is an update available - before going back to stock via the 11 step process, has anyone actually updated their device yet - or am I just not patient enough and the update is actually rolling out slowly and not available manually? Any help is appreciated, since I would hate to blast phones to get the update (i would rather wait on a rooted version, but would love to get a better experience than the current ROM provides!)
Click to expand...
Click to collapse
No one that I know of has updated their device...
Unknown when it will roll out, but check this http://support.vzw.com/system_update/droid_2_global.html
60lpsdf250 said:
No one that I know of has updated their device...
Unknown when it will roll out, but check this http://support.vzw.com/system_update/droid_2_global.html
Click to expand...
Click to collapse
same link as op, herp. Got Derpes?
60lpsdf250 said:
No one that I know of has updated their device...
Unknown when it will roll out, but check this http://support.vzw.com/system_update/droid_2_global.html
Click to expand...
Click to collapse
try *#*#checkin#*# or the other way around, i forgot.
My wife has the D2 Global on vzw. running the orig 2.2 not rooted or bootstrapped.
No update notifications / plus the software update says the phone is up to date.
*#*#2432546#*#*
Checkin works fine, still no update atleast in the Phoenix Metro Cell System.
Just tried checkin as well and no gingerbread love here, either. In Columbus, Ohio. I believe the update is still in it's "soak-test" phase, which means only a select few will actually receive it just yet. My guess is we're sstill a week out from actual release, but don't quote me on it. Only wishful hoping at this point .
Nothing here in NC yet.
Ive tried the *#*#checkin#*#* also no go.
Anyone got it yet? I wish we can find the SBF so we can just flash it ourselves
will being rooted prevent me from getting the update?
giganticprune said:
will being rooted prevent me from getting the update?
Click to expand...
Click to collapse
If you have a custom ROM on your rooted device then most defiantly. I went back to the original stock using the 11 step process without a problem, but you will most probably have to wipe/factory data to get it to work.
I'm still waiting for the new update though
Root, etc.
Just got a Droid 2 Global from Assurion (brand new) as a replacement for a stolen Droid 2. Pure stock, never been rooted; no update. So those of you with no update don't need to panic over whether you ran Z4ROOT or not; the update is NOT yet here, at least on my phone (California) and it is pure as the driven snow.
http://www.droid-life.com/2011/06/15/droid2-global-gingerbread-starts-rolling-out-today/
This is the latest. Its rolling out today. slowly. I wish someone would just get the SBF and we can flash it.
rhcp0112345 said:
http://www.droid-life.com/2011/06/15/droid2-global-gingerbread-starts-rolling-out-today/
This is the latest. Its rolling out today. slowly. I wish someone would just get the SBF and we can flash it.
Click to expand...
Click to collapse
I'm pretty sure it would be an update.zip file, not an sbf file, but all the same it would be nice if someone would just copy it to their pc before updating so we could all have it already.
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
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?
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
So, its been what, four months since 4.1.2 hit the servers? Any idea why my lowly i9020A hasn't gotten her OTA?
Fylk said:
So, its been what, four months since 4.1.2 hit the servers? Any idea why my lowly i9020A hasn't gotten her OTA?
Click to expand...
Click to collapse
Who is your carrier? My impression is that OTAs are determined by the carrier, not Google. My i9020a is with Rogers, and it has gotten it. Also, if you have a custom ROM, OTAs might be turned off. Do you have a custom ROM?
For some reason I have not gotten an OTA since the time of ICS. I am using the i9020A model of Nexus S on AT&T (US).
I have to either manually download the OTA link posted by someone else on XDA or flash the stock image from Google's server.
Try switch your phone into airplane mode>Manage Apps>Google service framework (something like that)>Force stop>Clear data>Switch off airplane mode>Connect to wifi >Settings>About phone>Check whether you get your 4.1.2 ota update or not.
I tried this method twice when I didn't receive my 4.1.1 and 4.1.2 ota updates,and it works.Hope this helps you.
Sent from my Nexus S using xda premium
I have the same problem in my Nexus S. It received the OTA notification but failed in the middle of the installation process. After some reading. I found out that the installation process first checks for the ROM image signature; if it is not the original ROM, it won't proceed.
In my case, I have it rooted and installed a custom ROM. I ended up have to install the upgrade myself. It is quite simple. just search for it and you will find all the instructions.