Develop Bugs

NOT able to update

i converted my galaxy nexus from yakjuxw to yakju
and even i got a 4.1 jelly bean update official by google
downloaded that file and after successful installation ask me to reboot and install option
and process starts but it continues just for few seconds and after that some error comes and by default it switch back to ICS
I TRY THIS 4-5 times but it showing me same error......
plz help
pranav:crying:

Not 100% sure but the update could be for yakjuxw. In which case it would explain error.

Taysider said:
Not 100% sure but the update could be for yakjuxw. In which case it would explain error.
Click to expand...
Click to collapse
If he has a yakju device, he wouldn't receive a yakjuxw update... not to mention that there's no 4.1 for yakjuxw yet.

If you have installed a custom recovery or changed anything with the phone's system, the update will fail.
Sent from my Galaxy Nexus using Tapatalk 2

You should be on XXLA2 Radio and latest bootloader
Sent from my Galaxy Nexus using xda app-developers app

Other than that it might help if you told us what the error message said...

OTA

I'm on a 4.2 ROM and I cannot get the OTA Update message out of my status bar asking me to install 4.2. How do I get rid of it? Any help would be greatly appreciated.

Bump
Sent from my Galaxy Nexus using xda app-developers app

Its for 4.2.1
Sent from my Galaxy Nexus using Tapatalk 2

I got it once, but when I tried to install it, it failed (and the notification disappears btw). Can anyone tell me if its because of a custom kernel that the ota installation fails? Is there any way to force it? Where is the ota zip stored?
Sent from my Nexus Prime JB 4.2

Right. But if I update is it going to brick and/or unroot my phone? These are things I do not want to happen so I would like to know before I go ahead with it.
Sent from my Galaxy Nexus using xda app-developers app

Obviously flashing an OTA is going to unroot your phone (assuming it even installs). But it won't lock your bootloader so it will take 5 seconds to re root.

I'd rather not deal with it but I guess I'll probably have to anyway. I was just wondering if there is anyway to get rid of the message without installing it? Maybe flashing a 4.1.2 ROM?
Sent from my Galaxy Nexus using xda app-developers app

bbaaccoonn said:
I'd rather not deal with it but I guess I'll probably have to anyway. I was just wondering if there is anyway to get rid of the message without installing it? Maybe flashing a 4.1.2 ROM?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
huh....if you flash a custom rom, no OTA update should ever appear. Nor could you ever run a official OTA update.

bk201doesntexist said:
huh....if you flash a custom rom, no OTA update should ever appear. Nor could you ever run a official OTA update.
Click to expand...
Click to collapse
Actually a notification for the ota can show up if your running a custom ROM, and you can run it, but as soon as it tries to install through recovery, it just fails/aborts.
I had it happen to me awhile back when I was running Pa
Sent from my Galaxy Nexus using xda premium

OTA 4.2 to 4.2?
I have gsm maguro which I recently flashed stock 4.2 takju from 4.1.2 yakju.
I did not expect to be looking at an OTA update notice wanting me to update to 4.2 (which I am already on).
I would have thoght the update manager would check the build and version of my phone before offering update. Could it be that because I did an official OTA update from 4.1.1 yakju to 4.1.2 yakju that I am marked down as being on 4.1.2 now, and so is now offering 4.2 without checking the current build and version I am running.
I would like to know how to get rid of that update notification from my status bar if I can, or if I should do the update anyway. At the moment I have unlocked bootlocker but no root. I can not remember if OTA would wipe my apps and data, am guessing no as bootlocker already unlocked?
Some expert advice would come in handy. You know what an expert is yeah? X is an unknown quantity and a spurt is a drip under pressure.
Hmm, what to do. Nexus wizards, please advise. I have started downloading the 4.2.1 factory image anyways but I would still like to know what would be recommended in the situation I was in. I am fairly new, though I have learned to flash stock roms with adb, and have stuck with stock roms for the moment while I get the hang of things. Not sure if I get updates from google now or from Samsung. Am guessing google, but then why would google not offer to update me to 4.2.1 seeing as it is now out rather than to 4.2?
Shtrangeness.:cyclops:
---------- Post added at 08:13 PM ---------- Previous post was at 07:45 PM ----------
LiquidXed said:
Its for 4.2.1
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
When this gentleman says "Its for 4.2.1" I am guessing that he is saying the update which reads
"This software will upgrade your Galaxy Nexus to Android 4.2 Jellybean..." is actually the 4.2 to 4.2.1 OTA update, just not marked properly?
I just love it when things are marked incorrectly, makes life so much less confusing? They should always do that to keep me in a continuous state of bewliderment. New google policy, mark every file with the name of the file which preceeds it, except on Sundays, when they should be marked in any manner whatsoever.
Thanks for the answer bloke. You are the bees knees. I did kind of have an inkling that it might be 4.2.1. Crazy boyz and girlz. Just mad. Somewhere between irrational, nearly right, not correct, and just plain silly.

Updated, Rooted, and now I get an update?

So I updated to 4.1.2 recently and decided I'd simply root my phone. Now today I have the AT&T updater telling me I have an update pending. I'm already on 4.1.2 and the only possible reason I could conceive as to why this is popping up is because during rooting something must have changed and that flagged the updater as me having an obsolete firmware. Anyone else getting this?

mrmcpowned said:
So I updated to 4.1.2 recently and decided I'd simply root my phone. Now today I have the AT&T updater telling me I have an update pending. I'm already on 4.1.2 and the only possible reason I could conceive as to why this is popping up is because during rooting something must have changed and that flagged the updater as me having an obsolete firmware. Anyone else getting this?
Click to expand...
Click to collapse
What is your current firmware
Sent from my GT-N7105 using xda premium

4.1.2 Baseband I317UCALK7 Build Number JZO54K.I317UCALK7

mrmcpowned said:
4.1.2 Baseband I317UCALK7 Build Number JZO54K.I317UCALK7
Click to expand...
Click to collapse
The latest is actually I317UCAMA4; the ALK7 is the one right before that

Thanks, I have TWRP installed so do I have to reinstall the stock recovery and then continue the update and whatnot?

Don't waste your time with the ATT update; just flash almost any custom ROM, and you will have all the benefits plus much more...

wase4711 said:
Don't waste your time with the ATT update; just flash almost any custom ROM, and you will have all the benefits plus much more...
Click to expand...
Click to collapse
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Sent from my GT-N7105 using xda premium

Android The Greek said:
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
I've tried this, but the update still fails. Could it be my modified system files from setting up Google wallet?
Sent from my Nexus 7 using xda app-developers app

bookem11 said:
I've tried this, but the update still fails. Could it be my modified system files from setting up Google wallet?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Could be, I always keep a stock backup jsut incase. You can always dirty flash a stock rom and see if that works
Sent from my GT-N7105 using xda premium

If you are going to stick with stock, you may want to use autoruns to disable the check for updates. That way at least the notification will go away.

Android The Greek said:
I agree, but if you want to upgrade, use cf auto root to reinstall stock recovery, use full unroot in super su, then run update
Click to expand...
Click to collapse
I did all of the above. Update was downloaded successfully, Phone reboot itself and started installing update. And than "updated was interrupted" message popped out. I've tried it several times with the same result.
Any ideas what I'm doing wrong?

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.

[Q] Unable to update to JWR66Y from JWR66V

Of my galaxy nexus, the build number of recent firmware is JWR66V of Takju updated one month or longer ago. The phone showed twice of notice of updating to JWR66Y, so then pressed button to reboot and install. I did not watch the whole installing. After booting, the build number I checked was still JWR66V. I tried pressing the "Check now" button in "System updates", but no response and still showed "Last checked for updates on Jul 31."
Anyone can give help with that? Thanks a lot.

You are probably rooted and with custom recovery.... That's why the update failed.
The update package is at /cache.
From SuperSu do a full unroot, re-apply stock recovery and try update again.
Sent from my Galaxy Nexus using xda app-developers app

wisefreakz said:
You are probably rooted and with custom recovery.... That's why the update failed.
The update package is at /cache.
From SuperSu do a full unroot, re-apply stock recovery and try update again.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thank you very much!
Surely I did not (never) get it rooted and no custom recovery. I only use it as the second (spare) phone, so I keep the system entirely original and installed some common software. I checked the /cache directory with estrong explorer, but it showed empty.
Is that could be because Yakju model using Takju firmware?
Weird. Keep waiting for answer.

pursuefun said:
Thank you very much!
Surely I did not (never) get it rooted and no custom recovery. I only use it as the second (spare) phone, so I keep the system entirely original and installed some common software. I checked the /cache directory with estrong explorer, but it showed empty.
Is that could be because Yakju model using Takju firmware?
Weird. Keep waiting for answer.
Click to expand...
Click to collapse
Weird...! There is no yakju or takju hw.... They are sw bundled to different countries... I dunno if being unrooted you can see what's in the cache folder...
Sent from my Galaxy Nexus using xda app-developers app

wisefreakz said:
Weird...! There is no yakju or takju hw.... They are sw bundled to different countries... I dunno if being unrooted you can see what's in the cache folder...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I was wondering if I can see files in /cache without rooted, too. But, I don't want to root it for that. Maybe I will flash the whole firmware of JWR66Y, if the problem can't be solved.
Thank you very much.