Hi,
As the title says, I still don't have 4.2 update for my Galaxy Nexus and I can't make it to update. I tried the trick by clearing cache from Google Services Framework app but still can't make it to update.
Couple of days ago I needed to restart it, and I think then started to upgrade, but I didn't have time then to wait so I needed to skip the update, but since then nothing helps. This should heve been updated long ago.
The device is not carrier specific and it was bought from Amazan.
Anyone any idea on what I can do?
Thanks!
1.) root
2.) flash rom
3.)????
4.)profit!
gileShake said:
Hi,
As the title says, I still don't have 4.2 update for my Galaxy Nexus and I can't make it to update. I tried the trick by clearing cache from Google Services Framework app but still can't make it to update.
Couple of days ago I needed to restart it, and I think then started to upgrade, but I didn't have time then to wait so I needed to skip the update, but since then nothing helps. This should heve been updated long ago.
The device is not carrier specific and it was bought from Amazan.
Anyone any idea on what I can do?
Thanks!
Click to expand...
Click to collapse
use search, this question has been beaten into the ground.
You most likely have the jc003 build International GNex. That one depends on Samsung for OTA updates. I got a used one from Amazon and this was the case. You should just root it and update it manually. Yeah it is a pain in the ass but there isn't another way. It takes some time to get everything correctly set up but it is easier than you might think.
U gotta root and flash 4.2.1..I had the same issue with my gnex that I got fron ebay
Sent from my Galaxy Nexus using xda app-developers app
neo_x22000 said:
U gotta root and flash 4.2.1..I had the same issue with my gnex that I got fron ebay
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
you do not need root. dont spread mis-information.
Zepius said:
you do not need root. dont spread mis-information.
Click to expand...
Click to collapse
So, what is the solution then? I just wait?
Can't you just flash the Google firmware via fastboot?
Sent from my Galaxy Nexus using xda premium
gileShake said:
So, what is the solution then? I just wait?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Use nexus root toolkit unlock boot loader, factory reset using factory image 4.2.1 downloaded from the upper link relock bootloader or root at your choice...
Sent from my Galaxy Nexus using Tapatalk 2
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
VZW Galaxy Nexus finally got thr uodate, but when i tried to apply it, fail. No reason given. Anyone have this happen? I am running stock and I do have root.
Sent from my Galaxy Nexus using xda app-developers app
mfratto said:
VZW Galaxy Nexus finally got thr uodate, but when i tried to apply it, fail. No reason given. Anyone have this happen? I am running stock and I do have root.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
3 options:
a) make sure you didn't change anything system-wise (like build.prop, system apps) if you did go back and restore those changes. then rerun OTA.
b) call vzw tell them you want your jellybeanz why didn't it go through wtf
c) take matters into your own hands, flash cwm/twrp, and check this thread here.
Yes. Sorry for the spaz. My bad.
Working through all the posts now. Should have done that first.
Sent from my Transformer Prime TF201 using XDA Premium HD app
What build of 4.0.4. do you have? It probably wont work if you have imm30b. You will need to upgrade to imm76k first
mfratto said:
Yes. Sorry for the spaz. My bad.
Working through all the posts now. Should have done that first.
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
working
ngabdala said:
What build of 4.0.4. do you have? It probably wont work if you have imm30b. You will need to upgrade to imm76k first
Click to expand...
Click to collapse
I do have IMM76K. I did not read/search the forum first. I had installed GoogleNow, but when I tried to restore back to stock voice, some of the files did not get replaced properly. That was causing the update failure. Once I replaced those, it is updating.
mfratto said:
I do have IMM76K. I did not read/search the forum first. I had installed GoogleNow, but when I tried to restore back to stock voice, some of the files did not get replaced properly. That was causing the update failure. Once I replaced those, it is updating.
Click to expand...
Click to collapse
if it is settled then, op, please update thread title with "[Solved]" at the beggining? thanks.
sent from my i9250
post your OTA availability and experience updating it...lucky Poland is first!
This is good the international version. Not ours.
Sent from my SGH-I747 using Tapatalk 2
Exactly. We will be a bit farther down the road
Sent from my SGH-I747M using xda premium
Hopefully the AT&T version isn't far behind.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Someone will tweak it to work for AT&T
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
well i spoke to Samsung and they said in the past they use to wait for Bell , Rogers , Telus , but not anymore as the update is made for all samsung s3 canadian via ota and they no more need the provider so it should be fast and the proof is all galaxy s3 get the update in the same time . all application are update it via Google play so let's see .time will tell .
Question, since I'm rooted, would I have any issues with installing this upgrade?
T-Mobile US got 4days ago
Sent from my SAMSUNG-SGH-I747 using xda premium
Obsessive said:
Question, since I'm rooted, would I have any issues with installing this upgrade?
Click to expand...
Click to collapse
Well there are great apps out there, I use Voodoo OTA. And it creates a backup of your root, then you have the option to do a temp unroot so when you are doing the update OTA (only works for OTA updates), the update won't detect that your device is rooted and after upgrade complete, open up Voodoo OTA, click Restore Root and voilà!
This should work all of the time, but I haven't tested it in a real scenario yet.
Let me know what happens!
Michael
oriveradel said:
T-Mobile US got 4days ago
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Final version?
oriveradel said:
T-Mobile US got 4days ago
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
They got JB 4 days ago? Wasn't in the news anywhere...
I thought they were starting out with Europe then probably coming here?
oriveradel said:
T-Mobile US got 4days ago
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I think you are referring to another leak. The first official JB update has come only for Poland.
greenglue said:
Well there are great apps out there, I use Voodoo OTA. And it creates a backup of your root, then you have the option to do a temp unroot so when you are doing the update OTA (only works for OTA updates), the update won't detect that your device is rooted and after upgrade complete, open up Voodoo OTA, click Restore Root and voilà!
This should work all of the time, but I haven't tested it in a real scenario yet.
Let me know what happens!
Michael
Click to expand...
Click to collapse
FrankJL_ said:
Final version?
Click to expand...
Click to collapse
Thanks for the response. I'm currently using ClockwordMod and since I'm still newbish I think I'll wait until others are able to install this upgrade on their device.
Obsessive said:
Thanks for the response. I'm currently using ClockwordMod and since I'm still newbish I think I'll wait until others are able to install this upgrade on their device.
Click to expand...
Click to collapse
Hi!
I was talking about official updates only with the OTA(over-the-air/wirelessly). So if you're in USA/CAN you'll have to wait for the JB update to come over here first then get pushed out to devices, then before update sue the app.
Michael
This is awesome news. Quick question though, since I'm new to the SGSIII. If I "disabled" some apps under the application manager, can I still install the OTA when it comes around? I'm not rooted or anything, I just got the phone a couple days ago and don't feel like voiding my warranty quite yet
shiftylock said:
This is awesome news. Quick question though, since I'm new to the SGSIII. If I "disabled" some apps under the application manager, can I still install the OTA when it comes around? I'm not rooted or anything, I just got the phone a couple days ago and don't feel like voiding my warranty quite yet
Click to expand...
Click to collapse
You dont need to disable anything. You are on stock - so wait until the OTA is released. It will inform you, and just let it download and install.
Wond3r said:
You dont need to disable anything. You are on stock - so wait until the OTA is released. It will inform you, and just let it download and install.
Click to expand...
Click to collapse
I think he was asking if he has some apps disabled, vs rooting to remove them, if it'll be an issue to install OTA. I have all the Rogers apps disabled, since I'm not using the Rogers network. I don't see any issue with the OTA working, since no system files were changed, you're just telling them to not run. Worst case, just re-enable them when you know the OTA is out, do the update and disable the apps again. That's my plan!
Just tried to update with the "check for updates" : option under settings and it didn't work. My phone is rooted, and so when it rebooted (it props for reboot and install) it went into CW and aborted install. Is there a way around this?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
martiantakeover said:
Just tried to update with the "check for updates" : option under settings and it didn't work. My phone is rooted, and so when it rebooted (it props for reboot and install) it went into CW and aborted install. Is there a way around this?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Are you in Poland? So far its only rolling out in Poland for the International Exynos S3
roriii said:
well i spoke to Samsung and they said in the past they use to wait for Bell , Rogers , Telus , but not anymore as the update is made for all samsung s3 canadian via ota and they no more need the provider so it should be fast and the proof is all galaxy s3 get the update in the same time . all application are update it via Google play so let's see .time will tell .
Click to expand...
Click to collapse
Wat
Herp derp SGS3 Tapatalk 2
Just bought my Nexus a little over a week ago as to an S3 can't seem to update to jelly bean for some reason though..help?
Sent from my Galaxy Nexus using xda app-developers app
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Misledz said:
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Click to expand...
Click to collapse
Don't use a toolkit. Learn how to unlock bootloader and fastboot on your own as it is better than having it spoon fed
Did you try going into Settings > Apps > All Applications > Google Services Framework & Clear cache / Clear data? Sometimes doing that will make it work. Try that. Don't use a toolkit...
Misledz said:
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Click to expand...
Click to collapse
Let's not forget needs about toroplus.. don't need Verizon stuff on sprint. Adb is so easy! Use that! Toolkit is for halfa++ corner cutters
After you clear cache go to your dialer and type *#*#checkin#*#* and wait for confirmation then immediately go to settings about phone and update.
Based on the screen shot, it's gsm but build number isn't there. What build is the Op on? So far it's only yakju/takju, yakjuxw, yakjuxe, and yakjuzs that have jb so if he's on a different build and really want jb, then he needs to flash but if he can wait, then he has to wait still
Sent from my Galaxy Nexus using Tapatalk 2
you just unlock bootloader using toolkit
Sent from my Galaxy Nexus using Tapatalk 2
arrish4 said:
you just unlock bootloader using toolkit
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Stop that. Hold-your-hand-kits are bad.
Sent from my Galaxy Nexus using xda premium
arrish4 said:
you just unlock bootloader using toolkit
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Don't you look out for traffic when crossing the road?
Someone already got knocked over and you still want to try cross a highway.
Pics not showing on my end....and three simple words
fastboot oem unlock
Doesn't get easier than that.
And if just trying to get updates then do the checkin dialer. It forces the update to push
I was stuck on 4.0.3 for a week and just got tired of waiting and just rooted and loaded the stock 4.1.1 rom. This was my first time rooting and loading the rom. Wasn't hard at all.
Sent from my Galaxy Nexus using xda app-developers app
Misledz said:
Lol. Just download the Tool Kit and the official Google 4.1.1 firmware that is available from their site (Links are in Development Section | Official Firmware links) make sure you know if your's is maguro or toro, then download the respective firmware and flash it via ToolKit.
Click to expand...
Click to collapse
how do I check whether mine's maguro or toro?
RoyJ said:
Did you try going into Settings > Apps > All Applications > Google Services Framework & Clear cache / Clear data? Sometimes doing that will make it work. Try that. Don't use a toolkit...
Click to expand...
Click to collapse
tried that doesn't work. What's wrong with a toolkit? Everybody's telling me not to use it...
thephantom said:
Based on the screen shot, it's gsm but build number isn't there. What build is the Op on? So far it's only yakju/takju, yakjuxw, yakjuxe, and yakjuzs that have jb so if he's on a different build and really want jb, then he needs to flash but if he can wait, then he has to wait still
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here. Trying my best not to root or whatever for now. Stock for now!
Sent from my Galaxy Nexus using xda app-developers app
Seems to be a yakjuxw from the new screen shot. Since you have gsm, it's maguro. You should be getting the jb update already
Sent from my Nexus 7 using Tapatalk 2
JC0406 said:
how do I check whether mine's maguro or toro?
tried that doesn't work. What's wrong with a toolkit? Everybody's telling me not to use it...
Here. Trying my best not to root or whatever for now. Stock for now!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You don't need to root it to load the factory image from Google. You only need the bootloader unlocked and you can do it through fastboot. Really very simple That's your best bet. As far as the first toolkit, I don't think there's any harm in using it specially if you're just going to use it to flash the factory image and unlock bootloader.
Try going to menu, options, applications, scroll over to all applications and clear data on Google services framework, Then go to about phone, system updates. That's what I did for the ota jb.
Sent from my Galaxy Nexus using xda app-developers app
rock7632 said:
You don't need to root it to load the factory image from Google. You only need the bootloader unlocked and you can do it through fastboot. Really very simple That's your best bet. As far as the first toolkit, I don't think there's any harm in using it specially if you're just going to use it to flash the factory image and unlock bootloader.
Click to expand...
Click to collapse
Hmm okay thanks. That will void the warranty won't it? Is there a thread about it already in the development thread?
evostevo1 said:
Try going to menu, options, applications, scroll over to all applications and clear data on Google services framework, Then go to about phone, system updates. That's what I did for the ota jb.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Tried that already. Doesn't work.
Sent from my Galaxy Nexus using xda app-developers app
Do check out the threads made by efrant so you can see the processes for it. They're very simple and you'll learn a lot as well.
Sent from my Galaxy Nexus using Tapatalk 2
JC0406 said:
Hmm okay thanks. That will void the warranty won't it? Is there a thread about it already in the development thread?
Click to expand...
Click to collapse
Not really. If you want to claim warranty, you can always lock the bootloader. And just use the toolkit from the thread in the development section. Remember you only have to do 2 things, unlock bootloader and flash factory image for 4.1.2.
zephiK said:
Don't use a toolkit. Learn how to unlock bootloader and fastboot on your own as it is better than having it spoon fed
Click to expand...
Click to collapse
I would agree with you completely. But I feel you're going to spend more time explaining it to someone who would rather take the easier way out than do all that. Yesterday had to explain to a 40 year old, father of two what adb was that I felt he was probably not ready to start sipping from the advanced user's method. I spent an hour trying to explain everything, what more if there was no toolbox?
Sent from my Galaxy Nexus using Tapatalk 2
Misledz said:
I would agree with you completely. But I feel you're going to spend more time explaining it to someone who would rather take the easier way out than do all that. Yesterday had to explain to a 40 year old, father of two what adb was that I felt he was probably not ready to start sipping from the advanced user's method. I spent an hour trying to explain everything, what more if there was no toolbox?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I agree with you, but if there is no toolkit, it won't be like this, people will have to learn adb and fastboot. Forces the newbs to learn adb and fastboot.
Well since it seem like he only look at posts recommending toolkits, his on you guys...............
And yes, wrong section, questions goes to the Q&A section.
Beamed from my Grouper.
I decided to go back to 4.1.2, unlocked and rooted
of course now I am getting OTA notification: how can I get rid of this?
thegios said:
I decided to go back to 4.1.2, unlocked and rooted
of course now I am getting OTA notification: how can I get rid of this?
Click to expand...
Click to collapse
I followed the advice of a post I found somewhere on a forum and deleted the OTA upgrade package from /cache and then said "Ok" to the upgrade. It failed to complete, at which point I haven't been bothered about upgrading since, even after rebooting.
I used the FOTAKill.apk file. Moved it to the system/app folder, rebooted into recovery, wiped cache and no more notification.
Flash cm10 stable lol.
Sent from my Nexus 7 using xda premium
Switch to yakju, in all seriousness how come you went back to 4.1.2m
Sent from my Galaxy Nexus using xda premium
Guessing cause 4.2 is horridly laggy (on top of other issues). Thinking of doing same myself.
msavic6 said:
Switch to yakju, in all seriousness how come you went back to 4.1.2m
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using xda premium
thegios said:
I decided to go back to 4.1.2, unlocked and rooted
of course now I am getting OTA notification: how can I get rid of this?
Click to expand...
Click to collapse
By allowing it to complete your ROM upgrade if your running stock
Sent from my Galaxy Nexus
msavic6 said:
Switch to yakju, in all seriousness how come you went back to 4.1.2m
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
besides having many bugs, my phone with 4.2 is waking up with no apparent reason every 30 minutes or so
You method work for me. After reading the feedback from user using 4.2, I decided to stay with my old trusty 4.1.2.
highvista said:
I followed the advice of a post I found somewhere on a forum and deleted the OTA upgrade package from /cache and then said "Ok" to the upgrade. It failed to complete, at which point I haven't been bothered about upgrading since, even after rebooting.
Click to expand...
Click to collapse
garrychau said:
You method work for me. After reading the feedback from user using 4.2, I decided to stay with my old trusty 4.1.2.
Click to expand...
Click to collapse
worked 4 me as well thanks
Hey All,
Just got a friends Nexus and it was last used with 4.1.2 jellybean, I tried updating via OTA in settings but there is no update there and says my phone is up to date. I'd like at least 4.2.2 although 4.3 would do well
I've tried using methods of clearing data from the Google framework but that did not work.
Also I have only just installed everything i want on it as i had to factory reset.
Any help?
Thanks in advance
Hunglikeagecko said:
Hey All,
Just got a friends Nexus and it was last used with 4.1.2 jellybean, I tried updating via OTA in settings but there is no update there and says my phone is up to date. I'd like at least 4.2.2 although 4.3 would do well
I've tried using methods of clearing data from the Google framework but that did not work.
Also I have only just installed everything i want on it as i had to factory reset.
Any help?
Thanks in advance
Click to expand...
Click to collapse
Which nexus do you have? There are several variants.
How would it find that out?
I'm not this bad with technology but am new to this device aha
Thanks for your help
Sent from my Galaxy Nexus
Hunglikeagecko said:
How would it find that out?
I'm not this bad with technology but am new to this device aha
Thanks for your help
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Which carrier is it for?
DR3W5K1 said:
Which carrier is it for?
Click to expand...
Click to collapse
Its unlocked, Australian. That's all I know, in the about phone section of the settings it says the model is Galaxy Nexus.
Hunglikeagecko said:
Its unlocked, Australian. That's all I know, in the about phone section of the settings it says the model is Galaxy Nexus.
Click to expand...
Click to collapse
LOL OKAY... Well you have a GSM model since the phone is outside of US.
http://forum.xda-developers.com/galaxy-nexus/general/ref-official-google-ota-update-urls-t1419170
Try this ^ guide.
BTW your device is a maguro just so you know.
DR3W5K1 said:
LOL OKAY... Well you have a GSM model since the phone is outside of US.
http://forum.xda-developers.com/galaxy-nexus/general/ref-official-google-ota-update-urls-t1419170
Try this ^ guide.
BTW your device is a maguro just so you know.
Click to expand...
Click to collapse
On that guide there are many code names for different devices, which one do you think that mine would be?
Thank you so much for your help!
CWM->restore = vuole , mmm you have CWM don't you?
Išsiųsta naudojantis Galaxy Nexus Tapatalk 4 Lt
Hunglikeagecko said:
On that guide there are many code names for different devices, which one do you think that mine would be?
Thank you so much for your help!
Click to expand...
Click to collapse
Maguro
Search on google for nexus factory images and download adequate for your gnex and flash of course
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
remabrate1 said:
Search on google for nexus factory images and download adequate for your gnex and flash of course
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
With fastboot. No toolkits of course.
Sent from my Galaxy Nexus using xda app-developers app
and to add to this, to find all relevant info on your build I believe you can find it in bottom left when you boot into fastboot/bootloader
which is done by holding both volume buttons and power button down all at the same time
I'm not this bad with technology but am new to this device aha
I think I may have screwed up pretty majorly,
I rooted and installed cwm as usual and tried flashing updates but that didn't work
Then I decided that I would install a custom ROM on it which I wasn't going to, so now I'm stuck as I wiped data and tried flashing both pa and slim but both failed, I assume this is because of an older version of cwm which was used because it was needed to flash the updates.
So now I am stuck without an os and when I boot it just goes through the Google logo twice then goes to cwm.
What is suggested for these situations aha? Thanks
Hunglikeagecko said:
I think I may have screwed up pretty majorly,
I rooted and installed cwm as usual and tried flashing updates but that didn't work
Then I decided that I would install a custom ROM on it which I wasn't going to, so now I'm stuck as I wiped data and tried flashing both pa and slim but both failed, I assume this is because of an older version of cwm which was used because it was needed to flash the updates.
So now I am stuck without an os and when I boot it just goes through the Google logo twice then goes to cwm.
What is suggested for these situations aha? Thanks
Click to expand...
Click to collapse
Just use adb sideload. Saved my ass a couple of times too.
Thanks but I found a really good method on XDA because I believe it was soft bricked. I used Odin to flash stock 4.2.2 and that got rid of root and custom recovery. Once that was done I then updated to 4.3 in the settings via ota
Thank you for all you help
I have no idea about any of this adb sideload stuff so I'll learn about it before I screw up next time aha