I tried searching for a solution, but I was unable to find one. If such a thread exists, I apologize.
I recently got a used Sprint Galaxy Nexus. The day I got it, after factory resetting and getting stock, unrooted 4.0.4, I was prompted for an update, and of course accepted. While rebooting after the update, I got the image of the android with the red triangle/warning symbol. So after waiting for a bit, I took out the battery. Everything rebooted as normal. As I have learned in the past few days, that was the FD02 update, and upon checking my build number, I see that I am still on FC12. Earlier today I got another prompt to update, and once again it failed to reboot. I have noticed that 3g reception has been rather poor, and it is to my knowledge that that is precisely what FD02 is supposed to address.
If anyone has any solutions as to why a stock, unrooted device cannot complete an OTA update, I'm all ears.
Thank you
Flash the fc12 modems listed in the ota fix sticky thread in the sprint galaxy nexus Dev section.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks lol. I was looking only in this subforum, and didn't even notice there was one specifically for Sprint GNs. I'm dumb.
Related
This morning I got the message to update to the EL26 or whatever it is. I clicked to update. I don't know if it finished or not, or what happened. But I clicked on my About Phone section and everything says the same thing it said before. But my internet on my phone is worse than it was before. Anyone else have this issue? Is the update good to have? How can I try to update again?
Sent From My Sprint Samsung Galaxy SII - Epic 4G Touch
is your phone rooted? i used the method they have in the general section and just used cwm to installed the update. havent noticed many different things but i havent messed with my phone that much today.
MissLaniS said:
This morning I got the message to update to the EL26 or whatever it is. I clicked to update. I don't know if it finished or not, or what happened. But I clicked on my About Phone section and everything says the same thing it said before. But my internet on my phone is worse than it was before. Anyone else have this issue? Is the update good to have? How can I try to update again?
Sent From My Sprint Samsung Galaxy SII - Epic 4G Touch
Click to expand...
Click to collapse
Well MissLani it sounds like your update did not go through... When you go to about phone, under build number does it say GINGERBREAD EK02 or does it say EL29? If you still see EK02 (which will also be seen somewhere in the baseband version, and kernel version) than the update did not go through. If it says EL29 they you are good to go with the newest update. It is somewhat controversial on whether or not the update is good to have. Some people have better results on EK02 and others see some improvements on EL29. I am running EL29 and prefer it over the EK02.
Wife got update message and bricked her stock phone. She is out of town, so I did not get a chance to investigate. Sprint store replaced it. New one updated without issue.
Sent from my Transformer Prime TF201 using Tapatalk
It still says EK02. & now my battery won't charge anymore. Have had it plugged in for hours and it still says 5%. Tried different charger. Same thing. It shows that it is charging. But keep getting critical battery low message.
Sent From My Sprint Samsung Galaxy SII - Epic 4G Touch
Sounds like something may have gone wrong during the upgrade process. You may have to take it to a Sprint store and have it replaced. I'm assuming you havn't rooted.
No, I am rooted.
I can't even use my Back up app to save everything, cuz as soon as it starts, the phone shuts off. It charged yesterday. Just woke up & now it won't charge anymore.
Sent From My Sprint Samsung Galaxy SII - Epic 4G Touch
MissLaniS said:
No, I am rooted.
I can't even use my Back up app to save everything, cuz as soon as it starts, the phone shuts off. It charged yesterday. Just woke up & now it won't charge anymore.
Sent From My Sprint Samsung Galaxy SII - Epic 4G Touch
Click to expand...
Click to collapse
Try Titanium Backup and see if that works, if not, you can also save your App's as APK's through APPs backup program, which isn't bad, though you won't get to save the apk's data.
If none of this methods work out for you, then do a full system recovery *restore* and try to update before reinstalling all your things, then after the update, just do a soft/hard reset to make sure any lil data is gone, and you'll start fresh with EL29
Yah my phone will not hold a charge at all anymore. I'm prolly gonna have to take it to sprint store later..
What do I need to do so that they don't know I rooted my phone? How do I get it back to original state?
Sent From My Sprint Samsung Galaxy SII - Epic 4G Touch
Hi XDA,
I'm new to Android (first Android phone), and have never done any unlocking/rooting/etc. I've been working in iOS-land for 4 years, but wanted to try something new and refreshing.
I'm trying to figure out why my TELUS GSM Galaxy Nexus is stuck on 4.0.1? If my searching/reading is correct, it sounds as though the factory build they put on isn't eligible (yet) for the update, so you have to put on a different ROM entirely? (the yaku...something).
I thought the updates were pushed out by Google, not the carrier (e.g. TELUS/Rogers/Fido/etc). Why is everyone else running 4.0.2 or later (I know CDMA is even farther ahead) and I'm stuck at 4.0.1? And if CDMA is all the way up at 4.0.4, why isn't GSM? Wouldn't the people implementing bug fixes, etc, be updating for both platforms simultaneously?
I was oping factory updates would come quicker? I never wrecked any of my iOS devices (came pretty close, but eventually mastered DFU mode, pwning, and worst case scenario, rolling back to stock iOS 4 or 5). If I brick my Nexus though, I'm going to be in a world of hurt.
jasphair said:
Hi XDA,
I'm new to Android (first Android phone), and have never done any unlocking/rooting/etc. I've been working in iOS-land for 4 years, but wanted to try something new and refreshing.
I'm trying to figure out why my TELUS GSM Galaxy Nexus is stuck on 4.0.1? If my searching/reading is correct, it sounds as though the factory build they put on isn't eligible (yet) for the update, so you have to put on a different ROM entirely? (the yaku...something).
I thought the updates were pushed out by Google, not the carrier (e.g. TELUS/Rogers/Fido/etc). Why is everyone else running 4.0.2 or later (I know CDMA is even farther ahead) and I'm stuck at 4.0.1? And if CDMA is all the way up at 4.0.4, why isn't GSM? Wouldn't the people implementing bug fixes, etc, be updating for both platforms simultaneously?
I was oping factory updates would come quicker? I never wrecked any of my iOS devices (came pretty close, but eventually mastered DFU mode, pwning, and worst case scenario, rolling back to stock iOS 4 or 5). If I brick my Nexus though, I'm going to be in a world of hurt.
Click to expand...
Click to collapse
Id like to know this too. Im on Rogers and have the Rogers version of the GNEX and it too came with v4.0.1
I have since rooted, etc and flashed a custom 4.0.3 ROM (see signature for info) but I seem to be having some network issues (bug in 4.0.3 custom ROMS) which may FORCE me to go back to stock and if I do then Id definitely like to know WHY we have not received any Official updates to our devices as of yet...
Your updates are coming from google not your carriers. However Samsung is in charge of ensuring the update works in certain regions hence the delay.
Sent from my Galaxy Nexus using XDA App
yiannisthegreek said:
Id like to know this too. Im on Rogers and have the Rogers version of the GNEX and it too came with v4.0.1
I have since rooted, etc and flashed a custom 4.0.3 ROM (see signature for info) but I seem to be having some network issues (bug in 4.0.3 custom ROMS) which may FORCE me to go back to stock and if I do then Id definitely like to know WHY we have not received any Official updates to our devices as of yet...
Click to expand...
Click to collapse
Google hates Canada.
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
ray2jerry said:
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info but as I mentioned, I am already running a Custom 4.0.3 ROM but I seem to be having signal drop issues with it so I may have to flash something else to fix that as I have read that these signal drop issues are 4.0.3 AOSP ROM related...
ray2jerry said:
For what it's worth when I got this phone from Virgin Mobile just before Xmas it was yakjuyx or whatever and 4.0.1. Minutes after turning it on it upgraded OTA to 4.0.2 so they are pushing updates in Canada, even 'Samsung controlled' builds.
That said it's not a concern after installing a custom yakju ROM already at 4.0.3. So either you wait patiently for OTAs that may or may not come or take control of your own device ;-). Remember, it can all be put back where it was!
rAy
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That can't be right. The only OTA update that went out for yakjuux was the volume fix update. I've never heard of anyone getting 4.0.2 that had yakjuux. The first batch of phones that came out in December received that volume update but it stayed 4.0.1. Any phones bought recently already came with the volume update applied.
So I just bought the GSM version of the Galaxy Nexus. It is yakju and I am using it with AT&T. No matter how many times I've tried I cannot get the phone to do an OTA update to at least 4.0.2, let alone 4.0.4. So I have a couple questions, keeping in mind that I am not particularly interested in rooting and would rather just do an OTA update.
1. Will the 4.0.2 update eventually come through if I wait? I don't mind waiting, but I don't want to wait indefinitely without making any progress.
2. If I do want to or need to do a manual update, can I go straight from 4.0.1 to 4.0.4?
Like I said, I would prefer to wait for the OTA update as I'm having no issues with 4.0.1 right now.
On a completely unrelated note, I have 14 days to return this phone. If you were me, would you return it and wait for the One X. I like the idea of having a raw android Google phone, but the One X seems attractive.
I think you should get an iphone.
iphone. helping computer illiteracy become popular since 2007.
I received my Nexus about a week ago. Within 5 minutes of turning it on I received the 4.02 OTA update. 10 minutes later I was rooted and running CM9 so I can't say if I would have received the 4.04 OTA update.
Sent from my Galaxy Nexus using xda premium
get stock images and flash to 4.0.4.
search the forums on how to do that.
rsawlani said:
Like I said, I would prefer to wait for the OTA update as I'm having no issues with 4.0.1 right now.
Click to expand...
Click to collapse
Then just wait for the OTAs.
On a completely unrelated note, I have 14 days to return this phone. If you were me, would you return it and wait for the One X. I like the idea of having a raw android Google phone, but the One X seems attractive.
Click to expand...
Click to collapse
There are already lots of spammy nerd bashing threads on this topic. No one can make this decision for you.
You have a few options....
1. Download Factory images for 4.0.4 from Google and use Galaxy Nexus Toolkit to flash (you will lose all your data and pictures, videos, music)
2. Root your phone (you'll still lose your data because you have to unlock your bootloader)
3. Wait for the 4.0.2 update than the 4.0.4 update
Your choice
When you get the HTC One X you gonna be saying how much you wish you had AOSP
Sent from my GT-P7510 using xda premium
YoungAceAtlanta said:
You have a few options....
1. Download Factory images for 4.0.4 from Google and use Galaxy Nexus Toolkit to flash (you will lose all your data and pictures, videos, music)
2. Root your phone (you'll still lose your data because you have to unlock your bootloader)
3. Wait for the 4.0.2 update than the 4.0.4 update
Your choice
When you get the HTC One X you gonna be saying how much you wish you had AOSP
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Or when Android 5.0, "when will One X be getting Android 5.0?!"
Same Here
I guess were both on the same boat Except i am on Tmobile. As soon as i unboxed and setup my Gnex this past friday i was expecting an OTA update to 4.0.4. But appearantly that wasn't the case as i am still stuck on 4.0.1 two days later. I am really hoping i get that OTA soon...there is no way i am rooting ever again. My last phone which was a Samsung Vibrant had a custom ICS rom...everything was well until i was greeted by the deadly "Encryption Unsuccessful" screen not knowing what to do i hit reset phone. 1 min later my phones only use was as a door stop.
I know this may sound kind of silly but maybe we haven't received our updates because its the weekend . Im waiting till monday to see if i get the OTA update. Hopefully it arrives soon.
Merio90 said:
I guess were both on the same boat Except i am on Tmobile. As soon as i unboxed and setup my Gnex this past friday i was expecting an OTA update to 4.0.4. But appearantly that wasn't the case as i am still stuck on 4.0.1 two days later. I am really hoping i get that OTA soon...there is no way i am rooting ever again. My last phone which was a Samsung Vibrant had a custom ICS rom...everything was well until i was greeted by the deadly "Encryption Unsuccessful" screen not knowing what to do i hit reset phone. 1 min later my phones only use was as a door stop.
I know this may sound kind of silly but maybe we haven't received our updates because its the weekend . Im waiting till monday to see if i get the OTA update. Hopefully it arrives soon.
Click to expand...
Click to collapse
Most OTAs roll out in groups. Well at least from the last time I did a OTA .. I guess thats how they still work. Only so many users get them at a time. Not everyone who has a gnex get it at once
Sent from my Galaxy Nexus using xda premium
YoungAceAtlanta said:
Most OTAs roll out in groups. Well at least from the last time I did a OTA .. I guess thats how they still work. Only so many users get them at a time. Not everyone who has a gnex get it at once
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Now that I see other people having this problem, I think OTA updates for 100% stock Android 4.0.1 Samsung i9250 Galaxy Nexus are just not happening at all for now... (verbiage/garbiage deleted
As for my Nexus One(s)... (I'll just say I never saw this happen)
EDIT:
At about 8pm MDT (GMT-06:00) in the US, my i9250 finally updated from 4.0.2 to 4.0.4. I consider this an important validation of the integrity of my device. Earlier today I flashed 4.0.2 but still had to wait.
So clearly there was a period of days (March 30 to April 2 at least) that OTA updates where not happening for the i9250. This was alarming because I've rolled my i9250 back to 100% stock Android 4.0.1 several times after playing with different ROMs. Each time it quickly updated to 4.0.2. This time it took a few days. For a while I was worried my phone had a problem.
I just rolled back to a stock ROM 4 days ago.
But did only get 1 OTA update immediately after first boot. The one from ITL41D to ITL41F (4.0.1).
No OTA to 4.0.2 or even 4.0.4 yet. (All imgs are stock ITL41F with locked bootloader of course)
First, I apologize if there's a thread with an answer... I was unable to find one.
I’ve got a big problem with my phone…sorry for the long post, but I want to get as much info in as possible.
I have been trying to regain access to the cellular network since about 8am today (eastern time). I noticed my lack of signal when I got to work. Yes I’m in a basement, but I haven’t had problems before. I will see everything from blue bars with the 3G logo to a triangle with an x. In any case, I am unable to send or receive phone calls, text, or mms. I have a Samsung Galaxy Nexus on Verizon.
At first I thought I needed a reboot. Then a battery pull. After no luck, I thought that maybe I needed a fresh start. I have had 4 or 5 ICS-based ROMs and quite a few custom kernels, and most recently I’ve been playing with Jelly Bean. I thought that perhaps I had some leftover junk scattered about and figured that I would just format my SD card and start from scratch.
The long and short of the next part is that basically I put my phone back to stock settings, tried JellyBelly and CM9 RC1 after the 4.0.4 OTA update, but still no service! So now I’m back to stock again. The bootloader is unlocked, however I cannot root my phone. And I still cannot text or call. I have signal bars lit up, as well as 3G and am actually using Google Talk on 3G.
Mobile network is on, and set to LTE/CDMA. Aside from this morning, I haven’t flashed anything since Thursday (6/28/12). I cannot boot into recovery with ClockworkMod or Optimus Prime Touch- that just yields a picture of Andy with his chest open and a red triangle I’ve tried just flashing the radio, too. But that doesn’t seem to get me any results. I read about people having problems with their SIM cards so I pulled and reseated mine. That didn’t help, either….
I’m getting flustered and don’t have any other ideas. Could someone help me breathe the rest of the life back into my phone? I have no idea which directly to go now.
Thanks!
-Sarah
EDIT: Can't use 3G for Gvoice/talk now. boo
Probably your network. I'm having the same issues, but that's because the towers are down due the the crazy storm we had on Friday.
Sent from my Galaxy Nexus using xda premium
Anyone else on Verizon in your area having the same issues?
cundiffr said:
Probably your network. I'm having the same issues, but that's because the towers are down due the the crazy storm we had on Friday.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I hope so... I was able to call and text once I got out of the basement though. This morning, as soon as I step in, I'm getting the same thing.
consultant.ben said:
Anyone else on Verizon in your area having the same issues?
Click to expand...
Click to collapse
One of my friends did yesterday, but only for a short time. He also has a Gnex. However, he was able to fix it by flashing a new JellyBean ROM. Only one of my coworkers is on Verizon, but he didn't have any issues here. He's got an iPhone.
Only one of my coworkers is on Verizon...he has been experiencing issues trying to text, but can still make calls.
I have finally restored my phone back to the JellyBean ROM, but still have no service
Just thought I'd update the thread.
Have had my nexus now for several months. Its a uk simfree direct from amazon.co.uk. yakju, gsm, Its stock, un rooted.
Originally it was running 4.0.2 and ran perfectly. But since the it picked up the 4.0.4 ota update (just after the release) i get freezing and random reboot issues while its in standby (never happens when i am using it). After reboot there is often a hole in my battery log (see attached pic).
The freezing is a big issue has i have to take out the battery to bring it back to life.
If this is a common issue then i will stick with it, but if not them i will have to return it. I don't want to root or load an alternative rom because i don't think i should have to just to get a reliable phone.
I have removed most of my apps to see if that helps, but i didn't have that many anyway and most of those are google own.
I would appreciate thoughts!
Sent from my Galaxy Nexus using xda premium
i have a samsung galaxy nexux with 4.0.4, too and it works perfect. it sounds like a hardware defect for me..
No other opinions?
Sent from my Galaxy Nexus using xda premium
Easiest way to find out if it is hardware related, is to start from scratch: flash the factory image and see if you still have the freezing. If not, it is some app or some setting you changed. If you still have the freezing, it's probably hardware related.
Well since i had jelly bean ota, no freezing or reboots :thumbup:
/touchwood
Sent from my Galaxy Nexus using xda premium
I feel better after finding this thread--at least now I know my experience is not totally unique.
The same thing happened to my wife's Galaxy Nexus, which came as a yakjuwx 4.0.2. After applying the OTA update to 4.0.4, the phone will invariably reboot by itself within 30-40s in standby. The Samsung service centre (in Singapore) even took the trouble to change the motherboard (so they claimed) but that didn't resolve issue. But since they only have the 4.0.2 ROM on hand and will always flash the device back to that, and since the phone does not exhibit the problem in 4.0.2, the problem is solved as far as they are concerned. After discussing a bit with one of their engineers, he even advised me to hold off updating to 4.0.4.
The amazing thing is that the same pattern of problems persist even if I flash the phone to the Google factory images (yakju). The phone will be fine in yakju 4.0.2, but not after the OTA update to either 4.0.4, or 4.1.1. This suggests that there is something hardware related involved, but there's no way for me to prove it.
Currently, the phone is running Google factory image yakju 4.0.2 without problems. To stop the OTA notification from shoping, I've rooted the device, used Root Explorer to (1) delete the OTA update file in /cache and (2) renamed system/etc/security/otacerts.zip to otacerts.zip.bak. After one restart, I said "yes" to the update notification, which then immediate shows that the phone is up to date, and it has not been bothering since. Since my wife is not big on the 'latest and biggest' upgrades, this seems an acceptable solution for her.
This obviously happens only to some Galaxy Nexus. My own device, an identical yakjuwx 4.0.2 model, updated OTA to 4.0.4 without any issues. It was subsequently upgraded unofficially to yajku 4.1.1 and ran well for a week. But something else happened--it heats up while simply refusing to charge--and it's also returned for servicing. Sad to say this but I'm slightly regretting going with the two Nexus...
(*Incidentally, for all their inability to solve the problem at a more fundamental level, and more strangely, their lack of the facility to install the yakjuwx 4.0.4 update themselves, the Samsung service centre people in Singapore have been very friendly and helpful. They were also very lenient with the warranty--I didn't have a proper receipt as the phone was purchased second hand but they accepted it on the basis of the serial number. Furthermore, they didn't make any comment about the fact that the bootloader was unlocked. It seems their policy to simply flash any phone given to them for servicing back to factory yakjuwx 4.0.2 no questions asked, before proceeding with further tests. I was warned, of course, that any phones left with them will be wiped.)
I had no issues with 4.0.2, it was only 4.0.4 that seemed to be a problem for my device.
Uptime now 275 hours on 4.1.1 :thumbup:
Sent from my Galaxy Nexus using xda premium