[Q] Stock ROM 4.0.2 won't update - Samsung Galaxy Nexus

I have an unlocked Nexus on stock rom 4.0.2. I haven't been using for a couple of weeks. Finally I decided it's time to sell it. So I charged it up and reset to factory settings. On restart it told me that there is an update available.
Sweet! Let's do it. The phone restarts, goes into update mode and then somewhere in the middle it fails. After a minute it restarts and works ok, but the OS is still 4.0.2
This happened about a week ago. Since that time it has asked me to update 3-4 times and has failed every one of them.
Anyone can suggest me how to deal with this? I just want to upgrade it to 4.0.4 via normal way.

why bother updating when your anyways selling it
and why ru selling it by the way ?? is it buggy,faulty or something ??
i dont have my nexus with me yet but i'll can advice clearing that setting (and data if available) from settings and try checking update >> apply update
or simply screw all that manually flash 4.0.4

You have an update for which variant on which carrier???
This could be a download issues that happens. It should eventually work. But I don't know which carrier your on and also there could be OTA traffic.

If you changed kernel /radios/Stock recovery for cwm/twrp /Stock system apps the ota wont work..
If you want to flash yakju or takju(Stock factory images) follow efrant's guide
here
Galaxy Nexus Stock + Franco m3

aish_varya said:
and why ru selling it by the way ?? is it buggy,faulty or something ??
Click to expand...
Click to collapse
I got a corporate iphone.
msedek said:
If you changed kernel /radios/Stock recovery for cwm/twrp /Stock system apps the ota wont work..
Click to expand...
Click to collapse
The only thing I did to that phone after unboxing it is rooting it. Nothing else has been changed.
DLD511 said:
You have an update for which variant on which carrier???
Click to expand...
Click to collapse
Not sure what do you mean by that. The update just pops up saying there is a new version available. The phone was bought in Czech Republic, it is not locked to any carrier.

It won't update if you don't have stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2

dobroezlo said:
[snip]
The only thing I did to that phone after unboxing it is rooting it. Nothing else has been changed.
Click to expand...
Click to collapse
If you "rooted" by flashing the root files using CWM, then you need to flash back the stock recovery for the update to work.
Sent from my Galaxy Nexus using Tapatalk 2

Related

Is ICS 4.0.2 latest?

So, I got my GN today and I just noticed that my OS is 4.0.2
Is that the latest and the greatest?
Sent from my Galaxy Nexus using xda premium
Without rooting yes.
Sent from my Galaxy Nexus using xda premium
A few quick questions about the phone you just got:
1) Was it made in China or Korea?
2) Is the build version yakju or something like yakjuwx/yakjusc/yakuux/etc? You can find this with the Android system info app
3) Who did you buy it from?
Thanks!
Got my 4.0.2 update today in the morning (an hour ago) as well.
1. How to check that? Sticker under the battery doesn't have that info.
2. Mine is "yakjuwx". What does it say?
3. I bought mine in Lithuania/Europe and not from a mobile operator but from official store. Box says that it's made in Korea and distributor - Poland/Europe.
BTW, what has been fixed in 4.0.2?
i believe it's the latest if you're unrooted.. no official update for 4.0.3 yet..
Also recieved 4.0.2 today and got yakjuxw
My phone (i9250) just downloaded the 4.0.2 update. Upon reboot it got stuck on that android busy screen. After about half an hour I removed the battery. I could then boot into Android normally. It's still 4.0.1 and now claims there are no updates available.
My phone is rooted using the WugFresh method, but I did not install any custom ROM. Is it to be expected that a rooted Galaxy Nexus would fail OTA updates?
wirtzpeitz said:
My phone is rooted using the WugFresh method, but I did not install any custom ROM. Is it to be expected that a rooted Galaxy Nexus would fail OTA updates?
Click to expand...
Click to collapse
Have you changed the radio or recovery?
I have 4.0.1. Bought in Norway. Build is ITL41F.I9250XWKK9
aquavalanche said:
i believe it's the latest if you're unrooted.. no official update for 4.0.3 yet..
Click to expand...
Click to collapse
not an official OTA, but the official 4.0.3 update itself is right there on google's servers for any nexus user to build for themselves. Build your own zip.
There was rumor/speculation of another update release by the end of January.
Well it's February so rumours are rumours. Not being a smartass or anything. I hope we get the update soon. Some glitches are inconvenient.
Sent from my Galaxy Nexus using xda premium
Are updates carrier-centric? My phone reports that there are no updates, and I'm on 4.0.1.
ChazzMichaelMichaels said:
A few quick questions about the phone you just got:
1) Was it made in China or Korea?
2) Is the build version yakju or something like yakjuwx/yakjusc/yakuux/etc? You can find this with the Android system info app
3) Who did you buy it from?
Thanks!
Click to expand...
Click to collapse
1) dont know
2) where do I see that?
3) VerizonWireless
a1exus said:
1) dont know
2) where do I see that?
3) VerizonWireless
Click to expand...
Click to collapse
He is talking about the GSM model, you have CDMA.
I hope they release the OTA soon... it's so laggy....
wirtzpeitz said:
My phone is rooted using the WugFresh method, but I did not install any custom ROM. Is it to be expected that a rooted Galaxy Nexus would fail OTA updates?
Click to expand...
Click to collapse
If you used the WugFresh tool kit to unlock and root your phone, then it installed ClockworkMod Recovery. Having CWM on your phone will prevent it from receiving OTA updates.
IMHO if you've unlocked and rooted your phone, it's time for a custom rom. There are some really good, stable roms out there using 4.0.3. And the developers update far more frequently than you'd recieve OTA updates.
Don't be scared, the developers have made it as easy as they possibly could. Before a month ago, I'd never run anything but a stock phone. I'm still a complete noob, but I've run three different custom roms, flashed kernels, radios, and added mods... Just follow directions, always back-up, and if things get hairy, you've a large community of really smart people who are willing to help.
diegodbm said:
I hope they release the OTA soon... it's so laggy....
Click to expand...
Click to collapse
Considering they haven't even started rolling out 4.0.2 in some regions, I think we have a bit of a wait on our hands.
Ridel said:
Are updates carrier-centric? My phone reports that there are no updates, and I'm on 4.0.1.
Click to expand...
Click to collapse
Its region-specific. Read up on this whole argument over "yakju" vs "yakju**" phones.

Got OTA notification but....

...I downloaded the 4.0.4 update and went to install and reboot. But the phone got stuck at the screen with the android belly up and a exclamation point. Pulled the battery and rebooted and was at 4.0.2 still. Haven't gotten another OTA notification. Do I get another OTA alert or do I have to update manually.
I have a GSM Nexus, rooted but with stock 4.0.2. And I activated OTA RootKeeper before downloading the update. Any help will be greatly accepted.
Sent from my Galaxy Nexus using Tapatalk
Besides root and maybe unlock your bootloader, did you change anything in your system (install mods, different radio etc. or rename system files)? If you are not completely stock your OTA will not work and you will have to update manually or get back to Stock first.
Sent from my Galaxy Nexus using xda premium
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Well the screen you were looking at (Android belly up) is the stock recovery. If you see that: no need to pull battery. Simply push volume up + power simultaneously and you'll get into the recovery menu. Scrolling through the options can be done with the volume buttons, select with the power button.
That said: I think no one knows for sure but I myself would not wait and update myself. There are a lot of guides here on how to do that and if you flash the stock images you will have the same as anyone who had the OTA. Make a proper backup first (you allways should)! You will lose all your data if you have to unlock your bootloader.
Sent from my Galaxy Nexus using xda premium
jrodsep said:
Nothing changed. Except for root and unlocked bootloader everything is stock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
stuu.f said:
Have you installed CWM recovery installed?
The "belly up" android is the phone trying to boot in the stock recovery to update the phone. But as you may have CWM recovery installed (which replaces the stock recovery) the phone cannot complete the update.
You will need to re-install the stock recovery. I believe you can do this with the GNex Toolkit.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Is it possible to get the Stock Recovery Screen when you have CWM installed? Didn't think that was possible... that it would just boot into CWM recovery. That is why I didn't mention it (trying to learn here).
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Lex_Michdeandroid said:
Same problem here. Stock 4.0.2, rooted, CWM installed.
Does this mean we will lose settings before we are able to update the device?
Click to expand...
Click to collapse
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Viridis Draco said:
this mean you are not eligible for the OTA update mate, because you have a custom recovery
i suggest you to
flash the stock rom manually
flash a custom rom wih 4.04 inside
my 2 cents
Click to expand...
Click to collapse
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
I don't even understand why I have CWM installed in the first place. I only neet root acces, all the rest can stay stock for all I care... Is there a way to avoid these problems in the future? So be able to root and OTA at the same time?
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Viridis Draco said:
custom recovery is needed in order to install custom ROM dude, is quite simple
and yes, you can root the stock ROM without custom recovery, there are a lot of guide about that in the developer section
Click to expand...
Click to collapse
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Edit: would it be easier if I just get the stock recovery back and then try to get the OTA to turn up again?
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
So my only option to fix this now is flash 4.0.4 manually (will I lose stuff?) and then root again and get stock recovery back? Sorry for my n00b questions, thanks for your help!
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Viridis Draco said:
you have nothing broken mate, i can't tell you if you will lose data, it depend on your ROM, what you flash and mainly how
the Force and the Developer Section is with you, young padawan
damn, i'm playing SW:TOR too much:/
Click to expand...
Click to collapse
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Lex_Michdeandroid said:
Thank you master for your soothing words. I just want my Galaxy Nexus to be like he is right out of the box, but rooted. Thats all I need from him... I am guessing my girlfriends Nexus S is going to be a pain in my assholes in a few weeks bc its still on GB and my TF101 will also go haywire because of my rooting adventures...
First this GN nuisance... Guess I am going to have to wait until tomorrow, I am flying to Dublin in about two hours and I don't think I can fix this in time...
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
i agree, take your time and you wouldn't regret it
I want to manually flash 4.0.4 and stay unrooted. Should I use the GNex Toolkit to flash 4.0.4 directly or do I need to flash the same version I have on my phone?
Sent from my Galaxy Nexus using Tapatalk
I had the same issue described by the OP, the belly up android when trying to update to 4.0.4 from the OTA notification. I had previously changed to 4.0.2 yakju using efrant's instructions from the first post in this thread: http://forum.xda-developers.com/showthread.php?t=1391881
However, I had skipped the optional sections. In particular step 12 to flash the recovery partition. I went back and just executed step 12 (fastboot flash recovery recovery.img) and rebooted. Then I was able to update to 4.0.4 successfully from the OTA notification.
I'm guessing I didn't have the "stock recovery" because I previously had the default Samsung version?
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Lex_Michdeandroid said:
Just got the update again OTA, and again the belly up droid. I'm really pissed now, bc it also reset my Go launcher... Had 7 screens w/ widgets and shortcuts...
Why did it go wrong again? I thought I put back the recovery to stock to solve the OTA problem... Should I do other things? The phone starts to really slow down and I'm ready to toss this piece of c* in the bin...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I had the same issue just now with my phone (unlocked, rooted, stock revcovery), but a quick reboot allowed the update to complete and I'm now on 4.0.4. Did you check the version number again after this latest attempt?
Yes, still 4.0.2.
And of course, my phone says I'm up to date. Lovely, NAAAAAT!
Sent from my Galaxy Nexus using XDA

GNex rejecting ALL 4.1

RIght, it seems my phone is rejecting all and any 4.1 OTAs and ROMs.
I have tried every combination of stock takju, yakju, OTA, ROMs, recovery, radios the lot.
My phone applies the update ok then when it starts it just sits in a boot loop getting hotter and hotter.
Does anyone know what the hell is going on and what it could be?
Or has anyone else had this problem?
I can happily flash stock Google images (4.0.4), 4.x.x ROMs no problem it just seems to be JB.
Thanks
How long do you let it boot?
Sent from my Galaxy Nexus using xda premium
gchild320 said:
How long do you let it boot?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry, it won't let me post in Dev. (to new to the site)
I let it boot for a good 20-30 mins, iv literally tried everything... WIth root, without root you name it, i tried it
rparkerbsgg said:
Sorry, it won't let me post in Dev. (to new to the site)
I let it boot for a good 20-30 mins, iv literally tried everything... WIth root, without root you name it, i tried it
Click to expand...
Click to collapse
Have you tried super wipe?
Android revolution HD super wipe lite nexus or something of the sort. Its a flash able zip that may help you out.
Sent from my Galaxy Nexus using xda premium
gchild320 said:
Have you tried super wipe?
Android revolution HD super wipe lite nexus or something of the sort. Its a flash able zip that may help you out.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah i did try that to no avail.. its starting to p!ss me off now
Why dont you tell us what exact phone you have, and walk is through a typical ROM installation
Sent from my Galaxy Nexus using xda premium
Try locking then unlocking the bootloader (this should wipe all your data off the phone!). Then flash stock factory images via fastboot. If you still can't boot after doing that then something is wrong with your phone physically.
if you don't have the drivers and fastboot setup:
drivers: http://forum.xda-developers.com/showthread.php?t=1379875&highlight=naked+samsung
fastboot: http://www.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/ (just rename the fastboot and adb .exe's back to their original names w/o the -windows suffix).
factory images: https://developers.google.com/android/nexus/images
edit: or use the toolkit that sarni84 mentioned below - if your not comfortable manually doing it via a command prompt.
Yes I would flash a stock image with the toolkit it should wipe everything it will suck but it seems like your problems are deeper. Then after flashing the 4.0.4 IMG use efrants guide to flash to new 4.1.1
running_penguin said:
Why dont you tell us what exact phone you have, and walk is through a typical ROM installation
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have a GSM Galaxy Nexus from the UK, the day i got it i flashed the factory 4.0.2 image from google to bring it to clean yakju.
When i download a ROM or anything firstly i check the md5, assuming thats all good i follow the install proceedure to the letter (wipe data, cache, dalvik if needed) I have flashed many ROMs on my Nexus as well as my previous S2 and Nexus S before that.
I have literally tried everything from clean install of factory 4.0.4 yakju and takju, lock and unlock boot loader, root and un-root, OTA and custom ROMs but nothing seems to work.
I have even tried restoring a friends nandroid of stock 4.1.1 android via CWM just to see if that works but nothing.
well... so why not stay with 4.0.4 yakju and just wait for stock ROM 4.1.1 yakju to be available and/or working OTA update? why going through all this hassle?
https://developers.google.com/android/nexus/images
rparkerbsgg said:
I have a GSM Galaxy Nexus from the UK, the day i got it i flashed the factory 4.0.2 image from google to bring it to clean yakju.
When i download a ROM or anything firstly i check the md5, assuming thats all good i follow the install proceedure to the letter (wipe data, cache, dalvik if needed) I have flashed many ROMs on my Nexus as well as my previous S2 and Nexus S before that.
I have literally tried everything from clean install of factory 4.0.4 yakju and takju, lock and unlock boot loader, root and un-root, OTA and custom ROMs but nothing seems to work.
I have even tried restoring a friends nandroid of stock 4.1.1 android via CWM just to see if that works but nothing.
Click to expand...
Click to collapse
Sounds like something is broken or your nand flash is corrupted or bad. Probably best to RMA it considering you've tried everything that should have restored it if it wasn't broken.
Hannes The Hun said:
well... so why not stay with 4.0.4 yakju and just wait for stock ROM 4.1.1 yakju to be available and/or working OTA update? why going through all this hassle?
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I got the official OTA from our friends at google (i didn't do the framework services clear) it just came through.
i got the whole 145mb download, it verifies, reboots to the android guy with his front open, loads fine then on reboot, nothing, just the big X boot screen looping out.
It was after that didn't work that i explored the ROM route with the same results

Jb 4.1

To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Jpcsilva said:
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Click to expand...
Click to collapse
Flash your phone back to stock... then do the ota update... profit...
Sent from my Galaxy Nexus using xda app-developers app
Everything must must be bone stock to install an ota.
Jellin' like a felon
The issue at hand here is that you have a custom recovery. I can't say that if you remove CWM that you'll be able to OTA update, but that's at least what was the problem there. Now, if you want to keep all your apps and update to the OTA jelly bean instead of the Google I/O preview build, you can flash this here: http://forum.xda-developers.com/showthread.php?t=1737849
Follow the instructions on that post to update. This is what I did and it worked perfectly.
Camera not working after JB update!
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
nishantbhatia84 said:
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
Click to expand...
Click to collapse
What Rom? Custom or stock
What kernel? Custom or stock
Sent from my Galaxy Nexus using Tapatalk 2
And how do i do that? I really dont know how to flash it
Sent from my Galaxy Nexus using xda app-developers app
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
nishantbhatia84 said:
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
first try factory reset, otherwise yes go back to stock ics and check.
Jp182
atifsh said:
first try factory reset, otherwise yes go back to stock ics and check.
Click to expand...
Click to collapse
But going to factory reset will not remove the cwm recovery... right? If i go to factory data reset on my phone ( remember i am using a 4.1 rom) will it go back to ics and delete all roms / root? Cause this sounds like the best way to do it, but you were the first one that said that. Bought my phone from Amazon unlocked ( do you guys think it is gonna update?)
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
I don't get it. What did you do? Factory reset? Installed the stock?
Sent from my Galaxy Nexus using xda app-developers app
HELPPPPPP
nishantbhatia84 said:
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PLZ, tell me!! If I do the factory reset is it gonna remove CWM, and all stuff i have installed?
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ok
phazerorg said:
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Sorry man, I know i am not giving a lot of information, but that's cause i really don't know. I did a random "how to update your galaxy nexus to 4.1" tutorial, and i don't even remember where...... I just know the links i download were from here.
So what i am going to do:
1: Factory data reset
2: I think it's going back to ICS
3: Just do the normal system update that should just pop up.
My only fear is if the phone does not ask for update.
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Factory reset factory reset
phazerorg said:
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Click to expand...
Click to collapse
I want to restore it VIA FACTORY RESET. Cant i?
Jpcsilva said:
I want to restore it VIA FACTORY RESET. Cant i?
Click to expand...
Click to collapse
No, that will just wipe data. You'll have a clean phone, but with the same ROM you currently have. The phone doesn't keep a copy of the stock firmware hidden away or anything like that. Efrant's guide is the proper way to restore everything back to stock.

Error while updating to 4.3 OTA

I received an update notification through OTA, and I've start the upgrade process, the device restarted to do the upgrade, but while upgrading it gave an error and hanged, I've removed the battery and start the phone, but I'm still on 4.2.2, and whenever I try to check for update it gave that there's no update.
???????
Sent from my Galaxy Nexus using xda app-developers app
Forget to tell that my device is yakju
Sent from my Galaxy Nexus using xda app-developers app
Is your phone stock? If you're rooted and made any modifications to system files (mods, build.prop edits, etc) your phone will fail during the OTA. You need to be completely stock on the latest 4.2.2 radios for your model. Basically you have to be more or less on the 4.2.2 OTA to get 4.3.... always been like that for every android version though.
Can't you fasboot flash the factory images?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
RoyJ said:
Is your phone stock? If you're rooted and made any modifications to system files (mods, build.prop edits, etc) your phone will fail during the OTA. You need to be completely stock on the latest 4.2.2 radios for your model. Basically you have to be more or less on the 4.2.2 OTA to get 4.3.... always been like that for every android version though.
Can't you fasboot flash the factory images?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Exactly what happened to me. So, I flashed factory images, received OTA for 4.2.2, cleared Google Services Framework several times, 4.3 showed up. In process of installing. Good to go.
I think flashing the image it's the easiest way, any one had the link for yakju?
Sent from my Galaxy Nexus using xda app-developers app
Also happened to me. Cleared "Google Services Framework" and tried to re-install 4.3 when it came down.
Still got an error
Any ideas?
ronsher said:
Also happened to me. Cleared "Google Services Framework" and tried to re-install 4.3 when it came down.
Still got an error
Any ideas?
Click to expand...
Click to collapse
are you on a completely stock rom? if not, it will always fail.
My friend has problem too
I rooted and install custom reovery and costume kernel for him
He got 4.3 OTA update but he get error in installing
would somebody tell me what can I do for him?
hes_luckey said:
My friend has problem too
I rooted and install custom reovery and costume kernel for him
He got 4.3 OTA update but he get error in installing
would somebody tell me what can I do for him?
Click to expand...
Click to collapse
wow.... does no one read anything? there's a thread exactly like this in Q/A, and i even said the reason it will fail not 1 post above yours... my mind is blown at the pure laziness that you have shown.

Categories

Resources