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.
Related
[Q] I'mgetting "Error in /tmp/sideload/package.zip" when I try to update my Nexus S
I've searched countless times on how to fix this, yet every time I find a thread containing someone asking about this they never answer it or they're dealing with a rooted device.
My device is not, and has never been, rooted. Never manually updated anything on the phone before trying now.
I tried to manually update to 2.3.3 after never receiving the OTA. Then I tried the 2.3.4 update and I keep getting the "Error in /tmp/sideload/package.zip" message.
Can someone explain, or point me in the direction, of a non-rooted answer. Why am I getting this message to begin with?
Do you own the European version? The SLCD 19023 one?
No, it's the American version.
It's weird because I received the 2.3.2 update. But aftr that...I never got the 2.3.3 pushed to me. And now when I try to manually update to the .3 or .4 update...I keep getting that message.
Vandam500 said:
Do you own the European version? The SLCD 19023 one?
Click to expand...
Click to collapse
No, it's the American version.
It's weird because I received the 2.3.2 update. But aftr that...I never got the 2.3.3 pushed to me. And now when I try to manually update to the .3 or .4 update...I keep getting that message.
me too. the same problem with my Nexus S
And me too, Davey. Same problem. Bought the Nexus S in New York on late December and I live in Spain. My phone is unrooted.
Haven't received the OTA for 2.3.3 yet and tried both manually updates for 2.3.3 and 2.3.4, but getting the same message as you.
It's frustrating!
Same problem here with a UK-bought Nexus S. I have tried with the bootloader Locked and Unlocked. Although bought in UK there is no guarantee that it is not an American import. It was bought from Carphone Warehouse who seem to source their kit from any where they can get it.
So as other people are successfully installing it has to be something specific to this physical handset.
Hands0n said:
Same problem here with a UK-bought Nexus S. I have tried with the bootloader Locked and Unlocked. Although bought in UK there is no guarantee that it is not an American import. It was bought from Carphone Warehouse who seem to source their kit from any where they can get it.
So as other people are successfully installing it has to be something specific to this physical handset.
Click to expand...
Click to collapse
So from the few posts here it's seeming like an international device issue...but yet I'm in the States. So I don't get it.
It's just frustrating that I can't get an answer about it. Many a people are speaking on it, but nobody can explain or solve it. Sigh.
Same issue as you - error in /tmp/sideload
I have Nexus S 2.3.3 (manually updated) from US. I am trying to manually bump it to 2.3.4 -- same issue. I have rooted & unlocked the device. No Mods here.
Same error.
Baseband is I9020XXKB1
Kernerl - 2.6.35.7-g1d030a7 [email protected] #1
Build GRI40
Updated!!!
OK guys -- Finally figured out the problem for /tmp/sideload/package.zip.
If there is any change to the bootloader by any app (RomManager or has ClockWorkMod), then you won't be manually be able to upgrade to 2.3.4
Solution for those on GRI40 2.3.3
1. Flash stock 2.3.3 gingerbread again in recovery more. Do a quick search on XDA and grab it. Almost 90 MB file.
2. Once flashed - Boot it, sign in with google account and under setting, privacy - do a factory data reset. Start it clean. I DID NOT checked the SD card data.
3. Flashed 2.3.3 in recovery again.
4. Reboot it. Did not signed in once booted. Turn USB ON. Put the 2.3.4 file (around 12 MB).
5. Flash it again in recovery mode.
6. I signed in to Google account without restoring my backup.
That's it. On 2.3.4 - Unlocked state remains!
Hi there!
Finally managed to install the 2.3.4 version on my Nexus S and works perfect! Already tried the Google Talk video chat and it's fantastic.
You can find all the instructions and the update files in the following link (thanks to the impaler for that):
http://forum.xda-developers.com/showthread.php?t=1055950
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
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
Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?
Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
AvataroftheSun said:
Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?
Click to expand...
Click to collapse
I had to Odin back to stock and go get a new SIM card from Verizon... Got the OTA instantly after the new sim was put in... It's a known issue
Sent from my SCH-I535 using xda app-developers app
annoyingduck said:
Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Click to expand...
Click to collapse
Mm, checked those out, and scrosler says that the bootloader needs to be unlocked, and doesn't provide any other information on how to flash it properly (Odin vs. custom recovery). Though if it's stock, it shouldn't matter...
I odin'd back to root66 and it took the update as soon as i checked for it. (and I dont even live in Verizon coverage)