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.
Related
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
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.
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?
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.
I have a i9250 gsm Galaxy Nexus, maguro. JWR66V. It used to be Yajuux but I changed this to Yakju with Wug Fresh's Nexus Tool kit. I manually updated my phone to 4.3. However, about once a week, I get a notice that my phone would like to update to 4.3. The download is only 1.7mb. Once I allow the update, the phone reset, boots up and says "installing system update" with the android mascot on the screen and a swirly atom-thing at his stomach. After about a minute a message comes up that says "error!" with the android mascot now on his back. I have to remove the battery and restart my phone, otherwise it hangs. The update notice won't come back for another week, unless I stop the google service framework app and clear the data. I'm assuming these system updates are to upgrade to JWR66Y, but I don't know why I keep having these errors. Any help/advice would be appreciated.
Figured it out
Solved. I managed to sideload the update through the Nexus toolkit. Even after updating though, it didn't show the correct version. I had to unroot by uninstalling supersu (survival mode didn't work), then doing the OTA update, then reinstalling the binaries for Supersu.
Can anyone recommend a good site/feed that keeps track of these security updates/other major updates?
And the toolkit gets the credits, even when the user still has no idea what just happened.
beekay201 said:
And the toolkit gets the credits, even when the user still has no idea what just happened.
Click to expand...
Click to collapse
braindead users win again!
No Clue..
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
dipenv said:
Can someone, Experienced.. Tell me what exactly to do here.. I am on Stock Rom, Rooted, with TWRP Recovery. Exact same problem when I try to install the Update. Same 1.7 MB Update. Any Help would be much appreciated.
Click to expand...
Click to collapse
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for this explanation. Very helpful to braindead user like myself, and will help me know what to do for future updates.
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Does doing this wipe the phone?
Not if you only install the update. You will have to reinstall supersu after the update because you will lose root.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
The reason the update doesn't install is because you are using a third party recovery.img (twrp) and Android cannot update your phone with twrp, only with it's own recovery. You can download the update posted in one of the threads and install from twrp.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Zepius said:
thats not correct. ive updated with OTAs through TWRP.
the update is failing because something isnt stock.
Click to expand...
Click to collapse
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Update through twrp by downloading the update not through ota since you have third party software.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Requesting the download link if possible. Searched the forum but couldn't found one. Tx in Advance.
Solved. Got it! HERE