This is the official OTA update zip for the sprint galaxy nexus from Fc12 to FD02:
http://android.clients.google.com/pa...12_to_FD02.zip
How to manually update:
coming soon
I can't wait. I'm rooted and hope this manual update is better than the error 7 I'm getting doing the auto update.
Actually thought I would add that I did the odinn back to stock and you know what?
The update STILL doesn't apply.
Same dumb old error 7
Last edited by Raxethorian; 05-03-2012 at 01:42 AM.
Can't manually update since it flashed a new recovery, i think this ota is messed up not sure.
Sent from my Nexus S 4G using Tapatalk 2
They have a zip on here http://nexuscm.blogspot.com/2012/05/...io-images.html that you can flash through recovery
I forgot to mention it was for radio only my bad. I got them from the SPRINT Galxy Bexus CM google + page https://plus.google.com/103634938164...ts/bPK3hr2Gz4G
Using the FC12-FD02.zip posted at Cyanogenmod Nexus blog site partially works after a return to stock FC12 odinn restore.
The good news is that until 4G LTE is available in Salt Lake City, I now have 3g data!
So thank you for that at least.
Oh well, nothing ventured nothing gained.
I now have L700.05 V.FD02/L700.FC12
A hybrid radio setup, for crying out loud in the night.
Today's update on Cyanogenmod Nexus blog site 5-4 has this new message:
"Update 5/4/2012: Fixed FC12 and FD02!
People who had flashed the FD01 or FC12 leaks from the forums experienced an inability to install the official FD02 OTA upgrade from Google. This issue can now be easily fixed with the images below. Either use CWM or fastboot to clean flash FC12 then OTA should work thereafter. If you use CM9 or other custom ROM's, you can flash directly to the latest version FD02. Be warned that flashing CDMA takes almost 2 minutes."
I was able to use CWM and flashed the radios successfully to FD02.
Using LTE/CDMA ota SpeedTest.net averages 2.1 Mbps on download, 1.10 Mbps up. Ping averaged 160ms.
I'm happy.
Anyone know if qbking77 is still going to post a manual update vid given the problems with this update?