I got my phone a few days ago and it came with ICS installed already on it. Well today I went to my settings and hit software update and there is an update out there for my phone but when I got to install it the phone reboots into CWM.
The file size is like 46551kb. Anyone have any idea what this update is for?
catchjeff said:
I got my phone a few days ago and it came with ICS installed already on it. Well today I went to my settings and hit software update and there is an update out there for my phone but when I got to install it the phone reboots into CWM.
The file size is like 46551kb. Anyone have any idea what this update is for?
Click to expand...
Click to collapse
read this on the update http://forum.xda-developers.com/showthread.php?t=1956299
Related
I received the prompt finally to update to 2.3.2 so when I hit the button and my phone rebooted I got the triangle with the ! inside so I had to do a battery pull. Any ideas why this happened and will the OTA come back? I never even received the new market ota either. I'm rooted and stock.
Sent from my Nexus S
Bronk93 said:
I received the prompt finally to update to 2.3.2 so when I hit the button and my phone rebooted I got the triangle with the ! inside so I had to do a battery pull. Any ideas why this happened and will the OTA come back? I never even received the new market ota either. I'm rooted and stock.
Sent from my Nexus S
Click to expand...
Click to collapse
Many others have reported this and had a simple fix for it. Can't remember it but you should search.
Bronk93 said:
I received the prompt finally to update to 2.3.2 so when I hit the button and my phone rebooted I got the triangle with the ! inside so I had to do a battery pull. Any ideas why this happened and will the OTA come back? I never even received the new market ota either. I'm rooted and stock.
Sent from my Nexus S
Click to expand...
Click to collapse
I had the same problem just now, so I rebooted the phone and tried to update it manually. When doing it manually, it gives an error message telling me what went wrong. It turns out that the modified Gallery 3D apk that I installed was the cause of the problem. When I reverted to the original Gallery apk, the update went through without a hitch.
How did u do it manually? Flashing a zip file?
Sent from my Nexus S
Bronk93 said:
How did u do it manually? Flashing a zip file?
Sent from my Nexus S
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=923860
Bronk93 said:
I received the prompt finally to update to 2.3.2 so when I hit the button and my phone rebooted I got the triangle with the ! inside so I had to do a battery pull. Any ideas why this happened and will the OTA come back? I never even received the new market ota either. I'm rooted and stock.
Sent from my Nexus S
Click to expand...
Click to collapse
Had the exact same issue.
I followed this thread which solved my problem : http://forum.xda-developers.com/showthread.php?t=923860
My Nexus S user experience has been LAME so far :
- Laggy UI
- Having to wait 10 days for a 601kb update
- Bugs after update (got stuck on the yellow triangle screen)
- Unable to modify my damn contact icon in SMS threads
Welcome to the pure Google world
theophane said:
Had the exact same issue.
I followed this thread which solved my problem : http://forum.xda-developers.com/showthread.php?t=923860
My Nexus S user experience has been LAME so far :
- Laggy UI
- Having to wait 10 days for a 601kb update
- Bugs after update (got stuck on the yellow triangle screen)
- Unable to modify my damn contact icon in SMS threads
Welcome to the pure Google world
Click to expand...
Click to collapse
Actually its more like welcome to the cutting edge. There is a reason why manufacturers wait and do so much testing before releasing updates. Not to say google doesn't but the more people you have testing the easier it is to find problems and fix them.
theophane said:
My Nexus S user experience has been LAME so far :
- Having to wait 10 days for a 601kb update
Welcome to the pure Google world
Click to expand...
Click to collapse
Oh, yes, because it's so much better to wait 5 months for an update that only brings you to the last version of the OS which was released 8 months ago (like the Vibrant just now getting Froyo)...
distortedloop said:
Oh, yes, because it's so much better to wait 5 months for an update that only brings you to the last version of the OS which was released 8 months ago (like the Vibrant just now getting Froyo)...
Click to expand...
Click to collapse
+1 10character
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
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
NevetsDrassel said:
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
Click to expand...
Click to collapse
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Jank4AU said:
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Click to expand...
Click to collapse
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
NevetsDrassel said:
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
Click to expand...
Click to collapse
I don't know how to permanently disable the update, but I'm sure there's a way. As info, I was able to easily fix my phone with the help of this thread posted by @thecubed: http://forum.xda-developers.com/showthread.php?t=2451696. I didn't read it all, but this might be what disables the update.
I'm not rooted. I took the latest update and all is fine. It's google+ fixes and Google wallet support. It actually let me set up tap & pay! I'll have to go somewhere to try it out.
Sent from my LG-D800 using Tapatalk
I got the notification too but figured that it would probably screw things up since I'm rooted and running TWRP so I did a little searching and came across this, http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3 . It's been a few hours since I changed the setting and haven't seen the update notification again although AT&T pushed the update into CACHE/FOTA sometime this morning.
Well scratch that, the notification just came back. I'll try freezing it now.
Well if rooted just use TB to freeze software update. I am also running a mixed partition D80020c. I am on Straight Talk AT&T. Before rooting I tried taking the official OTA of KitKat but for some reason you can't enter an APN type so I couldn't get or send MMS. So I flashed back to the D firmware,rooted,added custom recovery,entered the APN type and then flashed the modified C firmware. You could also use Root Freezer instead of Titanium Backup to freeze
Hi, yesterday I downloaded the new OTA update after the notificication about it appeared. But nothinh happened in the next four hours, there wasn't any notification of the download in progress or to install it. Today i tried to download it again but i can't: if i check if there is a new update in the setting, nothing happens. How can i solve this? Everything is stock on my phone, i haven't unlocked or rooted it.
Dario! said:
Hi, yesterday I downloaded the new OTA update after the notificication about it appeared. But nothinh happened in the next four hours, there wasn't any notification of the download in progress or to install it. Today i tried to download it again but i can't: if i check if there is a new update in the setting, nothing happens. How can i solve this? Everything is stock on my phone, i haven't unlocked or rooted it.
Click to expand...
Click to collapse
try offline update
Hi all,
Hoping this is an easy fix someone has seen before.
I have a used 16gb wifi version that I'm trying to update to 5.1.1.
The OTA download works OK, but when it says flash and reboot, the progress bar only gets about 20% along and then shows an "Error" message over the robot.
Wiped the download and redone the OTA a few times with same results.
Not so concerned about getting the update as I am in trying to figure out if the device is part of the recall or not.
I think that the system may have been loaded with a custom ROM by the previous owner but it looks to be put back to factory. Don't know if it is left in a weird state of locked/unlocked/rooted or not or if that should matter.
Thanks
Ron
Make sure you are getting the full update. Should be more than 700 mb. In system update click the 3 dots and select the full ota.
Resolved- Thanks
frenziedfemale said:
Make sure you are getting the full update. Should be more than 700 mb. In system update click the 3 dots and select the full ota.
Click to expand...
Click to collapse
Hey, thanks.
I found this just before your reply by accident when my son wanted to try the update ONE MORE time and hit the 3 dots by mistake. Just caught the word "full' before the window closed and went back to give that a try.
All the other devices in the house are Nexus so this new device was a bit of an anomaly that I wasn't used to.
Update worked just fine but now looks like we wait for the recall replacement to come in
BR
Ron